yPEE
A hEEEA

2

5

ANA San Francisco Fire Department(5)\§i| Unusual Occurrence
io

ee
From:

ie

ee

ie

04/11/2022

Eat ER its

TOR
TTTOTIRIT—

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

A mi
mma
A
_
while responding
1.0n the morningof April 5, 2022, at 0406am, Box 5165, Incident numbera22043125,
with lights and sirens heading east on 17th Street, Engine 12 encountered stopped Recology truck in
our lane.
;
2. The driver was out of the truck collecting trash.

3. Normally T would have gone around the stopped truck, but at the same time, a "self-driving" car fromthe company Cruise with no human in the driver's seat, drove up in the opposing lane heading west and
STOPPED exactly next to the Recology truck.
4. Engine 12 was dead in the water until the Recology driver came running and moved the garbage

truck, at which time we were able to continue on to the working fire.
Workflow _ FromTo
02022 nat
ForwardedEzoanano m—
Acknowledged 805
04/12/2022—

Contents Noted

D2

04/12/2022

Tmmmpwemids

Contents Noted

cn2

requested thisEE

Topo. lease ensure he receivesacopy.
Deputy, I believe this is somethin we need toinvestigate.
Importantly, this indent mentioned was E12

trying to respond to the Upper Terrace fire.

04122022
oun32022
ounsz0z2
04182022

Gaasmpaanddem——aw—
GallienInfo Only
Lowe
Contents Noted Coffink.
Workfow End
Ifo Orly
Law

Ihave also long envisioned a scenario ata red
light withtwosef-divingcarsnext to eachotherthatwouldnotgothrough ared in
response to red lights and sirens behind them.
Your copy. Also sent to CD2
please address this vith MTA. These are
becoming a nuisance
Clty staff wilworkwith Cruse and gather
addtional information.

Page 10f 112

“~
AT
5
3
PGR San Francisco Fire DepartmentWis) Unusual Occurrence
06/06/2022
iC
a
ET
From:

reiki

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. On June 6, 2022 at 0410 hours, E09 was dispatched to a report of an outside fire at 101 §/B andCesar Chavez under the freeway.
2. While enroute code 3, we encountered a potentially unsafe situation with a Cruise driverless car at
the intersection of Precita Ave. and Bryant St.
3. While traveling South on Bryant, a driveless car proceeded through a stop sign in our direction andcontinued to move into the intersection towards the engine.
4. E09 driver continued with due regard and caution until the driverless vehicle came to a complete stopin the intersection, and we proceeded to the incident.

5. The location of the Cruise vehicle in the intersection created an unsafe environment in the event.

multiple units were to respond.

5. I notified B10 of the incident in the morning at Station 9.

Workflow_ From
6062022 Stl
061062022 my
061062022 uw—

Forwarded
Acknowledged
Wordiow End

To
810
D3

Contents Noted
Duplicate UO

Page3of 112

Hh
Eo

:

.

(NA San Francisco Fire DepartmentWes) Unusual Occurrence

SY
in a aeiLn TA
From:
S————
TE

To:

06/13/2022

Chief of Department

Reference: Rules and Regulations, Section 1128
Ee ee ty_
1. On June 12, 2022 at 23:50 hours Engine 14 was the supply engine at a working fire incident #2075217.
2. E14 had charged large lines lying across the street supplying E31 down Funston Ave. from the Anza
St. intersection.
3. An autonomous vehicle heading west on Anza approached the charged large lines and came to aandComplete stop before accelerating up to approximately 10-15 mph as it proceeded over hose leads
on to the Park Presidio street light.
4, The crew of E14 and an SFPD Officer controling traffic observed this unoccupied self driving vehicle:
perform this hazardous driving behavior.
5. Battalion 7 Chief McGuire was notified of this observed occurrence.
6. No fire department property or personnel were harmed by this occurrence.
To
Workflow _ From
B07
Fowarded
0613202 Wma
Adctional statements are avallablefortis
ContertsNoled D2
06132022 mmmyD
incident f required.
Contents noted.
C02
Noted
Contents
osna0zz w——Acknowledged

Gadi

os132022 w—
06212022 em.

nfo Only
Info Onlycotae6212022 Owe

Worklow End

06/13/2022—F

AnotherCruise mishap. These things are

someone. Please forward togoing to hurtperson.
appropriate

Please communicate the gravy of thissituation to Cruise's JudyLeewhen speaking
with her next.

Page 7of 112

Case

Scene

Weve

os

>

(RA San Francisco Fire Department& iz) Unusual OccurrenceGi

01/24/2023

From:

SHEE

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1.0n 24 Jan 2023 at Laguna and Hayes streets (#23011518) my crew was extinguishing an outside
fire on the sidewalk.
2. E36 was parked in the middle of the street with all of its' emergency lights on.
3. A "Cruise" driverless vehicle rapidly approached us and stopped between the Engine and my crew.

4. We were unable to move the car and it was stopped on top of our hoseline.
5. I was able to speak to the operator via the car intercom and they were able to move the car after an
additional 5 minutes.

6. there was no damage to the hose reel or any injuries.
Workflow_ FromTo
0172412023

Cm—m—,

Forwarded

E3601202025 m—
01242023 Gummy

Contents Noted
Contents Noted

San
D3

ov2s2023 B=
otr2sn02 A—

Contents Noted
Acknowledged

CD2
CDT

0125/2023—

Contents Noted

Gms

01252023 SK

Acknowledged

pummR

01/26/2023

Workflow End

hm—iz

0510372023 pmmbainm Ifo Orly

Increasing incidents
ofautonomous vehicles
ether entering our scenes or hindering
responses
these things shoud not be alowed. too many
problems
please forward to Ramon and have it
addressed. Totally unacceptable and should

be grounds
tostop the program

pec

Page 9of 112
CW Se

Sena

ose

on

:

i

aa) San Francisco Fire Department

Wise) Unusual Occurrence
Ror
From:

cg

aNA 1Ja SEI
80 ESFNRS
TT————

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128i

03/11/2023

iil

1. On March 11 at approximately 22:05 Truck 3 was returning from a call going westbound on the 800

block of Geary Street, and encountered two autonomous Cruise vehicles blocking the road.
2. Geary is one way with two traffic lanes and cars parked on both sides. Several cars were double
parked on the left side. This is becoming a more common problem in itself.
3. The autonomous vehicles were in the red painted bus lane on the right side, opposite theother double parked cars on the lef. believe one of the autonomous cars was very slowly moving or
repositioning when we were approximately haf a block back. Truck 3 was not using any code 3 lights or
the siren, The space between the double parked cars on either side was not enough for Truck 3 tosafely pass. I rang the officer's bell several times hoping for someone to move. I then gave a very short
blast of the airhom. At least one of the Cruise vehicles moved slightly (inches), but not in a deliberatefashion, and it did not clear the road. The Cruise vehicles were midblock with no other vehicles in frontof them. They were not waiting for a red light. I cimbed outof Truck 3 and approached the twovehicles. Neither car had a driver or passenger. The vehicle in the rear started to move before the
Vehicle in the front. It pulled out slowly toward me as if to go around the other Cruise vehicle and thenstopped. Eventually both vehicles moved, but there was not a deliberate attempt to leave the road clear
in the first place ora deliberate attempt to get out of the way when prompted by Truck 3's bell or horn.
Both vehicles started with slow jerky movements as if they didn't know what to do.

Workflow _ From
01202 eww
03112023 Www
0122023 mmm
03122025 mm

Forwarded
Contents Noted
Acknowledged
Contents Noted

031372023

Contents Noted ~~ CDT

I'm sending this to GEE as well

03132025 owe—
ouzoz02s cm—

Acknowledged
Contents NotedTose to be srtthe pprateePlease forward toCity AY representative.

03/21/2023

Workflow End

Ew——

R——_

To
Tos
B04
D2
CD2

emmm—EEO.

Contents noted

Page 11of 112

FU
CE
:
5 Department(6A
San Francisco
Fire\§ie%)) Unusual Occurrence
is
From:

————————
OuTo:

Chief of Department

Reference:

Rules and Regulations, Section 1128

03/21/2023

1. On 03/21/23 I was responding to incident #23038973 as B10. While responding to the incident I

encountered a driverless Waymo vehicle license plate

535953 at 1128 hours. I was driving‘westbound on Palou Ave with lights and siren on when a driverless Waymo vehicle traveling eastboundon Palou

Ave proceeded to make a left hand turn directly in my path onto Newhall St. andcontinuously the car
stopped directly in front of my vehicle. With lights and siren onrefused to move blocking my response path. After approximately 1 min the car moved and pulled
over. At this time the incident

had been canceled and I proceeded to the driverless vehicles

drivers side window in order to notify the monitoring company that their car was

malfunctioning. I knocked on the window numerous times and no one ever responded. 1 moved awayfrom the vehicle and it immediately droveoffto
continue its route.
Workflow _FromTo
03212023 mn)
Forwarded
03
ou212023 w—
Contents Noted CD2
Forwarding UO from Battalion 10 regarding
driverless Waymo vehide impeding the flow of
traffic and emergency response of Battalion 10

03/22/2023

Fesm——"

03222023 aww—R
03222025 rem

Acknowledged—

Acknowledged
Workflow End

CD

on March 21, 2023.
‘secondeventthat needs tobe documented
and addressed
FYI, prevention notified for documentation andfolow up

Page 130f 112

:3
co
PGA San Francisco Fire Department
Wiss) Unusual Occurrence
&

ee

a

From:

03/21/2023

eaeoeSE,

TE ————

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

a sab Empaths Cteg reo att2Liee_
1. On 03/21/23 I responded to Incident #23039343 as B10. While responding code 3 ‘with lights andsiren on traveling south on Dolores St. in the left lane at approximately 1719 hoursI encountered adriverless Waymo vehicle. The Waymo vehicle was directly in front of me traveling south on Dolores
approached it ith lights and siren it began to move over to the right lane enough for
St. AST
into my direction andme to pass. As Iwas passing the vehicle appeared to turn sharply
accelerated towards my righ rear quarter panel. Upon noticing this in my rearview mirrorI accelerated
to avoid being hit by thedriverless vehicle. As I passed the vehicle continued to come all theway over into my lane and appeared to accelerate towards my rear bumper. I thenfurther

accelerated to get away from the vehicle as quickly as possible.
Workflow _ FromTo
03212025 em)
Forwarded
03
03212023 mwe—_
Contents Noted C2
Forwarding 2nd UOfrom Battalion 10
regarding driveress Waym vec affecting
theemergencyresponseof Battalion 10 andalmost makingcontactwith the Battalion 10
bugay.
03222023 ag
Acknowledged milananother diveriss Issue to document
03222023 mao
Acknowledged CDI
B77notified to document
03222023 N—,
Wordlow End

Page 15 of 112

NA San Francisco Fire DepartmentWim) Unusual Occurrencei

03/24/2023

Fromeonesemem—————

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. On March 21st, 2023, (on Incident# FD23039379) at 706 Missouri, I was the officer of Engine 25
and encountered several Waymo cars that were driverless and poseda risk to fire personnel.
2. Engine 25 responded to a downed tree on a vehicle. Upon arrival, Engine 25 noted there were nowires down, a large tree was blocking Missouri street and there were no occupants/victims in thedamaged vehicle.
3. After trimming tree limbs, putting up caution tape and clearing a lane on Missouri for traffic, Engine
25 noted a vehice driving northbound on Missouri ata fas rate of speed. Engine 25 attempted to slow
down the vehicle by shining their box ight on the river as there were fir service personnel working in
the area.
4. The vehicle was a diverless Waymo vehicle and finally stopped last minute a few feet from Engine 25(Engine 25 had it's Code 3 lights on). The officer of Engine 25 noted another vehicle coming the same
direction at a fast rate ofspeed and tried to slow it down. It was also a driverless Waymo vehicle
that slowed down last minute and swerved to is lef to avoid crashing into the 1st Waymo vehicle, This
2nd Waymo vehicle stopped a few feet from theofficerof Engine 25.
5. Luckily we had just finished working on the tree and had the fire engine to create a barrier between
us and the Waymo vehicles if needed. Had we been working on the downed tree in the dark and those
two Waymo vehicles came down the hill (northbound on Missouri) at their fast rate of speed, I am

unsure those driverless vehicles would have stopped in time to avoid hitting fire service personnel.
6. Thank you for your time and attention in this matter.

Adz Syed
Lieutenant- Engine 25
Workllow__ From
242025 pn

Tovar

™
E25

0242023 Gand

Contents Noted

B1003242020 Gms

2

UaywmoContetsNoed

D3

Cons

Page 170f 112

wa
Se
qPNR

:

:

San Francisco Fire Department\§is) Unusual OccurrenceEE
tp aa al 0DL da
From:
———
To:
Reference:

0312412023
ursSORIENED

Chief of Department
Rules and Regulations, Section 1128

1. On March 21, 2022, Engine 41 responded to multiple calls of trees, and wires down, due to theextreme weather.
2. Manyofthese cals were along Clay street from Polk to Jones, where multiple downed trees hadbrought down Muni "trolley" high voltage overhead wires.
3. Muni responded at Engine 41's request, and was able to de-energize the lines, mitigating theelectrical hazard.
4. The lines still possessed a physical hazard as they lay on the ground in some locations, and thenreturned to the next pole in an arc.
5. Engine 41 cordoned off multiple intersections to keep traffic from driving up streets into the low

hanging muni wires.

6. One of the streets closed off, with Caution tape and Caution sandwich boards, was the 1400 block ofClay street, between Hyde and Leavenworth.

7. At 21:56 incident # <23039567>, Engine 41 responded to the Intersection of Clay/Leavenworth for

an "electrical hazard".

8. Upon arrival we discovered two Cruise driverless vehicles had driven up Clay street, through our‘caution tape at Hyde, continued on, hit the low hanging muni wire and entangling the wire on their roof

elements. The two Cruise vehicles continued up Ciay through our second setofcaution tape at
Leavenworth. As they continued up the street, rise in elevation increased the tensionofthe wire on theroof, and the two vehicles finally came to a stop in the intersection of Clay and Leavenworth.
9. Two Cruise employees arrived on scene. We had them take over manual control of the vehicles. We
had to back the vehicles halfa block back down Cay street to release the tension on the wire, toremove it from their roof elements.
10. This incident raises many serious concerns about the safety of these Cruise driverless vehicles, The
need for these vehicles to recognize a road closed by caution tape, and caution sandwich boards isimperative. Secondly, the vehicle failed to recognize the large gauge Muni line hanging in its path. If
this wire had still been "hot" this would have been much more hazardous. It is also of note that thevehicle did not recognize when ithitthe heavy wire, or that it was being dragged on ts rooftop for halfa block.
11.1 have attached pictures. Note the caution tape and sandwich board wrapped around the vehicle.
The Muni wire can also been seen on the roof.
To
Workflow _FromEa
Forwarded
024025 wmmm—T
ConenisNoled 801
03242023 @mmmmTContents Noted
Contents Noted D203252023 o—_—S
Contents Noted CD23252023 pam
Page 190f 112

CMe

nH

:

Ww
NR San Francisco Fire Departmentey) Unusual Occurrencei

