A United Launch Alliance Vulcan rocket failed on Sunday shortly after launch from Florida while carrying 40 satellites for Amazon’s Leo broadband unit, Reuters reported. ULA said the rocket “suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.”
The 40 lost satellites equal about 10% of the 396 Amazon had launched before Sunday, by our arithmetic from Amazon’s own mission list. Those 396 are about 12% of the 3,232 satellites the FCC requires Amazon Leo to deploy by 30 July 2029.
Business Pill · Vertical Integration
A short explainer on vertical integration, when a company owns more layers of its own supply chain. It teaches the general idea and does not discuss Amazon Leo, ULA or this launch.
The key insight: As we read Amazon’s own numbers, Sunday’s loss is small in satellites and large in launches: the 40 satellites are about 1.3 weeks of the 30-a-week production rate Amazon cited to the FCC, while the flight was the first of 38 contracted on Vulcan, by our arithmetic.
The mission, LV-01 (Leo Vulcan 1), lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station at 12:40 p.m. EST, 17:40 UTC, Spaceflight Now reported. It flew in the VC6L configuration, with six solid rocket boosters, ULA’s mission page says.
“Since the anomaly just occurred, we don’t have any specific data yet to understand what occurred today,” ULA said in its statement. It added: “Today, we did not meet that standard.” Spaceflight Now reported that, according to ULA’s update, something went wrong during the burn of the Centaur upper stage.
ULA said it will “work closely with our customer and other appropriate organizations to find the cause, determine the appropriate corrective action, and return to flight as quickly as possible.” Reuters reported that it was the company’s first mission failure in its two-decade history, and Spaceflight Now that it was only the fifth flight of a Vulcan rocket.
Amazon Leo satellites launched before ULA’s failed LV-01 flight, the 40 lost on it, and the two FCC deployment milestones. The 396 is the sum of Amazon’s own mission list; the shares are our arithmetic.
Reuters posted its report at 20:35 UTC on 15 November: a United Launch Alliance Vulcan rocket failed shortly after launch from Florida with 40 satellites for Amazon’s Leo unit aboard. The piece takes the failure from Reuters and ULA’s own statement, and the satellite counts from Amazon’s mission list and the FCC order.
What Amazon Lost
Amazon calls LV-01 “our largest Leo payload to date” and “the first of 38 contracted Leo missions on Vulcan.” Its mission updates page says Amazon Leo “has launched nearly 400 satellites to date across 14 missions since that initial launch, making it the third-largest constellation in orbit.”
The 14 completed missions on that page add up to 396 satellites, by our arithmetic, so the 40 on LV-01 equal about 10% of everything Amazon had launched. Spaceflight Now reported that the flight would have pushed the total launched to 436.
In its application to the FCC, Amazon Leo cited “scaling manufacturing capabilities to 30 satellites per week”. At that rate, the 40 satellites are about 1.3 weeks of production, by our arithmetic.
The FCC Clock
The FCC’s Space Bureau order of 5 June 2026 states that “Amazon Leo is required to deploy 1,616 satellites by July 30, 2026 and deploy 3,232 satellites by July 30, 2029.” The 3,232 figure is down from 3,236, after an earlier modification.
Amazon had asked in January to push the 50% deadline back by 24 months, or to waive it. The order says: “We grant Amazon Leo’s request for waiver, in part.” It kept the 2029 date, and it said the waiver was supported “particularly due to the delays in launch availability”.
If Amazon misses the final milestone, the order says, its authorization falls to “the total number of satellites that are operational on that date”. The order also required Amazon Leo to forfeit its surety bond if it missed the 50% milestone on 30 July 2026; the 396 launched to date are about 25% of that 1,616 figure, by our arithmetic.
From 396, Amazonneeds 2,836 more satellites in orbit within 988 days, about 20 a week, by our arithmetic. That is about 71 launches the size of LV-01.
Starlink counts from Jonathan McDowell’s statistics page, updated 15 November; the Amazon Leo count is the sum of Amazon’s mission list. The ratio is our arithmetic.
Against Starlink
Jonathan McDowell’s Starlink statistics, updated on 15 November, count 13,122 Starlink satellites launched and 11,215 still in orbit. That is about 33 times the 396 Leo satellites launched, by our arithmetic. Our piece on Starlink’s share of active satellites has the wider count.
Amazon buys its launches from others. Spaceflight Now reported that besides the 38 Vulcan flights, Amazon has booked 24 launches on Blue Origin’s New Glenn, 24 on Ariane 6 and 13 on SpaceX’s Falcon 9. It also reported that New Glenn has not flown since an on-pad explosion in May. Our piece on Starship’s tower catches tracks SpaceX’s own rocket programme.
The Structural Read
As we read the FCC order, the clock that matters now is 30 July 2029: Amazon has 396 satellites launched against 3,232 required, and needs about 20 a week to close the gap, by our arithmetic. The order said the waiver was supported “particularly due to the delays in launch availability”.
As we read the launch list Spaceflight Now reported, Amazon’s constellation rides on four rocket families from three providers besides SpaceX. With Vulcan’s cause not yet known and New Glenn not flying since May, as reported, two of those are now waiting on investigations.
ULA, Vulcan Leo 1 mission status, 15 November 2026
“Every flight generates data, and every flight teaches us something.”
Three Implications
FOR AMAZON LEO The 396 launched to date are about 12% of the 3,232 the FCC requires by 30 July 2029, by our arithmetic; the loss of LV-01 keeps that share where it was.
FOR ULA ULA said it will find the cause and “return to flight as quickly as possible”; it had no specific data yet on what went wrong.
The framework argues: “The job of any operator, investor, or builder is to know which layer they are operating inside and which layer the binding constraint is rotating toward next.”
As we read it, Amazon Leo’s binding constraint has sat in the launch layer, not the satellite factory: the FCC order cites launch delays, and Amazon cites production of 30 satellites a week. The framework predates the failure and does not discuss Amazon Leo or ULA.
What Is Not Established
The cause of the failure is not known; ULA said it had no specific data yet. How long Vulcan will be grounded, and whether the Federal Aviation Administration will lead a mishap investigation, were not stated in the ULA statement or the reports we read. Amazon’s mission page, as we read it at about 20:55 UTC, still showed LV-01 in its pre-launch form.
The value of the lost satellites and any insurance were not given in the sources we read. The 396 count is satellites launched, from Amazon’s list, not satellites working today.
This Week In The AI Supercycle
AI Lost Its Central Banker, the Lab Oligopoly, and the Future of Open Source
This week’s issue: the Nvidia leadership change, read as the AI build-out losing its central banker: who now finances the GPU landlords, backstops the data centres and sponsors open models, and why two labs are becoming the bank.
ULA’s Vulcan failed about 10 minutes into flight on Sunday and lost 40 Amazon Leo satellites, its first mission failure, Reuters reported. The payload equals about 10% of the 396 satellites Amazon had launched, which are about 12% of the 3,232 the FCC requires by 30 July 2029, by our arithmetic.
A note on sourcing. The failure and its timing are from Reuters’ report of 15 November, which we read in full, ULA’s mission status statement and Spaceflight Now’s report. Satellite counts per mission are from Amazon’s Amazon Leo mission updates page, and the deployment milestones, the waiver and Amazon’s cited production rate from the FCC Space Bureau’s Order DA 26-553 of 5 June 2026. Starlink counts are from Jonathan McDowell’s statistics page, updated 15 November.
The 396 total, the shares, the weekly rate and the comparisons are our arithmetic. We did not contact ULA or Amazon for this piece.
Gennaro Cuofano is a CRO and tech executive who has worked in AI since late 2015, starting with bringing NLP, natural-language generation, voice and chatbot products to the marketing industry. His background is in law and finance: he holds a Master's degree in Law and an International MBA with an emphasis on corporate finance (LUISS Business School and the University of San Diego, 2012), and worked as a financial analyst at a real-estate investment firm in San Diego and as an assistant controller. His work focuses on business model strategy, business engineering and, more broadly, structural analysis: how companies make money, read from their own filings. He created FourWeekMBA and leads research there and at The Business Engineer, his newsletter on AI and business strategy, with over 95,000 subscribers and more than 1,000 published analyses. His writing has also appeared on Entrepreneur (for example, How to Digitize a Family Business in Europe) and HackerNoon. Find him on LinkedIn and Substack. See how we source.
