United Launch Alliance (ULA) says early flight data from its failed Nov. 15 Vulcan mission points to low booster performance soon after liftoff. The vehicle did not place its payload of 40 Amazon Leo broadband satellites into orbit. ULA’s Nov. 17 update is preliminary: the FAA is overseeing a required investigation, and the root cause and next launch date remain unknown. ULA’s latest update, Reuters’ report and GeekWire’s coverage confirm the mission loss.

What happened to Amazon’s 40 Leo satellites?

Vulcan lifted off from Cape Canaveral on Nov. 15 carrying 40 satellites for Amazon Leo, Amazon’s low-Earth-orbit internet constellation. About 10 minutes into the flight, the vehicle suffered an anomaly and failed to deliver its mission to orbit. The payload was lost; the satellites did not join Amazon’s network, according to Reuters.

Amazon had described LV-01 as the first Vulcan mission for Leo and the largest batch it had planned to send on one rocket at that point. The flight was the first of 38 Vulcan launches under contract with ULA. Amazon said Vulcan would carry more than 1,500 first-generation Leo satellites across those missions, making the rocket a major part of its deployment plan. Its prelaunch announcement also listed Arianespace, Blue Origin and SpaceX among the program’s other launch providers.

What does ULA’s early investigation say?

In its Nov. 17 update, ULA said preliminary indications point to low booster performance just after liftoff. The company says that led to stage separation at an altitude and velocity below what was needed to reach orbit. The second stage and its RL10 engines appeared to operate as planned. ULA said the solid rocket boosters also appeared to perform normally.

These are early indications, not a final explanation of why the vehicle underperformed. ULA says it is still reviewing telemetry and cautions against speculation while the investigation is under way. It has not announced a definitive root cause or a return-to-flight date.

The distinction matters. ULA’s phrase “low booster performance” does not mean the company has identified a failed solid-rocket booster. Its update says those boosters appeared nominal. The failure mechanism and any corrective actions remain to be established.

Why does the FAA investigation affect the next launch?

The FAA said on Nov. 16 that it is requiring a mishap investigation, will oversee ULA’s work and must approve the final report, including corrective actions. The agency says Vulcan can return to flight when it determines that any system, process or procedure related to the mishap does not affect public safety. The FAA’s statement does not set a completion date.

Before launch, Amazon said its next Vulcan mission could fly within weeks of a nominal first mission. That was a conditional plan, not a date commitment after an unsuccessful flight. GeekWire reported that the next Vulcan mission must wait on the investigation. ULA says it will work to return to flight safely, but neither company has announced a new date.

Could the failure delay Amazon Leo service?

The lost payload is a deployment setback, but the size of any service delay is not yet known. Amazon had said it expected initial service rollout later in 2026. Reuters reported before the launch that 398 Leo satellites had been deployed across 14 earlier missions. Amazon’s prelaunch description called 40 the largest batch planned at the time. The failure removes one planned increment of capacity; it does not establish that Amazon’s whole rollout has stopped.

Amazon’s launch strategy is not limited to Vulcan. The company’s announcement lists other providers, including Arianespace, Blue Origin and SpaceX. That gives Leo alternative launch paths, although it does not guarantee that other rockets can replace Vulcan’s near-term capacity or timing. The main open questions are how quickly ULA and the FAA complete the investigation, and how Amazon adjusts its launch sequence afterward.

Reuters described the incident as ULA’s first mission failure in its 20-year history. Vulcan is intended to support both commercial and government launches, so the outcome of the safety review matters beyond Amazon’s satellite network.

What is confirmed—and what is not?

Confirmed: the Vulcan mission suffered an anomaly about 10 minutes after liftoff, and the 40 Amazon Leo satellites did not reach orbit. ULA has published preliminary data pointing to low booster performance early in the flight. The FAA is overseeing a required mishap investigation.

Not yet confirmed: the root cause, the corrective action, when Vulcan will return to flight, and whether Amazon’s expected service rollout will move. Treat specific delay forecasts or claims that the entire Leo program is halted as speculation unless Amazon, ULA or regulators provide new evidence.

Frequently asked questions

Did the Vulcan rocket explode?

ULA has described an in-flight anomaly and a lost mission. Its current update does not say the rocket exploded. The confirmed outcome is that the vehicle failed to deliver its 40-satellite payload to orbit.

Did Amazon lose 40 satellites that were already in service?

No. The 40 spacecraft were the payload on the failed launch and never joined the constellation. Reuters reported that Amazon had deployed 398 satellites on earlier launches before this mission.

Is Amazon Leo’s service launch now delayed?

No revised service date has been announced in the sources reviewed. Amazon had targeted initial service later in 2026, but the effect of the lost payload and the Vulcan investigation on that target is not yet clear.

When can Vulcan fly again?

There is no public return-to-flight date. The FAA says it must oversee the mishap investigation and determine that any related system, process or procedure does not affect public safety before Vulcan returns to flight.

Schedule effects remain uncertain while the investigation is under way. This article separates ULA’s preliminary telemetry findings from the FAA’s final determination.