Yes—the premise is accurate, but the date and regulatory context matter. On June 23, 2025, one day after Tesla began limited paid robotaxi rides in Austin, the National Highway Traffic Safety Administration (NHTSA) confirmed that it had contacted Tesla after videos appeared to show the vehicles speeding, entering an opposing lane, braking unexpectedly, and committing other apparent traffic violations.
That contact was not a public finding that Tesla’s robotaxi system was defective, nor did it mean NHTSA had approved or shut down the service. It was part of a broader process of information gathering and oversight that later expanded to Tesla’s automated-driving technology, crash reporting, remote assistance, and the federal rules governing autonomous vehicles.
What happened when Tesla’s Austin robotaxis launched?
Tesla began offering limited paid rides to invited customers in South Austin on June 22, 2025. The initial service included a human safety monitor in the front passenger seat, so it was not an entirely unmonitored public deployment.
The following day, videos circulated online that appeared to show some robotaxis:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
- 【OEM Fit & Plug-and-Play for Tesla Model Y (2020-2024) and Model 3 (2016-2023)】 Specifically designed for Tesla Model Y and Model 3, this HotSunTesTec CarPlay HUD installs quickly in just 50 minutes without modifying your car. The 9.6-inch HD 2.5D screen with a 1920x480 resolution features an ultra-thin bezel for a sleek look and superior visibility, perfectly blending with your Tesla’s interior.
- 【Seamless 60 FPS Wireless CarPlay and Android Auto】 Enjoy smoother, faster CarPlay and Android Auto integration with 60 FPS performance. Use your favorite navigation, music, and apps on split or full screen. Supports Siri and Google Assistant for voice commands, enabling hands-free convenience.
- 【Automotive-Grade Linux System with High-Performance CPU】 Powered by a Linux system and vehicle-grade CPU, this HUD offers 4x faster performance than the previous model with ultra-low power usage, ensuring a stable, long-lasting experience in all driving conditions.
- 【No AC Vent Obstruction and Customizable Interface】 Unlike other models, this HUD is uniquely optimized for the Tesla Model Y and Model 3 to avoid blocking air conditioning vents. Choose from five unique, high-quality UI designs to personalize your HUD interface for a fun and functional driving experience.
- 【Immersive Driving Features & Real-Time Sync】Available in five colors (white, red, black, blue, grey) to match your Tesla’s exterior, this HUD supports steering wheel control, day/night modes, and OTA updates for easy, worry-free software upgrades. Displays real-time vehicle info like turn signals, brake status, speed, and temperature. Additional safety features include Auto-Pilot alerts, Blind Spot Monitoring, Front Collision Warning, Battery Warming, Passenger Seat Adjustment
- Exceeding the speed limit.
- Swerving into an opposing lane.
- Braking suddenly or unexpectedly.
- Making other maneuvers that appeared to violate traffic rules.
Videos can lack context, and an isolated clip does not establish a legally proven violation or a system defect. Nevertheless, NHTSA confirmed on June 23 that it was in contact with Tesla to gather more information about the reported incidents and determine whether further action was necessary.
TechCrunch’s contemporaneous report documented both the Austin launch and NHTSA’s confirmation.
What did NHTSA actually do?
Three separate federal actions are important here. They should not be collapsed into one generic claim that NHTSA “opened a robotaxi investigation.”
1. It contacted Tesla about the Austin incidents
NHTSA said it was gathering information after the videos and reports appeared. That is meaningful federal scrutiny, but “contacted the manufacturer” is more precise than saying the agency had announced a dedicated Tesla robotaxi defect investigation.
Regulatory contact, information requests, and investigations can all be early steps in a safety review. None is, by itself, proof that a vehicle or automated-driving system violated federal law.
2. It requested detailed information about Tesla’s robotaxi plans
On May 8, 2025—before the Austin launch—NHTSA’s Office of Defects Investigation sent Tesla a nine-page information request. The letter asked about the planned service’s technical design and operating model, including:
Rank #2
- Brand: Matchbox
- Batteries required: False
- Batteries included: False
- Which automated-driving system Tesla intended to use.
- Whether Tesla regarded the system as an automated driving system (ADS) or a Level 2 advanced driver-assistance system.
- Planned fleet size at launch and during the following 12 and 24 months.
- Deployment locations and timing.
- Real-time monitoring, teleoperation, and remote assistance.
- The limits on remote control and the responsibilities of remote personnel.
- The duties of in-vehicle safety personnel.
- Sensors, computing hardware, and system architecture.
- Whether Tesla planned to use vehicles that did not fully comply with Federal Motor Vehicle Safety Standards.
- Whether Tesla would seek exemptions from those standards.
- How the robotaxi software related to Tesla’s consumer FSD Supervised product.
The NHTSA information request shows that federal scrutiny was not limited to social-media videos. The agency was also examining how Tesla planned to classify, build, supervise, and operate the service.
3. It later audited Tesla’s crash-reporting compliance
On August 19, 2025, NHTSA opened audit query AQ25002 concerning Tesla’s compliance with Standing General Order 2021-01. NHTSA said it had found numerous Tesla crash reports submitted months after the underlying crashes, even though applicable reporting requirements generally called for reports within one or five days after Tesla learned of a reportable incident.
Free tools Windows power users keep installed
One-click scans. No signup required.
The audit covered an estimated 2.6 million Tesla vehicles subject to the order—not just robotaxis. NHTSA said it was examining the cause and scope of the delays, potentially missing reports, data completeness, and Tesla’s claimed data-collection fix. The AQ25002 document does not establish that every delayed report involved a robotaxi or that Tesla intentionally concealed crashes.
Why the ADS-versus-Level 2 distinction matters
Tesla’s product name “Full Self-Driving” does not determine the federal regulatory classification. What matters is what the system actually does and whether a human driver must remain responsible and attentive.
Level 2 ADAS can control steering and speed, but the human driver must remain fully engaged and responsible for driving. Tesla’s consumer FSD Supervised system is treated as Level 2 driver assistance.
An automated driving system (ADS) performs the driving task within a defined operating design domain. A robotaxi intended to operate without a conventional driver raises a different ADS question, depending on the system and circumstances.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #3
![Matchbox Tesla Model Y, 70 Years 89/100 [White]](https://m.media-amazon.com/images/I/51XQmx0TiDL._SL160_.jpg)
- Toy Vehicle Form: Car
- Theme: Car
That distinction affects reporting obligations, technical questions, supervision requirements, and how regulators interpret a crash. A Tesla with FSD Supervised engaged is not automatically part of the robotaxi fleet, and a crash involving FSD is not automatically evidence about Tesla’s Austin robotaxi service.
What is the Standing General Order?
NHTSA’s Standing General Order on crash reporting requires designated manufacturers and operators to report certain crashes involving ADS and SAE Level 2 ADAS.
For ADS vehicles, a reportable crash can include an incident in which the ADS was engaged within 30 seconds and the crash involved qualifying property damage or injury. For Level 2 systems, reporting generally applies when the system was engaged within 30 seconds and the event involved a vulnerable road user, a fatality, air-bag deployment, or hospital treatment.
The resulting data is useful for regulatory oversight, but NHTSA warns against treating it as a simple safety league table. Reports can be incomplete, duplicated, unverified, or shaped by differences in manufacturers’ telemetry and access to crash information. A reported crash does not automatically prove that the automated system caused it, and the dataset is not necessarily statistically representative of every crash.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsDoes this mean NHTSA is investigating Tesla’s robotaxis?
Not in one clearly defined, publicly announced proceeding covering every robotaxi issue. The most accurate description separates:
- NHTSA’s June 23, 2025 contact with Tesla about apparent Austin incidents.
- The May 8, 2025 information request about Tesla’s planned robotaxi system and deployment.
- Broader federal reviews involving Tesla’s Autopilot, FSD, automated-driving systems, and crash reporting.
- The AQ25002 audit query concerning delayed Standing General Order reports across a large Tesla vehicle population.
An investigation is also not the same as a finding of fault. NHTSA may request records, analyze incidents, and evaluate possible defects before deciding whether enforcement, a recall, or another remedy is warranted.
Does the federal government approve robotaxi launches?
Generally, no. NHTSA says it does not preapprove new vehicle technologies or systems. Manufacturers generally certify that their vehicles comply with applicable federal safety standards. NHTSA can then investigate possible safety defects or violations and enforce the Federal Motor Vehicle Safety Act.
That federal role differs from state and local authority. Texas and local governments may control operational, licensing, traffic, and transportation questions, while NHTSA focuses primarily on federal vehicle-safety requirements, defects, reporting, and recalls.
There was therefore no basis to describe NHTSA as having “approved” Tesla’s Austin robotaxis. There was also no evidence in the cited actions that the agency had issued a general federal ban on the service.
How the federal AV picture changed by 2026
By mid-2026, federal attention had broadened beyond Tesla-specific questions. NHTSA announced work toward the first federal automated-vehicle performance standards, updated the Part 555 exemption process, and authorized a temporary exemption allowing Zoox to commercially deploy up to 2,500 vehicles annually for two years.
NHTSA said its updated guidance would address emergency-responder interaction, safety-management systems, remote assistance, and post-crash behavior. A Zoox exemption does not automatically apply to Tesla; it is evidence that the federal framework is evolving through separate standards and exemption decisions.
On July 8, 2026, NHTSA also called on AV developers to address repeated cases in which driverless vehicles allegedly interfered with emergency responders—for example, by blocking emergency vehicles or failing to respond appropriately to flashing lights, cones, smoke, fire, or flares. The statement was directed at the AV industry broadly, not expressly at Tesla alone. Read the agency’s first-responder safety statement and its AV standards and exemption announcement.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What readers should—and should not—conclude
- Supported: Tesla’s robotaxis attracted NHTSA attention almost immediately after the Austin launch.
- Supported: NHTSA had already sought detailed information about Tesla’s robotaxi architecture and operating plans.
- Supported: Tesla later faced a broader audit query over delayed crash reports.
- Not established: That the online videos alone proved a federal safety defect.
- Not established: That NHTSA had approved Tesla’s robotaxis.
- Not established: That every Tesla crash report involved a robotaxi or FSD.
- Not established: That delayed reporting proved intentional concealment.
Crash counts also cannot be used casually to claim that Tesla is safer or less safe than another AV developer. NHTSA specifically cautions that differences in telemetry, reporting access, duplicates, incomplete data, and incident classification can distort comparisons.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
