For the first nine minutes, the launch from Cape Canaveral looked routine. ULA’s Vulcan rocket climbed away from Space Launch Complex 41 on November 15, its six solid rocket boosters burned and dropped away on schedule, and the company’s broadcast cheered a long-delayed return to flight. Then, about 10 minutes in, the mission was gone.
Read next on Morning Overview: The FAA wants $2.39 million from a flight school it says flew a Cessna about 280 times with an unapproved part
Vulcan failed to reach orbit, destroying the 40 Amazon Leo broadband satellites it carried. It is the first total mission failure in United Launch Alliance’s history, and days later the cause remains unclear, with the company pointing to weak performance from the rocket’s first stage.
A shortfall in first-stage performance
Vulcan lifted off at 12:40 p.m. Eastern after a string of delays, including a scrub caused by a pump failure at a gaseous nitrogen plant and a hold for oscillations in a liquid hydrogen pressure relief valve, SpacePolicyOnline reported. At 1:30 p.m., ULA said on X that the vehicle “suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.” The company added that it holds itself to the standard of mission success and acknowledged that it had not met that standard on this flight, according to The Next Web.
In a later update, ULA said telemetry and the mission were lost at about 10 minutes into flight, and that early indications pointed to low booster performance just after liftoff, which led to stage separation at too low an altitude and below the minimum velocity needed to reach orbit, Ars Technica reported. The Centaur V upper stage and the solid rocket boosters performed normally.
ULA chief executive Mark Peller said at a Washington Times panel that the company knew there had been “a significant shortfall in booster, or first-stage performance,” Breaking Defense reported. The upper stage was left in “such a low energy stage” that it “couldn’t make up for that performance deficit, and it was unable to reach orbit,” he said.
The loss was total. All 40 satellites, part of Amazon’s planned low-Earth-orbit broadband network, were destroyed, Nature World News and other outlets reported.
Engines or plumbing?
The question investigators face is whether the problem lies in the two BE-4 engines that power Vulcan’s core stage, built by Blue Origin, or in the rocket systems around them. Two independent sources told Ars that preliminary data suggest the problem originated on the launch vehicle side rather than in the engines themselves, possibly in the systems that feed methane and liquid oxygen to the engines. They described the investigation as “incredibly complicated” and in its early stages.
Engineers are examining whether one BE-4 began producing lower thrust shortly after liftoff and never returned to full throttle. High-zoom tracking video appeared to show one engine slightly dimmer than the other after the boosters were jettisoned, nearly two minutes into flight. Ars stressed that the information is preliminary and that no definitive conclusions can be drawn. The Federal Aviation Administration is requiring ULA to conduct a mishap investigation, which ULA is leading.
The answer matters well beyond ULA. Blue Origin’s own New Glenn rocket uses a similar version of the BE-4 and has been grounded since a launch pad explosion in May that was later traced to a main oxygen valve on one engine. Blue Origin hopes to return New Glenn to flight as early as January, and if the Vulcan failure were traced to the engine, that schedule would almost certainly slip.
A blow to the Space Force and Amazon
This was Vulcan’s fifth flight since its debut in January 2024. Two earlier flights had problems with nozzles on the Northrop Grumman solid rocket boosters, but the rocket compensated and reached orbit both times. The Space Force grounded Vulcan for national security missions in late February over the booster issues, and by October 1 it had reassigned six missions to SpaceX, Breaking Defense reported. The Amazon launch was meant to show Vulcan was ready for both commercial and government payloads.
Vulcan is also central to ULA’s future. It replaces the company’s Delta and Atlas V rockets; the final Delta IV flew in 2024, and the six remaining Atlas Vs are committed to Boeing’s Starliner, SpacePolicyOnline noted. ULA has a large backlog of commercial orders, many of them for Amazon Leo, so every month Vulcan spends grounded pushes that backlog further out.
Ars reported that the failure is likely to sideline Vulcan for at least half a year. That would leave SpaceX’s Falcon 9 and Falcon Heavy as the only rockets currently able to carry the most critical national security payloads, deepening what analysts describe as SpaceX’s near monopoly. Amazon, which had more than a dozen Vulcan launches for its Leo constellation planned for 2027, faces delays of its own. Until ULA and Blue Origin can say what went wrong in the first minutes of flight, both companies’ rockets, and the payloads waiting for them, are on hold.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- Melting permafrost is setting off a newly identified kind of catastrophic landslide, scientists say
- Cadillac cut the price of its cheapest EV, which goes up to 317 miles on a charge
- Winter weather advisories cover I-80, I-70 and the Bighorns with up to 15 inches of snow
- Arizona’s governor declared a statewide emergency after Flagstaff logged its wettest Nov. 1 on record