Opinion
By Burt Dicht
NSS Space Coast Correspondent
On April 19, I was at Jetty Park in Cape Canaveral and watched Blue Origin’s New Glenn rocket thunder into the morning sky on its third flight (illustrated above before launch). It was a spectacular launch. The massive booster performed as expected and successfully landed on the recovery barge in the Atlantic Ocean, demonstrating once again the promise of Blue Origin’s reusable launch system.
The mission was not without challenges. While the first stage performed well, the second stage failed to place its payload into the intended orbit. As a result, the Federal Aviation Administration grounded New Glenn pending an investigation and corrective actions. Just recently, Blue Origin completed that process and received approval to resume flight operations.
That made the events of last night even more difficult to watch.
During a hot-fire test at Space Launch Complex 36, New Glenn Flight 4 suffered a catastrophic anomaly that destroyed the vehicle and appears to have caused significant damage to the launch complex. The images quickly spread across social media, generating a familiar mix of speculation, criticism, and instant analysis.
There is still a great deal we do not know, and that matters. In the first 24 hours after an event like this, social media often fills the information vacuum with confident conclusions. I prefer to start with what we know and allow the engineers and investigators time to do their work.
The first and most important fact is simple: no one was injured. Rockets can be rebuilt. Launch pads can be repaired. People cannot. Whatever the ultimate findings of the investigation, every member of the team went home safely. That is not a small thing.
What We Know So Far
New Glenn was on the pad for a hot-fire test, essentially a dress rehearsal for launch where the engines are ignited with the vehicle held down. It is one of the most demanding ground tests you can run. You load propellant, chill down the hardware, count down, and light the engines in as close to a launch configuration as possible while still remaining on the ground.
From what has been shared publicly, the anomaly occurred as the vehicle was entering that firing sequence. Within seconds, a localized problem became a full-scale fire and then an explosion that destroyed the vehicle and damaged surrounding ground infrastructure.
That is about as far as we can responsibly go right now on the question of what happened. The cause, whether it originated in the engines, propellant systems, avionics, ground support equipment, or some interaction among them will only emerge through a careful investigation. The details will matter, and they will take time.
In the meantime, it is worth stepping back and reminding ourselves why companies conduct tests like this in the first place.
Why Tests Sometimes End This Way
“Space is hard” is a phrase that gets used so often it risks becoming a cliché. The challenge here is not some vague characteristic of spaceflight; it is the very specific difficulty of bringing a brand-new heavy-lift, partially reusable launch system and its supporting ground infrastructure into operation.
A hot-fire test does not simply evaluate engines. It exercises:
- Propellant loading and pressurization
- Valves, sensors, and control software
- Structural loads throughout the vehicle and launch mount
- Ground plumbing, electrical systems, and pad structures
When everything works properly, the test looks almost like a launch, just without the command to release the hold-downs. When something is wrong, the test is designed to reveal it, sometimes dramatically. That is not a failure of the testing process. It is the purpose of the testing process.
History is full of examples where important lessons came from events no one wanted to see. Early Atlas and Titan rockets failed in ways that reshaped their designs. More recently, Starship prototypes and test articles have failed on the pad and in flight, each contributing valuable engineering knowledge and design improvements.
None of this makes an explosion any easier to watch, but it does place it in context. Ambitious new systems rarely evolve without a few very visible setbacks. The key is not whether a program encounters problems. The key is how it responds.
The Path Forward for SLC-36
Space Launch Complex 36 has clearly suffered significant damage (see photos from Florida Today). The launch mount, support structures, and associated ground systems will all require extensive inspection before decisions can be made regarding repair or replacement.
Broadly speaking, Blue Origin and the relevant oversight authorities will need to:
- Secure the site and address any remaining hazards
- Document and assess the damage
- Recover and preserve data and hardware relevant to the investigation
- Conduct a comprehensive root-cause analysis
- Design and implement technical and procedural corrections
- Repair or rebuild affected infrastructure
- Requalify both the launch systems and ground systems through additional testing
None of this will happen quickly. The pace of New Glenn’s return to flight will likely be determined as much by the status of the launch complex as by the findings of the investigation itself.
Yet this is not unfamiliar territory. Throughout the history of the Cape, launch facilities have been damaged by accidents, hurricanes, and other events, only to be rebuilt and returned to service. It is painstaking work, but it is work that has been done before.
Artemis, Moon Bases, and Schedules
Because New Glenn and Blue Origin’s lunar lander programs are part of the Artemis architecture, it is natural to ask what this means for NASA’s plans to establish a long-term human presence on the Moon.
At the time of writing, the honest answer is that we simply do not know the full schedule impact. The loss of a flight vehicle, damage to a launch complex, and the resulting investigation will almost certainly introduce delays. How significant those delays become depends on what investigators discover and how extensive the recovery effort proves to be.
Blue Origin’s role in Artemis extends beyond launching payloads. The company is developing the Blue Moon cargo and crew landers that are intended to support NASA’s long-term lunar exploration strategy. While those programs are separate from New Glenn itself, the rocket is an important part of the transportation architecture envisioned to support them. Any significant delay therefore has the potential to ripple into broader planning and schedules.
At the same time, Artemis was deliberately designed around multiple partners and transportation systems. NASA understood from the beginning that creating a sustainable presence on the Moon would require redundancy and flexibility. SpaceX’s Human Landing System, Blue Origin’s Blue Moon program, SLS, Orion, commercial cargo providers, and international partners all contribute different elements of the overall architecture.
That does not make any individual setback painless, but it does mean the future of lunar exploration does not depend on a single rocket or a single launch pad.
The vision of a true lunar base, supplied regularly, expanded over time, and supported by multiple transportation systems is precisely why having more than one heavy-lift launch provider matters. In that sense, it is in everyone’s interest that Blue Origin successfully work through this setback, regardless of which company’s hardware you may personally favor.
On “Just Put It on Another Rocket”
One idea that surfaces quickly after any launch vehicle setback is the suggestion to simply move a payload to another rocket. In this case, some have already speculated about flying Blue Origin’s Mark 1 cargo lander on a Falcon Heavy.
Exploring alternatives is healthy, but it is important to recognize that launch vehicles and payloads are often tightly coupled. Mark 1, as publicly described, is sized for New Glenn’s larger fairing and tailored to its performance characteristics and mission profile. Falcon Heavy has different capabilities, dimensions, and operational constraints.
Could a future lander be adapted for another launch vehicle? Certainly. Engineers make those kinds of changes all the time. But it is not a simple matter of swapping logos on a payload adapter. Such modifications require significant engineering effort, testing, and time.
For now, the practical focus remains understanding this anomaly and returning New Glenn and SLC-36 to operational status.
Waiting for the Facts
It is tempting, especially in the first news cycle after a dramatic event, to treat every image or video clip as if it reveals the entire story. It does not. Cameras on the beach and phones on the causeway capture the outcome. They do not capture the detailed sequence of events that produced it.
Investigators will examine sensor readings, valve timing data, engine performance information, software logs, thermal conditions, and physical evidence recovered from the site. Hypotheses will be tested and retested. Conclusions will be challenged and verified. That process can be frustrating for those of us watching from the outside. We would all like immediate answers. But waiting for facts is how launch systems become safer and more reliable. Quick explanations are rarely complete explanations.
We Are in This Together
For all the rivalry that gets projected onto different rockets and companies, the launch community is far more interconnected than many people realize. Engineers move between organizations. Ideas are shared through conferences, technical papers, and professional networks. When a major anomaly occurs, people across the industry pay attention and quietly ask themselves a simple question: Could that happen here?
That is how lessons spread.
If you care about seeing people living and working on the Moon, then you care about the health of the entire spaceflight ecosystem, NASA, commercial companies, international partners, and the launch providers that make the logistics possible. New Glenn’s setback is serious, but it is also part of the larger story of developing the transportation systems needed to expand humanity’s presence beyond Earth.
A Personal Reflection
Having followed the space program for most of my life, I have learned that progress is rarely a straight line. The rockets and spacecraft we celebrate today often passed through years of setbacks, redesigns, delays, and failures before achieving success.
The history of spaceflight is filled with examples. From the earliest days of the Space Age through Apollo, the Space Shuttle era, and today’s commercial launch industry, major advances have often been accompanied by setbacks that forced engineers to rethink assumptions, improve designs, and strengthen operations.
Although I have only lived on Florida’s Space Coast for a few years, I have had the privilege of witnessing firsthand the remarkable transformation taking place here. Launches that were once occasional events have become almost routine. New vehicles, new companies, and new capabilities are reshaping the industry and expanding access to space in ways that would have been difficult to imagine just a decade ago.
As someone who watched New Glenn rise from the Cape a little over a month ago, I find the contrast between that successful launch and this week’s explosion striking. One event demonstrated the promise of the vehicle. The other demonstrated the challenges that still remain. Both are part of the same story.
The pad will be cleared. The investigation will run its course. Designs and procedures will be revised. Lessons will be learned. And someday, another New Glenn will stand on a rebuilt Space Launch Complex 36 awaiting its countdown.
When that day comes, it will do so because engineers, technicians, and managers were willing to confront difficult facts, learn from failure, and keep moving forward. That is not a slogan. It is how launch vehicles mature. It is how exploration advances.
And it is how the future of spaceflight has always been built.
