Rocket Failure Destroys 40 Amazon Satellites in Serious Blow to Internet Constellation

Rocket Failure Destroys 40 Amazon Satellites in Serious Blow to Internet Constellation

2026-11-18 companies

Cape Canaveral, Wednesday, 18 November 2026.
A booster malfunction during a Sunday launch destroyed 40 Amazon broadband satellites, threatening deployment timelines and tightening pressure against regulatory deadlines and market rival Starlink.

Mission Failure Details and Immediate Aftermath

On Sunday, 15 November 2026, a United Launch Alliance (ULA) Vulcan rocket suffered a catastrophic failure during its ascent, resulting in the total loss of 40 Amazon (NASDAQ: AMZN) Project Kuiper broadband satellites intended for low Earth orbit (LEO). Preliminary telemetry data indicated that the rocket’s first stage underperformed shortly after liftoff from Cape Canaveral Space Launch Complex 41 at 12:40 p.m. Eastern Time, failing to achieve the necessary altitude and velocity for orbital insertion [1][2][5]. The mission anomaly occurred approximately 10 minutes into flight, with the Centaur upper stage—powered by two L3Harris RL10 engines—failing to recover from the low-energy state imparted by the deficient first stage performance [2][3]. ULA confirmed in a statement that while the solid rocket boosters (SRBs) and upper stage operated nominally, the performance shortfall in the booster phase was irrecoverable [2][3].

Investigation and Regulatory Oversight

The Federal Aviation Administration (FAA) has taken the lead in overseeing ULA’s mishap investigation, as mandated by federal regulations governing commercial launch failures [1][4]. ULA has committed to a rigorous, data-driven investigation to determine the root cause of the booster performance shortfall, with findings subject to FAA approval before any corrective actions are implemented [1][2][4]. ULA CEO Mark Peller acknowledged the severity of the issue, stating that the booster left the Centaur upper stage in ‘such a low-energy state in terms of altitude and velocity that Centaur wasn’t designed for and couldn’t make up for that performance deficit’ [5]. Peller also noted that modifications to the SRB nozzles—implemented after a prior Vulcan flight experienced nozzle issues—performed as intended during this launch [5].

Broader Implications for Project Kuiper and Amazon’s Strategic Timelines

The loss of 40 satellites represents a significant setback for Amazon’s Project Kuiper, which aims to deploy a 3,232-satellite LEO broadband constellation with a final operational deadline of 30 July 2029 [1][GPT]. The failure comes as Amazon races to meet regulatory milestones, having previously secured an extension from the Federal Communications Commission (FCC) after missing the initial 30 July 2026 deadline for deploying 1,616 operational satellites [1][GPT]. Amazon’s Project Kuiper has launched 396 satellites across 14 successful missions between April and July 2025, primarily aboard Atlas V rockets, but has not yet initiated commercial internet service [1][GPT]. The next scheduled Project Kuiper launch—a European Space Agency Ariane 6 mission carrying 36 satellites—is targeted for no earlier than 23 November 2026, pending further reviews [1][alert! ‘deadline subject to change’].

Competitive Landscape and Industry Repercussions

The Vulcan failure intensifies pressure on Amazon’s Project Kuiper to accelerate deployment, particularly as it faces stiff competition from SpaceX’s Starlink, which has already deployed thousands of satellites and begun commercial service in multiple regions [GPT]. The loss also raises broader questions about the reliability of launch manifest timelines and insurance risk profiles across the aerospace supply chain, particularly for satellite broadband constellations reliant on frequent, high-volume deployments [GPT]. ULA’s Vulcan rocket, intended to become a cornerstone of U.S. space access, now faces heightened scrutiny over its operational readiness and the integrity of its first-stage propulsion systems [5][GPT]. While Blue Origin’s BE-4 engines—used in the Vulcan’s first stage—were retrofitted with fixes prior to this launch, the exact role of the engines in the performance shortfall remains under investigation [1][5].

Sources


Commercial space Satellite constellation