Connect with us

News

SpaceX wants to unleash Starhopper but longer Raptor test fires come first

SpaceX has reportedly fired a Raptor engine for more than 40 seconds, a necessary step along the path to untethered Starhopper test flights. (SpaceX & NASASpaceflight/bocachicagal)

Published

on

According to SpaceX CEO Elon Musk, the next round of Starhopper activity will focus on removing the spacecraft prototype’s tethers and performing far more substantial hop tests.

Longer tests demand that SpaceX begins expanding the known performance envelope of its full-scale Raptor engine. Towards that end, longer-duration tests would need to be done at the company’s McGregor, TX development facilities to reduce risk, tests that Musk confirmed are already well underway. A recent Raptor static fire reportedly lasted no less than 40 seconds, more than enough time for a single-engine Starhopper to significantly expand both the maximum altitude and velocity of future hop tests. In support of the upcoming Starhopper test campaign, significant construction work is also ongoing at SpaceX’s Boca Chica test and development facilities.

Starhopper awaits its return to hop testing, April 24th. (NASASpaceflight – bocachicagal)

Unleashing the Hopper

During the months of March and April, SpaceX’s South Texas team effectively completed Starhopper and put the prototype through its first real tests. The process began with tank proof tests in which Starhopper’s tanks were filled with liquid nitrogen – relatively neutral and unreactive – to safely identify and repair any leaks, while also subjecting the vehicle to cryogenic temperatures. The proof testing also put the newly installed ground systems (GSE) and vehicle-pad connection hardware through their paces before moving to Starhopper’s nominal liquid oxygen and liquid methane propellant.

Following at least half a dozen or so wet dress rehearsals (WDRs) that saw Starhopper loaded with LOx and methane, SpaceX technicians analyzed the health of the prototype and soon began live tests with a Raptor engine installed. Designed to produce no less than 2000 kN (450,000 lbf, 205 mT) of thrust at full throttle, Raptor offers more than twice the max thrust of the latest variant of the Merlin 1D engine that powers Falcon 9 and Heavy (941 kN or 212,000 lbf). In other words, a single Raptor should be more than enough to lift Starhopper off the ground 150+ tons of propellant aboard.

In the above tweets, Musk indicates that Starhopper’s next step will be untethered hop tests powered by one Raptor engine. This is further supported by confirmation that Raptor completed its longest static fire test yet on April 27th.

After several unsuccessful test attempts, Starhopper completed two static fires (<10s combined) and hopped – tethered – a handful of feet off the ground on April 3rd and 5th, three weeks after Raptor was first installed. Days later, the lone Raptor engine was removed from Starhopper and shipped back to SpaceX’s Hawthorne, CA factory or McGregor, TX testing facilities for post-test analysis and inspection. In short, SpaceX used Starhopper as a sort of ad hoc test stand for the second serial Raptor (SN02) produced, completing two major acceptance tests simultaneously.

A handful of concise tweets published by Musk in the last few days of April implicitly confirmed that the next steps for Starhopper involved untethered flights off its South Texas pad, once again powered by a single Raptor engine. As both the prospective altitudes and flight times rise for future Starhopper tests, so do the risks posed to SpaceX’s adjacent facilities and the prototype itself. To minimize those risks and progress the Raptor program as a whole, SpaceX has been extensively testing the third serial Raptor (SN03) at its McGregor facilities. Instead of a rushed test regime similar to the one that almost completely destroyed Raptor SN01 less than two weeks after testing began, SN03 is participating in a more cautious and systematic series of tests.

Technicians work inside Starhopper’s LOx tank on April 22nd. (NASASpaceflight – bocachicagal)
While almost impossible to visualize the changes from a flat perspective, several dozen trucks of dirt and concrete were delivered to Starhopper’s pad last week. (NASASpaceflight – bocachicagal)

Confirmed by Elon Musk, this included significantly increasing the length of Raptor SN03’s latest static fires, culminating in an April 27th test that lasted ~40 seconds. Above all else, long test fires are necessary to demonstrate that Raptor can reliably operate for dozens of seconds at a time, given that any failure leading to a loss of thrust could cause Starhopper – basically a controlled explosive device – to fall out of the sky. The famous Musk/SpaceX ethos of moving fast and breaking things does not preclude a pragmatic attitude towards the destruction of facilities and prototypes that could take months and millions of dollars to rebuild.

The ETA of future hop tests is unclear. For the time being, it appears that SpaceX’s South Texas facilities will be caught up in construction work for at least another week. Whether or not Raptor SN03 is next in line for installation on Starhopper, SpaceX will likely put it through several more long-duration static fires before moving ahead with untethered hop tests. All things considered, the rough Starship prototype is unlikely to restart powered testing for another two or so weeks. Stay tuned!

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

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.

Published

on

By

boring-company-prufrock-1-2

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.

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.

Continue Reading

News

Tesla urges New Jersey owners to oppose new bill that could block Robotaxi

Published

on

Credit: Grok

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.

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.

Continue Reading

News

Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest

Published

on

Credit: TESLARATI

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.

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.

Continue Reading