03/30/2023

From:

JU

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. 3/29/23 Incident #23043573 3909 Mission: Self driving vehicle "CRUISE" stopped approximately 8'
behind E32. Couple minutes later it moved about 5'. I knocked on the window and attempted to makecontact. Took several minutes for the window to roll down, and I was able to speak to Customer Care.
After the incident, the vehicle moved but stopped in the intersection , proceeded to make a right tun
but into the oncoming lane. It corrected itself and got into the correct lane and drove of.
Workflow FromTo
03/3072023

Ew——

Draft

—

Form created as draft. SelectApply Changes
to begin workflow.

Page 2201112

- A(GR San Francisco Fire Department)) Unusual Occurrence
Wi%m

4

From:

SA

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

041412023

1. On April 14, 2023 while conducting a hoseline drill in front of Fire Station 14, a self-driving car

traveled past a hoseline in operation. The car pulled to the right and stopped while t attempted contact‘with it's monitoring company.
2. Batt. 07,e who was observing the drill spoke via car phone with the company and reported theoccurrenc to them and that there vas no damage to the cr.
3. Prior to the dri, traffic cones were placed to create a safe working area with several members
monitoring traffic in front of Fire Station 14.
To
Workllow _ From
Fowarded | TH
Catarz0zs ep
B07
Info Only
ounanezs mpm
aor
Info Orly
0142025 amContents ned.
ConentaNoted 807
ouranozs mw
retunedEn
Reumedoutazzs em.
Worktow End
Orta: —

Page 23of 12

a
i
G
~ —
AGA San Francisco
Fire Department

ups I—_Aest) Unusual OccurrenceiE
mies mieFrom:

A ————

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

04/14/2023

1. On April 14, 2023, E14, E31, T14 and B07 were conducting a hose line drill in front of Fire Station

14. While operating a hose stream, a self-driving car drove through the stream of water and pulled to
the right side of the road and activated it's hazard lights.
2. The firefightersatthe drill had placed traffic cones in the street to create a safe working area andhad assigned safety people to monitor road conditions. Prior to the car driving through the stream ofwater, the car approched the cones, stopped and then proceeded to drive into the work area.
3. Batt. 07, Chief Styles approched the car and made verbal contact with the technology attendant andinformed them of the situation and that there was no damage to the car.
4. The attendant was instructed to roll up the windows and proceed away from the drill site.
5. The car company is named Cruise.
Workflow _FromTo
1an02 tm
ForwardedTia
outros Amy
Contents Noted B07
Contents noted.
owen San
Contents Noted D2
Adtional Informatin- Afer talkingtothe
attendant,the vehide drove off afera few
minutes.
Ounaz0zs emm—
Contents Noted CD2
ow172023 em
Acknowledged Coffink
another driverlss nddentforCptFores
outs eve
Acknowledged FloresR
Please ford Incident
to ula Frediander andend word
0412472023(m—_

Workflow End

Page25 of 112

wv
A San Francisco Fire Department

Wis 2) Unusual Occurrence
Si

From:

04/17/2023——————
TRTo:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1.0n Sunday 4/16/2023 at approximately 23:53 Engine 5 was responding to a full Box at 2488 Geary
Blvd.
2.Engine 5 was the supply engine and drove around the block to back down from the Lyon street side.
3.As we were approaching Geary Bivd from Lyon St we were blocked by a Cruse self driving vehicle.
4.The self driving vehicle would not move and this created an obstacle for water supply.
6.Luckily this was a false alarm and the members on scene were able to improvise.
7.Vehicle information: Cruse vehicle is license #751145P3.

Workflow _Fromrez: em—ourraces wm
4172025 Wemaoarte0zs

Forwarded
Contents Noted
ContemsNoled
ReturnedContents Noted

To
05
605
D2
es
B05

04192023 Gwmaalp ~~ ContentsNoted

D2047202023

FAN.

Acknowledged—

ouzorzzs—

Acknowledged

CDT

Oa1o2023 mmmmm—

4242025 Wy

Conteris Noted

Worklow End

CAMASC

CD2

Contents noted
Take out 47
Forwarding up Chain with requested edit.

Resubmitted after edited 3 per D2 Sorts
request.
this is becoming a daily problem. These things:
must
betakenoffthe roadhis
i becominga daly sue. We should
considerforma eter o he tate requesting
20 end to the program

Page 27 of 12

Scene

>

PRA San Francisco Fire Department\Wisk)) General Formis

04/18/2023

ficultAssistant Deputy Chief- Fire Prevention and Investigation

From:
To:

Subject:

Autonomous Vehicle Incident

Reference:

E mail

1. On 4/18/23 incident #23052651 we were operating at a working fire at 1597 Howard st.

2. E36 was on the 12th st side with a supply led from them to E29 supplying on the NW comer.
from tailboard of E36 and twenty feet from intersection while still an active operation. All FD apparatus
had C3 lights on.
3. A "Cruise" autonomous vehicle drove N on 12th and stopped in our scene approximately ten feet

4. We attempted to disable the vehicle
5. Car sat for approximately ten minutes and then drove off on its own accord prior to our ability to takephotos or get plate number.

Workflow From
Oiltenczs ewmemm—

Forwarded

04/18/2023@E-=-D.

Contents Noted ~~ CD2.

04/19/2023

AR—G—_—N—

04182023 mmContents Noted

To
0s

C1

=
contents notedlerym indent.
obateve
This is becoming a pr
ed toputoutcones orabenexp'ectt
Drivers ces
flar
atevery working incident to educate theautonomous vehides. Tl forward to Coffin

Workflow End

Page 2901112

CAMA

KCene

(

4AT

5

:

PGA ) San Francisco Fire Department&hizs%)) Unusual Occurrence
if
From:

04/20/2023

iRR

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. At incident #23053861 at approx. 1530 hours on 04/20/23 at a working fire along the corner of
Sacramento and Presidio Bivd., a CRUISE driverless vehicle license plate # 74169C3 came into an active

fire scene at 3249 Sacramento St..
2. When this driverless car first came into the block at Sacramento and Presidio, it stopped initially next
to E51, and then began to jut forward incrementally proceeding east towards the fire scene itself at
3249 Sacramento.
3. Asiit proceeded, it came into close contact with the driver of ES1 who was supplying the main engine

in front of the fire building, other firefighters proceeding to the command post, and also hose supplying
the lead engine in front of the fire building.
4. To stop its forward movement, I had thedriverof ES1 place chalk blocks on the CRUISE vehicle
driver front tre, stopping its forward movement.

5. RC 2, Cpt. Salan then gave me the emergency contact number to CRUISE to try to make contact withthe company concerning this vehicle.
6. With contact with the company, the operator after about 8-10 minutes (and with my assistance

stopping traffic) was able to back the car out from the fire scene and the car proceeded north along
Presidio Bivd.
To
Workflow _ From
04202025 Swamy
Forwarded
Tanmpatd forward
04212023 Wemmm—
CoenisNoted CD2“Tiserratic behavior continued a the vehide
drove away impeding MUNI travel.
o4z12023 wm—
Acknowledged Swine
Weneed thi addressed, and movedupthe

04/21/2023

Rem—

Acknowledged

0424/2023——)

Workflow End

cot‘priority list. Its becoming a daily problem‘yet another

Page 31af 12

CASE

Scene

&

om
@N2 San Francisco Fire Department(aed)iy) Unusual Occurrence
i

From:

04/25/2023

TT ——

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1.0n 04/25/2023 at 1025 hours T11 was responding code 3 to Box 8217 at 442 Arlington St. Incident#23056225
2. Enroute T11 tured left onto Roanoke St from Chenery St. Approaching from the opposite direction
was a driverless Waymo Jaguar vehicle. The vehicle continued to approach until within 10 feet andstopped. Roanoke is a single lane street with parallel parking on both sides. The vehicle remained

blocking the street. We approached the vehicle on foot, the windows went down and we heard a voiceof the operator monitoring the vehicle. I informed the monitor that the vehicle was blocking a SFFD
vehicle's response to a SIB Box and that they needed to direct the vehicle into the driveway adjacent tothe car. The monitor responded "yes, I understand." The Waymo vehicle however did not move. I
directed the T11 driver to back up T11 onto Chenery and continue to the call on the next available street
wide enough for the truck, Bosworth St.
3. Battalion 6 was notified as to the reason for our delay. B06 had already cancelled the Box before wearrived on scene.
4. On our route back to the firehouse we saw another Waymo vehicle that had a operator in the vehicle.
I informed them of what occurred. He stated he would report it and recommend the area to be blocked

for their vehicles as the streets are to narrow for them to operate.

Workflow _ From
Ouzsiz0zs emm—ouzs2023 am—
ouzs2023 wm
04252023 Gm
04250023 am
0427/2023

S—

4272025 W—
04272023 Nema

Forwarded
Info Only
Acknowledged
Contents Noted
Contents Noted

To
Hoo
808
D3
COZ
C1

Info Only.

K
CoffinInfo Only
Workow End

CoffinWaymoblockingTi response toBox 8127
clan puta picture ofthis Waymo incident
on Twitter,
Contents Noted

Page 330f 112

PRA San Francisco Fire Departmentsy) Unusual Occurrence

041252023

i
From:

SORE

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. At approximately 21:53 on April 25, 2023 Truck 3 was in route to a building alarm at 1177 Market
Street (Incident #2305652) going Code 3 with lights and siren.
2. Truck 3 was travelling south on Polk Street, and as we approached Geary Street a Cruise autonomousvehicle was in the right lane west bound on Geary. All traffic was stopped on Polk and Geary except that
the Cruise vehicle was lurching forward in uneven movements toward the intersection. The vehicle cameofTruck 3 had slowed down the Cruise vehicle
t00 close to Truck 3's path. It seemed that i the drivermight have continued in front of us. We were going approximately 5-10 mph after first controling theintersection.
3. We could not see a driver or passenger in the vehicle.
Workflow_ FromTo
04252023

04252023
04262023
04262023
04272023
04272025
4272023

Cummiemmily

WWW
w—
Wem
wma
pn,
mm

Forwarded

ConlenisNoted
ContenisNoted
CortenisNoted
Acknowledged
Contents Noted
Workflow End

Tos

B04
D2
CD2
emm—_
C1

noted
2s mentioned, driverlss carIncidentsare
dangerous and frequent.
antherPage 35 of 12

7
PRA San Francisco Fire Department\§éist)) Unusual OccurrenceSE0412612023

From:
I——
To
Chief of Department
Reference: Rules and Regulations, Section 1128
1. At 18:08 on April 26, 2023 I arrived on scene at 2396 Pine Street (Incident #23056929).

2. Engine 38 positioned in front of the apartment building, just past the entrance.
3. A Cruise autonomous vehicle was behind Engine 38 when they arrived. The Cruise vehicle stopped
approximately 10-15 feet behind the engine.
4. wanted the vehicle to move so that Truck 5 would be able to stop behind Engine 38 for a good it toaerial shot.Itried waving my arms, and walking at the vehicle from the sidewalk side to encourage
go around the engine. Eventually the vehicle moved forward to within approximately 6 feet of Engine

38's tailboard. This made things worse because it was close to compromising a hose lead from 38, and it
would have been hardfor the vehicle to turn enough to pass Engine 38 going forward. Iwould also be

uncomfortable with crew members working at the taiboard as I have seen these vehicles lurch
unexpectedy. don't trust what might happen with hoses and ladders being carried very close to thesensors of the vehicle.
5. Around this time Truck 5 arrived. I motioned for the driver to pull up behind the Cruise vehicle withcode 3 lights, hoping the vehicle would move out of the way. I was standing on the sidewalk side of thevehicle to make it possible for the vehicle to go out into traffic. This did not work.

6. The crew of Truck 5 assisted me with poking and prodding the vehicle, and pounding on the windows

until the driver's window rolled down. This happened a couple minutes after the vehicle initially stopped.
I went to the window and communicated with someone. The individual apologized for theinconvenience", and said a team was working on moving the car. Even after talking to him the car did
not immediately get moved from the scene. I informed him that this time it was an "inconvenience", but
if someone needed to be rescued by the Truck it could have been a lfe and death situation.
7. 1f the same situation occurs behind an aerial truck it may be dificult or Impossible to remove wooden
ladders.
To
Workflow _ From
202 emai
Fowarded
20ienc) em
ContentsNoted D2
Forwarded
This is an Increasing problem. I beleve there
0i262029 emma ContentsNoted CD2
are many mors incidents that are not beng
ported, Instructing BCs to make sure crews
ar reportingthes for amoreaccuratepictureofthis oreport tocompanyandpowersthat
be.
04/27/2023

E—-

ores w—4202) N—

‘Acknowledged

Acknowledged
Woriow End

J

CD

anothernumber3 today!
Page Tot 112

CNUs ST

Stenc

4%. San Francisco Fire Department(ads)ek) Unusual Occurrence
3
pe

From:
To:

04/26/2023

I———
Chief of Department

Reference: Rules and Regulations, Section 1128
1. On 4/26/2023 Truck 5, Engine 5 and Battalion 4 were dispatched to a building alarm 1425 Fillmore,
Incident # 23057047
2. Both Engine and Truck were facing North in the Southbound lane leaving one lane for through traffic.
3. As we exited the rigs to gather equipment a "Cruise" autonomous vehicle attempted to squeeze past
both rigs. When the driver of the Truck 5 stepped in front of the vehicle it honked at us and completely
froze blocking any through traffic, There were three passengers In the back seat who were unable tocontrol the vehicle. 1 made my way to the window spoke vith an operator over the intercom andexplained that this vehicle needs to either wait for all members of the fire department crews to Safely
exit the area or pull to the curb. The vehicle was remotely taken over and guided past our emergency
vehicles.

