This story is currently available in Englisch only — a translation isn't ready yet.
ULA's Vulcan fails 10 minutes into flight, dooming 40 Amazon Leo satellites
The first outright failure for United Launch Alliance since it was formed in 2006 came during the Centaur upper stage's planned 12-minute burn.
ℹ️ Browser-Stimme · KI-Studiostimme bald verfügbar

United Launch Alliance's Vulcan rocket failed about 10 minutes into its climb to space on Sunday, dooming a payload of 40 Amazon Leo internet satellites and grounding the vehicle pending an investigation.
ULA said in a statement issued some 50 minutes after liftoff that the rocket, launched from Space Launch Complex 41 at the Cape Canaveral Space Force Station, "suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit." The company said it would "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 the company, a partnership between Boeing and Lockheed Martin, was formed in 2006. Sunday's flight was only the fifth for Vulcan, the rocket replacing ULA's fleet of Atlas 5 rockets, and the first in nine months while ULA and booster supplier Northrop Grumman worked to resolve problems with nozzles used by strap-on solid-fuel boosters that marred two earlier flights.
The solids appeared to work normally Sunday, burning out and falling away about a minute and 40 seconds after liftoff. The two methane-burning BE-4 engines powering the first stage appeared to fire longer than ULA's pre-launch timeline called for, and the first stage separated later than expected. After separation, the hydrogen-fueled Centaur upper stage took over for a planned 12-minute and 15-second burn; ULA said something went wrong during that Centaur firing but gave no additional details.
The 214-foot-tall Vulcan blasted off from pad 41 at 12:40 p.m. ET atop 3.8 million pounds of thrust from six Northrop Grumman strap-on solid-fuel boosters and two BE-4s. A Friday attempt was scrubbed after problems knocked out a gaseous nitrogen plant that serves multiple launch providers, and a Saturday attempt was delayed by network problems between the Vulcan and ground systems. On Sunday, launch controllers called a hold at the T-minus 20-second mark over an unexplained technical issue, resolved it, and the rocket climbed away at the end of the launch window. It is not yet known whether that problem played any role in the failure.
Sunday's launch was the first of 38 Vulcan flights purchased by Amazon for Leo, designed to compete head-to-head with Elon Musk's Starlink and other space-based internet providers. ULA has already launched eight Leo flights using Atlas 5 rockets. Amazon has also booked 24 Leo launches aboard Blue Origin's New Glenn rocket, 24 aboard the European Ariane 6, and 13 aboard SpaceX's Falcon 9. More than 3,300 Leo satellites will be needed to complete the constellation, and Sunday's flight would have pushed the total number launched to date to 436.
Amazon Leo must now wait for ULA's failure investigation to run its course, and it is also waiting for Jeff Bezos-owned Blue Origin to get New Glenn flying again after a catastrophic on-pad explosion last May. That failure was caused by a problem with an oxygen valve in one of New Glenn's seven BE-4 first-stage engines; the BE-4s used Sunday had been retrofitted with a fix by Blue Origin engineers.
NASA Administrator Jared Isaacman wrote on X: "The team at @NASA is available to assist in all matters related to the investigation and remediation effort. Artemis, Moon Base, and the nation need ULA." ULA CEO Mark Peller told Aviation Week & Space Technology before the flight that the company had "identified three credible causes (of the nozzle issue), and we have taken positive steps to mitigate all of those." The U.S. Space Force had put Vulcan launches of national security payloads on hold pending further analysis.
Sources — how we know this
4 independent sources corroborated this
- PrimaryCBS News
- CorroboratingHacker News Front Page
- CorroboratingLe Figaro
- CorroboratingRBC