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.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
