ULA's Vulcan Rocket Fails 10 Minutes After Launch, Destroying 40 Amazon Leo Satellites in Company's First Mission Failure
A United Launch Alliance Vulcan rocket failed about 10 minutes after liftoff from Cape Canaveral on Sunday, Nov. 15, destroying all 40 Amazon Leo internet satellites aboard in the first outright mission failure in ULA's history. The company said the anomaly occurred during the flight and that the cause is under investigation.
A United Launch Alliance Vulcan rocket failed about 10 minutes after liftoff from Florida on Sunday, Nov. 15, destroying all 40 Amazon Leo broadband satellites it was carrying. Spaceflight Now and Reuters reported that it was the first outright mission failure for ULA, the Boeing and Lockheed Martin joint venture formed in 2006.
The rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station at 12:40 p.m. EST, Space.com reported. About 50 minutes later, ULA confirmed the loss in a statement: "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 it did not yet know what went wrong. "Since the anomaly just occurred, we don't have any specific data yet to understand what occurred today," ULA said in an update posted on X, according to Space.com. In a separate statement quoted by Spaceflight Now, 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."
What happened during the flight
The mission, called Vulcan Leo 1, flew with six Northrop Grumman solid rocket boosters strapped to a first stage powered by two methane-burning BE-4 engines built by Blue Origin. Spaceflight Now said the 214-foot rocket climbed away on about 3.8 million pounds of thrust.
According to Spaceflight Now, the boosters appeared to work normally, burning out and falling away about a minute and 40 seconds after liftoff. The outlet reported that the first stage appeared to burn longer than ULA's pre-launch timeline called for, and that it appeared to separate from the hydrogen-fueled Centaur upper stage later than expected. Telemetry-driven animation on the webcast showed the Centaur making unusual orientation adjustments early in its planned 12-minute, 15-second burn, and ULA's update indicated the problem occurred during that Centaur firing. SpaceWireDaily, summarizing reporting by NASASpaceflight, said the anomaly struck during the Centaur V's first burn.
The launch itself followed several delays. Spaceflight Now reported that a Friday attempt was scrubbed after problems knocked out a gaseous nitrogen plant that serves multiple launch providers, and a Saturday attempt was called off because of network problems between the rocket and ground systems. On Sunday, controllers held the countdown at T-minus 20 seconds for an unexplained technical issue before ULA resolved it and launched at the end of the window. Spaceflight Now said it was not yet known whether that issue played any role in the failure.
A return to flight that ended in a loss
Sunday's launch was only the fifth flight of Vulcan, which debuted in January 2024 and is replacing ULA's Atlas V, and its first in nine months, Space.com and Spaceflight Now reported. On Vulcan's second flight in October 2024 and its fourth in February 2026, a nozzle on one of the solid rocket boosters burned through and fell off shortly after liftoff. Both missions still reached their intended orbits.
After the Feb. 12 mission, designated USSF-87, the U.S. Space Force paused national security launches on Vulcan. "Until this anomaly is solved, we will not be launching Vulcan missions," Col. Eric Zarybnisky, the Space Force's portfolio acquisition executive for assured access to space, said at the time, according to Spaceflight Now. Commercial flights were allowed to proceed.
ULA said before the launch that an investigation involving the company, Northrop Grumman, the Space Force and other government agencies had identified three credible causes of the nozzle problem and that changes to the nozzle's design and manufacturing had been built into the boosters for this mission. "Every flight generates data and every flight teaches us something," ULA President and CEO Mark Peller said in a pre-launch statement on the company's website. Spaceflight Now reported that the boosters appeared to perform as expected on Sunday.
The flight also used BE-4 engines that had been retrofitted after Blue Origin's New Glenn rocket, which uses the same engine, was destroyed in an on-pad explosion in May. Spaceflight Now said that failure was traced to an oxygen valve in one of New Glenn's BE-4 engines, and Peller told Aviation Week & Space Technology that Blue Origin had installed a "retrofit kit" on the engines flown on Vulcan Leo 1.
A setback for Amazon Leo
Amazon Leo, formerly known as Project Kuiper, is Amazon's planned low Earth orbit internet constellation, designed to compete with SpaceX's Starlink. Space.com reported that the system will consist of more than 3,200 satellites and that about 400 had reached orbit on 15 earlier launches using Atlas V, SpaceX's Falcon 9 and Arianespace's Ariane 6. Sunday's 40-satellite payload was the largest of any Amazon Leo mission to date, according to ULA.
The launch was the first of 38 Vulcan flights Amazon has purchased, Spaceflight Now reported, alongside 24 launches booked on New Glenn, 24 on Ariane 6 and 13 on Falcon 9. Reuters described the failure as the latest setback for Amazon's deployment schedule. SpaceWireDaily, citing NASASpaceflight, reported that Amazon obtained a Federal Communications Commission extension in June allowing it until July 30, 2029, to complete the constellation.
Amazon Leo will now have to wait for ULA's failure investigation before flying on Vulcan again, Spaceflight Now reported, while also waiting for New Glenn to return to service. ULA said its customers "will have visibility into the investigation process."
NASA Administrator Jared Isaacman offered the agency's help in a post on X. "The team at @NASA is available to assist in all matters related to the investigation and remediation effort," he wrote. "Artemis, Moon Base, and the nation need ULA. We are in your corner and here to help."
The cause of the failure had not been publicly identified as of Monday morning, Nov. 16, and ULA had not announced a timeline for Vulcan's next flight.
Sources
- Spaceflight Now: ULA suffers first outright failure with loss of Vulcan rocket carrying 40 Amazon Leo satellites
- Reuters: Rocket from Boeing-Lockheed firm fails mid-flight, destroys payload of Amazon satellites
- Space.com: Vulcan Centaur rocket fails during return-to-flight launch, 40 Amazon satellites lost
- SpaceNews: Vulcan launch of Amazon Leo satellites fails
- Spaceflight Now: ULA delays to Sunday Vulcan rocket launch of 40 Leo satellites for Amazon
- United Launch Alliance: Vulcan Leo 1: Delivering 40 satellites to space
- SpaceWireDaily: ULA's Vulcan suffers anomaly on return to flight with first Amazon Leo payload
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Wow
0
Sad
0
Angry
0
Comments (0)