PCMag editors select and review products independently. If you buy through affiliate links, we may earn commissions, which help support our testing.

SpaceX: There Was No Near-Collision Between Starlink and OneWeb Satellites

In an FCC filing, SpaceX calls out OneWeb, a rival satellite internet provider, for allegedly providing false statements to the media about Starlink nearly causing a satellite collision.

 & Michael Kan Principal Reporter

Our team tests, rates, and reviews more than 1,500 products each year to help you make better buying decisions and get more from technology.

Our Expert
LOOK INSIDE PC LABS HOW WE TEST
65 EXPERTS
43 YEARS
41,500+ REVIEWS

(Photo Illustration by Pavlo Gonchar/SOPA Images/LightRocket via Getty Images))


Earlier this month, news emerged that SpaceX’s Starlink network narrowly avoided a satellite collision. But on Tuesday, the company told the FCC that the incident was grossly overblown. 

In a filing (PDF) with the agency, SpaceX blames rival satellite internet provider OneWeb for generating the alarm when in reality no danger existed. “Despite recent reports to the contrary, the parties made clear that there was no ‘close call’ or ‘near miss,’” writes David Goldman, SpaceX director of satellite policy. 

On April 9, The Verge reported that recently launched satellites from OneWeb had nearly collided with the Starlink constellation from SpaceX. Satellites from the two companies allegedly at one point came as close as 190 feet. 

The Starlink satellite internet network
The Starlink satellite internet network. (Credit: satellitemap.space)

To prevent crashes, each Starlink satellite has an automated collision-avoidance system. However, OneWeb’s government affairs chief, Chris McLaughlin, told The Wall Street Journal that SpaceX had to turn off the system due to satellites coming in such close contact with OneWeb’s own network.  

“Starlink’s engineers said they couldn’t do anything to avoid a collision and switched off the collision-avoidance system, so OneWeb could maneuver around the Starlink satellite without interference,” the Journal wrote, citing McLaughlin. 

However, SpaceX portrays the incident very differently. “Despite OneWeb’s previous public claims, SpaceX’s autonomous collision-avoidance system was and remains fully functional at all times,” Goldman says in the FCC filing. “SpaceX only turned off the capability at OneWeb’s explicit request after OneWeb decided to conduct a maneuver.”

A timeline of the events supplied by Goldman says SpaceX initially volunteered to manually maneuver the Starlink satellites, but both companies decided to wait. “The probability of collision never exceeded the threshold for a maneuver, and the satellites would not have collided even if no maneuver had been conducted,” he added. 

The filing goes on to say officials from both SpaceX, OneWeb, and the FCC held a call on Tuesday to discuss the situation. Goldman then claims OneWeb offered in the meeting “to retract its previous incorrect statements” on the incident. 

“SpaceX looks forward to hearing confirmation from OneWeb when those retractions have been made,” Goldman adds. 

OneWeb did not immediately respond to a request for comment. But Goldman suggests the whole dispute is about OneWeb and other companies trying to limit competition in the satellite broadband market. “Similarly, Viasat has been making misrepresentations about space safety and demanding unilateral restrictions on competitors in scores of Commission filings and public statements,” Goldman writes.

Indeed, SpaceX has been sparing with rival internet providers on the scope of Starlink, which the FCC can control. SpaceX is hoping to eventually launch tens of thousands of satellites in low-Earth orbit to provide high-speed broadband. But both ground-based ISPs and satellite broadband providers have tried to convince the FCC to impose restrictions on the Starlink network and deny it federal funding. So don't be surprised if more spats around Starlink erupt.

About Our Expert

Michael Kan

Michael Kan

Principal Reporter

My Experience

I've been a journalist for over 15 years. I got my start as a schools and cities reporter in Kansas City and joined PCMag in 2017, where I cover satellite internet services, cybersecurity, PC hardware, and more. I'm currently based in San Francisco, but previously spent over five years in China, covering the country's technology sector.

Since 2020, I've covered the launch and explosive growth of SpaceX's Starlink satellite internet service, writing 600+ stories on availability and feature launches, but also the regulatory battles over the expansion of satellite constellations, fights with rival providers like AST SpaceMobile and Amazon, and the effort to expand into satellite-based mobile service. I've combed through FCC filings for the latest news and driven to remote corners of California to test Starlink's cellular service.

I also cover cyber threats, from ransomware gangs to the emergence of AI-based malware. In 2024 and 2025, the FTC forced Avast to pay consumers $16.5 million for secretly harvesting and selling their personal information to third-party clients, as revealed in my joint investigation with Motherboard.

I also cover the PC graphics card market. Pandemic-era shortages led me to camp out in front of a Best Buy to get an RTX 3000. I'm now following how the AI-driven memory shortage is impacting the entire consumer electronics market. I'm always eager to learn more, so please jump in the comments with feedback and send me tips.

The Best Tech I've Had:

  • My first video game console: a Nintendo Famicom
  • I loved my Sega Saturn despite PlayStation's popularity.
  • The iPod Video I received as a gift in college
  • Xbox 360 FTW
  • The Galaxy Nexus was the first smartphone I was proud to own.
  • The PC desktop I built in 2013, which still works to this day.

Read full bio