ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14339)
[COLLISION]Feb 1, 2026 · Zoox · Zoox Robotaxi · Miami
Failure Mode
COLLISION
Event Date
Feb 1, 2026
Primary Entity
Zoox
Robotic Platform
Zoox Robotaxi
Jurisdiction / Location
Miami
Audit Standard
Physical State Verified
Incident Abstract & Audit Findings
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.
System & Fleet Architecture
Operating Manufacturer
Hardware Platform
Operational Sectors
Primary Sources & Evidentiary Filings
- Inspect Filing
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-14339
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-14339
Related Incidents & Failure Precedents
6 records on file- Amazon Prime Air MK30 drone crashes into residential garden in Darlington, UK, prompting AAIB investigation[COLLISION]
Jul 29, 2026 · Amazon · Amazon Astro · Seattle
Details - Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle collision in Los Angeles, multiple people hospitalized[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle crash in LA's Pico-Union, one person critically injured[COLLISION]
Jul 25, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Tesla remote operator crashed a Robotaxi into a tree stump in Houston, NHTSA data shows[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details - Tesla robotaxi remote operator crashed vehicle into metal fence in Houston[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details
Incident Context & FAQ
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.