Vulcan launch fails to put 40 Amazon Leo satellites in orbit
ULA says an anomaly about ten minutes into the November 15 flight prevented the Amazon Leo payload from reaching orbit. The company has begun investigating the cause.

United Launch Alliance failed to deliver 40 Amazon Leo satellites to orbit on November 15 after its Vulcan rocket suffered an anomaly roughly ten minutes into flight, the company said. ULA had not identified the cause in its initial statement.
The rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida at 12:40 p.m. Eastern Standard Time, or 17:40 UTC. That was 12:40 a.m. on November 16 in Bangkok; the launch date in Florida was November 15.
In a statement posted at 18:30 UTC, ULA said data received by its launch director confirmed the anomaly and the failure to deliver the Amazon mission to orbit. The company said it would work with its customer and the appropriate organisations to determine what happened, identify corrective action and return to flight.
ULA’s initial announcement did not identify a failed component. The timing alone does not establish a cause, and the company had not set a date for another flight in that statement.
A setback on the first Vulcan mission for Amazon Leo
ULA’s mission overview lists a payload of 40 broadband satellites and identifies the flight as the first of 38 Vulcan launches purchased for Amazon’s constellation. Eight earlier deployment missions used ULA’s Atlas V rocket.
This Vulcan configuration paired six solid rocket boosters with a Centaur V upper stage optimised for low Earth orbit. Amazon Leo is intended to provide internet access in locations beyond the reach of existing networks; the loss prevents this batch of spacecraft from joining the constellation.
Contemporaneous launch reporting identified the mission as Vulcan’s fifth flight. Earlier flights had experienced booster anomalies while still delivering their payloads. Those incidents do not establish the cause of the November 15 loss, which remains subject to investigation.
Sources
- Statement confirming the mission anomaly,15November2026 — United Launch Alliance
- Vulcan Leo1 mission overview — United Launch Alliance
- Assigned writer
- Olivia BrownCredit pending confirmation
- Assigned reviewer
- Harry WilsonReview pending