News
SpaceX sends OneWeb satellites to orbit on 55th launch of 2022
SpaceX has successfully launched the first of at least three missions for Starlink competitor OneWeb, completing its 55th launch of the year in the process.
Hopefully ending a strange series of delays that began last month, Falcon 9 lifted off from SpaceX’s NASA Kennedy Space Center LC-39A pad several days behind schedule on December 8th, 2022. The rocket performed perfectly, ascending for about nine minutes to reach a parking orbit around 400 kilometers (~300 mi) above Earth’s surface. B1069, Falcon 9’s flight-proven booster, shut down, separated from the upper stage, flipped around with cold-gas thrusters, and began boosting back to the Florida coast two and a half minutes after liftoff.
Thanks to the launch’s timing, which happened moments after sunset, B1069 first experienced sunset on the ground, ascended back into the light after liftoff, and finally experienced a second sunset while racing back to Earth – all beautifully captured by SpaceX tracking cameras. Eight minutes after liftoff, the Falcon 9 booster touched down on SpaceX’s LZ-1 landing pad, completing its fourth orbital-class launch in 12 months. Around the same time, Falcon 9’s upper stage reached orbit.


The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
An hour after liftoff, the upper stage ignited a second time to circularize its parking orbit. Its payload – a record 40 OneWeb satellites weighing roughly 6.5 metric tons (~14,300 lb) – was then deployed in two sets of 13 and one set of 14 over the next half hour, after which the upper stage likely performed a deorbit burn to ensure it doesn’t become space debris.
For its own Starlink internet constellation, SpaceX routinely launches 54+ satellites – weighing almost 17 tons (~37,000 lb) – at once, demonstrating the kind of efficiency that can be achieved when a satellite is explicitly designed to use as much of Falcon 9’s performance as possible. To some extent, OneWeb did something similar, but for a different rocket. OneWeb’s far more traditional 150-kilogram (~330 lb) satellites were loosely designed to launch on Russia’s Soyuz 2.1 after the company purchased up to 21 of the rockets for $1-1.5 billion in 2015.
But their more traditional hollow-box design and traditional cylindrical payload dispenser means they take up as much or more space than Starlink satellites despite weighing 50-100% less. OneWeb says each satellite provides up to 7 gigabits per second (Gbps) of bandwidth, while each Starlink V1 satellite appears to have about 20 Gbps.


As previously discussed on Teslarati, OneWeb directly competes with SpaceX’s far larger Starlink internet constellation, and refused to engage with the company for launch services – even though Falcon 9 could have likely deployed its satellites more quickly and efficiently – until it was forced to.
“The only reason OneWeb agreed to launch a small subset of its first-generation satellites on SpaceX rockets was a series of egregious actions from Russia that made the pair’s exclusive arrangement too toxic to continue. In June 2015, just 16 months after Russia illegally invaded Ukraine’s Crimea and Donbas regions, OneWeb chose to tie itself at the hip to the unstable aggressor with a firm $1-1.5 billion contract that committed the entirety of its first satellite constellation to 21 Russian Soyuz rockets.
OneWeb nearly escaped consequences from that dubious decision. But in February 2022, Russia doubled down on eight years of small-scale war and Ukrainian occupation with a full-scale, gloves-off invasion with explicit genocidal intent. Europe eventually responded in part with economic sanctions and military supplies that Russia did not appreciate. In response, Russia took a batch of 36 OneWeb satellites hostage, stole the Soyuz rocket OneWeb had already paid for, and killed any possibility of the company completing the six or seven Soyuz launches left under its Arianespace contract. In September 2022, OneWeb announced that it had written off a loss of $229 million as a result of those stolen satellites and rockets.”
Teslarati.com — December 6th, 2022
OneWeb was thus forced to either accept major delays while waiting for European launch options or look elsewhere. OneWeb was able to secure two contracts for India LVM3 rockets, each carrying 36 satellites, but the company chose SpaceX – the only Western launch provider in the world with large amounts of near-term capacity to spare – to launch three batches of 40 satellites.
After its first SpaceX launch, OneWeb should have 500 working satellites in orbit. Another LVM3 launch and two Falcon 9 launches should leave the company with 616 of 648 planned satellites in orbit. It’s unclear how OneWeb intends to launch the 32 remaining satellites.
OneWeb Flight 15 was SpaceX’s 55th successful launch of 2022, leaving the company just five launches away from achieving a 60-launch target set by CEO Elon Musk in March. Following an unintentional 12-day gap between launches caused by several delays, it’s no longer clear if SpaceX can hit that target. SpaceX has never launched later than December 23rd, and it’s extremely unlikely that the company will be able to launch five more times in the next 15 days. Even if it can break through that apparent barrier, it’s also almost impossible to imagine that SpaceX will be able to launch five more times before the end of the year if each mission continues to suffer days or weeks of technical delays.
Originally scheduled to lift off on November 22nd, 29th, 30th, and December 7th, SpaceX’s next mission – carrying a private Japanese Moon lander – is scheduled to launch no earlier than December 11th. After HAKUTO-R, Spaceflight Now reports that SpaceX has another four launches tentatively scheduled this month.
Rewatch SpaceX’s first OneWeb launch here.



