Vulcan finally flew on Sunday, and it didn’t make it. ULA’s Vulcan Centaur lifted off from Cape Canaveral at 12:40 p.m. ET (11:40 a.m. Chicago time) carrying 40 Amazon Leo broadband satellites, Space.com reports. About 10 minutes into flight, ULA said, the vehicle “suffered an anomaly” and “failed to deliver the Amazon mission to orbit.” ULA posted that on X about 50 minutes after launch and said it doesn’t yet have data on what happened.
The solid rocket boosters, the reason for the nine-month pause after nozzle problems in October 2024 and February 2026, appear to have done their job and separated on time. The problem came later. It was the first of 38 Vulcan launches Amazon has bought, after two scrubs this week, which I covered in the earlier updates.
My take
That’s a rough day for ULA and Amazon, and for anyone who wants more than one heavy-lift option. No guessing at causes from me. I’ll wait for ULA’s data. Expect Space Force to look hard at this before any national security payload rides Vulcan again.
God Bless, and Needs Garlic!
References & Further Reading
- Vulcan Centaur rocket fails during return-to-flight launch, 40 Amazon satellites lost (Space.com)
- ULA says Vulcan suffered an anomaly and failed to put 40 Amazon Leo satellites in orbit (Space Coast Wire)
- Update: Vulcan Centaur return-to-flight slips to Saturday (EtherNinja)
- ULA targets Friday the 13th for Vulcan’s return to flight (EtherNinja)