United Launch Alliance loses 40 satellites after Vulcan Centaur anomaly

United Launch Alliance's Vulcan Centaur suffered an anomaly 10 minutes into its Nov. 15 flight, and 40 Amazon Leo satellites were lost.

Published
2 Min Read
United Launch Alliance loses 40 satellites after Vulcan Centaur anomaly

United Launch Alliance’s Vulcan Centaur suffered an anomaly about 10 minutes into its Nov. 15 launch from Florida’s Cape Canaveral Space Force Station, and the mission lost 40 Amazon Leo satellites. The rocket had lifted off at 12:40 p.m. ET, or 1740 GMT, on a flight carrying those satellites toward low Earth orbit.

- Advertisement -

The loss leaves one launch with a payload of 40 satellites gone in flight, not a delayed or scrubbed liftoff. For Amazon Leo, the mission was aimed at building out its broadband constellation in low Earth orbit, but the failure cut that effort short before the payload reached its destination.

Nov. 15 liftoff

The Vulcan Centaur climbed from Cape Canaveral Space Force Station on Nov. 15 and flew for roughly 10 minutes before the anomaly occurred. That timing places the failure after liftoff and before the mission could complete the trip to low Earth orbit.

Because the rocket was carrying 40 satellites for Amazon Leo, the failure did not affect a single spacecraft. It wiped out a full launch payload at once, making the loss a large one for the mission rather than a minor in-flight problem.

Florida launch timeline

The sequence is straightforward: liftoff at 12:40 p.m. ET, then an anomaly about 10 minutes later, then loss of the satellites on the same day. The launch time matters because it fixes the point in flight where the problem started, while the payload count shows how much was at stake on a single mission.

- Advertisement -

What caused the anomaly remains unclear. That is the part left open by the available facts, and it is the piece that will determine whether the failure is treated as a one-off event or a broader problem with the flight.

Amazon Leo payload loss

The mission was hauling 40 satellites for the Amazon Leo broadband constellation toward low Earth orbit, so the failure struck a payload intended for a specific deployment goal. With the satellites lost during ascent, the result is not a partial delivery or a delayed insertion into orbit.

The immediate question is what happened 10 minutes into flight. Until that is answered, the only established outcome is that the Vulcan Centaur’s Nov. 15 mission ended with the loss of 40 Amazon Leo satellites.

Advertisement
Share This Article
Investigative news reporter specialising in local government, public policy, and social issues. Two-time Regional Press Award winner.