4. As these autonomous vehicles are learning traffic patterns they have become more aggressive with
first responder units and their attempts to navigate around them. They could potentially delay fast,

aggressive hose leads as well as impede ladder and tool removal from trucks.
5. This was our second such interaction today. First was UO submitted by Battalion 4 Incident#
23056929
Workflow _ FromTo
ET)
Contents Noted 805
04272023 QimmalylContentsNoted

D2

Contents noted

04/27/2023

Contents Noted

co2

More Cruise

T—_———G

0422025 shameouzrnez e—4272023 Manan

Acknoviedged admis
Contents Noted CD
VWorklow End

anctreranother

Page 390f 112

#q
PGA San Francisco Fire Department(Ess) Unusual OccurrenceNy
05/03/2023

7

a
a
From:

i

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. On the morning of 04/29/2023 E44 responded to a medical dispatch at 162 Tioga Road at 01:29 am.
2. Upon arrival there was a male passenger in the back seat ofa WAYMO ride share vehicle.
3, The passenger was finally awakened and was able to open the door.
4. The passenger who had a smell of etoh declined any medical attention.
5. When the passenger left the vehicle FF Loh from E44 gained access to the drivers seat and a rideshare technician came onto audio.
6. It was stated that the WAYMO vehicle was blocking a narrow street and we needed access to the car
to move it and park it out of the way.
7. The WAYMO representative stated that we were not granted access to move the car and that atechnician needed to come out and move the car.
To
Workflow _ From
05/03/2023

A—_—_—

Forwarded

E17

05/03/2023

e———_—

Contents Noted

Eum—05092023 remem»

Contents Noted

C02

dine

Acknowledged—[a05/09/2023

051092023 wm"
05002023 ew.

Contents Noted

Contents Noted
Worlow End

aummmmmum»that we do na have thetis veryconc
abityto manueralnilyngtakeover and movethesears.
Forwarding drveress vefice UO from CPT
Murphy on 5/3/2023.

Please forward to Cty AV representative toreport to Waymo.

Page 41 of 12

29
4

A San Francisco Fire DepartmentvWim) Unusual Occurrence
EY

0

ATI

eo

TL ih AWa

From:

T————

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128lM

05/03/2023

imi:

a
yy
EM
_
suddenly stopped in
1. respectfully submit this Unusual Occurence to document a Waymo vehicleto thatfront of D3's Bugay as D3's emergency lights were applied while attempting back into the Quarters of
Station 7.
2. This incident occurred on May 3, 2023 at approximately 2110 hours when D3 was returning from aBox. The license # was 15104H3.
3, A video clip has been emailed to the deputy Chief of Operations as it could not be uploaded to thisUO on HRMS.
To
Workflow _ From0
Forwarded
05032025 mmmmmm—I
05032023 Mwm—_ Contents Noted C2
ane,“Thevideodip hasbeenemalledto youas twouldnotupload on HRMS In Box.
05092023 ao
Acknowledged CDT
Video emailedtoyou
Is this al goingtodm prevention?
Acknoviedged Ramm
0512023 em)
0511/2023

N—

osi22023 ween

Info Only

Workow End—

iPage 43of 112

z¥
PA San Francisco Fire Department

Wy Unusual OccurrenceNi

05/05/2023

ea
e
——e
I
From:
Deputy Chief of Operations
To:
Reference: Rules and Regulations, Section 1128e_atched to Incident #23060822 at 1161 Mission St.
1. On May 4, 2023 at 2141 hours Engine 36 was dispe
for the Buikling Alarm.
2. Engine 36 went enroute at 2142.

3. While attempting to leave the apparatus bay of Station 36 to respond to the Alarm, Engine 36
became blocked in the station by a driverless vehicle.

4. The crew of Engine 36 exited the engine and approached the driverless vehicle that had stopped in
front of the apparatus bay in attempt to get thedriveriss vehicle to move.
5. While attempting to get the driverless vehicle to move Battalion 2 was notified by Engine 1 that thebuilding alarm was set off in relation to Engine 1's
Incident #23060819 a dumpster fire.
6. Battalion 2 canceled the Incident, Engine 36 going AOR at 2145 while Engine 36 was stil attempting
to get the driverless vehicle to move.
7. With the incident being canceled, Engine 36 backed into quarters.
8. Not until Engine 36 backed into the apparatus bay did the driverless vehicle drive away from blocking
the apparatus bay of Engine 36.
©
Workflow _ From
T%
Forwarded
505202 ampmm—
contents noted
Contents Noted 802
os0s2025 mn
82was noted this morning of an unusual
05052023 Memmladady ComentsNoled D3
occurence involvinga diveress vehiceblocking the apparatus bay during a dispatch.
ellerdefrsom the incideUntnsof
beEnfogirnet36wawasabs lecanctono
ponding
delay. Pictures ofvehicle are enclosed.
05052023 wm, Contents Noted CD2
we shouldbeablteo sue a tation vith ths
Acknowledged CDI
05092023 ami
nfo—
nfo Only
0502023 emmwe—
05/09/2023

CRE—G-_

Workflow End

Page 45 of 112

29

TW
—
PBA San Francisco Fire DepartmentWis) Unusual OccurrenceiP

05/08/2023

Cs lie TL
em
er
EA———
From:
To:

Deputy Chief of Operations

Reference:

Rules and Regulations, Section 1128

ie
C
_
g
1.

On May 6, 2023 BO1 responded toa Building Alarm at 1060 Bush, Inc# 23061787.

2. E41 was parked in the Number 1 lane. BO1 parked behind E41 in the Number 1 lane.
3. Approximately 2-3 minutes after B01 had parked a Cruise Driverless car pulled up directly behind
B01 in the Number 1 lane and stopped.
4. The Cruise Driverless car remained behind BO1 for the duration of the call and then after sitting
still for 20 minutes it pulled into the Number 2 lane, narrowly missinga firefighter on E41 as he wasputting gear back into the Engine.

Per a request form Division 2 I am submitting the Unsual Occurrence Form with attached photos
5.
through the Chain of Command to Deputy Chief Robert Postel...

6. If you have any questions please do not hesitate to callTo
Workflow _ From
Driveriss Crue vehide photos
02
Fomwarded
05082025 Wmmmmnt®
05/10/2023

051202305112023
051202905112023
051122023

emmnm)!

Gem
Wemmm—
@mmm—
W—G
mmm

Contents Noted ~~ CD2

Acknowledged
Retumednfo Only
Workow End
Contents Noted

CDT
Jy
—

Close call again. CRUISE

another
for flores

Femi

Page 48 of 112

aL 22—i“

PGA \ San Francisco Fire Department

Wizzky) General Form
Siig

a

eee

re

ieee

From:

RAAT

To:

Chief
- Battalion 05

Subject:

Autonomous Vehicle, Obstruction of Fire Apparatus

05/09/2023

pees aptiet

Reference:

1. The following event occurred on May Sth, 2023 at 11:13

2. Reference Waymo Autonomous vehicle with no attendant; License Plate 404893
3. While traveling southbound on Webster and returning to quarters, Truck 5 "swung out" to align the
trailer for backing into quarters.
4. Even though Truck 5 had all emergency lights operating, a Waymo vehicle as described aboveofTruck 5 and stopped in a location that prevented our rearward travel. It
approached the rear
continued to creep forward until I tuned it's drivers-side mirror forward and pounded on the window.
5. After leaning into the vehicle to call an attendant on the telephone, and being connected, I was
informed that there Is no way to move the vehicle. The attendant was unable to move the vehicle
backward, and told me that I would be unable to move the vehicle myself. The vehicle then tried to rol
the windows up while I was leaning in and talking to the telephone attendant.

6. I was then informed that we would have to wait for a Waymo person to arrive to move the vehicle.

7. Truck 5 abandoned its efforts to back into quarters and drove around the block so the Waymo car
could move out from in front of the Fire Station.
8. The Waymo vehicle moved over to the side of the street after Truck 5 had cleared the street for it,
and then drove off before anyone came to assist or we were able to make additional contact withWaymo personnel regarding the car.
To
Workflow __ From
Ta
05
Forwarded
050972025 am
051002023

Mu—=—_

Contents Noted

05/00/2023

M——

Workflow End

BOS.
“This shouldbean Unusual Occurrence:

Page 510i 112

A San Francisco Fire Departmentiss) Unusual OccurrenceFc

05/09/2023

From:

TT

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. On May 9th 2023 at 1555hrs in front of Station 2 a Cruise autonomous car failed to stop and ran over
several lengths of hose that were laid out in the street. The car ran over the gorter/wye. The car
stopped when it was approached by members of E2.

2. The SFPD were notified and officer Tang Badge # 877 responded. Incident # 230322078

3. Vehicle information : License # 740733, orange and white Cruise car.
4. Driver info: No driver present in vehicle..

5. Cruise was notified by cellphone. They arrived at 1315 hrs, Carina Contrares Gudino Cell phone # 415

314 1554 was the cruise representative.
6. A equipment request for a replacement gorter and Wye was submitted via HRMS.

7. There were no injuries connected with this incident.
8. Pictures of the incident were sent to Div 2 .
Worldlow__ FromTo
05092023 we
Forwarded
2)05092023 Lm
Contents Noted B01
05092023 Jemmmmgg
ContentsNoled D2
05/10/2023

mm—_———>

Contents Noted ~~ CD205112023 mmm

Acknowledged

CDI

05/11/2023

Gm

Contents Noed

igummd05112023 wmmm—
06232020 dmmm—uWorkflow End
Info Oly

30623/2023

Info Only

Jmm—

io

Information reviewed.
2 Contacted and picturesof incident
forwarded via Cell phone.
CRUISE

Appears a ort shutoffandwye vere‘damaged. That Is several thousand dollars ofdamageidyou hear whowe are supposedto submit
the damage costs to?
mM
Please see attached unusual Occurrence.

Cruse contact person, regarding Insurance
dlaim (Marissa 702-790-5180).

Page 59.f 112

CAUS ee

Noa

R28
RA

San Francisco Fire Departmentiss) Unusual Occurrence

05/19/2023

SU
From:

BT

—————

ily

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. 0n 16 May 2023 at 0915 hours (#2306112) IFO 109 Oak st 3 driverless vehicles caused traffic toback up.
2. The driverless vehicles were all "Cruise" License # 750140P3, 2531953, (the 1st vehicle license plate# was not recorded).
3. Traffic went from 3 lanes down to 1 because of a vehicle accident.
4. Each one of these three "Cruise" driverless vehicles stopped and blocked traffic both before passing
the Fire Engine and immediately in front of the Fire Engine.
5. This caused already slow traffic to come to a standstill and the drivers of the other vehicles became

frustrated and were honking their homns trying to coerce the driverless vehicles to move through thegreen lights.
6. These events were witnessed by the crew of E-36, B-2 and the responding SFPD Officer.

Workflow _From
05/19/2023

Fmm——

051972020 dmmm—"

To

Forwarded

E36

10 Only—

0123/2023 =)Acknowledged

HERET®

05/27/2023

minasanle

Acknowledged-

05/27/2023

Guim

06/01/2023

Contents Noted ~~ Eu

Acknoviedged
Ino Onlygmaimiumiemny

Info Only.

0——

06/01/2023 \iaiammuig

nfo Onlyaa

os002023 em
05002020 Wma
0012023 N—.
08012020 Mmmm)

Contents Noted

Info Only
Workflow End——

Page 1 of 112

2% 24
7 PA San Francisco Fire Department\6s%)) Unusual Occurrence
aS
From:

05/27/2023————————————

To:
Chief of Department
Reference: Rules and Regulations, Section 1128
1. On Friday May 26I responded to 99 Grove as the Officer of E36 to a call for service CAD#23070893.
2. At approximately 2215hrs we approached the intersection of Polk and Grove to find a driverlessvehicle stopped in the intersection
3. The position of the vehicle was in such a position that the engine driver had to maneuver around inheavy traffic to obtain apparatus placement

4. The AV company involved was Cruise, one vehicle involved, California license plate number 2565353
5. There was no call to the company for assistance, once we maneuvered around the vehicle andpositioned the vehicle drove away
6. recommend these companies work to ensure the vehicles pull over appropriately and not stop theirvehicles in the middle of intersections.
Workflow_ From©
05/27/2023

Gey

Forwarded

E36

osizrz0zs —-—Osos —
0527002 WEEMS
053072023 em

Contents Noted
Contents Noted
ComentsNoted
Retumed

802
D3
CD
0s

0502023 mm

Retumedme05012023 samy
06022029 ammn—

Acknowledged
Contents Noted

D3
CD206022023 pumeiy

Acknowledged

B_—__—__

Info Onlycot

06/02/2023

Os0s2023

N=

Contents Noted
Ifthe inks on the bottom of the form are
attachments, they are not able to be opened.
Please use the proper attachment process. Ifthey are something ls, what ae they andwhy are they in the report?
cre,Please see my corrected version ofthe
attachments.
Thank you.
Corrected attachments
links corrected as requested

Wordiow End

Page g3of 12

RA San Francisco Fire Department
Wit) Unusual OccurrenceNg

eb Tan

Aa

From:

—
T——
I

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

oy,

LL

05/30/2023
et1. On May 30, 2023, at 11:39 hours, I (B06) was dispatched to Incident # 23072355 with E11 and T11
fora building alarm at 1220 Noe Street.
2. When arrived on scene, I parked my vehicle across the street from the incident address and noticed
a driverless Waymo vehicle, traveling southbound on Noe had stopped approximately 15 feet from thecomer of 25th Street. The Waymo vehicle was driverless, however there was a third party female
passenger in the back seat. Her purpose was "testing" and she stated she was not a Waymo
employee.
3. 1 approached the Waymo vehicle, license plate #53499F3 and could hear the female passenger
speaking to a Waymo representative. I told the Waymo representative that he needed to movethe
vehicle out of the way immediately. He stated that he was unable to do it, that a human had to move it
and that he had roadside assistance dispatched and their ETA would be approximately 3 minutes.
4. In the meantime, 1 observed the Waymo vehicle move approximately 5 feet forward, reversed to theend of the block and made a 3 point turn on Noe Street inorderto head Northbound on Noe Street.
5. It took approximately 6 minutes for the vehicle to move out of the way of the incident.

