On April 1, 2026, SpaceX filed a formal complaint with the Federal Communications Commission alleging that Amazon’s satellite internet service had been placing satellites in the wrong orbit. The claim was specific: Amazon’s vehicles were arriving at insertion altitudes 50 to 90 kilometers higher than their FCC authorization allowed, forcing Starlink to execute 30 collision-avoidance maneuvers within hours of a single Amazon launch. SpaceX argued the deployments violated Amazon’s orbital debris mitigation plan and created risks that no amount of coordination could fully mitigate.

Amazon fired back within 24 hours. Its rebuttal was two sentences of carefully chosen words: SpaceX itself had launched Amazon satellites on three Falcon 9 rideshare missions in 2025, placing them at roughly 460 kilometers—the same altitude range SpaceX was now complaining about. Amazon called the complaint “disingenuous.”

Welcome to the altitude war.

Why Altitude Matters

In LEO, the altitude at which a satellite operates is not a footnote. It determines how much atmospheric drag the spacecraft experiences, how long a defunct vehicle takes to reenter naturally, how often it passes over ground stations, and—critically—which operators win spectrum coordination disputes when two constellations occupy overlapping frequencies.

Below roughly 500 kilometers, atmospheric drag remains strong enough that a failed satellite deorbits within a few years. Above that threshold, drag fades and uncontrolled debris can persist for decades. This is why the FCC requires megaconstellation operators to file detailed orbital debris mitigation plans before launch—specifying insertion altitudes, disposal strategies, and timelines. Launching at an altitude not in the approved plan is a licensing violation, not merely a technical footnote.

Amazon’s February 12, 2026 Ariane 6 launch placed 32 satellites into parking orbits of approximately 450 to 490 kilometers. From there, the satellites were planned to fire their own thrusters and raise to an operational altitude near 630 kilometers. SpaceX’s complaint alleged that the insertion altitude was 50 to 90 kilometers above the roughly 400 km Amazon was authorized to use as a staging orbit, and that Amazon had filed no amended debris mitigation plan before the launch to account for the change.

The Irony in the Complaint

The complaint would be straightforward if SpaceX were a neutral party. It is not.

In January 2026, Starlink announced it would spend the year lowering approximately 4,400 satellites from their current shells at roughly 550 kilometers down to approximately 480 kilometers. The stated rationale was safety: orbital zones below 500 km host fewer debris objects, and any failed satellite at lower altitude deorbits faster under natural drag. In the same January decision, the FCC granted SpaceX authorization for an additional 7,500 Gen2 Starlink satellites, bringing its total authorized fleet to 15,000 vehicles worldwide.

SpaceX was simultaneously expanding its constellation and moving a large portion of it toward 480 km—directly into the altitude band where Amazon was temporarily staging its own satellites. The insertion altitude Amazon used, 450 to 490 km, overlaps almost exactly with where Starlink is headed. Amazon noted, pointedly, that SpaceX itself had delivered Amazon Leo satellites to 460 km on Falcon 9 missions the year before without objection.

The resulting picture is peculiar: SpaceX objecting to Amazon operating at the altitude band Starlink is migrating into, while simultaneously lobbying the FCC to approve more satellites of its own at overlapping heights.

The FCC’s Dilemma

SpaceX’s altitude complaint landed on the FCC at an inconvenient moment. The commission was already weighing a separate Amazon petition for a 24-month extension of its satellite deployment deadline. Under FCC rules, Amazon needed 1,616 satellites in orbit by July 30, 2026 to maintain spectrum coordination priority in Ku and Ka bands. With fewer than 400 in orbit as that deadline approached, Amazon was far short.

SpaceX opposed the extension, arguing Amazon should be required to restart its license application from scratch—a procedurally ruinous outcome that would have effectively ended Amazon’s ability to compete in the LEO broadband market.

