On November 15, 2026, a Vulcan Centaur failed to put 40 Amazon Leo satellites into orbit. In a preliminary account reported November 17, United Launch Alliance (ULA) said low booster performance began just after liftoff; the vehicle separated its stages too low and too slowly to reach orbit, and telemetry and the mission were lost about 10 minutes into the flight.
Our earlier report on the failed Vulcan mission carrying Amazon Leo satellites covered the payload loss. This follow-up focuses on the flight sequence and the early technical possibilities.
The timeline matters: ULA placed the start of low performance just after liftoff, while telemetry and the mission were lost about 10 minutes into the flight.
What happened during the flight?
ULA’s preliminary account linked the failed mission to low booster performance early in the flight. Stage separation came before Vulcan had enough altitude and velocity to reach orbit, leaving the 40 satellites undelivered.
ULA said the solid rocket boosters performed nominally after nozzle improvements, and described the Centaur V upper stage as nominal as well. Centaur V could not recover from the earlier performance loss.
What possible causes did early reporting describe?
Ars Technica reported that two sources preliminarily pointed to the launch vehicle rather than an engine-internal problem, with methane or liquid-oxygen propellant-feed systems among the possible areas of concern. The same report said ULA engineers were considering whether one BE-4 engine had produced reduced thrust. Vulcan’s first stage uses two BE-4 engines.
These possibilities are distinct from ULA’s account of the solid rocket boosters and Centaur V performing nominally; neither identifies a specific failed component.
Who is leading the investigation?
Ars Technica reported on November 17 that ULA was leading the investigation under Federal Aviation Administration oversight. Space.com reported that Amazon had 38 Vulcan launches booked for Amazon Leo and that the failed flight was the first.