Twenty years without a single lost mission at United Launch Alliance came to an end on Sunday when its Vulcan rocket failed after liftoff from Cape Canaveral, taking 40 Amazon Leo internet satellites down with it.
Lifting off shortly after lunchtime in Florida, the flight was meant to mark Vulcan’s comeback after nine months on the ground. On two of its four earlier flights a nozzle had burned off one of the strap-on solid boosters, and engineers had spent most of the year redesigning it. Those boosters seemed to behave this time. About ten minutes into the mission, however, ULA said it had detected an anomaly and that the payload would not reach orbit. The company, created in 2006 when Boeing and Lockheed Martin merged their rocket businesses, said it was too early to know the cause and promised full transparency.
Ars Technica, citing several people familiar with the flight, reported that the trouble lay in the core stage rather than the Centaur upper stage. Its two Blue Origin BE-4 engines kept burning roughly 30 seconds past their planned cutoff, and telemetry animation showed the rocket beginning to spin before the Centaur separated and tried, without success, to steer back on course.
Amazon arguably loses the most. Its Leo network, built to rival SpaceX’s Starlink, has only 396 satellites in orbit out of more than 3,200 planned, while hundreds more wait in storage. This was the first of 38 Vulcan flights it bought. The company said every launch carries risk and that it still trusts ULA.
The Pentagon faces knock-on effects too. Vulcan is supposed to carry around half of upcoming US national security missions but remains barred from them until investigators finish. NASA chief Jared Isaacman offered help, noting the agency plans to fly a version of Centaur on future Artemis Moon rockets. If the BE-4 is implicated, Blue Origin’s own New Glenn, which uses a similar engine, could also be delayed.
