SpaceX and Amazon are fighting over who gets to fly where in low Earth orbit, and the Federal Communications Commission is caught in the middle of what amounts to a high-stakes real estate dispute in the crowded orbital environment.
In an early April letter to the FCC, SpaceX accused Amazon of violating the orbital debris mitigation plan attached to its broadband satellite license by deploying satellites at higher altitudes than authorized. Amazon fired back in its own FCC filing, denying any rule violation and pointing out that SpaceX only raised the alarm after moving its own Starlink constellation into the very altitudes where Amazon’s satellites were being inserted.
The technical details matter, but the institutional dynamics matter more. This is a fight between the world’s dominant satellite internet provider and its most ambitious competitor, waged through FCC filings and framed in the language of space safety. Both companies have financial and strategic reasons to want the other slowed down.
The Altitude Problem
Amazon’s FCC license states that its satellites will be launched into an initial deployment orbit around 400 kilometers before being raised to operational altitudes between 590 and 630 kilometers. SpaceX’s complaint, as reported by SpaceNews, alleges that Amazon has instead been inserting satellites at altitudes ranging from 460 to 490 kilometers on multiple launches.
The specific wording in Amazon’s license is doing enormous legal work in this dispute. SpaceX reads it narrowly: 400 kilometers means 400 kilometers, give or take a small margin. Amazon reads it broadly: the phrase grants flexibility to meet mission requirements, and nowhere does the license specify a rigid ceiling on insertion altitude.
Both readings have some logic. But the gap between 400 and 490 kilometers is not trivial when another company has recently parked thousands of satellites in the 475-to-485-kilometer band.
Collision Avoidance Maneuvers
SpaceX’s letter focused on a February Ariane 6 launch that carried Amazon Leo satellites to higher insertion altitudes. According to SpaceX, the deployment triggered collision avoidance maneuvers by Starlink satellites. SpaceX characterized the deployments as creating unmitigable collision risks with dozens of operational spacecraft.
SpaceX said the problem had occurred on previous launches but that the February mission brought it to a crisis point. The company also alleged that Amazon failed to update its debris mitigation plan or share predicted maneuver plans for the newly deployed satellites, making coordination impossible.
SpaceX wrote in the filing that Amazon must ensure its launch plans comply with its authorization before creating irreparable harm.
The collision avoidance maneuvers from a single launch represent a striking operational burden. Each maneuver costs propellant and satellite lifetime. Whether SpaceX is inflating the severity for regulatory effect or genuinely documenting a safety problem, the claim alone puts pressure on the FCC to weigh in.
Amazon’s Defense: SpaceX Created This Conflict
Amazon’s response offers a different chronology. The company pointed out that SpaceX announced in early 2025 that it would move thousands of Starlink satellites from orbits around 550 kilometers down to lower altitudes in the 475-485-kilometer range. That decision, which SpaceX described as improving space safety, placed the Starlink constellation directly in the path that Amazon’s satellites were already transiting on their way to higher operational orbits.
Amazon also noted that SpaceX itself served as a launch provider for Amazon missions in 2025, deploying satellites to initial altitudes around 460 kilometers without raising any objections. Amazon stated in its FCC filing that SpaceX only began raising these issues after lowering the altitude of its Starlink constellation.
Amazon argued that the issues raised by SpaceX do not involve violation of Commission rules or industry standards. Amazon stated that its launch and insertion parameters comply with industry standards and best practices.
The implication is clear: SpaceX moved into the neighborhood and then complained about the traffic.
The Logistics of Changing a Launch
One of the most telling details in Amazon’s filing is the explanation of why it cannot simply lower its insertion altitudes overnight. According to Amazon, modifying deployment parameters with launch providers requires extensive technical assessment. When Amazon approached Arianespace about lowering the insertion orbit for near-term missions, the timeline for those changes would have caused significant delays.
Amazon said it proposed an alternative solution to SpaceX that would have maintained Amazon’s deployment schedule while addressing safety concerns. SpaceX declined the proposal and, according to Amazon, offered no counter-proposal. Amazon did not disclose what that solution entailed.
The company said it is now working with Arianespace to implement a lower target insertion orbit starting with upcoming Ariane 6 launches of Amazon Leo satellites. It is also coordinating with other launch providers to determine if they can lower insertion altitudes without schedule impacts.
This is where the competitive pressure becomes visible. Amazon has announced it is accelerating deployment of its 3,232-satellite constellation, targeting a high launch cadence carrying multiple satellites per launch. Amazon’s deployment schedule includes launches from United Launch Alliance and Arianespace in the coming weeks.
Any delay to that schedule is not just a technical inconvenience. Amazon faces an FCC-imposed deadline to deploy half its constellation, and it has purchased additional Falcon 9 launches from SpaceX to help meet that target. The irony of buying launches from the company accusing you of orbital negligence is not lost on the industry.
Institutional History and Regulatory Gamesmanship
This is not the first time SpaceX and Amazon have used FCC proceedings as competitive weapons. As Ars Technica noted, both companies have accused each other of leveraging regulatory filings to slow the other’s satellite launches at various points over the years. The pattern is well established: file a complaint, force the competitor to spend months responding, gain a few weeks or months of relative advantage.
The current FCC political environment adds another layer. FCC leadership has recently been critical of some regulatory filings between the companies. SpaceX and CEO Elon Musk have a closer relationship with the current FCC leadership than Amazon does. Whether that translates into favorable regulatory treatment on this specific dispute remains to be seen, but Amazon is not operating on friendly terrain.
The FCC’s orbital debris mitigation framework was designed for a different era, one with far fewer satellites and far more space between them. Recent rules requiring deorbiting of defunct satellites represented a modernization. But the current dispute exposes a gap: the framework does not clearly address what happens when two mega-constellations need to transit through the same altitude band, one temporarily during deployment and one permanently during operations.
What the FCC Actually Has to Decide
The commission has a narrow question and a broad one. The commission must decide whether Amazon’s license language encompassing approximately 400 km allows deployments at 460 to 490 kilometers. If yes, SpaceX’s complaint has limited regulatory traction regardless of the safety arguments. If no, Amazon has a compliance problem it needs to fix immediately.
The broader question is harder. As mega-constellations proliferate, the orbital bands in low Earth orbit are becoming contested space. SpaceX operates more than 6,000 Starlink satellites. Amazon is building toward 3,232. Other operators are filing for their own constellations. The FCC needs a coordination framework that anticipates these conflicts rather than adjudicating them after the fact.
SpaceX framed its complaint as a safety issue, and the collision avoidance claims give that framing some teeth. But the company also has an obvious interest in making Amazon’s deployment schedule as difficult as possible. Amazon framed its response as a good-faith effort to accommodate a problem created by SpaceX’s own altitude change, while also having an obvious interest in maintaining launch cadence at any cost.
Both companies are telling a version of the truth. The satellites were higher than 400 kilometers. SpaceX did move its constellation into the same band. Coordination was inadequate. The question is who bears the burden of adjustment, and how quickly.
The FCC will likely push for a negotiated outcome rather than a formal enforcement action. But the underlying problem will only intensify. Low Earth orbit is getting crowded. The rules written for a handful of government and commercial operators do not scale well to a world where two companies alone plan to operate more than 9,000 satellites. Every altitude dispute, every collision avoidance maneuver, every accusatory FCC filing is a symptom of an orbital environment changing faster than the institutions designed to govern it.
Amazon’s satellite broadband ambitions are not going away. SpaceX’s dominance of the market is not going away either. The FCC is going to be settling these fights for a long time.
Photo by Zelch Csaba on Pexels