Tesla Austin robotaxi fleet logs 14 crashes prompting NHTSA investigation
Tesla's robotaxi fleet in Austin recorded 14 crashes over 800,000 miles of operation. This data was disclosed to NHTSA and is part of a broader safety investigation.
Tesla's robotaxi fleet reported 14 crashes to NHTSA after logging approximately 800,000 miles.
Key facts
- What
- Tesla's robotaxi fleet in Austin recorded 14 crashes over 800,000 miles of operation.
- Incident date
- Feb 1, 2026
- Who
- Tesla
- Failure mode
- Tool Misuse
- AI surface
- Chatbot
- Severity
- High
What happened
Tesla's Austin robotaxi fleet logged approximately 800,000 miles between June 2025 and February 2026. During this period, the fleet reported 14 crashes to the National Highway Traffic Safety Administration. These incidents have contributed to an ongoing investigation into the safety performance of the FSD system.
What broke inside the model
- 01 · TriggerThe agent selects the correct tool.
- 02 · Model stepIt fills the call with the wrong arguments.
- 03 · Control gapNo validation checks the arguments first.
- 04 · FailureThe tool runs against the wrong target.
- 05 · ConsequenceThe wrong record, account, or system is hit.
At the tool call, the arguments point at the wrong target.
The autonomous driving system failed to prevent collisions while operating in autonomous mode. These failures occurred across multiple incidents in an urban environment, indicating a gap in the system's safety performance during deployment.
What it cost
Sources
- PressTesla’s FSD: 10 billion miles, but no magical milestone for autonomyelectrek.co
- PressTesla Discloses Two Robotaxi Crashes to NHTSAteslarati.com
- Court FilingTesla FSD Investigation 2026aguiarinjurylawyers.com
Cite this entry
https://failureindex.ai/failures/tesla-austin-robotaxi-fleet-logs-crashesAI Failure Index. "Tesla Austin robotaxi fleet logs 14 crashes prompting NHTSA investigation" (FI-0309). Realm Labs. https://failureindex.ai/failures/tesla-austin-robotaxi-fleet-logs-crashes (indexed Jun 5, 2026).Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0309. Full dataset at /data.
Note from Realm Labs, the Index steward
How Realm would have caught this
- OmniGuard
- AgentRealm
Realm can inspect a tool call against the user's actual intent before it runs, and hold calls whose arguments or target do not match what was asked, so the wrong tool or the wrong arguments never reach the system of record.