Vulcan Rocket Failure: ULA Loses 40 Amazon Leo Satellites 10 Minutes Into Flight

ULA's Vulcan rocket failed about 10 minutes after liftoff on 15 November 2026, losing all 40 Amazon Leo satellites on board. It is ULA's first outright failure since 2006. Here is what happened, what is still unknown and what it means for Amazon and the US Space Force.

By SpaceTracker.live TeamPublished 8 min read
Large white rocket with six side boosters climbing into a clear blue sky above a Florida launch pad, trailing bright exhaust flames and smoke
Artist's impression: AI illustration made with Google Gemini, edited by SpaceTracker.live Team. Not an actual photo.

The Vulcan rocket failure on Sunday, 15 November 2026, cost Amazon 40 broadband satellites and handed United Launch Alliance the worst day in its 20-year history. Vulcan lifted off from Space Launch Complex 41 at Cape Canaveral at 12:40 p.m. EST (17:40 UTC, 11:10 p.m. IST) on a mission called Vulcan Leo 1, or LV-01. The climb looked clean on the live stream. About 10 minutes into the flight, something went wrong, and the satellites never reached orbit.

ULA confirmed the loss roughly 50 minutes after liftoff. It is the first time a ULA rocket has failed outright since the company was formed in 2006 as a joint venture of Boeing and Lockheed Martin. We previewed this launch last week in our Vulcan return-to-flight story, and it was meant to be a comeback. Instead it has become a serious setback for two companies at once.

What happened during the Vulcan rocket failure

The countdown itself was bumpy. A Friday attempt was scrubbed after a gaseous nitrogen supply at the Cape failed, and Saturday's try was called off over communication problems between the rocket and ground systems. On Sunday, controllers held at T-20 seconds for a technical issue, cleared it and launched near the end of the window.

The first part of the flight looked normal. The six solid rocket boosters, which had nozzle problems on two earlier Vulcan flights, worked this time: they burned out and dropped away at about 1 minute 40 seconds. According to ULA, staging, ignition of the Centaur V upper stage and the release of the payload fairing were all confirmed. The Centaur was due to fire for 12 minutes and 15 seconds to push the 40 satellites into low Earth orbit. Around the 10-minute mark, during that burn, the mission was lost.

The ULA launch webcast did not mention a problem, and the broadcast ended without saying whether the upper stage had finished its burn. Then came the statement. In it, ULA said the vehicle "failed to deliver the Amazon mission to orbit" and admitted it had no specific data yet on the cause. The company promised a full investigation with its customer and said Amazon would have visibility into the process. You can follow every launch and its result as it comes in on our rocket launches today page.

What we know and what we don't

It is important to separate facts from guesses this early. Here is the honest picture on the morning after.

  • Known: the boosters, staging and fairing release worked; the failure came about 10 minutes into the flight; all 40 satellites were lost.
  • Observed but unexplained: Spaceflight Now noted that the first stage's BE-4 engines seemed to fire a little longer than the published timeline, and that the Centaur made unusual attitude corrections early in its burn. Neither has been linked to the failure.
  • Unknown: the root cause, and whether the brief countdown hold played any part.

Two pieces of hardware will get extra attention. This was the first flight of the shorter, low-orbit version of the Centaur V upper stage, built for heavy constellation missions like this one. It was also the first Vulcan with six boosters, the most powerful VC6L configuration. In addition, the BE-4 engines from Blue Origin had been modified after a New Glenn rocket using the same engine exploded on its pad in May. Blue Origin is reportedly helping with the investigation. None of this proves anything yet, and good failure reviews usually take weeks or months.

Vulcan Leo 1 flight timeline and Vulcan launch recordTimeline of the 15 November 2026 Vulcan Leo 1 flight: liftoff at 17:40 UTC, solid boosters separate at about 1 minute 40 seconds, the Centaur V upper stage ignites after staging, an anomaly occurs about 10 minutes into flight during a planned 12 minute 15 second Centaur burn, and ULA confirms the failure about 50 minutes after liftoff. Below, Vulcan record: five flights, four successes (two with booster nozzle problems) and one failure.Vulcan Leo 1: what happened on 15 November 2026Liftoff 12:40 p.m. EST (17:40 UTC, 11:10 p.m. IST) from SLC-41, Cape Canaveral, with 40 Amazon Leo satellitesPlanned Centaur V burn: 12 min 15 sLiftoffT+0Boosters drop awayabout T+1 min 40 sStaging, Centaur ignitesfairing jettison confirmedAnomalyabout T+10 minFailure confirmedabout T+50 minULA has not yet said what failedVulcan Centaur launch record1Jan 2024Cert-1Success2Oct 2024Cert-2Success, booster nozzle lost3Aug 2025USSF-106Success4Feb 2026USSF-87Success, booster nozzle lost5Nov 2026Amazon Leo LV-01Failure, payload lostSources: ULA statements, Spaceflight Now. Illustration: SpaceTracker.live

