On Sunday, Nov. 15, a Vulcan rocket operated by United Launch Alliance (ULA), a joint venture between aerospace giants Boeing and Lockheed Martin, malfunctioned approximately 10 minutes after liftoff from Cape Canaveral Space Force Station in Florida, destroying its entire payload.
The disaster marked the first complete mission failure in ULA’s 20-year history and dealt another blow to a launch system the Pentagon has been counting on to provide reliable access to space.
The implications extend well beyond Amazon’s lost satellites. Vulcan is expected to carry a substantial portion of America’s most sensitive national security payloads, including military communications, navigation, surveillance, and intelligence spacecraft.
Its latest failure threatens to leave SpaceX with an even greater share of the country’s military launch business at a time when Washington is seeking to maintain multiple independent launch providers.
For the best of our weekly content!
You are now signed up for our newsletter
Check your email to complete sign up
Rocket fails just 10 minutes into flight
The Vulcan rocket lifted off at approximately 12:40 p.m. Eastern Time, carrying 40 satellites intended for Amazon Leo, the company’s developing satellite internet network designed to compete with SpaceX’s Starlink.
The mission initially appeared to proceed normally, with the rocket’s six solid-fuel boosters separating as expected.
However, approximately 10 minutes into the flight, something went seriously wrong.
In a statement reported by Reuters, ULA confirmed that the rocket had suffered an anomaly and failed to place its payload into orbit.
“Today, we did not meet that standard,” the company acknowledged, referring to its commitment to successful missions.
ULA said it would work with Amazon and other organizations to identify the cause, implement corrective measures, and resume launches.
The precise cause remains unknown.
According to a Nov. 15 investigation by Ars Technica, the rocket’s two BE-4 engines, manufactured by Jeff Bezos’ Blue Origin, appeared to operate for at least 30 seconds longer than expected.
Telemetry-based animations also indicated that the vehicle began spinning shortly after the main engines shut down, forcing its upper stage to make unusual adjustments.
Sources familiar with the flight told Ars Technica that the initial problem appeared to originate in the rocket’s main booster stage. However, investigators have not established whether the engines, propellant systems, or another component caused the malfunction.
The failure is especially troubling because Vulcan had only recently returned to flight following months of investigations into earlier technical problems.
During launches in October 2024 and February 2026, the rocket experienced failures involving its solid rocket booster nozzles.
Both missions nevertheless reached their intended orbits, but the problems prompted additional investigations and temporarily halted Vulcan’s national security launches.
Sunday’s mission was supposed to demonstrate that the rocket was ready to resume a regular launch schedule.
Instead, the failure could result in another lengthy grounding.
Amazon, which has booked 38 Vulcan launches, also faces significant consequences.
The destroyed satellites were part of the company’s effort to build a broadband network of more than 3,200 spacecraft. Amazon has successfully launched nearly 400 satellites but needs substantially more to expand commercial service.
Despite the setback, Amazon expressed confidence in its launch partner.
“There is risk with any launch,” the company said in a statement published on its official mission updates page, adding that it believes ULA will learn from the failure.
The situation is complicated by delays affecting Blue Origin’s New Glenn rocket, another launch vehicle Amazon has contracted to deploy its satellites.
With Vulcan facing a fresh investigation and New Glenn experiencing its own development setbacks, Amazon may have to rely more heavily on other launch providers, including SpaceX, the very company it hopes to challenge in the satellite internet market.
Pentagon faces growing dependence on SpaceX
The military implications may be even more significant.
ULA has long been one of the Pentagon’s principal launch contractors, providing rockets for some of the United States’ most valuable national security satellites.
Vulcan was developed to replace the company’s older Atlas V and Delta IV rockets, preserving an independent American launch capability alongside SpaceX.
In April 2025, the U.S. Space Force announced approximately $13.5 billion in National Security Space Launch contracts involving SpaceX, ULA, and Blue Origin.
Under the arrangement, SpaceX was expected to receive 28 missions worth approximately $5.9 billion, while ULA was allocated 19 missions valued at approximately $5.4 billion. Blue Origin was selected for seven additional missions worth approximately $2.4 billion.
The contracts cover particularly demanding military and intelligence missions, with launches planned over several years.
At the time, Gen. Chance Saltzman, then chief of space operations, emphasized the importance of maintaining a reliable launch infrastructure.
“A robust and resilient space launch architecture is the foundation of both our economic prosperity and our national security,” Saltzman said in the Space Force’s official announcement.
However, Vulcan’s continuing technical problems have complicated that objective.
Following the February booster malfunction, the Space Force suspended further national security launches aboard Vulcan while engineers investigated the incident.
Col. Eric Zarybinsky, the Space Force’s program executive officer for assured access to space, made the military’s position clear at the time.
“Until this anomaly is all over, we will not be launching National Security Space Launch missions on Vulcan,” he told reporters, according to a February report by Air & Space Forces Magazine.
Military satellite launches increasingly shift to SpaceX
The disruption has already forced military officials to rearrange launch schedules.
According to Ars Technica, six national security launches originally assigned to ULA were transferred to SpaceX rockets to expedite the deployment of critical spacecraft.
Some of those missions involved GPS satellites, which provide essential positioning, navigation, and timing services for both military operations and civilian infrastructure.
The Space Force has also reassigned future SpaceX missions to ULA as part of the exchanges, seeking to preserve its contractual balance between providers.
But another prolonged suspension of Vulcan launches could make that balance increasingly difficult to maintain.
SpaceX’s Falcon 9 and Falcon Heavy rockets have become indispensable to the Pentagon’s satellite deployment operations, and further problems at ULA could increase the military’s reliance on Musk’s company.
Blue Origin’s New Glenn is intended to provide a third major option for national security launches, but it has yet to establish the operational record needed to serve as a fully proven alternative.
The consequences could extend to NASA.
The agency has selected a version of ULA’s Centaur upper stage for future missions involving its Space Launch System, although investigators have not established whether Sunday’s failure involved that component.
Following the accident, NASA Administrator Jared Isaacman offered ULA assistance with its investigation.
“Artemis, Moon Base, and the nation need ULA,” Isaacman wrote on X.
For Washington, the concern extends beyond delays and financial losses.
As China expands its military and commercial space capabilities, the United States is seeking to ensure that critical satellites can be launched quickly, reliably, and without excessive dependence on any single contractor.
Vulcan was supposed to help provide that flexibility.
Original article


Comments