News
SpaceX CEO Elon Musk updates schedule for first orbital Starship launch
SpaceX CEO Elon Musk has presented the first significant update on the company’s Starship program since September 2019, offering a couple of new details about the status of the first orbital launch attempt of the largest and most powerful rocket ever built.
Unfortunately, above all else, the promised update was primarily a rehash of the broad-strokes vision of SpaceX’s Starship and Mars programs, as well as some basic details – most already known – about the rocket, its Raptor engines, and how it will be operated. Nonetheless, a large portion of the event was dedicated to audience questions, some of which actually extracted some specific details from the SpaceX CEO. Perhaps the single most important news: a rough but updated schedule for Starship’s first orbital test flight.
To be clear, a great many questions remain unanswered. Months after Starbase’s first orbital tank farm reached some degree of completion, SpaceX has yet to fill four main liquid methane (LCH4) tanks with even an ounce of fuel. Over the same period, the farm’s five liquid oxygen and nitrogen (LOx/LN2) tanks have been filled with thousands of tons of propellant and coolant. Why is still entirely unclear, save for speculation that SpaceX ran afoul of rudimentary methane storage regulations and is ever so slowly rectifying those errors with modifications. Without so much as a partially operational tank farm, SpaceX will be unable to attempt an orbital Starship launch, let alone start the process of qualifying a Super Heavy booster for flight with wet dress rehearsals (WDRs) and static fire tests.
Musk also failed to confirm or offer an educated guess as to which Starship and Super Heavy booster will support the first orbital test flight (OTF), whether the first OTF will truly reach orbit (rather than ‘just’ orbital velocity), and what will happen to Ship 20 and Booster 4 if – as a great deal of speculation suggests – they’ve fallen out of favor. If they’re to be replaced, it’s also unclear why that is or how long it might take to qualify a new ship and booster given that Super Heavy B4, for example, has yet to attempt a single static fire test a full six months after it first reached its full height.
Nonetheless, largely thanks to questions asked by members of the media, Musk did offer some valuable insight into Starship’s first orbital-class test flight. The SpaceX CEO says that he believes the Federal Aviation Administration (FAA) could complete an environmental assessment of Starbase as early as March. In the same presentation, Musk stated that SpaceX would “hopefully [complete environmental reviews] a couple months.” A lack of environmental approval has been the single most important bottleneck of orbital Starbase launch operations for months. The FAA originally anticipated that those reviews would be complete by the end of 2021 but recently delayed the estimated date of completion to the end of February 2022. Another delay from February to March (or later) has been expected for weeks.
It’s unclear how seamless the whole process will be but SpaceX will also need to receive an FAA license for orbital Starship launches after clearing environmental reviews. That could take days, weeks, months, or even a year or more. If SpaceX doesn’t receive a Finding Of No Significant Impact (FONSI) on its Starbase environmental assessment (EA) and instead has to complete a far more extensive Environmental Impact Statement (EIS), Starbase could be stuck in bureaucratic gridlock well into 2023 or even 2024.
Thankfully, Musk is extremely confident in SpaceX’s alternatives. In the event that Starbase becomes indefinitely unusable, SpaceX has already received full environmental approval to launch Starship out of Kennedy Space Center Pad 39A. The company has already begun the process of assembling a Starship launch and catch tower offsite and Musk believes that a Pad 39A Starship launch site could be brought online in just 6-8 months if SpaceX refocuses all of its Starship resources onto Florida.
The CEO also says that SpaceX’s goal is to have the hardware needed for Starship’s first orbital test flight ready to launch around the same as regulatory approval is secured – “hopefully a couple months for both,” in Musk’s words. If Starship S20 and Booster 4 are still assigned to mission, that schedule is not difficult to believe. Starship has already completed virtually all of the ground testing needed to qualify it for flight, while – from the outside – Super Heavy has never looked more ready for static fire testing.
If SpaceX intends to use a different ship and booster, though, the company will have to cut the amount of time needed for final assembly and qualification testing by a factor of two or three relative to B4/S20. If the next ship and booster pair takes a similar amount of time as B4/S20, the hardware needed for Starship’s first orbital launch attempt might not be ready until August or September 2022. SpaceX will also need to build, test, qualify, and ship around three-dozen Raptor 2 engines, the production of which could singlehandedly take at least six or seven weeks at the current pace of production.
Ultimately, no matter where the cards currently in the air end up falling, it looks like SpaceX has an extremely busy – and hopefully fruitful – year of Starship development and testing ahead of it
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
