DEPLOYDatabase

Incident · Collision

ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13952)

On January [XXX], 2026 at 4:30 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, Texas on [XXX] at the intersection with San Jacinto Street. The AVRIDE AV was traveling northwestbound on [XXX] engaged in autonomous mode when a passenger car entering [XXX] from [XXX] proceeded to drive into the intersection without stopping at the stop sign.

The front side of the passenger car made contact with the right-side doors of the AVRIDE AV. The AVRIDE AV stayed at the location of the collision but the passenger car drove away from the scene. The AVRIDE AV’s airbags deployed and the vehicle required towing.

Both vehicles sustained damage. Rider and the AV Safety Driver alleged minor injuries. Rider was transported from the scene via self transport to the hospital. A police report was filed.

Occurred 2026-01-01 · Avride delivery robot at Bowling Green, Ohio, USA · Avride · Bowling Green, Ohio, USA · Sidewalk delivery

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.
Track ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13952)

Machine-readable surfaces

Sources (1)

  1. https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-31101-13952

Common questions

What happened in ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13952)?
On January [XXX], 2026 at 4:30 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, Texas on [XXX] at the intersection with San Jacinto Street. The AVRIDE AV was traveling northwestbound on [XXX] engaged in autonomous mode when a passenger car entering [XXX] from [XXX] proceeded to drive into the intersection without stopping at the stop sign. The front side of the passenger car made contact with the right-side doors of the AVRIDE AV. The AVRIDE AV stayed at the location of the collision but the passenger car drove away from the scene. The AVRIDE AV’s airbags deployed and the vehicle required towing. Both vehicles sustained damage. Rider and the AV Safety Driver alleged minor injuries. Rider was transported from the scene via self transport to the hospital. A police report was filed.
When did this incident occur?
The incident is recorded as occurring on January 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13952)?
Avride delivery robot by Avride is the recorded robot involved in this incident at Bowling Green, Ohio, USA.
Has anyone responded to ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13952)?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13952)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 1 source (1 primary) · last reviewed 2026-08-23

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-08-23

Sources by quality tier

1
primary-regulatory-filing
Regulatory filing

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13952).

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 ab130e6b-063b-44be-b96f-eb6b6e352a83