Workflow_ Fromos02023 wen

Forwarded

To
03

S——_

Contents Noted

cDb205312023 mn

Acknowledgedama

05/31/2023

Info Onlyco1

05/302023—

06012023 enmemmm

mM

Worklow End

Page 66 of 112

R28
A San Francisco Fire Department
Wiz) Unusual Occurrence
Nig

05/31/2023

From:

—————
A

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

1. On 5/31/23 B10, E29, T7 were ofs of incident #23072652 at 693 Vermont St. E29 and T7 wereparked directly in front of this address in the northboundtraffic lane with code 3 lights on.

2. While members were getting ready to put equipment back on apparatus a Cruise vehicle travelingincident. License #83047R3 with thenorthbound on Vermont St. began approaching thename of Carnation on the bumper. The vehicle slowed to an almost stop approximately 15' from E29s
“The car then began to continuously creep towards E29 while starting and stopping.
rear bumper.

At this point the car was approximately 3' from E29 and I felt the‘members were not safe to

put away their equipment. As we have been instructed I moved the rectangular object mounded on thepassenger side where

the rear view mirror is typically. The car stopped for a moment and showedwithin 18" of E29s
"Camation reported a collision” on all 4 screens in the car. The care then got
bumper and turned into the opposing southbound lane parkingnextto E29. The vehicle then stopped
for a few minutes with thecollision message on all 4 screens. Doors were locked, windows
up, and no controller on the speaker attempting to talk to us. The vehicle then suddenly
clearedthe collision message, a map appeared and then the vehicle drove off.

Workflow __FromO5o2023 mm
os12023 een.
05012023 em

Forwarded
Contents Noted
Contents Noted

To
0
CD2
CD

051312023 Fem

Contents Noted

mang

06012023 laste

Workflow End

osatzozs o—Info Only

Cwm

sending to Sam also

Lu

Srene

Page
68 of 12

A San Francisco Fire Department

feiss) Unusual Occurrence

06/05/2023

Sv

From:

TI
—

To:

Chief of Department

Reference:

Rules and Regulations, Section 1128

es
m
N
_—
1. On June Sth, 2023 at 08:08 hours E02 was dispatched to 766 Vallejo Code 3(23075083) for SOB.
2. The Engine bay was blocked by a driverless Waymo car with a passenger in the back. License Plate
535213.
3. The passenger got out and walked away leaving the car stil blocking the firehouse.
to move
4. T got in the car and was talking to Someone from Waymo remotely telling them they neededoverride:the car ASAP for our Code 3 call. The employee from Waymo was flustered and was trying to
the car and have it moved. It took over 2 minutes for the car to finally move.
5. E02 was than able to respond. Battalion 1 was notified when back in quarters.

Workflow_ From
061052023

FSSS——yTo

Contents Noted ~~ BOT

0610672023 eMmmmmangg ~~ Contens Noted

miniaqgip notifiedofother needs regarding

D205062023 Tamang!
os07202) PWG,

ContenisNoted C02
Retumed02008202) Wee—"

Relumed06/08/2023 Smid

Retumed06/09/2023 elimi, Wrkow End

Bot
a

wes
00Report: Ttwas »code 3 al 30there
the
on
info
id
other
photographsorforno timevehi.
Contents noted. I can't find the autonomous
Gar forwarding drop dow.
The correct form isthfirst one under General
Form on the drop down men. Pleaseresubmit on the proper form
See return comments.

Page 7001 112

20 ar AY

Em-

A San Francisco Fire Department—— 5) Autonomous Vehicle Incident-

06/07/2023

derrd
emetic
From:
————
To:

Deputy Chief of Operations

Reference:

Unusual Occurrence 1128

Incident Date

06/07/2023

Time

07:47

wm

i

ities

Incident No
Location

491 Chestnut St

AV Company

Waymo

Numberof AVs Involved

1

Licence Plate(s)40693F3
Contacted Company?
Yes
AV Company Response ~~ 8
TimeSupervisor ID

RI1361 Rivieccio,Claudio N

eeof Event)
Impact (Description olBYent)
IpactDescripion

1. E02 was blocked in Quarters due to Waymo Car parked in front of Engine Bay. Incident #23076009.
2. E02 was not able to respond to Medical call. Notified Radio we were delayed.

3. Knocked on windowsofcar to get a holdof Waymo employee. Took over 8 minutes to have car put
into manual mode to move.
4. Notified BO1.
5. Notified Scott Campbell, First Responder Ambassador Waymo of the situation. Second time thisweek this has happen.
6. Fileda Failure to Report Form to CD2.
To
Workflow _ From
TET
B01
Forwarded
06072025 mmm
061072023

Cuidem®

Acknowledged

D2

06/08/2023

WEN

Acknowledged

C2

06/08/2023

J
NES

06082023 m——=Acknowledged

CD

Acknowledged

Pim

Assignment” form also

“Failure To Complete‘completed
today (6/7/2023) for this event;
SFPD Inc. # 231580556; Waymo venice
Tense pate (CA)# 406933.

form
2nd time this week.wasthereanotherhat came up. | dont remember i. all incidents
must be documented.
Page 7401 112

—=

21 0

3
i
a /6A) San Francisco=
Fire Departmentbist) Autonomous Vehicle Incident=

06/12/2023

i

as,

ee
RT
From:
R—
To:

Deputy Chief of Operations

Reference:a aIncident Date
Time

ida

toe

06/11/2023
22:31

Incident No
Location

Post Street/Leavenworth Street

AV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)Contacted Company?
AV Company Response

No

Time

Supervisor ID.

ee,

Ea DoEO

Impact (Description of Event)|

1. On Sunday, June 11, 2023 at 22:31, Truck 3 was responding with emergency lights and siren to a|drive in both lanes to avoid holes and bumps in the road.
3. We crossed the intersection of Leavenworth Street against the red light after gaining control of the|building alarm at 711 Post Street. Incident # 23078275.
2. Truck 3 was mostly in the center lane and somewhat in the left lane, heading East on Post Street. We
intersection. Vehicles with drivers stopped before entering the intersection in the right and left lane on

Leavenworth. The unusual occurrence was that a Cruise autonomous car was coming from further down

the hill in the center lane. The autonomous vehicle did not slow down until it entered the intersection,and barely stopped a few feet from the tiller wheels of Truck 3. Truck 3 was moving at approximately
10 miles per hour through the intersection. Any vehicle coming up Leavenworth had plenty of time toreact to the emergency lights on the truck, but the cruise vehicle did not react until almost coliding withthe back of the trailer in the middle of the intersection.
4. No pictures were taken as we were responding to an emergency.
To
Workflow _ Fromoo
B04
Forwarded
2202 Gada
08/12/2023

Umum

Workflow End“

Page 8001 112

ES
PR San Francisco Fire Department
Wiig) Autonomous Vehicle Incident
Nis

06/12/2023

STIS

From:

Deputy Chief of Operations

To:
Reference:
Incident Date

06/06/2023

Time

16:25

Incident No
Location

2750 Jackson Street

AV Company

CruiseNumberof AVs Involved

2

Licence Plate(s)Jingle and Milky Way (16773F3)

Contacted Company?

No

AV Company Response
Time
Supervisor ID
Impact (Description of Event)

1. Sorry for late notice. I forgot about the incident when trying to concentrate on building alarm andbroken sprinkler.
2. Engine 38 and Truck 5 were both double parked on Jackson facing Westbound in front of said
address. Two cruise autonomous vehicles were coming from opposing directions in the one available
open lane. Engine 38 had emergency lights on, Truck 5 did not, Battalion 4 bugay did not. Whenarthdley,autonomous vehicles met head on they froze. It took a bit of time before Jingle backed up awkw
and Milky Way was able to pass by.
3. Had this been a full box and other rigs were arriving then the open lane would have been rendereduseless.
4.1 would like to suggest that the company program the vehicles to avoid an emergency scene by goingaround the block, and avoid the area if possible. Most people do this in order to stay outofthe way andavoid a traffic jam.
ree
i odratedeteI
B04
0622025 mama | Fowwarde
Contents Noted

06/12/2023

SGG—

06212023 mmm

Acknowledged

06/22/2023—

Workflow End

06222028 myInfo Only“

D2

More incidents

CD—

Page 820f 112

CA So

Seen

Fp

NA San Francisco Fire Department(iS) Unusual Occurrence- Accident
i

06/13/2023

From:

TS“
—

To:

Chief of Department

Reference:

Rules and Regulations, Section 1127

1. E18 was involved ina non injury traffic accident on 6/12/2023 at 2200 hours.
a vehicle accident response at the intersection of 25th and Lincoln
2. E18 was clearing the scene ofway.

3. E18 was backing down Lincoln way West bound in the East bound lanes. East bound lanes wereclosed by SFPD. While both the members of E18 were backing the driver in the appropriate positions theofficer was stopping traffic on Lincoln Way in the West bound direction. All drivers in their personalvehicles complied and were stopping for an E18 an emergency vehicle. A Cruise self driving car failed toyield and was driving directly toward the officer. One of the backers turned their attention from backing
the engine driver to the officer and the self driving car. The officer was moving out of the way of theself driving car to avoid being struck. Without the direction of that backer E18 struck a non occupied
parked car, parked on Lincoln Way.

4. E18 immediately stopped moved to a safe location notified Batt 8 and SFPD and went out of service
to document the backing accident.

5. Had it not been for a self driving car not yielding to an emergency vehicle, the backer and officer's

attention would not have been changed from backing E18 to the hazard of a not yielding self driving car.

6. An accident report has been filed.

Workllow _ From
Ge1a0zs emm—

Fowarded

061132023

Contents Noted ~~ B08.

HN——

™
Ee

06132020 Mmm— Rotumedee

Peasecomect grammar.

06/13/2023

SHN—_—G

Contents Noted

B08

06/13/2023

Jmmmmamsd

Contents Noted ~~ D2

Self Driving Car UO

06/13/2023

WEW—-

Returned

B08

Please have the Officer complete the new

06/13/2023

Ju— Returned

Souls‘SeeNotesfrom Div2.

06/23/2023@W=—=o.D

Contents Noted ~~ BOS

06/23/2023

S—_

Workflow End

Autonomous Vehide InadentReporton HRMS
insteadofthis UO, Thanks.
Resubmitted on correct form 6/23/2023.

Page
86 of 112

A San Francisco Fire Department(6) Autonomous Vehicle Incident

y06/15/2023

Sg

ae TERaLR PTrRPe
ee
From:
I————
To:

Deputy Chief of Operations.

Reference:

INSAptEI
eet
Incident Date
0611512023
Time
05:00

ee

Incident No

06/15/2023 04:52 - 231660297 - 1 280SB TO 101SB XR - 82C2

Location

280 NB @ Alemany

AV Company

Waymo

Numberof AVs Involved

9

Licence Plate(s)Contacted Company?

UNK
No

AV Company Response
Time
Supervisor ID
Impact (Description of Event)

As we were responding to an incident using freeway 280, we approached a driverless vehicle with ourlights on. The vehicle stopped on the freeway. We switched off our c3 lights to allow the vehicle toprocesd. A car that comes to a stop on the freeway poses 2 great hazard to oncoming traffic.
™
Worklow FromST
B10
Fowaried
Oiaz0z —Contents Noted 03
osr152023 Femme
Forwarding E25 Waymo Incident on 280.
ConentsNod CD2
OB1S025 WWW[E25 was unable to obtain CAplate on waymo
vehicle as they were traveling at freeway

oertonazs m—oonozizs wwe.

aWoriow End

Specd.

Page 88 of 112

was
ANA San Francisco Fire Department(62) Autonomous Vehicle Incident
iis

From

06/15/2023

J————————

To:

Deputy Chief of Operations

Reference:

U/O reports for driverless vehicles email

Incident Date

06/15/2023

Time

20:18

Incident No
Location

15th Street/Julian Ave

AV Company

Waymo

Number of AVs Involved

1

Licence Plate(s)did not get license plate number

Contacted Company?

No

AAV Company Response
Time
Supervisor ID

nia

Impact (Description of Event)Rescue 2 was dispatched to incident #2308011 and was responding code 3 to assist SFPD with a‘medical aid. While traveling down the narrow Julian Ave, a Waymo vehicle came to a stop. There were

three occupants in the vehicle. All occupants exited the vehicle. The vehicle blocked our route to the
medical aid. Rescue 2 backed down Julian Ave to 16th Street to use an alternate route. The Incident
with the Waymo vehicle caused approximately a 4 minute delay in response time.
To
Workflow __From3
Forwarded
152023 ummm
06/16/2023

W—_‘Acknowledged

D306162023 —Contents Noted ~~ CD2

oprton0zs weg
cons pantoen0z02s me

Acknowledged
Info Orly
Workow End

Femme
cot

“TheGFmeetsall required policy guidelines.

Fonardng onan Vefde Incident form.

Page s0of 112

A San Francisco Fire Department

Wy) Autonomous Vehicle Incident\

06/17/2023

From:

i

To:

Deputy Chief of Operations

Reference:
Incident Date

06/17/2023

Time

0134

Incident No

06/17/2023 01:32 - 231680158 - 430 TURK ST -52C1G

Location

PostHyde

AAV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)Contacted Company?

No

AV Company Response
Time
Supervisor ID

TT————

Impact (Description of Event)
1. Truck 3 was responding to a building alarm, following Engine 3.

2. When making the right-hand turn from Post onto Hyde, a Cruise vehicle had stopped in the right laneat the very beginning of the block.
3. The driver of Truck 3 makes this turn at least 5-10 times a day. Hyde Street provides 3 lanes to tum
into, but becauseofthe Cruise vehicle frozen on the comer we only had two lanes. This surprised thedriver, and slightly slowed our response.
4. As the officer, I leaned out the window to check our clearance. T was shocked to see someone in thedriver's seat of the Cruise vehicle. He waved and smiled, but he did not bother to move the vehicle
forward so we could clear the back of the car.
Workflow _ FromTo
672025 wm
Fowarded
B04
0682025 WNWWR
ContentsNoted D2
4
osi1on02s em
Contents Noted CD2
06/19/2023

