Industry

What happened to Vulcan LV-01, the Amazon Leo launch that failed?

United Launch Alliance's (ULA) Vulcan rocket lifted off from Cape Canaveral, Florida, at 12:40:30 p.m. Eastern Standard Time (EST) on 15 November 2026 (17:40:30 UTC) with 40 Amazon Leo internet satellites, but it never reached orbit and the satellites were lost. ULA lost telemetry, the flight's data link, about 10 minutes in. ULA says early data shows the trouble started just after liftoff, with low performance from the first stage. The exact cause is not yet known, and the FAA is overseeing an investigation.

Get launch alerts in your inbox

· Published · Updated · 6 min read

A white Vulcan rocket with Amazon and ULA logos and six side boosters stands on the launch pad between tall lattice towers under a blue sky
Vulcan with the 40 Amazon Leo satellites on the pad at Space Launch Complex 41, Cape Canaveral, during fueling on 15 November 2026, a few hours before liftoff. Image: ULA

United Launch Alliance's (ULA) Vulcan rocket lifted off at 12:40:30 p.m. Eastern Standard Time (EST) on Sunday 15 November 2026 (17:40:30 UTC) with 40 Amazon Leo satellites, and failed to reach orbit. The satellites were lost. ULA says early data shows the first stage underperformed just after liftoff. The exact cause is not yet known.

The mission, called LV-01 (Leo Vulcan 1), was Amazon's first launch on Vulcan. For background on the network itself, read what is Amazon Leo.

Vulcan LV-01 failure: the key facts

  • Liftoff: 12:40:30 p.m. EST (17:40:30 UTC), 15 November 2026, Space Launch Complex 41, Cape Canaveral Space Force Station, Florida.
  • Rocket: Vulcan VC6L, with six solid rocket boosters and a new, shorter Centaur V upper stage built for low Earth orbit.
  • Payload: 40 Amazon Leo satellites, the biggest Leo batch yet.
  • Result: did not reach orbit. ULA lost telemetry, the flight's data link, about 10 minutes in.
  • Early finding (ULA): low performance from the booster, Vulcan's liquid-fuelled first stage, just after liftoff.
  • Investigation: led by ULA, overseen by the Federal Aviation Administration (FAA).
  • Flight number: Vulcan's fifth flight since it first flew in January 2024.

What happened during the flight?

ULA's own timeline, from its statements and posts, runs like this:

  • 13 and 14 November: two launch attempts were called off for ground problems. First a power cut at the Air Liquide plant that supplies nitrogen gas to the pad, then a network fault between ground equipment and the rocket, ULA said.
  • 15 November, 12:40:30 p.m. EST: liftoff, at the end of a launch window that opened at 12:11 p.m. EST.
  • About 2 minutes in: ULA posted that the six solid rocket boosters had burned out and dropped away, with Vulcan continuing on its two BE-4 main engines.
  • About 10 minutes in: ULA lost telemetry and the mission.
  • 1:30 p.m. EST: ULA confirmed the rocket "suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit".
  • 16 November: the FAA said it was requiring ULA to carry out a mishap investigation.
  • 17 November, 9:30 a.m. EST: ULA gave its first detailed account of what went wrong.
A Vulcan rocket lifting off on a bright flame beside a steel lattice tower, with billowing white and brown exhaust clouds at the pad
Vulcan clears the pad at Space Launch Complex 41 with the 40 LV-01 satellites, 15 November 2026. A frame from ULA's liftoff video. Image: ULA

What went wrong with Vulcan?

ULA says the problem began early, even though the mission was lost later. In its 17 November update, ULA said: "early indications are that just after liftoff the launch vehicle experienced low booster performance, resulting in stage separation occurring when the vehicle was low in altitude and below minimal velocity to reach orbit."

In plain words: the first stage did not push hard enough. When it let go of the upper stage, the rocket was too low and too slow. ULA says the Centaur V upper stage started normally and its RL10 engines worked as planned, but it "was unable to recover from the performance loss".

