DEPLOYDatabase

Incident · Collision

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

An unoccupied Zoox autonomous vehicle was traveling in the right lane on northwest-bound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. Partway through the right turn, the Zoox vehicle further slowed to yield to a pedestrian crossing [XXX], and at that time, a cyclist traveling northwest on the adjacent sidewalk rapidly entered the crosswalk.

The Zoox vehicle braked to yield to the approaching cyclist, and the cyclist made contact with the right rear side of the nearly stopped Zoox vehicle. The bicycle fell to the ground, but its rider remained upright. The cyclist picked up their bicycle and rode away from the scene.

Shortly after, the Zoox vehicle resumed operation to return to base. There was minor damage to the Zoox vehicle. There were no reported injuries, and police were not notified.

Occurred 2026-02-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.
Track ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14339)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14339)?
An unoccupied Zoox autonomous vehicle was traveling in the right lane on northwest-bound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. Partway through the right turn, the Zoox vehicle further slowed to yield to a pedestrian crossing [XXX], and at that time, a cyclist traveling northwest on the adjacent sidewalk rapidly entered the crosswalk. The Zoox vehicle braked to yield to the approaching cyclist, and the cyclist made contact with the right rear side of the nearly stopped Zoox vehicle. The bicycle fell to the ground, but its rider remained upright. The cyclist picked up their bicycle and rode away from the scene. Shortly after, the Zoox vehicle resumed operation to return to base. There was minor damage to the Zoox vehicle. There were no reported injuries, and police were not notified.
When did this incident occur?
The incident is recorded as occurring on February 1, 2026 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-14339)?
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-14339)?
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-14339)?
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-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-14339).

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 8ac35cf9-c866-465b-8801-5697630a5e2b