News
SpaceX Starlink competitor OneWeb misled the FCC, media with false “near-miss” narrative
In the latest trials and tribulations of a SpaceX Starlink competitor that went bankrupt after spending $3 billion to launch just 74 small internet satellites, it appears that OneWeb knowingly misled both media and US regulators over a claimed “near-miss” with a Starlink satellite.
Back on April 9th, OneWeb went public with claims that SpaceX had mishandled its response to a routine satellite collision avoidance warning from the US military, which monitors the location of satellites and space debris. According to OneWeb government affairs chief Chris McLaughlin, SpaceX disabled an automated system designed to detect and automatically command Starlink satellite collision avoidance maneuvers to let OneWeb move its satellite instead. McLaughlin also stated that “Coordination is the issue – it is not sufficient to say ‘I’ve got an automated system.’”
He also recently criticized the maneuverability of Starlink satellites, claiming that “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.” As it turns out, OneWeb’s “near-miss” appears to have been a farce and the company scrambled to promise to retract those statements in an April 20th meeting with the FCC and SpaceX.
In far more egregious comments made on April 20th to the Wall Street Journal, a publication with a long history of blindly disseminating anti-SpaceX rhetoric, McLaughlin likened OneWeb’s satellites to “Ford Focus” cars and attempted to lambast Starlink satellites by comparing them to “Teslas: They launch them and then they have to upgrade and fix them, or even replace them altogether.”
Over the past 17 months, SpaceX has launched more than 1380 operational Starlink v1.0 satellites, some 870 of which are operational. Another ~440 are in the process of reaching operational orbits. All told, some 1365 are still in orbit and around 1345 of those satellites are working as expected for a total Starlink v1.0 failure rate of roughly 2.5%. As is SpaceX’s bread and butter, however, reliability has been continuously improving and of ~960 Starlink satellites launched over the last ~12 months, the overall failure rate has dropped to less than 1% – an almost threefold improvement.
After exiting bankruptcy last November, OneWeb has completed just two more launches for a total of 140 operational satellites in orbit of a planned ~650. Operating at a much higher ~1200 km (~750 mi) orbit, any failure of OneWeb satellites would produce debris that could remain in orbit for decades, whereas SpaceX has explicitly chosen much lower ~550 km (~340 mi) orbits, meaning that debris reenters in a matter of years. At Starlink’s sub-300-kilometer (~185 mi) insertion orbit, any faulty satellites screened during SpaceX’s checkout process reenter in a matter of days or weeks thanks to drag from Earth’s atmosphere.
The first phase of SpaceX’s Starlink constellation will require approximately 4400 satellites in low Earth orbit (LEO) and the company is already almost a third of the way to that milestone. A second phase could see those numbers grow as high as ~12,000, followed by a third phase with more than 40,000 satellites much further down the road. Relative to OneWeb, Starlink is dramatically more ambitious and each SpaceX satellite offers superior bandwidth and latency in a bid to blanket the Earth in affordable, high-quality broadband internet.
Of course, as a consequence of needing so many satellites to build out a network with enough bandwidth to serve tens to hundreds of millions of people, there is an obvious risk that unreliable satellites could make LEO a much more challenging place to operate for both SpaceX and the rest of the world. It also demands an entirely new approach to collision avoidance given the impracticality of human operators manually managing a fleet of thousands – or tens of thousands – of satellites.
Towards that end, SpaceX is developing an autonomous collision avoidance system – though virtually nothing is known about that system outside of the company, creating a far from optimal situation for all other satellite operators. Nevertheless, aside from one publicized avoidance maneuver in 2019, SpaceX appears to be quickly becoming a responsible and (mostly) transparent operator and custodian.
In an apparent attempt to capitalize on vague fears of “space debris” and satellite collisions, OneWeb – or perhaps just McLaughlin – took it upon itself to consciously misconstrue a routine, professional process of collision-avoidance coordination between OneWeb and SpaceX. McLaughlin ran a gauntlet of media outlets to drag SpaceX through the mud and criticize both the company’s technology and response, ultimately claiming that SpaceX’s Starlink satellite was incapable of maneuvering out of the way.
Instead, according to a precise, evidenced timeline of events presented by SpaceX to the FCC, the coordination was routine, uneventful, and entirely successful. OneWeb itself explicitly asked SpaceX to disable its autonomous collision avoidance software and allow the company to maneuver its own satellite out of the way after SpaceX made it clear that the Starlink spacecraft could also manage the task. The event was neither “urgent” or a “close call,” as OneWeb and media outlets later claimed. SpaceX says it has been coordinating similar avoidance maneuvers with OneWeb since March 2020.
Most damningly, SpaceX says that immediately after OneWeb disseminated misleading quotes about the event to the media, “OneWeb met with [FCC] staff and Commissioners [to demand that] unilateral conditions [be] placed on SpaceX’s operations.” Those conditions could have actually made coordination harder, “demonstrating more of a concern with limiting [OneWeb’s] competitors than with a genuine concern for space safety.” Crucially, despite lobbying to restrict its competitors, “OneWeb [has] argued forcefully that [it] should be exempt from Commission rules for orbital debris mitigation due to their status as non-U.S. operators.”
In simple terms, OneWeb is trying to exploit the FCC to suppress its competition while letting it roam free of the exact same regulations. Meanwhile, SpaceX is focused on launching satellites and serving tens of thousands of beta customers as Starlink speeds towards virtually uninterrupted global coverage barely a year and a half after operational launches began – all while coordinating with dozens of other satellite operators to be the best ‘neighbor’ it can be in space.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
