New Glenn static-fire explosion traced to BE-4 engine valve, implications for ULA Vulcan

During a static‑fire test on May 28, Blue Origin’s New Glenn rocket suffered a catastrophic explosion that destroyed the vehicle and heavily damaged Launch Complex 36. The company’s investigation, disclosed on August 5, points to a malfunctioning liquid‑oxygen valve in one of the seven BE‑4 engines as the origin of the anomaly. This finding not only shapes the path to rebuilding New Glenn but also raises questions for United Launch Alliance, which relies on the same BE‑4 engine for its Vulcan Centaur. Understanding the valve issue is critical for both companies’ upcoming launch schedules.

What happened

Blue Origin confirmed that the May 28 static‑fire test ended in an explosion when a liquid‑oxygen valve in a BE‑4 engine failed to open correctly, causing an over‑pressure event that destroyed the first stage. Hardware recovered from the pad showed damage localized to the valve assembly, and subsequent hot‑fire tests on spare engines reproduced the failure mode, confirming the root cause.

The company announced that it will manufacture a modified valve design and retrofit it onto existing BE‑4 engines by the end of the month. While the focus remains on rebuilding Launch Complex 36, Blue Origin noted that the issue could extend to United Launch Alliance, whose Vulcan Centaur also uses the BE‑4, though ULA has not yet detailed any schedule impact.

Why it matters

The valve failure highlights a single‑point vulnerability in the BE‑4 propulsion system, affecting both Blue Origin’s New Glenn and ULA’s Vulcan programs. Delays in implementing the fix could push back New Glenn’s first orbital flight and potentially stall Vulcan’s return to service, impacting satellite operators and national security payloads that depend on these launchers. Additionally, the incident underscores the importance of rigorous component testing for high‑pressure cryogenic systems, a lesson that reverberates across the commercial launch industry.

How to think about it

Stakeholders should treat the valve issue as a risk that can be mitigated through a structured retrofit program. First, verify the new valve design on ground‑test stands before installing it on flight hardware. Second, update launch manifest timelines to reflect the retrofit window, communicating clearly with customers about revised dates. Finally, incorporate enhanced valve health‑monitoring sensors into future BE‑4 production runs to catch anomalies early.

FAQ