The FCC rejected SpaceX’s position. In granting the waiver, the commission explicitly cited the public interest in having a viable competitor to Starlink, which already operates more than 7,600 satellites and serves around 10 million subscribers. But the FCC did not simply capitulate to Amazon: any satellite Amazon launches after July 30 will temporarily lose its spectrum coordination priority status. Until Amazon either hits 50% of its full constellation deployment or reaches a hard deadline in March 2028—whichever comes first—it bears the regulatory burden of avoiding interference with rivals, including Starlink.

As for the altitude complaint itself, the FCC has issued no direct ruling. The complaint is live in the regulatory record but unresolved.

Debris Rules as Competitive Infrastructure

The altitude fight points to something larger: orbital debris regulations, designed as a shared technical commons, are increasingly being wielded as competitive tools.

The FCC’s debris rules require satellite operators to maintain a post-mission disposal reliability rate of at least 95%. SpaceX’s semi-annual compliance report, filed in July 2026, disclosed that it had controlled-deorbit 260 Starlink satellites between December 2025 and May 2026—primarily first-generation v1.0 and v1.5 units that had reached the end of their five-year service lives. SpaceX reported a disposal reliability rate exceeding 99%. This is a genuine engineering achievement, but it also means SpaceX is filing detailed regulatory compliance reports that create a standard Amazon must now match.

When SpaceX complains that Amazon launched at the wrong altitude without an updated debris plan, it is using those same compliance standards as a lever. Whether or not the underlying safety concern is legitimate—and there may well be a real concern mixed in with the competitive motivation—the filing creates regulatory drag. Amazon must respond, document its approach, and potentially amend its filings. That takes time and legal resources, and anything left in the record can be cited again the next time SpaceX wants to challenge an Amazon milestone.

Where Amazon Stands

Despite the regulatory headwinds, Amazon Leo has been moving. By early July 2026, following an Atlas V launch that delivered 29 more satellites, the constellation stood at approximately 396 units—making it the third-largest satellite constellation currently in orbit. Amazon says this is enough to begin limited commercial service before the end of 2026, though full commercial viability requires deploying most of the remaining ~2,800 satellites it still needs under its FCC authorization of 3,236 total.

Launch capacity remains the binding constraint. Amazon is relying on a mix of ULA’s Atlas V, Blue Origin’s New Glenn, and Arianespace’s Ariane 6. New Glenn suffered a setback earlier in 2026 when a rocket exploded during a static fire test, destroying the launch pad and delaying a planned 48-satellite mission. The clock toward Amazon’s July 2029 full-deployment deadline is running.

For now, Amazon Leo operates under a reduced regulatory status. Its newest satellites carry no spectrum priority. In any interference dispute that arises before it reaches scale, Amazon is the one that must move, adjust, or absorb costs. That is precisely the position SpaceX lobbied for— and the FCC, while refusing to eliminate Amazon as a competitor, gave SpaceX a version of what it wanted.

The Altitude Band as Contested Territory

What the SpaceX-Amazon dispute makes clear is that specific altitude bands in LEO are no longer generic parking space. They are contested territory with implications for spectrum rights, debris liability, and competitive standing. As both constellations grow—and as other operators including Eutelsat OneWeb and Telesat Lightspeed continue to fill in their own orbital shells—the overlapping altitude ranges where satellites temporarily coexist during insertion or lowering maneuvers will become more frequent and more fraught.

The FCC has handled this round by threading a narrow needle: preserve competition, maintain some regulatory teeth, leave the core altitude complaint unresolved. That approach may work for one dispute. As a framework for managing two constellations of thousands of vehicles operating in overlapping shells, it is almost certainly insufficient. Whether the commission develops clearer altitude-band rules before the next filing season—or waits until another emergency maneuver triggers another emergency complaint—may determine how orderly the next phase of LEO development actually is.

Fifty kilometers does not sound like much. In the regulatory ecosystem of low Earth orbit right now, it is everything.

Sources