Amazon Leo missed its FCC deployment deadline by more than 1,200 satellites — 396 in orbit against ~1,616 required — and rides on with a lesser penalty and its spectrum priority stripped
From the Space digest for 2026-10-16
What happened: GCN reporting published October 16 (~4:20 PM ET) says Amazon's Leo constellation reached just 396 spacecraft by its own July deployment deadline — far short of the 1,616 required (one variant of the report states 1,618) — and the FCC nonetheless let the fleet keep flying, resolving the shortfall with a lesser penalty rather than the full licensing consequence; a second, more detailed piece adds that the waiver fix quietly stripped the constellation's spectrum priority, tilting the competitive terms against it in the race with Starlink.
What's genuinely new: A development of the thread "space — Amazon Leo: Ariane 6 consolidation + India market entry," which has tracked the constellation's slippage — the October 12 "later this year" service-start framing after the missed mid-2026 internal marker, 1,000 satellites produced with roughly 400 in orbit as of October 7–9, and the November 23-at-earliest Ariane 6 VA267 deployment. This is the first on-record regulatory-consequence layer: a number for the deadline miss (396 vs ~1,616), and a named FCC action (keep-flying waiver plus spectrum-priority loss). It lands directly beside the ledgered "initial services by end of 2026" claim, and the deployment-gap arithmetic is the harder version of the same slippage story. Coverage is single-outlet-grade (GCN, two variants); docket documents are not in the window.
Watch: the FCC waiver/docket terms as a primary source; how the spectrum-priority loss affects Leo's competitive standing against Starlink; whether the deployment make-up schedule endangers the year-end service-start target (ledger, review-by January 31, 2027); the Ariane 6 VA267 flight (NET November 23, 2026) against the 1,200-satellite gap.