Vulcan Rocket Fails, Destroying 40 Amazon Internet Satellites
A United Launch Alliance Vulcan rocket failed during its climb to orbit Sunday, destroying all 40 Amazon Leo broadband satellites aboard and creating a major setback for two of the largest players in the commercial space industry.
The 214-foot rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida at approximately 12:40 p.m. Eastern time. The mission initially appeared to proceed normally, but United Launch Alliance said the vehicle suffered an anomaly about 10 minutes into flight and failed to deliver its payload to orbit.
Largest Amazon Leo launch ends in failure
The mission, known as Leo Vulcan 1, carried the largest single group of satellites Amazon had attempted to launch for its low-Earth-orbit internet network. Amazon Leo is being built as a competitor to SpaceX’s Starlink, with thousands of satellites planned to provide broadband service around the world.
Reuters reported that all 40 satellites were lost. The failure occurred on Vulcan’s fifth flight and its first mission in nine months. It was also the first outright launch failure in United Launch Alliance’s history since Boeing and Lockheed Martin formed the company in 2006.
ULA has not identified the cause. The company said it had not yet received or analyzed enough data to determine what went wrong and promised to work with Amazon and other organizations to investigate, identify corrective action and return Vulcan to flight.
What happened during the ascent
Specialist reporting from Spaceflight Now said the rocket’s six strap-on solid-fuel boosters appeared to function and separate normally. Vulcan’s first-stage engines then continued the climb before the hydrogen-powered Centaur upper stage began its planned burn.
The company’s public confirmation placed the anomaly around 10 minutes after liftoff, during the upper-stage portion of the mission. ULA has not said which system failed, and early observations cannot establish a cause. Engineers will analyze telemetry, hardware performance and the mission timeline before determining when another Vulcan can launch.
The rocket uses BE-4 first-stage engines supplied by Blue Origin, which is assisting with the investigation. Reuters noted that the failure appeared to occur after the stages separated, but the available information was not sufficient to rule any system in or out.
Pressure on Amazon’s satellite timetable
Sunday’s mission was supposed to be the first of 38 Vulcan launches purchased by Amazon. The company has also reserved flights on Blue Origin’s New Glenn, Europe’s Ariane 6 and SpaceX’s Falcon 9 to assemble the constellation.
Amazon said after the failure that launch missions carry risk and described ULA as a trusted partner. The company’s mission update confirmed that the payload was lost while expressing confidence that ULA would learn from the failure.
Amazon had deployed 398 of the 3,236 satellites it says it needs for global coverage before Sunday’s attempt, according to Reuters. Losing the 40-spacecraft batch does not end the project, but it removes what would have been its largest single deployment and could increase pressure on an already demanding launch schedule.
A wider impact on U.S. launch capacity
The consequences extend beyond Amazon. Vulcan is intended to replace ULA’s long-running Atlas V fleet and perform national-security, commercial and scientific missions. A significant investigation could ground the rocket for months and force customers to rearrange launches in a market with limited heavy-lift capacity.
The investigation now must determine why a mission that appeared stable during its opening minutes failed before reaching orbit. Until ULA identifies the anomaly and completes corrective work, both its launch calendar and Amazon’s satellite expansion face new uncertainty.
Featured image: editorial illustration.