Rummy

Acknowledged

08202023 gmmm—

Workflow End—

Page S20 112

$e 7
San Francisco Fire Department
8) Autonomous Vehicle Incident
Xess

i
From:
To:

——
TI
Deputy Chief of Operations

Reference:

None

Incident Date

06/19/2023

Time

20:55

0611912023

Incident No
Location

1050 17Th Street

AV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)75102P3

Contacted Company?

Yes

AV Company Response

They never did respond while we were there. More than 10 mins

SupanorD

Impact (Description of Event)
1. After a working fire, I noticeda Cruise car in front on E29 from the Cruise parking lot on 17th street.

ns.
2. E29 was blocked in and could not get out because T4 was behind us during fire operatio
e
d
mov
not
t
3. The Cruise parking lot had tech-guys on scenebutthey said, "tha they coul e it". the car fromhad to come out to movtheir location and a member from their main campus
und the Cruise car.
4. After T4 moved back a couple of feet, that gave us enough room to get aro
5. A member from the main campus never did arrive on scene while we were stuck.
To
Workflow _FromFe
B02
Forwarded
Oorioz02 wm—
poComenisNoted D3
06212023 SWWSNSContents Noted CD206222023 pm
0612212023 Umm—p

Workflow End

06222023 Lamm

Info Orly

alyWill forward to Crmtsmmaiety

Starting to forward you these info only. We cansit down andgooverexpectations
Thank you for agreeing in principle sir.

Page 94of 12

|

= 3¢
AR San Francisco Fire DepartmentWig) Autonomous Vehicle Incident

06/23/2023

Si
From
To:
Reference:

ARTS
Deputy Chief of Operations
none

Incident Date

06/22/2023

Time

12:40

Incident No
Location

Station 11

AAV Company

Waymo

Numberof AVs Involved

1

Licence Plate(s)53516F3

Contacted Company? ~~ No
AV Company Response

Time

Supervisor ID
Impact (Description of Event)

While truck 11 was backing in to the station with spotters stopping traffic, the automated vehicle
stopped and then tried to drive around the spotters. The spotters moved to block the vehicle and it tried
to go around the spotters again.
To
Workflow _ From
06/23/2023 alia

622025 WWmmmK
oo252028 me
06262023 wma
6262025 WWE

Forwarded

Acknowiedged
Contents Noted
Info Orly
Worklow End

B06

D3
CD2
mmoles

806 s awag.re ofthis stuaton and s
monitorinhiss the typeof nddentthtdoes not ely
trigger an emergency response” notation on
thir end. A question for the Truck world be.
lights on or off."

Page 97 of 112

A San Francisco Fire DepartmentWm) Autonomous Vehicle Incident

06/23/2023

Ri

From:

HE

To:

————_

Deputy ChiefofOperations

Reference:yy BaaSeTt

Incident Date

06/22/2023

Time

2215

Incident No- 100406/22/2023 22:04 - 231733400 - 130 COLLINGWOOD ST

Location

130 Collingwood

AV Company

Waymo

Number of AVs InvolvedaLicence Plate(s)Contacted Company?

Yes

AAV Company Response
Time
Supervisor ID

10
di
—————

Impact (Description of Event)
1. no physical contact, blocked one way street

2. no damage to ity property
3. Passangers dropped off 1 block away prior to incident
4. 10 minutes for driverless to clear roadway
To
Workflow _ From
E24
Fowarded
06202025 Mamata
06232025 Wms ~~ ContenisNoted BOS
Acknowledged D306232023 WMWOMC
os252023 mm
06262023 mm—D
06262023 LomWP®

Contents Noted
Info Only
Workow End

CD2
—

=
Somewhat confusing narrative; th paint of
this from i to nay the chainofcommand
thatthe roadway was blocked by the vehicle.

Page 990i 112

«@“PR San Francisco Fire Department\isg| Autonomous Vehicle Incident

06/23/2023

Sg

From:
To:
Reference:TT
Deputy Chief of Operations

Incident Date
Time
Incident No
Location

06/12/2023
2000
06/12/2023 21:22 - 231633164 - LINCOLN WY/25THAV - 2085
25th AVE and Lincoln Way

AV Company

CruiseNumberofAVs Involved
Licence Plate(s)Contacted Company?
AV Company Response
Time

1
none
No
none

Supervisor ID

Dri

Impact (Description of Event)
1. E18 was involved in a non injury traffic accident on 6/12/2023 at 2200 hours.
2. E18 was clearing the scene of a vehicle accident response at the intersection of 25th and Lincoln
Way.
3. E18 was backing down Lincoln way West bound in the East bound lanes. East bound lanes wereclosed by SFPD. While both the members of E18 were backing the driver in the appropriate positions theofficer was stopping traffic on Lincoln Way in the West bound direction. Al drivers in their personalvehicles complied and were stopping for an E18 an emergency vehicle. A Cruise self driving car failed toyield and was driving directly toward the officer. One of the backers tured their attention from backing
the engine driver to the officer and the self driving car. The officer was moving out of the way of theself drivingcarto avoid being struck. Without the direction of that backer E18 struck a non occupied
parked car, parked on Lincoln Way.
4. E18 immediately stopped moved to a safe location notified Batt 8 and SFPD and went out of service
to document the backing accident.
5. Had it not been for a self driving car not yielding to an emergency vehicle, the backer and officer's
attention would not have been changed from backing E18 to the hazardof a not yielding self driving car.
6. An accident report has been filed.
To
Workflow _From
TTT
B08
Fowwerded
06232025 wmmmmmp
ContentsNoled BOB
06232025 WmEEERD
Os232023 Sw—Contents Noted D2
Resubiitting on correct form.
Page 101of 12

$e Lpy

TR San Francisco Fire Departmentisn) Autonomous Vehicle Incident
Re

0612412023

From:

—————
ET

To:

Deputy Chief of Operations

Reference:

Rules and Regulations: Article 1128 Unusual Matters& 1112 Response to Alarms.

Incident Date

06/24/2023

Time

12:55

Incident No

06/24/2023 12:55 - 231751618 - 4TH ST/MISSION ST- 3102

Location

2 Falmouth Street

AV Company

Waymo

Numberof AVs Involved

1

Licence Plate(s)40687F3

Contacted Company?
Yes
AV Company Response ~~ N/A
Time

Supervisor ID

IEE———

Impact (Description of Event)

1. E01 was returning back to quarters on Falmouth Street when a Waymo blocked our route anddelayed our response to Incident #23084135. The street has 2 way traffic, but is narrow.

2. Waymo had 2 passengers in the vehicle. E01 members turned on the lights to stop the vehicle fromattempting to continue its route head on towards E01. Then E01 members proceeded to get out and‘make contact with the vehicle. The passengers inside Waymo pressed a button in the interior of thevehicle for assistance. E01 requested the Waymo Support Team back the vehicle up, but the Waymo

Support Team was unbale to back the vehicle remotely. E01 turned off our lights to make the situation
less complicated for the Waymo vehicle.
3. While attempting to deal with this issue, EO1 was dispatched to 4th& Mission, Incident #23084135
for a medical Unconscious Abnormal Breathing. E01 had to backup the Engine to Shipley Alley and thenproceed to 6th Street to respond.
4. The Waymo vehicle had no reaction to being on a tight street with E01, but to stop and be a barrierthat would not move. E01 was delayed responding and can see incidents like this occurring frequently
with SFFD vehicles due to the tight streets in San Francisco.

Captain ESE—

To

Workflow _ From
06/24/2023

Wm—

Forwarded

B02

06/24/2023

Cu—

Contents Noted

D3

Noted B2

Page 10301 12

AA San Francisco Fire Department
Weis) Autonomous Vehicle Incident
od
From:

ETT
——

To:

Deputy Chief of Operations«

06/28/2023

atReference:
Incident Date

06/28/2023

Time

17:10

Incident No
Haight/Steiner

Location

AV Company

Waymo

Number of AVs Involved

1

Licence Plate(s)Contacted Company?
AV Company Response

NA
No

Time
Supervisor ID

In
————

Impact (Description of Event)Bent;\mpsctiDescriponoi

patna

Doo allcde

While suppling E6 at the Working Fire a Waymo Vehicle was going to run over charged 3" hose line. The
driver of E36 stopped the Waymo Vehicle by standing in front of it. The vehicle then started to creep
forward, the driver of E36 banged on the window and tried to get the car to respond The car did not
respond to verbal commands. So the Driver of E36 put a chalk block under the tire of the Waymovehicle, so it would not drive over the hose lines. The Waymo vehicle then drove over the chalk blockand made a u-turn and left the scene.
Incident # 23086097

Workflow _ From
Cozen0zs wey

Fowardedi)
B020628/2023 “=Contents Noted

Gmmmm—uy
cp2

06002023 emi

Contents Noled

06/29/2023

WENE

Contents Noted

06/30/2023

E——

Workflow End

IEA,FAD

D3

Ta

eaE

.

Scent

Page 10701 112

NE «2A San Francisco Fire Departmentdis) Autonomous Vehicle Incident
hE
From:

07/03/2023
RA————————

To:

Deputy Chief of Operations

Reference: ~~ G.O. 23 A-34 San Francisco Fire Department FEMA CA-TF3
Incident Date

07/02/2023

Time

19:58

Incident No

07/02/2023 19:43 - 231832706 - 350 GOLDEN GATE AV - 53A2

LocationIFO Station 03, 1067 Post St.

AV Company

Waymo

Number of AVs Involved

1

Licence Plate(s)NAContacted Company?
AV Company Response

Yes
1 Day

Time
Supervisor ID

Sp

Impact (Description of Event)
After retuming from Inc.# 23088039 on 07/02/2023, T03 was preparing to back into Quarters withwaning lights on and operating properly and 2 FF's, as spotters, set up on Post St. to stop cars fromattempting to go around the Truck as it was backing up. One of the vehicles that stopped in the street‘was an unoccupied autonomous Waymo vehicle.

As T03 started to go in reverse, the Waymo vehicle lunged forward a few feet and then stopped, nearly
striking one of the FF's in the street who was in frontofthe autonomous vehicle. I, as the Officer, had

703 continue to back into Quarters asI walked up to the Waymo vehicle that was stil stopped on Post
St. I directed the other vehicles that were stopped on Post St. to continue onas I carefully approached
the vehicle on the "driver's side” and knocked on the window, saying, "Roll down the window”. The“driver's side” window rolled down and I leaned in and asked to talk to a representative. A person's
voice spoke up and at that time I opened the "driver's side” door and leaned in 50 as to hopefully
prevent the car from moving any more and I could hear the Waymo representative better. 1 had a very
brief conversation with the Waymo representative and described what had happened and stated that it‘was not ok.
After the brief conversation, I closed the door and returned to Quarters, The Waymo vehicle drove away
without further incident, This whole incident lasted about 3-4 minutes.
At approximately 13:30hrs on 07/03/2023I received a phone call on the SFFD Main Line from anotherrepresentative of Waymo asking for details on the incident. I politely informed this person that I would
not be able to talk to him about this and that the SFFD has a procedural process regarding autonomousvehicles. I asked for his contact information and let him know someone would contact him if necessary.
“The Waymo representative's name is, Scott Campbell and his phone number is, 916-862-1306.

Page 1090f 112

5 A San Francisco:xaRFire Department
Wit Autonomous Vehicle Incident

hg

i
From:
To:

TR

ne RI BA pi

Ye0711412023

TERT

aA
Deputy Chief of Operations

Reference:
Ee
Bl
le plEa
Incident Date
0711412023
z

Time

Incident No
Location

03:50

07/14/2023 03:53-231950282 - 1030 POST ST- WF
1030 Post

AV Company
Crise
Impact (Description of Event)“Truck 5 approaching fire building, west bound on Post from Larkin. Fire blowingoutthe top floor
streetside windowof a fully occupied apartment building in the early morning. Cruze vehicle stopped in
the middle of the lanes with emergency blinkers on, Cruze vehicle was blocking either of the two
possible aerial ladder placements available to truck truck 5. Truck 5 stopped and waited for 30 seconds
and the Cruise vehicle did not move. With no abilty
tothrow the aerial ladder becauseofthe Cruisevehicle, Truck 5 movedoffthe the far side of thestreetfrom the fire and began to go to work. Once
Truck 5 had moved outofthe way.of the Cruise vehicle; It continued on its way andleftthe scene. No
photos, we were going toworkat a working fire. Our inabity.to/get an aerial placement due to theautonous vehicle was reported immediately to the Incident commander.

CAs SeSeen

Page 10of 1

SC Sn%.

GR San Francisco Fire Departmentmr) Autonomous Vehicle Incident

07/14/2023

ee
S
PIE
StdG
L
hd
FOP meFrom:
To:
Deputy Chief of Operations
Reference:
Aa Br ptaLh aIncident Date
071312023
Time

23:10

Incident No

07/13/2023 22:51 - 231943820 - 40 GEARY ST - 62638

Location

IFO 1067 Post

CruiseAV Company
Impact (DescriptionofEvent)outUpon returning to Quarters from a building alarm, T03 had stopped IFO Quarters to allow spottersvehicle wasand then proceeded forward with all warning lights on and flashing. At that time a “Cruise”(drivers's
lane
hand
left
In'thewasvehicleapproaching us on Post St and hadjustcrossed Polk. This
to reverse
positionInside of the Truck) and was not slowing down. T03 slowly proceeded forward to be
into Quarters.
Atthat polnt the spotter realized the unmanned autonomous vehicle was not going to stop and got out
vehicle.
ofthe way and attempted to verbally warm the Truck Driver of the uncontrolled
to reverse into
preparing
was
it
as
T03
past
“The autonomous car narrowly missed the spotter and shot
‘Quarters and never slowed down or stopped.
“This could have been a major tragedyifthe spotter was distracted or looking another direction or if the
Truck driver hadn't heard the spotters warning and adjusted the Tractor's position.

Page 1of1

Yo
PGA \ San Francisco Fire Departmentist) Autonomous Vehicle Incident

071612023

hg
From:

Sinlsnantemmpe——To:
Deputy Ghief of Operations
Reference:
Incident DateTime

07/15/2023

+

2259

Incident No

Location
1800-2000 block of Sth Avenue
AV Company
CruiseImpact (Description of Event)
After staging forSFPD to clear a scene on 9th Avenue, a Cruise autonomous vehicle entered the scene

