Physical State | The risk-data layer for a robotic world

Incident Abstract & Audit Findings

An unoccupied Zoox vehicle (Vehicle 1) was stationary in the right lane on northeast-bound [XXX] at [XXX] in San Francisco, stopped behind traffic at a red light. After the light turned green, the Zoox vehicle initially remained stopped to yield to an active police vehicle making a right turn onto [XXX] from the adjacent lane.

System & Fleet Architecture

Operating Manufacturer

ZooxView Manufacturer

Hardware Platform

Zoox RobotaxiView Spec

Operational Sectors

Physical AI / Robotics

Primary Sources & Evidentiary Filings

https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-13660
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-13660
Inspect Filing

Related Incidents & Failure Precedents

6 records on file

Incident Context & FAQ

What happened in ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13660)?

An unoccupied Zoox vehicle (Vehicle 1) was stationary in the right lane on northeast-bound [XXX] at [XXX] in San Francisco, stopped behind traffic at a red light. After the light turned green, the Zoox vehicle initially remained stopped to yield to an active police vehicle making a right turn onto [XXX] from the adjacent lane. During the subsequent green light cycle, as the Zoox vehicle began to proceed straight along [XXX], two passenger cars, including Vehicle 2, cut across its path from behind, attempting an illegal right turn onto [XXX] from a through lane. The Zoox vehicle braked hard, but contact was unavoidable, and Vehicle 2 clipped the Zoox vehicle's left front fender. The front-seat passenger of Vehicle 2 exited to inspect the Zoox vehicle before returning to their car and leaving the scene without exchanging information. The Zoox vehicle then cleared the scene and returned to base. Upon inspection, the Zoox vehicle was found to have sustained minor damage. Police were notified, and no injuries were reported.

When did this incident occur?

The incident is recorded as occurring on December 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 ZOOX Zoox (NHTSA SGO 30610-13660)?

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 ZOOX Zoox (NHTSA SGO 30610-13660)?

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 ZOOX Zoox (NHTSA SGO 30610-13660)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.