Starlink operator SpaceX claims that Amazon violated orbital debris requirements by launching satellites into initial altitudes that are too high, increasing the risk of collision with other satellites and spacecraft. SpaceX, which recently reported two Starlink satellite failures that created new space debris, yesterday accused Amazon and its launch partner Arianespace of negligence that \u201cneedlessly and significantly increases risk to other operational systems and inhabited spacecraft.\u201d<\/p>\n
Amazon Leo, formerly known as Kuiper Systems, is launching satellites into low-Earth orbits (LEO) to compete against Starlink\u2019s much larger constellation of broadband satellites. Amazon denied that its launch altitudes violate any requirements or impose a safety risk and said SpaceX itself helped Amazon launch satellites into a similar altitude last year when Amazon used SpaceX as a launch partner.<\/p>\n
SpaceX only objected to the launch parameters after moving its Starlink satellites into nearby altitudes, Amazon said. Changing the altitude of a recent Leo launch would have delayed it by months, according to Amazon. Both Amazon and SpaceX have accused each other of using Federal Communications Commission proceedings to delay the other\u2019s satellite launches at various times over the years.<\/p>\n
Amazon also said it informed the FCC of the launch altitudes that SpaceX now objects to. SpaceX and CEO Elon Musk have a friend at the top of the FCC, though, as Chairman Brendan Carr recently slammed Amazon\u2019s petition to deny a SpaceX request to launch up to 1 million satellites.<\/p>\n
SpaceX\u2019s letter to the FCC yesterday alleged that \u201cAmazon is continuing to violate its approved orbital debris mitigation plan and the express conditions in its license\u2014dispensing satellites 50-90 km higher than authorized and without adequate coordination or information sharing.\u201d<\/p>\n
Amazon told the FCC in a 2021 application that \u201cKuiper Satellites will be launched into an initial deployment orbit at or near 400 km\u201d before being raised to orbital altitudes between 590 km and 630 km. \u201cAfter injection at or near 400 km and successful checkout, each Kuiper Satellite will initiate collision avoidance procedures that will continue throughout on-orbit operations,\u201d Amazon told the FCC in the filing that SpaceX cited in yesterday\u2019s letter.<\/p>\n
,<\/p>\n
Amazon also told the FCC it would \u201cfurther mitigate the risk of collision\u201d by \u201ccoordinat[ing] during operations, in real-time, with systems through whose orbital altitudes Kuiper Satellites will transit.\u201d The FCC subsequently approved Amazon\u2019s orbital debris mitigation plan with license conditions requiring coordination and information-sharing with other space operators using similar orbits, SpaceX said.<\/p>\n
\u201cDespite its repeated representations and related license conditions, Amazon launched eight times into orbits with insertion altitudes above 450 km without submitting any amended orbital debris mitigation plan or seeking Commission approval for such a change,\u201d SpaceX alleged. \u201cMost recently, even with input from SpaceX, Amazon\u2019s February 12, 2026, launch on Ariane 6 inserted its satellites at an altitude sufficiently high that it led to unmitigable collision risks with dozens of operational spacecraft.\u201d<\/p>\n
SpaceX alleged that \u201cAmazon did not update its orbital debris mitigation plan\u201d and \u201cdid not provide sufficiently accurate\u201d information to other operators about the February launch. This \u201csignificantly increased the risks to all satellite operations near the 480 km insertion altitude as well as to inhabited spacecraft,\u201d SpaceX said.<\/p>\n
Amazon filed a letter with the FCC today to respond to the allegations. \u201cThe facts demonstrate that Amazon Leo launches to altitudes permitted under its license, has been transparent about its insertion altitudes with both the Commission and with SpaceX, and operates squarely within established industry safety standards,\u201d Amazon said.<\/p>\n
Amazon said its launch altitudes comply with the \u201cat or near 400 km\u201d license requirement, which provides \u201csome flexibility in adjusting parameters.\u201d Amazon said it went ahead with the 450 km insertion altitude because \u201cchanging near-term Ariane launch parameters would cause multi-month delays,\u201d but has responded to SpaceX\u2019s concerns by committing to using lower initial altitudes starting with its fourth Ariane mission. The February 12 mission was the first of 18 booked launches.<\/p>\n
\u201cLaunch vehicle providers generally require at least months\u2014and typically one year\u2014to retarget insertion altitude due to the complexity of final mission analysis, which encompasses trajectory analysis, coupled loads analysis, and integrated thermal analysis,\u201d Amazon told the FCC. \u201cArianespace, for example, requires three to six months for final mission analysis when changing target orbit parameters. Amazon Leo began this process immediately upon learning of SpaceX\u2019s concerns and has worked diligently with its launch providers to implement changes as quickly as operationally feasible.\u201d<\/p>\n
,<\/p>\n
Amazon said it \u201cproposed a solution that would maintain Amazon Leo\u2019s deployment schedule while still addressing SpaceX\u2019s concerns,\u201d but that \u201cSpaceX declined this proposal and has not proposed alternative solutions.\u201d Amazon also said it \u201cexplain[ed] the change to Commission staff before making it\u201d and \u201cnoted a mean insertion altitude of 450 km in multiple space safety reports filed with the FCC.\u201d<\/p>\n
For the February 12 launch, Amazon said it coordinated to \u201censure maneuver reliability through ISS\u2019s altitude and to mitigate space safety risks caused by increased solar activity,\u201d and \u201cexplained this safety-focused approach to SpaceX in coordination meetings long before launching production satellites into this altitude.\u201d<\/p>\n
SpaceX has FCC authorization to launch 15,000 of its second-generation Starlink satellites at various altitudes, including 475 km, 480 km, and 485 km. SpaceX alleged that Amazon\u2019s February launch \u201cforced Starlink satellites alone to perform 30 collision avoidance maneuvers within hours immediately following the Ariane launch to avoid the newly deployed satellites. Even in the presence of these maneuvers, the risk from this insertion is estimated to considerably exceed the Commission\u2019s semi-annual reporting threshold of 1 \u00d7 10\u207b\u2075 for unmitigated conjunctions.\u201d<\/p>\n
Amazon said the risk threshold described in SpaceX\u2019s letter \u201crelies on a risk measurement methodology that the Commission expressly rejected when evaluating Amazon Leo\u2019s orbital debris mitigation plans.\u201d Amazon said it uses an industry-standard \u201crisk threshold consistent with best practices adopted by both NASA and the FAA,\u201d and \u201cindependently verified its risk posture with SpaceNav to ensure that the probability of collision remains within established industry standards.\u201d<\/p>\n
SpaceX itself launched Amazon satellites into an insertion altitude of 460 km in July 2025 and on two subsequent occasions, Amazon said. Amazon said that SpaceX only began raising objections in the past few months, \u201cafter lowering the altitude of its Starlink constellation to 475, 480, and 485 km (\u00b130 km orbital tolerance), with satellites operating as low as 462 km at the equator. This adjustment placed SpaceX\u2019s satellites directly into the altitude range Amazon Leo uses for orbit insertion\u2014creating the overlap from which SpaceX\u2019s concerns arise.\u201d<\/p>\n
,<\/p>\n
SpaceX argued that \u201cAmazon and Ariane unilaterally increased the insertion altitudes for the February 12, 2026, launch with full knowledge that thousands of satellites are already operating at those altitudes.\u201d Noting that the FCC has approved more satellites to be lowered into those altitudes, SpaceX claimed that Amazon\u2019s \u201cunapproved action materially altered the collision risk profile the Commission evaluated when it approved Amazon\u2019s orbital debris mitigation plan.\u201d<\/p>\n
SpaceX didn\u2019t ask the FCC to take any specific action but said that Amazon must \u201cswiftly ensure its launch plans comport with its authorization before it creates irreparable harm.\u201d Amazon told the FCC in response that it \u201cwill continue to work constructively with SpaceX and other operators,\u201d and said the agency \u201cshould recognize that the current situation stems in significant part from SpaceX\u2019s own recent orbital adjustments, and that Amazon Leo has already taken meaningful steps to address the concerns those adjustments created.\u201d<\/p>\n
SpaceX has over 10,000 Starlink satellites in orbit. The firm said this week that it was monitoring for space debris after losing contact with a satellite, but said the problem seemed to pose \u201cno new risk\u201d to other space operations. SpaceX reported a similar incident in December and has not said what caused the satellite failures.<\/p>\n
LeoLabs, which uses a radar network to track objects in low-Earth orbit, has said the \u201cfragment creation events\u201d were apparently caused by the Starlink satellites themselves, not by collisions with debris or other space objects. In both cases, LeoLabs said it \u201cdetected tens of objects in the vicinity of the satellite after the event.\u201d<\/p>\n
SpaceX has also complained about collision risks from a Chinese constellation. Starlink Senior VP Michael Nicolls said in December that a Chinese company had launched nine satellites without coordinating with other space users, \u201cresulting in a 200 meter close approach\u201d between one of the Chinese satellites and a Starlink satellite.<\/p>\n
SpaceX says it wants to launch a million satellites to create an orbital data center. The potentially massive constellation would increase the importance of measures to prevent the creation of space debris, both from internal failures and collisions with other spacecraft.<\/p>\n","protected":false},"excerpt":{"rendered":"
Starlink operator SpaceX claims that Amazon violated orbital debris requirements by launching satellites into initial altitudes that are too high, increasing the risk of collision with other satellites and spacecraft. SpaceX, which recently reported two Starlink satellite failures that created new space debris, yesterday accused Amazon and its launch partner Arianespace of negligence that \u201cneedlessly […]<\/p>\n","protected":false},"author":1,"featured_media":42773,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[],"class_list":["post-43320","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/43320"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=43320"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/43320\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/42773"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=43320"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=43320"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=43320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}