Connect with us

News

Rocket Lab’s 12th Electron mission “Don’t Stop Me Now” ready for launch

A Rocket Lab Electron rocket is pictured on the launch stand during a wet dress rehearsal ahead of the twelfth operational launch from LC-1 in New Zealand. ( Photo Credit: Rocket Lab)

Published

on

During the height of the global coronavirus pandemic, SpaceX and United Launch Alliance (ULA) missions from Florida were deemed “critical infrastructure” by the US federal government. This allowed the launchers to create safe working environments supporting rocket production and steady launch cadences. However, the nation’s most prominent launcher of smallsats, Rocket Lab, headquartered in Long Beach, California took a different approach halting all production and launch related operations. Although headquartered in the US, Rocket Lab manufactures its Electron rocket in Auckland, New Zealand, and launches from its Launch Complex 1 on New Zealand’s Mahia Peninsula.

An aerial photo depicts Rocket Lab’s Launch Complex 1 in Mahia, New Zealand identifying the payload and fairing integration cleanrooms, and the operational Pad A and Pad B scheduled to come online later this year. (Credit: Rocket Lab)

Soon after the New Zealand government initiated a strict nationwide Level 4 lockdown requiring all residents, except essential workers, to remain at home on March 23rd, Rocket Lab stood down from operational missions. Unlike in the United States, the launching and production of rockets were not deemed critical in New Zealand and could not proceed. The lockdown went into place just five days ahead of the company’s scheduled twelfth launch of Electron on March 30th. Rocket Lab announced that the “Don’t Stop Me Now” launch (named in honor of a Rocket Lab board member that recently passed away) would be postponed but did not announce a new launch date as, at the time, it was unknown just how long the nationwide Level 4 lockdown would last.

In early May, Rocket Lab was allowed to return to operational status as pandemic restrictions began to lift in New Zealand. Company founder and chief executive officer, Peter Beck, announced on Twitter that the Electron rocket had returned to LC-1 to complete a wet dress rehearsal (WDR) ahead of announcing a new targeted launch date. Rocket Lab then confirmed that all WDR objectives had been successfully met and the twelfth Electron mission would be proceeding to a targeted launch date in early June.

Rocket Lab was quick to return to launch procedures as the Electron vehicle and LC-1 remained in “a state of readiness throughout the COVID-19 lockdown.” In a statement issued soon after the successful WDR, the company assured that “enhanced health and safety processes will be implemented for this launch in line with government health advice to protect Rocket Lab personnel. These measures include physical distancing, split shifts, maintaining contact tracing registers, and enhanced cleaning procedures.”

Advertisement

The twelfth “Don’t Stop Me Now” Electron mission is designated as a rideshare which will carry multiple smallsat payloads to orbit for NASA, the National Reconnaissance Office (NRO), and University of New South Wales (UNSW) Canberra Space. Electron’s Kick Stage propelled by the 3D-printed Curie engine will deliver the ANDESITE (Ad-Hoc Network Demonstration for Extended Satellite-Based Inquiry and Other Team Endeavors) spacecraft developed by teams at Boston University under NASA’s CubeSat Launch Initiative (CSLI). It will use a series of minisatellites to measure the electrical currents of the Earth’s magnetic field from low Earth orbit. The payload carried for the NRO, Rapid Acquisition of a Small Rocket (RASR) contract vehicle, follows a previously NRO-dedicated mission launched in January 2020. Finally, the twelfth launch of the Electron will also support the M2 Pathfinder (M2PF) communications satellite to low Earth orbit UNSW Canberra Space.

“Don’t Stop Me Now” has a fourteen day launch widow extending from June 11th to June 24th with a daily launch opportunity during a two-hour window 04:43 – 06:32 UTC (00:43 – 02:32 EDT). The Rocket Lab team is currently counting down to the first launch attempt scheduled for Thursday, June 11th at the top of the window at 04:43UTC (00:43 EDT) from LC-1 in Mahia, New Zealand. Fifteen minutes ahead of the launch attempt, a live stream will be posted to Rocket Lab’s social media accounts and made available on the company’s website: www.rocketlabusa.com/live-stream.

Advertisement

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.

Space Reporter.

Advertisement
Comments

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

Cybertruck

Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK

Published

on

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.”

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.

Continue Reading