News
SpaceX CEO Elon Musk explains why Blue Origin’s Starship lawsuit makes no sense
For the first time since SpaceX competitor Blue Origin took NASA to federal court after losing a Moon lander contract to Starship and a protest over that loss, unsealed documents have finally revealed the argument Jeff Bezos’ space startup is focusing on in court.
After the details broke in new court documents filed on Wednesday, SpaceX CEO Elon Musk weighed in on Twitter to offer his take on why the arguments Blue Origin has hinged its lawsuit on make very little sense.
While one seemingly significant portion of the main complaint claiming to reveal “additional substantial errors” in SpaceX’s Starship HLS proposal was almost fully redacted, most of the opening argument is legible. In short, Blue Origin appears to have abandoned the vast majority of arguments it threw about prior to suing NASA and the US government and is now almost exclusively hinging its case on the claim that SpaceX violated NASA’s procurement process by failing to account for a specific kind of prelaunch review before every HLS-related Starship launch.
For NASA’s HLS competition, SpaceX proposed to create a custom variant of Starship capable of serving as a single-stage-to-orbit crewed Moon lander with the help of the rest of the Starship fleet – including Super Heavy boosters, cargo/tanker Starships, and a depot or storage ship. SpaceX would begin a Moon landing campaign by launching a (likely heavily modified) depot Starship into a stable Earth orbit. Anywhere from 8 to 14 Starship tanker missions – each carrying around 100-150 tons of propellant – would then gradually fill that depot ship over the course of no more than six or so months. Once filled, an HLS lander would launch to orbit, refill its tanks from the depot ship, and make its way to an eccentric lunar orbit to rendezvous with NASA’s Orion spacecraft and three Artemis astronauts.
As Blue Origin has exhaustively reminded anyone within earshot for the last five months, SpaceX’s Starship Moon lander proposal is extremely complex and NASA is taking an undeniable risk (of delays, not for astronauts) by choosing SpaceX. Nevertheless, NASA’s Kathy Lueders and a source evaluation panel made it abundantly clear in public selection statement that SpaceX’s proposal was by far the most competent, offering far a far superior management approach and technical risk no worse than Blue Origin’s far smaller, drastically less capable lander.
The bulk of Blue Origin’s argument appears to be that its National Team Lander proposal was drastically disadvantaged by the fact that SpaceX may or may not have incorrectly planned for just three ‘flight readiness reviews’ (FRRs) for each 16-launch HLS Starship mission. While heavily redacted, Blue Origin wants a judge to believe that contrary to the US Government Accountability Office’s (GAO) fair assessment that such a small issue is incredibly unlikely to have changed the competition’s outcome, it would have “been able to propose a substantially lower price” for its lander. To be clear, a flight readiness review is an admittedly important part of NASA’s safety culture, but it ultimately amounts to paperwork and doublechecks over the course of a day or two of meetings.
All else equal, the need to complete an FRR before a launch is incredibly unlikely to cause more than a few days of delays in a worst-case scenario and would have next to no cost impact. There is no reasonable way to argue that being allowed to complete some launches without an FRR would have singlehandedly allowed Blue Origin to “[engineer] and [propose] an entirely different architecture.” Nevertheless, that’s exactly what the company attempts to argue – that it would have radically and completely changed the design it spent more than half a billion dollars sketching out if it had only been able to skip a few reviews.
Curiously, Blue Origin nevertheless does make a few coherent and seemingly fact-based arguments in the document. Perhaps most notably, it claims that when NASA ultimately concluded that it didn’t have funds for even a single award (a known fact) and asked SpaceX – its first choice – to make slight contract modifications to make the financial side of things work, NASA consciously chose to waive the need for an FRR before every HLS Starship launch. Only via purported cost savings from those waived reviews, Blue Origin claims, was NASA able to afford SpaceX’s proposal – which, it’s worth noting, was more than twice as cheap as the next cheapest option (Blue Origin).
Ultimately, it thus appears that Blue Origin may have a case to make that NASA awarded SpaceX the HLS Option A contract despite a handful of errors that violated contracting rules and the HLS solicitation. Relative to just about any other possible issue, though, it’s hard not to perceive the problems Blue Origin may or may have correctly pointed out as anything more than marginal and extraordinarily unlikely to have changed the outcome in Blue’s favor had they been rectified before the award. Most importantly, even if Blue Origin’s argument is somehow received favorably and a judge orders NASA to overturn its SpaceX HLS award and reconsider all three proposals, it’s virtually inconceivable that even that best-case outcome would result in Blue Origin receiving a contract of any kind.
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.
A Tesla Cybertruck driver in the United Kingdom had their all-electric pickup seized by local police in the Greater Manchester area after the department cited “legitimate concerns.”
Last Thursday, police saw the pickup on the roads and decided to pull the driver over. Greater Manchester Police said:
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a collision with the Cybertruck.”
🚨 A Tesla Cybertruck, which is illegal to drive in the UK due to safety concerns, has been seized by police in Greater Manchester
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a… pic.twitter.com/cqhdPok3DM
— TESLARATI (@Teslarati) June 16, 2026
The Cybertruck in question was, according to the BBC, registered and insured abroad and was confiscated. The driver, who is a UK resident, was reported.
The Greater Manchester Police Department then added:
“The Tesla Cybertruck is not road-legal in the UK and does not hold a certificate of conformity.”
The Cybertruck cannot be legally driven in the UK because it has no UK Type Approval for operation in the country. This is due to some safety concerns, which are related to its angular shape and design. The stainless steel exoskeleton has sharp edges and projections that violate UK/EU rules on pedestrian protection.
Tesla has considered creating what it referred to as an “international version” that would be approved for operation in Europe. However, there has been no real movement on that front by the company, as it has been focused on the Robotaxi rollout primarily.
A new report claims that Apple is in the process of developing what would be the missing link for Tesla to get CarPlay.
Apple and Tesla have been reportedly working together for some time to give Tesla owners the opportunity to utilize CarPlay within their vehicles. While many owners are more than happy with Tesla’s in-house UI, which is seamless, effective, and smooth, some still want CarPlay, which does have its advantages.
A report from 9to5Mac now states that a new CarPlay technology that was highlighted during the Worldwide Developers Conference (WWDC) would potentially be the bridge between Tesla and Apple. With the addition of a feature known as “Route Sharing,” which gives a navigation app the ability to share routing data with the vehicle, Tesla would be able to launch CarPlay in its vehicles, the report states.
CarPlay has not been a priority for Tesla because it has done extremely well with its in-house UI, but some drivers are just used to it. Additionally, it could improve Tesla’s subpar Navigation or offer improved app capabilities, especially with iMessage.
Route Sharing is an intended addition to CarPlay’s iteration in iOS 26.4, which was released in March:
The addition of CarPlay would undoubtedly be welcome, but at the same time, it seems like Tesla realizes it is not of the utmost priority. There are so many things that Tesla is working on currently within its own vehicles, especially attempting to solve self-driving.
Back in February, Bloomberg had reported that Tesla was still working on bringing CarPlay to its vehicles, but it had not due to app compatibility issues and incredibly low adoption rates of iOS 26.
This bottleneck could buy Tesla the proper amount of time to develop CarPlay for its vehicles. It would be a welcome addition, and could be brought on with either the Summer or Fall 2026 Software Updates.
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
