On a Sunday afternoon in November, a rocket built by the long-standing partnership of Boeing and Lockheed Martin lifted off from Cape Canaveral carrying forty satellites meant to bring internet access to people far from the world's cables. Ten minutes later, something in its upper stage faltered, and the satellites never reached the orbit they were built for. It is a reminder that every effort to reach beyond the sky asks for trust in machinery that cannot yet be fully known, and that the path forward now depends on patient investigation rather than a single answer.
ULA's Vulcan Rocket Fails on Debut Amazon Leo Mission, Losing 40 Satellites
The first outright failure since ULA was formed in 2006
Forty satellites gone in one flight. What actually failed?
ULA says an anomaly hit about ten minutes in, during the Centaur upper stage's burn. Beyond that, no details yet.
Worth being careful there. ULA confirmed the anomaly and the failure to reach orbit. Anything about why is not confirmed.
But there were signs earlier, weren't there?
The first stage appeared to burn longer than the pre-launch timeline, separation looked late, and the Centaur made unusual orientation moves early on.
Those are observations from telemetry and animation, with the word appeared attached. They aren't a diagnosis. Nobody has tied them to the cause.
And the hold at T-minus 20 seconds?
Unexplained at the time, resolved, and the rocket launched at the end of the window. Whether it mattered is unknown.
Why does the history of boosters and engines matter?
Two earlier flights had nozzle problems, and the BE-4 valve issue destroyed a New Glenn. Both were addressed before Sunday.
Right, and the boosters looked normal. Those past issues are context, not suspects. The reporting doesn't link them to this failure.
What's the practical cost?
Amazon's schedule. Vulcan is grounded for an unknown period, New Glenn is still recovering, and the constellation needs over 3,300 satellites.
Le Pouls
- A Vulcan rocket carrying 40 Amazon Leo satellites lost its upper stage ten minutes into flight, and the payload never reached orbit.
- This is ULA's first outright launch failure since the company formed in 2006, landing hard on a program already strained by booster nozzle trouble.
- Engineers are now combing through telemetry for a cause, while the Space Force has paused national security Vulcan launches and New Glenn remains grounded.
- Amazon's push to build a constellation of more than 3,300 satellites now faces delays, with its 38 Vulcan flights and other launch contracts all waiting on answers.
On a Sunday afternoon in November, a rocket built by the long-standing partnership of Boeing and Lockheed Martin lifted off from Cape Canaveral carrying forty satellites meant to bring internet access to people far from the world's cables. Ten minutes later, something in its upper stage faltered, and the satellites never reached the orbit they were built for. It is a reminder that every effort to reach beyond the sky asks for trust in machinery that cannot yet be fully known, and that the path forward now depends on patient investigation rather than a single answer.
At 12:40 p.m. Eastern on Sunday, a United Launch Alliance Vulcan rocket rose from pad 41 at Cape Canaveral, a 214-foot vehicle carrying 40 Amazon Leo internet satellites. The first minutes looked ordinary, with the boosters burning out on schedule. But the first stage seemed to run longer than planned, and the Centaur upper stage moved in unusual ways early in its burn. About ten minutes into the flight, the rocket failed to deliver its payload to orbit.
The launch had already been delayed for days, by a ground-system problem that knocked out a nitrogen plant, network trouble, and a last-second hold at T-minus 20 seconds. Whether that hold had any link to the failure is still unknown. Vulcan had also suffered booster nozzle problems on earlier flights, and its engines, built by Blue Origin, carried their own history of valve trouble on a different rocket. ULA has not said whether any of this played a role.
For ULA, a partnership of Boeing and Lockheed Martin, this is the first outright failure since its founding in 2006. For Amazon, it is a serious setback in a race to build a satellite network that needs more than 3,300 spacecraft. Amazon has said every launch carries risk and that it trusts ULA to learn from this one. ULA has promised customers visibility into its investigation. Until the telemetry reveals what went wrong, the length of Vulcan's grounding remains uncertain.
At 12:40 p.m. Eastern on Sunday, United Launch Alliance's Vulcan rocket left pad 41 at Cape Canaveral Space Force Station and headed northeast. It stood 214 feet tall and carried 40 Amazon Leo internet satellites. Roughly ten minutes into the flight something went wrong, and the satellites never reached orbit.
About 50 minutes after liftoff, ULA issued a statement saying that data received by its Launch Director confirmed an anomaly 10 minutes into the flight. The company said the rocket failed to deliver the Amazon mission to orbit. It promised to work with its customer and other organizations to find the cause and return to flight quickly. The loss is the first outright failure for ULA, a Boeing and Lockheed Martin partnership, since the company was formed in 2006.
The liftoff itself was the product of several days of delay. A Friday attempt was scrubbed after problems knocked out a gaseous nitrogen plant that serves multiple launch providers. Saturday brought another delay because of network problems between the Vulcan and ground systems. On Sunday, controllers held the countdown at T-minus 20 seconds over an unexplained technical issue. ULA resolved it and launched at the very end of the window. It is not yet known whether that hold had anything to do with the failure.
The early flight looked normal. Six Northrop Grumman solid-fuel strap-on boosters and two methane-burning BE-4 engines produced 3.8 million pounds of thrust. The boosters burned out and fell away about a minute and 40 seconds after liftoff. But the first stage appeared to burn longer than ULA's pre-launch timeline called for, and it appeared to separate from the hydrogen-fueled Centaur upper stage later than expected. Telemetry-driven animation showed the Centaur making unusual orientation adjustments early in its burn, which was planned to last 12 minutes and 15 seconds. ULA's commentators mentioned no problems, and the broadcast ended without confirming whether that first Centaur firing ran its full length.
The boosters were a particular worry going in. This was only Vulcan's fifth flight and its first in nine months, during which ULA and booster supplier Northrop Grumman worked on nozzle problems that marred flights in 2024 and this past February. The Space Force put Vulcan launches of national security payloads on hold pending further analysis, though commercial flights could proceed. ULA CEO Mark Peller told Aviation Week & Space Technology before the flight that the company had identified three credible causes and mitigated all of them. The boosters appeared to work normally Sunday.
The BE-4 engines carried their own history. Blue Origin, which builds them, had a valve problem in its New Glenn rocket, where an oxygen valve in one of seven BE-4 engines caused a catastrophic on-pad explosion last May. Peller said Blue Origin developed a design improvement and retrofitted the engines on this Vulcan, and that the work is continuing through ULA's engine inventory. The company has not said whether the engines played any role Sunday.
For Amazon the stakes are large. This was the first of 38 Vulcan flights it has bought for its Leo constellation, which is meant to compete with Starlink and other space-based internet providers. ULA has already flown eight Leo missions on Atlas 5 rockets. Amazon has also booked 24 launches on New Glenn, 24 on Europe's Ariane 6 and 13 on SpaceX's Falcon 9. The constellation needs more than 3,300 satellites, and Sunday's flight would have raised the number launched to 436. Amazon now waits on ULA's investigation, and on Blue Origin getting New Glenn flying again.
Amazon Leo said on X that every launch carries risk, especially inaugural missions like LV-01, and that it believes ULA will learn from this one. ULA promised customers visibility into the investigation. NASA Administrator Jared Isaacman offered help on X, saying Artemis, Moon Base and the nation need ULA. The cause is still unknown, and the length of Vulcan's grounding will depend on what engineers find in the telemetry.
Citations marquantes
The team at NASA is available to assist in all matters related to the investigation and remediation effort. Artemis, Moon Base, and the nation need ULA.— NASA Administrator Jared Isaacman, on X
ULA is committed to full transparency with our customers, and they will have visibility into the investigation process.— United Launch Alliance statement