News
SpaceX sends Starship’s first vacuum Raptor engine to Boca Chica
For the first time, SpaceX has shipped a vacuum-optimized Raptor engine to its Boca Chica, Texas Starship factory days after the company’s present reiterated plans for an inaugural orbital launch attempt as early as July.
Back in March 2021, CEO Elon Musk confirmed that he’d set SpaceX a goal of attempting Starship’s first orbital launch no later than the end of July – around four and a half months distant at the time. Fifteen weeks later, though the prospects of an orbital launch attempt happening in July have practically shrunk to zero, SpaceX COO and President Gwynne Shotwell – best known for acting as a more grounded foil to Musk’s often impractical schedule estimates – reiterated that the company is still “shooting for July” for Starship’s first orbital launch attempt.
As of late June, hitting that target would require SpaceX to string together numerous extraordinary feats of engineering and rocketry in record time or attempt some extremely unorthodox corner-cutting.
The launch pad and launch vehicle hardware needed for Starship’s first space shot are currently far from ready for flight. On June 24th, Musk unexpectedly revealed that the Super Heavy booster prototype SpaceX is now in the late stages of assembly isn’t actually the booster that will carry Starship on its first space launch attempt. In other words, though dozens of rings in various states of work are strewn about SpaceX’s Boca Chica factory, the company has yet to begin assembling the massive 65m (~215 ft) tall booster required for the first orbital launch attempt.
Using Super Heavy Booster 3 (B3) as a ruler, assembly could easily take 9-10 weeks – starting whenever the process actually begins. If SpaceX started stacking Booster 4 today, in other words, it’s unlikely that the rocket would even be complete by the end of August. Barring SpaceX taking unprecedented shortcuts, completing the booster is just part of the process of preparing for flight and B4 would still need to be qualified for flight, likely involving at least one cryogenic proof and static fire test.
In a best-case scenario where SpaceX begins assembly today, manages to halve Booster 4 assembly time in one fell swoop, the sneaks the second Super Heavy ever completed through qualification testing in a single week, the orbital flight test booster still wouldn’t be ready for Starship installation (likely another unprecedented first) before mid-August.
That would then leave SpaceX five or six weeks to fully assemble Starship S20, a process that has yet to begin. Like Starship SN15, which Musk said sported “hundreds of improvements”, Musk has also stated that Ship 20 and all after it will feature another batch of upgrades needed to take Starship orbital. Starship SN15 was very gradually stacked and assembled over the course of almost four months, though that slow assembly can likely be blamed on the fact that SpaceX is busy testing Starships SN8 through SN11 and was effectively waiting to see if any other major changes might be required.
While most of S20’s upgrades are a mystery, the ship’s thrust dome – spotted in work at Boca Chica earlier this month – has already confirmed that the prototype will be the first with the necessary hardware for Raptor Vacuum engine installation. That likely means that S20 will also be the first Starship to attempt to static fire six Raptor engines*, potentially producing more thrust than a Falcon 9 booster. On June 27th, one such vacuum-optimized Raptor (RVac) arrived in Boca Chica for the first time ever, making it clear that the comparatively brand new engine may already be ready to start integrated Starship testing.
*Update: SpaceX CEO Elon Musk says that the Raptor Vacuum delivered to Boca Chica on June 27th is, in fact, meant for Starship S20, seemingly confirming that the prototype will fly with a full six Raptor engines.
Of course, beyond Starship and Super Heavy, SpaceX also has a great deal of work left to get the rocket’s first orbital-class launch facilities partially operational. SpaceX will need to complete and activate at least one or two more custom-built propellant storage tanks, sleeve those three or four tanks with three or four massive thermos-like ‘shells,’ complete thousands of feet of insulated plumbing and wiring, finish a massive ‘launch table,’ install that table on a six-legged ‘launch mount;’ outfit that table and mount with an array of power, avionics, hydraulics, and fueling equipment and plumbing; complete a ~145m (~475 ft) ‘integration tower,’ and perform the first fit checks and shakedown tests with a real booster or Starship.
Only then will SpaceX be able to attempt Starship’s first space launch. All told, it might not be literally impossible for SpaceX to complete all the above work in less than five weeks, but it’s safe to say that the odds of that happening could probably make a lottery ticket blush. Regardless, if Starship reaches orbit at any point before the end of 2021, it would beat out simpler “next-generation” rockets like Ariane 6, ULA’s Vulcan, and Blue Origin’s New Glenn despite beginning concerted development years later and with a far less certain funding situation.
Tesla has launched a direct campaign targeting its customers in New Jersey, sending emails that warn of pending legislation that could effectively block true driverless technology in the state.
The email focuses on Senate Bill S.1677 and Assembly Bill A.3968, measures intended to create a three-year autonomous vehicle pilot program but laden with requirements that Tesla argues make unsupervised Robotaxis impossible.
Tesla is sending out this email to New Jersey Tesla owners, warning them that NJ could block autonomous vehicles, and to take action.
“Proposed legislation moving through Trenton right now would impose restrictions so severe that true driverless deployment would remain illegal.… pic.twitter.com/2bmY646AUL
— Sawyer Merritt (@SawyerMerritt) June 16, 2026
According to the email, the bills impose “restrictions so severe that true driverless deployment would remain illegal.” Specific hurdles include mandates for human safety drivers during operations, multimillion-dollar insurance minimums, reportedly $5 million, and thresholds like 100,000 miles of demonstrated safe autonomous driving before any driverless approval.
Tesla contends these are arbitrary barriers that ignore real-world performance data and favor entrenched competitors over innovative technologies like its Full Self-Driving (FSD) system.
The push comes as Tesla has started expanding Robotaxi operations in states like Texas, where unsupervised vehicles are already providing rides in several cities. New Jersey, by contrast, risks falling behind. The company highlights in the email communication that more than 94 percent of serious crashes result from human error, meaning impairment, distraction, or fatigue. These are all problems that Robotaxis eliminate entirely.
In 2025, New Jersey recorded 582 traffic deaths, underscoring the human cost of delayed adoption.
Tesla’s outreach stresses the transformative potential of robotaxis. For families, they could offer safer school runs without drowsy or distracted drivers. For seniors and people with disabilities, robotaxis promise independence and reliable mobility.
In areas with limited public transit, they could deliver affordable, on-demand transportation, reducing congestion, emissions, and overall transportation costs. Economically, the company warns that restrictive rules could cost New Jersey jobs, innovation investment, and billions in potential growth as autonomous ride-hailing scales elsewhere.
Supporters of the legislation, including Sen. Andrew Zwicker, describe the pilot as a cautious framework with strong safety oversight, including incident reporting, expert task forces, and restrictions in sensitive zones like school areas. They view it as balancing innovation with public protection.
Tesla and pro-AV advocates counter that the bill lacks technology neutrality, creates insurmountable entry barriers for commercial deployment, and prioritizes process over outcomes — effectively functioning as a de facto ban on services like Robotaxi.
This latest clash echoes Tesla’s past battles in New Jersey over direct vehicle sales. The email directs owners to Tesla’s advocacy platform, where they can send customized messages to legislators calling for amendments: outcome-based safety standards, open competition, and clear pathways for fully driverless commercial operations.
As hearings approach, Tesla’s campaign frames the issue as a choice between protecting the status quo and embracing life-saving progress. With robotaxi technology already proving itself in permissive states, New Jersey owners are being asked to ensure their state doesn’t lock out the future of transportation.
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.
Tesla urges New Jersey owners to oppose new bill that could block Robotaxi
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
