Skip to content
Companies

ULA Vulcan Failure Destroys 40 Amazon Leo Satellites, Deepening Amazon's Launch Squeeze

The Boeing and Lockheed Martin joint venture's first launch failure since 2006 hits a Starlink rival with about 390 satellites in service and 38 Vulcan launches booked.

·2 min read

Prefer Nakoda News on Google

United Launch Alliance's Vulcan rocket failed to reach orbit with 40 Amazon Leo satellites on November 15.
United Launch Alliance's Vulcan rocket failed to reach orbit with 40 Amazon Leo satellites on November 15.Photo: Engadget

A United Launch Alliance Vulcan rocket failed about 10 minutes after lifting off from Cape Canaveral, Florida, on Sunday, destroying 40 Amazon Leo internet satellites. It was the first launch failure for ULA, a joint venture of Boeing and Lockheed Martin, since it was formed in 2006, Engadget reported.

"Based on data received by our Launch Director, we confirm that 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 post on X.

The loss sets back Amazon's effort to build a satellite broadband network to rival SpaceX's Starlink at a time when it is already behind schedule. The Federal Communications Commission required Amazon Leo to have 1,600 satellites in orbit by July 31, 2026. The network has about 390 in service. Amazon still planned to have 3,232 satellites in orbit by July 2029, a goal that may now be harder to reach.

Vulcan is central to that plan. Amazon has 38 Vulcan launches booked, following eight successful missions on ULA's older Atlas V, and many of them are now likely to be delayed. Another of its launch providers, Jeff Bezos' Blue Origin, lost a New Glenn rocket when it exploded on the launch pad in May. Amazon has 24 flights booked on that rocket.

ULA said it had no specific data yet on what went wrong. "Every flight generates data, and every flight teaches us something," the company wrote. It said it would work with its customer and other appropriate organisations to find the cause, decide on corrective action and return to flight as quickly as possible, and that customers would have visibility into the investigation.

The launch had already been delayed. A refuelling problem scrubbed an attempt on Friday, and on Sunday controllers called a hold at T-minus 20 seconds for an unspecified technical issue that was resolved within the launch window. The rocket lifted off at 12:40 p.m. Eastern time.

The solid rocket boosters, which caused problems on two earlier Vulcan flights, appeared to work normally. The first-stage methane engines fired longer than ULA's estimated timeline suggested, as Spaceflight Now pointed out. ULA said on its website that the anomaly apparently came during the planned 12.25-minute burn of the hydrogen-powered Centaur upper stage.

Vulcan will now be under review by engineers and could be grounded.

Amazon had already warned in July that "no operator could have predicted that all three core heavy-lift launch programs... would experience repeated, concurrent scheduling slips severe enough to exhaust the buffers Amazon Leo had built in."

By

Nakoda News AI & Tech Desk

AI models, chips, products and research, and what they can and cannot do.

About the desk

Related coverage