Amazon Leo lost 40 satellites when United Launch Alliance’s first Vulcan mission for the network failed about 10 minutes after liftoff, but the immediate financial loss is not the main investor question. The larger issue is schedule concentration: Amazon has booked 38 Vulcan launches to carry more than 1,500 first-generation satellites, close to half of its current 3,232-satellite Gen1 network. The failure does not erase the nearly 400 satellites already launched, and an Ariane 6 mission carrying 36 more remains targeted for no earlier than November 23. Yet ULA has not disclosed a cause, corrective action or return-to-flight date, so Amazon’s highest-capacity deployment lane is now uncertain.
Evidence reviewed through November 16, 2026, 11:55 a.m. EST. Mission time and satellite counts are as reported by Amazon, ULA, the FCC and Reuters. AHNIM calculations are identified separately.
Three findings that matter
- Confirmed outcome: LV-01 lifted off at 12:40 p.m. EST on November 15 and failed to place 40 Amazon Leo satellites in orbit. ULA has confirmed the anomaly but has not publicly assigned it to the boosters, BE-4 first-stage engines, Centaur upper stage or another subsystem.
- Scale: 40 satellites equal 10.1% of the 398 satellites Reuters reported Amazon had previously launched, but only 1.24% of the current 3,232-satellite Gen1 constellation. The payload loss is material to deployment cadence, not a 10% reduction in satellites already operating.
- Concentration: Amazon says 38 Vulcan missions—including failed LV-01—will carry more than 1,500 first-generation satellites. Using 3,232 as the denominator, that is at least 46.4% of the network. Diversified providers reduce single-vehicle dependence, but they do not instantly replace Vulcan’s contracted capacity.
What failed—and what has not been established
Amazon’s official mission page now records the payload as lost. ULA said the Vulcan vehicle suffered an anomaly about 10 minutes into flight and failed to deliver the mission to orbit. The planned sequence called for the first stage to shut down and separate at roughly five minutes, followed by a Centaur V burn. That timing narrows the portion of flight under review, but it does not establish a root cause.
This distinction matters because the rocket combines several systems and suppliers. Vulcan’s first stage uses Blue Origin BE-4 engines, the VC6L configuration flew with six Northrop Grumman solid boosters, and this mission introduced a shorter low-Earth-orbit-optimized Centaur V. Public timing alone is not enough to assign fault. Reuters reported that Blue Origin is assisting the investigation, but assistance is not evidence that the BE-4 engines caused the loss.
We therefore treat three claims as unverified: the failed component, how long Vulcan will remain grounded and whether LV-02 can retain the “within weeks” schedule Amazon described before launch. Those are investigation outputs, not facts available at publication.
The 40-satellite loss is a cadence problem before it is an income-statement problem
| Deployment measure | Verified figure | AHNIM interpretation |
|---|---|---|
| Satellites lost on LV-01 | 40 | No addition to the in-orbit network |
| Previously launched | 398 reported by Reuters; Amazon says nearly 400 | Loss equals 10.1% of that prior launch count, but does not remove those satellites |
| Current Gen1 constellation | 3,232 satellites | Lost payload equals 1.24% of the authorized total |
| Vulcan launch contract | 38 launches, more than 1,500 satellites | At least 46.4% of Gen1 tied to this vehicle family |
| Next disclosed mission | 36 satellites on Ariane 6, no earlier than November 23 | Provider diversification remains active |
Amazon has not disclosed the manufacturing cost of the 40 satellites, the mission’s insured amount or a discrete Leo asset write-off. We do not convert the payload count into a dollar loss. For a company of Amazon’s scale, an undisclosed batch cost is unlikely by itself to determine consolidated earnings. The timing effect can be more important: broadband service requires enough satellites in the right orbital planes, ground infrastructure and customer terminals—not merely a cumulative production count.
Amazon said it completed its 1,000th satellite in September and has hundreds of flight-ready spacecraft. That reduces the risk that satellite production is the immediate bottleneck. It also increases the importance of launch throughput: inventory on the ground cannot provide coverage or generate service revenue.
Why Vulcan concentration matters despite a 100-plus-mission manifest
Amazon deliberately spread launches across ULA, Arianespace, Blue Origin and SpaceX. The November 23 Ariane 6 target illustrates the benefit. One provider’s investigation does not stop every deployment. The portfolio also includes more than 100 missions, giving Amazon options over several years.
But diversification is not the same as fungibility. Amazon describes Vulcan as its primary workhorse, with more than 1,500 first-generation satellites across 38 missions. Amazon also funded dedicated integration infrastructure and a mobile launch platform so two Vulcan missions could be prepared at once. Those investments were intended to turn vehicle capacity into cadence. If the investigation delays the next Vulcan flights, other providers would need available rockets, compatible mission profiles and revised integration slots to absorb the gap.
The correct investor test is not whether Amazon has another launch on the calendar. It is whether the combined provider portfolio can still deliver enough satellites, to the required orbital planes, without pushing service availability and cash returns further out. Amazon has not formally withdrawn its stated plan to begin service later in 2026, so a delay is a risk—not yet a confirmed outcome.
The FCC clock did not disappear after the July milestone
The FCC originally authorized 3,236 satellites and later reduced the Gen1 total to 3,232. In its 2026 order, the agency waived certain automatic consequences tied to the July 30, 2026 interim milestone and allowed Amazon to continue working toward a final July 30, 2029 deployment deadline, subject to conditions. The order did not declare the deployment problem solved. It temporarily removed priority status from spectrum associated with satellites not deployed by the interim date and preserved incentives to complete the network.
Using 398 previously launched satellites as a rough starting point, the remaining gap to 3,232 is about 2,834 satellites, and reported launch progress is 12.3%. These are not counts of operating satellites: launch totals can include spacecraft that have deorbited or are not operational, and the FCC’s compliance test has authorization-specific conditions. The arithmetic does show why repeated launch cadence matters more than one batch’s percentage of the full constellation.
What changes in the Amazon investment thesis
For Amazon, LV-01 weakens the near-term execution case for Leo but does not yet justify a company-wide valuation reset. The network’s replacement cost, insurance recovery, revised launch schedule and commercial service impact are not public. The loss also does not change the AWS growth and cash-investment evidence in our Amazon Q3 2026 cash-flow analysis. Leo and AWS are both capital-intensive, but they have different revenue paths and should not be combined into one capex conclusion without disclosure.
The event does strengthen one risk factor: Amazon’s ability to manufacture satellites faster than they can be launched creates schedule and working-capital exposure. The next evidence is operational rather than promotional:
- ULA’s identified root cause, corrective action and return-to-flight approval;
- whether LV-02 receives a revised date or moves behind other Vulcan customers;
- the no-earlier-than-November-23 Ariane 6 mission result and subsequent provider cadence;
- Amazon’s updated service-rollout geography and timing; and
- future filings that quantify satellite losses, insurance or Leo-related cash commitments.
We found no verifiable post-failure AMZN price-target or rating change as of the review cutoff. Existing consensus estimates are not a substitute for an event response, so we do not present them as one. AHNIM is not updating a Base fair value in this article; there is therefore no comparable AHNIM Base-versus-consensus gap to calculate.
Related coverage
Our Amazon TorchNeuron analysis separates technical adoption from AWS profit, while the Starship Flight 15 analysis applies the same rule to launch milestones: one technical success or failure does not by itself prove reusable economics or commercial cadence.
This article is for information and education, not personalized investment advice. We separate company statements, external reporting and AHNIM calculations. See our research responsibility, AI-use and corrections policy.
Sources and original documents
- Amazon Leo mission updates: LV-01 payload loss and LE-04 schedule, updated November 15, 2026
- Amazon Leo LV-01 overview: 38 Vulcan missions, 1,500-plus satellites and dedicated launch infrastructure, November 2026
- United Launch Alliance Vulcan Leo 1 mission page and official anomaly statement, November 15, 2026
- ULA mission profile for the VC6L and LEO-optimized Centaur V, November 10, 2026
- FCC Space Bureau Order DA 26-553: Amazon Leo milestones and conditions, 2026
- Reuters: Vulcan failure, 40-satellite loss, 398 prior launches and investigation context, November 16, 2026

Leave a Reply