The MachineRecord
NHTSA Standing General Order 2021-01

The SGO file, in a form you can search

NHTSA publishes the crash reports as three CSV files of 116 columns each, with several versions of the same report mixed in. This is the same data as one table: driverless systems (ADS) and Level 2 driver assistance side by side, 2021 to today including NHTSA's archive, one row per report at its latest version, every row traceable to its NHTSA report number. Free, CC BY 4.0, refreshed from NHTSA on every pipeline run.

Reports
8612
Fatal
87
Of them Level 2
79
Reporting entities
64
Incidents
2019-08 to 2026-09
Clear filters

1995 reports, showing 1801 to 1900.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
30531-3662ADSTransdev Alternative Services2022-07 02:50San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported12Intersection
On July [XXX], 2022 at 2:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and…On July [XXX], 2022 at 2:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and preparing to make a left turn onto [XXX] to travel south. A passenger car passed the Waymo AV and the vehicle directly behind the Waymo AV by crossing into and driving in the opposing lane of traffic. As the passenger vehicle passed the Waymo on the left, the right side of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. At the time of impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3635-1.
30531-3663ADSTransdev Alternative Services2022-07 23:23San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported9Street
On July [XXX], 2022 at 11:23 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] i…On July [XXX], 2022 at 11:23 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] in the rightmost lane when a passenger car approached the Waymo AV from behind on the left. Just after passing the Waymo AV, the passenger car veered across the path of the Waymo AV into the entrance of a gas station on the right hand side of the roadway. The right rear corner of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3633-1.
30531-3664ADSTransdev Alternative Services2022-07 06:54San Francisco, CA2021 Jaguar I-PaceADSPassenger CarMinor0Intersection
On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehice (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on the [XXX] at [XXX]. The Waymo AV was stopped in the dedicated…On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehice (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on the [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane facing north on the [XXX], awaiting a green signal for a protected left turn onto [XXX]. The signal for traffic proceeding north on the [XXX] turned green, and traffic in adjacent lanes began moving. The left turn arrow signal for the dedicated turn lane occupied by the Waymo AV remained red. The passenger car that had been stopped immediately after which the passenger car left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage and the Waymo AV test driver reported lower back pain. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3628-1.
30531-3665ADSTransdev Alternative Services2022-07 10:08San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Parking Lot
On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]t. The Waymo AV came to a stop while…On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]t. The Waymo AV came to a stop while yielding for an oncoming van in a narrow passageway in a parking lot. While attempting to pass the Waymo AV, the van made contact with the sensor housing on the left rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was stationary and engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3625-1.
30610-3508 v2ADSZoox, Inc.2022-07 14:30San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported1Intersection
A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, Ca when a passenger vehicle turning left from [XXX] on to [XXX] struck the rear of the Zoox vehicle damaging the sensors. There were no injuri…A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, Ca when a passenger vehicle turning left from [XXX] on to [XXX] struck the rear of the Zoox vehicle damaging the sensors. There were no injuries and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
540-3643ADSGeneral Motors, LLC2022-07 2:57San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-…On August [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3580-1)
540-3644ADSGeneral Motors, LLC2022-07 22:46San Francisco, CA2020 Cruise AVADSSUVNo Injuries Reported6Intersection
On August [XXX, 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-…On August [XXX, 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3581-1)
540-3645ADSGeneral Motors, LLC2022-07 1:39San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported12Street
On August [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise…On August [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3582-1)
540-3647ADSGeneral Motors, LLC2022-07 00:27San Francisco, CA2020 Cruise AVADSOther, see NarrativeNo Injuries Reported0Street
On August [XXX], GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On August [XXX], GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3584-1)
30270-3255 v2ADSWaymo LLC2022-06 12:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] A Waymo Autonomous Vehicle ("Waymo AV") operating in San Fra…A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] between [XXX] and [XXX]. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3435ADSWaymo LLC2022-06 07:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on ea…On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX], a pickup that had previously been stopped behind the Waymo AV rolled forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Eastern time zone on the required date.
30270-3437ADSWaymo LLC2022-06 10:07San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous…On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous mode behind stopped traffic facing east on [XXX]. The passenger vehicle ahead of the Waymo AV transitioned into reverse and began to accelerate, making contact with the front sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Eastern time zone on the required date.
30270-3655ADSWaymo LLC2022-06 16:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeMinor18Intersection
On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] a…On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] at [XXX], according to a claim by the driver of the passenger vehicle. The Waymo AV was in autonomous mode and preparing to enter southbound [XXX] via the slip lane at southbound [XXX]. The Waymo AV proceeded to merge onto [XXX] as a passenger vehicle on [XXX] approached from behind. A pickup truck was traveling next to the passenger vehicle in the adjacent left lane. As the passenger vehicle approached the Waymo AV from behind, the passenger vehicle entered the adjacent left lane that was occupied by the pickup truck and maneuvered around the Waymo AV. The pickup truck proceeded without stopping, and the passenger vehicles driver shortly after signaled to the Waymo AV test driver to pull over. The Waymo AV test driver then transitioned to manual mode and pulled over. Waymo has no data or knowledge of any contact between any of the three vehicles. There was no contact or collision between the Waymo AV and any other vehicle. However, the driver and passenger in the passenger vehicle have subsequently alleged injuries based on alleged contact between the pick-up truck and passenger vehicle, which contact their allegations attribute to the behavior of Waymos AV in a bodily injury claim under Waymos insurance policy. Waymo received notice of this insurance claim on July [XXX]. Waymo is reporting this event under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Eastern time zone on the required date.
30412-3080 v2ADSCruise LLC2022-06 1:54San Francisco, CA2020 Cruise AVADSNon-Motorist: PedestrianUnknown5StreetRedacted by NHTSA as confidential business information
30412-3084 v2TMR-0214ADSCruise LLC2022-06 23:00San Francisco, CA2022 Cruise AVADSPassenger CarMinor0IntersectionRedacted by NHTSA as confidential business information
30412-3281 v2ADSCruise LLC2022-06 10:49San Francisco, CA2020 Cruise AVADSNon-Motorist: CyclistMinor19StreetRedacted by NHTSA as confidential business information
30531-3256 v2ADSTransdev Alternative Services2022-06 12:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. As the Waymo AV turned left and into the parking lot, the Waymo AV's…A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did no contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX].
30531-3445ADSTransdev Alternative Services2022-06 7:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on ea…On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX], a pickup that had previously been stopped behind the Waymo AV rolled forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX]
30531-3446ADSTransdev Alternative Services2022-06 10:07San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous…On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous mode behind stopped traffic facing east on [XXX]. The passenger vehicle ahead of the Waymo AV transitioned into reverse and began to accelerate, making contact with the front sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX]
30531-3660ADSTransdev Alternative Services2022-06 16:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeMinor18Intersection
On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] a…On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] at [XXX], according to a claim by the driver of the passenger vehicle. The Waymo AV was in autonomous mode and preparing to enter southbound [XXX] as a passenger vehicle on [XXX] approached from behind. A pickup truck was traveling next to the passenger vehicle in the adjacent left lane. As the passenger vehicle approached the Waymo AV from behind, the passenger vehicle entered the adjacent left lane that was occupied by the pickup truck and maneuvered around the Waymo AV. The pickup truck proceeded without stopping, and the passenger vehicle's driver shortly after signaled to the Waymo AV test driver to pull over. The Waymo AV test driver then transitioned to manual mode and pulled over. Transdev has no data or knowledge of any contact between any of the three vehicles. There was no contact or collision between the Waymo AV and any other vehicle. However, the driver and passenger in the passenger vehicle have subsequently alleged injuries based on alleged contact between the pick-up truck and passenger vehicle, which contact their allegations attribute to the behavior of Waymo's AV in a bodily injury claim under Waymo's insurance policy. Waymo received notice of this insurance claim on July [XXX]. Transdev Alternative Services is reporting this event under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3655-1.
30590-3431ADSApple Inc.2022-06 15:15Mountain View, CA2016 Lexus RX 450hADSPassenger CarNo Injuries Reported0Intersection
Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's …Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's designated seating position, and with a safety operator in the front passenger seating position. Subject vehicle approached a red light to make a right turn East-bound onto [XXX]. The safety operator suggested that the safety driver disengage the ADS and make the turn in manual mode because the vehicle was hesitant in approaching the intersection. The safety driver disengaged the ADS, and, approximately 250ms later, subject vehicle was lightly struck from behind by a white Mazda3. Having seen debris on the roadway, the driver and operator believed they had run over a rock and did not realize they were hit by the vehicle. After concluding the mission, the driver and operator found damage to a sensor during an inspection. A subsequent review of video led to discovery of the crash. No injuries were reported, and law enforcement was not called to the scene. In addition to telematics and video, we also have photographs of the vehicle's damaged sensor.
30610-3072 v2ADSZoox, Inc.2022-06 13:15San Francisco, CA2016 Toyota HighlanderADSNon-Motorist: OtherModerate12Intersection
A Zoox vehicle in autonomous mode was proceeding westbound with the right of way on a green traffic light at the six way intersection of [XXX], [XXX], and [XXX], when a person operating an electric scooter ran a red ligh…A Zoox vehicle in autonomous mode was proceeding westbound with the right of way on a green traffic light at the six way intersection of [XXX], [XXX], and [XXX], when a person operating an electric scooter ran a red light and proceeded northbound into the intersection. The scooter made contact with the left rear quarter panel of the Zoox vehicle, at which time the Zoox vehicle had disengaged from autonomous mode. The Zoox vehicle pulled over, and police and emergency services arrived at the scene. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field and to update for additional information received in August 2022. This update provides complete information for this incident.
30610-3215 v2ADSZoox, Inc.2022-06 10:45San Mateo, CA2016 Toyota HighlanderADSSUVNo Injuries Reported6Street
A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the seco…A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the second vehicle and cut in abruptly from the left, making contact with the front left side and sensors of the Zoox vehicle as it was exiting the space. The Zoox operator disengaged to manual mode just before the contact. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
30610-3320ADSZoox, Inc.2022-06 14:36San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported25Street
A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor dama…A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor damage to both vehicles. The Zoox vehicle had disengaged for unrelated traffic within 30 seconds of the contact. There were no injuries and the police were not called.
540-3083 v2ADSGeneral Motors, LLC2022-06 1:54San Francisco, CA2020 Cruise AVADSNon-Motorist: PedestrianUnknown5Street
On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3080-2)
540-3085 v2ADSGeneral Motors, LLC2022-06 23:00San Francisco, CA2022 Cruise AVADSPassenger CarMinor0Intersection
On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3084-2)
540-3283 v2ADSGeneral Motors, LLC2022-06 10:49San Francisco, CA2020 Cruise AVADSNon-Motorist: CyclistMinor19Street
On July [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured…On July [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3281-2)
30270-3055 v2ADSWaymo LLC2022-05 01:16San Francisco, CA2021 Jaguar I-PACEADSMotorcycleNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3219ADSWaymo LLC2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3220ADSWaymo LLC2022-05 09:19San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX] while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3221ADSWaymo LLC2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Intersection
On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] at [XXX]. , [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30412-3073ADSCruise LLC2022-05 4:37San Francisco, CA2020 Cruise AVADSPassenger CarMinor0IntersectionRedacted by NHTSA as confidential business information
30531-3064 v2ADSTransdev Alternative Services2022-05 01:16San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativeMotorcycleNo Injuries Reported0Intersection
Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Sa…Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202205[XXX]-0 (rev.202205[XXX]215904).
30531-3225ADSTransdev Alternative Services2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-[XXX].
30531-3226ADSTransdev Alternative Services2022-05 09:19San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX]. while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX].
30531-3227ADSTransdev Alternative Services2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Intersection
On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] …On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-2022[XXX]-0 (rev.20220615[XXX])
30610-3158 v2ADSZoox, Inc.2022-05 13:30San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported25Street
A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is su…A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
30711-3157ADSPony.ai2022-05 15:00Irvine, CA2021 Hyundai Kona EVADSPassenger CarNo Injuries Reported4Street
On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of t…On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of the Pony.ai vehicle. The Pony.ai vehicle did not suffer damage. There were no injuries, the police were not called to the scene, and the Pony.ai vehicle was driven back to Pony.ai's Irvine-area facility. Please note that the "UNK" checkbox was selected for the Pony.ai vehicle in the grid as there is no option to select "no damage" for the subject vehicle. The only minor damage in the incident was to the passenger vehicle.
540-3123ADSGeneral Motors, LLC2022-05 4:37San Francisco, CA2020 Cruise AVADSPassenger CarMinor0Intersection
On June [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order").General Motors LLC (GM) manufactured the Cruise-op…On June [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order").General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3073-1)
855-3183 v2ADSMercedes-Benz USA, LLC2022-05 15:05Commerce, CA2022 Mercedes-Benz S350DADSHeavy TruckNo Injuries ReportedHighway / Freeway
While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resu…While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resulted in two minor scratches and two indentations on the rear bumper of the Mercedes-Benz. The driver of the truck did not pull over after the collision. The Mercedes-Benz was driven from the incident location, and further inspection of the vehicle concluded no additional damage beyond the cosmetic dents and surface scratches.
30270-2610 v2ADSWaymo LLC2022-04 02:27San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported20Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was in autonomous mode and proceeding southbound on [XXX] in the rightmost lane, with a passenger vehicle traveling parallel in the left adjacent lane. As the two vehicles approached [XXX], the passenger vehicle cut into the Waymo's lane and braked before turning right on [XXX]. As the passenger vehicle executed the right turn, the Waymo AV test driver transitioned to manual mode, applied the brakes, but made contact with the passenger side rear corner of the passenger vehicle. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The other party immediately left the scene of the event. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2646 v2ADSWaymo LLC2022-04 19:55San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger car on [XXX] at [XXX] The Waymo AV came to a stop at a stop sign on [XXX] at [XXX] and as it was about to proceed, a passenger vehicle behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2743 v2ADSWaymo LLC2022-04 14:53San Francisco, CA2021 Jaguar I-PaceADSPickup TruckMinor0Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2743-1]. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2743-1]. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling in autonomous mode in the slip lane on northbound [XXX] at [XXX]. As the Waymo AV slowed to yield to a pedestrian pushing a shopping cart in a crosswalk, the Waymo AV test driver transitioned to manual mode and stopped the Waymo AV. The Waymo AV test driver then proceeded forward but had to yield to approaching traffic in the merge between northbound [XXX] and northbound [XXX]. As the Waymo AV came to a stop, a pickup truck traveling behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and the Waymo AV test driver was transported from the scene for medical treatment due to reported injuries. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2793 v2ADSWaymo LLC2022-04 02:31San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Auto…Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA made contact with a parking lot driveway on the 200 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2818 v2ADSWaymo LLC2022-04 16:36San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Street
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2818-1]. On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2818-1]. On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling on westbound [XXX], when it slowed for the vehicle directly in front of the Waymo AV, which stopped shortly after passing [XXX]. Shortly after the Waymo AV came to a stop, the SUV behind the Waymo AV was rear-ended by a pickup truck, and the SUV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3009ADSWaymo LLC2022-04 8:14San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On April [XXX], 2022 at 8:14 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped at a red l…On April [XXX], 2022 at 8:14 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped at a red light facing northeast on [XXX] in autonomous mode. While the light was still red, a passenger vehicle that had been stopped behind the Waymo AV began to move forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3011ADSWaymo LLC2022-04 06:37San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported17Street
On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in ma…On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in manual in the left lane of [XXX] (a one-way street). After passing through the [XXX] intersection, a parked pickup truck on the left side of [XXX] pulled out of the parked position and made contact with the front left fender of the passing Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30412-2823 v2ADSCruise LLC2022-04 23:21San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-2884ADSCruise LLC2022-04 00:43San Francisco, CA2020 Cruise AVADSSUVNo Injuries Reported5IntersectionRedacted by NHTSA as confidential business information
30412-2885ADSCruise LLC2022-04 01:55San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-2886ADSCruise LLC2022-04 23:21San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported22StreetRedacted by NHTSA as confidential business information
30412-2887ADSCruise LLC2022-04 00:13San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-2888ADSCruise LLC2022-04 03:35San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported2StreetRedacted by NHTSA as confidential business information
30531-2822 v2ADSTransdev Alternative Services2022-04 16:36San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Street
The content of this report is unchanged from the initial report (Report ID 30531-2822-1) On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collisi…The content of this report is unchanged from the initial report (Report ID 30531-2822-1) On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling on westbound [XXX], when it slowed for the vehicle directly in front of the Waymo AV, which stopped shortly after passing [XXX]. Shortly after the Waymo AV came to a stop, the SUV behind the Waymo AV was rear-ended by a pickup truck, and the SUV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is identical to WaymoLLC-202204[XXX]-0 (rev.202204[XXX]190125)
30610-2913ADSZoox, Inc.2022-04 05:55San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported8Intersection
A Zoox vehicle in autonomous mode was proceeding straight through the intersection of [XXX]. and [XXX]. when it was rear-ended by a passenger vehicle that was switching lanes and made contact with the Zoox vehicle's rear…A Zoox vehicle in autonomous mode was proceeding straight through the intersection of [XXX]. and [XXX]. when it was rear-ended by a passenger vehicle that was switching lanes and made contact with the Zoox vehicle's rear sensors. The other party left the scene. The police were not called, and there were no injuries.
30711-2862ADSPony.ai2022-04 9:00Miliptas, CA2020 Hyundai Kona EVADSPassenger CarNo Injuries Reported0Parking Lot
On April [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was parked in a parking lot when a passenger vehicle reversed into the Pony.ai vehicle. T…On April [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was parked in a parking lot when a passenger vehicle reversed into the Pony.ai vehicle. The Pony.ai vehicle sustained minor damage to the driver's side rear door. There were no injuries, the police were not called to the scene, and the Pony.ai vehicle was driven back to Pony.ai's Fremont facility.
540-2827 v2ADSGeneral Motors, LLC2022-04 23:21San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On May [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manuf…On May [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: (30412-2823-2)
540-2907ADSGeneral Motors, LLC2022-04 00:43San Francisco, CA2020 Cruise AVADSSUVNo Injuries Reported5Intersection
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order").?General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order").?General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI; GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-2884-1)
540-2925ADSGeneral Motors, LLC2022-04 01:55San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-2885-1)
540-2926ADSGeneral Motors, LLC2022-04 23:21San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported22Street
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI; GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-2886-1)
540-2927ADSGeneral Motors, LLC2022-04 00:13San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported1Street
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-2887-1)
540-2928ADSGeneral Motors, LLC2022-04 03:35San Francisco, CA2020 Cruise AVADSPassenger CarUnknown2Street
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-2888-1)
1712-2474 v2ADSRobert Bosch, LLC2022-03 08:50Los Angeles, CAEQS 450 4maticADSUnknownMinorParking LotRedacted by NHTSA as confidential business information
30270-2605 v2ADSWaymo LLC2022-03 01:16San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported9Intersection
The description of the event in this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2605-1]. On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') ope…The description of the event in this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2605-1]. On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was slowing for a stop sign while traveling westbound on [XXX] in autonomous mode. An SUV approached from behind and made contact with the rear of the Waymo AV. The other party immediately left the scene of the event. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained moderate damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2609 v2ADSWaymo LLC2022-03 11:07San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported4Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2609-1]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fr…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2609-1]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on the 1000 block of [XXX]. The Waymo AV was stopped at a red traffic light on southbound [XXX] when a pedestrian entered the crosswalk. When the traffic light turned green, the Waymo AV remained stopped for a crossing pedestrian who had just reached the pedestrian island in the middle of the crosswalk. After a brief pause, the ADV started to proceed, when the SUV behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2773ADSWaymo LLC2022-03 07:35San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported3Intersection
On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on …On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on [XXX] in manual mode in a narrow passageway. The Waymo AV approached a stop sign and the test driver steered to the right around a parked vehicle with oncoming traffic approaching. The right rear sensor housing of the Waymo AV made contact with a parked SUV on the right side of the road. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2775ADSWaymo LLC2022-03 12:22San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic…On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic, eastbound on [XXX] in autonomous mode. A parked car to the right of the Waymo AV began reversing into the street and made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30412-2588 v2ADSCruise LLC2022-03 13:24San Francisco, CA2022 Cruise AVADSNon-Motorist: CyclistSerious4StreetRedacted by NHTSA as confidential business information
30412-2593 v2ADSCruise LLC2022-03 02:07San Francisco, CA2020 Cruise AVADSPickup TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-2654 v2ADSCruise LLC2022-03 12:26San Francisco, CA2020 Cruise AVADSPassenger CarModerate10Street
A Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound in the rightmost lane on [XXX] between [XXX] and [XXX]. Ahead of the Cruise AV, a delivery truck was double-park…A Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound in the rightmost lane on [XXX] between [XXX] and [XXX]. Ahead of the Cruise AV, a delivery truck was double-parked in the rightmost lane of westbound [XXX]. The Cruise AV began to maneuver around the double-parked vehicle by changing lanes. At the same time, a 2010 Honda Civic traveling behind the Cruise AV in the rightmost lane also began to maneuver and increase speed into the leftmost lane. Shortly thereafter, contact was made with the Cruise AV's side door, damaging the front driver side door and radar assembly. There were no reported injuries at the scene by either party and police were not called. The driver of the Honda Civic later claimed injuries related to the event. [Cruise processes ADS compute data regarding the incident.]
30610-2584 v2ADSZoox, Inc.2022-03 15:00San Francisco, CA2016 Toyota HighlanderADSNon-Motorist: OtherMinor2Intersection
A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right a…A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right and made contact with the rear corner of the Zoox vehicle at low speed. Police were not called. The Zoox vehicle was in autonomy in the 30 second period prior to contact.
30610-2651ADSZoox, Inc.2022-03 08:20San Francisco, CA2016 Toyota HighlanderADSPassenger CarMinor1IntersectionA Zoox vehicle in autonomous mode was stopped in traffic when a passenger vehicle from behind made contact with the rear of the Zoox vehicle at low speed. The police were not called.
30711-2666ADSPony.ai2022-03 11:30Tustin, CA2019 Hyundai Kona EVADSOther, see NarrativeNo Injuries Reported23Street
On March [XXX], 2022, while in supervised ("Drivered") autonomous mode traveling eastbound in the right lane of [XXX] in Tustin, CA, a Pony.ai Autonomous Vehicle drove over a temporary sign that had previously fallen ove…On March [XXX], 2022, while in supervised ("Drivered") autonomous mode traveling eastbound in the right lane of [XXX] in Tustin, CA, a Pony.ai Autonomous Vehicle drove over a temporary sign that had previously fallen over and was lying flat on its side in the travel lane. The impact redirected the vehicle towards the curb. The Safety Operator took control, disengaging autonomous mode, braked, and steered the vehicle away from the direction of the curb. The right front tire scraped the right curb. The vehicle sustained minor damage to the right front strut and control arm. There were no injuries and no other vehicles involved. The Safety Operator drove the vehicle back to Pony.ai's Irvine facility. Explanation for "Roadway Description": There was a sign lying flat on its side in the travel lane. Explanation for "Crash With" Description: The subject vehicle's tire made contact with the right curb.
540-2590 v2ADSGeneral Motors, LLC2022-03 13:24San Francisco, CA2022 Cruise AVADSNon-Motorist: CyclistSerious4Street
On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruis…On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report.(Reference file: 30412-2588-2).
540-2594 v2ADSGeneral Motors, LLC2022-03 02:07San Francisco, CA2020 Cruise AVADSPickup TruckNo Injuries Reported0Street
On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruis…On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI; GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference.? GM's submission is based on facts supplied to GM by Cruise.? GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: (30412-2593-2).
540-2706 v2ADSGeneral Motors, LLC2022-03 12:26San Francisco, CA2020 Cruise AVADSPassenger CarModerate10Street
On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an updated report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") m…On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an updated report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report.? Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI; GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: (30412-2654-2).
855-2464 v2ADSMercedes-Benz USA, LLC2022-03 08:50Los Angeles, CAMercedes-Benz EQS 450 4MaticADSOther, see NarrativeMinor1Parking LotNo additional information to report at this time.
30270-2248ADSWaymo LLC2022-02 17:46San Francisco, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported4Intersection
On February [XXX], 2022 at 5:46 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a bicyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling…On February [XXX], 2022 at 5:46 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a bicyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling southbound on [XXX] when it came to a stop at [XXX]. As the Waymo AV proceeded, a bicyclist traveling northbound on [XXX] proceeded through the stop sign without stopping in order to make a left turn onto westbound [XXX]. The Waymo AV began to brake and the test driver (in the driver's seating position), disengaged the AV system and continued braking. As the bicyclist attempted to complete their left turn, the bicyclist made contact with the driver side rear corner of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user was involved. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2358 v2ADSWaymo LLC2022-02 17:46San Francisco, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported4Intersection
Other than correcting the towing status of the Waymo AV, which was not towed, the content of this report is unchanged from the initial report submitted on February [XXX], 2022 [Report ID #30270-2248-1]. On February [XXX…Other than correcting the towing status of the Waymo AV, which was not towed, the content of this report is unchanged from the initial report submitted on February [XXX], 2022 [Report ID #30270-2248-1]. On February [XXX], 2022 at 5:46 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a bicyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling southbound on [XXX] when it came to a stop at [XXX]. As the Waymo AV proceeded, a bicyclist traveling northbound on [XXX] proceeded through the stop sign without stopping in order to make a left turn onto westbound [XXX]. The Waymo AV began to brake and the test driver (in the driver's seating position), disengaged the AV system and continued braking. As the bicyclist attempted to complete their left turn, the bicyclist made contact with the driver side rear corner of the Waymo AV. At the time of the impact, the Waymo's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user was involved. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2551ADSWaymo LLC2022-02 08:44San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On February [XXX], 2022 at 8:44 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was stopped at a stop sign facing …On February [XXX], 2022 at 8:44 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was stopped at a stop sign facing west on [XXX] in autonomous mode while yielding to pedestrians in the crosswalk. After the pedestrians had crossed, the Waymo started to edge forward when an SUV to the Waymo AV's rear passed the Waymo AV by driving in the oncoming traffic lane and made contact with the left rear sensor housing of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2552ADSWaymo LLC2022-02 15:05San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Street
On February [XXX], 2022 at 3:05 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pick-up truck on [XXX] near [XXX]. The Waymo AV was traveling westboun…On February [XXX], 2022 at 3:05 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pick-up truck on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode and came to a stop while yielding to an oncoming pick-up truck in a narrow roadway. The oncoming truck continued proceeding straight and made contact with the rear left sensor of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2553ADSWaymo LLC2022-02 15:02San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On February [XXX], 2022 at 3:02 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red …On February [XXX], 2022 at 3:02 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light facing north on [XXX] at the [XXX] intersection in autonomous mode. While the traffic light was still red, the vehicle immediately behind the Waymo AV began to accelerate and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2554ADSWaymo LLC2022-02 19:45San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On February [XXX], 2022 at 7:45 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle at the northbound merge lane on the 100 block of [XXX…On February [XXX], 2022 at 7:45 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a vehicle approached from behind and made contact with the rear bumper of the Waymo AV. The other vehicle left the scene without exchanging information. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2555ADSWaymo LLC2022-02 00:49San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On February [XXX], 2022 at 12:49 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red…On February [XXX], 2022 at 12:49 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light facing west on [XXX] at the [XXX] intersection in the left turn lane in autonomous mode. While the traffic light was still red, the vehicle immediately behind the Waymo AV began to accelerate toward the right side of the Waymo AV and made contact with the right rear bumper of the Waymo AV. The other vehicle left the scene without exchanging information. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2556ADSWaymo LLC2022-02 13:00San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Intersection
On February [XXX], 2022 at 1:00 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. While traveling southbound on [XXX…On February [XXX], 2022 at 1:00 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. While traveling southbound on [XXX] at [XXX] in autonomous mode, the Waymo AV approached a green light and signaled for a right turn when a pedestrian entered the adjacent crosswalk in accordance with the pedestrian 'WALK' signal. As the Waymo AV began to slow, the driver transitioned the system into manual mode. A few seconds later, a passenger vehicle approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30412-2476 v2ADSCruise LLC2022-02 00:48San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported13IntersectionRedacted by NHTSA as confidential business information
30610-2227 v2ADSZoox, Inc.2022-02 08:40San Francisco, CA2016 Toyota HighlanderADASNon-Motorist: CyclistNo Injuries Reported0Street
A Zoox vehicle in manual mode was stopped on [XXX], when a bicyclist riding on the wrong side of the street rode into the front bumper of the Zoox vehicle. The Zoox vehicle did not incur any damage. There were no injurie…A Zoox vehicle in manual mode was stopped on [XXX], when a bicyclist riding on the wrong side of the street rode into the front bumper of the Zoox vehicle. The Zoox vehicle did not incur any damage. There were no injuries and the police were not called. Autonomy was engaged within the 30 second period prior to the collision. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. This update provides complete information for this incident
30610-2482ADSZoox, Inc.2022-02 20:55San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported0Street
A Zoox vehicle when in autonomous mode was stopped at a traffic light on [XXX] at [XXX] when a passenger vehicle hit the Zoox vehicle from behind. The passenger vehicle left the scene without exchanging information. Ther…A Zoox vehicle when in autonomous mode was stopped at a traffic light on [XXX] at [XXX] when a passenger vehicle hit the Zoox vehicle from behind. The passenger vehicle left the scene without exchanging information. There were no injuries and the police were not called.
540-2512 v2ADSGeneral Motors, LLC2022-02 00:48San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported13Intersection
On June [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactu…On June [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise"s responses to these fields, and incorporates Cruise"s responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: Cruise Report ID 30412-2476-2)
30270-2160ADSWaymo LLC2022-01 17:20San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported11Intersection
On January [XXX], 2022 at 5:20 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was in autonomous mode on east…On January [XXX], 2022 at 5:20 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was in autonomous mode on eastbound [XXX] as it approached [XXX]. The test driver (in the driver's seating position) transitioned to manual mode before reaching the intersection. The Waymo AV then proceeded through a green light into the intersection in manual mode. A passenger vehicle traveling northbound on [XXX] then entered the intersection against its red light, making contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage to its front fascia and the passenger vehicle sustained damage to its driver side doors. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV was towed away and the passenger vehicle's airbags deployed. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2168ADSWaymo LLC2022-01 02:11San Francisco, CA2021 Jaguar I-PaceADSMotorcycleNo Injuries Reported2Intersection
On January [XXX], 2022 at 2:11 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was in autonomous mode on southbound …On January [XXX], 2022 at 2:11 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was in autonomous mode on southbound [XXX] in the intersection with [XXX], when the Waymo AV began to slow for a motorcyclist traveling on northbound [XXX] signaling to make an unprotected left turn onto [XXX]. The test driver (in the driver's seating position) transitioned to manual mode and continued to slow the Waymo AV. The motorcyclist attempted to turn behind the Waymo AV and made contact with the left rear corner of the Waymo AV. The motorcyclist remained upright and rode away without stopping to provide any information. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage to the driver's side of the rear bumper. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user (motorcyclist) was involved. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2197ADSWaymo LLC2022-01 17:20San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported11Intersection
The content of this report is unchanged from the initial report submitted on January [XXX], 2022 [Report ID # 30270-2160-1]. On January [XXX], 2022 at 5:20 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San…The content of this report is unchanged from the initial report submitted on January [XXX], 2022 [Report ID # 30270-2160-1]. On January [XXX], 2022 at 5:20 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was in autonomous mode on eastbound [XXX] as it approached [XXX]. The test driver (in the driver's seating position) transitioned to manual mode before reaching the intersection. The Waymo AV then proceeded through a green light into the intersection in manual mode. A passenger vehicle traveling northbound on [XXX] then entered the intersection against its red light, making contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage to its front fascia and the passenger vehicle sustained damage to its driver side doors. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV was towed away and the passenger vehicle's airbags deployed. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2198ADSWaymo LLC2022-01 20:40San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On January [XXX], 2022 at 8:40 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a SUV on [XXX] at [XXX]. While proceeding straight on eastbound [XXX] in autonomou…On January [XXX], 2022 at 8:40 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a SUV on [XXX] at [XXX]. While proceeding straight on eastbound [XXX] in autonomous mode, the Waymo AV slowed down and came to a halt at the stop sign at the intersection with [XXX]. A SUV approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo vehicle was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2206ADSWaymo LLC2022-01 02:11San Francisco, CA2021 Jaguar I-PaceADSMotorcycleNo Injuries Reported2Intersection
The content of this report is unchanged from the initial report submitted on January [XXX], 2022 [Report ID # 30270-2168-1]. On January [XXX], 2022 at 2:11 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San…The content of this report is unchanged from the initial report submitted on January [XXX], 2022 [Report ID # 30270-2168-1]. On January [XXX], 2022 at 2:11 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was in autonomous mode on southbound [XXX] in the intersection with [XXX], when the Waymo AV began to slow for a motorcyclist traveling on northbound [XXX] signaling to make an unprotected left turn onto [XXX]. The test driver (in the driver's seating position) transitioned to manual mode and continued to slow the Waymo AV. The motorcyclist attempted to turn behind the Waymo AV and made contact with the left rear corner of the Waymo AV. The motorcyclist remained upright and rode away without stopping to provide any information. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage to the driver's side of the rear bumper. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user (motorcyclist) was involved. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2226ADSWaymo LLC2022-01 20:40San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
Other than updating the Waymo AV's speed and damage description, the content of this report is unchanged from the initial report submitted on January [XXX], 2022 [Report ID # 30270-2198-1]. On January [XXX], 2022 at 8:4…Other than updating the Waymo AV's speed and damage description, the content of this report is unchanged from the initial report submitted on January [XXX], 2022 [Report ID # 30270-2198-1]. On January [XXX], 2022 at 8:40 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a SUV on [XXX] at [XXX]. While proceeding straight on eastbound [XXX] in autonomous mode, the Waymo AV slowed down and came to a halt at the stop sign at the intersection with [XXX]. As the Waymo began to proceed, a SUV approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained moderate damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo vehicle was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2323ADSWaymo LLC2022-01 02:04San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
On January [XXX], 2022 at 2:04 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger vehicle at [XXX] and [XXX]. While the Waymo AV was proceeding …On January [XXX], 2022 at 2:04 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger vehicle at [XXX] and [XXX]. While the Waymo AV was proceeding straight in autonomous mode on eastbound [XXX], a passenger vehicle turned right onto westbound [XXX] from [XXX], crossing the center lane line and traveling in the oncoming traffic lane. The driver of the Waymo AV transitioned the system into manual mode and slowed, and moved to the right most edge of the lane. The oncoming passenger vehicle struck the left side of the Waymo AV and immediately proceeded to leave the scene of the collision. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver (in the driver's seating position) was operating the Waymo AV in manual mode. The Waymo AV sustained moderate damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2327ADSWaymo LLC2022-01 09:00San Francisco, CA2021 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Intersection
On January [XXX], 2022 at 9:00 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a box truck at the northbound merge lane on the 100 block of [XXX]. While…On January [XXX], 2022 at 9:00 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a box truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. The box truck then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV and the box truck both sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2328ADSWaymo LLC2022-01 14:24San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On January [XXX], 2022 at 2:24 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light facing …On January [XXX], 2022 at 2:24 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light facing north on [XXX] in autonomous mode at the [XXX] intersection. The light turned green and the Waymo AV proceeded partially into the intersection, yielding to pedestrians in the left crosswalk while preparing to make a left turn. An SUV parked behind the Waymo AV on the right shoulder of Sacramento street pulled out of the shoulder and made contact with the right side of the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2329ADSWaymo LLC2022-01 06:30San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported4Intersection
On January [XXX], 2022 at 6:30 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light on …On January [XXX], 2022 at 6:30 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light on northbound [XXX] at [XXX]. After the traffic light turned green and the Waymo AV had begun to accelerate, the passenger vehicle behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV and the trailing passenger vehicle both sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30412-2173 v3ADSCruise LLC2022-01 03:56San Francisco, CA2020 Cruise AVADSSUVNo Injuries Reported25IntersectionRedacted by NHTSA as confidential business information

What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.