Vendors & EquipmentUnited Launch AllianceVulcanBe 4Blue Origin

Vulcan Failure Traced to Fuel Feed, Not BE-4 Engines

ULA has cleared Blue Origin's BE-4 engines in the Nov. 15 Vulcan failure that lost 40 Amazon Leo satellites, focusing the probe on fuel supply in the liquid core stage.

3 min read

ULA Clears Blue Origin BE-4 Engines, Focuses Vulcan Failure Probe on Core Stage Fuel SupplyVendors & Equipment
ULA Clears Blue Origin BE-4 Engines, Focuses Vulcan Failure Probe on Core Stage Fuel SupplyGregoryButler / pixabay

Why it matters

  • ULA cleared the BE-4 engines on Nov. 18 as the cause of the Nov. 15 Vulcan launch failure.
  • The failure destroyed 40 Amazon Leo broadband satellites, a major deployment batch.
  • Investigators now focus on inadequate fuel delivery within Vulcan's liquid core stage.
  • Blue Origin targets an early-January return to flight for New Glenn, which uses the same BE-4 engine family.
  • All six solid strap-on boosters and the Centaur upper stage performed nominally during the flight.

The story

United Launch Alliance (ULA) has cleared Blue Origin's BE-4 engines of blame for the Nov. 15 Vulcan launch failure that destroyed 40 Amazon Leo broadband satellites, narrowing the investigation to inadequate fuel delivery inside the rocket's liquid core stage.

The company announced the preliminary finding on Wednesday, Nov. 18, in a technical update based on initial telemetry from the failed ascent. The verdict matters far beyond one mission. Blue Origin uses the same BE-4 engine family on the first stage of its New Glenn heavy-lift vehicle, so an engine design flaw or manufacturing defect would have grounded two U.S. launch providers simultaneously and forced extensive parallel hardware inspections across the heavy-lift sector.

What does the clearance change for Blue Origin?

It removes immediate return-to-flight pressure. Blue Origin can now press ahead with its targeted early-January New Glenn launch without carrying the shadow of Vulcan's anomaly. Had the engines been implicated, the stand-down would have hit both fleets at once, compounding U.S. launch capacity constraints at a time when satellite constellation operators depend on tight deployment schedules.

The BE-4 burns liquefied natural gas. Preliminary flight data shows the propulsion units themselves performed within specification, according to ULA's Nov. 18 update.

What exactly failed on the Nov. 15 flight?

Telemetry points to a propellant supply problem, not an engine problem. ULA engineers have traced the orbital insertion shortfall to insufficient fuel reaching the first-stage engines from within the Vulcan liquid core stage. The company has not yet disclosed whether a mechanical fault, a pressurization issue, or a feedline anomaly restricted the flow.

The rest of the vehicle performed nominally:

  • All six solid rocket strap-on boosters ignited cleanly and burned through their full profiles.
  • The Centaur upper stage operated as expected after main booster separation.
  • The BE-4 main engines ran normally until starved of propellant.

That fault isolation narrows the corrective engineering scope. ULA now needs to fix propellant delivery within the booster's tankage or feedlines before Vulcan resumes commercial and national security launch operations — a materially smaller task than a redesign touching shared engine hardware.

How hard does the loss hit Amazon Leo?

The 40 satellites aboard represented a major deployment batch for the LEO broadband constellation. The failure delays near-term orbital replenishment while ULA runs its formal investigation and implements hardware or procedural fixes.

For Amazon, the setback translates into lost deployment cadence rather than a program-ending event, but each grounded launch batch pushes back the constellation's service buildout. Amazon's Leo competes in a market where orbital slotting and coverage milestones are time-sensitive, and a standdown measured in months would compress later deployment schedules.

What comes next?

The investigation team, led by ULA President and CEO Mark Peller, is continuing detailed telemetry analysis, hardware inspections, and ground testing to pinpoint the mechanism that restricted fuel flow to the BE-4 engines.

Two gates govern the return to flight. ULA must first determine why the liquid core stage suffered the propellant supply disruption, then verify corrective measures with federal regulators and launch customers. Those steps will dictate when Vulcan flies again, while Blue Origin's New Glenn aims for its early-January window with its engines now formally cleared.

Also reported

Source: satnews.com

Share this article:

« PreviousNext »

More from Daniel Okafor

Daniel Okafor

Show full bio

Senior reporter covering regulation, policy and their impact on Carrier business, 5G and 6G, fiber and broadband at Telecom Gazette.

591 articles