DEPLOYDatabase

Incident · Collision

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

On April [XXX], 2026 at 9:29 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the left lane on [XXX] in autonomous mode when it began to slow down and come to a stop while staying in the left lane.

An SUV was traveling further behind the AVRIDE AV in the left lane and a pickup truck was traveling in the right lane alongside the SUV on [XXX]. As the SUV approached the AVRIDE AV, it moved to the right lane to go around the AVRIDE AV.

This maneuver resulted in the right side of the SUV making contact with the left side of the pickup truck. Neither the SUV nor pickup truck made contact with the AVRIDE AV. The SUV and pickup truck sustained damage.

The AVRIDE AV sustained no damage. No injuries were reported.

Occurred 2026-04-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-15016)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-15016)?
On April [XXX], 2026 at 9:29 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the left lane on [XXX] in autonomous mode when it began to slow down and come to a stop while staying in the left lane. An SUV was traveling further behind the AVRIDE AV in the left lane and a pickup truck was traveling in the right lane alongside the SUV on [XXX]. As the SUV approached the AVRIDE AV, it moved to the right lane to go around the AVRIDE AV. This maneuver resulted in the right side of the SUV making contact with the left side of the pickup truck. Neither the SUV nor pickup truck made contact with the AVRIDE AV. The SUV and pickup truck sustained damage. The AVRIDE AV sustained no damage. No injuries were reported.
When did this incident occur?
The incident is recorded as occurring on April 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-15016)?
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-15016)?
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-15016)?
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-15016).

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 9382939f-a12b-4eab-b49d-ed373fb1e8cc