SpaceX Files Complaint Against Amazon Over Satellite Launch
SpaceX has lodged a formal complaint with the FCC, claiming that Amazon launched a satellite at an unauthorized altitude, which could increase the risk of collisions in low Earth orbit. The complaint highlights issues surrounding orbital debris management.
The conflict revolves around Amazon’s Project Kuiper, aimed at establishing a broadband satellite network to rival SpaceX’s Starlink, which currently operates over 10,000 satellites. SpaceX insists that Amazon, along with its launch partner Arianespace, sent its satellites to altitudes significantly higher than what was approved in their orbital debris plan.
According to SpaceX’s letter to the FCC, Amazon launched satellites into orbits above 450 kilometers on eight different occasions without the proper updates to their debris mitigation plan or the necessary approvals. In a 2021 filing, Amazon had indicated its satellites would initially launch at about 400 kilometers, later rising to operational altitudes between 590 and 630 kilometers.
The specific incident in question involves an Amazon satellite launched aboard an Ariane 6 rocket on February 12, 2026. SpaceX alleges this satellite was placed at a height that raised significant risks of collisions with existing spacecraft. They reported that their own Starlink satellite had to execute 30 collision avoidance maneuvers shortly after the launch to steer clear of the new Amazon satellite, and they believe the risk from this incident exceeds FCC standards.
Amazon responded to these allegations by asserting that their launches complied with the flexibility allowed in the licensing terms. They stated that they had been open with both the FCC and SpaceX about their launch altitudes and had discussed their safety measures in meetings prior to launching satellites in the contested altitude range. Interestingly, they noted that SpaceX had itself launched an Amazon satellite to 460 kilometers in July 2025 without prior objections.
In their defense, Amazon contended that the root of the problem lies in SpaceX’s recent decision to lower parts of its Starlink constellation to altitudes that overlap with Amazon’s launch range. This change prompted SpaceX to raise concerns, according to Amazon.
On the topic of collision risk assessment, Amazon criticized the approaches cited by SpaceX, referencing that the FCC had previously dismissed those measures during the analysis of their debris plan. Amazon maintains that it adheres to industry-standard risk thresholds, certified by space safety firm SpaceNav.
Amazon acknowledged that modifying the insertion altitude for an Ariane launch involves considerable lead time, with Arianespace requiring several months for final mission analysis when altering orbit parameters. They expressed a commitment to reduce the initial altitude for future launches and mentioned that SpaceX rejected a solution that would have satisfied both parties’ concerns.
This dispute is the latest in a lengthy regulatory back-and-forth between the two companies, each accusing the other of using the FCC process to block satellite launches.
The context for this conflict includes rising worries about space debris proliferation. Recently, SpaceX noted they had lost contact with a Starlink satellite, marking their second such issue since December. Radar tracking firm Leolabs reported that these incidents led to numerous pieces of traceable debris, likely caused by the Starlink satellite itself rather than outside collisions.
While SpaceX hasn’t asked the FCC for specific action against Amazon, they emphasized the urgent need for Amazon to align its launch plans with regulatory requirements before any serious damage occurs. Amazon indicated that they aim to keep working constructively with SpaceX and other operators to resolve current orbital issues.
