News
Rocket Lab secretly launches revolutionary satellite and readies for US launch debut
Rocket Lab’s recent flawless return to flight mission nicknamed “I Can’t Believe It’s Not Optical,” set the company up for loftier goals in the latter half of 2020 in a big way. Returning to operation after an in-flight anomaly and subsequent investigation is a massive accomplishment for any launcher. Returning to flight and debuting a pathfinder satellite developed and built in-house, however, solidified Rocket Lab as a full end-to-end space systems company.
For good measure, company founder and chief executive officer, Peter Beck, hopes to round out the year by activating two more Electron launchpads – one of which will be the launcher’s first US-based launch location dedicated to supporting missions for the United States government. Furthermore, following Electron’s seventeenth flight, Rocket Lab hopes to recover the expended first-stage booster – and perhaps more importantly, a mountain of data – as a stepping stone to launch vehicle reuse, a practice pioneered and solely dominated by SpaceX.
A return to flight and an introduction to space systems
Just eight weeks after Electron’s ill-fated thirteenth flight resulting in the loss of a second stage and all customer payloads due to an in-flight electrical anomaly, the next Electron was raised at Launch Complex 1 in Mahia, New Zealand. The fourteenth flight of Electron was a dedicated mission for San Francisco-based information services company, Capella Space. Initially announced, the mission deployed a single microsatellite called “Sequoia” to an approximate 500km circular orbit. Peter Beck later confirmed the mission also secretly featured the successful deployment of Rocket Lab’s first in-house designed and built satellite called “First Light.”
“First Light” is a pathfinder spacecraft based on Rocket Lab’s configurable Photon satellite platform. According to Rocket Lab, it exploits Electron’s Kick Stage, “a nimble but powerful extra stage on Electron designed to circularize payload orbits.” The Kick Stage is designed as a satellite bus with extended capabilities to transition into a satellite – Photon – and performing an independent standalone mission. This is exactly what occurred with “First Light.”
Following the deployment of the “Sequoia” microsatellite, Rocket Lab teams signaled the Kick Stage to enable the standalone Photon capabilities. The command transitioned the spacecraft from a delivery vehicle to a fully functional satellite for the very first time. “First Light” serves as the testbed of many upgraded components including improved management systems for power, thermal, and attitude control.
in a statement provided by Rocket Lab Beck said, “Launching the first Photon mission marks a major turning point for space users – it’s now easier to launch and operate a space mission than it has ever been. When our customers choose a launch-plus-spacecraft mission with Electron and Photon, they immediately eliminate the complexity, risk, and delays associated with having to build their own satellite hardware and procure a separate launch.”
Eventually, the extended Photon capabilities of the Kick Stage will be used to support lunar and interplanetary missions. Beck has gone on record many times stating that Rocket Lab is working toward funding a private mission to Venus with a more robust version of the Photon platform which will deploy a probe to collect information about the Venusian atmosphere.
Counting down to Electron’s first launch from Virginia
On September 17, just two weeks after introducing the world to “First Light,” Rocket Lab announced the final successful Electron wet dress rehearsal at its new Launch Complex 2 (LC-2) at the Mid-Atlantic Regional Spaceport in Wallops Island, Virginia.
The wet dress rehearsal is a standard preparatory practice of raising the rocket vertical on the launchpad, fueling the rocket, and conducting a practice run of all countdown systems and procedures ahead of a launch attempt. This gives launch teams the opportunity to ensure that the rocket is prepared for flight and work out any kinks that may arise ahead of sending the vehicle to space. The countdown is carried down to T-0 and then the vehicle is emptied and safed.
Recently, Rocket Lab was granted a five-year Launch Operator License by the Federal Aviation Administration for the LC-2 site enabling the space systems company to support up to ten Electron missions a year from U.S. soil. The new operator license combined with the one previously procured for Launch Complex 1 in New Zealand allows Rocket Lab to support up to 130 flights of the Electron rocket globally per year.
It was speculated that Electron’s next flight – and the first launch from LC-2 in Virginia – would be the dedicated STP-27RM mission coordinated by the U.S. Space Force’s Space and Missile Systems Center. The first from Virginia will launch a single microsatellite for the Air Force Research Laboratory’s Monolith program. However, the first mission from Virginia is still waiting on a debut date to be identified.
In order for Electron to fly from Virginia, NASA must first certify Electron’s Autonomous Flight Termination System (AFTS) – a protective measure that will automatically destroy the rocket in a safe manner should anything anomalous occur during first stage flight. Electron’s AFTS has already previously flown numerous times from New Zealand. The first flight from Virginia, however, will be the first time a vehicle will launch from the Mid-Atlantic Regional Spaceport with an AFTS.
15 launches, 3 launch pads, and a booster recovery
Until then, Rocket Lab is busy preparing for flight fifteen from New Zealand. The recently announced mission, nicknamed “In Focus,” is a rideshare mission featuring nine SuperDove satellites for Planet Labs and one payload for Spaceflight Inc. customer Canon Electronics Inc.
While preparing for the next flight, nearby Rocket Lab is simultaneously wrapping up construction on yet another launch pad. Launch Complex 1B is very much near completion and is expected to be brought online by year’s end. And that’s not the last goal Rocket Lab looks to achieve by the new year.
Beck has time and time again confirmed that the seventeenth flight of Electron will be the first attempt at recovering an expended first stage booster. Eventually, the company will attempt to catch the booster as it is falling back to Earth under the canopy of a parachute by utilizing a helicopter equipped with a specialized grappling hook. The first attempt at recovering a booster is not expected to be quite as elaborate.
Rocket Lab has strengthened the first-stage booster enough to survive the return trip. Until now, the booster has slammed into the ocean water and broken up into small bits. With the assistance of improved software and a deployable parachute, the booster of flight seventeen is expected to softly float back for a gentle water landing with the assistance of “recovery pontoons” as described in a Twitter post by Beck.
As of now, Rocket Lab has not identified any target dates for the upcoming milestones. The company has previously stated that the first mission from Virginia is expected to launch in the third quarter of 2020. Electron’s next flight – “In Focus” – from New Zealand is expected in the first half of October. Rocket Lab will provide future launch and development updates on their social media accounts.
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
