Recalling the 2016 SpaceX Falcon 9 Failure
A former NASA engineer named John Muratore served as launch director during an early September 2016 static fire test of a Falcon 9 rocket in Florida. Propellant loading had proceeded normally ahead of a planned launch two days later. Without warning the vehicle detonated, producing a violent fireball that destroyed the rocket, damaged substantial portions of the launch site, and eliminated the attached AMOS-6 satellite.
It came out of nowhere, and it was really violent.
Blue Origin New Glenn Test Outcome
Nearly a decade later, on May 28, Blue Origin performed a static fire test of its New Glenn rocket at a Florida site several miles from the earlier SpaceX location. The test sequence advanced to engine ignition before the vehicle also experienced a destructive explosion. The incident occurred after the company had progressed further into its test timeline than some prior attempts.
Public details remain limited, yet the event has prompted questions about the time required to repair or rebuild affected ground infrastructure. Observers have drawn comparisons to previous industry experiences with similar hardware losses and facility recovery.
Implications for Future Testing
Both episodes illustrate that static fire operations, while intended to verify systems before flight, carry inherent risks of rapid and total vehicle loss. The 2016 SpaceX case resulted in extended downtime for launch facilities and payload replacement. Blue Origin now faces parallel decisions regarding pad restoration and schedule adjustments. Industry participants continue to refine test protocols and hardware margins in response to such outcomes.
