Incident · Collision
ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818)
An occupied Zoox autonomous vehicle began to proceed on a fresh green traffic signal on westbound [XXX] at [XXX] when the driver of a stationary passenger vehicle (Vehicle 2), parallel-parked in the curb lane, rapidly opened the driver door into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable.
The right side front fender, wheels, bodyside, and door panels made contact with the outside edge of the opening door of Vehicle 2. The Zoox vehicle came to an immediate stop and was later towed from the scene to be inspected for damage. First responders arrived at the scene.
The passenger of the Zoox vehicle did not report any injuries. Later media stories reported the driver of Vehicle 2 had a "smashed hand" and his "hand was hurting, and that he was also experiencing pain to his neck area and lower back" based on a third party's account, and that the driver "declined their offer to take him to the hospital." Zoox vehicle camera footage shows clearly that no part of the robotaxi came into contact with the driver themselves, and that their hands, leg, and body did not interact with either the robotaxi or the parked vehicle's door at any moment during the contact event.
Occurred 2026-01-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.Machine-readable surfaces
- Markdown mirror: /incidents/nhtsa-sgo-30610-13818.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/cdd82f9e-748a-40ba-aff4-97b2ad249844
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Common questions
What happened in ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818)?
When did this incident occur?
What robot was involved in ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818)?
Has anyone responded to ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818)?
What is the current status of ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818)?
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 San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818).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 cdd82f9e-748a-40ba-aff4-97b2ad249844