ULA says Vulcan first stage underperformed just after liftoff
ULA's first detailed account cites low booster performance, not an upper-stage fault, but does not say whether Blue Origin's BE-4 engines caused the shortfall.
- What happened
- ULA said on 17 November that early data shows Vulcan's first stage underperformed soon after liftoff and separated too low and too slow to reach orbit.
- What’s new
- The trouble now appears to have begun just after liftoff, not about 10 minutes in during the Centaur burn as first thought.
- Why it matters
- If the BE-4 engines are implicated, Blue Origin's New Glenn could also be delayed, compounding launch shortages for Amazon and the US Space Force.
United Launch Alliance said on 17 November that early data indicates the first stage of its Vulcan rocket underperformed shortly after liftoff on 15 November, according to GeekWire. The flight was carrying 40 Amazon Leo internet satellites and failed to put them in orbit. ULA's first detailed explanation pointed to what it called low booster performance, its name for Vulcan's core stage. Because of the shortfall, that stage separated while the rocket was too low and too slow to reach orbit.
A revised picture of the failure
ULA's account shifts the timeline. On 15 November the failure appeared to happen about 10 minutes into flight, during the burn of the Centaur upper stage. ULA now says it lost telemetry around that point, but the problem started just after liftoff. According to ULA, the Centaur's two L3Harris RL10 engines worked as planned but could not make up the deficit. The six Northrop Grumman solid rocket boosters, which were behind trouble on two previous Vulcan missions, seem to have worked as expected.
The core stage is powered by two BE-4 engines from Blue Origin. ULA has not identified the cause of the underperformance or said whether the engines were involved, and says it wants to avoid speculation while the investigation is at a very early stage. Ars Technica reported that the preliminary data suggests the BE-4 engines may not be to blame, while stressing that no firm conclusions can be drawn. The FAA will supervise the investigation ULA is leading and must sign off on its final report and any fixes.
Blue Origin chief executive Dave Limp wrote on X that it is ULA's mission to provide updates and that Blue Origin is supporting ULA with BE-4 data and analysis.
Who is affected
Ars Technica expects the failure to keep Vulcan grounded for at least half a year, likely more. It names the US Space Force, whose national security missions are queued up for Vulcan, and Amazon as the customers most affected. According to GeekWire, Amazon has purchased 38 Vulcan launches for Leo, and this was the first. Vulcan is slated to carry more than 1,500 first-generation satellites, the largest share of any launcher in the Leo program.
The question of the engines matters beyond Vulcan. Amazon has also booked 24 New Glenn launches, and that rocket's first stage carries seven BE-4s. New Glenn has not flown since May, when a faulty oxygen valve led to a BE-4 exploding during a ground test. ULA CEO Mark Peller said before the flight that the engines on this Vulcan had been retrofitted with Blue Origin's fix for that valve, according to GeekWire. Ars Technica says Blue Origin hopes to fly New Glenn again in January at the earliest, and that a BE-4 cause would certainly delay that. Ars adds that such a delay would also set back NASA, which relies on New Glenn for its Artemis program.
Amazon's next Leo launch, an Ariane 6 mission with 36 satellites, remains targeted for no earlier than 23 November from French Guiana, GeekWire reports.