Networks & InfrastructureAmazon LeoVulcan RocketUnited Launch AllianceSatellite Constellation
Amazon Loses 40 Satellites as Vulcan Rocket Fails on First Leo Mission
Amazon lost 40 LEO satellites after ULA's Vulcan rocket failed ten minutes into its November 15 flight from Cape Canaveral, ULA's first total failure since 2006.
Networks & InfrastructureWhy it matters
- ULA's Vulcan rocket lost 40 Amazon Leo satellites on November 15, the company's first total failure since 2006.
- The anomaly occurred 10 minutes into flight; Ars Technica reports it struck the booster stage.
- LV-01 was the first of a planned 38-launch partnership between Amazon and ULA.
- Amazon Leo has launched nearly 400 satellites across 14 missions since April 2025.
- The next Amazon launch, Arianespace's LE-04 with 36 satellites, is targeted for no earlier than November 23.
The story
Amazon lost 40 low Earth orbit satellites on November 15 after United Launch Alliance's Vulcan rocket suffered an anomaly ten minutes into flight, ending the largest single batch of Amazon Leo spacecraft attempted to date and marking ULA's first total mission failure since the company was formed in 2006.
The mission, designated Leo Vulcan 1 (LV-01), lifted off from Cape Canaveral Space Force Station and was meant to open a 38-launch partnership between Amazon and ULA. ULA, created through the merger of the rocket divisions of Boeing and Lockheed Martin, confirmed the vehicle failed to reach orbit. "ULA experienced an anomaly with the Vulcan rocket carrying Leo satellites, and the payload was lost," Amazon said in a statement.
The failure point came late in the ascent. According to updates on ULA's launch blog, staging, ignition of the Centaur V upper stage and payload fairing jettison all proceeded as planned. The final update before contact was lost placed the vehicle at 95 miles in altitude, traveling in excess of 11,000 mph east of Charleston. ULA said the anomaly occurred ten minutes into the flight.
What went wrong?
The cause remains under investigation. "Every flight generates data, and every flight teaches us something. Since the anomaly just occurred, we don't have any specific data yet to understand what occurred today," ULA said in a statement.
Ars Technica, citing multiple sources, reported that the anomaly struck the booster stage of the rocket — not the Centaur V upper stage and not the solid rocket boosters. That distinction matters. Vulcan already suffered a solid rocket booster nozzle anomaly during a launch in February. ULA said it, supplier Northrop Grumman, the US Space Force and other government agencies ran a "rigorous investigation" and completed a successful test by May.
A booster-stage failure on this flight would point investigators toward new territory, because LV-01 flew several first-of-their-kind configurations.
- It was the first mission to fly a shorter, optimized version of ULA's Centaur V upper stage, designed to carry more satellites.
- It was the first Vulcan flight in a new six-booster configuration.
- It was the first ULA mission to use new Amazon-funded infrastructure at Cape Canaveral, including a dedicated Vertical Integration Facility and a new mobile launch platform built for Leo missions.
Amazon noted the upgrades before the flight, stressing that while Vulcan had flown several missions for other ULA customers, this inaugural Amazon Leo launch carried meaningful technical change.
What does this change for Amazon's constellation?
In the short term, it removes 40 satellites from Amazon Leo's deployment schedule and puts the Vulcan campaign on hold pending an investigation. LV-02 had been expected to launch "within weeks" of a nominal LV-01 mission; that timeline now depends on how quickly ULA isolates the fault.
Amazon framed the loss as a known launch risk rather than a program setback. "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," the company said.
The stakes for Amazon are considerable. Melissa Wuerl, director of launch systems for Amazon Leo, said last week: "Larger rockets and more frequent launches are critical to scaling our constellation and getting service to customers, and the Vulcan program is designed to deliver on both dimensions." Vulcan is not a marginal supplier to the program. "Vulcan will launch close to half our first-generation constellation, making it our primary workhorse over the next several years, and we're looking forward to kicking off the sprint with our partners at ULA," Wuerl said.
Losing roughly half of a first-generation constellation's planned lift capacity to a grounded rocket is the practical problem now in front of Amazon's launch team.
The schedule ahead
The loss interrupts, but does not halt, Amazon Leo's build-out. The constellation has launched nearly 400 satellites across 14 missions since its first launch in April 2025. Amazon holds contracts with multiple providers beyond ULA: Arianespace, Jeff Bezos' Blue Origin and Elon Musk's SpaceX.
The next scheduled mission is already on the calendar. Arianespace's Leo Europe 4 (LE-04) is targeting a launch no earlier than November 23 from Europe's Spaceport in Kourou, French Guiana, carrying 36 Amazon satellites into orbit.
That flight will keep the deployment pipeline moving while ULA investigates. How long Vulcan remains grounded — and whether the six-booster configuration or the shortened Centaur V plays a role in the failure — will determine whether Amazon's 38-launch agreement with ULA can recover its intended pace in 2026.
Also reported
Source: datacenterdynamics.com
More from James Calloway
Show full bio
Staff writer covering companies, deals and strategy in Carrier business, 5G and 6G, fiber and broadband at Telecom Gazette.
503 articles