Amazon asks FCC for time extension for launching its Leo constellation
Amazon yesterday submitted a request to the Federal Communications Commission to extend the July deadline on its license for its Leo internet satellite constellation, which presently requires it to have 1,616 satellites in orbit by that date.
At present Amazon has 181 satellites in orbit, all launched in the last ten months. At that pace there is no chance the company can meet its FCC requirement. From its FCC submission:
While Amazon Leo will meet the deadline for full deployment of its constellation established by its license and the Commission’s rules, launch delays will cause it to fall short of the interim milestone requirement to deploy half of its originally authorized constellation by July 30, 2026. The Commission’s rules provide for extension of such milestones where, as here, delay arises from unforeseeable circumstances beyond an operator’s control or overriding public interest considerations favor an extension.
Because it meets both criteria, Amazon Leo respectfully requests a 24-month extension of its 50% milestone to July 30, 2028, or alternatively, a waiver of this interim requirement.
In its submission Amazon claims the delay is entirely the fault of the rocket companies it was relying on to launch the satellites, but that is a bogus claim. It initially choose to depend almost entirely on three new rockets (Blue Origin’s New Glenn, ULA’s Vulcan, and Arianespace’s Ariane-6), all of which had not launched and were still under development. To expect these to launch on time was absurd.
Furthermore, its ULA contract also called for launches using company’s already operational Atlas-5 rocket, which Amazon claims were delayed because of “unexpected anomalies and delays caused by issues with its vehicle fairings and solid rocket boosters.” I don’t buy it, and suspect the real cause was that Amazon was unable to produce the satellites on time.
Faced with these delays and a stockholder lawsuit, Amazon subsequently signed SpaceX to do three launches, which that company did quickly, in less than four months. If Amazon had truly wanted to get its Leo satellites in orbit on time, it would have given SpaceX more launches and gotten it done.
Nonetheless, it is likely the FCC will agree to Amazon’s extension request. The company has now shown it is committed to the process and intends to get its constellation in orbit. It is not sitting on its license doing nothing. I would not be surprised however if the FCC imposes some new requirements in an effort to force Amazon to launch more satellites more quickly.
Amazon yesterday submitted a request to the Federal Communications Commission to extend the July deadline on its license for its Leo internet satellite constellation, which presently requires it to have 1,616 satellites in orbit by that date.
At present Amazon has 181 satellites in orbit, all launched in the last ten months. At that pace there is no chance the company can meet its FCC requirement. From its FCC submission:
While Amazon Leo will meet the deadline for full deployment of its constellation established by its license and the Commission’s rules, launch delays will cause it to fall short of the interim milestone requirement to deploy half of its originally authorized constellation by July 30, 2026. The Commission’s rules provide for extension of such milestones where, as here, delay arises from unforeseeable circumstances beyond an operator’s control or overriding public interest considerations favor an extension.
Because it meets both criteria, Amazon Leo respectfully requests a 24-month extension of its 50% milestone to July 30, 2028, or alternatively, a waiver of this interim requirement.
In its submission Amazon claims the delay is entirely the fault of the rocket companies it was relying on to launch the satellites, but that is a bogus claim. It initially choose to depend almost entirely on three new rockets (Blue Origin’s New Glenn, ULA’s Vulcan, and Arianespace’s Ariane-6), all of which had not launched and were still under development. To expect these to launch on time was absurd.
Furthermore, its ULA contract also called for launches using company’s already operational Atlas-5 rocket, which Amazon claims were delayed because of “unexpected anomalies and delays caused by issues with its vehicle fairings and solid rocket boosters.” I don’t buy it, and suspect the real cause was that Amazon was unable to produce the satellites on time.
Faced with these delays and a stockholder lawsuit, Amazon subsequently signed SpaceX to do three launches, which that company did quickly, in less than four months. If Amazon had truly wanted to get its Leo satellites in orbit on time, it would have given SpaceX more launches and gotten it done.
Nonetheless, it is likely the FCC will agree to Amazon’s extension request. The company has now shown it is committed to the process and intends to get its constellation in orbit. It is not sitting on its license doing nothing. I would not be surprised however if the FCC imposes some new requirements in an effort to force Amazon to launch more satellites more quickly.














