_Incident · Collision_

# ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13661)

Canonical ID: `38c20d85-2d4c-42ea-b040-932c0ffc6268`

- **Occurred:** 2025-12-01
- **Kind:** `collision`
- **Status (derived):** active
- **Company:** [Zoox](/companies/zoox.md) (id: `6ab92a95-6f4e-4493-a771-ae645c7969c6`)

An occupied Zoox autonomous vehicle (Vehicle 1) was traveling west on [XXX] past [XXX] when it encountered debris in the lane. The Zoox vehicle braked hard for the debris and was then rear ended by a close-following Pickup (Vehicle 2) that was abruptly merging into the lane directly behind the Zoox vehicle. The Vehicle 2 driver then reversed and left the scene without attempting to exchange information. Shortly after, the Zoox vehicle cleared the scene, turned right onto [XXX], and pulled over to allow the riders to exit the vehicle. The Zoox vehicle then returned to base for inspection and was found to have sustained moderate damage. There were no reported injuries, and the police were notified.

## Sources (1)

1. https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-13661

## Common questions

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

An occupied Zoox autonomous vehicle (Vehicle 1) was traveling west on [XXX] past [XXX] when it encountered debris in the lane. The Zoox vehicle braked hard for the debris and was then rear ended by a close-following Pickup (Vehicle 2) that was abruptly merging into the lane directly behind the Zoox vehicle. The Vehicle 2 driver then reversed and left the scene without attempting to exchange information. Shortly after, the Zoox vehicle cleared the scene, turned right onto [XXX], and pulled over to allow the riders to exit the vehicle. The Zoox vehicle then returned to base for inspection and was found to have sustained moderate damage. There were no reported injuries, and the police were notified.

### 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.

### Who was involved in ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13661)?

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-13661)?

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-13661)?

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


_API: GET /v1/incidents/38c20d85-2d4c-42ea-b040-932c0ffc6268 · sources: /v1/incidents/38c20d85-2d4c-42ea-b040-932c0ffc6268/sources · responses: /v1/incidents/38c20d85-2d4c-42ea-b040-932c0ffc6268/responses · status: /v1/incidents/38c20d85-2d4c-42ea-b040-932c0ffc6268/status · canonical URL: /incidents/nhtsa-sgo-30610-13661_