ULA's Vulcan Rocket Fails Mid-Flight, Destroying Amazon Satellite Payload in Setback for New Flagship

Ten minutes into the flight, the rocket failed to reach orbit.
ULA confirmed Vulcan's anomaly after launch from Florida, with the Amazon satellites lost.
Mark

A rocket failed ten minutes after liftoff. Why does that timing matter?

Mimi

Ten minutes in, the rocket is well into its climb and close to the point of reaching orbit. ULA's statement says it failed to deliver the Amazon mission to orbit, so the satellites never got there and were lost.

Mark

What was the rocket carrying?

Mimi

Satellites for Amazon's internet constellation. Vulcan is ULA's new flagship, and this was meant to be part of a regular run of Amazon launches.

Luke

Do we know what went wrong?

Mimi

No. ULA says it had no specific data yet to explain what happened.

Luke

So anomaly is doing a lot of work in that statement.

Mimi

It is. It confirms that something failed and says nothing about the cause. Any explanation right now would be guesswork.

Mark

What are the stakes for ULA?

Mimi

The company is two decades old, and Vulcan is its new flagship. The failure comes just as it was trying to settle into a steady launch schedule for Amazon.

Luke

Has anyone said how long Vulcan will be grounded?

Mimi

No. The source doesn't give a timeline or say how many satellites were aboard. Those are open questions until the investigation produces findings.

Mark

So what should we watch for?

Mimi

ULA's analysis of the flight data, a stated cause, and any word on when Vulcan flies again.

  • A Vulcan rocket lost its way roughly ten minutes after liftoff from Florida, and the Amazon satellites it carried never reached orbit.
  • ULA has labeled the event only an anomaly, offering no cause and no named system, which leaves the company and its customer in open uncertainty.
  • Engineers are now combing through flight data to find out what went wrong, and no timetable for answers has been given.
  • Amazon's Kuiper constellation depends on a steady rhythm of launches, and that rhythm now hangs on how quickly Vulcan can be cleared to fly again.

On a Florida morning that began like any other launch day, a rocket that its makers hoped would anchor their future lifted from Space Launch Complex 41 and fell short of its purpose about ten minutes later. United Launch Alliance, a company already two decades old, had staked much on the Vulcan vehicle as its new flagship, and on the promise it held for Amazon's satellite internet network. The satellites aboard were lost, and the reason has not yet been found, leaving a gap between hope and orbit that only careful study of the flight data can begin to close.

A United Launch Alliance Vulcan rocket lifted off from Space Launch Complex 41 in Florida, carrying a batch of satellites meant for Amazon's internet constellation. About ten minutes into the flight, it failed, and the satellites never reached orbit. The company, which has been building toward this moment for two decades, confirmed the anomaly in a short statement but could not yet say what had happened.

ULA described the event carefully. Every flight generates data and teaches something, the company said, but this one had only just occurred, and no specific information yet explained the failure. No cause was named, and no system was singled out.

The stakes are considerable. Vulcan was meant to be the company's new flagship and the engine of a regular launch schedule for Amazon's Kuiper project. A constellation needs repeated launches, and a rocket that cannot reliably reach orbit cannot supply them. How soon Vulcan flies again will depend on what the investigation uncovers.

The next step is the analysis of flight data. Until a cause is found, the length of any pause and the pace of Amazon's deployment remain open questions.

A United Launch Alliance Vulcan rocket lifted off from Space Launch Complex 41 in Florida and, about ten minutes into its flight, failed. The rocket did not deliver its cargo, a batch of satellites for Amazon's internet constellation, to orbit. The cause was not immediately clear.

ULA confirmed the failure in a statement. Based on data received by the company's Launch Director, it said, the Vulcan vehicle suffered an anomaly ten minutes into the flight and failed to deliver the Amazon mission to orbit. The company used the word anomaly and offered no further description of what went wrong.

The statement also made clear how little the company knew at that point. Every flight generates data and teaches something, ULA said, but because the anomaly had only just occurred, it had no specific data yet to explain what happened. It did not name a suspected cause or say which system was involved.

The Amazon satellites aboard were lost. The failure is a significant setback for Vulcan, which ULA has positioned as its new flagship rocket. The company is two decades old, and Vulcan was meant to carry it into a regular cadence of launches for Amazon's growing satellite internet constellation, the project known as Kuiper.

That cadence is what the failure puts in question. A constellation depends on repeated launches, and a rocket that cannot reliably reach orbit cannot supply them. How quickly Vulcan flies again, and how many Amazon missions it can take on, will depend on what investigators find.

The report comes from Joey Roulette, a Reuters space reporter who covers the business and politics of the global space industry. He was part of a team that won the 2024 Pulitzer Prize in national reporting for Reuters' coverage of Elon Musk's business empire.

The next step is the analysis of flight data ULA says it will carry out. Until the company identifies a cause, the length of any pause in Vulcan launches, and the pace of Amazon's deployment plans, remain unanswered.

Every flight generates data, and every flight teaches us something. Since the anomaly just occurred, we don't have any specific data yet to understand what occurred today.
— United Launch Alliance statement
Quieres la nota completa? Lee el original en Reuters ↗
Contáctanos FAQ