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
443 reports, showing 301 to 400.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 540-5940 | ADS | General Motors, LLC | 2023-06 09:36 | San Francisco, CA | 2022 Cruise AV | ADS | Other, see Narrative | Unknown | 7 | Street | On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5782-1) | |
| 540-5941 | ADS | General Motors, LLC | 2023-06 22:37 | San Francisco, CA | 2022 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5828-1) | |
| 540-5942 | ADS | General Motors, LLC | 2023-06 23:30 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 1 | Street | On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5831-1) | |
| 540-5948 | ADS | General Motors, LLC | 2023-06 00:50 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Street | On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5832-1) | |
| 540-5950 | ADS | General Motors, LLC | 2023-06 23:08 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5833-1) | |
| 540-5951 | ADS | General Motors, LLC | 2023-06 21:04 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5836-1) | |
| 669-5837 | ADS | Hyundai Motor America | 2023-06 21:42 | Las Vegas, NV | 2021 Hyundai IONIQ 5 | ADS | Passenger Car | Minor | 3 | Intersection | On June 23, 2023, Motional informed HMNA's NASO of a crash incident occurring on June [XXX], 2023, at 9:42 PM PDT, involving a Hyundai IONIQ 5 test vehicle operating in proprietary ADS autonomous mode with a safety drive…On June 23, 2023, Motional informed HMNA's NASO of a crash incident occurring on June [XXX], 2023, at 9:42 PM PDT, involving a Hyundai IONIQ 5 test vehicle operating in proprietary ADS autonomous mode with a safety driver at the wheel and a safety operator in the front passenger seat. According to Motional, the test vehicle was travelling northbound in the left-most of two left turn lanes on a local road at approximately 10 mph. The test vehicle then braked for an approaching taxi in the adjacent lane that appeared to be crossing into the Motional test vehicle's lane and was rear-ended by a silver Toyota from behind. The Toyota vehicle fled the scene of the accident. Hyundai understands that the equipment and software used during the test is proprietary to Motional and not used as OEM equipment in any Hyundai/Genesis vehicle produced for sale to the general public. Hyundai currently does not offer an ADS feature on any vehicle offered for sale in the U.S. market. | |
| 30270-5429 v2 | ADS | Waymo LLC | 2023-05 10:32 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 4 | Street | The content of this report is unchanged from the initial report submitted on May 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle (Waymo AV…The content of this report is unchanged from the initial report submitted on May 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the middle lane on westbound [XXX] between [XXX] and [XXX]. A slower traveling van in the left adjacent lane began to initiate a right lane change in front of the Waymo AV, and the Waymo AV test driver transitioned to manual mode and braked. The SUV traveling behind the Waymo AV then made contact with the rear of the Waymo AV. 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 and SUV 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 because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5456 v2 | ADS | Waymo LLC | 2023-05 15:27 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | Other than a correction to the reported mileage, the content of this report is unchanged from the initial report submitted on May 8, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at …Other than a correction to the reported mileage, the content of this report is unchanged from the initial report submitted on May 8, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 3:27 PM PDT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was traveling westbound in the left lane on [XXX] and had just passed [XXX] when it detected an oncoming pickup truck traveling eastbound in the Waymo AVs lane. The Waymo AV stopped and the pickup truck re-entered the correct lane for eastbound traffic and passed the Waymo AV. The pickup truck was immediately followed by a large group of cyclists traveling eastbound in multiple lanes of the roadway, including the right lanes and on the wrong side of the double-yellow centerline. The Waymo AV remained stopped as the oncoming cyclists rode around both sides of the Waymo AV. One cyclist then made contact with the front of the stationary Waymo AV, and then immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user was involved. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5611 | ADS | Waymo LLC | 2023-05 17:54 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 10 | Parking Lot | On May [XXX], 2023 at 5:54 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo A…On May [XXX], 2023 at 5:54 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo AVs undercarriage then made contact with a speed bump (the AV did not contact any vehicle or other road user). At the time of the contact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained undercarriage damage. Waymo is reporting this crash under Request No. 1 of the Second Amended 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. | |
| 30270-5612 | ADS | Waymo LLC | 2023-05 17:34 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 8 | Parking Lot | On May [XXX], 2023 at 5:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo A…On May [XXX], 2023 at 5:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo AVs undercarriage then made contact with a speed bump (the AV did not contact any vehicle or other road user). At the time of the contact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained undercarriage damage. Waymo is reporting this crash under Request No. 1 of the Second Amended 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. | |
| 30270-5756 | ADS | Waymo LLC | 2023-05 13:37 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 32 | Street | On [XXX], 2023 at 1:37 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] at S [XXX]. While traveling eastbound on [XXX], a passenger vehi…On [XXX], 2023 at 1:37 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] at S [XXX]. While traveling eastbound on [XXX], a passenger vehicle in the oncoming lane veered out of their lane and into the eastbound lane. The vehicle made contact with the left rear door of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The other party immediately left the scene without exchanging information. The Waymo AV 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. | |
| 30270-5757 | ADS | Waymo LLC | 2023-05 21:29 | Mesa, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 63 | Highway / Freeway | On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Mesa, Arizona was in a collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right lane…On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Mesa, Arizona was in a collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right lane on a three-lane stretch of the [XXX] when a load of hay bales fell off a truck traveling in the center lane ahead of the Waymo AV. The front left fender of the Waymo AV made contact with a hay bale. 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 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. | |
| 30270-5758 | ADS | Waymo LLC | 2023-05 20:48 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 6 | Street | On[XXX], 2023 at 8:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX}. While traveling west on [XXX}, the Waymo AV was…On[XXX], 2023 at 8:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX}. While traveling west on [XXX}, the Waymo AV was executing a pullover maneuver in autonomous mode and made contact with the left rear bumper of a parked vehicle. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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. | |
| 30270-5759 | ADS | Waymo LLC | 2023-05 23:30 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On [XXX], 2023 at 11:30 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light at the intersect…On [XXX], 2023 at 11:30 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light at the intersection of [XXX] at [XXX]. A passenger vehicle that had been previously stopped behind the Waymo AV proceeded forward, making 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 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. | |
| 30270-5760 | ADS | Waymo LLC | 2023-05 09:42 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On [XXX], 2023 at 09:42 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX], just west of [XXX]. The Waymo AV was traveling westbound on [XXX] whe…On [XXX], 2023 at 09:42 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX], just west of [XXX]. The Waymo AV was traveling westbound on [XXX] when it came to a stop, yielding to a U-Haul box truck that was attempting to reverse into a parking lot to the right of the Waymo AV. The truck exited the lot and re-entered the oncoming eastbound lane, making contact with the left front end of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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. | |
| 30270-5762 | ADS | Waymo LLC | 2023-05 10:56 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Animal | No Injuries Reported | 23 | Street | On [XXX] at 10:56 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small …On [XXX] at 10:56 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog, which did not survive. 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 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. | |
| 30412-5422 v3 | ADS | Cruise LLC | 2023-05 02:44 | San Francisco, CA | 2022 Cruise AV | ADS | Other Fixed Object | Minor | 7 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5430 v2 | ADS | Cruise LLC | 2023-05 09:32 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | Minor | 5 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5624 | ADS | Cruise LLC | 2023-05 21:24 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | Minor | 15 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5697 | ADS | Cruise LLC | 2023-05 03:34 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 9 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5708 | ADS | Cruise LLC | 2023-05 00:35 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5709 | ADS | Cruise LLC | 2023-05 00:35 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 8 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5710 | ADS | Cruise LLC | 2023-05 23:12 | Austin, TX | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5711 | ADS | Cruise LLC | 2023-05 00:14 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30413-5633 | ADS | May Mobility | 2023-05 16:40 | Grand Rapids, MN | 2021 Toyota Sienna | ADS | Non-Motorist: Other | No Injuries Reported | 0 | Intersection | On Tuesday May [XXX] at 16:40 local time, the May shuttle was driving Northbound from [XXX] to [XXX] in Grand Rapids, MN, in autonomous mode and was followed by 2 people riding on scooters. As the May shuttle made the tu…On Tuesday May [XXX] at 16:40 local time, the May shuttle was driving Northbound from [XXX] to [XXX] in Grand Rapids, MN, in autonomous mode and was followed by 2 people riding on scooters. As the May shuttle made the turn, the VRUs were traveling in the same direction as the May shuttle on opposite sides of the lane. As the May shuttle completed the turn at 10 MPH, the brakes were applied and the vehicle came to a complete stop because one of the riders attempted to cross over in the lane which caused VRU safety buffer to intersect with vehicle path, which led the vehicle to slow to a stop. The scooter rider contacted the rear left rear bumper of the shuttle. Scooters were traveling at an estimated speed of 12 mph and accelerating. | |
| 30531-5440 v2 | ADS | Transdev Alternative Services | 2023-05 10:32 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 4 | Street | The content of this report is unchanged from the initial report. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [X…The content of this report is unchanged from the initial report. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was fraveling in autonomous mode in the middle lane on westbound [XXX] between [XXX] and [XXX]. A slower traveling van in the left adjacent lane began to initiate a right lane change in front of the Waymo AV, and the Waymo AV test driver transitioned to manual mode and braked. The SUV 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. The Waymo AV and SUV sustained damage. This is a duplicate of report 30270-5429-1. | |
| 30531-5768 | ADS | Transdev Alternative Services | 2023-05 21:29 | Mesa, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 63 | Highway / Freeway | On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was ina. collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right la…On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was ina. collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right lane on a three-lane stretch of the [XXX] when a load of hay bales fell off a truck traveling in the center lane ahead of the Waymo AV. The front left fender of the Waymo AV made contact with a hay bale. At the time of the impact, the Waymo WV'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 is a duplicate of NHTSA Report ID 30270-5757-1. | |
| 30531-5769 | ADS | Transdev Alternative Services | 2023-05 23:30 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On [XXX] at 11:30 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX] Parkway. The Waymo AV was stopped at a red light at the inter…On [XXX] at 11:30 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX] Parkway. The Waymo AV was stopped at a red light at the intersection of [XXX] at [XXX] Parkway. A passenger vehicle that had been previously stopped behind the Waymo AV proceeded forward, making contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained 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 is a duplicate of NHTSA Report ID: 30270-5759-1. | |
| 30531-5770 | ADS | Transdev Alternative Services | 2023-05 10:56 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Animal | No Injuries Reported | 23 | Street | On [XXX], 2023 at 10:56 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when …On [XXX], 2023 at 10:56 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog, which did not survive. 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 is a duplicate of NHTSA report ID 30270-5762-1. | |
| 30610-5714 | ADS | Zoox, Inc. | 2023-05 10:52 | Paradise, NV | 2016 Toyota Highlander | ADS | Passenger Car | Minor | 0 | Street | A Zoox vehicle in autonomy was stopped in a merge lane, yielding and waiting for cross traffic, when it was rear ended at low speed by a vehicle behind. A Zoox operator reported "slight shoulder pain." Police were not c…A Zoox vehicle in autonomy was stopped in a merge lane, yielding and waiting for cross traffic, when it was rear ended at low speed by a vehicle behind. A Zoox operator reported "slight shoulder pain." Police were not called. | |
| 30610-5716 | ADS | Zoox, Inc. | 2023-05 11:40 | San Francisco, CA | 2017 Toyota Highlander | ADS | SUV | Minor | 1 | Street | A Zoox vehicle in autonomy was coming to a gradual stop for traffic ahead when it was rear ended by vehicle 2 at low speed. There was minor damage to the striking vehicle and police were not called. A Zoox operator repor…A Zoox vehicle in autonomy was coming to a gradual stop for traffic ahead when it was rear ended by vehicle 2 at low speed. There was minor damage to the striking vehicle and police were not called. A Zoox operator reported "sore neck and back". | |
| 30792-5565 | ADS | WeRide Corp | 2023-05 11:41 | San Francisco, CA | 2023 Nissan Leaf | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | On Monday May [XXX] at 11:41am a Weride autonomous vehicle (Vehicle 1) was in Autonomous Mode stopped at the intersection of [XXX] towards [XXX] appropriately yielding to a illegally U turning skateboard on [XXX] North t…On Monday May [XXX] at 11:41am a Weride autonomous vehicle (Vehicle 1) was in Autonomous Mode stopped at the intersection of [XXX] towards [XXX] appropriately yielding to a illegally U turning skateboard on [XXX] North to South direction in front of the AV (Vehicle 1). While yielding, a bicyclist was coming from behind our AV (Vehicle 1) head was turned left possibly looking for cross traffic. When the cyclist turned his head forward, it was too late to react in time to our stopped vehicle(Vehicle 1) with the given distance and speed they were traveling at in which the cyclist collided with our vehicle (Vehicle 1). Our Weride safety officer immediately disengaged and hand signaled to the bicyclist to pull over to the closest safe place to park as to not obstruct traffic. As our safety officer parked and got out of the car to check on the bicyclist, the bicyclist was already on in motion on his bicycle and "fist bumped" our safety officer while passing by him and leaving the scene without exchanging any information. | |
| 540-5425 v3 | ADS | General Motors, LLC | 2023-05 02:44 | San Francisco, CA | 2022 Cruise AV | ADS | Other Fixed Object | Minor | 7 | Intersection | On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Crui…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated 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-5422-3) | |
| 540-5445 v2 | ADS | General Motors, LLC | 2023-05 09:32 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | Minor | 5 | Intersection | On May 10, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured th…On May 10, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated 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-5430-2) | |
| 540-5639 | ADS | General Motors, LLC | 2023-05 21:24 | San Drancisco, CA | 2022 Cruise AV | ADS | Passenger Car | Minor | 15 | Street | On May 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured …On May 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5624-1) | |
| 540-5726 | ADS | General Motors, LLC | 2023-05 03:34 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 9 | Street | On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5697-1) | |
| 540-5729 | ADS | General Motors, LLC | 2023-05 00:35 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5708-1) | |
| 540-5730 | ADS | General Motors, LLC | 2023-05 00:35 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 8 | Street | On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5709-1) | |
| 540-5731 | ADS | General Motors, LLC | 2023-05 23:12 | Austin, TX | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5710-1) | |
| 540-5735 | ADS | General Motors, LLC | 2023-05 00:14 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5711-1) | |
| 30270-5202 v2 | ADS | Waymo LLC | 2023-04 10:46 | 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 6, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle (Waym…The content of this report is unchanged from the initial report submitted on April 6, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:46 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 southbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding south on [XXX] was green for the Waymo AV as it approached the intersection. As the Waymo AV approached, an individual riding a motorized scooter traveling north on [XXX] proceeded to turn left onto westbound [XXX], across the paths of the Waymo AV and other oncoming vehicles. The Waymo AV began to brake, and the Waymo AV test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car traveling directly behind the Waymo AV then made contact with the rear of the Waymo AV. The individual riding the scooter was not contacted by the Waymo AV or any other vehicle. 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. Both the Waymo AV and the passenger car sustained damage, and the individual on the motorized scooter left the scene. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a Vulnerable Road User was involved. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5208 v2 | ADS | Waymo LLC | 2023-04 10:48 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | The content of this report is unchanged from the initial report submitted on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:48 AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:48 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was proceeding northwest on [XXX] near the intersection with [XXX] when it came to a stop to yield to a heavy truck traveling southeast on [XXX]. As the heavy truck drove past the Waymo AV, the drivers side section of the heavy truck made contact with the rear drivers side sensor of the Waymo AV. The heavy truck then left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV 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. | |
| 30270-5584 | ADS | Waymo LLC | 2023-04 22:56 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV ca…On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV came to a stop to yield to an oncoming SUV in a narrow passageway. The SUV proceeded around the Waymo AV and made contact with the left rear sensor housing 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 driver of the SUV stopped briefly but left before sharing their information. The Waymo 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. | |
| 30270-5586 | ADS | Waymo LLC | 2023-04 17:29 | Santa Monica, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in th…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding southwest on [XXX] was red as the Waymo AV approached the intersection and came to a stop. The signal for traffic proceeding southwest on [XXX] then turned green, and traffic in adjacent lanes began moving while the Waymo AV waited for traffic in its lane to begin to move. The SUV that had been stopped directly behind the Waymo AV began moving forward and the front of the SUV 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 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. | |
| 30270-5588 | ADS | Waymo LLC | 2023-04 15:43 | Tempe, AZ | 2017 Chrysler Pacifica | ADS | Passenger Car | No Injuries Reported | 5 | Intersection | On April [XXX], 2023 at 3:43 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the …On April [XXX], 2023 at 3:43 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. After the Waymo AV entered the right-turn lane, a passenger car began to exit from the shopping center driveway to the right of the Waymo AV. The Waymo AV began to brake as the passenger car began to turn in front of the AV onto [XXX]. The passenger car's front bumper made contact with the front right corner of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV did not sustain damage the passenger car 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. | |
| 30270-5591 | ADS | Waymo LLC | 2023-04 8:02 | Phoenix, AZ | 2021 Jaguar I-PACE | ADS | Van | No Injuries Reported | 1 | Intersection | On April [XXX], 2023 at 8:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] in the leftmost…On April [XXX], 2023 at 8:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding north on [XXX] was yellow as the Waymo AV approached the intersection. The Waymo AV slowed, preparing to stop, and a van traveling directly behind the Waymo AV then 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. Both the Waymo AV and the van 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. | |
| 30270-5592 | ADS | Waymo LLC | 2023-04 17:29 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Street | On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] between [XXX…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] between [XXX] and [XXX] when it approached an SUV that was stopped in the lane in front of the Waymo AV. The Waymo AV began passing the stopped SUV on the left when the SUV began reversing in the lane. The Waymo AV then stopped behind and to the left of the SUV, and the SUV continued reversing and began a turning maneuver to enter a parking space. The left side of the SUV made contact with the front right corner of the Waymo AV. At the time of the impact, the Waymo AV was stopped and the AVs Level 4 ADS was engaged in autonomous mode. 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. | |
| 30270-5593 | ADS | Waymo LLC | 2023-04 13:53 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While the Waymo AV was parked at the right side cu…On April [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While the Waymo AV was parked at the right side curb of the road on [XXX], an SUV that was passing the parked Waymo AV in the rightmost lane made contact with the rear drivers side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV did not sustain damage the SUV 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. | |
| 30412-5220 v2 | ADS | Cruise LLC | 2023-04 4:45 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5287 v2 | ADS | Cruise LLC | 2023-04 03:15 | Austin, TX | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5288 v2 | ADS | Cruise LLC | 2023-04 03:15 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 9 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5458 | ADS | Cruise LLC | 2023-04 00:35 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5459 | ADS | Cruise LLC | 2023-04 23:35 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5460 | ADS | Cruise LLC | 2023-04 20:13 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5461 | ADS | Cruise LLC | 2023-04 21:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 4 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5462 | ADS | Cruise LLC | 2023-04 14:58 | Mesa, AZ | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 34 | Street | Redacted by NHTSA as confidential business information | |
| 30413-5396 | ADS | May Mobility | 2023-04 16:16 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | Passenger Car | No Injuries Reported | 18 | Street | On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice a…On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice as fast as the May shuttle and catching up to the May shuttle from behind. The May shuttle began to slow for traffic ahead, which was stopping for a red light, but the following vehicle did not decelerate. While slowing, the May shuttle identified a bollard on the side of the road as a likely pedestrian and added a safety buffer which intersected with the predicted trajectory of the shuttle. This caused the shuttle to increase deceleration to avoid the projected collision with the buffer. The following vehicle started braking late and impacted the May shuttle from behind with a relative velocity of 6.2 m/s. Re-simulation of this event with a future software version shows that the May shuttle would have decelerated less abruptly. | |
| 30531-5205 v2 | ADS | Transdev Alternative Services | 2023-04 10:46 | 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. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenge…The content of this report is unchanged from the initial report. On April [XXX], 2023 at 10:46 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 southbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding south on [XXX] was green for the Waymo AV as it approached the intersection. As the Waymo AV approached, an individual riding a motorized scooter traveling north on [XXX] proceeded to turn left onto westbound [XXX], across the paths of the Waymo AV and other oncoming vehicles. The Waymo AV began to brake, and the Waymo AV test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car traveling directly behind the Waymo AV then made contact with the rear of the Waymo AV. The individual riding the scooter was not contacted by the Waymo AV or any other 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. Both the Waymo AV and the passenger car sustained damage, and the individual on the motorized scooter left the scene. Transdev Alternative Services is reporting this crash under Request No 1 of Standing General Order 2021 01 because a Vulnerable Road User was involved. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30531-5088-1. | |
| 30531-5604 | ADS | Transdev Alternative Services | 2023-04 17:29 | Santa Monica, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in th…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding southwest on [XXX] was red as the Waymo AV approached the intersection and came to a stop. The signal for traffic proceeding southwest on [XXX] then turned green, and traffic in adjacent lanes began moving while the Waymo AV waited for traffic in its lane to begin to move. The SUV that had been stopped directly behind the Waymo AV began moving forward and the front of the SUV 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 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 report ID 30270-5586-1. | |
| 30531-5605 | ADS | Transdev Alternative Services | 2023-04 22:56 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV …On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV came to a stop to yield to an oncoming SUV in a narrow passageway. The SUV proceeded around the Waymo AV and made contact with the left rear sensor housing of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The driver of the SUV stopped briefly but left before sharing their information. The Waymo sustained damage. Transdev Alternative Serivces 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 is a duplicate of report ID 30270-5584-1. | |
| 30610-5232 v2 | ADS | Zoox, Inc. | 2023-04 11:19 | San Francisco, CA | 2017 Toyota Highlander | ADS | Other, see Narrative | No Injuries Reported | 0 | Intersection | A Zoox vehicle in autonomy was proceeding northbound on [XXX] in stop-and-go traffic through an active construction zone. At the same time, an e-scooter traveling near the right curb was passing other slow traffic behind…A Zoox vehicle in autonomy was proceeding northbound on [XXX] in stop-and-go traffic through an active construction zone. At the same time, an e-scooter traveling near the right curb was passing other slow traffic behind the Zoox vehicle. Before the e-scooter could also pass the Zoox vehicle on the right, the e-scooter weaved away from the curb, seemingly to avoid a drainage grate, and came within a close following distance behind the Zoox vehicle. As the Zoox vehicle came to a stop again for traffic ahead the e-scooter rider did not stop, and the e-scooter made contact with the right rear tail light of the Zoox vehicle. The e-scooter rider remained upright, did not stop to exchange information, and immediately rode off while the Zoox vehicle was still stopped. There were no injuries and police were not called. The damage to the Zoox vehicle was limited to a cracked tail light lens. This 10-Day update provides complete information for this incident. | |
| 540-5227 v2 | ADS | General Motors, LLC | 2023-04 4:45 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | On April 18, 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) manufact…On April 18, 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-5220-2) | |
| 540-5296 v2 | ADS | General Motors, LLC | 2023-04 03:15 | Austin, TX | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated 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-5287-2) | |
| 540-5297 v2 | ADS | General Motors, LLC | 2023-04 03:15 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 9 | Street | On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated 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-5288-2) | |
| 540-5488 | ADS | General Motors, LLC | 2023-04 00:35 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | On May 12, 2023, 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 May 12, 2023, 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-5458-1) | |
| 540-5489 | ADS | General Motors, LLC | 2023-04 23:35 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Intersection | On May 12, 2023, 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 May 12, 2023, 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-5459-1) | |
| 540-5490 | ADS | General Motors, LLC | 2023-04 20:13 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On May 12, 2023, 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 May 12, 2023, 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-5460-1) | |
| 540-5491 | ADS | General Motors, LLC | 2023-04 21:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 4 | Intersection | On May 12, 2023, 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 May 12, 2023, 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-5461-1) | |
| 540-5492 | ADS | General Motors, LLC | 2023-04 14:58 | Mesa, AZ | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 34 | Street | On May 12, 2023, 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 May 12, 2023, 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-5462-1) | |
| 669-5206 v3 | ADS | Hyundai Motor America | 2023-04 15:45 | Gahanna, OH | 2023 Hyundai Santa Fe | ADAS | SUV | No Injuries Reported | 70 | Highway / Freeway | A company associate was operating the subject Santa Fe vehicle heading north on the [XXX] with the Highway Drive Assist ("HDA") feature engaged. A Nissan vehicle merged into the subject vehicle's lane and made contact wi…A company associate was operating the subject Santa Fe vehicle heading north on the [XXX] with the Highway Drive Assist ("HDA") feature engaged. A Nissan vehicle merged into the subject vehicle's lane and made contact with the driver's side of the Santa Fe resulting in a crash. The Hyundai vehicle was immobilized requiring towing assistance. No airbags allegedly deployed during the crash. A police report was filed with Gahanna Police Department and the report number is 23GAH.8195.AC. NASO is in process of retrieving the police report. 10-Day Update to 669-5206-1: No new information received. Monthly Update to 669-5206-2: According to the police report, the Santa Fe was travelling in the left lane of the road when the Nissan vehicle attempted a lane change directly into their lane of travel making contact with the Santa Fe's right side. The police report also indicated that no autonomous driving function was engaged in the Santa Fe vehicle at the time of the incident. The operator of the Nissan vehicle was cited for an unspecified charge. | |
| 30270-5114 v2 | ADS | Waymo LLC | 2023-03 20:04 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | Street | The content of this report is unchanged from the initial report submitted on March 21, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On March [XXX], 2023 at approximately 8:04 PM PST a Waymo Autonomous…The content of this report is unchanged from the initial report submitted on March 21, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On March [XXX], 2023 at approximately 8:04 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pothole on [XXX] near [XXX]. The Waymo AV was traveling in the second lane on a four-lane section of northbound [XXX] when the passenger side rear tire made contact with a pothole. The tire began to deflate and the Waymo AV pulled over on a side street. At the time of impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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. | ||
| 30270-5318 | ADS | Waymo LLC | 2023-03 20:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 2 | Parking Lot | On March [XXX], 2023 at 8:27 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco was in a collision involving a fixed object on [XXX] near [XXX]. As the Waymo AV was leaving a parking lot to turn left…On March [XXX], 2023 at 8:27 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco was in a collision involving a fixed object on [XXX] near [XXX]. As the Waymo AV was leaving a parking lot to turn left onto [XXX], the front of the Waymo AV made contact with a chain that was connected between a parking lot road sign and a temporary pole. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The road sign fell down due to tension on the chain. 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. | |
| 30270-5319 | ADS | Waymo LLC | 2023-03 12:03 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On March [XXX], 2023 at 12:03 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling southbound …On March [XXX], 2023 at 12:03 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling southbound on [XXX] when it approached a heavy truck and trailer that was positioning to reverse perpendicularly across [XXX] to back into an adjacent driveway. The Waymo AV stopped and the truck and trailer began reversing across [XXX]. The rear passengers side corner of the truck then made contact with the front drivers side corner of the stationary Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV 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. | |
| 30270-5320 | ADS | Waymo LLC | 2023-03 21:28 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 9:28 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 stopped in the dedicated l…On March [XXX], 2023 at 9:28 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 stopped in the dedicated left turn lane facing west on [XXX], awaiting a green signal to turn onto [XXX]. The signal for traffic proceeding west on [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. 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 passenger car 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. | |
| 30270-5322 | ADS | Waymo LLC | 2023-03 2:19 | San Bruno, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 64 | Highway / Freeway | On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was travelin…On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was traveling south on [XXX] in the rightmost exit lane for [XXX] towards [XXX] when it made contact with road debris (tire scrap). 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 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. | |
| 30270-5323 | ADS | Waymo LLC | 2023-03 17:10 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 8 | Intersection | On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling …On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] in autonomous mode, merging into the rightmost lane. As the Waymo AV merged, the test driver transitioned from autonomous mode to manual mode and began accelerating. The front of the Waymo AV made contact with the rear of a passenger car that was stopped in the rightmost lane. 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. Both the Waymo AV and the passenger car 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. | |
| 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. | |
| 30270-5325 | ADS | Waymo LLC | 2023-03 10:43 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a thre…On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a three-lane road behind a passenger vehicle for a red light facing southwest on [XXX] at [XXX] in autonomous mode. The light turned green while cross-traffic remained backed up in the intersection. The Waymo AV nudged forward and slowed to a stop, yielding for the blocking cross traffic. An SUV that had been stopped behind the Waymo AV proceeded 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 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. | |
| 30270-5326 | ADS | Waymo LLC | 2023-03 13:35 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 2 | Intersection | On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode from…On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode from westbound [XXX] onto northbound [XXX], the Waymo AV was yielding to traffic approaching from the left. As the Waymo AV attempted to proceed, the test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car behind the Waymo AV proceeded forward and made contact with the rear of the Waymo AV. 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 and the passenger vehicle 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. | |
| 30412-4960 v2 | ADS | Cruise LLC | 2023-03 01:06 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information | |
| 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 | |
| 30412-5101 v2 | ADS | Cruise LLC | 2023-03 3:26 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 21 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5136 v2 | ADS | Cruise LLC | 2023-03 04:29 | San Francisco, CA | 2022 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 15 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5140 v2 | ADS | Cruise LLC | 2023-03 14:46 | San Francisco, CA | 2023 Cruise AV | ADS | Bus | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5229 | ADS | Cruise LLC | 2023-03 04:23 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5240 | ADS | Cruise LLC | 2023-03 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5241 | ADS | Cruise LLC | 2023-03 21:49 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5242 | ADS | Cruise LLC | 2023-03 03:20 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 12 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5243 | ADS | Cruise LLC | 2023-03 23:30 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30530-5289 | ADS | Aurora Operations, Inc. | 2023-03 08:01 | Weatherford, TX | 2022 Peterbilt 579m | ADS | Passenger Car | No Injuries Reported | 65 | Highway / Freeway | At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicl…At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicle encroaching on the lane. This vehicle continued to veer toward Aurora's truck at over 65 miles per hour, causing a collision. Aurora disengaged autonomy before impact and pulled to the shoulder along with the involved vehicle. Both vehicles were able to be driven from the scene, and there were no reported injuries. | |
| 30531-5328 v2 | ADS | Transdev Alternative Services | 2023-03 21:28 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 9:28 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 stopped in the dedicated…On March [XXX], 2023 at 9:28 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 stopped in the dedicated left turn lane facing west on [XXX], awaiting a green signal to turn onto [XXX]. The signal for traffic proceeding west on [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. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was prest (in the driver's seat). Transdev Alternative Services is reporting this crash under Request no. 2 of Standing Gneral Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of 30270-5320-1. | |
| 30531-5329 v2 | ADS | Transdev Alternative Services | 2023-03 2:19 | San Bruno, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 64 | Highway / Freeway | On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was travel…On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was traveling south on [XXX] in the rightmost exit lane for [XXX] towards [XXX] when it made contact with road debris (tire scrap). 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 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of 30270-5322-1. | |
| 30531-5330 v2 | ADS | Transdev Alternative Services | 2023-03 17:10 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 8 | Intersection | On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling…On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] in autonomous mode, merging into the rightmost lane. As the Waymo AV merged, the test driver transitioned from autonomous mode to manual mode and began accelerating. The front of the Waymo AV made contact with the rear of a passenger car that was stopped in the rightmost lane. At the time of the impact, the Waymo's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both the Waymo AV and the passenger car 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 is a duplicate of 30270-5323-1. | |
| 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. | |
| 30531-5335 | ADS | Transdev Alternative Services | 2023-03 10:43 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a th…On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a three-lane road behind a passenger vehicle for a red light facing southwest on [XXX] at [XXX] in autonomous mode. The light turned green while cross-traffic remained backed up in the intersection. The Waymo AV nudged forward and slowed to a stop, yielding for the blocking cross traffic. An SUV that had been stopped behind the Waymo AV proceeded 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 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 is a duplicate of 30270-5325-1. | |
| 30531-5336 | ADS | Transdev Alternative Services | 2023-03 13:35 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 2 | Intersection | On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode fr…On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode from westbound [XXX] onto northbound [XXX], the Waymo AV was yielding to traffic approaching from the left. As the Waymo AV attempted to proceed, the test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car behind the Waymo AV proceeded 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 not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV and the passenger vehicle 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 is a duplicate of 30270-5326-1. | |
| 30610-5224 | ADS | Zoox, Inc. | 2023-03 22:45 | Paradise, NV | 2016 Toyota Highlander | ADS | Other Fixed Object | No Injuries Reported | 4 | Street | A Zoox vehicle in autonomous mode was traveling northbound on an access road towards [XXX] in Las Vegas, Nevada, when the driver disengaged for a vehicle in the oncoming lane rounding a tight curve. Approximately eleven …A Zoox vehicle in autonomous mode was traveling northbound on an access road towards [XXX] in Las Vegas, Nevada, when the driver disengaged for a vehicle in the oncoming lane rounding a tight curve. Approximately eleven seconds after disengaging, the driver proceeded in manual mode making a right turn and struck the curb at low speed. There were no injuries and police were not called. | |
| 30610-5225 v2 | ADS | Zoox, Inc. | 2023-03 14:40 | Paradise, NV | 2016 Toyota Highlander | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | A Zoox vehicle in autonomous mode was stopped in a merge lane from northbound [XXX] onto [XXX] yielding and waiting for cross traffic. As it began to creep forward, it again came to a stop and it was struck by the vehicl…A Zoox vehicle in autonomous mode was stopped in a merge lane from northbound [XXX] onto [XXX] yielding and waiting for cross traffic. As it began to creep forward, it again came to a stop and it was struck by the vehicle behind at low speed. There were no injuries and police were not called. This report was updated to change the mileage section to "Highlander". | |
| 540-4965 v2 | ADS | General Motors, LLC | 2023-03 01:06 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | On March 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On March 15, 2023, 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-4960-2) |
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.