DEPLOYDatabase

Incident · Collision

ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15628)

An unoccupied Zoox autonomous vehicle was making a left turn from eastbound [XXX] onto northbound [XXX] in Las Vegas when an active emergency vehicle, with lights and sirens, was rapidly approaching the intersection and conducting a right turn onto northbound [XXX]. The Zoox vehicle was slowing to yield to the approaching active emergency vehicle, when an SUV (Vehicle 2) traveling behind it failed to stop, and rear ended the slowing Zoox vehicle.

Two other passenger vehicles (Vehicles 3 & 4) were following behind Vehicle 2. Vehicle 4 appeared to have made contact with Vehicle 3 from behind. Neither Vehicle 3 nor Vehicle 4 contacted the Zoox vehicle, and it does not appear that either contacted Vehicle 2.

The driver of Vehicle 2 then pulled over ahead and contacted Zoox support to exchange information. The police were notified, but did not arrive at the scene. The Zoox vehicle was towed from the scene and found to have sustained moderate damage.

Occurred 2026-06-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.

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15628)?
An unoccupied Zoox autonomous vehicle was making a left turn from eastbound [XXX] onto northbound [XXX] in Las Vegas when an active emergency vehicle, with lights and sirens, was rapidly approaching the intersection and conducting a right turn onto northbound [XXX]. The Zoox vehicle was slowing to yield to the approaching active emergency vehicle, when an SUV (Vehicle 2) traveling behind it failed to stop, and rear ended the slowing Zoox vehicle. Two other passenger vehicles (Vehicles 3 & 4) were following behind Vehicle 2. Vehicle 4 appeared to have made contact with Vehicle 3 from behind. Neither Vehicle 3 nor Vehicle 4 contacted the Zoox vehicle, and it does not appear that either contacted Vehicle 2. The driver of Vehicle 2 then pulled over ahead and contacted Zoox support to exchange information. The police were notified, but did not arrive at the scene. The Zoox vehicle was towed from the scene and found to have sustained moderate damage.
When did this incident occur?
The incident is recorded as occurring on June 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 Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15628)?
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 Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15628)?
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 Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15628)?
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 Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15628).

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 b8defae5-2296-4e65-a4aa-dd5fcf10e11e