Back to Newsroom

ULA Vulcan fails to deliver 40 Amazon Leo satellites to orbit

ULA confirmed the mission failed to reach orbit. Amazon had tied its next Vulcan launch to a successful first flight; revised timing is unverified.

United Launch Alliance said Sunday that its Vulcan rocket failed to deliver Amazon's Leo mission to orbit after an anomaly about 10 minutes into flight. The mission was intended to carry 40 broadband satellites.

The immediate business question is how the investigation affects Amazon's next launches. Before the flight, Amazon had made the timing of its second Vulcan mission conditional on a successful first mission. That condition now needs a new assessment; a revised launch date has not been verified.

ULA confirms the outcome, with the cause unresolved

ULA's November 15 statement, also published in the live updates linked from its mission page, said it would investigate the cause and determine corrective action with its customer and other organizations. It did not identify a cause or give a return-to-flight date.

The original mission description specified a 40-satellite payload. The failure establishes that this flight did not add those satellites to Amazon's network. It does not establish which component failed, the financial loss or the length of any interruption.

The next launch had a condition

In an account published November 9 and updated November 14, Amazon said its second Vulcan mission, LV-02, was being prepared and expected within weeks of a nominal LV-01 mission. In this context, nominal means a flight that proceeds as intended.

Amazon described 38 contracted Vulcan missions expected to deploy more than 1,500 first-generation satellites. That makes Vulcan's ability to launch repeatedly a substantial part of the program's deployment plan. Those figures describe contracted missions and intended deployment, not satellites already operating in orbit.

Our analysis: manufacturing progress and usable network capacity are separate milestones. Amazon says it has hundreds of flight-ready satellites. That inventory can support a faster launch pace once transport is available, but it cannot provide orbital coverage while it remains on the ground.

The consequence to measure is therefore how quickly Amazon can turn finished hardware into operating capacity. A replacement mission, a revised Vulcan schedule or a confirmed booking elsewhere would be more informative than assigning a company-wide earnings impact without disclosed costs.

Other launch providers give Amazon options

Amazon's plan also includes Arianespace, Blue Origin and SpaceX. That diversity is a reason to avoid treating one unsuccessful mission as proof that the entire service rollout must slip.

It is not evidence that another rocket can immediately absorb these satellites or the next Vulcan payload. Availability, compatibility and a confirmed booking would need to be established. The sources reviewed do not provide that replacement plan.

For Amazon Leo, the distinction is concrete: ULA has confirmed the failed delivery; the effect on the wider deployment calendar remains open. The next consequential disclosure is a supported path back to launches, with dates and capacity attached.

Source note: The outcome statement is dated November 15, 2026. Amazon's launch plans predate the flight. This report does not assign a cause, insurance recovery, loss value or revised service-start date. Business implications are TrendyVest analysis.

More from the Newsroom