Vulcan Centaur Failure Destroys 40 Amazon Leo Satellites in First Mission for the Constellation

A United Launch Alliance Vulcan Centaur rocket failed roughly ten minutes after liftoff from Space Launch Complex 41 at Cape Canaveral on 15 November 2026, destroying all 40 Amazon Leo internet satellites it carried. The mission, designated Vulcan Leo 1 or LV-01, was the first Vulcan flight for Amazon’s satellite broadband constellation and the rocket’s first launch in nine months.

  • Total loss: All 40 Amazon Leo satellites were destroyed after ULA confirmed an anomaly about ten minutes into flight.
  • First total failure: It marks the first complete mission failure for ULA since Boeing and Lockheed Martin formed the joint venture in 2006.
  • Heaviest payload yet: The rocket carried more than 22,700 kilograms of satellites, the largest and heaviest payload in ULA’s history.
  • Debut configuration: The flight introduced the VC6L variant with six solid rocket boosters and a shortened Centaur V upper stage optimized for low Earth orbit.

What happened during the ascent

ULA’s launch broadcast described a nominal climb. At one minute and 45 seconds, the six solid rocket boosters separated at an altitude of about 35 kilometers. Around the six-minute mark, the company confirmed first-stage separation. The Centaur V upper stage then ignited and the payload fairing opened, with the vehicle flying at roughly 153 kilometers altitude and more than 17,700 km/h, east of Charleston, South Carolina.

That was the last technical update before ULA’s statement. “Based on data received by our Launch Director, we confirm that the Vulcan vehicle launched from Space Launch Complex 41 suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit,” the company said. ULA added that because the anomaly had just occurred, it had no specific data yet to understand what happened.

Spaceflight Now reported that the first stage appeared to burn longer than planned and separated later than expected, and that telemetry animations showed unusual orientation maneuvers by the Centaur at the start of its burn. ULA did not confirm those observations. The countdown had already faced disruptions: a Friday attempt was scrubbed over a failed nitrogen plant serving multiple launch providers, Saturday’s attempt was postponed by a network issue between the rocket and ground systems, and Sunday’s countdown paused 20 seconds before liftoff for an unexplained fault. Whether any of these played a role remains unknown.

A rocket returning from scrutiny

The flight was Vulcan’s fifth since its 2024 debut. Its previous two missions, in 2024 and February 2026, saw damage to the nozzles of Northrop Grumman-built solid rocket boosters; both still reached orbit, but the US Space Force paused national security launches pending an investigation. ULA said it identified three credible causes and applied nozzle changes to this vehicle. Before liftoff, ULA CEO Mark Peller told Aviation Week & Space Technology that every flight generates data and teaches the company something.

The mission also introduced a new Centaur V upper stage for low Earth orbit, 1.8 meters shorter and carrying a third less propellant than the previous model, a weight saving that lets each rocket lift more satellites. Fully loaded, the vehicle stood 65.5 meters tall and weighed about 903.5 tonnes. The plan called for deploying the satellites from minute 70 over the Pacific at roughly 459 kilometers altitude in 16 separations: four single deployments and twelve triple deployments.

“There is risk with any launch, and that’s especially true for inaugural missions like LV-01,” Amazon said. “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.”

NASA Administrator Jared Isaacman offered technical assistance for the investigation, according to reports. ULA has not said how long the analysis will take or when Vulcan will fly again.

Why the loss matters for Amazon Leo

Amazon has contracted 38 Vulcan launches, and the company estimated the rocket would carry more than 1,500 satellites, close to half of its first-generation constellation. Melissa Wuerl, Amazon Leo’s director of launch systems, had described Vulcan as central to that build-out. Before Sunday, Amazon had placed 398 Leo satellites in orbit across 14 missions since 2025, about 12% of the 3,236 needed for global coverage, and had hoped to begin initial internet service this year. The company faces a deadline of 30 July 2029 to put its first-generation constellation into operation.

Amazon spreads launches across several vehicles: 38 with Vulcan, 24 with Blue Origin’s New Glenn, 24 with Europe’s Ariane 6 and 13 with SpaceX’s Falcon 9. Those alternatives have their own troubles. New Glenn exploded on its launch pad in May during a ground test, days before a scheduled Amazon Leo flight; the investigation traced the problem to a main oxygen valve in a BE-4 engine, the same model that powers Vulcan’s first stage. Blue Origin retrofitted the BE-4 engines on this Vulcan with a design change, though it is unclear whether they played any role in Sunday’s failure. Amazon’s next launch is an Ariane 64 carrying 36 satellites, no earlier than 23 November.

The failure lands at the worst possible moment for ULA, which was trying to establish a regular cadence and convince the Space Force that Vulcan is ready for national security missions. A lengthy grounding would tighten US launch capacity while SpaceX’s Falcon 9, the world’s most active rocket, is no longer accepting new bookings. For Amazon, the setback widens the gap with Starlink, which operates more than 11,000 satellites and millions of customers, and whose parent company deploys its own hardware. Reliability, not manifest size, will decide how quickly the orbital broadband race narrows.

Sources & References