DEPLOYDatabase

Incident · Collision

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

An occupied Zoox autonomous vehicle was traveling north in the left through-lane of Las Vegas Boulevard, past [XXX], in Las Vegas. An SUV (Vehicle 2) traveling slightly ahead in the adjacent right lane executed an abrupt lane change into the Zoox vehicle's lane, then immediately braked hard to a stop to avoid a jaywalking pedestrian who was moving east-to-west across the northbound lanes.

In response, the Zoox vehicle braked hard and steered left; however, the right front corner of the Zoox vehicle made contact with the left rear corner of Vehicle 2 before coming to a stop. Following the collision, both vehicles moved over to the left turn-lane to exchange information. Law enforcement responded to the scene and no injuries were reported.The Zoox vehicle was subsequently towed for inspection; inspection confirmed it sustained minor damage.

Occurred 2026-08-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 Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-16450)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-16450)?
An occupied Zoox autonomous vehicle was traveling north in the left through-lane of Las Vegas Boulevard, past [XXX], in Las Vegas. An SUV (Vehicle 2) traveling slightly ahead in the adjacent right lane executed an abrupt lane change into the Zoox vehicle's lane, then immediately braked hard to a stop to avoid a jaywalking pedestrian who was moving east-to-west across the northbound lanes. In response, the Zoox vehicle braked hard and steered left; however, the right front corner of the Zoox vehicle made contact with the left rear corner of Vehicle 2 before coming to a stop. Following the collision, both vehicles moved over to the left turn-lane to exchange information. Law enforcement responded to the scene and no injuries were reported.The Zoox vehicle was subsequently towed for inspection; inspection confirmed it sustained minor damage.
When did this incident occur?
The incident is recorded as occurring on August 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-16450)?
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-16450)?
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-16450)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (1 primary) · last reviewed 2026-10-18

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-10-18

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-16450).

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 26cc10ac-7120-466a-81b9-e561b68ed98e