News
SpaceX Starship factory overflowing with new and flight-proven rockets
After a relatively relaxed period of production and testing, SpaceX’s South Texas Starship factory is practically overflowing with new and flight-proven ships as the company prepares for the rocket’s next major tests.
Even before the one-off Starship Mk1 prototype failed a pressure test late last year, SpaceX was in the process of upgrading its Boca Chica production facilities and refining the ship’s design and manufacturing processes. Starship SN1, the first prototype built as part of that upgrade, rolled to the launch pad on February 25th, 2020, followed by Starship SN2 (turned into a test tank) just a week or so later. Starship SN3 and SN4 would both follow in early and late April, ultimately ending with the latter prototype’s spectacularly violent demise in late May.
Over the remaining three or so months, the pace of testing has slowed a bit as SpaceX’s Starship development program enters the full-scale flight testing phase. Starship SN5 began testing on July 1st, followed by SN6 around six weeks later. Both prototypes successfully hopped just 30 days apart. Now, although SpaceX still plans to hop SN5 a second time and may hop SN6 twice, too, the Starship program’s focus has shifted to high-altitude, high-velocity flight tests and the adoption of a new steel alloy.
Presumably in anticipation of a learning curve as that new steel alloy begins to be tested at full-scale for the first times, SpaceX is churning out Starship prototypes at an unprecedented pace. Intriguingly, that production ramp is hinged upon the assumption that a 304L-class steel alloy (compared to the 301 stainless steel used to build SN1 through SN6) will be as good or better than 301 steel in every significant way.
Currently, that assumption isn’t entirely baseless but is still built upon the success of Starship SN7, SpaceX’s first 304L test tank. SpaceX never confirmed its results but it’s believed that that test tank – more of a material demonstrator than an actual structural Starship prototype – surpassed all previous pressure records before it burst in June.
Given that SN7 performed quite well, it’s at least a bit less surprising that SpaceX is hinging months of work and at least four full-scale Starship prototypes on an otherwise unproven steel alloy. The next big test for 304L Starships will be a second test tank known as SN7.1. Rolled to the test site on September 7th, essentially as soon as Starship SN6 was safed and returned to the factory after its hop debut, SN7.1 is significantly more complex than its sibling and will test a ~304L Raptor mount (thrust puck) and skirt section. The forces and general conditions those new parts will be subjected to are substantially different than most of what SN7 was subjected to, meaning that there is a chance that 304L steel is less optimal in different scenarios.
With any luck, SN7.1’s test campaign – scheduled to begin as early as 9pm CDT (UTC-5), September 10th (today) – will be a flawless success, proving that SpaceX’s new steel alloy is universally superior to 301 for Starship-related applications. If that’s the case, Starship SN8 – the first full new-alloy prototype – will likely be fully outfitted with a nosecone and header tanks before beginning acceptance testing.
Eventually, if SN7.1 aces its tests and SN8 performs well during preflight preparations, Starship SN8 could become the first prototype to launch with a full nose, header tanks, and flaps, as well as the first to fly with three Raptor engines. If Starship SN8 fails for any reason or is damaged during testing, though, it appears that SpaceX will have no shortage of ships built out of the same new steel alloy to choose from.
In just the last ten days, labeled parts and rings for Starships SN9, SN10, and SN11 have all been spotted, implying that SpaceX is concurrently building at least four new Starships. Notably, both Starships SN9 and SN11 already appear to have some of the studs needed for heat shield tile installation affixed to sections of their steel hulls. Based on the sheer number of steel ring stacks spotted over the last week, it’s also safe to assume that SN9’s tank section (and possibly SN10’s, too) is largely prefabricated.
Assuming two of the in-work nosecones are ultimately meant for flight, SpaceX may already have enough hardware on hand to fully assemble two Starships (presumably SN8 and SN9) – including nosecones, header tanks, nose rings, and flaps. It’s safe to say that if SN7.1 achieves its goals, preparations for the first triple Raptor hop, 20 km (~12 mi) test flight, and skydiver-style landing attempt could come together incredibly quickly.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