Elon Musk
The Boring Company just doubled its tunneling power in Nashville
The Boring Company’s Prufrock MB2 is commissioned and ready to mine beneath Nashville’s streets.
The Boring Company’s second tunnel boring machine, Prufrock MB2, is officially ready to dig in Nashville. The company confirmed the news on X, posting: “Prufrock-MB2 is ready to mine in Nashville! MB2 commissioning is complete, including the brief 11 rpm rotation shown here. Will MB2 catch up to MB1, who had quite the head start? And Prufrock-MB3 ships in August!”
MB2 arrives with meaningful improvements over its predecessor. Lessons learned from the launch and operation of MB1 have already been applied to MB2 to improve efficiency and prepare the machine for launch.
Traditional tunnel boring machines operate in a stop-and-go cycle, digging roughly five feet, halt, erect precast concrete segments to line the tunnel wall, then resume. That repeated interruption is one of the main reasons conventional tunneling is slow and expensive. Prufrock is designed to install the tunnel liner simultaneously with mining, eliminating the need to stop every five feet. The machine also skips the need for excavated launch pits. Prufrock arrives on a truck, tilts down, and launches into the ground within 24 hours. And when the tunnel is complete, it emerges from the ground and drives to its next launch site on a trailer, eliminating the need for expensive cranes or pit excavation. The machine is also fully electric and runs with zero people in the tunnel during normal operations, controlled remotely from a surface operations center.
Prufrock-MB2 is ready to mine in Nashville! MB2 commissioning is complete, including the brief 11 rpm rotation shown here.
Will MB2 catch up to MB1, who had quite the head start?
And Prufrock-MB3 ships in August! pic.twitter.com/TTrMql2aRg
— The Boring Company (@boringcompany) June 17, 2026
It won’t be long before we hear of another major update on The Boring Company’s Music City Loop project – a planned underground transit network beneath Nashville that would move passengers in electric vehicles through a series of tunnels at highway speeds, and bypassing surface traffic entirely. Nashville was selected in part because of its strong rock conditions that suits the Prufrock machines well, and relatively less regulatory hurdles.
Progress has been steady on multiple fronts. All 37 permits and approvals required ahead of tunneling have been obtained, out of 45 total. Key wins include a fully executed TDOT tunnel permit authorizing 25 miles of tunnel, unanimous airport authority approval for a Nashville International Airport station, and the city’s first residential station agreement serving downtown tower residents.
With MB1 already tunneling, MB2 now commissioned, and MB3 shipping in August, Nashville is becoming something of a live proving ground for scaled tunnel boring. The broader ambition is not limited to one city. The Boring Company’s stated goal is to make underground transportation a practical alternative to surface roads across major metro areas. Nashville is one of many cities, including a successful Las Vegas tunnel system, where that idea is being put to the test at real speed.
News
Tesla urges New Jersey owners to oppose new bill that could block Robotaxi
Tesla has launched a direct campaign targeting its customers in New Jersey, sending emails that warn of pending legislation that could effectively block true driverless technology in the state.
The email focuses on Senate Bill S.1677 and Assembly Bill A.3968, measures intended to create a three-year autonomous vehicle pilot program but laden with requirements that Tesla argues make unsupervised Robotaxis impossible.
Tesla is sending out this email to New Jersey Tesla owners, warning them that NJ could block autonomous vehicles, and to take action.
“Proposed legislation moving through Trenton right now would impose restrictions so severe that true driverless deployment would remain illegal.… pic.twitter.com/2bmY646AUL
— Sawyer Merritt (@SawyerMerritt) June 16, 2026
According to the email, the bills impose “restrictions so severe that true driverless deployment would remain illegal.” Specific hurdles include mandates for human safety drivers during operations, multimillion-dollar insurance minimums, reportedly $5 million, and thresholds like 100,000 miles of demonstrated safe autonomous driving before any driverless approval.
Tesla contends these are arbitrary barriers that ignore real-world performance data and favor entrenched competitors over innovative technologies like its Full Self-Driving (FSD) system.
The push comes as Tesla has started expanding Robotaxi operations in states like Texas, where unsupervised vehicles are already providing rides in several cities. New Jersey, by contrast, risks falling behind. The company highlights in the email communication that more than 94 percent of serious crashes result from human error, meaning impairment, distraction, or fatigue. These are all problems that Robotaxis eliminate entirely.
In 2025, New Jersey recorded 582 traffic deaths, underscoring the human cost of delayed adoption.
Tesla’s outreach stresses the transformative potential of robotaxis. For families, they could offer safer school runs without drowsy or distracted drivers. For seniors and people with disabilities, robotaxis promise independence and reliable mobility.
In areas with limited public transit, they could deliver affordable, on-demand transportation, reducing congestion, emissions, and overall transportation costs. Economically, the company warns that restrictive rules could cost New Jersey jobs, innovation investment, and billions in potential growth as autonomous ride-hailing scales elsewhere.
Supporters of the legislation, including Sen. Andrew Zwicker, describe the pilot as a cautious framework with strong safety oversight, including incident reporting, expert task forces, and restrictions in sensitive zones like school areas. They view it as balancing innovation with public protection.
Tesla and pro-AV advocates counter that the bill lacks technology neutrality, creates insurmountable entry barriers for commercial deployment, and prioritizes process over outcomes — effectively functioning as a de facto ban on services like Robotaxi.
This latest clash echoes Tesla’s past battles in New Jersey over direct vehicle sales. The email directs owners to Tesla’s advocacy platform, where they can send customized messages to legislators calling for amendments: outcome-based safety standards, open competition, and clear pathways for fully driverless commercial operations.
As hearings approach, Tesla’s campaign frames the issue as a choice between protecting the status quo and embracing life-saving progress. With robotaxi technology already proving itself in permissive states, New Jersey owners are being asked to ensure their state doesn’t lock out the future of transportation.
News
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
Turn-by-turn navigation is not new technology.
For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.
Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.
Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.
Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.
But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.
This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.
More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.
It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?
Multiple Data Sources
First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.
Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.
Persistent Learning
FSD seems to struggle with persistent learning from driver interventions.
Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.
This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.
I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.
The next thing I’ve noticed, and this might be controversial, is that Nav has gotten even worse.
I think that might actually be a good thing; Tesla seems to be adjusting it. They just need to adjust it the opposite way.
The car is taking extremely strange routes to very… https://t.co/UHg3tVfNA2
— TESLARATI (@Teslarati) June 16, 2026
Reasoning, Scaling, and Intuition
Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.
Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.
Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.
Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.
Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.