News
SpaceX’s Falcon 9 may soon have company as Rocket Lab reveals plans for Electron rocket reuse
The most prominent launcher of small carbon composite rockets, Rocket Lab, announced plans on Tuesday to recover the first stage of their Electron rocket and eventually reuse the boosters on future launches.
In short, CEO Peter Beck very humbly stated that he would have to eat his hat during the ~30-minute presentation, owing to the fact that he has vocally and repeatedly stated that Rocket Lab would never attempt to reuse Electron. If Rocket Lab makes it happen, the California and New Zealand-based startup will become the second entity on Earth (public or private) to reuse the boost stage of an orbital-class rocket, following SpaceX’s spectacularly successful program of Falcon 9 (and Heavy) recovery and reuse.
What is Rocket Lab?
Rocket Lab – headquartered in Huntington Beach, California – is unique among launch providers because they specialize in constructing and launching small carbon composite rockets that launch from the gorgeous Launch Complex 1 (LC-1) in Mahia, New Zealand. Their production facilities are located in Auckland, New Zealand, where they not only produce their own rockets but also 3D print Rutherford engines, the only orbital-class engine on Earth with an electric turbopump.

Electron’s 1.2-meter (4 ft) diameter body is built out of a super durable, lightweight carbon composite material that relies on custom Rocket Lab-developed coatings and techniques to function as a cryogenic propellant tank. It is powered by 9 liquid kerosene and oxygen (kerolox) Rutherford engines that rely on a unique electric propulsion cycle. The engine is also the only fully 3D-printed orbital-class rocket engine on Earth, with all primary components 3D-printed in-house at Rocket Lab’s Huntington Beach, CA headquarters. Pushed to the limits, a complete Rutherford engine can be printed and assembled in as few as 24 hours.
Currently, Rocket Lab is producing an Electron booster every 20-30 days and flies about once a month out of New Zealand. Since the first operational flight at the end of 2018 Rocket Lab has supported both commercial and government payloads. With a new launch complex (LC-2) coming online in Wallops, Virgina by the end of this year, they look to increase launch frequency, but also widen its market of customers. According to CEO Peter Beck, booster reuse could be a boon for Electron’s launch cadence.

“Electron, but reusable.”
In the world of aerospace, SpaceX is effectively the only private spaceflight company (or entity of any kind) able to launch, land, and reuse orbital-class rockets, although other companies and space agencies have also begun to seriously pursue similar capabilities. Rocket Lab’s announcement certainly brings newfound interest to the private rocket launch community. Reuse of launch vehicle boosters – typically the largest and most expensive portion of any given rocket – is a fundamental multiplier for launch cadence and can theoretically decrease launch costs under the right conditions.
Rocket Lab hopes, more than anything, that recoverability will lead to an increase in their launch frequency and – at a minimum – a doubling of the functional production capacity of the company’s established Electron factory space. This will allow for more innovation and give the company more opportunities to “change the industry and, quite frankly, change the world,” according to founder and CEO Peter Beck.
Unlike like SpaceX’s Falcon 9, propulsive landing is not an option for the small Electron rocket. In fact, cost-effective recovery and reuse of vehicles as small as Electron was believed to be so difficult that Beck long believed (and openly stated) that Rocket Lab would never attempt the feat. Beck claims that in order to land a rocket on its end propulsively – by using engines to slow the booster while it hurdles back to Earth in the way the Falcon 9 booster does – would mean that their small rocket would have to scale up into the medium class of rockets. As Beck stated, “We’re not in the business of building medium-sized launch vehicles. We’re in the business of building small launch vehicles for dedicated customers to get to orbit frequently.”

The main concern that Rocket Lab faces with the daunting task of not using propulsion to land is counteracting the immense amount of energy that the Electron will encounter on its return trip through the atmosphere. In order to return the booster in any sort of reusable condition they will have to decrease the amount of energy that the rocket is encountering which presents in the forms of heat and pressure from ~8 times the speed of sound to around 0.01 times the speed of sound. This decrease also needs to occur in around 70 seconds during re-entry and according to Beck “that’s a really challenging thing to do.” Beck went on further to explain that this really converts into dissipating about 3.5 gigajoules of energy which is enough energy to power ~57,000 homes.
Breaking through “The Wall”
When re-entering the atmosphere the energy that any spacecraft endures creates shockwaves of plasma which must be diverted away in order to protect the integrity of the spacecraft. An example of this can be seen during the re-entry of a SpaceX fairing half. Beck explains that “the plasma around those shockwaves is equal to about half the temperature of the (surface of the) sun” which can reach temperatures as high as 6,000 degrees fahrenheit. It also endures aerodynamic pressure equal to that of three elephants stacked on top of the Electron, according to Beck. His team refers to these challenges as breaking through “The Wall.”Beck explains that they will attempt to solve these problems differently using passive measures and aerodynamic decelerators.
The Wall is something that Beck and his team have been trying to tackle for some time now. Since the Electron began operational flights at the end of 2018 data has been collected to inform the problem solving process. In total Electron has successfully completed 7 flights, with its 8th scheduled to occur within the coming days. Beck explains that flights 6 and 7 featured data collection done through 15,000 different collection channels on board of Electron. The upcoming eighth flight will feature an advanced data recording system nicknamed Brutus. This new recording system will accompany Electron on the descent, but will survive while the booster breaks up as usual. It will then be collected and the data will be evaluated and used to further inform the decision making process for how to best help Electron survive its fall back to Earth.
Catching rockets with helicopters
Once Rocket Lab breaks through The Wall and effectively returns Electron without harm, the booster will need to be collected before splashing down into corrosive saltwater. This was demonstrated to be done via helicopter which according to Beck is “super easy.”
An animation depicts a helicopter leaving a dedicated recovery vessel to capture the Electron booster after it deploys a parafoil and begins gliding. The helicopter will intercept the booster’s parachute using a hook and will then carry the booster back to the recovery vessel, where technicians will carefully secure it.



The entire goal of recovering a booster is to be able to reuse it quickly. Beck explains that since Electron is an “electric turbopump vehicle…in theory, we should be able to put it back on the pad, charge the batteries up, and go again.”
Although this goal is ambitious, it is one that – if achieved – will significantly impact the launch community in very positive ways. Not only will the option of rapid reusability open up, but so will opportunity for more agencies to engage in the world of satellite deployment. The Electron currently costs anywhere between $6.5 – 7 million per launch to fly. If the production cost of a new booster is removed space becomes attainable for many more customers.
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.
News
Tesla urges New Jersey owners to oppose new bill that could block Robotaxi
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.
News
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
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.