ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11331)
[COLLISION]Jun 1, 2025 · Zoox · Zoox Robotaxi · Miami
Failure Mode
COLLISION
Event Date
Jun 1, 2025
Primary Entity
Zoox
Robotic Platform
Zoox Robotaxi
Jurisdiction / Location
Miami
Audit Standard
Physical State Verified
Incident Abstract & Audit Findings
A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying both the northbound and southbound lanes on [XXX]. The Zoox vehicle slowed and moved to the right for the oncoming Vehicle 2 however, as Vehicle 2 passed, its driver's side mirror made contact with the driver's side 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-11331
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-11331
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 San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11331)?
A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying both the northbound and southbound lanes on [XXX]. The Zoox vehicle slowed and moved to the right for the oncoming Vehicle 2 however, as Vehicle 2 passed, its driver's side mirror made contact with the driver's side rear of the Zoox vehicle. The driver of Vehicle 2 failed to stop and exchange information. The Zoox vehicle did not sustain any damage, but Vehicle 2 appeared to have sustained minor damage to its driver's side mirror. There were no reported injuries, and the police were not notified.
When did this incident occur?
The incident is recorded as occurring on June 1, 2025 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 San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11331)?
Zoox Robotaxi by Zoox is the recorded robot involved in this incident at Miami.
Has anyone responded to ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11331)?
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 San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11331)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.