A hard blow for Amazon Leo

For Amazon, the timing could hardly be worse. Amazon Leo, the broadband network formerly known as Project Kuiper, is trying to catch up with SpaceX's Starlink. Before Sunday, about 400 Leo satellites had reached orbit on 15 launches using Atlas V, Falcon 9 and Ariane 6. LV-01 would have pushed the total to around 436. The full network needs more than 3,200 satellites, so every lost batch matters.

LV-01 was also the first of 38 Vulcan launches Amazon has bought, the biggest single block in its launch plan. Amazon says Vulcan is meant to carry more than 1,500 first-generation satellites, which you can read in Amazon's announcement of the mission. A second Vulcan flight, LV-02, was being prepared to fly within weeks. That now depends on the investigation.

Amazon's public reaction was calm. In a post on X, it said launches carry risk, "especially true for inaugural missions," and called ULA a trusted partner. That is the right tone for a long contract, but the practical problem is real. Amazon's other heavy rocket, Blue Origin's New Glenn, is still waiting to fly again after the May explosion. That leaves Europe's Ariane 6, with the next mission (LE-04) targeting no earlier than 23 November, and a smaller set of SpaceX Falcon 9 flights. You can follow the satellites already in orbit on our Amazon Leo satellite tracker.

Why this matters for ULA and the US military

ULA built its reputation on reliability. Its Atlas V and Delta rockets put together a near-spotless record over almost two decades, and the company won national security contracts on that record. Vulcan replaces Atlas V, so its health matters far beyond Amazon.

Vulcan had already been grounded once. Booster nozzles burned through and fell off on the second flight in October 2024 and the fourth in February 2026. Both times the rocket still reached the right orbit, but the US Space Force paused national security launches on Vulcan until ULA fixed the problem. ULA spent nine months on that work, and this flight was supposed to close the chapter. Now Vulcan faces a fresh grounding with no return date, and the Space Force schedule will slip again.

There was an offer of help, too. NASA Administrator Jared Isaacman said on X that the agency was ready to assist with the investigation. That matters because Vulcan is also due to launch NASA work, including the Dream Chaser cargo spaceplane in the coming years. Information on the rocket's design is on ULA's Vulcan Centaur page.

A week of extremes in spaceflight

It is striking how different the past few days have been. On 13 November, SpaceX caught a Starship upper stage for the first time, covered in our Starship Flight 15 report. A day later, Rocket Lab flew Electron for the 100th time, which we wrote about in Rocket Lab's 100th launch. Then, on Sunday, one of the world's most trusted launch companies lost a rocket.

That contrast is a reminder that rockets stay hard even for experienced teams. New hardware, a new configuration and a new customer all came together on one flight. Most rockets that fail early go on to fly well once the cause is found. The question for ULA is how quickly it can show that, and for Amazon, how much ground it loses to Starlink in the meantime.

What happens next

ULA will now lead a formal investigation, with Amazon involved and other agencies likely to take part. Expect updates on which stage failed first, then a list of corrective actions, before any new launch date. Until then, all Vulcan missions are effectively on hold.

We will update our coverage when ULA shares findings. For the next flights from every company, check our rocket launch schedule or the next rocket launch countdown.

Key takeaways

  • Vulcan launched at 12:40 p.m. EST on 15 November 2026 and failed about 10 minutes into flight, losing 40 Amazon Leo satellites.
  • It is the first outright failure of a ULA rocket since 2006 and Vulcan's first loss in five flights.
  • Boosters, staging and fairing release worked; the cause is still unknown.
  • The flight debuted a shorter Centaur V and the six-booster VC6L version, both now under scrutiny.
  • Amazon's 38-launch Vulcan plan and the Space Force schedule are on hold until ULA finds the cause.

Source: United Launch Alliance statements, with additional reporting from Amazon and Spaceflight Now. Analysis by the SpaceTracker.live Team.

Source: United Launch Alliance (ULA)

#Vulcan#ULA#Amazon Leo#Launch Failure#Centaur V#Blue Origin#BE-4#Space Force#Starlink#Cape Canaveral
Share:WhatsAppXFacebook