and found no way through. All ofthe SFFD apparatus including ambulance, RC, and Truck 18 heading
Southbound were blocked a few hundred feet awaywhen the vehice tried to problem solve and tum
around. It did not respond to Initial attempts to stop it, puling door handles, etc. and continued tomove small increments forward and back, eftand right, in anattempttogetthrough somehow. After
we moved all personnel, equipment, and patient away from the area of the vehidle(approximately 10
minutes) it found a driveway and moved itself Into a parallel parked position allowing emergency
vehicles through.
No contact between AV and city vehicles.
No property damage
No passengers at the time.

CNW IstSct

Pago tot

“1 A \ San Francisco Fire Department(5) Autonomous Vehicle Incidentod

a ——gt oe
From:

Hip

To:
Reference:

Deputy Chief of Operations
Email - 06/06/2023 fromMessen

Incident Date

Time

LN

07/26/2023

ete FE

07/26/2023

0130

Incident No

Location

18th ave/Balboa

AV Company
CruiseImpact (Description of Event)ealaDes ono Rar
1. On the morning on Wednesday July 26, 2023, E34 was dispatched to a working fire at 1625 Balboa
St (#23098958).
2. E34 was 3rd due and approached the fire scene from 18th Ave and Balboa. E34 backed down to E14
and dropped a supply then lead out to 18th Ave hydrant. FF O'Toole was the engine operator.
3," FF O'Toole stated that while he was performing his duties as a supply company, a self driving“Cruise” vehicle drove up Balboa and stopped right next to the fire engine at the intersection where he
was maneuvering large diameter hose.
4. The driverless car remained in that position for approximately 30 minutes before it drove away down
18th Ave. The driveriess car impacted FF O'Toole's operations and created more of an unsafe evolution.
FF O'Toole overcame the obstacle and completed all tasks needed to suppress the fire.

CANN CS

QeeinsPage to11

A San Francisco Fire Department(ge) Autonomous Vehicle Incident
xii

07/27/2023

From:

Pid

To:

Deputy Chief of Operations

Reference:

None

Incident Date

07/26/2023

Time

22:35
07/26/2023 22:26 - 232073356 - 2ND ST/HOWARD ST - 23D1G

Incident No
Location
AV Company

2nd/Minna
CruiseImpact (Description of Event)
1. No physical contact between AV and any city property

2. No city property damage
3. 2 passengers in AV

4. No passenger pick up or drop off was occurring during incident but passengers exited car shortly after
AV blocked roadway
5. AV turned off 2nd St onto Minna where E35 and RC1 were providing pt. care. AV backed up andstopped at comer of intersect in the middle of the roadway blocking Minna St from 2nd St for approx. 5
minutes. This blockage of the roadway caused M86 to have to park on 2nd St. AV moved to the side ofstreet approx. 2 minutes after M86 parked on 2nd St.

Page Tar1

1s

San Francisco Fire Department(5) Autonomous Vehicle Incident

07/28/2023

nL
From:

Air

SAR

To:

Deputy Chiefof Operations

Reference:

Email dated 5/11/23 from CD2

Incident Date
Time

07/27/2023
20:42

Incident No

07/27/2023 20:42 - 232083167 - 1242 19THAV - WF

Location

1242 19th ave

AV Company

CruiseImpact (Description of Event)

1. At 20:41 E40 was dispatched to a working fire at 1242 19th ave . E40 was second due . We weretraveling west bound on Irving and turned the rig around at 19th and Irving to facilitate a supply line. A
cruise vehicle was behind the rig in our path of travel. Because 19th ave has 3 lanes we were able toback up around the stopped vehicle.
2. There were spotters present while the engine was reversing.
3.We were not able to disarm the vehicle due to the working fire.
4, The driver informed me that a Cruise rep was on scene to deal with the vehicle in about an hour.
5. Due to the position of the vehicle our response time was slightly delayed.

Page tof1

RA San Francisco Fire Department(ies) Autonomous Vehicle Incident

07/28/2023

=
From:

iB

To:

Deputy Chief of Operations

Reference:

Incident Date

07/28/2023

Time

09:25

Incident No
Location

IFO Fire Station 5, Webster side

AV Company

CruiseNumber of AVs Involved;

Licence Plate(s)2567283

Contacted Company?

Yes

AV Company Response

7 Minutes from phone call(

Time
Supervisor ID|

Impact (Description of Event)[|

Truck 5 was parked IFO the fire station on the Webster Street side, partially strattling the North boundleft turn lane and painted median (where we always park.) Traffic cones had been placed alongside theapparatus so as to notify traffic that the vehicle was parked and to allow the crew to work around the‘appartaus to conduct our morning checks.At approximately 09:25, a Cruze vehicle as above approached
the front of the apparatus in a manner that showed it was not able to identify the nature of the activities
being conducted around Truck 5. One of the crew members who was nearby approached the vehcile,which did not move or make any attempt to correct the behavior. In the name of safety of the Truck 5
crew working around the Truck, a traffic cone was placed on the hood of the Cruise vehicle and theemergency phone number of Cruise was called.
The phone call took 5 minutes and Cruise repsonded with a person to move the vehicle in about 7.
While the Cruise representative, Clinton, suggested we remove the cone so that a person could move the
car remotely, for the safety of the Truck 5 crew, I opted to leave the cone on the hood of the Cuise
vehicle until a live person was present to move the vehicle.
Problem resolved at approximately 09:42

To

Workflow _ From|

07/28/2023 gles

ForwardedBOS

ome eesAcknowledged

D2

07/28/2023

(

imide

Contents noted

Contents Noted ~~ CD2

Page 10f4

A San Francisco Fire Department(Gas) Autonomous Vehicle Incident
cg

07/26/2023

eeaulh heia LIN
From:

I.

To:

Deputy Chief of Operations

Email - 06/06/2023 from AC Rabbitt
I
rehe
a

Reference:

Incident Date

07/26/2023

Time

0130

Incident No
Location

18th ave/Balboa

AAV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)unable to obtain
Contacted Company?
No
AV Company Response ~~ N/A
Time

Supervisor ID

I———

Impact (Description of Event)

1. On the morning on Wednesday July 26, 2023, E34 was dispatched to a working fire at 1625 Balboa
St (#23098958).
2. E34 was 3rd due and approached the fire scene from 18th Ave and Balboa. E34 backed down to E14

and dropped a supply then lead out to 18th Ave hydrant. FF O'Toole was the engine operator.
3. FF OToole stated that while he was performing his duties as a supply company, a self driving"Cruise" vehicle drove up Balboa and stopped right nextto the fire engine at the intersection where he

was maneuvering large diameter hose.

4. The driverless car remained in that position for approximately 30 minutes before it drove away down
18th Ave. The driverless car impacted FF O'Toole's operations and created more of an unsafe evolution.

FF O'Toole overcame the obstacle and completed all tasks needed to suppress the fire.

To

Workiow _From

Forwardedtie.

07/26/2023 —Contents Noted

YRS.

omsiaczs wm

Contents Noted C02

07272023 Laman

Workflow End

0726/2023

diy

Form filled out....in the INCIDENT NO.....box
tried
multipleintines
to putthe incident
infomation
troughtesearch
ox and was
not able to input information once "appliedchanges” was ape tothe electronic form.

Page act 18

gSa) San Francisco Fire Department(2%) Autonomous Vehicle Incident
SE

0712712023

From:

HR
————— 11To:

Deputy Chief of Operations

Reference:

None

Incident Date

07/26/2023

Time

22:35

Incident No

07/26/2023 22:26 - 232073356 - 2ND STHOWARD ST - 23D1G

Location

2ndMinna

AAV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)Contacted Company?

75108P3
No

AV Company Response
Time
Supervisor IDo
EE"

Impact (Description of Event)

1. No physical contact between AV and any city property

2. No city property damage
4. No passenger pick up or drop off was occurring during incident but passengers exited car shortly after
AV blocked roadway
5. AV tuned off 2nd St onto Minna where E35 and RCI were providing pt. care. AV backed up andStopped at comer of intersect in the middle of the roadway blocking Minna St from 2nd St for approx. 5
minutes. This blockage of the roadway caused M86 to have to park on 2nd St. AV moved to the side ofstreet approx. 2 minutes after M86 parked on 2nd St.
To
Workllow _From
TET preCortenisNoted 803
07272025 Wmmm—
or22025 m—
Conteris Noted D3
havereviewed
thsVehie Incident
ContentsNoted CD2072772023 @mm—N
Worklow End
726202) Lem
3. 2 passengers in AV

Page 100118

io

San Francisco Fire Department(83%) Autonomous Vehicle Incident

08/01/2023

RL

From:
To:

LL
Deputy Chief of Operations

Reference:
Incident Date

08/01/2023

Time

14:48

Incident No

08/01/2023 14:47 - 232131789 - 170 OFARRELL ST - 9E2

Location

Polk Street between Geary and O'Farrell

AV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)Contacted Company?

No

AV Company Response
Time
Supervisor ID

TTT——

Impact (Description of Event)
1. While enroute to 170 O'Farrell for a medical call an unmanned Cruise vehicle stopped in the centerof Polk Street going southbound. There were no vehicles to the right of the Cruise vehicle. There wasplenty of room to move out of the way, but it just stopped.
2.This forced Truck 3 to either pass on the right side or against oncoming traffic on the left side.
3. 1.did not obtain any other information because we were enroute to a Code 3 Medical callTo
Workflow_ From
TsTr
B04
Forwarded
001202) pam
Contents noted
Acknowledged D2
08022023 gue
Contents Noted CD2
on02z023 w—Woriiow End
08022023 Wm——

Page 10/9

ANA) San Francisco Fire Department==) Autonomous Vehicle Incident

08/03/2023

Nis
From:

———————

To:

Deputy Chief of Operations

Reference:
Incident Date

08/03/2023

Time

2122

Incident No

08/03/2023 21:19 - 232153399 - 233 PARKER AV - BOX

Location

Parker and Anza intersection

AV Company

CruiseNumber of AVs Involved

1

Licence Plate(s)35984R3

Contacted Company?

No

AAV Company Response

Time

Supervisor ID’.

Impact (Description of Event)
While E21 was backing down to the 1st in engine a Cruise vehicle was stopped in the crosswalk and wasin our way resulting in a delay. There was no damage to any property. There weren't any passengers.

The Cruise Vehicle never cleared the crosswalk for us.

Wo

EO

08/03/2023

AN—_—

tr
Forwarded

081042023 Wmmmggy~~ Acknowledged
08/04/2023 W-—>5

oBOAZ23 laMEMD

eta

LC

BOS.

D2

Contents Noted

Contents Noted ~~ CD2

ViorowEnd

Page 3019

, SR San Francisco Fire Department

or

G5 Autonomous Vehicle Incident
Si

A

a

08/05/2023

lpr a TE

RL

From:

Deputy Chief of Operations.

To:
Referen

ce:
entin
a
a
N
r
Incident Date

08/05/2023

Time

1106

Incident No

08/05/2023 11:08 - 232171029 - 100 34THAV - 7181

Location

Legion of Honor

AV Company

Waymo

NumberofAVs Involved

1

Licence Plate(s)UNKContacted Company?

Yes

AV Company Response

25 mins

Time

A———

Supervisor ID

Impact (Description of Event)
1. E14/T14 responded toa car fire at Legion of Honor. Firefighting efforts were conducted using force
entry tools and stretching a 150" ready line.
2. During fire operations, a Waymocarturned southbound on 34th Ave entering the fire operations

Scene and stopped moving. This action impacted our suppression efforts negatively due to members
having to walk around the Waymo with a charged hose line and fight active fire. The car was positioned
between the car on fire and the fire engine.
3, Law enforcement was requested to assist with traffic control.
4. T14 members entered the Waymo and placed it in manual mode and moved it to a safe location.
5. Waymo staff arrived and reprogrammed the Waymo and both cars left the scene.

Workflow _ From
On052023 emp.
osi0sr0zs Se—=o0s0zs Vm
08/06/2023

LAWNS

Forwarded
Contents Noted
Contents Noted

To
807
D2
CD2

Contents noted==7

Workflow End

Pages ols

AR San Francisco Fire Department
sy Autonomous Vehicle Incident

Sk
08/06/2023

2s

ee
ee
————
EE
From:
To:

Deputy Chief of Operations

Reference:

Rules and Regulations, section 1128

Incident Date

08/06/2023

Time

03:59

Incident No

Location

Cesar Chavez/Kansas

AV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)452572

Contacted Company?

No

AAV Company Response
Time

none

Supervisor ID

Sa

Impact (Description of Event)
E09 responded to Incident #23104117 at approximately 0359 hours, an MVA involving an SFPD

officer.

E09 blocked 1 east bound lane of Cesar Chavez traffic with the apparatus to protect the scene and‘members rendering purer Cav~SPFD created a traffic block on the west bound lanes of Cesar Chavez and North bound lanes of Kansas“While rendering aide to both the SFPD officer and driver of the second car, an AV vehicle attempted todrive through the scene.

~The AVE Vehicle was identified by the SFPD conducting traffic control on Cesar Chavez as Cruise license
plate# 452572, side badging "Tap Dance"“The SFPD officer attempted to make contact with the AV company and after an attempt the resolution
was for the SPFD officer turn off all warning lights to move the squad car that was protecting theincident scene so the AV could reset and adjust for a turn on to Kansas. It is unknown if the SFPD officer
was in contact with the AV company at the time of resolution.

This incident created multiple unsafe conditions 1. AV attempting to enter scene, 2. To resolve issue
the Squad car protecting scene and diverting traffic was moved for the AV to rest and 3. Units on scene
had to tun off warning lights so the AV could reset.
To
Workflow _ From
Forwarded

B10

W—

Contents Noted

03—

Contents Noted

C02

08/06/2023

E—_—_

08/06/2023

ou0s2023

Forwarding AV Inddent report rom @hmaess®
Page 80f9

51

77 San Francisco Fire Department(ak) Autonomous Vehicle Incident
SF

ee
—————
AT
From:
To
Deputy Chief of Operations
Reference: Rules and Regulations, section 1128
treme
Incident Date
08/06/2023
Time
03:59

a

08/06/2023
ii

OTA

Incident No

Foetion)

Cesar Chavez/Kansas

