DEPLOYDatabase

Incident · Traffic disruption

San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire scene

The San Francisco Fire Department reported that on January 22, 2023 a driverless Cruise vehicle continued advancing toward firefighters working an active scene on the 1300 block of Hayes Street, and a firefighter broke the vehicle's front window after verbal warnings and physical contact failed to stop it. Cruise states that its vehicles are built to detect and yield to emergency scenes and first responders. This record is attributed to the SFFD incident report as compiled by Mission Local and to independent reporting by Forbes.

Occurred 2023-01-22 · Cruise

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 San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire scene

Machine-readable surfaces

Sources (2)

  1. San Francisco Fire Dept. Decided They Should Smash The Window Of A Cruise Robotaxi · https://www.forbes.com/sites/bradtempleton/2023/01/31/san-francisco-fire-dept-decided-they-should-smash-the-window-of-a-cruise-robotaxi--did-they-overdo-it/ · 2023-01-31
  2. The 55 reports of robot cars interfering with the S.F. fire department · https://missionlocal.org/2023/08/cruise-waymo-autonomous-vehicle-robot-taxi-driverless-car-reports-san-francisco/

Common questions

What happened in San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire scene?
The San Francisco Fire Department reported that on January 22, 2023 a driverless Cruise vehicle continued advancing toward firefighters working an active scene on the 1300 block of Hayes Street, and a firefighter broke the vehicle's front window after verbal warnings and physical contact failed to stop it. Cruise states that its vehicles are built to detect and yield to emergency scenes and first responders. This record is attributed to the SFFD incident report as compiled by Mission Local and to independent reporting by Forbes.
When did this incident occur?
The incident is recorded as occurring on January 22, 2023 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire scene?
The incident is recorded as involving Cruise on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire scene?
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 San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire scene?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-07-25

Verification posture

Verified

Medium confidence

Review state

Stable

Last reviewed 2026-07-25

Sources by quality tier

1
secondary-established-publication
Established publication
1
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire scene.

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 7a45e844-1085-4df0-8616-6c721f3c0bba