Incident · Collision
Tesla robotaxi crash count rises to 14 in Austin, roughly 4x human driver rate
Federal crash reports show Tesla's Austin robotaxi pilot logged 14 crashes in ~800,000 miles. Rate roughly four times average human driver. Five new crash reports in January 2026.
Occurred 2026-02-17 · Tesla Robotaxi (Model Y ADS) at Orlando, Florida, USA · Tesla · Orlando, Florida, USA · Robotaxis · Investigated by NHTSA
How to read this record
Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.Machine-readable surfaces
- Markdown mirror: /incidents/collision-2026-02-17-tesla.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/9e843c1e-5a78-4d3a-bf60-b620ee418d0b
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Status history
- Active · 2026-07-03 · agent:depth
Common questions
What happened in Tesla robotaxi crash count rises to 14 in Austin, roughly 4x human driver rate?
When did this incident occur?
What robot was involved in Tesla robotaxi crash count rises to 14 in Austin, roughly 4x human driver rate?
Has anyone responded to Tesla robotaxi crash count rises to 14 in Austin, roughly 4x human driver rate?
What is the current status of Tesla robotaxi crash count rises to 14 in Austin, roughly 4x human driver rate?
Methodology: Verified · 1 source (no primary) · last reviewed 2026-07-14
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-07-14
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Tesla robotaxi crash count rises to 14 in Austin, roughly 4x human driver rate.Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID 9e843c1e-5a78-4d3a-bf60-b620ee418d0b