United Launch Alliance lost its heavy-lift Vulcan rocket and 40 Amazon Leo internet satellites when a flight anomaly occurred roughly ten minutes after liftoff on Sunday according to CBS News.
The failure deals a blow to Amazon’s satellite deployment timeline and marks the first total mission loss for United Launch Alliance since the Boeing and Lockheed Martin joint venture formed in 2006, Ars Technica reported. The 214-foot-tall rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station at 12:40 p.m. ET, powered by two methane-fueled BE-4 main engines built by Blue Origin and six Northrop Grumman strap-on boosters.
Initial telemetry indicated trouble before the ten-minute mark during the booster stage burn, according to Ars Technica. The twin BE-4 engines continued firing for roughly 30 additional seconds past their scheduled shutdown near the five-minute mark, suggesting an overburn to compensate for booster underperformance. Real-time telemetry broadcast by United Launch Alliance showed the vehicle begin to spin shortly before staging.
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. Full statement from @ulalaunch below. https://t.co/lS2GEioSak
Following separation, the Centaur V upper stage ignited its twin RL10 engines, but the flight failed to reach orbit. United Launch Alliance ended its live broadcast shortly afterward and confirmed the mission failure in a statement, noting that the company will work with customers to determine the root cause.
Investigation and engine history
Engineers face a potentially significant grounding of the Vulcan fleet while reviewing telemetry data from Sunday’s flight. The vehicle’s BE-4 engines had recently undergone retrofits to address an oxygen valve problem linked to a ground-test explosion at Blue Origin’s Launch Complex 36 in May, GeekWire reported.
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. Every flight generates data, and every flight teaches us…
Sunday’s flight was the first Vulcan mission in nine months, following a February launch failure involving a Space Force national security mission. That earlier mishap involved a nozzle separation on a Northrop Grumman solid rocket booster, though sources indicated the solid boosters appeared to function normally during Sunday’s ascent.
“Until this anomaly is solved, we will not be launching Vulcan missions,” Col. Eric Zarybnisky, the Space Force's portfolio acquisition executive for assured access to space, said two weeks after the February launch.
United Launch Alliance ended the webcast of its return to flight Vulcan mission, carrying Amazon LEO satellites, early and before payload deploy. Not a great sign, but we don't know what happened yet.https://t.co/g5ES2ZdRqr
“There is risk with any launch, and that’s especially true for inaugural missions like LV-01,” Amazon Leo said in a post on X, as GeekWire reported.
“ULA is committed to full transparency with our customers, and they will have visibility into the investigation process, which utilizes rigorous methodology and corrective action,” United Launch Alliance stated following the incident.

Amazon launch schedule impact
Amazon has purchased 38 Vulcan launches to deploy more than 3,200 satellites for its Leo constellation, which is designed to compete with SpaceX’s Starlink service. Prior to Sunday’s mishap, Amazon had launched 398 satellites using a combination of United Launch Alliance Atlas 5 rockets, SpaceX Falcon 9 boosters, and Arianespace Ariane 6 vehicles from South America.
The company’s next scheduled Leo mission is an Ariane 6 flight carrying 36 satellites, targeted for November 23, 2026, at the earliest, according to GeekWire. Amazon also holds launch reservations with Blue Origin’s New Glenn and SpaceX.
And LIFTOFF of the first Vulcan Amazon Leo mission, carrying 40 broadband satellites to low Earth orbit! pic.twitter.com/dv1MSjJUMF
Frequently asked questions about the Vulcan failure
What caused the Vulcan rocket anomaly?
United Launch Alliance has not yet determined the exact cause of the anomaly. Telemetry data showed the booster stage experiencing issues and overburning its BE-4 engines before the vehicle began to spin and failed to deliver its payload.
How many satellites were lost in the launch?
The mission carried 40 Amazon Leo internet satellites, which were completely lost when the rocket failed to reach orbit after launching from Cape Canaveral Space Force Station.
Multiple sources say the anomaly that impacted today's Vulcan launch occurred in the booster stage, not the Centaur V upper stage or SRBs. I don't yet know if the booster stage issue was caused by the BE-4 engines, the propellant management system, or another problem.
When was the previous United Launch Alliance failure?
Sunday’s incident was the first total mission failure for United Launch Alliance since the company was established through the merger of Boeing and Lockheed Martin’s rocket divisions in 2006.
Related reading