ULA also says the six solid rocket boosters, made by Northrop Grumman, appear to have worked normally. That matters because booster nozzle problems hit two earlier Vulcan flights, and ULA had changed the nozzle design for this launch.

ULA chief executive Mark Peller said on 17 November that the investigation is focused on the liquid-fuelled core stage, SpaceNews reports.

What is still not known?

The cause. ULA has not said why the first stage underperformed, and says it wants "to avoid speculation until the investigation is complete".

Here is what is confirmed and what is not:

  • Confirmed by ULA: low first-stage performance just after liftoff, early stage separation, a normal upper stage, normal solid boosters.
  • Confirmed by Amazon: the payload was lost.
  • Not confirmed: whether one of the two BE-4 engines, built by Blue Origin, was at fault.
  • Unconfirmed reporting: Ars Technica says two sources told it early data points to the rocket's propellant feed systems rather than the engines themselves, and that one engine may have run at lower thrust for most of the burn. Ars stresses the data is very preliminary.

The BE-4 question matters beyond Vulcan. Blue Origin's New Glenn uses seven BE-4s, and it has been grounded since a ground test explosion in May. See what happened to New Glenn and when New Glenn may fly again.

What happened to the 40 Amazon Leo satellites?

They were lost. Amazon's mission page says "the payload was lost", and Reuters reports the satellites were destroyed. Because the rocket never reached orbit, none of them went into service.

The FAA says it activated two Debris Response Areas during the flight. Those are zones where it moves aircraft away, or holds them on the ground, when debris falls outside the planned hazard area. Neither ULA nor the FAA has said exactly where the debris came down.

What does the failure mean for Amazon Leo?

It costs Amazon 40 satellites and, likely, time. Before LV-01, Amazon says it had launched nearly 400 Leo satellites on 14 missions since April 2025.

Vulcan is meant to be Amazon's main rocket. LV-01 was the first of 38 Vulcan launches Amazon has bought, and Amazon says Vulcan will carry more than 1,500 first-generation satellites, close to half the network. Amazon had said LV-02 could follow within weeks of a normal LV-01 flight. That now depends on the investigation.

Amazon's statement backed its partner: "There is risk with any launch, and that's especially true for inaugural missions like LV-01. ULA has been a trusted partner for Amazon, and we believe they'll learn from this mission and deliver on their long-term plans for Vulcan."

Amazon uses several rocket companies on purpose. Its next listed launch is LE-04 on Ariane 6, carrying 36 satellites from Kourou, French Guiana, no earlier than 23 November 2026.

What about the FCC deadline?

The July 2026 deadline is already gone. Amazon's licence from the Federal Communications Commission (FCC) required 1,616 satellites, half the network, in orbit by 30 July 2026. On 5 June 2026 the FCC waived that milestone, with conditions. The final deadline stays: all 3,232 first-generation satellites by 30 July 2029.

The conditions matter here. Satellites launched after 30 July 2026 temporarily lose their priority rights to radio spectrum, until 30 March 2028 or until Amazon has half the network working, whichever comes first, the FCC order says.

In my view, losing one launch of 40 satellites does not by itself break the 2029 deadline. A long Vulcan grounding is the bigger risk, because Vulcan is meant to carry so much of the network.

What does it mean for ULA and Vulcan?

Vulcan stays on the ground until the investigation is done. The FAA says a return to flight depends on it deciding that any system, process or procedure linked to the failure does not affect public safety. It will oversee ULA's investigation and must approve the final report and any fixes. Neither has given a timeline.

The US Space Force is also a big Vulcan customer. It had already paused national security launches on Vulcan after a booster nozzle problem on the February 2026 flight, Space.com reports. The Space Force has not made a public statement on LV-01 that we could find.

