Amazon Leo Misses Its FCC Half-Deployment Deadline, and Every Satellite It Launches Next Flies at Demoted Spectrum Priority
Amazon reaches its 30 July 2026 FCC milestone with about 331 of the roughly 1,616 satellites it needed in orbit, half of its 3,232-satellite first-generation Leo system. Under the conditional waiver the Space Bureau granted on 5 June, every Leo satellite Amazon launches after the deadline operates on a non-interference basis and yields to rivals on shared frequencies until Amazon reaches 50 percent or March 2028. Amazon also forfeits its surety bond, and its full-deployment date resets to 2029.
Watch · The story in brief
Amazon reaches its 30 July 2026 FCC milestone roughly 1,300 satellites short, so every Leo satellite it launches next flies at demoted, non-interference spectrum priority behind rivals until it certifies half deployment or March 2028 — with a look at how the FCC's processing rounds and 1990s paper-satellite rules reordered the queue before.
What happened
Amazon's first-generation Leo system, the low-Earth-orbit broadband network it renamed from Project Kuiper, faces a 30 July 2026 FCC milestone to have half of its 3,232 authorized satellites in orbit, about 1,616 spacecraft. As the date arrives Amazon has roughly 331 up. The company will not close a gap of more than a thousand satellites in a single launch cycle, so the milestone lapses.
On 5 June 2026 the FCC Space Bureau granted a conditional waiver, order DA-26-553, that avoided an outright forfeiture and reset Amazon's full-deployment deadline to 30 July 2029. The relief carries a price written into the spectrum. Every Leo satellite Amazon launches after 30 July 2026 operates on a non-interference basis, meaning it must accept interference from and avoid causing interference to other operators in the shared band, until Amazon reaches 50-percent deployment or 30 March 2028, whichever comes first. Amazon also forfeits the surety bond it posted against the original milestone.
Why it matters for dispute formation
The friction is coordination priority, the order in which two operators sharing a frequency must yield when their beams overlap. A satellite flying at non-interference status has to protect its neighbors and cannot demand protection in return. For a roughly twenty-month window, Amazon's newest satellites sit at the back of that queue in the same Ku- and Ka-band plan where Starlink, OneWeb, and Telesat operate, which hands a co-frequency rival room to lock in favorable coordination terms it would not otherwise hold.
The waiver also builds in a contest over facts. Amazon can shorten the penalty by certifying that it has satellites built and rockets booked to reach half deployment, a showing a competitor can examine and challenge at the Commission. So the dispute forms in two places at once: at the FCC, over whether Amazon has met the condition to restore its priority, and in the field, over which operator must suspend or reshape a transmission when signals collide while Amazon flies secondary.
Who's exposed
Exposed as the operator that reaches the 50-percent milestone roughly 1,285 satellites short, so under the June waiver every Leo satellite it launches after 30 July drops to non-interference status, yields to co-frequency rivals, and forfeits the surety bond posted against the deadline. Amazon carries that demoted priority until it reaches half deployment or March 2028, with the full-system date pushed to 2029.
Exposed to the upside of a rival flying secondary: for the penalty window Starlink can press coordination terms in the shared Ku- and Ka-bands while Amazon's newest satellites must protect it, though Amazon regains equal footing the moment it certifies half deployment.
Exposed as co-frequency NGSO operators whose own coordination posture moves with Amazon's status, since the order that demotes Amazon reshuffles who must yield to whom across the same Ku- and Ka-band plan.
Exposed as Amazon's launch providers, because the penalty ends through flight, not paperwork. Their cadence is the variable that controls how long Amazon carries demoted priority, and any slip extends the window a competitor benefits from.
The historical parallel · The FCC's NGSO processing-round priority framework (IB Docket 16-408) and the 1990s paper-satellite milestone enforcement
The Commission has long used deployment milestones and processing-round order to rank who yields to whom. In its 2017 non-geostationary framework, applicants who filed in a later round took priority behind first-round grantees, the same back-of-the-queue posture Amazon's post-deadline satellites now occupy. Earlier, in the 1990s, the FCC pressed milestone enforcement against paper satellites that held slots without building, forcing ICO Global and others to deploy or cede rights. The through-line is that milestones are not paperwork, they set coordination priority, and a missed one moves a real operator down the queue while its rivals coordinate around it.
What to watch
- Amazon's launch cadence across ULA, Blue Origin, and Arianespace, since only flight, not a filing, ends the non-interference window.
- Any Amazon certification that it has satellites built and rockets booked to reach half deployment early, and whether a competitor challenges that showing at the FCC.
- Coordination filings from Starlink, OneWeb, or Telesat that press advantage in the shared Ku- and Ka-bands while Amazon flies secondary.
- Whether the FCC treats the surety-bond forfeiture as the ceiling on consequences or opens a broader review of the Leo authorization.
Sources
See the disputes forming before the market does.
Signal Watch tracks the developments. The monthly Intelligence Brief synthesizes all four signals into the disputes most likely to crystallize next — free.
Get the Intelligence BriefFor general information only; not legal advice, and no attorney–client relationship is formed through this article. Company names appear because the companies are exposed to a public development — not as a statement of wrongdoing or a predicted outcome. Figures are as reported by the linked sources.