DEPLOYDatabase

Incident · Collision

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

On December [XXX], 2025 at 7:54 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southeastbound in autonomous mode in the center lane on [XXX] when it came to a stop at a red light at the intersection with [XXX]. While the AVRIDE AV was stopped, a tow truck traveling in the right lane began to enter the AVRIDE AV€™s lane of travel. There was sufficient space for the tow truck to move into the lane while the AVRIDE AV remained stopped. When the traffic signal turned green, both vehicles began to proceed slowly into the intersection. The tow truck then came to an abrupt stop while the light remained green. The safety driver of the AVRIDE AV applied the brakes, but due to the sudden stop by the tow truck, the front of the AVRIDE AV made contact with the rear of the tow truck. Both vehicles sustained damage. No injuries were reported.

Occurred 2025-12-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.

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13625)?
On December [XXX], 2025 at 7:54 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southeastbound in autonomous mode in the center lane on [XXX] when it came to a stop at a red light at the intersection with [XXX]. While the AVRIDE AV was stopped, a tow truck traveling in the right lane began to enter the AVRIDE AV€™s lane of travel. There was sufficient space for the tow truck to move into the lane while the AVRIDE AV remained stopped. When the traffic signal turned green, both vehicles began to proceed slowly into the intersection. The tow truck then came to an abrupt stop while the light remained green. The safety driver of the AVRIDE AV applied the brakes, but due to the sudden stop by the tow truck, the front of the AVRIDE AV made contact with the rear of the tow truck. Both vehicles sustained damage. No injuries were reported.
When did this incident occur?
The incident is recorded as occurring on December 1, 2025 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-13625)?
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-13625)?
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-13625)?
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-07-14

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-07-14

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

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 f9b7f2d7-6d2d-4dd9-a71d-7df50ed13371