News
SpaceX’s upgraded Starship set for test flight despite sore NASA contract losers
Within the last week, while SpaceX has been diligently working to ready an upgraded Starship prototype for its first launch, former competitors Blue Origin and Dynetics – both of which recently lost a historic NASA Moon lander contract to SpaceX – have filed “protests” and forced the space agency to freeze work (and funds).
That means that NASA is now legally unable to use funds or resources related to its Human Lander System (HLS) program or the $2.9 billion contract it awarded SpaceX on April 16th to develop a variant of Starship to return humanity to the Moon. However, just like SpaceX has already spent a great deal of its own time and money on Starship development and – more recently – a rapid-fire series of launches, the company appears to have no intention of letting sore losers hamper its rocket factory or test campaign.
Instead, on the same two days Blue Origin and Dynetics loudly filed official protests with the US Government Accountability Office (GAO), SpaceX performed two back-to-back static fire tests with a Starship prototype and Raptor engines outfitted with “hundreds of improvements.” Technical challenges and unsavory weather conditions forced SpaceX to call off a launch planned sometime last week but the company now appears to be on track to launch Starship prototype SN15 as early as Tuesday, May 4th.
In principle, the ability for companies to protest US government contracting decisions is a necessity and (nominally) a net good but it can easily be misused – and often in damaging ways. In the case of Blue Origin and Dynetics, it’s difficult not to perceive both protests as examples of the latter.
Blue Origin effectively disagrees with every single major point made and conclusion drawn by NASA’s Source Selection Authority (Kathy Lueders) and a separate panel of experts – often to the point that the company is strongly implying that it understands NASA’s contracting process better than the space agency itself. Blue Origin partners Northrop Grumman and Lockheed Martin are both partially or fully responsible for several of their own catastrophic acquisition boondoggles (F-35, Orion, SLS, James Webb Space Telescope, etc.) and are part of the military-industrial complex primarily responsible for turning US military and aerospace procurement into the quagmire of political interests, quasi-monopolies, and loopholes it is today.
The primary argument is generally shared by both protestors. In essence, Dynetics [p. 23; PDF] and Blue Origin [PDF] believe that it was unfair or improper for NASA to select just a single provider from the three companies or groups that competed. They argue that downselecting to one provider in lieu of budget shortfalls changed the procurement process and competition so much that NASA should have effectively called it quits and restarted the entire five-month process. Blue Origin and Dynetics also both imply that they were somehow blindsided by NASA’s concerns about a Congressional funding shortfall.
In reality, NASA could scarcely have been clearer that it was exceptionally sensitive about HLS funding and extremely motivated to attempt to return humans to the Moon by 2024 with or without the full support of Congress – albeit in fewer words. As Lueders herself noted in the HLS Option A award selection statement, the solicitation Blue, Dynetics, and SpaceX responded to states – word for word – that “the overall number of awards will be dependent upon funding availability and evaluation results.”
Additionally, implications that NASA somehow blindsided offerors with its lack of funding are woefully ignorant at best and consciously disingenuous at worse. Anyone with even the slightest awareness of the history of large-scale NASA programs would know that the space agency’s budget is all but exclusively determined by Congress each year and liable to change just as frequently if political winds shift. Short of blackmailing members of Congress or wistfully hoping that other avenues of legal political influence and partnership actually lead to desired funding and priorities appearing in appropriations legislation, NASA knows the future of its budget about as well as anyone else with access to the internet and a rudimentary awareness of history and current events.
It became clear that Congress was likely to drastically underfund NASA’s HLS program as early as November 2020 – weeks before HLS Option A proposals were due. The latest appropriations bill was passed on January 3rd, 2021, providing NASA $850 million of the ~$3.4 billion it requested for HLS. Historically, NASA’s experience with the Commercial Crew Program – public knowledge available to anyone – likely made it clear to the agency that it could not trust Congress to fund its priorities in good faith when half a decade of drastic underfunding ultimately delayed the critical program by several years. That damage was done by merely halving NASA Commercial Crew budget request from 2010 to 2013, whereas Congress had already set itself on a path to provide barely a quarter of the HLS funds NASA asked for in the weeks before Moon lander proposals were due.
Ultimately, the protests filed by Blue Origin and Dynetics are packed to the brim with petty axe-grinding, attempts to paint SpaceX in a negative light, and a general lack of indication that either company is operating in good faith. Instead, their protests appear all but guaranteed to fail while simultaneously forcing NASA to freeze HLS work and delay related disbursements for up to 100 days. Given that SpaceX is now technically working to design, build, qualify, and fly an uncrewed Lunar Starship prototype by 2023 and a crewed demonstration landing by 2024, 100 days represents a full 7-10% of the time that’s available to complete that extraordinary task.
Ironically, the protests made by Blue Origin and Dynetics have already helped demonstrate why NASA’s decision – especially in light of unambiguous budgetary restrictions – to sole-source its HLS Moon lander contract to SpaceX was an astute one. Had a victorious Blue Origin or Dynetics been in a similar position to SpaceX, it’s almost impossible to imagine either team continuing work to a significant degree in lieu of NASA funding or direction. SpaceX, on the other hand, hasn’t missed a beat and looks set to continue Starship development, production, and testing around the clock regardless of NASA’s capacity to help.
In other words, with a little luck, the actual schedule impact of a maximum 100-day work and funding freeze should be a tiny fraction of what it could have been if NASA had selected an HLS provider more interested in profit margins and stock buybacks than creating a sustainable path for humanity’s expansion beyond Earth.
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