AV Company
CruiseImpact Dearne)(Description of Event)Mae-E09 responded to Incident #23104117 at approximately 0359 hours, an MVA involving an SFPD
officer.
“£09 blocked 1 east bound laneofCesar Chavez traffic with the apparatus to protect the scene andmembers rendering cure.
lanes of Kansas~SPFD created a traffic block on the west bound lanes of Cesar Chavez and NorthAVboundattempted tovehiclean“While rendering aide to both the SFPD officer and driver of the second car,drive through the scene.
“The AVE Vehicle was identified by the SFPD conducting traffic control on Cesar Chavez as Cruise license:
plates 452572, side badging "Tap Dance"
an attempt the resolution“The SFPD officer attempted to make contact with the AV company and after
was protecting the
that
car
squad
the
move
was for the SPFD officer turn off all warning lights toincident scene so the AV could reset and adjust fora turn on to Kansas. It is unknown if the SFPD officer
was in contact with the AV company at the time of resolution.
2. To resolve issue“This incident created multiple unsafe conditions 1. AV attempting to enter scene,
the Squad car protecting scene and diverting traffic was moved for the AV to rest and 3. Units on scene
had to tum off warning lights so the AV could reset.

Page tof1

AR San Francisco Fire Department(ge) Autonomous Vehicle Incident
hs

a

a

From:

s8
08/07/2023

arecent

AATT————

Deputy Chief of Operations
To:
Reference: Department email from CD2, Postela lLeae
eT
08/06/2023
Incident Date
1:29
Time
Incident No

Location
AV Company

604 Waller St
CruiseImpact (Description of Event)604 Waller St, incident # 23104231. BS and EG arrived
E6, T6, and BS responded to a building alarm atarrived
scene autonomous cruise vehicle pulled behindon scene and positioned apparatus. Before T6 lights.onDuring
the course of the building alarm, theE6 and stopped because of the flashing warning
forward in the same area. T6 was unable to positionn
vehicle kept reversing backward and then moving
its apparatus in the appropriate position. The vehicle finally made its way around E6 before informatio
could be gathered about the vehicle.

Page fof1

RR San Francisco Fire Department

S q

(ey)
NH Autonomous Vehicle Incident

08/10/2023

a
From:

LITTR

To:

Deputy Chief of Operations

Reference:

No Reference

Incident Date

08/10/2023

Time

12:49 pm

Incident No
Location

Lincoln way between 4th and 3rd Avenues

AV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)Contacted Company?

15849T3
No

AV Company Response
Time

Supervisor ID

hl =LyImpact (Description of Event)Beed

pactDeWhile proceeding eastbound on Lincoln Way T12 encountered a Cruise vehicle completely stopped in the

middle lane of three lanes. T12 was not displaying any Code 3 lights at the time. T12 stopped‘approximately 15 feet behind the vehicle but in the right lane not knowing what the vehicle would donext. The Cruise vehicle stayed in the middle lane stopped. T12 then slowly proceeded eastbound in
the right lane and as we started passing the vehicle on the right side it started moving forward andgetting closer to T12. At this point the driver of T12 stopped, thinking that the Cruise vehicle would
collide with the truck. The vehicle then slowly proceeded forward then cut directly in front of T12 anddrove off.

Workflow_From

08/10/2023

Skmminially

08112023 memeTo

Forwarded

BOS

Acowledged

D2

08/11/2023

W——

Contents Noted ~~ CD2

08/11/2023

Mu——D

Workflow End

Contents noted

Page 1012

Lo

3

A San Francisco Fire Department(i) Autonomous Vehicle Incident
is05

io1 CORMAN

ov lh.

From:

—
AS——

To:

Deputy Chief of Operations

Reference:

Department email from CD2, Postel

ae

AOR

08/07/2023

chitin08/06/2023

Incident Date
Time

11:29

Incident No
Location

604 Waller St

CruiseAV Company

Numberof AVs Involved ~~ 1
Licence Plate(s)Contacted Company?
AAV Company Response
Time

Supervisor ID

Rldittoes

aoOB

Impact (Description of Event)E6, T6, and BS responded to a building alarm at 604 Waller St, incident # 23104231. BS and E6arrived
on scene and positioned apparatus. Before T6 arrived on scene autonomous cruise vehicle pulled behind
E6 and stopped because of the flashing waming lights. During the course of the building alarm, thevehicle kept reversing backward and then moving forward in the same area. T6 was unable to position
its apparatus in the appropriate position. The vehicle finally made its way around EG before information
could be gathered about the vehicle.

To

Workflow _ From

02

08/07/2023

EEN

Forwarded

08/07/2023(ENED

Contents Noted ~~ CD2.

08/08/2023

W——

Workflow End

toedit# added in narrative; unable

Incident“Incident
No" data field afte submitting.

Page tof 13

RR San Francisco Fire Department(aXe) Autonomous Vehicle Incident

08/10/2023

NEF
From

a]

To:

Deputy Chief of Operations

Reference:

No Reference

Incident Date

08/10/2023

Time

12:49 pmelIncident No
Location

Lincoln way between 4th and 3rd Avenues

AV Company

CruiseNumber of AVs Involved

1

Licence Plate(s)1584973

Contacted Company?

No

AV Company Response
Time
Supervisor ID
Impact (Description of Event)

While proceeding eastbound on Lincoln Way T12 encountered a Cruise vehicle completely stopped in the
middle lane of three lanes. T12 was not displaying any Code 3 lights at the time. T12 stopped
approximately 15 feet behind the vehicle but in the right lane not knowing what the vehicle would donext. The Cruise vehicle stayed in the middle lane stopped. T12 then slowly proceeded eastbound in
the right lane and as we started passing the vehicle on the right side it started moving forward andgetting closer to T12. At this point the driverof T12 stopped, thinking that the Cruise vehicle would
collide with the truck. The vehicle then slowly proceeded forward then cut directly in front of T12 anddrove off.

rimiiiniosidnseiie
smmmmbiWOOLFO
08/10/2023

Ciminielt

Forwarded

BOS

08/11/2023

WR—=_=

Acknowledged

D2

08/11/2023—_S

Contents Noted ~~ CD208112023 \ytlmmmm

Contents noted

Workflow End

Page af13

ii
VaA \ San Francisco Fire Department1%(sd) Autonomous Vehicle Incident

08/11/2023

i

et

iem
Ein
Sd
From:
To:

2

Deputy Chief of Operations

Reference: No Reference
siemem emalt eraIncident Date

08/11/2023

Time

10:37 am

Incident No

08/11/2023 10:35 - 232231126 - 515 PARNASSUS AV - 52C30

Location

Parnassus and Willard

AV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)unknown

Contacted Company?

No

AAV Company Response

Time

Supervisor ID

Impact (Description of Event)
ie
ties
Des
i
While responding to an incident at 515 Parnassus Avenue T12 was proceeding westbound on Parnassus
middle of theat Willard when we encountered a Cruise vehicle stopped directly in front ofup usin inthetheopposite
direction of
set
cones
with
Street. Due to the fact that there was a construction zone
to see If
lights3
e Codetravel we were unable to safely go around the vehicle. The driver tumedoffth
therefore was forced to drive over
the Cruise vehicle would proceed out of the way but it did not. T12
the construction cones, causing an undue hazard, to get around the Cruise vehicle and proceed to theincident.

To

Workflow _ From
08/11/2023—

0811202 WM
08/12/2023

W—.

08122023 mmm.

Forwarded

BOS

Ackowledged

D2

Contents Noted

Contents Noted ~~ CD2

Worklow End

Pages of 13

“>PR San Francisco Fire Department(52) Autonomous Vehicle IncidentSiee

08/11/2023
HE

hd mA ps hel

td

a

From:

To:
Reference:

NTETT————

Deputy Chief of Operations
6/5 Emailfromduuiisiiey

Incident Date
Time
Incident No
Location

08/11/2023
16:52- 52C4U
08/11/2023 16:53 - 232232615 - 3407 24TH ST
24th Street near Poplar

AV Company

CruiseNumberof AVs Involved

1

Licence Plate(s)75138P3

Contacted Company?

Yes

AAV Company Response

Time

Supervisor ID

T——"

Impact (Description of Event)
ere
Be
es
Ip
3407-24th Street, a comer building,
1. E11, T11 and B6 responded to Incident #23106824, located atbuildi
ng on 24th Street, T11 positioned
2. E11 positioned their apparatus just past the front door of thethe street in the gas station lot.
their aerial on Valencia St and B parked the buggy acrossa 45 degree angle In front of E11
3. Unoccupled Cruise vehicle license plate #751383 stopped atStreet.
24th
blocking the single opposite lane, preventing access downroll
4. Tttook a couple minutes for the driver side window to down.
5. After communicating with someone from Cruise, they were abl to successfully back the vehicle outof the incident area.
6. Time it took for AV clearance of 24th Street: 5 minutes.
7. Photos from incident attached.
To
Workflow _ FromTT
0
Forwarded
Oertiozs Mean
Hoo
Info Orlyoutiz0s WE
ae,
808
Oifi02) mmmmm—- Retumeds
Please complete. a UO any ford al AV indenteast
moving forward CD2 change thispractic
Week and 1s refering otheseasthe "AV UO."
Thank you.

Pagel 13

RA San Francisco Fire Department(ity) Autonomous Vehicle Incident

08/13/2023

Nis
From:

To:

4

NUTTTTTII—

Deputy Chief of Operations

Reference:
Incident Date

08/13/2023

Time

0045

Incident No

08/13/2023 00:35 - 232250084 - 98 WEST PORTAL AV - BOX

LocationIntersection in frontof 98 West Portal Av

AV Company

CruiseNumber of AVs Involved

1

Licence Plate(s)Contacted Company?

NA
No

AAV Company Response
Time
Supervisor ID

NA

Impact (Description of Event)
As companies were putting away equipment at 98 West Portal Av, an unoccupied Cruise vehicle began

to approach our scene from Vicente St and accelerated straight towards Engine 40 and not stopping until
it was approximately 5 feet from the pump panelofthe engine. This occurred as members of engine
40 were standing next to the engine putting equipment away. The vehicle paused at that position for
approximately 30 seconds before it started slowly backing up to where it initially started from.
To
Workflow _ FromaTT
EZ)
Forwarded
00132025 wm
Acknowledged B09
08132023 mld

Page 130f 13

A San Francisco Fire Department(is) Unusual Occurrence
SY
ee
From:

nial oSBaai

Ls
08/14/2023—

Chief of Department
To
Reference: Rules and Regulations, Section 1128
itt
ii Cetii _————1. On August 14, 2023 at 1836 hours, T03 responded to Incident # 23108330, a residential building
alarm box.
2. While on the scene, a GM Cruise, driverless car pulled within 10 feet of the rear of the apparatus.
3. The location of the driverless car prohibited the crewof T03 form being able to remove the ladders;
from the rear of the apparatus.
4. Had this been a working fire, the safety of the public and the members of the San Francisco Fire
Department would have been greatly impacted.
To
Workflow _ From
0514023 Smal

08152023 CERF
OBi152023 WEEMS
08/16/2023

WE.

Forwarded

804

ContenisNoted
Contents Noted

D2
CD2

Contents noted
can not send this down the Autonomous car
path through HRMSto my knowledge. I have.
reminded the members tha the other drop
down exists.

Workflow End

Page 1of1

A San Francisco Fire Department
Wiis2) Autonomous Vehicle Incident
as
From:
REIT,
To:
Deputy Chi
ofOperation
efs
Reference: June 5, 2023, Email Received from AC Patrick J. Rabbitt

Incident Date
Time
Incident No

le08/15/2023

08/15/2023
13:13
- BOX
08/15/2023 13:10 - 232271540 - 3770 24TH ST

Location
AV Company
NumberofAVS Involved
Licence Plates)

3770 24th St.
Cruise11585073

Contacted Company?

No

AV Company Response

N/A

Time

Supervisor ID

Impact(Description of Event)TOTSCI
EEE
ge oe oe HP MP RAI
iatiid
1. On Tuesday, August 15, 2023, E11, E07, E06, T11, T07, BOS, D3, RS2, M83 responded to Box5523, 3770 24th St., at 13:09 hours.
2. E11 placed their apparatus just beyond the property line of 34470 24th St. T11 placed theirapparatus in front of the reported address.
3. An unoccupied Cruise vehicle with license plate #15850TS3 stopped approximately 6 feet behind T11
thelr ground ladders.
Which did not allow the crew members to deploy second
floor.
4. Incident involved an overheated dryer on thehave coordinated with T07 and5. If this incident was a working fire, the members of T11 would
deployed their ground ladders based on the conditions of thetheincident.
6 minutes.
6. Time it took for the Autonomous Cruise Vehicle to clearor Cityincident:
property.
7. No physical contact between the AV and Department
8. Photos from incident attached.
To
Workflow _ From
08/15/2023

H—tY

08/15/2023 WWE

Forwarded

03

Contents Noted ~~ CD2

Divison 3 arrived on scene on immedietly

noticed that the driverless Cruise vehicle
obstructed the ability ofthe T11 Firefighters toHave any accestotheir ladder bed. 806was

instructed to write this incident up and
immediatley report it to CD2.

Page 10f2

A San Francisco Fire Department

7disp) Autonomous Vehicle Incident

08/15/2023

a

From
ES
To:
Deputy Chief of Operations
Reference:
Incident Date
0811412023
Time
2250
08/14/2023 22:45 - 232263401 - TTH STHARRISON ST - 2002M
Incident No
Location

Tth street/Harrison

AV Company

Crise

Number of AVs Involved

2

Licence Plate(s)Contacted Company?

AV Company Response

Time
Supervisor ID
Impact (Description of Event)
1. On 08/14/2023 while assigned to Medic8?, I responded to Incident FD23108420, for an auto vspedestrian.2. Upon arrival on scene, SFPD and SFFD E01 were providing patient care to a criticallyinjured patient in the street. The pt was GCS 3 with significant left lower extremity injuries requiring
application of a tourniquet to control bleeding.. When we arrived at scene, the only open lanes fororegress from the call were blocked by (2) Cruise vehicles that had stopped and were not moving
unablewere
webut
injuries,
threatening
life
with
transport
forleaving the scene.4. The pt was packaged
to leave the scene initially due to the Cruise vehicles not moving. This delay, no matter how minimal,
is of the essence to transport
contributed to a poor pt outcome. In anysignificanttraumatic event, time
the pt to definitive care in order to give them the best possible chance at survival. This pt was
unfortunately pronounced deceased in the ED approximately 20-30 minutes after armival.5. The fact that
Cruise autonomous vehicles continue to block ingress and egress to critcal 911 call is unacceptable.
To
Workflow _ From
RENE
Roe
Forwarded
O12 mmm
Acknowledged EMS2
opts w—O
08/15/2023

