Skip to content
Technology

United Launch Alliance Vulcan Rocket Fails, Destroying 40 Amazon Satellites

The mishap marks the first outright failure of a United Launch Alliance rocket since the company was formed in 2006.

By 3 min read

United Launch Alliance suffered a major mission failure on Sunday when its Vulcan Centaur rocket experienced an anomaly ten minutes into flight, resulting in the total loss of 40 Amazon internet satellites. The heavy-lift rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida, hauling the payload toward low Earth orbit as part of Amazon's expanding broadband constellation.

The company confirmed the failure roughly 50 minutes after liftoff. "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," United Launch Alliance stated on social media. The firm added that it would work closely with its customers and other appropriate organizations to determine the root cause.

This incident marks the first outright failure of a United Launch Alliance vehicle since the Boeing and Lockheed Martin joint venture was established in 2006. Sunday's flight was only the fifth mission for the Vulcan rocket and its first return to flight in nine months following extensive work to resolve previous issues involving strap-on solid-fuel booster nozzles from earlier flights.

The mission was intended to expand Amazon's low Earth orbit constellation, previously known as Project Kuiper and now referred to as Amazon Leo, which is designed to compete with rival satellite networks like SpaceX's Starlink. Amazon has contracted dozens of launches across various aerospace providers, needing more than 3,200 satellites to fully complete the global network. Sunday's flight was the first of 38 scheduled Vulcan launches purchased by Amazon.

Pre-launch preparations faced multiple hurdles before the rocket finally cleared the pad at 12:40 p.m. ET. A planned Friday attempt was scrubbed due to issues with a gaseous nitrogen plant, and a subsequent countdown on Saturday was delayed because of network communication problems between the rocket and ground systems. On Sunday, controllers temporarily halted the countdown at the T-minus 20-second mark due to an unexplained technical issue before successfully resetting for liftoff.

During the flight, the solid-fuel boosters appeared to perform nominally, burning out and separating as planned. However, the first-stage methane-burning BE-4 engines appeared to burn longer than outlined in the pre-launch schedule, and subsequent stage separation occurred later than expected. Telemetry data indicated that the hydrogen-fueled Centaur upper stage experienced unusual orientation adjustments during its initial engine burn before the mission ultimately failed.

Engineers and investigators will now review telemetry data to understand the precise sequence of events that led to the anomaly. The Vulcan fleet faces a potential grounding while the investigation proceeds, which will impact upcoming launch schedules for both United Launch Alliance and its commercial partners. NASA leadership has offered assistance to support the investigation and remediation efforts as the aerospace industry responds to the setback.

Sources

Related stories