Vulcan rocket failure reported, with 40 Amazon Leo satellites said to be lost

Letterjbp said on 16 November that a United Launch Alliance (ULA) Vulcan rocket had failed and 40 Amazon Leo satellites were lost. A separate post from HeyEric described an anomaly on Sunday’s Vulcan flight. The accounts do not establish the exact incident date; the reported satellite loss remains unconfirmed independently. X post by @letterjbp · X post by @HeyEric
HeyEric said early information placed the anomaly in Vulcan’s booster, not its upper stage or strap-on solids. The post said BE-4 engines were due to shut down shortly before five minutes into flight but continued firing for at least 30 seconds longer. It suggested underperformance, without establishing a cause.
The issue matters because Amazon’s Leo constellation needs launches to deploy satellites. HeyEric said 62 of 99 booked Amazon launches were assigned to BE-4-powered rockets: 38 Vulcan and 24 New Glenn flights. Those figures describe bookings, not satellites confirmed lost in this event. It described launch access as a constraint.
HeyEric said ULA’s chief executive had reported retrofitting Sunday’s Vulcan BE-4 engines with a Blue Origin fix. The post also cited a separate New Glenn explosion in May, which it said investigators traced to a faulty BE-4 valve. It offered no evidence that the events shared a cause.
HeyEric said Federal Communications Commission (FCC) deadlines called for half Amazon’s constellation by July 2026 and all of it by July 2029. It said the first deadline was waived in June, with a penalty. The supplied posts do not establish the failure’s cause, how many satellites were lost, or any effect on subsequent launches.
Featured image: Local Headlines Now branded illustration; not a photograph of this incident.