News
What’s causing SpaceX’s Falcon Heavy delays?
Although uncertainty in the schedule remains, SpaceX’s Falcon Heavy rocket appears to be nearly ready for its first engine ignition test (called a ‘static fire’) sometime within the next week or so.
An attempt at 1 PM EST today, January 16, was canceled for unspecified reasons, although Kennedy Space Center reportedly maintained the usual roadblock to prevent vehicles from driving past, implying that SpaceX still intends to conduct propellant loading tests with Falcon Heavy. It was noted earlier this morning by spaceflight journalist Chris Bergin that things were “a bit too quiet” if a test was indeed planned for today, and his intuition appears to have been correct. It still remains the case that Falcon Heavy is an experimental and untested rocket to an extent, and these delays are to be expected as SpaceX works out the inevitable kinks and bugs that arise during the extensive testing big launch vehicle has been and is still being put through.
KSC is in roadblock stance, so they will still do some testing it would seem, but we will have to wait for the Static Fire itself. https://t.co/DxzsRn85NR
— NSF – NASASpaceflight.com (@NASASpaceflight) January 16, 2018
Due to range requirements in support of an upcoming launch of the United Launch Alliance’s (ULA) Atlas 5 rocket, currently NET Thursday, SpaceX has postponed the static fire of Falcon Heavy without a replacement date. It is unlikely that another attempt will occur before the upcoming weekend, but SpaceX should have at least a solid week of uninterrupted range support once ULA’s launch occurs, hopefully without delay. Godspeed to ULA, in the meantime.
The crazy complexity of rocketry
Most recently, and perhaps somewhat related to Falcon Heavy’s static fire delays, SpaceX completed as many as two complete wet dress rehearsals (WDRs), which saw Falcon Heavy topped off with full tanks of its cryogenic (super cool) liquid oxygen (LOX) and rocket-grade jet fuel (RP-1). In essence, the rocket became equivalent to several hundred tons of carefully stabilized explosive. Nominally, these rehearsals appear entirely uneventful to an outside observer, with little more than ice formation and the occasional bursts of propellant tank vents to suggest that something important is occurring. However, anomalies like the failure of Falcon 9 during the Amos-6 static fire provide a staggering demonstration of just how explosive and sensitive a rocket’s fuel is, and Falcon Heavy has approximately three times the fuel capacity of Falcon 9. Empty, Falcon 9’s mass has been estimated to be around 30 metric tons, a minuscule amount of structure in the face of the more than 500 metric tons of propellant the vehicle carries at liftoff.
These propellant loading tests can also be challenging for reasons aside from their highly explosive nature. Due to basic realities of the physical nature of metal, the predominate ingredient for Falcon 9’s load-bearing structures, metallic structures shrink under extreme cold (and expand under heating). In the case of Falcon 9’s massive 45 meters (150 foot) tall first stage, the scale of this contraction can be on the order of several inches or more, particularly given SpaceX’s predilection towards cooling their propellant as much as possible to increase its energy density. For Falcon 9, these issues (thermodynamic loads) are less severe. However, add in three relatively different first stage boosters linked together with several extremely strong supports at both their tops and bottoms and that dynamic loading can become a fickle beast. The expansion or compression of materials due to temperature changes can create absolutely astounding amounts of pressure – if you’ve ever forgotten a glass bottled drink in the freezer and discovered it violently exploded at some future point, you’ll have experienced this yourself.
With several inches of freedom and the possibility that each Falcon Heavy booster might contract or expand slightly differently, these forces could understandably wreak havoc with the high precision necessary for the huge rocket to properly connect with the launch pad’s ground systems that transmit propellant, fluids, and telemetry back and forth. Information from two reliable Kennedy Space Center sources experienced with the reality of operating rockets, as well as NASASpaceflight.com, suggested that issues with dynamic loads (such as those created by thermal contraction/expansion) are a likely explanation for the delays, further evidenced by their observations that much of the pad crew’s attention appeared to be focused at the base of Transporter/Erector/Launcher (TEL). The TEL base hosts the clamps that hold the rocket down during static fires and launches, as well as the Tail Service Masts (TSMs) that connect with the Falcon 9/Heavy to transport propellant and data to the first stage(s). These connection points are both relatively tiny, mechanically sensitive, and absolutely critical for the successful operation of the rocket, and thus are a logical point of failure in the event of off-nominal or unpredicted levels of dynamic stresses.
-
- The white bars in this photo are half of Falcon Heavy’s seperation mechanism. A number of actuators take the place of the more common solid rocket motors used with vehicles like the Delta IV Heavy. (SpaceX)
-
- Falcon Heavy’s three boosters and 27 Merlin 1D engines on full display. (SpaceX)
-
- Falcon Heavy. Modeled and rendered by NASASpaceflight forum user WBY1984. (WBY1984)
Test, launch, land, repeat.
All things considered, these difficulties demonstrate that even after months (even years) of relentless modeling, testing, remodeling, and retesting, rockets (and especially huge rockets like Falcon Heavy) are immensely complex, and even tiny mistakes can lead the vehicle to stray from its expected behavior. Quite simply, the reality of engineering only truly comes into play once hardware is fully in the loop, and it’s in this state that SpaceX has demonstrated again and again a distinct and elegant ability to learn from their hardware, rather than attempt to salve uncertainty with a neurotic and counterproductive level of statistical analysis, modelling, and documentation. The agile launch company still dabbles in those aspects when beneficial or necessary, but testing comes first in its importance.
The conclusion here, then, is that Falcon Heavy’s delays betray this aspect of SpaceX – a launch company that loves its fans, but also understands the need for cautious testing when it comes to new and untried rocket hardware. Whether Falcon Heavy succeeds or fails, SpaceX will learn from the proceedings, and they will be better off for it (although maybe less so financially…).
Follow along live as launch photographer Tom Cross and I cover these exciting proceedings as close to live as possible.
Teslarati – Instagram – Twitter
Tom Cross – Instagram
Eric Ralph – Twitter
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
