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
8612 reports, showing 6601 to 6700.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-6514 | ADS | Waymo LLC | 2023-09 22:48 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Bus | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 10:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was stopped on the right lane of a m…On September [XXX], 2023 at 10:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was stopped on the right lane of a multi-lane road when a city bus attempted to pass using the adjacent left lane. The rear right fender of the bus made contact with the left rear sensor 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-6515 | ADS | Waymo LLC | 2023-09 19:41 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 7:41 PM PT 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 parked facing north on …On September [XXX], 2023 at 7:41 PM PT 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 parked facing north on [XXX] when a passenger vehicle that was parked on the opposite side of the street started reversing, and reversed into the left rear bumper 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-6516 | ADS | Waymo LLC | 2023-09 15:07 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Street | On September [XXX], 2023 at 3:07 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] when the…On September [XXX], 2023 at 3:07 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] when the Waymo AV slowed for stopped traffic ahead. The vehicle immediately behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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-6517 | ADS | Waymo LLC | 2023-09 09:24 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a truck on [XXX] an [XXX]. The Waymo AV had pulled over to the curb and par…On September [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a truck on [XXX] an [XXX]. The Waymo AV had pulled over to the curb and parked on the right side of [XXX] when a truck directly in front of the Waymo AV reversed and made contact with the front of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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-6518 | ADS | Waymo LLC | 2023-09 20:20 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 8:20 PM PT 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 parked on the right sid…On September [XXX], 2023 at 8:20 PM PT 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 parked on the right side on [XXX] when a passenger vehicle that had been previously parked in the driveway on the opposite side of the street began reversing and reversed into 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 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-6519 | ADS | Waymo LLC | 2023-09 19:49 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 7:49 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a food truck trailer on [XXX] at [XXX]. The Waymo AV stopped facing north on [XXX] a…On September [XXX], 2023 at 7:49 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a food truck trailer on [XXX] at [XXX]. The Waymo AV stopped facing north on [XXX] after a pickup truck hauling a food truck trailer ahead of the Waymo AV came to a stop. The pickup truck and food truck trailer then began to reverse into the stationary Waymo AV and the left rear bumper of the food truck trailer made contact with the front bumper 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-6520 | ADS | Waymo LLC | 2023-09 01:40 | Scottsdale, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | On September [XXX], 2023 at 1:40 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, California was in a collision involving a passenger car in a parking lot on [XXX] at [XXX]. The Waymo AV was stopped i…On September [XXX], 2023 at 1:40 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, California was in a collision involving a passenger car in a parking lot on [XXX] at [XXX]. The Waymo AV was stopped in a parking lot when a vehicle exiting a row of parked cars attempted to pass through a narrow space behind the rear of the Waymo AV. The front left bumper of the passenger car made contact with the right rear sensor of the 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-6521 | ADS | Waymo LLC | 2023-09 10:25 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 10:25 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a cargo trailer on [XXX] at [XXX]. The Waymo AV was traveling south on [XXX] when a…On September [XXX], 2023 at 10:25 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a cargo trailer on [XXX] at [XXX]. The Waymo AV was traveling south on [XXX] when a pickup truck hauling a cargo trailer immediately ahead of the Waymo AV stopped and began to reverse. The Waymo AV came to a stop and the rear of the cargo trailer made contact with the front bumper 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-6522 v2 | ADS | Waymo LLC | 2023-09 21:00 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was…On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was proceeding south on [XXX] in the leftmost lane and entered the slip lane to proceed north on [XXX]. As the Waymo AV came to a stop for a red light at the intersection with [XXX], the front of the passenger car which was following behind the Waymo AV made contact with the rear of the Waymo AV. The Waymo AV sustained damage. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. The previously submitted version of this report incorrectly listed the wrong zip code, and "September 20th" was noted as the date of this event in the narrative. This updated submission has been corrected to reflect the correct zip code and date. |
| 30412-6242 | ADS | Cruise LLC | 2023-09 21:42 | Houston, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information |
| 30412-6262 | ADS | Cruise LLC | 2023-09 02:35 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 2 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6363 | ADS | Cruise LLC | 2023-09 03:49 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6371 | ADS | Cruise LLC | 2023-09 20:14 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 16 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6384 | ADS | Cruise LLC | 2023-09 09:20 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 8 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6436 | ADS | Cruise LLC | 2023-09 22:16 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-6437 | ADS | Cruise LLC | 2023-09 23:02 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information |
| 30412-6438 | ADS | Cruise LLC | 2023-09 17:32 | San Francisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-6439 v2 | ADS | Cruise LLC | 2023-09 00:05 | Tempe, AZ | 2022 Cruise AV | ADS | Animal | No Injuries Reported | 15 | Street | Redacted by NHTSA as confidential business information |
| 30412-6440 | ADS | Cruise LLC | 2023-09 04:59 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information |
| 30412-6441 | ADS | Cruise LLC | 2023-09 10:54 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-6442 | ADS | Cruise LLC | 2023-09 23:56 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 10 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6444 | ADS | Cruise LLC | 2023-09 23:44 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 25 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6445 v2 | ADS | Cruise LLC | 2023-09 22:36 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 24 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6446 | ADS | Cruise LLC | 2023-09 09:37 | San Francisco, CA | 2020 Cruise AV | ADS | Van | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information |
| 30412-6447 | ADS | Cruise LLC | 2023-09 08:42 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information |
| 30531-6354 | ADS | Transdev Alternative Services | 2023-09 20:34 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the rig…On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the right lane on northbound [XXX], an SUV that was passing the parked Waymo AV made contact with the rear driver's side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vechile involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30270-6351-1. |
| 30531-6533 | ADS | Transdev Alternative Services | 2023-09 21:00 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was…On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was proceeding south on [XXX] in the leftmost lane and entered the slip lane to proceed north on [XXX]. As the Waymo AV came to a stop for a red light at the intersection with [XXX], the front of the passenger car which was following behind the Waymo AV made contact with the rear of the Waymo AV. The Waymo AV sustained damage. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present. Transdev Alternative Services is reporting this crash under Request No 2 of Standing General Order 2021-01. This is a duplicate of report ID 30270-6522-1. |
| 30590-6382 | ADS | Apple Inc. | 2023-09 11:33 | Emeryville, CA | 2017 Lexus RX 450h | ADS | Pickup Truck | No Injuries Reported | 0 | Highway / Freeway | Subject vehicle was on a testing mission in Emeryville, CA. The vehicle was traveling Westbound on [XXX] operated by the vehicle's Automated Driving System and supervised by a safety driver in the driver's designated sea…Subject vehicle was on a testing mission in Emeryville, CA. The vehicle was traveling Westbound on [XXX] operated by the vehicle's Automated Driving System and supervised by a safety driver in the driver's designated seating position, and with a safety operator in the front passenger seating position. Subject vehicle decelerated and came to a complete stop in response to traffic. Approximately three seconds later, with traffic remaining stopped ahead, a white Chevrolet Silverado made contact from the rear. Almost simultaneous with the crash, the safety driver disengaged the Automated Driving System through brake pedal force. After the crash, both vehicles proceeded to the side of the road to exchange information, and then took the closest exit to a nearby parking lot. Subject vehicle was towed given damage to the rear window. No injuries were reported, and law enforcement was not called to the scene. In addition to telematics and video, we have photographs of the damaged vehicles. |
| 30610-6373 | ADS | Zoox, Inc. | 2023-09 15:20 | San Francisco, CA | 2017 Toyota Highlander | ADS | Van | No Injuries Reported | 0 | Street | A Zoox vehicle in autonomy was slowing to a gradual stop on eastbound [XXX] for a red light at [XXX] when it was rear-ended by vehicle 2 at approximately 10 mph. There was minor damage, no reported injuries, and police w…A Zoox vehicle in autonomy was slowing to a gradual stop on eastbound [XXX] for a red light at [XXX] when it was rear-ended by vehicle 2 at approximately 10 mph. There was minor damage, no reported injuries, and police were not called. |
| 30711-6431 | ADS | Pony.ai | 2023-09 17:02 | Milpitas, CA | 2019 Lincoln MKZ | ADS | Other, see Narrative | No Injuries Reported | 58 | Highway / Freeway | On September [XXX], 2023, preparing to enter the [XXX] while traveling northbound on the [XXX] in Milpitas, California, a Pony.ai autonomous vehicle ("AV") collided with road debris while operating in supervised autonomo…On September [XXX], 2023, preparing to enter the [XXX] while traveling northbound on the [XXX] in Milpitas, California, a Pony.ai autonomous vehicle ("AV") collided with road debris while operating in supervised autonomous ("Drivered") mode. Immediately prior to the incident, the AV safety driver noticed a flat item in the center part of the AV's lane of travel. The AV safety driver disengaged from autonomous mode and attempted to dodge the debris. However, the debris made contact with the rear bumper, slightly damaging it. Following the collision, the AV safety driver promptly drove the AV to Pony.ai's Fremont facility. There were no injuries reported. |
| 30792-6492 | ADS | WeRide Corp | 2023-09 13:54 | San Francisco, CA | 2023 Nissan Leaf | ADS | SUV | No Injuries Reported | 0 | Street | At 1:54pm, a WeRide vehicle (Car 1) was stopped on [XXX] left turning lane to [XXX]. As our vehicle (Car 1) was stopped for red traffic light, the toyota suv (Car 2) approaching from behind collided with our vehicle (Car…At 1:54pm, a WeRide vehicle (Car 1) was stopped on [XXX] left turning lane to [XXX]. As our vehicle (Car 1) was stopped for red traffic light, the toyota suv (Car 2) approaching from behind collided with our vehicle (Car 1). Both parties pulled over both involved vehicles and cooperated to exchange information. The damage sustained to the WeRide vehicle (Car 1) and toyota suv (Car 2) are minor. |
| 33495-6725 | ADS | Apollo Autonomous Driving USA | 2023-09 12:25 | San Francisco, CA | 2017 Lincoln MKZ Hybrid | Unknown, see Narrative | SUV | No Injuries Reported | 5 | Street | An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in autonomous mode and stopped for a double-parked vehicle near [XXX]. An Apollo safety operator disengaged the AV from autonomous mod…An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in autonomous mode and stopped for a double-parked vehicle near [XXX]. An Apollo safety operator disengaged the AV from autonomous mode into conventional mode with use of the steering wheel. Then the AV side-swiped the double-parked vehicle while in conventional mode. There were no injuries, and emergency services were not needed. Both the AV and the second vehicle sustained minor damage. |
| 502-6362 | Level 2 | Ford Motor Company | 2023-09 09:30 | Westland, MI | 2021 Ford F-150 | ADAS | SUV | No Injuries Reported | 40 | Street | Redacted by NHTSA as confidential business information |
| 502-6643 | Level 2 | Ford Motor Company | 2023-09 | Lincoln, CA | 2022 Ford F-150 | ADAS | Passenger Car | No Injuries Reported | 10 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 540-6244 | ADS | General Motors, LLC | 2023-09 21:42 | Houston, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Street | On September 12, 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) manufact…On September 12, 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-6242-1). |
| 540-6290 | ADS | General Motors, LLC | 2023-09 02:35 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 2 | Intersection | On September 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) manufact…On September 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-6262-1) |
| 540-6349 | Level 2 | General Motors, LLC | 2023-09 11:32 | Napier Township, PA | 2023 Chevrolet Bolt EUV | ADAS | Other Fixed Object | No Injuries Reported | 69 | Highway / Freeway | At 11:32:24 am a Chevrolet Bolt EUV was traveling East on [XXX] in Napier, Pennsylvania. The vehicle struck the left-hand highway cement barrier. Air bags did not deploy at that time. The vehicle proceeded to careen …At 11:32:24 am a Chevrolet Bolt EUV was traveling East on [XXX] in Napier, Pennsylvania. The vehicle struck the left-hand highway cement barrier. Air bags did not deploy at that time. The vehicle proceeded to careen to the right, rolled over and landed on the right side shoulder of the highway. The side air bags deployed. Crash data indicates that Super Cruise was last active approximately 14 seconds prior to the crash. At that time, steering wheel input caused an override of the Super Cruise system. The crash occurred at 11:32:38. A pre-crash speed of 69 mph was the last vehicle speed recorded, approximately 14 seconds prior to the crash. |
| 540-6369 | ADS | General Motors, LLC | 2023-09 03:49 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 3 | Intersection | On September 22, 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) manufact…On September 22, 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-6363-1) |
| 540-6372 | ADS | General Motors, LLC | 2023-09 20:14 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 16 | Intersection | On September 28, 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) manufact…On September 28, 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-6371-1) |
| 540-6393 | ADS | General Motors, LLC | 2023-09 09:20 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 8 | Intersection | On October 2, 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) manufacture…On October 2, 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-6384-1). |
| 540-6451 | ADS | General Motors, LLC | 2023-09 22:16 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On October 12, 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…On October 12, 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-6436-1) |
| 540-6452 | ADS | General Motors, LLC | 2023-09 23:02 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | On October 12, 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) manufactur…On October 12, 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-6437-1) |
| 540-6453 | ADS | General Motors, LLC | 2023-09 17:32 | San Francisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On .October 12, 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) manufactu…On .October 12, 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-6438-1) |
| 540-6454 v2 | ADS | General Motors, LLC | 2023-09 00:05 | Tempe, AZ | 2022 Cruise AV | ADS | Animal | No Injuries Reported | 15 | Street | On October 16, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) ma…On October 16, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated 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-6439-2). |
| 540-6455 | ADS | General Motors, LLC | 2023-09 04:59 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 1 | Street | On October 12, 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) manufactur…On October 12, 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-6440-1). |
| 540-6461 | ADS | General Motors, LLC | 2023-09 10:54 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On October 12, 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) manufactur…On October 12, 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-6441-1). |
| 540-6462 | ADS | General Motors, LLC | 2023-09 23:56 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 10 | Intersection | On October 12, 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) manufactur…On October 12, 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-6442-1). |
| 540-6467 | ADS | General Motors, LLC | 2023-09 23:44 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 25 | Intersection | On October 12, 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) manufactur…On October 12, 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-6444-1). |
| 540-6468 v2 | ADS | General Motors, LLC | 2023-09 22:36 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 24 | Intersection | On November 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) m…On November 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated 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-6445-2) |
| 540-6470 | ADS | General Motors, LLC | 2023-09 09:37 | San Francisco, CA | 2020 Cruise 8AV | ADS | Van | No Injuries Reported | 10 | Street | On October 12, 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) manufactur…On October 12, 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-6446-1). |
| 540-6472 | ADS | General Motors, LLC | 2023-09 08:42 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | On October 12, 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) manufactur…On October 12, 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-6447-1) |
| 540-6486 v2 | Level 2 | General Motors, LLC | 2023-09 05:20 | San Bernardino, CA | 2023 Chevrolet Bolt EUV | ADAS | Other Fixed Object | Minor | 70 | Highway / Freeway | At 5:19:58 AM, a Chevrolet Bolt EUV was traveling west on [XXX] in San Bernardino, California. The vehicle struck the left hand guard rail. Airbags did not deploy. The last recorded ADAS telematic data indicates that …At 5:19:58 AM, a Chevrolet Bolt EUV was traveling west on [XXX] in San Bernardino, California. The vehicle struck the left hand guard rail. Airbags did not deploy. The last recorded ADAS telematic data indicates that Super Cruise was active approximately 43 seconds prior to crash. The crash occurred at 5:20:41 AM. A pre-crash speed of 70 mph was the last vehicle speed recorded, approximately, 43 seconds prior to the crash. A police report obtained on October 13, 2023 indicated that the driver was transported to a hospital. |
| 62-11740 | Level 2 | Honda (American Honda Motor Co.) | 2023-09 | TX | 2022 HONDA Pilot | Alleged Engaged | Passenger Car | Minor W/ Hospitalization | 65 | Highway / Freeway | Customer called in to report an accident she was involved in on [XXX]. She stated that she was driving on the highway with the ACC and LKAS on and another vehicle cut her off and she rear ended them. Customer sustained i…Customer called in to report an accident she was involved in on [XXX]. She stated that she was driving on the highway with the ACC and LKAS on and another vehicle cut her off and she rear ended them. Customer sustained injuries to her knees as they jammed into the dashboard. She got an abrasion on her left knee and 8 stitches on her right knee. The front steering wheel airbag deployed. Customer advised that the vehicle will likely be deemed a total loss and shared that she is financing the vehicle. NOTE: We recently let NHTSA's Office of Chief Council know about this past incident from 2023. |
| 1306-6035 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2023-08 08:00 | Albian, MI | 2021 Toyota Venza Hybrid | ADAS | Other Fixed Object | No Injuries Reported | 85 | Highway / Freeway | Entries in this report are based on unconfirmed allegations. On August 9, 2023, Toyota received an allegation related to this crash from the vehicle owner and mother of the driver who was operating the vehicle during the…Entries in this report are based on unconfirmed allegations. On August 9, 2023, Toyota received an allegation related to this crash from the vehicle owner and mother of the driver who was operating the vehicle during the crash event. On August 10, 2023, through additional contact with the driver of the vehicle, Toyota was notified that the crash resulted in the vehicle being towed from the scene. The contact record indicates that driver alleged the following: the driver alleged that, "the lane assist malfunctioned while cruise control was on." The driver stated he was driving on [XXX] (direction unknown) with the "adaptive cruise control and lane assist turned on". He stated that he, "had two hands on the wheel and had a secure grip, when he saw a light on the dashboard for the lane assist and the vehicle just veered to the left." He, "attempted to correct the direction but ended up fishtailing and losing control, ultimately hitting a cable barrier that was on the left" He stated that the cable barrier protected him from going into oncoming traffic, but it damaged the entire left side and front of the vehicle. He also stated that none of the airbags deployed and he was not injured. The police responded, and he had the car towed from the scene to a body shop. On September 11, 2023 Toyota completed a field report for a vehicle inspection related to the incident, and EDR, Vehicle Control History (VCH), and PCS Freeze Frame Data (PCS FFD) were recovered from the vehicle. The PCS FFD has an approximately 8 second pre-crash data recording. From the PCS FFD, Toyota observed that Lane Trace Assist (LTA) was engaged until approximately 8 seconds before the crash event, and Dynamic Radar Cruise Control (DRCC) was engaged until approximately 2 seconds before the crash event. The LTA (ADAS L2) disengagement was due to lack of driver input. Specifically, the TSS system detected no "driver steering wheel hold" for a certain amount of time, and suspended the operation after multiple driver visual and audible alerts. After the LTA suspension, at approximately 3 seconds prior to the crash event, the driver steered the vehicle left at approximately 27 degrees, veering off the road. The Vehicle Stability Control System activated at approximately 2.5 seconds prior to the crash event, which disengaged DRCC. The police report from the Calhoun County Sheriff's department is 23003098. |
| 1306-6164 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2023-08 16:42 | Northridge, CA | 2023 Toyota Corolla Hybrid | ADAS | Other Fixed Object | Unknown | 65 | Highway / Freeway | On August [XXX], 2023, Toyota received an allegation related to this crash from the vehicle owner. The owner alleged that her son was driving with his girlfriend at the time of the accident. She stated they were on the […On August [XXX], 2023, Toyota received an allegation related to this crash from the vehicle owner. The owner alleged that her son was driving with his girlfriend at the time of the accident. She stated they were on the [XXX] in Northridge, CA in the far left lane. Additionally, she stated that, "He had turned on the cruise control setting and set it at 70 MPH. He had been cruising for about 10 minutes when all of a sudden, the vehicle veered to the left and hit the center divider." The owner stated that all the airbags deployed except for the driver's airbag. The police responded, but the customer did not have details related to the law enforcement entity or whether a report was created. The driver and passenger sustained injuries described as (Driver): bruised knee and left foot injury, (Passenger): Bruising from seatbelt. ADAS Level 2 driving status was not reported by the owner. On August 18, 2023, Toyota completed a vehicle inspection with field report for the crash event and obtained the Vehicle Control History (VCH) indicating that ADAS L2 was engaged in the recorded moments prior to the crash. The VCH recording contains approximately 8 seconds of pre-crash data and images. From the VCH, Toyota observed the following: The vehicle was travelling in the center of 3 lanes before drifting left and contacting the concrete highway divider. Dynamic Radar Cruise Control (DRCC) was engaged from the start of the recording until the crash occurred. Lane Trace Assist (LTA) was engaged approximately 3.6 seconds prior to the crash event at which point it disengaged due to driver steering input. The field report shows that both Curtain Shield Airbags and the Driver Side Airbag were deployed. |
| 13781-10803 v2 | Level 2 | Tesla, Inc. | 2023-08 | Surprise, AZ | 2017 Tesla Model S | Unknown, see Narrative | Unknown | Serious | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-6046 v2 | Level 2 | Tesla, Inc. | 2023-08 | Allenhurst, NJ | 2016 TESLA Model X | Verified Engaged | Other Fixed Object | Serious W/O Hospitalization | 34 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6048 | Level 2 | Tesla, Inc. | 2023-08 09:07 | Los Angeles, CA | 2023 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 48 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6049 | Level 2 | Tesla, Inc. | 2023-08 09:43 | Seattle, WA | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6141 | Level 2 | Tesla, Inc. | 2023-08 14:29 | Brea, CA | 2023 Tesla Model Y | ADAS | Pickup Truck | Unknown | 1 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6142 | Level 2 | Tesla, Inc. | 2023-08 09:40 | San Mateo, CA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 72 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6143 | Level 2 | Tesla, Inc. | 2023-08 09:51 | Edgemont, CA | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 72 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6154 | Level 2 | Tesla, Inc. | 2023-08 18:09 | San Diego, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 52 | Street | Redacted by NHTSA as confidential business information |
| 13781-6155 | Level 2 | Tesla, Inc. | 2023-08 21:00 | Independence, MO | 2021 Tesla Model Y | ADAS | Pickup Truck | Unknown | 73 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6156 | Level 2 | Tesla, Inc. | 2023-08 16:51 | Houston, TX | 2021 Tesla Model 3 | ADAS | SUV | Unknown | 27 | Street | Redacted by NHTSA as confidential business information |
| 13781-6157 | Level 2 | Tesla, Inc. | 2023-08 03:19 | Phoenix, AZ | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 34 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6169 | Level 2 | Tesla, Inc. | 2023-08 11:38 | Detroit, MI | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 59 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6170 | Level 2 | Tesla, Inc. | 2023-08 12:11 | Newark, DE | 2019 Tesla Model 3 | ADAS | Heavy Truck | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6171 | Level 2 | Tesla, Inc. | 2023-08 22:06 | Ocean Township, NJ | 2021 Tesla Model Y | ADAS | Passenger Car | Unknown | 26 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6183 | Level 2 | Tesla, Inc. | 2023-08 01:18 | Burbank, CA | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 54 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6184 | Level 2 | Tesla, Inc. | 2023-08 15:04 | Concord, NH | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 40 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6185 | Level 2 | Tesla, Inc. | 2023-08 09:01 | Los Angeles, CA | 2023 Tesla Model Y | ADAS | Passenger Car | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6186 | Level 2 | Tesla, Inc. | 2023-08 04:20 | Golden Glades, FL | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6187 | Level 2 | Tesla, Inc. | 2023-08 17:26 | Mission Viejo, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6194 | Level 2 | Tesla, Inc. | 2023-08 01:45 | Lowhill Township, PA | 2020 Tesla Model 3 | ADAS | Passenger Car | Unknown | 41 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6195 | Level 2 | Tesla, Inc. | 2023-08 19:27 | DeSoto, TX | 2021 Tesla Model S | ADAS | Unknown | Unknown | 81 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6196 | Level 2 | Tesla, Inc. | 2023-08 07:13 | Los Angeles, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6197 | Level 2 | Tesla, Inc. | 2023-08 | Milpitas, CA | 2021 Tesla Model X | ADAS | SUV | Unknown | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6205 | Level 2 | Tesla, Inc. | 2023-08 13:54 | Green Cove Springs, FL | 2023 Tesla Model Y | ADAS | Motorcycle | Unknown | 12 | Street | Redacted by NHTSA as confidential business information |
| 13781-6206 | Level 2 | Tesla, Inc. | 2023-08 20:32 | College Park, GA | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 66 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6207 | Level 2 | Tesla, Inc. | 2023-08 11:02 | Brentwood, CA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 58 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6208 | Level 2 | Tesla, Inc. | 2023-08 23:51 | Sandy Springs, GA | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6212 | Level 2 | Tesla, Inc. | 2023-08 12:06 | Stone Park, IL | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 63 | Street | Redacted by NHTSA as confidential business information |
| 13781-6213 | Level 2 | Tesla, Inc. | 2023-08 11:50 | Hixton, WI | 2020 Tesla Model 3 | ADAS | Animal | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6224 | Level 2 | Tesla, Inc. | 2023-08 11:51 | San Antonio, TX | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 76 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6225 | Level 2 | Tesla, Inc. | 2023-08 10:37 | Midland, TX | 2019 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 50 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-8045 v2 | Level 2 | Tesla, Inc. | 2023-08 | Ponte Verda Beach, FL | 2023 Tesla Model 3 | ADAS | Unknown | Fatality | 54 | Street | Redacted by NHTSA as confidential business information |
| 13781-8295 v3 | Level 2 | Tesla, Inc. | 2023-08 12:32 | San Ramon, CA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Serious | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9715 | Level 2 | Tesla, Inc. | 2023-08 16:48 | Mesquite, TX | 2023 Tesla Model 3 | ADAS | Passenger Car | Unknown | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9818 | Level 2 | Tesla, Inc. | 2023-08 07:47 | Bunkerville, NV | 2017 Tesla Model X | ADAS | Other, see Narrative | Unknown | 47 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9827 | Level 2 | Tesla, Inc. | 2023-08 15:22 | Hialeah Gardens, FL | 2023 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 33 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9829 | Level 2 | Tesla, Inc. | 2023-08 23:18 | Braintree, MA | 2023 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 62 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9830 | Level 2 | Tesla, Inc. | 2023-08 20:59 | Pomona, CA | 2022 Tesla Model 3 | ADAS | Heavy Truck | Unknown | 73 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9831 | Level 2 | Tesla, Inc. | 2023-08 15:32 | Dedham, MA | 2023 Tesla Model Y | ADAS | Heavy Truck | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30270-6149 v2 | ADS | Waymo LLC | 2023-08 21:37 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Unknown | 0 | Intersection | The content of this report is unchanged from the initial report submitted on August 18, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2023 at 9:37 PM PT a Waymo Autonomous Vehicle (Way…The content of this report is unchanged from the initial report submitted on August 18, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2023 at 9:37 PM PT 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 stopped in traffic at a red light for a pedestrian crosswalk, facing westbound on [XXX]. A passenger vehicle behind the Waymo AV approached 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. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-6150 | ADS | Waymo LLC | 2023-08 18:38 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 8 | Intersection | On August [XXX], 2023 at 6:38 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped at a red light in the middle…On August [XXX], 2023 at 6:38 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped at a red light in the middle lane, facing northbound on [XXX] at [XXX]. When the light turned green, the pickup truck in the left turn lane to the left of the Waymo AV did not immediately proceed, and the Waymo AV attempted to merge into the left lane and make a left turn onto westbound [XXX] to pick up a rider that had hailed the Waymo AV while the vehicle was waiting at the red light. As the Waymo AV moved into the left lane, the adjacent pickup truck began to proceed forward and made contact with the drivers side 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was originally submitted to NHTSA on August 19, 2023 via emailed .pdf because NHTSAs online portal was offline for maintenance. Waymo submitted this report again via the re-opened portal on August 20, 2023. |
| 30270-6198 | ADS | Waymo LLC | 2023-08 20:56 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | On August [XXX], 2023 at 8:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound in the center…On August [XXX], 2023 at 8:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound in the center lane on [XXX]. As the AV came to a stop for a red light at the intersection with [XXX], the front of the passenger car that was traveling behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-6335 | ADS | Waymo LLC | 2023-08 19:12 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On August [XXX], 2023 at 7:12 PM PT a Waymo Autonomous Vehicle ("Waymo") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on …On August [XXX], 2023 at 7:12 PM PT a Waymo Autonomous Vehicle ("Waymo") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on the south side of [XXX]. A passenger car which had been parked in front of the Waymo AV began reversing and the rear of the passenger car made contact with the front of the Waymo AV. The passenger car then left the scene. At the time of the impact, the Waymo's 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-6336 | ADS | Waymo LLC | 2023-08 22:10 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | Minor | 0 | Street | On August [XXX], 2023 at 10:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light on eastb…On August [XXX], 2023 at 10:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light on eastbound [XXX] at [XXX]. Shortly after the traffic light turned green and the Waymo AV began to proceed forward, the Waymo AV slowed to a stop. The SUV that was traveling closely behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage, and the trailing SUV left the scene without exchanging information. A passenger in the Waymo AV reported injuries. 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-6337 | ADS | Waymo LLC | 2023-08 15:36 | Mesa, AZ | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Street | On August [XXX], 2023 at 3:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on t…On August [XXX], 2023 at 3:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on the West side of [XXX]. A pickup truck approached the Waymo from behind and slowed to a stop immediately behind the Waymo. The pickup truck then moved slowly forward until the front of the pickup truck was touching the rear of the Waymo AV. The pickup truck then slowly pushed into the rear of the Waymo AV for a few seconds before reversing, maneuvering around the Waymo AV, and leaving the scene. At the time of the impact, the Waymo AV's 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. |
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. 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. The themed reading of the driverless narratives is on the reports page.