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
137 reports, showing 101 to 137.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-5324 | ADS | Waymo LLC | 2023-03 19:00 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 1 | Street | On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] b…On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] behind traffic that was backed up from the intersection with [XXX]. As the Waymo AV was accelerating from a stop, a passenger vehicle approached the Waymo AV 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). The Waymo AV test driver reported having a minor injury and the passenger vehicle left the scene. 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. | |
| 30412-4996 v2 | ADS | Cruise LLC | 2023-03 13:01 | Tempe, AZ | 2023 Cruise AV | ADS | Passenger Car | Minor | 6 | Intersection | Redacted by NHTSA as confidential business information | |
| 30531-5331 | ADS | Transdev Alternative Services | 2023-03 19:00 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 1 | Street | On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX]…On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] behind traffic that was backed up from the intersection with [XXX]. As the Waymo AV was accelerating from a stop, a passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and. a test driver was present (in the driver's seating position). The Waymo AV test driver reported having a minor injury and the passenger vehicle left the scene. 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-5324-1. | |
| 540-5000 v2 | ADS | General Motors, LLC | 2023-03 13:01 | Tempe, AZ | 2023 Cruise AV | ADS | Passenger Car | Minor | 6 | Intersection | On March 20, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufac…On March 20, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day 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-4996-2). | |
| 30610-4810 v2 | ADS | Zoox, Inc. | 2023-02 13:50 | Paradise, NV | 2016 Toyota Highlander | ADS | Non-Motorist: Cyclist | Minor | 0 | Intersection | A Zoox vehicle in autonomy was stopped in a merge lane yielding and waiting for cross traffic when a bicyclist approached the side of the vehicle on a parallel path and made a gesture to the driver. When the Zoox vehicle…A Zoox vehicle in autonomy was stopped in a merge lane yielding and waiting for cross traffic when a bicyclist approached the side of the vehicle on a parallel path and made a gesture to the driver. When the Zoox vehicle began to move and had reached approximately 5mph, the cyclist changed trajectory towards the Zoox vehicle, which braked, and the cyclist made low speed contact with the rear of the Zoox vehicle. The cyclist reported no injury at the scene, but later followed up with an email stating he was sore. Police were not called, contact information was exchanged, and the cyclist rode away. This 10-Day update provides complete information for this incident. | |
| 30412-3748 v3 | ADS | Cruise LLC | 2022-09 18:46 | San Francisco, CA | 2022 Cruise AV | ADS | Motorcycle | Minor | 7 | Street | Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound on [XXX] between [XXX] and [XXX]. At the same time, a motorcyclist approaching from the rear began to merge into t…Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound on [XXX] between [XXX] and [XXX]. At the same time, a motorcyclist approaching from the rear began to merge into the Cruise AV's lane behind the Cruise AV. As the motorcycle approached the AV's rear, the AV braked and the motorcycle subsequently made contact with the Cruise AV's rear passenger side bumper, damaging the motorcycle's front fender. The driver of the motorcycle reported minor injuries and police were not called. | |
| 540-3753 v3 | ADS | General Motors, LLC | 2022-09 18:46 | San Francisco, CA | 2022 Cruise AV | ADS | Motorcycle | Minor | 7 | Street | On September 26, 2024 GM Cruise Holdings LLC ("Cruise") filed an update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manu…On September 26, 2024 GM Cruise Holdings LLC ("Cruise") filed an update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3748-3) | |
| 30412-3806 | ADS | Cruise LLC | 2022-08 03:53 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 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. | |
| 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) | |
| 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-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. | |
| 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-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. | |
| 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. | |
| 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-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. | |
| 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) | |
| 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 | |
| 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) | |
| 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. | |
| 1712-2474 v2 | ADS | Robert Bosch, LLC | 2022-03 08:50 | Los Angeles, CA | EQS 450 4matic | ADS | Unknown | Minor | Parking Lot | Redacted by NHTSA as confidential business information | ||
| 30610-2584 v2 | ADS | Zoox, Inc. | 2022-03 15:00 | San Francisco, CA | 2016 Toyota Highlander | ADS | Non-Motorist: Other | Minor | 2 | Intersection | A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right a…A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right and made contact with the rear corner of the Zoox vehicle at low speed. Police were not called. The Zoox vehicle was in autonomy in the 30 second period prior to contact. | |
| 30610-2651 | ADS | Zoox, Inc. | 2022-03 08:20 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | Minor | 1 | Intersection | A Zoox vehicle in autonomous mode was stopped in traffic when a passenger vehicle from behind made contact with the rear of the Zoox vehicle at low speed. The police were not called. | |
| 855-2464 v2 | ADS | Mercedes-Benz USA, LLC | 2022-03 08:50 | Los Angeles, CA | Mercedes-Benz EQS 450 4Matic | ADS | Other, see Narrative | Minor | 1 | Parking Lot | No additional information to report at this time. | |
| 30290-2180 v2 | ADS | Argo AI | 2022-01 12:22 | Miami, FL | 2020 Ford Escape | ADS | SUV | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-2216 v2 | ADS | Cruise LLC | 2022-01 13:10 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 7 | Street | Redacted by NHTSA as confidential business information | |
| 502-2178 v2 | ADS | Ford Motor Company | 2022-01 12:22 | Miami, FL | 2020 Ford Escape | ADS | SUV | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 540-2220 v2 | ADS | General Motors, LLC | 2022-01 13:10 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 7 | Street | On February [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 Cr…On February [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 alleged 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-2216-2). | |
| 30412-2020 | ADS | Cruise LLC | 2021-11 7:44 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 540-2103 | ADS | General Motors, LLC | 2021-11 7:44 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Street | On January [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 Cr…On January [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 alleged 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-2020-1) | |
| 30270-1410 | ADS | Waymo LLC | 2021-10 15:51 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | Minor | 0 | Intersection | On October [XXX], 2021 at 3:51 PM PDT a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV at [XXX] at [XXX]. The Waymo AV was traveling in autonomous mode w…On October [XXX], 2021 at 3:51 PM PDT a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV at [XXX] at [XXX]. The Waymo AV was traveling in autonomous mode westbound on [XXX] / [XXX] when it stopped for pedestrians who were in a crosswalk and between the westbound and eastbound lanes of [XXX]. An SUV following behind the Waymo AV struck the rear of the Waymo AV. The Waymo AV sustained minor damage to its rear bumper and trunk, and the SUV sustained minor damage to its front bumper and hood. The Waymo AV test driver (in the driver's seating position) later reported lower back pain. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV was stopped for pedestrians when the impact occurred. 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-15 v2 | ADS | Argo AI | 2021-07 09:26 | Washington DC, DC | 2019 Ford Fusion | ADS | Pickup Truck | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-16 v2 | ADS | Cruise LLC | 2021-07 13:15 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Other | Minor | 13 | Street | Redacted by NHTSA as confidential business information | |
| 502-18 v2 | ADS | Ford Motor Company | 2021-07 09:26 | Washington DC, DC | 2019 Ford Fusion | ADS | Pickup Truck | Minor | 0 | 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.