News
SpaceX’s NASA Starship contract safe for now as Blue Origin looks to Congress
Fresh off of a major contract loss during a competition to build NASA’s next crewed Moon lander, Blue Origin has begun aggressively lobbying Congress for the contract NASA didn’t give it.
Thankfully, albeit not at first, a modification has been made to an amendment first proposed by a Senator that has long pursued favorable treatment of Blue Origin that will prevent that legislation – if it passes – from unfairly interrupting the $2.9 billion contract NASA already awarded SpaceX. Announced on April 16th, that award came as a shock, effectively cementing SpaceX’s lunar Starship as both the cheapest and most technically sound proposal to return humanity to the Moon.
As such, although NASA made it clear that it would have selected two of the three competing proposals in a perfect scenario, Congress allocated just a quarter of the Human Landing System (HLS) funding NASA requested, forcing the agency between a rock and a hard place.
NASA repeatedly stated as much both before and after the decision was announced, effectively implying that the agency had learned its lesson with the Commercial Crew Program, in which it had selected two redundant providers – Boeing and SpaceX – only for Congress to systematically underfund the program for years. As a direct result of years of underfunding during an early and formative period, both providers suffered at least 2-3 years of delays, followed by another few years of more organic delays as development matured and new challenges were unsurprisingly uncovered.
Politically, NASA could never say that – effectively biting the hand that (under)feeds – out loud, but it was strongly implied in an official HLS source selection statement released to partially explain why it had chosen SpaceX and SpaceX alone. Almost instantly, both losing competitors – Blue Origin and Dynetics – filed protests with the US Government Accountability Office (GAO) filled with far more bizarre, rambling tangents than coherent legal arguments.
Unless GAO operates on a different standard than the court of law or uncovers something nefarious behind closed doors, a close reading of both partially redacted protests does not bode well for either document’s ability to sway the office’s opinion. Almost as if Blue Origin itself is aware of just how frivolous its protest really is, the company – seemingly backed by partners Northrop Grumman, Lockheed Martin, and Leidos – wasted no time lobbying Senator Maria Cantwell for an alternate avenue to get what it wants and the government money founder Jeff Bezos feels entitled to.
Cantwell represents Washington State, where both Amazon and Blue Origin are headquartered, and has frequently spoken out in support of – or personally introduced – legislation that would specifically favor Bezos’ space company. On May 12th, Cantwell introduced an amendment that would purportedly “maintain competitiveness” by forcing NASA to select a second HLS winner in addition to SpaceX. Without irony, the authorization bill also demanded that NASA make that decision within a mere 30 days.
Under those conditions, Congress would authorize $10 billion for NASA to develop and demonstrate two landers with an uncrewed and crewed Moon landing each – the original plan. Insultingly, Cantwell tacked that amendment onto an authorization bill, meaning that even if Congress were to pass the bill and the President were to sign it into law, Congress would still have to actually allocate that $10 billion in the form of a more than 10% boost to NASA’s annual budget. Historically, even if Congress were to defy all recent precedent and significantly boost NASA’s 2022 budget, there is no guarantee that that raise would be upheld for four or more years, which it would need to be for the authorization bill to be anything more than a hollow promise.
More recently, a clause was thankfully added clarifying that NASA is not allowed to “modify, terminate, or rescind” SpaceX’s HLS contract to comply with the amendment. Additionally, while still amounting to a legal gun to NASA’s head to force it to into a contract it knows it cant afford, the modification gives NASA 60 days to award a second lander contract. Based on the agency’s own selection statement, Blue Origin’s National Team would almost certainly be the recipient in the event that the bill becomes law, forcing NASA to commit more than $9 billion – instead of $2.9 billion – to the next stage of HLS development with no guarantee that its budget will be raised accordingly.
In the meantime, GAO still has to complete its reviews of Blue Origin and Dynetic’s protests and the White House has to submit its FY2022 budget request and consider adding NASA funding to its proposed jobs and infrastructure package.
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
