News
SpaceX’s orbital Starship prototype sheds tiles, comes to life during first tests
After weeks of mostly invisible – albeit slow and steady – work at Starbase’s suborbital launch and test facilities, SpaceX has finally kicked off the first orbital Starship prototype’s first test campaign.
Almost two months ago, Starship 20 (S20) departed the factory it was built in for the first time and was rolled a few miles down a South Texas highway to Starbase’s nascent orbital launch site. There, SpaceX briefly installed Ship 20 on top of Super Heavy Booster 4 (B4) – an important first and one done with the same ship and booster pair CEO Elon Musk says could eventually support the rocket’s inaugural orbital launch attempt. Mere hours after that August 6th photo opportunity and fit test, Ship 20 was rolled back to the Starbase build site for another week of work before again returning to the launch site.
This time around, Starship S20 headed for one of two suborbital launch and test stands and ultimately spent the better part of the next six weeks sitting in place as workers swarmed around the 50m (~165 ft) tall spacecraft and upper stage to prepare it for the next steps. In theory, those steps were simple enough, beginning with the completion of two basic qualification tests – the same tests that a half-dozen prototypes preceding Ship 20 completed without issue.
Effectively SpaceX’s first Starship or Super Heavy test of any kind in more than two months, it thankfully didn’t take long for things to get interesting. Before the pad had even been cleared of the last few remaining workers, Starship S20 violently shed a good dozen or so fragile heat shield tiles. CEO Elon Musk quickly confirmed speculation that Starship S20 had effectively jetted the tiles off its nose during a brief test of high-pressure cold gas maneuvering thrusters, coincidentally around the same time as SpaceX began to pressurize the rocket for its first tests.
Going into what was believed to be Starship S20’s first ambient-temperature pressure test and cryogenic proof test, the loss of some heat shield tiles was almost universally expected. In a structure as large as Starship, even just the thermal contraction of steel at supercool temperatures (and expansion as it warms back up) could change the rocket’s diameter an inch or so, potentially causing tiles to scrape or press against each other. About the size of a dinner plate and the thickness of an average paperback book, Starship’s ceramic heat shield tiles have proven to be very fragile, with dozens routinely chipping, cracking, and shattering during and after installation on Ship 20.
One unique (and no less unproven) aspect of Starship is SpaceX’s decision to mount its heat shield directly to the thin steel propellant tanks and skin that make up the rocket’s entire airframe. SpaceX’s first stab at the problem involves studs/pins welded – by robot – directly to the exterior of Starship’s tanks and skin. By embedding small metal plates inside each cast tile, they can be easily installed by aligning the tile and pressing it against each set of three barb-like pins, which then irreversibly lock in place. Over most of Starship’s hull, SpaceX then tacks on blankets of off-the-shelf ceramic wool insulation before tiles are installed on top of that steel and blanket sandwich. Compared to the Space Shuttle and Russia’s Buran, the only other orbital spacecraft to fly with non-ablative heat shields, Starship’s thermal protection system (TPS) is incredibly simple. Of course, the challenges imposed on heat shields by mechanical stresses during launch/landing, orbital reentry, and a need for rapid reusability are anything but simple.
As such, to see tiles blown off Starship S20 by cold gas maneuvering thrusters that were simply placed too close to adjacent TPS was an unexpected route to an expected outcome. During Monday’s nine-hour test window, SpaceX appeared to partially or fully pressurize Starship S20 at ambient temperatures before aborting a cryogenic proof test either before or just after it began. While an ambient-temperature proof was the easier of the two tests on the docket, it’s still encouraging to see no obvious tile loss caused by the actual mechanical stresses involved in the test.
Most importantly, compared to losing dozens of tiles to regular mechanical or thermal stresses, fixing an issue with thruster impingement is much easier and should only require a few design tweaks to one specific Starship component. The real nail-biting moments will come during Starship S20’s seemingly imminent cryogenic proof and static fire debuts, major TPS issues during either of which could necessitate vehicle-wide design changes and cause delays.
With any luck, whatever forced SpaceX to abort Starship S20’s first cryogenic proof test can be easily rectified, opening the door for additional attempts. Two more test windows are scheduled later this week from 5pm to 11pm CDT on Tuesday and Wednesday. Rewatch today’s brief testing below.
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
