DEPLOYDatabase

Incident · Collision

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

On July [XXX], 2026 at 11:54 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Austin, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound on [XXX] in autonomous mode while following a left-hand curve in the roadway.

As the AVRIDE AV proceeded forward, a cyclist operating an e-bike approached from behind on the left while traveling in the wrong direction on the two-way roadway. As the cyclist continued through the left-hand curve, the cyclist lost control and slid to the right, causing the right side of the e-bike to make contact with the left side of the AVRIDE AV.

The AVRIDE AV sustained minor damage. The e-bike did not sustain damage. No tow was required, and no airbags were deployed. The cyclist sustained minor injuries without requiring hospitalization.

Occurred 2026-07-01 · Avride

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 Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-16037)

Machine-readable surfaces

Sources (2)

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

Common questions

What happened in ADS crash report in Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-16037)?
On July [XXX], 2026 at 11:54 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Austin, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound on [XXX] in autonomous mode while following a left-hand curve in the roadway. As the AVRIDE AV proceeded forward, a cyclist operating an e-bike approached from behind on the left while traveling in the wrong direction on the two-way roadway. As the cyclist continued through the left-hand curve, the cyclist lost control and slid to the right, causing the right side of the e-bike to make contact with the left side of the AVRIDE AV. The AVRIDE AV sustained minor damage. The e-bike did not sustain damage. No tow was required, and no airbags were deployed. The cyclist sustained minor injuries without requiring hospitalization.
When did this incident occur?
The incident is recorded as occurring on July 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in ADS crash report in Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-16037)?
The incident is recorded as involving Avride on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to ADS crash report in Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-16037)?
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 Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-16037)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (2 primary) · last reviewed 2026-09-29

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-09-29

Sources by quality tier

2
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 Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-16037).

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 729fe740-7d1d-4f35-b641-aafd56dc1a22