Vulcan Rocket Failure Stalls Amazon Satellite Expansion
Original source
Vulcan rocket fails during launch, dealing major blow to SpaceX competitors
Ars Technica →United Launch Alliance’s Vulcan rocket failed Sunday during launch from Cape Canaveral, taking 40 Amazon Leo broadband satellites with it. The anomaly occurred roughly ten minutes into flight within the booster stage, where the dual BE-4 engines—each producing over half a million pounds of thrust—appear to have overburned by at least 30 seconds beyond their scheduled shutdown time. After engine cutoff, the rocket began spinning through the upper stage separation that followed. This marks ULA’s first total mission failure since the company formed in 2006.
The failure grounds Vulcan indefinitely while investigators work to understand what occurred. It directly disrupts Amazon’s plan to build a competing broadband satellite network against SpaceX’s Starlink. This was supposed to be the first of 38 Vulcan launches Amazon booked with ULA. The Amazon Leo constellation currently has 396 satellites deployed, though the full network requires 3,292 first-generation spacecraft. Amazon has contingency launch capacity through Arianespace, which holds 24 booked launches with three already completed and another scheduled this month, plus ten additional missions with SpaceX’s Falcon 9.
The incident extends beyond Amazon’s immediate concerns. Vulcan holds contracts to launch roughly half of the US military’s national security space missions. If investigators find the BE-4 engine caused the failure, delays could compound: Blue Origin’s New Glenn also uses BE-4 engines and already suffered a ground test explosion in May traced to a faulty valve in the same engine type. That incident knocked Blue Origin’s launch pad offline through at least year-end.
Read the full article
Continue reading at Ars Technica →This is an AI-generated summary. Read the original for the full story.