DEPLOYDatabase

Incident · Collision

ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)

A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southeast on [XXX], preparing to change lanes to the right to turn onto [XXX] in Santa Monica, when it was hit on the right rear corner (rear bumper, hatch, right rear wheel, and right rear quarter panel) by an SUV (Vehicle 2). The Zoox vehicle stopped facing southwest on [XXX], with the front of Vehicle 2 still engaged with the right rear of the Zoox vehicle.

The Zoox vehicle sustained severe rear damage, including damage to data recording systems. Vehicle 2 had major damage to its front end. Airbags deployed in both vehicles, and they were towed from the scene.

Police and emergency responders arrived to assist, and the driver of vehicle 2 was detained. The Zoox vehicle operator and two passengers reported soreness and a headache after the collision.

Occurred 2026-02-01 · Zoox Robotaxi at Miami · Zoox · Miami · Robotaxis

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 Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)?
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southeast on [XXX], preparing to change lanes to the right to turn onto [XXX] in Santa Monica, when it was hit on the right rear corner (rear bumper, hatch, right rear wheel, and right rear quarter panel) by an SUV (Vehicle 2). The Zoox vehicle stopped facing southwest on [XXX], with the front of Vehicle 2 still engaged with the right rear of the Zoox vehicle. The Zoox vehicle sustained severe rear damage, including damage to data recording systems. Vehicle 2 had major damage to its front end. Airbags deployed in both vehicles, and they were towed from the scene. Police and emergency responders arrived to assist, and the driver of vehicle 2 was detained. The Zoox vehicle operator and two passengers reported soreness and a headache after the collision.
When did this incident occur?
The incident is recorded as occurring on February 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)?
Zoox Robotaxi by Zoox is the recorded robot involved in this incident at Miami.
Has anyone responded to ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)?
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 Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)?
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 Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167).

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 c5b0546a-9339-403a-8876-98841437ff38