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.
SpaceX-OneWeb Ex Parte by Eric Ralph
-
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
