United Launch Alliance suffered the first total mission failure in its two-decade history on Sunday after its Vulcan rocket malfunctioned during flight, destroying a payload of 40 Amazon Leo broadband satellites and prompting an indefinite grounding of the launch vehicle.
Lifting off from Florida’s Cape Canaveral Space Force Station at 12:40 pm EDT, the rocket operated normally through the separation of its six strap-on solid rocket boosters. However, sources reported that trouble emerged in the booster stage, where the twin Blue Origin BE-4 main engines continued firing for roughly 30 seconds beyond their scheduled five-minute shutdown. Real-time telemetry broadcast by ULA indicated that the rocket began spinning around the time the Centaur V upper stage detached, and despite ignition and steering adjustments by the Centaur’s RL10 engines, the mission failed to achieve orbit.
The crash represents a significant setback for Amazon, which booked the mission as the first of 38 Vulcan launches intended to deploy its 3,292-spacecraft Leo broadband constellation against SpaceX’s Starlink. Although Amazon has manufactured over 1,000 satellites, only 396 are currently orbiting, leaving the majority of its hardware in storage amid recurring launch provider delays. With Blue Origin’s New Glenn rocket also delayed following a launchpad explosion in May, Amazon’s near-term deployment options remain largely constrained to previously reserved flights on Europe’s Ariane 6 and competitor SpaceX’s Falcon 9.
The failure also reverberates across the U.S. military and NASA. The Space Force currently relies on Vulcan for roughly half of its upcoming national security satellite flights and will likely need to shift more time-sensitive payloads to SpaceX. Meanwhile, NASA officials will be tracking ULA’s investigation closely, as the agency recently selected a variant of the Centaur upper stage to power future Space Launch System rockets for crewed Artemis lunar flights targeted to begin as early as 2028.
Source: arstechnica.com



