
ULA Vulcan Centaur Fails on Return-to-Flight, 40 Amazon Leo Satellites Lost
United Launch Alliance's Vulcan Centaur lifted off from Space Launch Complex 41 at Cape Canaveral at 12:40 p.m. Eastern on Sunday, carrying 40 Amazon Leo internet satellites. About 50 minutes later, ULA said the rocket suffered an anomaly 10 minutes into the flight and failed to deliver the mission to orbit.
United Launch Alliance's Vulcan Centaur lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station at 12:40 p.m. Eastern on Sunday, Nov. 15, carrying 40 Amazon Leo internet satellites. The satellites did not reach orbit.
About 50 minutes after liftoff, ULA said the rocket had suffered an anomaly 10 minutes into the flight.
"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," the company said in a statement posted on X. "Since the anomaly just occurred, we don't have any specific data yet to understand what occurred today."
Space com and Spaceflight Now published the same wording. Spaceflight Now also quoted ULA as saying it would work with its customer and other organizations to find the cause, determine the appropriate corrective action, and return to flight as quickly as possible.
Key details
Sunday's flight, named Vulcan Leo 1, was the first Vulcan launch for Amazon's broadband constellation, previously called Project Kuiper and now known as Amazon Leo. It was the fifth flight of the Vulcan Centaur, and the first in nine months.
The launch had slipped from a mid-November target. Spaceflight Now reported that a Friday attempt was scrubbed after problems at a gaseous nitrogen plant that serves multiple launch providers at the Cape, and that a Saturday attempt was delayed by network problems between the rocket and ground systems. On Sunday, controllers held the countdown at T-minus 20 seconds because of an unexplained technical issue, then launched at the end of the window. It is not known whether that hold was related to the later anomaly.
Vulcan flew with six solid rocket boosters. Those boosters appeared to perform as expected, according to Space com and Spaceflight Now, including on the nozzle problem that had kept the rocket off the pad. On two earlier missions, the second flight in October 2024 and the fourth in February 2026, a solid-rocket nozzle burned through and fell off about 30 seconds after launch. The rocket still delivered those payloads, but the U.S. Space Force paused national security launches on Vulcan until ULA addressed the issue.
A different problem ended Sunday's mission. Spaceflight Now and Ars Technica reported that the two BE-4 first-stage engines, built by Blue Origin, appeared to fire longer than ULA's pre-launch timeline. ULA has not identified a cause or named a failed stage.
Spaceflight Now and Reuters described the outcome as ULA's first outright mission failure since the Boeing-Lockheed Martin joint venture was formed in 2006.
Why it matters
Amazon Leo is planned as a constellation of more than 3,200 satellites that will compete with SpaceX's Starlink. Space com reported that about 400 of those satellites were already in orbit before Sunday, flown on Atlas V, Falcon 9, and Ariane 6. Sunday was supposed to be Vulcan's first contribution. Spaceflight Now reported that Amazon has purchased 38 Vulcan flights for the constellation.
The mission was meant to mark Vulcan's return to flight after months of solid-booster work. Instead, ULA's new flagship rocket ended the day short of orbit, and Amazon is short 40 satellites.
More stories

Arecibo Observatory Sent a 1,679-Bit Message Toward M13 in 1974

SpaceX Starship Flight 15 Completes Ship 42 Tower Catch

SpaceX Plans 70-Meter Starship V4 Ship With Nine Engines

Voyager 1 Nears One Light-Day From Earth

Victor Glover Describes Family Talks as a Challenge Before Artemis II


