_Incident · Collision_

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

Canonical ID: `2772db83-eeee-4f69-b98e-822a410a9234`

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

An occupied [Zoox](/companies/zoox.md) autonomous vehicle was proceeding southbound on [XXX] after making a full stop at a 4-way-stop at [XXX] in San Francisco, when a fast-moving cyclist ran the stop sign from a downhill section of [XXX] from the right. The Zoox vehicle came to a stop in the intersection to yield to the approaching cyclist.  The cyclist lost control, went over the handlebar, made contact with the left rear corner of the stopped Zoox vehicle, and then fell to the ground. The Zoox vehicle remained stopped in the intersection following the impact. Police and emergency services were notified and arrived at the scene. The cyclist was transported to a hospital via ambulance. The Zoox vehicle then resumed operation. There was no damage to the vehicle.

## Sources (1)

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

## Common questions

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

An occupied Zoox autonomous vehicle was proceeding southbound on [XXX] after making a full stop at a 4-way-stop at [XXX] in San Francisco, when a fast-moving cyclist ran the stop sign from a downhill section of [XXX] from the right. The Zoox vehicle came to a stop in the intersection to yield to the approaching cyclist.  The cyclist lost control, went over the handlebar, made contact with the left rear corner of the stopped Zoox vehicle, and then fell to the ground. The Zoox vehicle remained stopped in the intersection following the impact. Police and emergency services were notified and arrived at the scene. The cyclist was transported to a hospital via ambulance. The Zoox vehicle then resumed operation. There was no damage to the vehicle.

### When did this incident occur?

The incident is recorded as occurring on June 1, 2026 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-15707)?

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

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

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


_API: GET /v1/incidents/2772db83-eeee-4f69-b98e-822a410a9234 · sources: /v1/incidents/2772db83-eeee-4f69-b98e-822a410a9234/sources · responses: /v1/incidents/2772db83-eeee-4f69-b98e-822a410a9234/responses · status: /v1/incidents/2772db83-eeee-4f69-b98e-822a410a9234/status · canonical URL: /incidents/nhtsa-sgo-30610-15707_