OrbitalHub

Amazon announced on March 23, 2026, that it plans to double the annual launch rate for its Project Kuiper low Earth orbit broadband constellation to more than 20 missions, with the acceleration driven by pressure from a key Federal Communications Commission milestone requiring deployment of half its planned 3,232 first-generation satellites by July 30, 2026.

The company stated it is on pace to complete 11 launches in the first year of deployment since kicking off the campaign in April 2025, with three more missions slated in the coming weeks. As of mid-March, Amazon reported six fully stacked payloads at its satellite processing facility in Florida, representing more than 200 satellites in total, with another payload being prepared in French Guiana.

While 212 Amazon Leo satellites have been deployed so far, hundreds more await launch as the company seeks relief from the FCC deadline. Amazon is asking the regulatory body to extend the deadline by two years or waive it entirely, arguing that launch vehicle availability and other constraints have prevented the originally contemplated deployment pace.

Amazon has booked more than 100 launches for the constellation, including missions with United Launch Alliance, Arianespace, Blue Origin, and SpaceX. The company noted that Ariane 64, New Glenn, and Vulcan are expected to carry increasing numbers of Amazon Leo satellites as vehicle performance improves.

The next major milestone is a ULA Atlas 5 mission on March 29, set to carry 29 Amazon Leo satellites, up from the usual 27, following an engine upgrade enabling its heaviest payload to date. Another Atlas 5 is due in April, along with a second Ariane 64 launch for the constellation. The first Ariane 64 mission last month was Arianespace’s first using the rocket’s more powerful four-booster variant and carried 32 satellites.

According to Amazon, future upgrades will enable Ariane 64 to support even larger payloads. Most launches for the constellation this year are scheduled to use heavy-lift rockets, including Blue Origin’s New Glenn, expected to carry about 48 satellites initially, and ULA’s Vulcan Centaur, with capacity for around 40 from the start.

The company has invested more than $200 million in upgrading ULA facilities at Cape Canaveral to help increase launch cadence and improve turnaround times. These upgrades support the accelerated deployment that Amazon says is necessary to meet its contractual obligations and service commitments.

Amazon can build as many as 30 satellites per week from its facility in Kirkland, Washington, though this rate has slowed to reflect launch vehicle readiness and availability. The manufacturing capacity exists; the challenge lies in getting satellites to orbit on the planned schedule.

The FCC milestone requiring deployment of 1,616 satellites by July 30 reflects the commission’s interest in ensuring that spectrum allocated for broadband constellations is actually used. Waiving or extending the deadline would require Amazon to demonstrate that circumstances beyond its control have prevented compliance, and that the public interest would be served by granting relief.

Building and deploying a constellation of thousands of satellites requires fundamentally different economics than traditional satellite programs. The per-satellite cost must be low enough that total constellation expense remains manageable, while launch costs must be sufficiently controlled to avoid having transportation dominate the budget.

Amazon has pursued vertical integration as a primary strategy, manufacturing satellites in-house at its Kirkland facility rather than purchasing from traditional satellite builders. This approach provides greater control over costs and schedule but requires substantial capital investment in manufacturing infrastructure and expertise.

The launch procurement strategy spreads risk across multiple providers, ensuring that delays from any single vehicle do not halt the entire constellation deployment. However, this also means that Amazon must coordinate across different launch systems, each with its own interfaces, procedures, and performance characteristics.

The FCC deadline applies to the first-generation constellation of 3,232 satellites, but Amazon has indicated plans for additional satellites beyond that initial deployment. The regulatory framework requires operators to demonstrate meaningful deployment within specific timeframes to maintain spectrum rights, creating incentives to launch satellites even before they can be fully utilized in the network.

Satellite life expectancy in LEO typically ranges from three to seven years, depending on orbital altitude and design. This limited operational lifetime means that constellation operators must continuously launch replacement satellites to maintain service levels, adding ongoing launch costs to the initial deployment expense.