The same Ars report expects the failure to sideline Vulcan for at least half a year, and probably longer. That is a media estimate, not ULA's. See when will Amazon Leo and Vulcan fly next for the latest.

What happens next?

  • Investigation: ULA works through the flight data with Blue Origin and others, under FAA oversight. ULA says it will share more as it learns more.
  • Amazon Leo: LE-04 on Ariane 6, no earlier than 23 November 2026, is the next chance to add satellites.
  • Vulcan: no return-to-flight date yet. We track this in when will Amazon Leo and Vulcan fly next.

We will update this page when ULA or the FAA names a cause. Follow upcoming flights on our launch schedule and in this week's launches, and see how Amazon's rival is doing in what is Starlink and Amazon Leo vs Starlink on price.

Frequently asked questions

What happened to Vulcan LV-01?

ULA's Vulcan rocket lifted off at 12:40:30 p.m. EST (17:40:30 UTC) on 15 November 2026 from Cape Canaveral with 40 Amazon Leo satellites. It failed to reach orbit. ULA lost telemetry about 10 minutes into the flight, and Amazon says the payload was lost.

Why did the Vulcan rocket fail?

The root cause is not known yet. ULA says early data shows low performance from the booster, Vulcan's first stage, just after liftoff. Stage separation then happened too low and too slowly to reach orbit, and the Centaur V upper stage could not make up the difference.

Was it a BE-4 engine problem?

Not confirmed. Vulcan's first stage uses two BE-4 engines built by Blue Origin, but ULA has not said whether the engines played a role. Ars Technica reports, citing two unnamed sources, that early data may point to the rocket's propellant feed systems rather than the engines. That is unconfirmed reporting, not an official finding.

What happened to the 40 Amazon Leo satellites?

They were lost. The rocket did not reach orbit, so the satellites never went into service. The FAA says it activated two Debris Response Areas during the flight and briefly slowed or held aircraft outside the area where debris was falling.

Is Vulcan grounded?

Vulcan cannot fly again until the FAA decides that whatever caused the failure does not affect public safety. ULA leads the investigation, and the FAA oversees it and must approve the final report. Neither has given a return-to-flight date.

Does this delay Amazon Leo?

Amazon has not given a new schedule. LV-01 was the first of 38 Vulcan launches Amazon bought, and Vulcan is meant to carry more than 1,500 of its first-generation satellites. Amazon's next listed launch is LE-04 on Ariane 6 with 36 satellites, no earlier than 23 November 2026. Its FCC deadline to deploy all 3,232 first-generation satellites is 30 July 2029.

Is this ULA's first failure?

Reuters describes it as ULA's first mission failure in its 20-year history. It was Vulcan's fifth flight. Two earlier Vulcan flights had solid rocket booster nozzle problems but still reached their target orbits.

Sources

  1. ULA: Vulcan Leo 1 updates (15 and 17 Nov 2026)
  2. FAA: FAA requires mishap investigation of ULA KV-01 (16 Nov 2026)
  3. Amazon: Amazon Leo mission updates, with the LV-01 editor's note (updated 15 Nov 2026)
  4. FCC Space Bureau: order granting Amazon Leo a limited milestone waiver, DA 26-553 (5 Jun 2026)
  5. SpaceNews: ULA CEO says Vulcan failure probe focused on liquid core booster (17 Nov 2026)
  6. ULA on X: Vulcan suffered an anomaly 10 minutes into flight (15 Nov 2026)
  7. Amazon Leo on X: statement on LV-01 (15 Nov 2026)
  8. Ars Technica: The data is very preliminary, but Vulcan failure may not be due to BE-4 engines (Nov 2026)
  • #vulcan
  • #ula
  • #amazon-leo
  • #lv-01
  • #launch-failure
  • #faa
  • #be-4
  • #explainer

Follow The Space Road on Google

Add us as a preferred source and our stories show up more often in Google's Top Stories when you search for space news.

Add The Space Road as a preferred source on Google