What happened on Sunday?
After two scrubs - a nitrogen plant power outage on Friday and a ground-to-rocket communications issue on Saturday - Vulcan lifted off from Cape Canaveral on Sunday, November 15 at 12:11 p.m. EST. About 10 minutes into the flight, something went wrong. "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," ULA said, adding that it has no specific data yet on what occurred.
Update, November 18: ULA's first detailed account changes that picture. Early data suggests "low booster performance" - ULA's term for the core first stage - just after liftoff, so the stage separated when the rocket was too low and moving too slowly to reach orbit, GeekWire reports. The Centaur upper stage and its two RL10 engines apparently started and operated normally but could not make up the shortfall, and the six Northrop Grumman solid rocket boosters - the source of two earlier Vulcan anomalies - appear to have performed normally. ULA says it lost telemetry and the mission at about the 10-minute mark, but the trouble began just after liftoff. The core stage is powered by two Blue Origin BE-4 engines, but ULA has not said what caused the shortfall or whether the engines played a role, and wants to avoid speculation; the FAA will oversee the ULA-led investigation and approve its final report. Blue Origin CEO Dave Limp said his company is supporting ULA with BE-4 data and analysis while readying New Glenn for its own return to flight. Amazon's public response was measured: "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."
What does the failure mean for Amazon Leo?
It removes the constellation's biggest single addition at the worst time. Reuters counts 398 Leo satellites deployed across 14 launches since 2025 - about 12% of the 3,236 satellites Amazon needs for global service coverage. The 40 satellites lost on Sunday were the largest batch Amazon had ever launched at once, and the company had hoped to start initial internet service this year.
The deeper problem is dependence on other people's rockets. The New Glenn explosion in May happened days before that rocket was due to carry Amazon Leo satellites; Vulcan then spent nine months grounded over booster-nozzle and engine investigations before failing on its return. Reuters notes SpaceX's lead rests partly on launching its own satellites on its own rockets, and that lead is now over 11,000 satellites against Amazon's few hundred. Amazon says it believes in Vulcan's long-term plans, but it has not said how LV-01's loss changes the service start date. The next scheduled Leo launch is an Ariane 6 mission carrying 36 satellites, targeted for no earlier than November 23 from French Guiana, per GeekWire.
What does it mean for Vulcan and US launch capacity?
For ULA, this breaks a 100% mission success record maintained since the company formed in 2006 from Boeing's Delta and Lockheed's Atlas programs. The failure is expected to trigger a lengthy investigation that keeps Vulcan off the market for months, Reuters reports - and the Space Force had specifically been waiting for this mission's data before letting Vulcan resume national security launches, a decision that is now presumably on hold.
The timing compounds a wider US launch bottleneck. SpaceX is winding down Falcon 9 - the world's most active rocket - and is no longer taking bookings for it, while Blue Origin's New Glenn remains grounded after its May explosion. Fewer available rockets means Amazon's remaining deployment schedule, and everyone else's, competes for scarcer lift.
What if you were waiting for Amazon Leo?
Plan on Starlink timelines, not Leo's. Amazon has not given a revised service date, and the constellation math - 398 satellites up, roughly 2,800 more needed for global coverage, against a grounded primary rocket - argues for patience. We covered the run-up to this mission in our launch preview and scrub reports; this article supersedes both.
If you need satellite internet now, check the price and terms shown at your own checkout, and our referral link is below. Check Starlink's eligibility and the reward shown for your order; compatibility with other offers is not assumed.
Frequently asked questions
What caused the Vulcan failure?
Still under investigation, but ULA's November 18 account says early data points to an underperforming first stage: the core stage separated too low and too slow to reach orbit. The upper stage and solid boosters appear normal; the role, if any, of the BE-4 engines is undetermined.
Were the 40 Amazon Leo satellites destroyed?
Yes. The payload failed to reach orbit and was lost - the largest single batch Amazon had launched.
Has ULA failed a mission before?
No. This is the first mission failure in ULA's 20-year history, ending a 100% success record since 2006.
How big is Amazon Leo's constellation now?
About 398 satellites deployed since 2025, roughly 12% of the 3,236 Amazon needs for global coverage, per Reuters.
When will Vulcan fly again?
No date. The failure is expected to ground the rocket for months during the investigation, and the Space Force was waiting on this flight before restoring Vulcan to national security missions.
Does this delay Amazon Leo service?
Almost certainly, though Amazon has not given a revised date. It had hoped to begin initial service this year.
Sources
- Reuters: Rocket from Boeing-Lockheed firm fails mid-flight, destroys payload of Amazon satellites (November 15, 2026)
- The Verge: Vulcan rocket fails, destroying 40 Amazon Leo satellites (November 15, 2026)
- SpaceNews: Vulcan launch of Amazon Leo satellites fails (November 15, 2026)
- GeekWire: Early data points to Vulcan's first stage in launch failure that cost Amazon 40 Leo satellites (November 17, 2026)