ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)
[COLLISION]Feb 1, 2026 · Zoox · Zoox Robotaxi · Miami
Failure Mode
COLLISION
Event Date
Feb 1, 2026
Primary Entity
Zoox
Robotic Platform
Zoox Robotaxi
Jurisdiction / Location
Miami
Audit Standard
Physical State Verified
Incident Abstract & Audit Findings
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.
System & Fleet Architecture
Operating Manufacturer
Hardware Platform
Operational Sectors
Primary Sources & Evidentiary Filings
- Inspect Filing
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-14167
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-14167
Related Incidents & Failure Precedents
6 records on file- Amazon Prime Air MK30 drone crashes into residential garden in Darlington, UK, prompting AAIB investigation[COLLISION]
Jul 29, 2026 · Amazon · Amazon Astro · Seattle
Details - Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle collision in Los Angeles, multiple people hospitalized[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle crash in LA's Pico-Union, one person critically injured[COLLISION]
Jul 25, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Tesla remote operator crashed a Robotaxi into a tree stump in Houston, NHTSA data shows[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details - Tesla robotaxi remote operator crashed vehicle into metal fence in Houston[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details
Incident Context & FAQ
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.