ULA Vulcan Rocket Fails, 40 Amazon Leo Satellites Lost After Launch

United Launch Alliance’s Vulcan rocket failed to reach orbit on Sunday, November 15, 2026, and the 40 Amazon Leo internet satellites on board were lost. The rocket lifted off from Florida at 12:40 pm Eastern time (11:10 pm IST) and ran into trouble roughly 10 minutes into the flight. It is the first outright launch failure for ULA since the company was set up in 2006, and it is a serious blow to Amazon’s plan to build a rival to SpaceX’s Starlink.
How the Vulcan Launch Went Wrong
The 214-foot Vulcan took off from Space Launch Complex 41 at Cape Canaveral Space Force Station. It carried six strap-on solid boosters from Northrop Grumman, two methane-burning BE-4 engines on the first stage and a hydrogen-fuelled Centaur upper stage on top.
According to Spaceflight Now, the solid boosters burned out and dropped away normally at about 1 minute 40 seconds. That mattered, because booster nozzle problems had marred two earlier Vulcan flights. However, the first stage appears to have fired for longer than planned and separated from the Centaur later than expected. The Centaur was due to burn for about 12 minutes 15 seconds, and ULA said the problem happened during that phase.
The live webcast did not mention any issue and ended without confirming whether the Centaur had finished its burn. About 50 minutes after liftoff, ULA put out a statement saying the vehicle “failed to deliver the Amazon mission to orbit.”
A delayed countdown
The launch had already slipped twice. A Friday attempt was scrubbed after a gaseous nitrogen plant used by several launch providers went down, and a Saturday attempt was called off because of network problems between the rocket and ground systems. On Sunday, controllers held the count at T-minus 20 seconds for an unexplained technical issue before launching near the end of the window. Spaceflight Now said it is not yet known whether that hold had anything to do with the failure.
Key Facts About the Failed Mission
| Detail | Information |
|---|---|
| Launch date | November 15, 2026, 12:40 pm EST |
| Launch site | SLC-41, Cape Canaveral, Florida |
| Rocket | ULA Vulcan, fifth flight, first in nine months |
| Payload | 40 Amazon Leo satellites |
| Point of failure | Centaur upper stage burn, about 10 minutes in |
| Significance | First outright failure for ULA since 2006 |
What ULA and NASA Said
ULA said it would work closely with its customer and other organisations to find the cause and return to flight as soon as possible. The company said it does not yet have specific data on what happened but is committed to full transparency with customers during the investigation. Details are expected on ULA’s official website.
NASA Administrator Jared Isaacman offered the agency’s help, telling ULA that NASA is “in your corner.”
Before the flight, ULA chief executive Mark Peller had said the company had found and fixed three credible causes of the earlier nozzle problem. Blue Origin had also developed a valve fix for the BE-4 engines and fitted it to this rocket. The same engine type was linked to the May on-pad explosion of Blue Origin’s New Glenn rocket.
Why This Hurts Amazon Leo
Amazon Leo is Amazon’s planned satellite network for broadband internet, meant to compete with SpaceX’s Starlink. Engadget reported that Amazon has about 390 satellites in service. Amazon’s plan calls for 3,232 satellites in orbit by July 2029, and Spaceflight Now said more than 3,300 are needed to complete the network.
Amazon was already behind schedule. Engadget noted that the US Federal Communications Commission had required 1,600 satellites in orbit by July 31, 2026, a target Amazon missed. In July, Amazon blamed delays across all three of its heavy-lift launch partners.
The launch problem now affects both of its big American rockets at once:
- Vulcan: Amazon bought 38 Vulcan flights, and this was the first. Further launches must wait for the investigation.
- New Glenn: Amazon has 24 New Glenn launches booked, but the rocket has been grounded since the May explosion.
- Atlas V: ULA has already flown eight Leo missions on its older Atlas V rocket.
- Others: Amazon also holds 24 launches on Europe’s Ariane 6 and 13 on SpaceX’s Falcon 9.
Had Sunday’s flight worked, the total number of Leo satellites launched would have reached 436, according to Spaceflight Now.
Effect on US Military and Other Missions
The US Space Force had already paused national security launches on Vulcan pending more analysis of the earlier booster issues, while allowing commercial flights to continue. Those military missions remain on hold, and Spaceflight Now described the failure as a potentially significant grounding for the rocket. No return-to-flight date has been given.
Why It Matters for India
There is no direct impact on Indian users today, but global launch capacity decides how quickly satellite internet networks can grow and reach more countries. Readers following space can compare this setback with recent tests at home, such as ISRO’s upgraded PSLV third stage, and with SpaceX’s progress after Starship was caught by its tower. The Vulcan loss shows how a single failure can delay a huge satellite project and shift the balance in the race for space-based broadband.
What Comes Next for Vulcan
ULA’s investigation will look at the longer first-stage burn, the separation timing and the Centaur’s behaviour early in its burn. Until the cause is found and fixed, Vulcan will stay on the ground, and Amazon will have fewer ways to get its satellites into orbit in the months ahead.



