Vulcent Centaur Fails, Losing 40 Amazon Leo Satellites

ULA's Vulcan Centaur suffered its first total mission failure Nov. 15, losing 40 Amazon Leo satellites and grounding the rocket indefinitely.

@sharedot

Vulcent Centaur Fails, Losing 40 Amazon Leo Satellites

By @sharedot · · 7 pages

  • Space
  • Ula
  • Vulcan Centaur
  • Amazon Leo
  • Launch Failure

ULA's Vulcan Centaur suffered its first total mission failure Nov. 15, losing 40 Amazon Leo satellites and grounding the rocket indefinitely.

Ten Minutes to Failure: What Happened

United Launch Alliance's Vulcan Centaur lifted off from Cape Canaveral Space Force Station at 12:40 p.m. ET on Nov. 15, carrying 40 satellites for Amazon's Leo broadband constellation on the rocket's first Amazon Leo mission, dubbed Vulcan Leo 1.

ULA confirmed the vehicle 'suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit,' conceding it had no specific data yet to understand what occurred. The rocket and its payloads fell back to Earth minutes after liftoff.

It was the first total mission failure for ULA since Boeing and Lockheed Martin merged their rocket divisions to form the company in 2006.

A Return-to-Flight That Reversed

The failure is a bitter reversal for a rocket that had appeared to fix its previous problem.

Vulcan debuted in January 2024 and had four flights under its belt, but on two of them — October 2024 and February of this year — a solid rocket booster nozzle burned through and fell off about 30 seconds after launch.

The Space Force paused national security launches on Vulcan until ULA addressed it, and the company spent nine months on the ground before Sunday's return to flight.

ULA said in October that design and process improvements to the nozzle had mitigated the issue, and the six solid boosters appeared to perform normally this time — only for a different, more serious failure to appear.

Telemetry Shows an Overburn and a Spin

Multiple sources told Ars Technica the anomaly occurred in the booster stage, not the Centaur V upper stage or the solid rocket boosters.

Per Ars Technica, the two BE-4 main engines made by Blue Origin were supposed to shut down just shy of the five-minute mark but kept firing at least 30 seconds longer — a possible sign the booster underperformed and ran longer to compensate.

ULA's real-time telemetry animation then showed Vulcan start to spin moments after booster engine shutdown, with the Centaur's RL10 engines vectoring thrust in an apparent attempt to recover. ULA ended its broadcast minutes later without discussing the anomaly.

Whether a BE-4 engine was at fault could not immediately be determined.

The Stakes: Amazon, Space Force, and Artemis

Vulcan is contracted to launch roughly half of US military national security missions in the coming years and carries 38 Amazon Vulcan bookings, of which 37 remain.

Amazon's Leo constellation stands at 396 satellites against a planned 3,292 first-generation spacecraft, and the company says it has enough to start initial service by year's end — but more than half its network nodes are in storage awaiting launches.

Ars Technica reports ripple effects could extend further: a BE-4 fault could delay Blue Origin's New Glenn return to flight, which uses a similar engine, while NASA will want to rule out a Centaur V upper stage problem before flying a version of it on the Space Launch System for crewed Artemis lunar missions as soon as 2028.

What Comes Next

The failure is expected to ground Vulcan for an indefinite period while ULA investigates.

The company promised engineers will work to 'find the cause, determine the appropriate corrective action, and return to flight as quickly as possible,' pledging full transparency with customers and visibility into the investigation process.

Amazon struck a measured tone, saying ULA has been a trusted partner and that it expects the company to 'learn from this mission and deliver on their long-term plans for Vulcan.'

Amazon can lean on its 10 booked Falcon 9 missions and an Ariane 6 flight set for later this month, while Space Force officials are likely to shift more national security launches to SpaceX in the interim.

Sources

  1. space.com › Vulcan Centaur rocket fails during return-to-flight launch, 40 Amazon satellites lost
  2. arstechnica.com › Vulcan rocket fails during launch, dealing major blow to SpaceX competitors

More on Space