News
Rocket Lab channels SpaceX-like rapid launch capability in July 4 Electron mission
The prominent launcher of dedicated small satellite launches, Rocket Lab, looks to achieve SpaceX-like rapid launch capability of its Electron rocket. The company is targeting its shortest turn around time between missions from the same launch pad. Just three weeks ago, Rocket Lab returned to operational launch status following the easement of Covid-19 restrictions at the company’s Launch Complex 1 in Mahia, New Zealand. The Electron rocket completed its twelfth mission nicknamed “Don’t Stop Me Now” which supported a rideshare payload of five smallsats to orbit. Now, Rocket Lab is ready for its third mission of 2020 – the second in just three weeks – with Electron’s thirteenth mission “Pics Or It Didn’t Happen.”
The launch window for #PicsOrItDidntHappen opens on 3 July UTC. Lift-off will take place from Rocket Lab Launch Complex 1 Pad A on the Mahia Peninsula. pic.twitter.com/01sDCXVj03
— Rocket Lab (@RocketLab) June 15, 2020
Rideshare mission of space cameras
The “Pics Or It Didn’t Happen” mission features a rideshare manifest consisting of seven small satellite payloads for customers Planet, In-Space Missions, and rideshare and mission manager Spaceflight Inc.’s customer Canon Electronics. The majority of payloads are Earth-imaging satellites inspiring the “Pics Or It Didn’t Happen” mission nickname. The primary payload, Canon Electronics Inc.’s CE-SAT-IB microsatellite, will demonstrate the company’s high definition and wide-angle Earth-imaging capabilities and will serve as a testbed for future opportunities of mass production. Also aboard Electron is five of Planet’s latest generation SuperDove (Flock4e) Earth-observation satellites equipped with new sensors to produce higher quality images of Earth’s landmass on a near-daily basis. The UK enterprise In Space Missions provides the final payload with its maiden Faraday-1 6U CubeSat. According to In Space Missions, Faraday-1 is “the first in a series of satellites that will provide a turnkey service for commercial customers and research organizations wanting to access to space at a competitive and affordable cost.” Currently, In Space Missions has four more satellites under contract with the Faraday service.
Rocket Lab’s carbon composite Electron booster propelled by nine 3D-printed Rutherford sea-level engines capable of 36,000lbf (162kN) of thrust will send all payloads to a 500km sun-synchronous low Earth orbit at an inclination of 97.5 degrees.
It's almost time to go to space! Today's mission will see seven small sats launched to a 500 km circular orbit for @SpaceflightInc customer @Canon, as well as small sat operators @planetlabs and @Heads_InSpace. pic.twitter.com/mMKENVBeLa
— Rocket Lab (@RocketLab) July 4, 2020
Rapid launch capability within reach
According to Rocket Lab, a new Electron booster is produced in-house approximately every eighteen days at its production facility in Auckland, New Zeland. While Electron currently only launches from Launch Complex 1 on New Zeland’s Mahia Peninsula, Rocket Lab looks to further open small satellite access to orbit and expand its launching capabilities with two more operational launch complexes targeted to begin service later this year. The Mahia Peninsula location has recently undergone expansion, adding the neighboring Launch Complex 1B while a third launch location, Launch Complex 2, has been opened at the Mid-Atlantic Regional Spaceport in Wallops Island, Virginia.
Lots of launch pads, we got ‘em. Electron is on the pad at LC-1A this week with a front row view of construction progress on LC-1B. pic.twitter.com/ijZAVRc6yV
— Rocket Lab (@RocketLab) July 1, 2020
Rocket Lab Founder and CEO, Peter Beck, states that multiple launch locations “enables our small sat operators to do more, spend less, and get to orbit faster” and that “Rocket Lab has eliminated the small sat waiting room for orbit. We’ve focused heavily on shoring up our rapid launch capability in recent years and we’re proud to be putting that into practice for the small sat community with launches just days apart.”
The rocket backlog. pic.twitter.com/AhHlbNvEmq
— Peter Beck (@Peter_J_Beck) May 15, 2020
With an expansive backlog of Electron boosters, Rutherford engines, and the capability to soon launch missions back-to-back from neighboring launchpads Rocket Lab aims to break into the market of rapid launch capability joining the likes of SpaceX and its Falcon 9 rocket which has launched 91 times (89 times successfully) since 2010. The company also looks to break into the booster recovery market also pioneered by SpaceX.
Earlier this year, Rocket Lab completed a successful mid-air recovery demonstration of a parachute equipped test article with a helicopter and a specially designed grappling hook. Beck recently revealed on Twitter that Rocket Lab is targeting the seventeenth flight of the Electron to debut fully operational recovery efforts of the first stage booster to occur at some point before year’s end.
The “Pics Or It Didn’t Happen” mission previously scheduled for July 3rd, moved to July 5th, then pushed up to July 4th is now targeting liftoff NET 21:19 UTC/5:19 pm EDT from LC-1 in New Zealand taking advantage of more favorable launch weather conditions. Rocket Lab has stated on Twitter, however, that there is a “relatively high chance” of the launch attempt scrubbing to a later date as the possibility of high ground winds still persists. Should they be needed, backup launch opportunities extend through July 16th.
The “Pics Or It Didn’t Happen” Electron and payload are currently vertical at LC-1 ahead of the launch attempt. A Livestream of the effort will be made available approximately fifteen minutes ahead of liftoff posted to the company’s social media accounts and available on the company’s website: www.rocketlabusa.com/live-stream.
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.
Cybertruck
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
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.