Tesla Faces March 9 NHTSA Deadline to Hand Over FSD Crash Data as Austin Robotaxi Fleet Crashes at Four Times the Human Rate
NHTSA gave Tesla a final March 9 deadline to deliver crash video and telemetry from its FSD investigation, while data shows Austin robotaxis crash four times more often than human drivers.
Overview
Tesla has until March 9, 2026 to deliver critical crash video, event data recorder files, and CAN bus telemetry to the National Highway Traffic Safety Administration as part of a widening federal investigation into its Full Self-Driving software. The deadline, already extended twice from its original January 19 date, arrives as newly compiled data shows Tesla’s Austin robotaxi fleet is experiencing collisions at roughly four times the rate of human drivers by the company’s own metrics, and potentially eight times the human rate under NHTSA’s broader crash-reporting standards.
What We Know
NHTSA opened investigation PE25012 on October 7, 2025 after linking 58 incidents to vehicles operating with FSD engaged, including cases where cars ran red lights and drifted into opposing traffic lanes. By December, the number of documented incidents had grown to 80, a 60 percent increase drawn from 62 driver complaints, 14 Tesla-filed reports, and four media accounts. The probe covers approximately 2.88 million Tesla vehicles equipped with the software, according to Electrek.
On December 3, 2025, NHTSA issued a sweeping Information Request demanding data on consumer complaints, field reports, crashes, lawsuits, and internal safety assessments. Tesla was originally required to respond by January 19, 2026. On January 12, the company requested a first extension, telling the agency it still had 8,313 records requiring manual review and could process only about 300 per day, as reported by CMU Safety21. A second extension pushed the deadline to March 9 for the most complex materials: crash video, CAN bus data, event data recorder files, and Performance Anomaly Reports.
Meanwhile, Tesla’s Austin robotaxi program continues to generate safety concerns. The fleet, which began offering unsupervised rides on January 22, 2026 using the same FSD software under federal scrutiny, has accumulated at least 14 reported crashes since its June 2025 launch. Five new crash reports were filed in January 2026 alone, covering incidents from December 2025 and January 2026. All involved Model Y vehicles with the autonomous system verified engaged, and included a collision with a fixed object at 17 mph, a crash with a bus while stationary, a collision with a heavy truck at 4 mph, and two incidents where the vehicle backed into objects, according to Electrek.
With approximately 800,000 cumulative miles driven by mid-January, the fleet’s crash rate stands at roughly one incident per 57,000 miles. Tesla’s own Vehicle Safety Report states that the average American driver experiences a minor collision every 229,000 miles, placing the robotaxi fleet at approximately four times the human rate. Under NHTSA’s broader police-reported crash statistics of one incident per roughly 500,000 miles, the fleet’s rate is approximately eight times higher, as reported by Gizmodo.
One July 2025 crash was quietly upgraded in December to include a “Minor W/ Hospitalization” classification, marking the first reported injury requiring hospital treatment from the Austin program, according to Electrek.
What We Don’t Know
Tesla redacts all crash narratives submitted to NHTSA as “confidential business information,” preventing independent assessment of what caused each incident and whether the autonomous system or other factors were primarily responsible. Every other company filing autonomous driving system crash data with NHTSA, including Waymo, Zoox, Aurora, and Nuro, provides detailed incident descriptions.
It remains unclear whether Tesla will meet the March 9 deadline or seek a third extension. The company has characterized the compliance burden as “unduly burdensome” while managing multiple simultaneous NHTSA investigations, including separate probes into delayed crash reporting and door handle defects.
NHTSA has not indicated what enforcement actions it might take if the data reveals systemic safety issues, or whether the investigation could escalate from a Preliminary Evaluation to an Engineering Analysis, the step that typically precedes a recall.
Analysis
The March 9 deadline represents a critical juncture for Tesla’s autonomous driving ambitions. The company has staked its future growth narrative on scaling FSD into a commercial robotaxi business, yet the same software powering that vision is now the subject of a federal safety investigation covering nearly three million vehicles.
The contrast with Waymo is instructive. Waymo now completes over 450,000 fully driverless rides per week across ten cities and has logged more than 127 million miles without a safety driver, with peer-reviewed research suggesting it reduces serious-injury crashes by 90 percent compared to human drivers. When Waymo’s vehicles were caught passing school buses, the company filed a voluntary recall within weeks. Tesla, by contrast, has twice requested deadline extensions to comply with basic data requests and redacts the details of every crash its robotaxis are involved in.
The Austin fleet’s crash rate, while drawn from a relatively small sample of 14 incidents over roughly 800,000 miles, is trending in the wrong direction. Tesla began offering rides without safety monitors in late January 2026, shortly after the month’s initial batch of new crash reports. Whether the March 9 data submission changes the regulatory calculus or leads to further delays will likely shape both the pace of Tesla’s robotaxi expansion and the broader regulatory framework for autonomous vehicles in the United States.