United Launch Alliance's Vulcan rocket failed about 10 minutes after liftoff on Sunday, destroying all 40 Amazon Leo internet satellites aboard — the rocket's first flight in nine months, its first carrying Amazon's constellation, and ULA's first total mission failure since 2006. The rocket lifted off at 12:40 p.m. Eastern from Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida, and the anomaly struck during the first burn of the Centaur V upper stage, before the satellites could reach orbit.
Why it matters: this flight was supposed to clear two names at once. Vulcan is one of only two rocket families the U.S. Space Force trusts with its most sensitive national security payloads, and Amazon Leo is Amazon's answer to SpaceX's Starlink — a constellation that needs more than 3,200 satellites, with roughly 400 in orbit before Sunday. Losing 40 at once, on the very flight meant to prove the rocket was fixed, grounds Vulcan again and pushes both the military's manifest and Amazon's build-out back by months at least.
The detail that stings is WHERE it failed. Vulcan had been grounded since February, when a nozzle on one of its GEM-63XL solid rocket boosters burned through on the USSF-87 Space Force mission — the second such nozzle failure, after one on its second flight in October 2024. The Space Force suspended Vulcan's national security launches; Northrop Grumman redesigned and test-fired an enhanced nozzle in April, and ULA said on October 28 that the contributors had been identified and mitigated. On Sunday the boosters performed as expected. The failure came instead in the Centaur — the upper stage, flying for the first time in its shortened, low-Earth-orbit-optimised form, on the maiden flight of the most powerful Vulcan configuration, the six-booster VC6L.
ULA's own statement, posted about 50 minutes after launch, made no attempt to dress it up: "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." The company said it had no specific data yet on what occurred: "Today, we did not meet that standard. We will work closely with our customer and other appropriate organizations to find the cause, determine the appropriate corrective action, and return to flight as quickly as possible." All future Vulcan launches are on hold pending the investigation.
Sunday was hard even before the failure. The mission — LV-01, the first of up to 38 Vulcan launches Amazon has booked, carrying the most satellites any Amazon Leo mission has flown — had already been delayed twice, for a commodity flow issue and a communications issue, and the day's first attempt held at T-20 seconds over a pressure-reducing valve anomaly before the rocket finally left at the end of its 29-minute window, the first Vulcan processed at Amazon's new Vertical Integration Facility.
What happens next is an investigation with two customers watching. The Space Force had already said it would review this flight's data separately before restoring Vulcan to the national security manifest — that clearance is now further away, not closer. Amazon, for its part, must rebuild the lost batch into a schedule that was already racing Starlink's enormous head start. Every Vulcan flight generates data, as ULA put it; the question the investigation must answer is why a rocket that spent nine months being fixed failed on a part nobody was looking at.
📰 ProfiloPolitics Member News — choose your news, share it, earn credit:
https://white-curlew-963569.hostingersite.com
📢 Join ProfiloPolitics on Telegram:
https://t.me/profilopoliticsnews