DEPLOYDatabase

Incident · Collision

ADS crash report in Austin, TX involving a ZOOX Zoox (NHTSA SGO 30610-15722)

An occupied Zoox autonomous vehicle was traveling west on [XXX] toward [XXX] in Austin when it braked to a stop for a pedestrian and dog on a leash entering the crosswalk. A passenger car (Vehicle 2) traveling directly behind failed to slow down and rear ended the stopped Zoox vehicle.

Shortly after, the Vehicle 2 driver reversed, inspected both vehicles, then returned to their vehicle and remained at the scene. The Zoox vehicle passenger reported feeling "dazed" and "kind of woozy" and requested emergency services. The police were notified and arrived at the scene.

The Zoox fleet response team also arrived, and information was exchanged with the other party. Just as the Zoox vehicle started moving, an audible noise came from its fender, so it pulled over and was towed for further inspection. The vehicle was found to have sustained moderate damage to its rear end.

Occurred 2026-07-01 · Zoox

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 ZOOX Zoox (NHTSA SGO 30610-15722)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Austin, TX involving a ZOOX Zoox (NHTSA SGO 30610-15722)?
An occupied Zoox autonomous vehicle was traveling west on [XXX] toward [XXX] in Austin when it braked to a stop for a pedestrian and dog on a leash entering the crosswalk. A passenger car (Vehicle 2) traveling directly behind failed to slow down and rear ended the stopped Zoox vehicle. Shortly after, the Vehicle 2 driver reversed, inspected both vehicles, then returned to their vehicle and remained at the scene. The Zoox vehicle passenger reported feeling "dazed" and "kind of woozy" and requested emergency services. The police were notified and arrived at the scene. The Zoox fleet response team also arrived, and information was exchanged with the other party. Just as the Zoox vehicle started moving, an audible noise came from its fender, so it pulled over and was towed for further inspection. The vehicle was found to have sustained moderate damage to its rear end.
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 ZOOX Zoox (NHTSA SGO 30610-15722)?
The incident is recorded as involving Zoox 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 ZOOX Zoox (NHTSA SGO 30610-15722)?
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 ZOOX Zoox (NHTSA SGO 30610-15722)?
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 Austin, TX involving a ZOOX Zoox (NHTSA SGO 30610-15722).

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 f75dfb7b-ec11-454a-9bd3-d82b7ee346df