Connect with us

News

SpaceX Starlink competitor OneWeb misled the FCC, media with false “near-miss” narrative

Starlink (left) and OneWeb (right) haven't had the best relationship over the course of their reluctant coexistence. (SpaceX/OneWeb)

Published

on

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.

Advertisement
-->

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.

Advertisement
-->

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.

SpaceX-OneWeb Ex Parte by Eric Ralph

Advertisement
-->

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

SpaceX Starship Version 3 booster crumples in early testing

Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.

Published

on

Credit: SpaceX/X

SpaceX’s new Starship first-stage booster, Booster 18, suffered major damage early Friday during its first round of testing in Starbase, Texas, just one day after rolling out of the factory. 

Based on videos of the incident, the lower section of the rocket booster appeared to crumple during a pressurization test. Photos of the incident’s aftermath suggest that Booster 18 will likely be retired. 

Booster test failure

SpaceX began structural and propellant-system verification tests on Booster 18 Thursday night at the Massey’s Test Site, only a few miles from Starbase’s production facilities, as noted in an Ars Technica report. At 4:04 a.m. CT on Friday, a livestream from LabPadre Space captured the booster’s lower half experiencing a sudden destructive event around its liquid oxygen tank section. Post-incident images, shared on X by @StarshipGazer, showed notable deformation in the booster’s lower structure.

Neither SpaceX nor Elon Musk had commented as of Friday morning, but the vehicle’s condition suggests it is likely a complete loss. This is quite unfortunate, as Booster 18 is already part of the Starship V3 program, which includes design fixes and upgrades intended to improve reliability. While SpaceX maintains a rather rapid Starship production line in Starbase, Booster 18 was generally expected to validate the improvements implemented in the V3 program.

Tight deadlines

SpaceX needs Starship boosters and upper stages to begin demonstrating rapid reuse, tower catches, and early operational Starlink missions over the next two years. More critically, NASA’s Artemis program depends on an on-orbit refueling test in the second half of 2026, a requirement for the vehicle’s expected crewed lunar landing around 2028.

Advertisement
-->

While SpaceX is known for diagnosing failures quickly and returning to testing at unmatched speed, losing the newest-generation booster at the very start of its campaign highlights the immense challenge involved in scaling Starship into a reliable, high-cadence launch system. SpaceX, however, is known for getting things done quickly, so it would not be a surprise if the company manages to figure out what happened to Booster 18 in the near future.

Continue Reading

News

Tesla FSD (Supervised) is about to go on “widespread” release

In a comment last October, Elon Musk stated that FSD V14.2 is “for widespread use.”

Published

on

Tesla has begun rolling out Full Self-Driving (Supervised) V14.2, and with this, the wide release of the system could very well begin. 

The update introduces a new high-resolution vision encoder, expanded emergency-vehicle handling, smarter routing, new parking options, and more refined driving behavior, among other improvements.

FSD V14.2 improvements

FSD (Supervised) V14.2’s release notes highlight a fully upgraded neural-network vision encoder capable of reading higher-resolution features, giving the system improved awareness of emergency vehicles, road obstacles, and even human gestures. Tesla also expanded its emergency-vehicle protocols, adding controlled pull-overs and yielding behavior for police cars, fire trucks, and ambulances, among others.

A deeper integration of navigation and routing into the vision network now allows the system to respond to blocked roads or detours in real time. The update also enhances decision-making in several complex scenarios, including unprotected turns, lane changes, vehicle cut-ins, and interactions with school buses. All in all, these improvements should help FSD (Supervised) V14.2 perform in a very smooth and comfortable manner.

Elon Musk’s predicted wide release

The significance of V14.2 grows when paired with Elon Musk’s comments from October. While responding to FSD tester AI DRIVR, who praised V14.1.2 for fixing “95% of indecisive lane changes and braking” and who noted that it was time for FSD to go on wide release, Musk stated that “14.2 for widespread use.”

FSD V14 has so far received a substantial amount of positive reviews from Tesla owners, many of whom have stated that the system now drives better than some human drivers as it is confident, cautious, and considerate at the same time. With V14.2 now rolling out, it remains to be seen if the update also makes it to the company’s wide FSD fleet, which is still populated by a large number of HW3 vehicles. 

Advertisement
-->
Continue Reading

News

Tesla FSD V14.2 starts rolling out to initial batch of vehicles

It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.

Published

on

Credit: Grok Imagine

Tesla has begun pushing Full Self-Driving (Supervised) v14.2 to its initial batch of vehicles. The update was initially observed by Tesla owners and veteran FSD users on social media platform X on Friday.

So far, reports of the update have been shared by Model Y owners in California whose vehicles are equipped with the company’s AI4 hardware, though it would not be surprising if more Tesla owners across the country receive the update as well. 

Based on the release notes of the update, key improvements in FSD V14.2 include a revamped neural network for better detection of emergency vehicles, obstacles, and human gestures, as well as options to select arrival spots. 

It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.

Following are the release notes of FSD (Supervised) V14.2, as shared on X by longtime FSD tester Whole Mars Catalog.

Advertisement
-->

Release Notes

2025.38.9.5

Currently Installed

FSD (Supervised) v14.2

Full Self-Driving (Supervised) v14.2 includes:

  • Upgraded the neural network vision encoder, leveraging higher resolution features to further improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances.
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
  • Improved FSD’s ability to manage system faults and improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios, including unprotected turns, lane changes, vehicle cut-ins, and school buses.
  • Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
  • Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!

Upcoming Improvements:

  • Overall smoothness and sentience
  • Parking spot selection and parking quality
Continue Reading