The MachineRecord
RegistryTMR-0118

A Cruise self-driving robotaxi was struck by a San Francisco Fire Department truck en route to an emergency at the intersection of Polk and a person in the Tenderloin district, resulting in one passenger being transported to a hospital with non-severe injuries.

Minor injurycollisionotherCruise
Date of incident
2023-08-17
Location
San Francisco, California, USA
Sources
4
EscalationRegulator action

Established by press reporting. No regulator or court document is linked to this case yet.

Timeline

How the event developed

  1. 2023-08-18Report

    A Cruise self-driving robotaxi was struck by a San Francisco Fire Department truck en route to an emergency at the intersection of Polk and a person in the Tenderloin district, resulting in one passenger being transported to a hospital with non-severe injuries.

    cnbc.com
  2. 2023-08-18Report

    A Cruise driverless robotaxi failed to yield to a responding fire truck at Turk and a person in San Francisco, causing a collision that triggered the vehicle's airbags and injured the female passenger, who was transported by ambulance with non-severe injuries.

    cbsnews.com
  3. 2023-08-18Follow-up

    A San Francisco Fire Department ladder truck T-boned a Cruise robotaxi at the intersection of Turk and a person, deploying airbags and sending the passenger to hospital with a headache.

    forbes.com
  4. 2023-08-18Regulator action

    A Cruise driverless robotaxi collided with a fire truck at Polk and Turk streets in San Francisco, injuring a passenger who was transported to hospital with non-life-threatening injuries.

    sfstandard.com
Sources

Every claim above traces to one of these

Links are never hidden behind a paywall of ours. Where a copy of the page exists it is linked beside the source with the date it was taken, because news links rot and a dead link next to a saved copy is still evidence. Some copies predate this register: they were made by the Internet Archive before we existed, and the date shown is the date of that copy, not of our visit.

Right of reply

Named in this case?

Any company named here can submit a response. We publish it in the case unedited, and a request makes the pipeline re-check the case against its own sources within a day. Target turnaround for our reply is five working days.