News
SpaceX scrubs Starhopper’s final Raptor-powered flight as Elon Musk talks “finicky” igniters
For unknown reasons, SpaceX’s Starhopper prototype suffered a hold just 0.8 seconds prior to its second planned flight test, a hold that was eventually followed by a decision to scrub the August 26th attempt and try again tomorrow, August 27th.
Starhopper is a full-scale, partial-height testbed for SpaceX’s next-generation Starship launch vehicle, serving more as a semi-mobile test stand for steel rockets and Raptor engines than an actual Starship prototype. The unusual vehicle took flight for the first time ever on July 25th, reaching an altitude of roughly 20m (65 ft) under the power of a single Raptor engine, capable of producing up to 200 tons (450,000 lbf) of thrust. That test also suffered a minor scrub on the 24th, followed by a successful flight one day later, a chapter that Starhopper may now mirror on its second attempted flight, a 150m (500 ft) hop.
Notably, SpaceX CEO Elon Musk took to Twitter just seconds after the rocket’s scheduled liftoff suffered a last-second hold to indicate that Raptor’s torch igniters were proving somewhat finicky relative to the chemical alternative used by SpaceX’s proven Merlin engines.
The CEO later confirmed that that comment was directly related to the 26th’s scrub, indicating that Raptor serial number 06 (SN06) needed to have its igniters inspected prior to a second hop test attempt, now scheduled to occur no earlier than 6pm EDT (22:00 UTC) on August 27th. The gist of the difficulties with Raptor’s igniter starts with the reason that SpaceX is attempting to integrate an entirely new form of ignition into the engine, replacing the methods successfully used over tens or even hundreds of thousands of seconds of firing with the company’s Merlin 1 and Merlin Vacuum engines.
Merlin 1D and MVacD both rely on a relatively simple, reliable, cheap, and easy method of chemical ignition, using a duo of pyrophoric materials known as triethylaluminum-triethylborane (TEA-TEB). When mixed, these materials immediately combust, generating an iconic green flash visible during Falcon 9 and Heavy launches, and thus producing the ‘spark’ needed to start Merlin engines.
Generally speaking, TEA-TEB is an excellent method of igniting rockets, even if it is more of a brute-force, inelegant solution than alternatives. It does, however, bring limitations: every single ignition requires a new ‘cartridge’ be expended, fundamentally limiting the number of times Merlin 1D (and Merlin Vacuum) engines can be ignited before and after liftoff.
This doesn’t even consider the fact that TEA-TEB are extremely complex chemical products that would be next to impossible to produce off of Earth, at least for the indefinite future.
To combat these downsides, SpaceX has designed Raptor with an entirely different method of ignition, known as torch ignition. Technically speaking, Raptor’s power, design, and methalox propellant combine to demand more than a relatively common solution, in which spark plugs are used to ignite an engine. Instead, Raptor uses those spark plugs to ignite its ignition sources, what CEO Elon Musk has described as full-up blow torches. Once ignited, those blow torches – likely miniature rocket engines using the same methane and oxygen fuel as Raptor – then ignite the engine’s methane and oxygen preburners before finally igniting those mixed, high-pressure gases in the combustion chamber.
In simple terms, the fact that Raptor is a full-flow staged-combustion (FFSC) engine means that the pressures it must operate under are extreme, verging on unprecedented in large-scale rocketry. Extremely high-pressure gases (on the order of 3,000-10,000+ psi or 200-700+ bar) are just as difficult to reliably ignite, especially if hypergolic solutions (i.e. TEA-TEB) are off the table.
To get an even ignition – critical to avoid burn-through, minor explosions, and even catastrophic engine failures – Raptor’s torch ignition may actually involve a 360-degree ring of spark plug-lit torches around the point of ignition, an undeniably complex solution.
However, as Musk notes, these significant, “finicky” challenges brought on by Raptor’s exotic ignition method are motivated by the potential benefits such a solution might bring. Relative to Merlin 1D’s TEA-TEB ignition, torch ignition – once optimized and matured into a reliable solution – will permit an almost unlimited number of Raptor ignitions before, during, and after flight.
Avoiding TEA-TEB and other complex chemical igniters also means that Starship will technically be able to launch to Mars or the Moon, perform injection and landing burns, maybe even hop around the surface, and still be able to return to Earth – all without resupply. Such a return voyage would still be predicated on the ability to generate the methane and oxygen propellant needed to fuel Starships, but – assuming that challenge can be solved – torch-lit Raptors would be ready for such a mission. In the event that, say, something like August 26th’s scrub happens to a Starship on Mars, the crew would also be able to get out, inspect Starship’s Raptors, and even replace faulty spark plugs if necessary.
Technically, one could bring lots of spare TEA-TEB cartridges and install those in space or after landing, but those cartridges are quite literally firebombs waiting to ignite, whereas spare spark plugs are entirely inert.
For now, we’ll have to wait for SpaceX technicians to get their eyes and hands-on Starhopper’s lone Raptor engine to verify that its ignition hardware is in good health. If all goes well, Starhopper will attempt its final flight test as early as August 27th.
Update (August 27th): Starhopper is reportedly set for a second attempted 150m (500 ft) flight test today, scheduled to occur no earlier than 5pm EDT (21:00 UTC) on August 27th. Stay tuned for SpaceX’s official Livestream!
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
The Boring Company just doubled its tunneling power in Nashville
The Boring Company’s Prufrock MB2 is commissioned and ready to mine beneath Nashville’s streets.
The Boring Company’s second tunnel boring machine, Prufrock MB2, is officially ready to dig in Nashville. The company confirmed the news on X, posting: “Prufrock-MB2 is ready to mine in Nashville! MB2 commissioning is complete, including the brief 11 rpm rotation shown here. Will MB2 catch up to MB1, who had quite the head start? And Prufrock-MB3 ships in August!”
MB2 arrives with meaningful improvements over its predecessor. Lessons learned from the launch and operation of MB1 have already been applied to MB2 to improve efficiency and prepare the machine for launch.
Traditional tunnel boring machines operate in a stop-and-go cycle, digging roughly five feet, halt, erect precast concrete segments to line the tunnel wall, then resume. That repeated interruption is one of the main reasons conventional tunneling is slow and expensive. Prufrock is designed to install the tunnel liner simultaneously with mining, eliminating the need to stop every five feet. The machine also skips the need for excavated launch pits. Prufrock arrives on a truck, tilts down, and launches into the ground within 24 hours. And when the tunnel is complete, it emerges from the ground and drives to its next launch site on a trailer, eliminating the need for expensive cranes or pit excavation. The machine is also fully electric and runs with zero people in the tunnel during normal operations, controlled remotely from a surface operations center.
Prufrock-MB2 is ready to mine in Nashville! MB2 commissioning is complete, including the brief 11 rpm rotation shown here.
Will MB2 catch up to MB1, who had quite the head start?
And Prufrock-MB3 ships in August! pic.twitter.com/TTrMql2aRg
— The Boring Company (@boringcompany) June 17, 2026
It won’t be long before we hear of another major update on The Boring Company’s Music City Loop project – a planned underground transit network beneath Nashville that would move passengers in electric vehicles through a series of tunnels at highway speeds, and bypassing surface traffic entirely. Nashville was selected in part because of its strong rock conditions that suits the Prufrock machines well, and relatively less regulatory hurdles.
Progress has been steady on multiple fronts. All 37 permits and approvals required ahead of tunneling have been obtained, out of 45 total. Key wins include a fully executed TDOT tunnel permit authorizing 25 miles of tunnel, unanimous airport authority approval for a Nashville International Airport station, and the city’s first residential station agreement serving downtown tower residents.
With MB1 already tunneling, MB2 now commissioned, and MB3 shipping in August, Nashville is becoming something of a live proving ground for scaled tunnel boring. The broader ambition is not limited to one city. The Boring Company’s stated goal is to make underground transportation a practical alternative to surface roads across major metro areas. Nashville is one of many cities, including a successful Las Vegas tunnel system, where that idea is being put to the test at real speed.
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.
The Boring Company just doubled its tunneling power in Nashville
Tesla urges New Jersey owners to oppose new bill that could block Robotaxi
