DEPLOYDatabase

Incident · Collision

ADS crash report in Las Vegas, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11990)

A Zoox vehicle (Vehicle 1) in autonomous mode was traveling east towards the Passenger Pick-up area in Terminal 3 of [XXX] in Las Vegas. An SUV (Vehicle 2), traveling behind in the left adjacent lane, abruptly attempted to overtake and cut in front of the Zoox vehicle in an apparent attempt to change lanes to the right towards Terminal 3 Departures. The Zoox vehicle braked hard in response to the encroaching vehicle, and the operator then disengaged from autonomy and continued to brake, but contact could not be avoided. The right rear side of Vehicle 2 swiped the left front area of the Zoox vehicle. Both operators stopped after the collision and exchanged information. Both vehicles sustained moderate damage, and the Zoox vehicle was subsequently towed from the scene. There were no reported injuries, and police were not called.

Occurred 2025-10-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 TOYOTA Highlander (NHTSA SGO 30610-11990)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Las Vegas, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11990)?
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling east towards the Passenger Pick-up area in Terminal 3 of [XXX] in Las Vegas. An SUV (Vehicle 2), traveling behind in the left adjacent lane, abruptly attempted to overtake and cut in front of the Zoox vehicle in an apparent attempt to change lanes to the right towards Terminal 3 Departures. The Zoox vehicle braked hard in response to the encroaching vehicle, and the operator then disengaged from autonomy and continued to brake, but contact could not be avoided. The right rear side of Vehicle 2 swiped the left front area of the Zoox vehicle. Both operators stopped after the collision and exchanged information. Both vehicles sustained moderate damage, and the Zoox vehicle was subsequently towed from the scene. There were no reported injuries, and police were not called.
When did this incident occur?
The incident is recorded as occurring on October 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 Las Vegas, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11990)?
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 TOYOTA Highlander (NHTSA SGO 30610-11990)?
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 TOYOTA Highlander (NHTSA SGO 30610-11990)?
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 Las Vegas, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11990).

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 050e5790-64ee-4778-92e8-ac04f464b8d4