The Vulcan blasted off from pad 41 at Cape Canaveral Space Force Station at 12:40 p.m. ET and ran into trouble 10 minutes into the climb to space. ULA confirmed the anomaly about 50 minutes after launch, saying the vehicle had failed to deliver the Amazon mission to orbit, and pledged to work with its customer and other organizations to find the cause and return to flight as quickly as possible. It was only the fifth flight of a Vulcan and the first in nine months, after ULA and booster supplier Northrop Grumman worked to resolve nozzle problems on the strap-on solids. It also marks the first outright rocket failure for ULA since the Boeing-Lockheed Martin partnership was created in 2006.
The 214-foot rocket thundered away on 3.8 million pounds of thrust from six Northrop Grumman strap-on solid boosters and two methane-burning BE-4 engines. The solids burned out and fell away about a minute and 40 seconds after liftoff, but the first stage appeared to burn longer than ULA's pre-launch timeline called for and separated from the hydrogen-fueled Centaur upper stage later than expected. Telemetry-driven animation showed the Centaur making unusual orientation adjustments early in its burn, and ULA later said something went wrong during the Centaur's planned 12-minute, 15-second firing without offering details. Launch commentators never mentioned a problem, and the broadcast ended without confirming the burn ran its full duration.
The countdown was messy well before that. A Friday attempt was scrubbed after problems knocked out a gaseous nitrogen plant serving multiple launch providers, and Saturday brought another delay over network trouble between the Vulcan and ground systems. On Sunday, controllers called a hold at T-minus 20 seconds over an unexplained technical issue with the rocket, resolved it and launched at the very end of the window. Whether that hiccup played any role in the failure isn't known.
Sunday's flight was the first of 38 Vulcan launches Amazon has bought for Leo, its answer to Elon Musk's Starlink. ULA has already flown eight Leo missions on Atlas 5 rockets, and Amazon has also booked 24 launches on Blue Origin's New Glenn, 24 on Europe's Ariane 6 and 13 on SpaceX's Falcon 9. More than 3,300 satellites are needed to complete the constellation, and the lost payload would have pushed the total launched to date to 436. Amazon is also waiting on New Glenn, grounded since a catastrophic on-pad explosion last May traced to an oxygen valve in one of its seven BE-4 first-stage engines.
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, adding that Artemis, Moon Base and the nation need ULA and that the agency is in its corner.
ULA CEO Mark Peller told Aviation Week before the flight that the company had identified three credible causes of the strap-on nozzle issue that marred two earlier Vulcan flights, one in 2024 and one this past February, and had taken steps to mitigate all of them. The boosters worked normally Sunday. Peller also said Blue Origin developed a design improvement for the BE-4 valve problem and retrofitted the engines installed on the Vulcan Leo 1 rocket, and is working through ULA's engine inventory. The U.S. Space Force had already put Vulcan launches of national security payloads on hold pending further analysis.