Incident · Injury
Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassador
On January 17, 2026, around 2 p.m., a Zoox robotaxi in San Francisco collided with a suddenly-opened parked-car door, injuring a street ambassador (Jamel Durden, per reporting). The San Francisco Police Department opened an investigation and the California DMV reviewed the incident; Zoox filed a mandatory crash report. The collision raised questions about Zoox's edge-case detection as it expanded early-rider programs in SF and Las Vegas, adding to a pattern of recalls and operational issues.
Occurred 2026-01-17 · Zoox Robotaxi at San Francisco · Zoox
Machine-readable surfaces
- Markdown mirror: /incidents/zoox-sf-door-collision-2026-01-17.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/dc9653ab-52bd-4610-97d3-b5b474d74541
- Data documentation: /data
- Query this programmatically: Deploy MCP
Outcomes (1)
- bodily injuryverified
Revision history (2)
- 2026-06-05 · bodily_injury_severity · reported_press
- 2026-06-05 · outcome_class
Outcome rows carry verification_posture independently. Revision events carry basis (verified_court_filing, verified_insurance, reported_press, estimate, undisclosed). The framework records outcomes only when verifiable; absence is honest absence, not a claim of no-impact.
Sources (4)
- Context: Zoox December lane-crossing recall, expanding SF/Vegas rider programs · https://techcrunch.com/2025/12/23/zoox-issues-software-recall-over-lane-crossings/ · 2025-12-23
- SFPD investigating Jan 17 2026 Zoox door collision, street ambassador injured, DMV review · https://www.techbuzz.ai/articles/zoox-robotaxi-under-sfpd-probe-after-door-collision · 2026-01-20
- https://techcrunch.com/2026/01/28/san-francisco-police-department-investigating-zoox-collision-with-a-parked-car/
- https://missionlocal.org/2026/01/sf-zoox-autonomous-car-crash-accident/
Common questions
- What happened in Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassador?
- On January 17, 2026, around 2 p.m., a Zoox robotaxi in San Francisco collided with a suddenly-opened parked-car door, injuring a street ambassador (Jamel Durden, per reporting). The San Francisco Police Department opened an investigation and the California DMV reviewed the incident; Zoox filed a mandatory crash report. The collision raised questions about Zoox's edge-case detection as it expanded early-rider programs in SF and Las Vegas, adding to a pattern of recalls and operational issues.
- When did this incident occur?
- The incident is recorded as occurring on January 17, 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 Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassador?
- Zoox Robotaxi by Zoox is the recorded robot involved in this incident at San Francisco.
- Has anyone responded to Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassador?
- 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 Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassador?
- This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 4 sources (no primary) · last reviewed 2026-06-24
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-06-24
Sources by quality tier
- 2
- secondary-industry-publication
- Industry publication
- 2
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassador.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 dc9653ab-52bd-4610-97d3-b5b474d74541