Vulcan Fails 10 Minutes Into Flight, Losing 40 Amazon Leo Satellites
Hardware / news
Vulcan Fails 10 Minutes Into Flight, Losing 40 Amazon Leo Satellites
ULA has not named the failed stage, and the rocket had two earlier booster nozzle problems, in 2024 and February 2026.

United Launch Alliance's Vulcan rocket failed to deliver 40 Amazon Leo satellites to orbit on Sunday, November 15, about 10 minutes after it left Space Launch Complex 41 at Cape Canaveral, ULA said. The cause is not known, and the company has not given a date for the next Vulcan flight.
The vehicle lifted off at 1740 GMT, according to Anadolu Agency's report, and cleared the tower before the fault. ULA said on X that Vulcan "suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit," per WESH's account of the statement. The statement names no spokesperson and points to the Launch Director as the source of the data.
What ULA has and has not said
ULA said it has no specific data yet on what happened. "Today, we did not meet that standard," the company said, referring to its own measure of mission success, according to Anadolu. It said it will work with Amazon and the relevant authorities on root cause, corrective action and a return to flight.
Amazon Leo said on X: "There is risk with any launch, and that's especially true for inaugural missions like LV-01." It added that ULA "has been a trusted partner for Amazon."
The mission was the fifth Vulcan flight and the first in nine months, according to Spaceflight Now's mission page. That page lists the vehicle as flying six Northrop Grumman strap-on solid boosters, identified in a May 2026 headline as the GEM 63XL, with 3.8 million pounds of thrust at liftoff from the boosters and two BE-4 engines combined.
The booster history is the open question
Spaceflight Now says nozzle problems with the strap-on boosters "marred two earlier flights," one in 2024 and one in February 2026. Neither ULA nor Amazon has said whether Sunday's failure involves a booster, the BE-4 first stage or the Centaur upper stage. No outlet fetched for this report names a stage.
The fix differs by stage. A booster fault points back at the strap-on supplier; a first-stage or upper-stage fault opens a new investigation.
WESH also reports two scrubs before the attempt, a "Power Interruption" on Friday and a "Communications error" on Saturday, plus a countdown reset on Sunday for an "anomaly" in the launch sequence. It is unclear whether any of those is connected to the in-flight failure.

The arithmetic of the loss
The Space Force photo above shows the Atlas V that flew the Leo 7 mission from the same pad on May 29, 2026. Its caption puts the Leo satellites launched to that date at 331, and says the Atlas V would deploy 29 operational satellites on that flight. Vulcan was carrying 40, which is 38% more per launch (my calculation from the two figures).
The number that matters here is not the 40 satellites but the denominator. Forty is roughly 12% of the 331 already in orbit as of the May 29 caption, lost in one flight.
- Atlas V, Leo 7 flight29 satellites
- Vulcan LV-01 (lost)40 satellites
- Launched by May 29, 2026331 satellites
Source: U.S. Space Force photo captions via Wikimedia Commons (Leo 7, May 29, 2026); Anadolu Agency, Nov. 15, 2026
| Item | Figure | Source |
|---|---|---|
| Liftoff | 1740 GMT, Nov. 15 | Anadolu Agency |
| Failure point | About 10 minutes into flight | ULA via WESH |
| Satellites aboard | 40 | Anadolu, Spaceflight Now |
| Vulcan flights to date | 5, first in 9 months | Spaceflight Now |
What would change this read
If ULA's data shows a fault in the Centaur or the first stage rather than a booster nozzle, the February 2026 fix was not the problem and the grounding timeline resets. If it is a nozzle again, the question moves to the booster supplier. ULA has not said when it will share more, and Amazon has not said how the loss changes its launch plan.
Related reading on this site: SpaceX's Flight 15 ship catch, and the hardware-testing startup Nominal's $240 million round.
Sources
More in Hardware
- 01Starship's Ship 42 Is Caught After 14 Orbits, and Two Reports Give Different Reasons the Booster Was NotFlight 15 returned an upper stage to the tower for the first time and dropped 26 Starlink V3 satellites; SpaceX has no reflight date in these accounts.
- 02Genesis AI Raises $500 Million at $3.5 Billion, and Its CEO Says Eno's Hands Last WeeksThe Paris robot maker has built 30 to 40 Eno units and chose a US contract manufacturer, with no price and no paying customer count.
- 03Tesla Cybercab's Eight NHTSA Crashes Include a 53 mph Highway Hit With a Test Driver AboardThe four driverless crashes stayed under 5 mph; the Robotaxi median pre-crash speed is 1 mph, which says more about the geofence than the software.
- 04Anthropic's Three-Day AMD Port Covered Prefill for One Model on MI355XThe roadshow slide credits Claude Mythos Preview with a six-to-12-month job; it leaves out decode, the kernel denominator and any Nvidia comparison.