News
SpaceX urges Congress to expedite commercial spaceflight regulation reforms
Speaking in a Congressional hearing on the morning of June 26th, SpaceX Director of Government Affairs Caryn Schenewerk reaffirmed the company’s commitment to conducting “more than 25 [launches]” in 2018, a feat that will require a ~50% increase in launch frequency over the second half of the year.
Related to the focus of this particular hearing, namely regulatory reform, Representative Rick Larsen (WA-2) appeared to speak for everyone when he mirrored the four panelists’ sense of urgency for beginning the process of reforming federal space launch regulations by asking for an informal meeting outside the doors of the chamber once the session concluded, stating that “it’s that urgent.” In order for companies like SpaceX (and eventually Blue Origin) to be able to sustainably and reliably reach cadences of one launch per week in the near future, the currently cumbersome and dated launch licensing apparatus will almost invariably require significant reforms.
Pressure to remove artificial bottlenecks growing
Two primary problems were identified by the Air Line Pilots Association (ALPA), ULA, Blue Origin, and SpaceX officials present before the Congressional committee: the extreme sluggishness of licensing and the similarly obtuse brute-force integration of launch vehicle operations with the federal systems of air traffic control tasked with safely orchestrating tens of thousands of aircraft flights daily.
Whereas nominal orbital rocket launches result in vehicles like SpaceX’s Falcon 9 spending less than 90 seconds of real time within the bounds of that controlled airspace, the massive and disruptive “keep-out zones” currently required by the FAA for rocket launches frequently disrupt air traffic for more than 100 times as long. According to Ms. Schenewerk, SpaceX believes it already possesses the capabilities to integrate live Falcon 9 and Heavy telemetry with air traffic control, allowing those keep out zones to be dramatically compressed and highly responsive to actual launch operations, similar to how aircraft traffic is dealt with today.
- Falcon 9 1046’s Block 5 upper stage shown on its May 11 debut launch with Bangabandhu-1. SpaceX’s rockets already provide rich telemetry live to the company’s launch controllers. (SpaceX)
- After CRS-15, all orbital launches will be use Block 5 boosters and upper stages. The upgraded rocket’s next launch is NET July 20. (Tom Cross)
On the specific launch licensing side of this regulatory coin, SpaceX, Blue Origin, and ULA all expressed distaste for current standards, in which a worst-case scenario could see a launch provider forced to wait more than 200 days (up to eight full months) from the moment of filing to a launch license grant. Worse, even slight adjustments to a granted launch license require launch providers to resubmit themselves to that 200+ day process, effectively making timely modifications undependable exceptions to the rule.
Old rules, new rockets
The real barrier to these common-sense regulatory reforms is quite simply the extraordinary sluggishness of the FAA and those tasked with updating its guidelines and regulatory structures. Rep. Larsen was not exaggerating when he stated that he foresaw Congress choosing to delay those reforms by another 5+ years if given the opportunity, and it was thus likely a relief for the panel of witnesses (PDF) to hear him agree that these reforms must be pursued with the utmost urgency. In its current state, the FAA’s launch licensing is liable to be utterly swamped by the imminent introduction of multiple new smallsat launch providers on top of the already lofty launch cadence ambitions of SpaceX, ULA, and Blue Origin, as well as Orbital ATK to a lesser extent.
With SpaceX leading the charge, the American launch industry is already a year or more into a true renaissance of American spaceflight, and the FAA is simply not equipped to handle it. If reforms can be completed with haste rarely seen in Congress, the federal government can at a minimum ensure that it does not become a wholly artificial and preventable bottleneck for that explosion of domestic spaceflight activity.
- SpaceX’s Demo Mission-1 Crew Dragon seen preparing for vacuum tests at a NASA-run facility, June 2018. (SpaceX)
- A Falcon 9 fairing during encapsulation, when a launch payload is sealed inside the fairing’s two halves. This small satellite is NASA’s TESS, launched in April 2018. (NASA)
- A combination of scientific satellites and five Iridium NEXT communications satellites preparing for launch in May 2018. (NASA)
- Telesat’s SSL-built Telstar 19V conducts testing in an anechoic chamber before launch, currently NET July 19. (SSL)
Speaking of that activity, SpaceX is scheduled to begin its H2 2018 manifest push with as many as six Falcon 9 launches (five with Block 5 boosters) over the next ~60 days. Barring an abrupt increase in rocket booster production speeds, sources have confirmed that those 2-3 summer months will likely also feature one of the first rapid Falcon 9 Block 5 reuses, potentially seeing one of SpaceX’s highly-reusable rockets complete two orbital launches in approximately one month (30-50 days). That will, of course, depend upon both customer agreeability and the availability of rockets and launch facilities, but the goal of a rapid Block 5 reuse before summer’s end still stands, at least for now.
Up next is CRS-15, which will see the last orbital Block 4 Falcon 9 launch a flight-proven Cargo Dragon to the ISS with several thousand pounds of supplies in tow, with liftoff scheduled for NET 5:42 am EDT, June 29.
Follow us for live updates, peeks behind the scenes, and photos from Teslarati’s East and West Coast photographers.
Teslarati – Instagram – Twitter
Tom Cross – Twitter
Pauline Acalin – Twitter
Eric Ralph – Twitter
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.





