Incident · Regulatory action
NHTSA opened an investigation into Avride after 16 robotaxi crashes in Dallas and Austin
On May 6, 2026, NHTSA's Office of Defects Investigation opened an investigation into Avride after identifying 16 crashes (December 2025–March 2026) involving its Hyundai Ioniq 5 robotaxis in Dallas and Austin, with one minor injury. The crashes involved vehicles executing lane changes into other vehicles, failing to slow or stop behind cars, and striking stationary objects (including a dumpster); most occurred at speeds below 20 mph while an in-vehicle safety operator was present, with the safety monitor attempting to intervene in only one.
NHTSA described the pattern as 'inappropriate assertiveness and insufficient competence,' noting it 'may also constitute traffic safety violations.' The minor injury occurred in December 2025 when an Avride vehicle clipped the open door of a parked pickup truck; it was reported later via insurance and did not require hospitalization.
Occurred 2026-05-06 · Avride delivery robot at Bowling Green, Ohio, USA · Avride · Bowling Green, Ohio, USA · Sidewalk delivery · 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/avride-nhtsa-probe-16-crashes-2026-05.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/cc5e3f13-0bd6-405f-a68a-a87696b73e79
- Data documentation: /data
- Query this programmatically: Deploy MCP
Outcomes (1)
- regulatory actionverified
Revision history (1)
- 2026-06-05 · outcome_class
Outcome rows carry verification_posture independently. Revision events carry basis (verified_court_filing, verified_insurance, reported_press, estimate, undisclosed). The framework records outcomes only when verifiable; absence is honest absence, not a claim of no-impact.
Sources (4)
- NHTSA probe, crash narratives (door clip, van lane-change, dumpster), one safety-monitor intervention · https://techcrunch.com/2026/05/08/uber-partner-avride-is-under-investigation-for-self-driving-crashes/ · 2026-05-08
- NHTSA ODI 'competence of' Avride ADS; injury Dec 2025 truck-door clip · https://thenextweb.com/news/avride-uber-robotaxi-crashes-nhtsa-investigation · 2026-05-08
- 16 crashes Dec-Mar, property damage + one minor injury, below 20 mph, safety operators present · https://www.nbcdfw.com/news/local/robotaxi-operator-under-investigation-for-crashes-in-dallas/4023503/ · 2026-05-12
- https://www.nhtsa.gov/recalls?nhtsaId=DP26002
Common questions
What happened in NHTSA opened an investigation into Avride after 16 robotaxi crashes in Dallas and Austin?
When did this incident occur?
What robot was involved in NHTSA opened an investigation into Avride after 16 robotaxi crashes in Dallas and Austin?
Has anyone responded to NHTSA opened an investigation into Avride after 16 robotaxi crashes in Dallas and Austin?
What is the current status of NHTSA opened an investigation into Avride after 16 robotaxi crashes in Dallas and Austin?
Methodology: Verified · 4 sources (1 primary) · last reviewed 2026-07-21
Verification posture
Verified
High confidence
Review state
Stable
Last reviewed 2026-07-21
Sources by quality tier
- 2
- unclassified
- Unclassified source
- 1
- secondary-industry-publication
- Industry publication
- 1
- primary-regulatory-filing
- Regulatory filing
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for NHTSA opened an investigation into Avride after 16 robotaxi crashes in Dallas and Austin.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 cc5e3f13-0bd6-405f-a68a-a87696b73e79