For almost two decades, United Launch Alliance had never lost a mission outright. That streak ended on Sunday, November 15.
ULA’s Vulcan rocket lifted off from Cape Canaveral carrying 40 Amazon Leo internet satellites, but something went wrong about 10 minutes into the flight, and the satellites never reached orbit. Here is what we know so far.
What happened
The 214-foot-tall Vulcan launched from Space Launch Complex 41 at 12:40 p.m. EST, according to Spaceflight Now. Six strap-on solid rocket boosters and two methane-burning BE-4 engines powered the rocket off the pad, and the boosters appeared to work normally before falling away.
The trouble came later. After the first stage separated, the hydrogen-fueled Centaur upper stage was supposed to fire for about 12 minutes and 15 seconds. ULA said in a statement that the vehicle “suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.”
Spaceflight Now noted that the first stage appeared to burn longer than planned and that telemetry-driven animation showed the Centaur making unusual orientation adjustments early in its burn. Whether those observations are connected to the failure is not yet known.
ULA’s first outright failure
ULA, a joint venture of Boeing and Lockheed Martin, was formed in 2006. This was the company’s first total mission failure since then. It was also just the fifth flight of Vulcan, the rocket replacing ULA’s Atlas V, and the first in nine months, Spaceflight Now reported. SpaceNews also confirmed the loss of the mission.
“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,” ULA said.
A bumpy countdown
The launch had already been delayed twice. A Friday attempt was scrubbed after a problem knocked out a gaseous nitrogen plant that serves several launch providers, and Saturday’s try was called off because of network issues between the rocket and ground systems. On Sunday, controllers paused the countdown at T-minus 20 seconds for a technical issue, then launched at the end of the window. It is not known whether that issue played any role in the failure.
A big setback for Amazon Leo
Amazon Leo is Amazon’s planned satellite internet network, built to compete with SpaceX’s Starlink. More than 3,300 satellites will be needed to complete it. Sunday’s flight would have raised the total launched so far to 436, according to Spaceflight Now.
This was the first of 38 Vulcan launches Amazon has bought. The company has also booked launches on Blue Origin’s New Glenn, Europe’s Ariane 6 and SpaceX’s Falcon 9. Losing 40 satellites at once, and waiting on an investigation before the next Vulcan flight, will likely slow Amazon’s deployment schedule.
What it means for Vulcan
Vulcan had already faced scrutiny after problems with solid rocket booster nozzles on two earlier flights, which led the U.S. Space Force to pause national security launches on the rocket while it reviewed the issue. Now ULA faces a fresh investigation into a completely different part of the flight.
NASA Administrator Jared Isaacman offered help 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.”
What to watch next
The key questions are what failed during the Centaur burn, how long Vulcan will stay grounded and how Amazon reshuffles its launch plans. Investigations like this usually take weeks to months, and ULA has promised its customers “full transparency” throughout the process.
For a company that built its reputation on reliability, Sunday was a painful reminder that spaceflight is still hard, even for the most experienced teams.
Sources: Spaceflight Now, SpaceNews, Reuters.
Image: ULA's Vulcan VC2S rocket launch (8192438) by U.S. Space Force photo by DeAnna Murano via Wikimedia Commons, Public Domain Mark 1.0