40 Amazon broadband satellites lost after ULA Vulcan suffers first mission failure
6 min read
A United Launch Alliance (ULA) Vulcan rocket carrying 40 Amazon broadband satellites failed minutes after liftoff on 15 November, dealing a fresh blow to a launch programme that had only just resumed operations following a nine-month grounding over solid rocket booster problems.
The rocket lifted off from Cape Canaveral Space Force Station in Florida at 12:40 p.m. EST on its first flight since February.
The mission was intended to demonstrate that Vulcan was ready to resume commercial and US military launches after months of investigation and corrective work. Instead, the rocket suffered an unexplained anomaly and failed to deliver its satellites to orbit.

ULA has not identified the cause of the failure or established whether it was connected to the booster problems that had kept Vulcan grounded.
“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,” ULA said in a statement.
“Since the anomaly just occurred, we don’t have any specific data yet to understand what occurred today.”
The company acknowledged that the mission had fallen short of its standards.
“ULA exists to provide assured access to space for our nation and for the customers who depend on us. That purpose is why we take on some of the hardest missions in spaceflight, and why we hold ourselves to the standard of mission success. Today, we did not meet that standard,” it said.
“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.”
The failure marks the first complete mission loss for ULA, the company established by Boeing and Lockheed Martin in 2006.
Vulcan’s troubled return to flight
The rocket last flew on 12 February, carrying a national security payload for the US Space Force. Although it successfully delivered the spacecraft to its intended orbit, one of its four solid rocket boosters malfunctioned shortly after liftoff.

A similar problem involving a booster nozzle had occurred during Vulcan’s second flight in October 2024.
The repeated anomalies prompted ULA and booster manufacturer Northrop Grumman to conduct an extensive investigation, including engineering analysis, component examinations and ground testing.
The nine-month stand-down was intended to give engineers time to understand the problems and introduce corrective measures before resuming launches.
Speaking ahead of the mission, ULA president and chief executive Mark Peller acknowledged the risks associated with bringing a new launch vehicle into regular service.
“As with any new rocket, there are risks associated with every launch, and particularly as we are early in this phase of introduction of Vulcan to the market and working to a regular operational tempo. Every flight generates data and every flight teaches us something,” he said.
“And we’re going to look to this flight to get some more useful data in a flight environment on the effectiveness of the corrective action that we’ve implemented.”
Those remarks, carried in AGN’s prelaunch report on 13 November, have acquired added significance following Sunday’s failure.
Peller had also pointed to Vulcan’s ability to complete its first four missions despite the earlier booster problems.
“During our first four Vulcan missions, the robustness of Vulcan served us well. It flew through some difficult environments associated with the SRB anomalies and successfully completed all of those missions, giving the spacecraft both a smooth ride and precise, bullseye orbital injections,” he said.
Sunday’s mission was the first in which Vulcan failed to deliver its payload.
ULA has not established whether the latest anomaly was connected to the earlier booster problems.
Vulcan’s most powerful configuration
The mission was also significant because it marked the first use of Vulcan’s six-booster configuration, designated VC6L.
The rocket carried six Northrop Grumman GEM 63XL solid rocket boosters, the maximum number Vulcan can accommodate. These provide additional thrust during the initial climb, allowing the vehicle to carry heavier payloads.

Two BE-4 engines developed by Blue Origin powered the rocket’s central booster. They burn liquefied natural gas, primarily methane, and liquid oxygen.
Above the main booster was the Centaur V upper stage, fitted with two RL10 engines using liquid hydrogen and liquid oxygen.
The mission used a Centaur configuration optimised for low Earth orbit, together with a longer payload fairing to accommodate Amazon’s satellites.
The 40 spacecraft weighed more than 22,700kg, making the mission the heaviest payload ULA had attempted to launch.
Amazon had planned to use Vulcan’s greater lifting capacity to send larger batches of satellites into orbit, reducing the number of launches needed to build its broadband network.
Amazon’s broadband plans suffer setback
The failed mission was the first of 38 Vulcan launches contracted by Amazon to deploy its Leo satellite constellation, previously known as Project Kuiper.

The network is designed to provide high-speed internet access to homes, businesses and communities, particularly in areas where conventional broadband services are limited.
Amazon plans an initial constellation of more than 3,000 satellites operating in coordinated low Earth orbits.
The company has contracted launches with ULA, Europe’s Arianespace, Blue Origin and SpaceX.
ULA had already completed eight successful Amazon satellite deployment missions using its older Atlas V rocket.
Amazon said in September that it had completed production of its 1,000th satellite and had hundreds of flight-ready spacecraft awaiting launch.
Getting those satellites into orbit remains a major challenge.
In AGN’s prelaunch report, Melissa Wuerl, director of launch systems for Amazon Leo, explained why the company was relying heavily on Vulcan.
“Larger rockets and more frequent launches are critical to scaling our constellation and getting service to customers, and the Vulcan program is designed to deliver on both dimensions,” she said.
“Vulcan will launch close to half our first-generation constellation, making it our primary workhorse over the next several years, and we’re looking forward to kicking off the sprint with our partners at ULA.”
The loss of 40 satellites represents a setback to that deployment programme. Amazon has not announced how the failure will affect its launch schedule.
Questions over ULA’s next missions
ULA had been preparing to increase its launch frequency after Vulcan’s return to service.
Amazon has invested in dedicated launch infrastructure at Cape Canaveral, including a new Vertical Integration Facility and mobile launch platform.

The facilities allow ULA to prepare two Vulcan rockets simultaneously, reducing the time required between missions.
A second Amazon Vulcan mission, LV-02, was already undergoing preparations and had been expected to follow within weeks if Sunday’s flight succeeded.
That timetable is now uncertain.
The failure also has implications for the US Space Force, which is relying on Vulcan to launch national security satellites.
Vulcan is intended to become ULA’s principal launch vehicle as it replaces the company’s older Atlas V and retired Delta IV rockets.
Delta IV flew for the final time in April 2024, while Atlas V remains operational but is no longer in production.
The Space Force had been awaiting the outcome of Vulcan’s return-to-flight mission before proceeding with further launches.
The company has not announced when Vulcan will fly again.














