Skip to content
Theme
OnDevice Tools

SoftwareCloud & Services

Vulcan rocket failure may not stem from Blue Origin BE-4 engines

Early data suggests the problem that doomed ULA's return-to-flight Vulcan launch lay with the rocket itself, not its BE-4 engines, though the investigation is at a very early stage.

Illustration of the Vulcan rocket lifting off with its solid rocket boosters trailing flame against a clear sky

Key takeaways

  • ULA's return-to-flight Vulcan mission failed about 10 minutes into flight after the booster underperformed, leaving the vehicle too low and slow for stage separation to reach orbit.
  • Preliminary information from sources suggests the fault lay with the launch vehicle, possibly in systems feeding propellant to the engines, rather than in the BE-4 engines themselves.
  • The investigation is led by ULA under FAA oversight, and details are being closely held; both sources describe it as very complicated and early.
  • The setback is expected to sideline Vulcan for at least six months, affecting US Space Force missions and Amazon's Leo constellation launches, and could delay Blue Origin's New Glenn return to flight if the engines are implicated.
In this article
  1. A second failed flight in a row
  2. What the early data shows
  3. Why the BE-4 engines matter
  4. Who is affected
  5. A worsening launch picture

A second failed flight in a row

Illustration: plane, rocket, Amazon logo, search and the labels Amazon Leo, Blue Origin, New Glenn

United Launch Alliance confirmed on Tuesday morning that its Vulcan rocket ran into trouble during its return-to-flight mission, according to Ars Technica. The company said telemetry and the mission were lost about 10 minutes after liftoff.

ULA stated that just after leaving the pad, the booster produced less power than expected. As a result, the upper stage separated while the vehicle was still too low and too slow to make it to orbit.

What the early data shows

The investigation is led by ULA and overseen by the Federal Aviation Administration. According to Ars Technica, information about the failure is being tightly guarded by both ULA and Blue Origin, who have only confirmed they are working together on the cause. Two sources described the investigation as extremely complicated and still at an early stage.

Preliminary data from two sources points to a problem on the launch vehicle rather than in the engines themselves. Engineers are examining the systems that feed methane and liquid oxygen to the engines.

One possibility under review is that one of the two BE-4 engines delivered reduced thrust shortly after liftoff and never returned to full power during the burn. Tracking camera footage appeared to show one engine slightly dimmer than the other once the solid rocket boosters separated, roughly two minutes into flight. An uneven shutdown of the engines may also explain the sudden change in attitude seen in ULA's real-time animation near stage separation.

ULA did confirm that the Centaur V upper stage and the strap-on solid boosters worked as intended during the flight. The company gave no specifics about the weak booster performance.

Why the BE-4 engines matter

The focus on the engines is not arbitrary.

New Glenn suffered a catastrophic failure during a ground test in May, later traced to a main oxygen valve on one of its BE-4 engines. Last Tuesday, Blue Origin said a modified valve had passed qualification testing and was already fitted to engines for upcoming flights, with rollout across the rest of the fleet under way. The company expects to close its own investigation later this month.

If Vulcan's failure were eventually traced to the BE-4 engine, it would likely delay New Glenn's planned return to flight, which could come as early as January. That would be a blow not only for Blue Origin but also for NASA, which relies on New Glenn for much of the heavy lifting in its Artemis lunar programme.

Who is affected

This was the fifth Vulcan flight since the rocket debuted in January 2024. Two earlier flights had problems with the nozzles on the solid rocket boosters, but the vehicle compensated and still reached its intended orbit. The second nozzle issue forced a nine-month stand-down.

According to Ars Technica, the latest setback is likely to keep Vulcan grounded for at least six months, and probably longer. The US Space Force is likely to feel the impact most, as it has national security payloads awaiting rides on Vulcan. Amazon is also affected, with more than a dozen launches of its Amazon Leo satellite constellation planned for 2027.

A worsening launch picture

The failure adds pressure to what Ars Technica describes as a deteriorating launch situation in the United States. Fewer available rockets means payloads queue longer for their rides to space.

For now, firm conclusions are premature. The data is preliminary, and no definitive cause has been established. Readers should follow the FAA and ULA for official findings as the investigation progresses.

Sources

  1. The data is very preliminary, but Vulcan failure may not be due to BE-4 enginesArs Technica

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.