Vulcan launch failure destroys 40 Amazon Leo satellites

ULA's rocket suffered an anomaly about 10 minutes into the flight on 15 November, reportedly the company's first mission failure, and the cause is still unknown.

FrontierPublished
What happened
A ULA Vulcan rocket failed to reach orbit on 15 November, losing all 40 Amazon Leo satellites aboard.
What’s new
The loss is reportedly ULA's first mission failure, and it came on the first of 38 Vulcan launches Amazon bought.
Why it matters
Vulcan is meant to be the main launcher for Amazon's Starlink rival, so further Leo flights on it must wait for ULA's investigation.

A United Launch Alliance Vulcan rocket failed to reach orbit on 15 November, and the 40 Amazon Leo internet satellites it carried were lost. In a statement on X quoted by The Verge, ULA said data received by its launch director showed the vehicle suffered an anomaly roughly 10 minutes after leaving Space Launch Complex 41 and did not deliver Amazon's payload to orbit.

GeekWire reports that liftoff came at 12:40 p.m. ET from Cape Canaveral Space Force Station. The launch followed two days of delays and a countdown hold at 20 seconds to resolve a technical issue. It is not known whether that issue played a role.

What is known about the failure

ULA says it has no specific data yet on the cause. The company says it will cooperate with Amazon and other parties to identify what went wrong and resume flights as soon as it can. ULA said it holds itself to a standard of mission success: "Today, we did not meet that standard." According to The Verge, the company also pledged to be transparent as its investigation continues.

Early technical details come from secondary reports. Spaceflight Now, as cited by GeekWire, placed the anomaly during the burn of the Centaur upper stage, which uses two RL10 engines from L3Harris. According to the same report, the first stage seemed to run past its planned burn time. Spaceflight Now said a telemetry-based animation showed the Centaur making unusual orientation changes early in its burn. Northrop Grumman's six solid boosters caused problems on two earlier Vulcan flights. This time they appeared to work normally, according to Space.com and Spaceflight Now, as cited by GeekWire.

Both outlets describe the loss as a first for ULA. GeekWire, citing Spaceflight Now, calls it the first complete mission loss for the Boeing–Lockheed Martin joint venture since its 2006 formation, while The Verge says it is reportedly the first failure in the company's 20-year history.

A setback for Amazon Leo

According to GeekWire, Vulcan had not flown for nine months, and this mission opened a contract of 38 Vulcan launches bought by Amazon. Vulcan carried 40 satellites, compared with 29 on the last Atlas 5 Leo launch. Over the contract, Vulcan is due to loft more than 1,500 first-generation Leo satellites, the largest share of any launcher Amazon uses.

Before the failure, Amazon had put 396 Leo satellites into orbit across 14 missions since April 2025. GeekWire reports that Amazon's deadline for having all 3,232 first-generation satellites in orbit and working is 30 July 2029. Amazon had said a second Vulcan mission could follow within weeks, but that flight now depends on ULA's investigation. Amazon also has 24 launches booked on Blue Origin's New Glenn, a rocket that has not flown since a ground-test explosion in May. The next scheduled Leo launch is an Ariane 6 flight carrying 36 satellites, no earlier than 23 November.

In its post on X, Amazon Leo said every launch involves risk, especially inaugural missions such as LV-01. It described ULA as a trusted partner that it expects to learn from the failure.