ULA's CEO blames Vulcan booster shortfall for loss of 40 Amazon Leo satellites
Early ULA analysis points to the first stage, not the solid boosters, leaving Centaur V too low and too slow to reach orbit.

United Launch Alliance has given its first public explanation for the loss of a Vulcan Centaur carrying 40 Amazon Leo satellites on 15 November: a first-stage performance problem, not the solid rocket boosters.
ULA president and CEO Mark Peller said at a Washington Times event in Arlington, Virginia, that early analysis points to “a significant shortfall in booster first stage performance,” according to Aerospace America. The shortfall left the Centaur V upper stage separating with too little altitude and velocity, and the upper stage could not make up the difference. Nothing reached orbit, so none of the 40 satellites were deployed.
What the data shows
Per the report, the vehicle lifted off from Cape Canaveral at 12:40 p.m. Eastern and the performance problem began shortly after liftoff. The booster completed its boost phase, Centaur separated and its fairing came off, and the RL10 engines ignited after separation. In other words, the sequence ran as designed; the stack simply did not have the energy it needed.
The solid rocket boosters appear to have been cleared. Vulcan’s previous flight, in February, suffered a nozzle problem on one of its solids. ULA made several design changes to the nozzles afterward, and Peller said initial data suggests those changes worked, with all six solid boosters performing cleanly this time.
That narrows the suspects to the core stage, which our earlier report noted was a possibility. Aerospace America’s account does not say what component caused the shortfall, and ULA has not named one. The first stage is powered by two Blue Origin BE-4 engines, but nothing in the source ties the failure to them, so that remains an open question rather than a finding.
What happens next
The FAA says ULA will lead the mishap investigation, with the agency overseeing it and approving the final report, including any corrective actions. Peller said ULA is committed to finishing as quickly as possible. No return-to-flight date has been given.
The stakes extend beyond Amazon. As we covered in our look at the Pentagon fallout, this is Vulcan’s second problem flight in nine months, and the Space Force has already moved six national-security launches to SpaceX. A cause that sits in a new place, the core stage rather than the solids fixed after February, may complicate any argument that the rocket’s problems are behind it.
// Signal sources
Machine-written by AI from the sources above