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
267 reports, showing 101 to 200.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30531-3884 | ADS | Transdev Alternative Services | 2022-08 18:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Intersection | On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came …On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came to a stop behind a double-parked vehicle in the right lane. Shortly after coming to a stop, a van approached from behind and made contact with the rear of the Waymo AV. The van then changed lanes and 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 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-202208[XXX]-0 (rev.202209[XXX]162510). | |
| 30610-3703 v3 | ADS | Zoox, Inc. | 2022-08 17:21 | Menlo Park, CA | 2019 Toyota Highlander | ADS | Passenger Car | Minor | 2 | Street | A Zoox vehicle in autonomy had made a right turn from [XXX] onto [XXX] in Menlo Park, CA and was preparing to make an immediate, unprotected left turn onto [XXX]. The Zoox vehicle was slowing and moving at approximately …A Zoox vehicle in autonomy had made a right turn from [XXX] onto [XXX] in Menlo Park, CA and was preparing to make an immediate, unprotected left turn onto [XXX]. The Zoox vehicle was slowing and moving at approximately 2 mph with its brake lamps and left turn indicator illuminated, yielding to an oncoming vehicle with the right of way. A following vehicle - traveling at approximately 24 mph - then struck the Zoox vehicle's right rear bumper, and that vehicle's driver airbag appeared to have deployed on impact. The Zoox operator disengaged autonomy, proceeded with the left turn, and pulled over. The following vehicle continued its path of travel, veered out of the lane, and collided with a tree on the left side of the road. The Menlo Park Police Department was called to the scene. Two Zoox operators sustained minor injuries and it is unknown if the driver of the other vehicle sustained injuries. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. | |
| 30610-3719 v2 | ADS | Zoox, Inc. | 2022-08 21:20 | Las Vegas, CA | 2016 Toyota Highlander | ADS | Non-Motorist: Pedestrian | No Injuries Reported | 2 | Parking Lot | A Zoox vehicle in autonomy was proceeding at approximately 2mph towards an exit of a private hotel driveway in Las Vegas, Nevada when it was struck on its right front fender by two individuals involved in an altercation …A Zoox vehicle in autonomy was proceeding at approximately 2mph towards an exit of a private hotel driveway in Las Vegas, Nevada when it was struck on its right front fender by two individuals involved in an altercation who had darted out from the side of the roadway. The right front fender of the Zoox vehicle was dented. The two individuals fled the scene and Zoox is not aware of any reported injuries. We question whether this interaction meets the reporting requirements nevertheless, we are submitting this report out of an abundance of caution. This 10-Day update provides complete information for this incident. | |
| 30610-3751 | ADS | Zoox, Inc. | 2022-08 21:01 | San Francisco, CA | 2016 Toyota Highlander | ADS | Van | No Injuries Reported | 0 | Street | A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA, in stop-and-go traffic. The Zoox vehicle came to a stop for a vehicle ahead when a following van made light contact with the Zoox vehicle'…A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA, in stop-and-go traffic. The Zoox vehicle came to a stop for a vehicle ahead when a following van made light contact with the Zoox vehicle's rear bumper from behind. There were no injuries and the police were not called. | |
| 502-3864 | ADS | Ford Motor Company | 2022-08 17:55 | Miami Beach, FL | 2020 Ford Escape | ADS | Pickup Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-3866 | ADS | Ford Motor Company | 2022-08 12:31 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 540-3819 | ADS | General Motors, LLC | 2022-08 07:04 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 14 | Street | On September [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 Cru…On September [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-3801-1) | |
| 540-3820 | ADS | General Motors, LLC | 2022-08 03:53 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Street | On September [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 Cru…On September [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-3806-1) | |
| 988-3684 v2 | ADS | PACCAR Incorporated | 2022-08 18:00 | Palmer, TX | 2022 Kenworth T680 | ADS | Pickup Truck | No Injuries Reported | 15 | Highway / Freeway | Monthly Report Update: A police report was issued after the original SGO incident reports were submitted and described the cause of the collision as the pick-up truck's failure to control its speed before rear-ending the…Monthly Report Update: A police report was issued after the original SGO incident reports were submitted and described the cause of the collision as the pick-up truck's failure to control its speed before rear-ending the Kodiak AV. The content of this report is otherwise unchanged from the initial incident report submitted on August [XXX], 2022. On August [XXX], 2022, Kodiak Robotics, Inc. ("Kodiak") filed an Incident Report (the "Report") under the Standing General Order 2021-01 (the "Order"). PACCAR, Inc. (Paccar) manufactured the Kodiak-operated motor vehicle involved in the incident summarized in the Incident Report. Because Paccar is also a Reporting Entity under the Order, Paccar is submitting a duplicate of the redacted public copy of the Report. Paccar has selected "Unknown" in the "ADS version" field solely to avoid the second submission of nonpublic Kodiak CBI. Paccar is in possession of Kodiak's response to this field and incorporates Kodiak's response into this submission by reference. Paccar's submission is based on facts supplied to Paccar by Kodiak. Paccar has not investigated the alleged incident and has no independent knowledge of the facts in the Report. | |
| 12381-3438 v2 | ADS | Daimler Trucks North America, LLC | 2022-07 16:33 | ALBUQUERQUE, NM | 2021 FREIGHTLINER Cascadia | ADS | Other, see Narrative | No Injuries Reported | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 12381-3557 | ADS | Daimler Trucks North America, LLC | 2022-07 12:39 | Santa Rosa, NM | 2021 Freightliner Cascadia | ADS | Other, see Narrative | No Injuries Reported | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30270-3323 v2 | ADS | Waymo LLC | 2022-07 15:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | The content of this report is unchanged from the initial report submitted on July [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 3:26 PM PST a Waymo Autonomous Vehicle (Way…The content of this report is unchanged from the initial report submitted on July [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 3:26 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 traveling westbound on [XXX] when it detected a siren from a nearby emergency vehicle. As the Waymo AV slowed, a passenger vehicle 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 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 Eastern time zone on the required date. | |
| 30270-3324 v2 | ADS | Waymo LLC | 2022-07 00:57 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | Unknown | 0 | Street | The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 12:57 AM PST a Waymo Autonomous Vehicle ("Wa…The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 12:57 AM PST a Waymo Autonomous Vehicle ("Waymo AV") was traveling eastbound on [XXX] in autonomous mode when a pedestrian entered the roadway from the center median. The test driver then disengaged autonomous mode and braked to a stop as the pedestrian began to run toward the Waymo AV. The pedestrian stood in front of the vehicle, then jumped onto the hood of the Waymo AV and used their body to break the Waymo AV's windshield. The pedestrian was apprehended soon after by nearby police. The Waymo AV test driver was not physically injured but was taken to a nearby hospital out of an abundance of caution. The Waymo AV sustained major damage to its windshield. Waymo is reporting this event to ensure official notification to the agency of a notable event. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-3338 v2 | ADS | Waymo LLC | 2022-07 09:04 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 13 | Intersection | The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waym…The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode and turning left onto eastbound [XXX]. As the Waymo AV initiated the left turn, a passenger vehicle that had been following the Waymo AV 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 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 reported minor injuries. 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-3625 | ADS | Waymo LLC | 2022-07 10:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Parking 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]. The Waymo AV came to a stop whil…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]. 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. 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-3628 | ADS | Waymo LLC | 2022-07 06:54 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 0 | Intersection | On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehicle (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 dedicat…On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehicle (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 directly behind the Waymo AV began moving forward. The front of the passenger car made contact with the rear of the Waymo AV, immediately after which the passenger car left the scene. 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 and the Waymo AV test driver reported lower back pain. 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-3633 | ADS | Waymo LLC | 2022-07 23:23 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 9 | Street | 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 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 Eastern time zone on the required date. | |
| 30270-3635 | ADS | Waymo LLC | 2022-07 02:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 12 | Intersection | 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 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 Eastern time zone on the required date. | |
| 30270-3636 | ADS | Waymo LLC | 2022-07 02:50 | Tempe, AZ | 2017 Chrysler Pacifica | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was st…On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was stopped to pick up a passenger when a passenger vehicle, parked perpendicular and to the right of the Waymo AV, reversed out of a parking spot. The rear of the passenger vehicle made contact with the front passenger side corner of the Waymo AV as the passenger was closing the door on the driver side of the Waymo AV prior to fastening their seat belt. 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 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. | |
| 30330-3482 v2 | ADS | TORC Robotics, Inc. | 2022-07 16:33 | ALBUQUERQUE, NM | 2021 FREIGHTLINER CASCADIA | ADS | Other, see Narrative | No Injuries Reported | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30330-3561 | ADS | TORC Robotics, Inc. | 2022-07 12:39 | Santa Rosa, NM | 2021 FREIGHTLINER CASCADIA | ADS | Other, see Narrative | No Injuries Reported | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30412-3580 | ADS | Cruise LLC | 2022-07 2:57 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-3581 | ADS | Cruise LLC | 2022-07 22:46 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 6 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-3582 | ADS | Cruise LLC | 2022-07 1:39 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 12 | Street | Redacted by NHTSA as confidential business information | |
| 30412-3584 | ADS | Cruise LLC | 2022-07 00:27 | San Francisco, CA | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30531-3342 v2 | ADS | Transdev Alternative Services | 2022-07 9:04 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 13 | Intersection | The content of this report is unchanged from the original report. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on…The content of this report is unchanged from the original report. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode and turning left onto eastbound [XXX]. As the Waymo AV initiated the left turn, a passenger vehicle that had been following the Waymo AV 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 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 and the Waymo AV test driver reported minor injuries. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX]. | |
| 30531-3661 | ADS | Transdev Alternative Services | 2022-07 02:50 | Tempe, AZ | 2017 Chrysler Pacifica | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehice ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was s…On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehice ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was stopped to pick up a passenger when a passenger vehicle, parked perpendicular and to the right of the Waymo AV, reversed out of a parking spot. The rear of the passenger vehicle made contact with the front passenger side corner of the Waymo AV as the passenger was closing the door on the driver side of the Waymo AV prior to fastening their seat belt. 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 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-3636-1. | |
| 30531-3662 | ADS | Transdev Alternative Services | 2022-07 02:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 12 | Intersection | 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-3663 | ADS | Transdev Alternative Services | 2022-07 23:23 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 9 | Street | 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-3664 | ADS | Transdev Alternative Services | 2022-07 06:54 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 0 | Intersection | 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-3665 | ADS | Transdev Alternative Services | 2022-07 10:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Parking 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 v2 | ADS | Zoox, Inc. | 2022-07 14:30 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | 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-3643 | ADS | General Motors, LLC | 2022-07 2:57 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | 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-3644 | ADS | General Motors, LLC | 2022-07 22:46 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 6 | Intersection | 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-3645 | ADS | General Motors, LLC | 2022-07 1:39 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 12 | Street | 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-3647 | ADS | General Motors, LLC | 2022-07 00:27 | San Francisco, CA | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 0 | Street | 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 v2 | ADS | Waymo LLC | 2022-06 12:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking 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-3435 | ADS | Waymo LLC | 2022-06 07:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | 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-3437 | ADS | Waymo LLC | 2022-06 10:07 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | 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-3655 | ADS | Waymo LLC | 2022-06 16:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | Minor | 18 | Intersection | 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. | |
| 30290-3135 v2 | ADS | Argo AI | 2022-06 16:35 | Austin, TX | 2020 Ford Escape | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | 2022-06-[XXX] - Submission of 10 Day Update for Report 30290-3135-1: Argo AI has not received notice of any material new or materially different information about this incident. | |
| 30290-3346 | ADS | Argo AI | 2022-06 14:48 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 30290-3347 | ADS | Argo AI | 2022-06 13:30 | Pittsburgh, PA | 2020 Ford Escape | ADS | SUV | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-3080 v2 | ADS | Cruise LLC | 2022-06 1:54 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Pedestrian | Unknown | 5 | Street | Redacted by NHTSA as confidential business information | |
| 30412-3084 v2 | TMR-0214 | ADS | Cruise LLC | 2022-06 23:00 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-3281 v2 | ADS | Cruise LLC | 2022-06 10:49 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 19 | Street | Redacted by NHTSA as confidential business information | |
| 30531-3256 v2 | ADS | Transdev Alternative Services | 2022-06 12:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking 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-3445 | ADS | Transdev Alternative Services | 2022-06 7:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | 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-3446 | ADS | Transdev Alternative Services | 2022-06 10:07 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | 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-3660 | ADS | Transdev Alternative Services | 2022-06 16:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | Minor | 18 | Intersection | 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-3431 | ADS | Apple Inc. | 2022-06 15:15 | Mountain View, CA | 2016 Lexus RX 450h | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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 v2 | ADS | Zoox, Inc. | 2022-06 13:15 | San Francisco, CA | 2016 Toyota Highlander | ADS | Non-Motorist: Other | Moderate | 12 | Intersection | 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 v2 | ADS | Zoox, Inc. | 2022-06 10:45 | San Mateo, CA | 2016 Toyota Highlander | ADS | SUV | No Injuries Reported | 6 | Street | 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-3320 | ADS | Zoox, Inc. | 2022-06 14:36 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 25 | Street | 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. | |
| 502-3140 v2 | ADS | Ford Motor Company | 2022-06 16:35 | Austin, TX | 2020 Ford Escape | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-3413 | ADS | Ford Motor Company | 2022-06 14:48 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 502-3416 | ADS | Ford Motor Company | 2022-06 13:30 | Pittsburgh, PA | 2020 Ford Escape | ADS | SUV | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 540-3083 v2 | ADS | General Motors, LLC | 2022-06 1:54 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Pedestrian | Unknown | 5 | Street | 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 v2 | ADS | General Motors, LLC | 2022-06 23:00 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | 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 v2 | ADS | General Motors, LLC | 2022-06 10:49 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 19 | Street | 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) | |
| 1306-3355 | ADS | Toyota Motor Engineering & Manufacturing | 2022-05 16:11 | Arlington, TX | 2020 Lexus RX450H | ADS | Pickup Truck | No Injuries Reported | 11 | Street | This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 2022. Toyota has no additional information on this…This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned Monthly Report. Please refer to the report from May Mobility for details. | |
| 30270-2895 v2 | ADS | Waymo LLC | 2022-05 15:11 | Ennis, TX | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | Moderate | 62 | Highway / Freeway | Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-[XXX]-1…Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-[XXX]-1]. On May [XXX], 2022 at 3:11 PM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound Interstate [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the rightmost lane on Interstate [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it encountered tire debris in its lane, executed a right lane change, and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. The Waymo AV exited the roadway to the right shoulder of the road and came to a stop off of the roadway. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained moderate damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. The Waymo AV test driver was transported for medical care and the Waymo AV software operator, seated in the passenger seat, later sought medical attention. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved in the crash was transported from the scene to a hospital for medical treatment and 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-3055 v2 | ADS | Waymo LLC | 2022-05 01:16 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | Motorcycle | No Injuries Reported | 0 | Intersection | 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-3056 v2 | ADS | Waymo LLC | 2022-05 01:43 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | 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:43AM 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:43AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 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 AVs 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 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 undercarriage damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV 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-3057 v2 | ADS | Waymo LLC | 2022-05 02:30 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Unknown | 0 | Intersection | The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-3057-1]. On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Ari…The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-3057-1]. On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] at the [XXX] onramp. While the Waymo AV was stopped at a red light on southbound [XXX] in the rightmost through lane, a passenger vehicle approached the Waymo AV from behind and the right front of the passenger vehicle made contact with the left 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 major damage. The driver of the other vehicle was transported from the scene to a hospital for medical treatment. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away, the crash resulted in airbag deployment, and the driver of the other vehicle was transported from the scene to a hospital for medical treatment. 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-3219 | ADS | Waymo LLC | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | 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-3220 | ADS | Waymo LLC | 2022-05 09:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | 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-3221 | ADS | Waymo LLC | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | 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. | |
| 30290-3119 | ADS | Argo AI | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30410-3043 | ADS | Motional | 2022-05 12:58 | Las Vegas, NV | 2022 Hyundai Ioniq 5 | ADS | Other, see Narrative | No Injuries Reported | 8 | Street | Redacted by NHTSA as confidential business information | |
| 30412-3073 | ADS | Cruise LLC | 2022-05 4:37 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30413-3138 | ADS | May Mobility | 2022-05 16:11 | Arlington, TX | 2020 Lexus RX450H | ADS | Pickup Truck | No Injuries Reported | 11 | Street | The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passe…The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passenger-side mirror to contact the parked vehicle's driver-side mirror. The May vehicle's ground mapping module had fallen significantly behind in its processing of lidar data. As a result, actual objects were being filtered out of the lidar data during object detection. This filtering caused the truck to oscillate between being detected, detecting only the cab, detecting the cab and mirror, and not being detected at all. After assessing the issue, it has been determined that ground map latency alone will not cause safety issues. There is no risk to VRUs, or anything at ground level. The issue was with something in the air (mirror), above the ground. A permanent fix to address the ground map latency issue is in process and will be implemented in the entire fleet within the next 30 days. The second factor in the collision is that we were artificially constraining the vehicle to the right side of the road due to ambiguous and unpainted roadway. If we change that constraint to an advisory line (and allow the vehicle to cross the line to the left), we would have been far enough to the left to avoid collision (simulation success). Solution Implementation: AVO training for extra caution related to protruding items like mirrors (short term), software changes coming in the next update and hotfix (within 30 days), and further improvement in the following update (within 60 days). Until the tested software changes are implemented, we have advised the AVOs to take extra caution in these scenarios and to continue to disengage autonomy when desired. As always, we sacrifice autonomy for safety, as needed. | |
| 30490-3168 | ADS | Beep, Inc. | 2022-05 12:30 | Dunedin, FL | Navya | ADS | Bus | No Injuries Reported | 7 | Intersection | Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Tel…Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Telemetry/Video: Requested and received Vehicle taken out of service: Yes temporary safety hold Photographs: Yes Substantial damage: No damages to report Vehicle placed on safety hold: Yes vehicle has been inspected and available for service Lead Investigator: Chief Safety Officer The Beep shuttle attendant was traveling Southbound on [XXX] at approx 7-12 mph in ADS and headed towards the intersection of [XXX]. Beep vehicle stopped at red light at intersection. As the Beep vehicle was crossing the intersection in manual and slowing to a stop to return to ADS in a southbound direction, the trailing bus made light contact with its bicycle rack to the Beep shuttle rear end. The trailing vehicle is a bus owned and operated by the Pinellas Suncoast Transit Authority (PSTA). According to video, as reported by the shuttle attendant and the PSTA Road Supervisor, the bus was tailgating. Root Cause: Trailing vehicle following too closely and not observing Navya slowing to a stop. | |
| 30531-2902 v2 | ADS | Transdev Alternative Services | 2022-05 15:11 | Ennis, TX | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | Moderate | 62 | Highway / Freeway | Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30531-[XXX]-1…Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30531-[XXX]-1] On May [XXX], 2022 at 3:11 PM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the rightmost lane on Interstate [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it executed a right lane change and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. The Waymo AV exited the roadway to the right shoulder of the road and came to a stop off of the roadway. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained moderate damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. The Waymo AV test driver was transported for medical care and the Waymo AV software operator, seated in the passenger seat, later sought medical attention. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved in the crash was transported from the scene to a hospital for medical treatment and 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-202205[XXX]-0 (rev.202205[XXX]603622) | |
| 30531-3064 v2 | ADS | Transdev Alternative Services | 2022-05 01:16 | San Francisco, CA | 2021 Jaguar I-Pace | Unknown, see Narrative | Motorcycle | No Injuries Reported | 0 | Intersection | 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-3065 v2 | ADS | Transdev Alternative Services | 2022-05 01:43 | Phoenix, AZ | 2021 Jaguar I-Pace | Unknown, see Narrative | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact …The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 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 AVE did not contact any vehicle or road user). At the time of 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 the Waymo AV 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-202205[XXX]-0 (rev.202205[XXX]213041). | |
| 30531-3225 | ADS | Transdev Alternative Services | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | 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-3226 | ADS | Transdev Alternative Services | 2022-05 09:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | 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-3227 | ADS | Transdev Alternative Services | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | 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 v2 | ADS | Zoox, Inc. | 2022-05 13:30 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 25 | Street | 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-3157 | ADS | Pony.ai | 2022-05 15:00 | Irvine, CA | 2021 Hyundai Kona EV | ADS | Passenger Car | No Injuries Reported | 4 | Street | 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. | |
| 502-2973 v2 | ADS | Ford Motor Company | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 540-3123 | ADS | General Motors, LLC | 2022-05 4:37 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | 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 v2 | ADS | Mercedes-Benz USA, LLC | 2022-05 15:05 | Commerce, CA | 2022 Mercedes-Benz S350D | ADS | Heavy Truck | No Injuries Reported | Highway / 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. | ||
| 10003-3210 | ADS | Navistar, Inc. | 2022-04 15:52 | Tucson, AZ | 2021 International LT625 | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | 65 | Highway / Freeway | All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event doe…All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrier. The event occurred as follows: As the truck was being operated on the highway, within its mapped ODD, the driver and test engineer attempted to engage the ADS. However, the ADS was not functional at that moment due to the computer unit not having been initialized, and should not have been attempted to be activated. In short, this was a failed attempt to engage the system as a result of human error. The system has now been modified to prevent the ADS from attempting to engage unless the health of the system is fully functional to prevent human error from repeating this event. When the erroneous attempt to engage occurred, the uninitialized vehicle control unit rotated the steering to the left, causing the truck to veer left. The safety driver took control of the steering, and was able to steer accordingly, but not before the left front truck tire and left front quarter panel came into contact with the concrete barrier to the left of the lanes of travel. | |
| 273-2632 v2 | ADS | Chrysler (FCA US, LLC) | 2022-04 03:30 | Saint Clair, MI | 2022 Jeep Grand Cherokee | ADAS | Other Fixed Object | No Injuries Reported | 50 | Unknown | Redacted by NHTSA as confidential business information | |
| 30270-2610 v2 | ADS | Waymo LLC | 2022-04 02:27 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 20 | Intersection | 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 v2 | ADS | Waymo LLC | 2022-04 19:55 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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-2657 v2 | ADS | Waymo LLC | 2022-04 18:29 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Motorcycle | No Injuries Reported | 3 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was preparing to make a right turn from southbound [XXX] onto westbound [XXX], when it slowed to yield to a pedestrian crossing [XXX]. As the Waymo AV yielded, a motorcycle directly behind the Waymo AV was rear-ended by a pick-up truck. The motorcycle was pushed 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 and the motorcycle sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and a motorcycle was damaged. 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 v2 | ADS | Waymo LLC | 2022-04 14:53 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | Minor | 0 | Intersection | 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 v2 | ADS | Waymo LLC | 2022-04 02:31 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking 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 v2 | ADS | Waymo LLC | 2022-04 16:36 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | 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-3009 | ADS | Waymo LLC | 2022-04 8:14 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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-3010 | ADS | Waymo LLC | 2022-04 23:30 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Animal | No Injuries Reported | 24 | Street | On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode o…On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode on northbound [XXX] and had just passed [XXX] when a cat entered the street from the adjacent right curb. The Waymo AV then made contact with the cat. The Waymo AV braked and the Waymo AV test driver took manual control and brought the Waymo AV to a stop. 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 did not sustain any damage and the cat was found to be deceased; the cat did not have any identification tags or other signs of ownership. 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-3011 | ADS | Waymo LLC | 2022-04 06:37 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 17 | Street | 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. | |
| 30370-2949 | ADS | TuSimple | 2022-04 15:52 | Tucson, AZ | 2021 INTERNATIONAL LT 625 | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | 65 | Highway / Freeway | TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrie…TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrier. The event occurred as follows: As the truck was being operated on the highway, within its mapped ODD, the driver and test engineer attempted to engage the ADS. However, the ADS was not functional at that moment due to the computer unit not having been initialized, and should not have been attempted to be activated. In short, this was a failed attempt to engage the system as a result of human error. The system has now been modified to prevent the ADS from attempting to engage unless the health of the system is fully functional to prevent human error from repeating this event. When the erroneous attempt to engage occurred, the uninitialized vehicle control unit rotated the steering to the left, causing the truck to veer left. The safety driver took control of the steering, and was able to steer accordingly, but not before the left front truck tire and left front quarter panel came into contact with the concrete barrier to the left of the lanes of travel. The contact resulted in a scuff to the left tire and damage to the radar unit extending from the left quarter panel. | |
| 30412-2823 v2 | ADS | Cruise LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-2884 | ADS | Cruise LLC | 2022-04 00:43 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 5 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-2885 | ADS | Cruise LLC | 2022-04 01:55 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-2886 | ADS | Cruise LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 22 | Street | Redacted 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.