CE——

Contents Noted ~~ EMS1

08/16/2023

WESENSWM

Contents Noted

TSN

Acknowledged

CD2

08/16/2023

milInfo Onlycot

ont62023 mb

EMS1 working on getting additional information
re: amount of time cars were stopped and how

long our unit was delayed.

Page 10f2

De Ad emai=

NA San Francisco Fire Department(az) Autonomous Vehicle Incident

2 01
08/17/2023

Ni

From:
To:

fr

TIT
————
Section Chief- EMS Operations

Reference:
Incident Date

08/14/2023

Time

2250

Incident No
Location

Tth/Harrison

AAV Company

CruiseNumberof AVs Involved ~~ 2
Licence Plate(s)Contacted Company?
AV Company Response
Time

Supervisor ID
Impact (Description of Event)

1. On 8/14/2023 Iwas assigned to Medic 87 and responded to Incident FD23108420, at 7th street andHarrison, for an auto vs pedestrian. Harrison street is 4 lanes of one way traffic heading westbound.

Upon arrival on scene, the victim was found in the (2) left lanes of Harrison street, suffering from life

threatening injuries. SFPD and E01 had arrived prior to M87's arrival. SFPD had a vehicle parked in the#1 lane of Harrison, and E01had positioned its apparatus across the left 2 lanes of Harrison to shield thepatient from oncoming traffic. The right 2 lanes of Harrison were blocked by (2) autonomous Cruisevehicles that had stopped and were not moving, blocking ingress and egress to the incident scene.
2. The patient was suffering from life threatening injuries, with a GCS 3, agonal respirations, and absent.
peripheral pulses. SFPD had applied a tourniquet to the lef lower extremity to stop lie threatening
bleeding from injuries sustained after being struck by a vehicle. Ventiations were assisted with a BVM,
to a trauma center.
and the pt was packaged for rapid transport
3. While loading the patient to the ambulance, the (2) Cruise vehicles were stil stopped in the right 2
lanes of Harrison, prohibiting rapid egress from the scene. SFPD had attempted manual takeoveroftheautonomous vehicles, but were unsuccessful. This contributed to a delay in transport with a criticaltrauma patient.
4. SFFD members had to locate an SFPD officer and request him to move his vehicle to allow successfulegress from the scene, but doing so further delayed patient care. These delays caused by (2)autonomous vehicles blocking a norma egress route from the scene, contributed to a poor patient
outcome, delaying the definitive care required in severe trauma cases. The patient was pronounced
deceased at SFGH approximately 20-30 minutes after arrival due to severe blunt force trauma.
To
Workflow_ From
Page 16.0119

A San Francisco Fire Department&CE Autonomous Vehicle Incident

8
08/16/2023

ap

From:
=.
To:
Deputy Chief of Operations
Reference: E-mail from CD2 on June 5, 2023
Incident Date
08/16/2023
Time

13:50

Incident No

08/16/2023 13:44 - 232281798- 3327 26TH ST- BOX

Location

ICP on 26th Street

AV Company

CruiseNumberofAVs Involved

2

Licence Plate(s)2532753

Contacted Company?
No
AV Company Response
Time
Supervisor ID———
Impact (Description of Event)
While determining the extent of an exterior fire under wooden stairs at 3327 26th Street, I noticed avehicle proceed in the Eastbound direction through the intersection of of Capp Street and 26th Street.
At this time, fire apparatus were operating on the fireground in that specific intersection (Engine 11 wason the South side of the intersection and Engine 09 was on the North side of the intersection ofCapp and 26th Streets). At this incident, Engine 09 was the primary supply engine for Engine 40. A 3"
Supply line was dropped by Engine 09 and led to the LPH on the NW corner of Capp and 26th Street.
Companies were in the process of loading the 3 hose back on Engine 09 when this occured. Engine 40
was in the Eastbound lane of 26th Street with is 200" 1 3\4" ready line deployed and charged. Truck 11
was in the Westbound lane of 26th Street facing East. Truck 07 was in the Westbound lane of 26th
Street facing West.
T approached the lead AV in hopes for it to stall. The AV’ flashers initiated, then the AV began to
The AV vehicle thenattempt a 3-point tum back to the intersectionofCapp Street and 26th ofStet.
Stalled perpendicular to 26th Street. The AV remained for the duration the incident.
Twas unable to determine what actions the second AV vehicle took, but ti visible in the attachedphotos in the Eastbound lane with flashers on and stalled at the intersection of Capp Street and 26th
Sireet, 1 id not get the license plate number for the second AV but noted it was a Cruise model.
T noted no passengers or rivers in either vehicle.
To
Workflow _ Fromoz
Fovarded
Oerioz0zs mmm.
Page 10f5

7

NA San Francisco Fire Department(Ri) Autonomous Vehicle Incident

08/15/2023

iis
From:

TO)

To:

Deputy Chief of Operations

Reference: U0. 1128
Incident Date

08/15/2023

Incident No

08/15/2023 01:18 - 232270104 - 892 GREEN ST - BOX

Numberof AVs Involved

1

on:16

Time

Green/Taylor
Waymo

Location
AV Company

Licence Plate(s)NoContacted Company?
AV Company Response
Time
Supervisor ID
Impact (Description of Event)
1. Responding to FIB 1 Waymo car pinned in between T02 and T13 on the comer of Green and Taylor.
2. Waymo car blocked access for responding units to get around.
3. BOI on scene and saw the obstacle for responding units.
4 BOL took photosofthe car with no clear picture of reading license plate number.
Bom
Wor
801
Fonaried
C1502 wme—
Contents Noted

RetumedD2

oBri6z025 wmk

Contents Noted

08/17/2023 palaContents Noted

D2

2 pictures added per request.

08/15/2023

oBr182023@—"»

Contents Noted

B01

C2

Pleas attach any photosofAutonomous
Vehicle.

Page 10f2

©

i

=

NA San Francisco Fire Department¥

Ut) Autonomous Vehicle Incident

08/16/2023

Sg
s
e
Ca
From:

isietaiottsieniiiinsiy)|
FIT

To:

Deputy Chief of Operations

Reference:

Email from CD2 dated June 5, 2023

Incident Date

08/16/2023

Time

18:10

Incident No

08/16/2023 18:06 - 232282795 - 775 80 EB BAY BR Z SF, YB - 2006

Location

2nd/Bryant

AV Company

Waymo

Numberof AVs Involved ~~ 1
Licence Plate(s)53596F3

Contacted Company?
AV Company Response

No

Time
Supervisor ID

iis

Impact (Description of Event)At approximately 18:10 while heading to an MVA on the bay Bridge, RS1 encountered heavy traffic at‘the intersection of 2nd/Bryant. We were in the number 2 lane approaching 2nd street when an

autonomous "waymo" vehicle stopped in front of us. The vehicle then froze leaving us with only room topass on the right. As We attempted to pass the stalled vehicle at their right rear area, a civilian SUV‘approached from our right blind spot area and stopped just shy to the rear of the front tire. I told my

driver to stop but it was too late. The civilian car and us struck each other causing damage to the fenderand bumper of the civilian car and ZERO to the squad.
A MTA officer was on scene and saw the incident unfold. We cleared the intersection and pulled over tothe right. I exited RS1 and directed the civilian car to do the same. At this time the "Waymo" vehicle
turned up 2nd street heading to Harrison. There were NO passengers in the waymo vehicle.
An accident report has been filled out. BO3 and D03 were O.H.

To

Worklow_ From802

08/16/2023

WHGS——_

Forwarded

08/17/2023

WE——M

OBiTZz ew

Contents Noted ~~ D3

ComenisNoed

08/17/2023

W—_—_—_

Workflow End

CD2

please ensurenm?receives

Forvaring AV UO from RS1.

Page 120119

“7PA San Francisco Fire Department\&izz%)) Autonomous Vehicle Incidentiiyi AERTRINWL
TA,
From:
Deputy Chief of Operations
To:
Reference:

Incident Date
Time
Incident No

08/17/2023
1242

Location

Fulton/26th Ave

AV Company

CruiseLicence Plate(s)83016R3, Unknown 2nd Plate

SnelA

08/17/2023
Petr

Number ofAVs Involved ~~ 2
Contacted Company?

AV Company Response
Time.
Supervisor ID

Impact (Description of Event)
1.0n 8/17/23 at 1212 Hours E14 responded to an MVA (Incident # 23109651) involving a Scooter and
2 BMW SUV at the Intersection of Fulton and 26th Ave. PD was on scene upon arrival and E14 secured
and blocked the scene in the intersection with the apparatus to maintain scene control and crew safety.
‘Approximately 50 feet back from the Intersection a Cruise Automous Vehicle with license plate 83016R3
Stopped in the inside lane and ceased any movement. A second Cruise Autonomous Vehicle with an
unknown license plate shut down in the outside lane approximately 50 feet behind the 1st Cruise
Autonomous Vehicle. This caused much confusion for people operating vehicles in surrounding cars
trying to avoid the accident and scene itself and caused Fire Personnel to assist with controlling traffic.
2. There was no physcial contact between AV and City Property and therefor no damage.
3. There didn't appear to be any drivers or passengers in either Cruise AV.
4. There didn't appear to be a drop off or pick up in progress.
5. The cruise vehicles didn't clear the scene for the duration of our incident.
6. Photo attached.
To
Workflow_ From
B07

08/17/2023@—/

Forwarded

08/18/2023(=~

Contents Noted ~~ D2

08/18/2023

Sm—_—_—»

Contents Noted

08/22/2023

LUWw—

Workflow End

co2

More incidentsof autonomous vehicles unableto"solve" the situation andsocausing issues for
traffic and response.

Page 10f2

PA San Francisco Fire Department\Si2y) Autonomous Vehicle Incident
ie
From:

Aer
08/20/2023

ETTORETo:
Deputy Chief of Operations
Reference: No Reference
Incident Date
0812012023
Time
19:12
Incident No
08/20/2023 19:08 - 232322689 - 1290 12TH AV - 52C3G
Location
11th Avenue and Judah Street
AV Company
Waymo
NumberofAVs Involved 1
Licence Plate(s)unknown
Contacted Company?
No
AV Company Response
Time
Supervisor ID
Impact (Description of Event)
Truck 12 was heading Westbound on Judah Street responding with lights and sirens to a building
alarm. As we approached 11th Avenue a driverless Waymo vehicle with passengers heading
Southbound on 11th Avenue stopped at the stop sign then started to proceed across the intersection
directly in front of T12. The vehicle stopped and started 3 times until t finally came to a stop in the
middle of the intersection causing the driver of T12 to swerve abruptly left into the oncoming traffic laneto avoid the vehicle and causing an extreme hazard.
To
Workflow _ From
08/20/2023

E—

08/20/2023

Eam—.)

0821/2023 Tm.

Forwarded

BOS.

Contents Noted

D2

Contonts Noted

CD2

Contents noted

Page 1012

4AA San Francisco Fire Department\§is) Autonomous Vehicle Incident
en

dl

emcee

RLFv

3
08/21/2023

ou tptheTe a]SRFrom:
EORTS———
To:
Deputy Chief of Operations

Reference: No Reference
Incident Date
0812112023
Time

01:10

Incident No

08/21/2023 01:11 - 232330091 - 1369 9TH AV - 52C4U

Location

1145 Stanyan Street

AV Company

CruiseLicence Plate(s)unknown

Contacted Company?

No

Number ofAVs Involved

1

AAV Company Response

Time.

Supervisor ID

Impact (Description of Event)
Truck 12 was in quarters and attempting to respond to a building alarm. A Cruise vehicle was stopped
directly in frontof quarters preventing T12 from leaving. T12 had to tumoffall lights and eventually
the vehicle drove off allowing T12 to respond after a significant delay.
Workflow _ FromTo
08/21/2023

ENS
R

08212023 WEEN
08212023 Wem
08222023 W——=

Forwarded

ContenisNoted
Contents Noted
Wordow End

BOS

D2
D2

Contents noted.

Page to12

RA San Francisco Fire Department
NE) Autonomous Vehicle Incident=Fe#

08/21/2023

eh
From:

eT ANE i EaSEE

i

oo

EO

To:
Deputy Chief of Operations
Reference:
et,
aNR
tm
Incident Date
0812112023
Time
04:20
08/21/2023 04:15 - 232330295 - 2055 SILVER AV - 7181
Incident No
Location
Siver AV and Topeka AV
AV Company
Crise
Number of AVs Involved 1
Licence Plate(s)NAContacted Company?
No
AV Company Response

:30

Time
Supervisor ID
Impact (Description of Event)
1. On 08/21/2023 at 04:15 E42 was dispatched to a vehicle fire at 2055 Silver Av. After
extinguishmentofthe vehide fire E42 was informed about a second vehidie fire at the S/W comer ofSilver Av and Topeka Av by 2 motorists.
2. E42 responded to the second vehicle fire and founded a vehice fully involved. Since E42 had used
street for ourhalfa tank of water at the fist vehicle fire, we secured a LP hydrant located across the stopped
andSupply. E42 deployed a 1 3/4" ready line for extinguishment. All approaching motorist
made U-tums to avoid the scene.
5. E42 notice a vehicle approaching very fast. This vehicle ran over our ready line and stopped short of£42, which had its emergency lights on. We were fortunate that our ready line was not damaged. Upon
approaching the vehicle to see if the driver would move by safely, 1 noticed that it was an autonomous
Cruise vehicle.
4. While we were mopping up, the Crise vehicle took off and made a right turn on Topeka Av. andstopped about 50' away. The Cruise vehicle blocked Topeka Av. with its binkers on, until a Crise techShowed up to assist with its removal.
5. The AV Cruise had no passengers.
6. The Av Cruise remained on scene blocking the road for about 45 min.
Workflow _ From
2202s ——
082220 amas

Forwarded
ContensNoted

To
B10
D3

it
Page 1012