Incident · Collision
ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-11563)
An unoccupied Zoox autonomous vehicle was stopped at a green traffic light on eastbound [XXX], waiting for traffic ahead to clear to turn left onto [XXX] in San Francisco. A pickup truck (Vehicle 2) was also stopped for the same traffic light, directly behind the Zoox vehicle. After the light turned yellow, the Vehicle 2 driver passed the stopped Zoox vehicle on the left side, striking the left rear fender, and proceeded through the red light. The Vehicle 2 driver did not stop to exchange information. Shortly afterward, the Zoox vehicle turned left onto [XXX] to clear the scene, briefly stopped again, and then pulled over. The Zoox vehicle was then towed for inspection. It sustained minor damage. There were no reported injuries and the police were not called.
Occurred 2025-08-01 · Zoox
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-11563.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/57c8b436-25fd-490f-b978-0162d4325bea
- 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-11563)?
- An unoccupied Zoox autonomous vehicle was stopped at a green traffic light on eastbound [XXX], waiting for traffic ahead to clear to turn left onto [XXX] in San Francisco. A pickup truck (Vehicle 2) was also stopped for the same traffic light, directly behind the Zoox vehicle. After the light turned yellow, the Vehicle 2 driver passed the stopped Zoox vehicle on the left side, striking the left rear fender, and proceeded through the red light. The Vehicle 2 driver did not stop to exchange information. Shortly afterward, the Zoox vehicle turned left onto [XXX] to clear the scene, briefly stopped again, and then pulled over. The Zoox vehicle was then towed for inspection. It sustained minor damage. There were no reported injuries and the police were not called.
- When did this incident occur?
- The incident is recorded as occurring on August 1, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
- Who was involved in ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-11563)?
- The incident is recorded as involving Zoox on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
- Has anyone responded to ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-11563)?
- 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-11563)?
- 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-07-14
Verification posture
Verified
High confidence
Review state
Stable
Last reviewed 2026-07-14
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-11563).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 57c8b436-25fd-490f-b978-0162d4325bea