Page Nav

SHOW

Ads Place

ULA's Vulcan Fails 10 Minutes Into Flight, Losing 40 Amazon Leo Satellites — the Company's First Total Mission Failure Since 2006

United Launch Alliance's Vulcan rocket failed about 10 minutes into its flight on Sunday, November 15, destroying its payload of 40 Amazon Leo internet satellites and ending the launch company's run of mission success that stretched back to its formation in 2006.

The 214-foot Vulcan lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station at 12:40 p.m. Eastern on Sunday, riding six Northrop Grumman strap-on solid boosters and two methane-burning BE-4 engines. The solids appeared to perform normally and burned out about a minute and 40 seconds into flight. After the first stage separated, the hydrogen-fueled Centaur upper stage took over for a planned burn of 12 minutes 15 seconds — and something went wrong during that firing, Spaceflight Now reported. ULA has not identified the cause.

"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," ULA said in a statement issued about 50 minutes after liftoff. "We will work closely with our customer and other appropriate organizations to find the cause, determine the appropriate corrective action and return to flight as quickly as possible."

It was the first outright failure of a United Launch Alliance rocket since Boeing and Lockheed Martin formed the company in 2006, and only the fifth flight of the Vulcan — the rocket built to replace ULA's Atlas 5 fleet. Sunday's flight was Vulcan's first in nine months, after ULA and booster supplier Northrop Grumman worked through nozzle problems that marred two earlier flights, and it was the first of 38 Vulcan launches Amazon has purchased to build out Leo, its planned rival to SpaceX's Starlink network.

The weekend had already tested the rocket before it flew. A Friday attempt was scrubbed after problems knocked out a gaseous nitrogen plant that serves multiple launch providers; a Saturday attempt was delayed by network problems between the Vulcan and ground systems; and on Sunday the countdown held at T-minus 20 seconds for an unexplained technical issue before controllers resolved it and launched at the end of the window. Whether the hold played any role in the failure is not known.

For Amazon, the loss lands on a program already racing a clock. Reuters reported that 398 Leo satellites have been deployed across 14 launches since 2025 — about 12 percent of the 3,236 satellites Amazon needs for global service coverage — and that Sunday's flight was the first carrying Leo satellites on a Vulcan. "There is risk with any launch, and that's especially true for inaugural missions like LV-01," Amazon said in a statement carried by Reuters. "ULA has been a trusted partner for Amazon, and we believe they'll learn from this mission and deliver on their long-term plans for Vulcan."

The failure is expected to lead to a lengthy technical investigation that keeps Vulcan off the market for months, Reuters reported, deepening a U.S. launch bottleneck. Blue Origin, which supplies the BE-4 engines that power Vulcan's first stage, is working with ULA in the investigation, according to a person familiar with the matter who spoke to Reuters on condition of anonymity; it was not clear whether the BE-4s played any role, and the failure appeared to occur after the second stage separated from the BE-4-powered booster. NASA Administrator Jared Isaacman promised assistance if needed, Spaceflight Now reported.

Vulcan now waits on its own investigation. The rocket that was supposed to open Amazon's biggest launch campaign instead gave ULA the first total mission failure in its two decades — 10 minutes into a Sunday afternoon flight, with 40 satellites aboard.

No comments

Latest Articles