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 6901 to 7000.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 13781-5785 v2 | Level 2 | Tesla, Inc. | 2023-06 10:16 | Turlock, CA | 2022 Tesla Model Y | ADAS | Passenger Car | Fatality | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5791 | Level 2 | Tesla, Inc. | 2023-06 00:11 | Garden Grove, CA | 2022 Tesla Model S | ADAS | Unknown | Unknown | 45 | Street | Redacted by NHTSA as confidential business information |
| 13781-5792 | Level 2 | Tesla, Inc. | 2023-06 22:19 | Weston, MA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 32 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5793 | Level 2 | Tesla, Inc. | 2023-06 14:12 | Berkeley Heights, NJ | 2020 Tesla Model S | ADAS | Unknown | Unknown | 20 | Street | Redacted by NHTSA as confidential business information |
| 13781-5794 | Level 2 | Tesla, Inc. | 2023-06 12:38 | Albuquerque, NM | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 42 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5795 | Level 2 | Tesla, Inc. | 2023-06 12:24 | Middleton, OH | 2023 Tesla Model S | ADAS | Unknown | Unknown | 76 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5796 | Level 2 | Tesla, Inc. | 2023-06 22:19 | Millville, WV | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 47 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5800 | Level 2 | Tesla, Inc. | 2023-06 06:09 | FIllmore, CA | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5801 | Level 2 | Tesla, Inc. | 2023-06 09:07 | Oakland, CA | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 64 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5802 | Level 2 | Tesla, Inc. | 2023-06 21:56 | Richardson, TX | 2023 Tesla Model Y | ADAS | Passenger Car | Unknown | 16 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-5803 | Level 2 | Tesla, Inc. | 2023-06 09:20 | Long Beach, CA | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 30 | Street | Redacted by NHTSA as confidential business information |
| 13781-5806 v2 | Level 2 | Tesla, Inc. | 2023-06 15:20 | Adkins, TX | 2022 Tesla Model 3 | ADAS | Heavy Truck | Serious | 22 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-5807 | Level 2 | Tesla, Inc. | 2023-06 02:18 | Oakmont, PA | 2016 Tesla Model S | ADAS | Unknown | Unknown | 61 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5808 | Level 2 | Tesla, Inc. | 2023-06 16:39 | Dallas, TX | 2022 Tesla Model 3 | ADAS | Unknown | Unknown | 73 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5820 | Level 2 | Tesla, Inc. | 2023-06 01:16 | Los Angeles, CA | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 2 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5821 | Level 2 | Tesla, Inc. | 2023-06 21:30 | Gwinnett Place, GA | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 58 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5822 | Level 2 | Tesla, Inc. | 2023-06 05:12 | Chandler, AZ | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 41 | Street | Redacted by NHTSA as confidential business information |
| 13781-5823 | Level 2 | Tesla, Inc. | 2023-06 11:32 | State College, PA | 2021 Tesla Model Y | ADAS | Animal | Unknown | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9686 | Level 2 | Tesla, Inc. | 2023-06 12:18 | Beaumont, CA | 2016 Tesla Model X | ADAS | Unknown | Unknown | 75 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9687 | Level 2 | Tesla, Inc. | 2023-06 07:25 | Des Moines, WA | 2019 Tesla Model S | ADAS | Passenger Car | Unknown | 29 | Street | Redacted by NHTSA as confidential business information |
| 13781-9688 | Level 2 | Tesla, Inc. | 2023-06 22:06 | Milpitas, CA | 2016 Tesla Model X | ADAS | Unknown | Unknown | 69 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9690 v2 | Level 2 | Tesla, Inc. | 2023-06 23:14 | Pleasantville, NJ | 2022 TESLA Model X | Verified Engaged | Other Fixed Object | Unknown | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9793 v2 | Level 2 | Tesla, Inc. | 2023-06 20:59 | San Diego, CA | 2018 Tesla Model 3 | ADAS | Unknown | Serious | 53 | Unknown | Redacted by NHTSA as confidential business information |
| 28349-5694 v5 | ADS | Lucid USA, Inc. | 2023-06 14:59 | Foster, RI | 2023 Lucid Air Touring | ADAS | Pickup Truck | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30270-5650 v2 | ADS | Waymo LLC | 2023-06 13:17 | Phoenix, AZ | 2021 Jaguar I-PACE | ADS | Passenger Car | Moderate | 13 | Highway / Freeway | After submitting the previous 1-Day report on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], Waymo received notice that the test driver was not transported from the scene to the hospital for medic…After submitting the previous 1-Day report on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], Waymo received notice that the test driver was not transported from the scene to the hospital for medical treatment, but did seek medical treatment at a hospital at a later time. As such, this event could have qualified for a 5-Day report. The narrative below has been updated to reflect this information. This updated report also now lists the Highest Injury Severity Alleged as moderate, and Transdev Alternative Services as an entity that may be aware of this incident. On [XXX], 2023 at 1:17 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, AZ was in a collision involving a passenger car on [XXX] in the southbound direction near the [XXX]. The Waymo AV was traveling in the rightmost lane (out of 5 lanes) in the southbound direction of [XXX], and the left 3 lanes were closed due to a work zone. The vehicle traveling ahead in the same lane as the ADV made an abrupt lane change to the left, revealing a stack of slow-moving vehicles in the Waymo AVs lane. The test driver of the Waymo AV took manual control of the vehicle and started to decelerate and steer toward the right shoulder in response to slow traffic ahead. 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 not engaged and a test driver (in the drivers seating position) was operating the Waymo AV in manual mode. The Waymo AV and the other vehicle sustained damage. The test driver reported an injury, for which they later sought medical treatment. Waymo reported this crash under Request No. 1 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5813 | ADS | Waymo LLC | 2023-06 20:58 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 35 | Street | On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and prepar…On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and preparing to make a right lane change. As it initiated the lane change, the rear passenger side tire struck small debris in the road. 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 AVs tire immediately deflated. Waymo is reporting this event 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-5817 v2 | ADS | Waymo LLC | 2023-06 23:18 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | Minor | 0 | Intersection | Other than adding the law enforcement investigation details, the content of this report is unchanged from the initial report submitted on July 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On June […Other than adding the law enforcement investigation details, the content of this report is unchanged from the initial report submitted on July 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On June [XXX], 2023 at 11:18 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving a pick-up truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and stopped at a stop sign at the intersection of [XXX] when a pick-up truck 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 then took manual control of the Waymo AV and the pick-up truck then made contact with the rear of the Waymo AV again. The Waymo AV test driver pulled towards the side of the road and stopped. TThe pick-up truck then made contact with the rear of the Waymo AV again and when the test driver of the Waymo AV resumed movement, the pick-up truck followed the Waymo AV and repeatedly made further contact with the Waymo AV. At one point the pick-up truck driver verbally harassed the Waymo AV test driver. The Waymo AV test driver was eventually able to elude the pickup truck and wait nearby for law enforcement to arrive. 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-5957 | ADS | Waymo LLC | 2023-06 12:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Parking Lot | On June [XXX], 2023 at 12:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot at [XXX]. The Waymo AV came to a stop while yielding to …On June [XXX], 2023 at 12:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot at [XXX]. The Waymo AV came to a stop while yielding to a pickup truck which was reversing into a perpendicular parking space in front of the Waymo AV. While the Waymo AV was stopped, a van which was in a parking space immediately to the right of the Waymo AV began reversing out of the parking space. The rear of the van made contact with the right side 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. 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-5958 | ADS | Waymo LLC | 2023-06 15:44 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On June [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parallel parked along the …On June [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] when a passenger car pulled up behind the Waymo AV. 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. 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-5959 | ADS | Waymo LLC | 2023-06 17:06 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | On June [XXX], 2023 at 5:06 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]. The Waymo AV was stopped for a red light …On June [XXX], 2023 at 5:06 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]. The Waymo AV was stopped for a red light on [XXX] at [XXX] with its turn signal activated to indicate intent to turn left onto [XXX]. The traffic light turned green, and the Waymo AV slowly moved forward, yielding to oncoming traffic, when the vehicle that had been previously stopped behind the Waymo AV proceeded forward, making contact with the rear bumper of the Waymo AV. The other party immediately left the scene of the event. 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-5960 | ADS | Waymo LLC | 2023-06 21:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Street | On June [XXX], 2023 at 9:19 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was parallel parked along the …On June [XXX], 2023 at 9:19 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was parallel parked along the curb on southbound [XXX] when a pickup truck that was initially parked directly behind the Waymo AV began to maneuver out of its parking spot. As the pickup truck pulled out of the parking spot, it initiated a multi-turn maneuver and reversed into the parked Waymo AV. The rear passenger's side corner of the pickup truck made contact with the driver side 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-5961 | ADS | Waymo LLC | 2023-06 07:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On June [XXX], 2023 at 7:50 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and sto…On June [XXX], 2023 at 7:50 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and stopped at a stop sign at the intersection of [XXX]. While yielding to pedestrians crossing the street, a pickup truck traveling directly 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-5962 | ADS | Waymo LLC | 2023-06 21:39 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 56 | Highway / Freeway | On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when …On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when road debris appeared from under the passenger vehicle in front of the Waymo AV. The Waymo AV test driver transitioned to manual mode just before the Waymo AV made contact with the road debris. 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. |
| 30410-5786 v2 | ADS | Motional | 2023-06 21:42 | Las Vegas, NV | 2021 Hyundai Ioniq 5 | ADS | Passenger Car | Minor | 3 | Intersection | On June [XXX], 2023, at 9:42 PM PDT, a Motional Hyundai Ioniq 5 was operating in autonomous mode with a safety driver at the wheel and a safety operator in the front passenger seat. The Motional vehicle was northbound …On June [XXX], 2023, at 9:42 PM PDT, a Motional Hyundai Ioniq 5 was operating in autonomous mode with a safety driver at the wheel and a safety operator in the front passenger seat. The Motional vehicle was northbound on [XXX], in the left-most of two left turn lanes, turning onto [XXX] at 10 MPH. The Motional vehicle then braked for an approaching taxi in the adjacent turn lane that was perceived to be crossing into the lane of the Motional vehicle and was rear-ended by a silver Toyota traveling behind it. |
| 30412-5661 | ADS | Cruise LLC | 2023-06 04:31 | Chandler, AZ | 2020 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 14 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5687 v2 | ADS | Cruise LLC | 2023-06 22:22 | San Francisco, CA | 2022 Cruise AV | ADS | Van | Unknown | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5782 | ADS | Cruise LLC | 2023-06 09:36 | San Francisco, CA | 2022 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 7 | Street | Redacted by NHTSA as confidential business information |
| 30412-5799 | ADS | Cruise LLC | 2023-06 22:37 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 7 | Street | Redacted by NHTSA as confidential business information |
| 30412-5828 | ADS | Cruise LLC | 2023-06 22:37 | San Francisco, CA | 2022 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-5831 | ADS | Cruise LLC | 2023-06 23:30 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information |
| 30412-5832 | ADS | Cruise LLC | 2023-06 00:50 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information |
| 30412-5833 | ADS | Cruise LLC | 2023-06 23:08 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information |
| 30412-5836 | ADS | Cruise LLC | 2023-06 21:04 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30531-5669 | ADS | Transdev Alternative Services | 2023-06 13:17 | Phoenix, AZ | 2021 Jaguar I-PACE | ADS | Passenger Car | Unknown | 13 | Highway / Freeway | On [XXX], 2023 at 1:17 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, AZ was in a collision involving a passenger car on [XXX] in the southbound direction near the [XXX]. The Waymo AV was traveling i…On [XXX], 2023 at 1:17 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, AZ was in a collision involving a passenger car on [XXX] in the southbound direction near the [XXX]. The Waymo AV was traveling in the rightmost lane (out of 5 lanes) in the southbound direction of [XXX], and the left 3 lanes were closed due to a work zone. The vehicle traveling ahead in the same lane as the ADV made an abrupt lane change to the left, revealing a stack of slow-moving vehicles in the Waymo's lane. The test driver of the Waymo AV took manual control of the vehicle and started to decelerate and steer toward the right shoulder in response to slow traffic ahead. 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's Level 4 ADS was not engaged and a test driver (in the driver's seating position) was operating the Waymo AV in manual mode. The Waymo AV and the other vehicle sustained damage. Transdev Alternative Services is reporting this collision under the 5-day reporting guidelines because a vehicle was towed but nobody was transported to the hospital from the scene of the collision and there was no Vulnerable Road User involved. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of collision report ID: 30270-5650-1. |
| 30531-5814 | ADS | Transdev Alternative Services | 2023-06 20:58 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 35 | Street | On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and prep…On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and preparing to make a right lane change. As it initiated the lane change, the rear passenger side tire struck small debris in the road. 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 s tire immediately deflated. Transdev Alternative Services is reporting this event under Request No 1 of Standing General Order 2021 01 because a vehicle involved was towed away. This is a duplicate report to Waymo 30270-5813-1 report. |
| 30531-5818 | ADS | Transdev Alternative Services | 2023-06 23:18 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | Minor | 0 | Intersection | On June [XXX], 2023 at 11:18 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Los Angeles, California was in a collision involving a pick-up truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX…On June [XXX], 2023 at 11:18 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Los Angeles, California was in a collision involving a pick-up truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and stopped at a stop sign at the intersection of [XXX] when a pick-up truck 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 then took manual control of the Waymo AV and the pick-up truck then made contact with the rear of the Waymo AV again. The Waymo AV test driver pulled towards the side of the road and stopped. The pick-up truck followed the Waymo AV and repeatedly made further contact with the Waymo AV. At one point the pick-up truck driver verbally harassed the Waymo AV test driver. The Waymo AV test driver was eventually able to elude the pickup truck and wait nearby for law enforcement to arrive. The Waymo AV sustained damage. Transdev Alternative Services is reporting a duplicate report from Waymo LLC report number: 30270-5817-1. |
| 30531-5966 | ADS | Transdev Alternative Services | 2023-06 21:39 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 56 | Highway / Freeway | On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane whe…On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when road debris appeared from under the passenger vehicle in front of the Waymo AV. The Waymo AV test driver transitioned to manual mode just before the Waymo AV made contact with the road debris. 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-5962-1. |
| 30711-5675 | ADS | Pony.ai | 2023-06 11:39 | Fremont, CA | 2021 Hyundai Kona EV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On [XXX], 2023, while in supervised ("Drivered") autonomous mode with Pony.ai's ADS engaged, a Pony.ai AV was rear-ended twice, in quick succession, by a passenger vehicle. The incident occurred at the intersection of [X…On [XXX], 2023, while in supervised ("Drivered") autonomous mode with Pony.ai's ADS engaged, a Pony.ai AV was rear-ended twice, in quick succession, by a passenger vehicle. The incident occurred at the intersection of [XXX] and [XXX] in Fremont, CA. At the time of the incident, the Pony.ai AV was stopped at a red light on [XXX] at the intersection with [XXX], heading west-southwest. The incident occurred when a passenger vehicle directly behind the Pony.ai AV proceeded to rear-end the Pony.ai AV two times in quick succession. Following the incident, the Pony.ai safety operator disengaged the AV from autonomous mode. Concerned for his safety, the Pony.ai operator immediately drove the vehicle back to the Pony.ai Fremont office (a distance of approximately 1 mile). The passenger vehicle which had rear-ended the Pony.ai AV followed it back to Pony.ai's Fremont office. After a brief interaction during which the driver of the striking vehicle threatened Pony.ai employees, the driver of that vehicle drove away. The Fremont police were called by Pony.ai staff, and they responded and took a report about the incident. There were no injuries reported. The Fremont Police Department report number is [XXX]. |
| 30792-5747 | ADS | WeRide Corp | 2023-06 14:06 | san jose, CA | 2019 NISSAN LEAF | ADS | Heavy Truck | Moderate | 0 | Street | At 2:06pm a WeRide driverless vehicle (car 1) was stopped behind a big rig truck (vehicle 2). As our vehicle (car 1) was stopped behind the big rig truck, the big rig truck proceeded to reverse backwards and eventually c…At 2:06pm a WeRide driverless vehicle (car 1) was stopped behind a big rig truck (vehicle 2). As our vehicle (car 1) was stopped behind the big rig truck, the big rig truck proceeded to reverse backwards and eventually collided into the WeRide vehicle (car 1). Both parties pulled over both involved vehicles and cooperated to exchange information. The damage sustained to the WeRide vehicle was moderate and the big rig truck did not have any damage. |
| 33495-6720 | ADS | Apollo Autonomous Driving USA | 2023-06 15:39 | San Francisco, CA | 2020 Chrysler Pacifica | ADS | Non-Motorist: Other | No Injuries Reported | 9 | Intersection | On June [XXX], 2023 at 3:39 PM PDT, an Apollo Autonomous Vehicle ("Apollo AV") operating in San Francisco, California, was in a collision involving a scooter on [XXX] near [XXX]. The Apollo AV was traveling westbound on…On June [XXX], 2023 at 3:39 PM PDT, an Apollo Autonomous Vehicle ("Apollo AV") operating in San Francisco, California, was in a collision involving a scooter on [XXX] near [XXX]. The Apollo AV was traveling westbound on [XXX] passing the intersection with [XXX]. The intersection has stop signs clearly installed at all four ways, which require vehicles to make full stop before entering the intersection. The Apollo AV made a full stop, entered and passed approximately 75% of the intersection. A person on scooter coming southbound from [XXX], approached the intersection. The person on scooter entered the intersection without stopping, then made contact with the passenger rear-side of Apollo AV. Our Apollo AV operator immediately disengaged the AV, pulled over to the closest safe place to park, got out of the car to check the person on scooter, who already left the scene on his scooter without exchanging any information. The Apollo AV had small minor paint scratch, which do not need repair. The police were not called. |
| 502-5810 v2 | Level 2 | Ford Motor Company | 2023-06 9:13 | Crothersville, IN | 2021 Ford Escape | ADAS | Other Fixed Object | Minor | Highway / Freeway | No new incidents to report for the 10-Day update submission (report# 502-5810) Due to an application error, the NHTSA SGO portal server was unavailable on July 10, 2023, therefore the submission was completed on July …No new incidents to report for the 10-Day update submission (report# 502-5810) Due to an application error, the NHTSA SGO portal server was unavailable on July 10, 2023, therefore the submission was completed on July 11, 2023. | |
| 540-5666 | Level 2 | General Motors, LLC | 2023-06 16:23 | Kinder, LA | 2022 Chevrolet Bolt EUV | ADAS | Pickup Truck | Unknown | 61 | Intersection | On the afternoon of [XXX], 2023, a Chevrolet Bolt EUV was traveling northeast on [XXX] in Kinder, Louisiana. Per the OnStar recording, the Bolt driver noticed a truck traveling from the west heading east into the interse…On the afternoon of [XXX], 2023, a Chevrolet Bolt EUV was traveling northeast on [XXX] in Kinder, Louisiana. Per the OnStar recording, the Bolt driver noticed a truck traveling from the west heading east into the intersection of [XXX] and [XXX]. In an attempt to avoid the crash, the Bolt driver indicated he steered the vehicle from the left lane to the right lane. The truck did not stop at the intersection and struck the Bolt on the driver side of the vehicle, deploying the side airbag. Crash data indicates that Super Cruise was engaged and active at 16:22:47 EST. At 16:23:18 EST the driver took control of the vehicle. The crash occurred at 16:23:25 EST. A pre-crash speed of 61 mph was the last vehicle speed recorded, approximately 4 seconds prior to the crash. |
| 540-5667 | ADS | General Motors, LLC | 2023-06 04:31 | Chandler, AZ | 2020 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 14 | Intersection | On June 6, 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 th…On June 6, 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-5661-1) |
| 540-5688 v2 | ADS | General Motors, LLC | 2023-06 22:22 | San Francisco, CA | 2022 Cruise AV | ADS | Van | Unknown | 0 | Intersection | On June 16, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufact…On June 16, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update 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-5687-2) |
| 540-5805 | ADS | General Motors, LLC | 2023-06 22:37 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 7 | Street | On June 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 June 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-5799). |
| 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. |
| 842-5787 v2 | Level 2 | Mazda North American Operations | 2023-06 18:30 | NY | 2022 MAZDA CX-30 | ADAS | Unknown | No Injuries Reported | 20 | Unknown | Verbatim text of initial customer complaint as recorded by Mazda Customer Experience Center representative is provided: "Customer states he set the vehicle driver assist to "traffic jam" mode while driving on the highway…Verbatim text of initial customer complaint as recorded by Mazda Customer Experience Center representative is provided: "Customer states he set the vehicle driver assist to "traffic jam" mode while driving on the highway on his way home from a concert when he tapped the gas and the vehicle darted forward hitting the vehicle in front of him. Customer believes the vehicle malfunctioned and caused the accident on it's own. Customer will have the vehicle brought to ROMANO MAZDA to have the vehicle diagnosed for any issues." Additional verbatim text of follow-up inquiry by Mazda Customer Experience Center representative to customer is provided: "The customer stated that he was in the right lane and he wanted to merge into the left lane customer stated as he turned his head for a min to check before merging over the car in front of him stopped really fast and his car just reveled up to 20 mphs for no reason he stated that the car just took off and hit the car in front of him he stated that he didn't hit the gas or anything he stated everything happened so fast that he couldn't even hit his breaks to try to stop the car. The customer stated that everything is still a little fuzzy to what happened. ( The 1st time the customer was telling me what happened he stated that the car that was in front of him was at a complete stop and his car just took off for no reason the customer also stated that when he got on the highway about 10-15 minutes of driving, he had turned the system on and set if for 20 mph but nothing happened he stated then while driving the car did a couple jumps then took off and hit the car in front of him" Points of clarification/interpretation in order to explain the details of this incident are provided: "Traffic Jam" Mode was used to describe Mazda's Traffic Jam Assist (TJA) ADAS-2 function, which is alleged to have been operating for some time prior to the crash. The driver indicated the TJA function was active while driving on the highway, at some point the driver disengaged the TJA function by applying brakes for unknown reasons, followed by reactivating TJA at a later point. Eventually the reported crash occurred. No injuries were reported as a result of the incident. No air bags were deployed as a result of the incident. The subject vehicle was towed away from the incident scene. (July 10, 2023 update) On June 23 2023, Mazda opened an investigation to verify Connected Vehicle (CV) data. On July 2 2023, Mazda confirmed from CV data analysis that the level 2 Advanced Driver Assistance System (ADAS), known as Traffic Jam Assist (TJA), was cancelled by pressing the brake pedal thirty-nine seconds prior to collision. For this reason, it was concluded that the TJA system had no influence on causing the crash incident to occur. As this vehicle was verified to disengage the level 2 ADAS system more than thirty seconds prior to collision, this case does not meet reporting criteria under the Second Amended Standing General Order 2021-01. Mazda considers this incident closed with no further reporting obligations. |
| 855-5908 v2 | Level 2 | Mercedes-Benz USA, LLC | 2023-06 23:30 | Bedford, PA | 2022 Mercedes-Benz GLC 300 | ADAS | Pole / Tree | No Injuries Reported | Unknown | MBUSA learned during its investigation that the vehicle was sold at auction and therefore cannot conduct an inspection nor continue its investigation. The "Reporting Entity or Manufacturer Investigating?" field has been …MBUSA learned during its investigation that the vehicle was sold at auction and therefore cannot conduct an inspection nor continue its investigation. The "Reporting Entity or Manufacturer Investigating?" field has been updated from "Yes" to "No" based on this new information. The customer has been informed of the status. | |
| 945-5789 v4 | Level 2 | Nissan North America, Inc. | 2023-06 23:40 | CA | 2019 Nissan Rogue Sport | ADAS | Other, see Narrative | Unknown | 65 | Highway / Freeway | The information contained in this report is based solely on Nissan's understanding of the allegations received during customer's discussions with Nissan Consumer Affairs representatives. On 6/[XXX]/2023, Claimant orall…The information contained in this report is based solely on Nissan's understanding of the allegations received during customer's discussions with Nissan Consumer Affairs representatives. On 6/[XXX]/2023, Claimant orally reported that he was driving the subject vehicle with ProPilot Assist (PPA) system on when the vehicle began to veer into the other lanes. Claimant reportedly attempted to turn the PPA system off but the buttons and brakes stopped working, and the vehicle crashed into a tollbooth. Claimant reported severe damage to the passenger side and front of the vehicle and airbag deployments. Claimant reported bruising injuries and chest pain but stated he had not seen a doctor yet. During a follow-up call on 6/[XXX]/2023, the Claimant stated he was traveling from Sacramento towards San Francisco. Claimant alleges he was stuck in traffic and activated the PPA system at 65 mph, but as he approached the bridge for the tollbooth, he began pressing the button to lower speed. He alleges the vehicle would not slow down, the steering wheel would not turn, and the brake pedal "became hard", and the vehicle continued to accelerate. Claimant alleges the wheel finally let go, but the vehicle hit one side of the tollbooth. Claimant reported he was transported to the hospital via ambulance. Nissan has requested a vehicle inspection. A vehicle inspection was scheduled for July 12th but was cancelled by the claimant on July 11th prior to Nissan picking up the vehicle. Nissan attempted to re-scheduled for July 19th, but the claimant failed to respond to request. From July 12th to July 18th, six attempts were made to contact the claimant with no response. On July 20th, Nissan closed the claim file due to lack of customer response. As of August 14th, there has been no further attempt made by the customer to contact Nissan regarding the incident, and the investigation is considered closed at this time. |
| 945-5880 v2 | Level 2 | Nissan North America, Inc. | 2023-06 06:00 | St. Paul, MN | 2022 Nissan Rogue | ADAS | Unknown | No Injuries Reported | Intersection | The information contained in this report is based solely on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives. On 7/[XXX]/2023, Claimant ora…The information contained in this report is based solely on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives. On 7/[XXX]/2023, Claimant orally reported that she was crossing an intersection while using the ProPilot Assist (PPA) system, the system turned off, she had to apply "hard brakes," but the subject vehicle crashed into another vehicle. Claimant reported the subject vehicle was towed to a Nissan dealer. During a follow-up call on 7/[XXX]/2023, Claimant reported that the PPA disengaged automatically after the "alarm system went off for the brakes". The subject vehicle reportedly hit the rear of another vehicle. During a follow-up call on 7/11/2023, Claimant reported that she is alleging a defect with the engine caused the accident not the PPA. She reportedly has concerns with the PPA, but not related to this specific accident nor any accident in general. She reported that the PPA was not in use at the time of this accident. Nissan requested a vehicle inspection. On 7/18/2023, Nissan closed the claim file due to the lack of customer response via phone or email. As of 8/14/2023, the customer has made no further attempt to contact Nissan regarding the incident, and the investigation is considered closed at this time. | |
| 10039-6029 v5 | Level 2 | BMW of North America, LLC | 2023-05 06:00 | NJ | 2023 BMW iX xDrive50 | ADAS | Other Fixed Object | No Injuries Reported | 33 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1306-5602 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2023-05 02:23 | Elk Grove, CA | 2022 Toyota Corolla Hybrid | ADAS | Other Fixed Object | Unknown | 85 | Highway / Freeway | On May [XXX], 2023, Toyota received an allegation related to this crash from a rental car company representative on behalf of the renter (driver) and determined this case is reportable under the SGO. The contact record i…On May [XXX], 2023, Toyota received an allegation related to this crash from a rental car company representative on behalf of the renter (driver) and determined this case is reportable under the SGO. The contact record indicates that the rental car representative said the driver alleged the following: He was driving from Disneyland to Northern California on [XXX] with the cruise control set to 70 MPH. He stated there was a "steer assist malfunction" which caused the vehicle to move to the right, and that he overcorrected while steering to the left, causing a rollover crash ending in a ditch. As a result of the crash, the driver alleged that the vehicle has "all over damage" and the "passenger side and the side airbags deployed". There were 4 occupants in the vehicle including the driver. Injuries described as the result of the crash were "mostly bumps and bruises to passengers, but the driver had a torn ligament in the shoulder, but mostly neck and back pain." There were no hospitalizations. The highest injury severity alleged cannot be determined based on the injuries allegation details stated above. On June 30, 2023, Toyota completed a vehicle inspection and field report for the incident and obtained Vehicle Control History (VCH) along with Event Data Recorder (EDR) data from the subject vehicle. Toyota also found that certain remote data was available, and it was analyzed to support in investigation. VCH provides an approximately 8 second pre-crash data recording, and EDR provides an approximately 4.6 second pre-crash data recording. Based on the data obtained, the following was observed: The vehicle was traveling at approximately 85 MPH with Dynamic Radar Cruise Control (DRCC) and Lane Trace Assist (LTA) engaged until approximately 4 seconds prior to the crash event. At approximately 4 seconds prior to the crash event, the driver's steering input changed the steering angle from approximately 4 degrees left to approximately 40 degrees right, and the Vehicle Stability Control system operated, which disengaged the DRCC and LTA. No FCW or AEB activation occurred. The crash resulted in deployment of both curtain shield airbags. |
| 1306-5625 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2023-05 17:04 | Converse, TX | 2022 Toyota Camry | ADAS | Pole / Tree | Unknown | 50 | Rural Road | Some entries in this report are based on unconfirmed allegations. On May [XXX], 2023, Toyota received an allegation related to this crash from a rental car company representative and determined this case is reportable un…Some entries in this report are based on unconfirmed allegations. On May [XXX], 2023, Toyota received an allegation related to this crash from a rental car company representative and determined this case is reportable under the SGO. The contact record indicates that the rental car representative said the driver alleged the following: The vehicle was being driven by a renter, who claims the Lane Tracing Assist was defective. The driver stated the feature was active, and she was within the lane markings when the feature, "pulled her into oncoming traffic and caused her to lose control and impact a metal pole." As a result of the crash, the driver alleged that none of the airbags deployed. The driver was the only occupant. Injuries described as the result of the crash were, "damage to the sternum," for which, "the driver had to seek out medical treatment." The highest injury severity alleged cannot be determined based on the injuries allegation details stated above. Toyota completed a vehicle inspection and field report for this incident on July 18, 2023. Event Data Recorder (EDR) and Vehicle Control History (VCH) were obtained from the vehicle. EDR provides and approximately 4.75 second pre-crash recording and VCH provides and approximately 7 second pre-crash recording. It was observed that Dynamic Cruise Control (DRCC) and Lane Tracing Assist (LTA) were not engaged in the recorded moments leading up to the crash event. The vehicle was not operating with ADAS L2 engaged. |
| 13781-10051 v2 | Level 2 | Tesla, Inc. | 2023-05 | Dekalb County, CA | 2022 Tesla Model 3 | Unknown, see Narrative | Unknown | Serious | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-5427 v2 | Level 2 | Tesla, Inc. | 2023-05 03:41 | Silverton, TX | 2022 Tesla Model 3 | ADAS | Unknown | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5428 v2 | Level 2 | Tesla, Inc. | 2023-05 03:35 | Stockton, CA | 2020 Tesla Model 3 | ADAS | Passenger Car | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5441 v2 | Level 2 | Tesla, Inc. | 2023-05 13:20 | Anaheim, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5442 v2 | Level 2 | Tesla, Inc. | 2023-05 13:24 | Dixie, GA | 2019 Tesla Model S | ADAS | Other, see Narrative | Unknown | 28 | Unpaved Road | Redacted by NHTSA as confidential business information |
| 13781-5443 v2 | Level 2 | Tesla, Inc. | 2023-05 14:42 | Los Angeles, CA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 62 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5444 v2 | Level 2 | Tesla, Inc. | 2023-05 00:37 | Redwood City, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 49 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5450 v2 | Level 2 | Tesla, Inc. | 2023-05 23:53 | Frisco, TX | 2021 Tesla Model Y | ADAS | Pickup Truck | Unknown | 34 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-5451 v2 | Level 2 | Tesla, Inc. | 2023-05 16:20 | Eveleth, MN | 2023 Tesla Model Y | ADAS | Passenger Car | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5452 v2 | Level 2 | Tesla, Inc. | 2023-05 08:37 | Newnan, GA | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5453 v2 | Level 2 | Tesla, Inc. | 2023-05 13:59 | Big Lake, MN | 2021 Tesla Model 3 | ADAS | Unknown | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5454 v2 | Level 2 | Tesla, Inc. | 2023-05 21:06 | Williamsburg, KY | 2019 Tesla Model 3 | ADAS | Pole / Tree | Unknown | 44 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5455 v2 | Level 2 | Tesla, Inc. | 2023-05 19:34 | Minneapolis, MN | 2021 Tesla Model Y | ADAS | SUV | Unknown | 16 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5466 v2 | Level 2 | Tesla, Inc. | 2023-05 21:48 | Irvine, CA | 2021 Tesla Model 3 | ADAS | Unknown | Unknown | 6 | Street | Redacted by NHTSA as confidential business information |
| 13781-5468 v2 | Level 2 | Tesla, Inc. | 2023-05 04:32 | Kansas City, MO | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 71 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5477 v2 | Level 2 | Tesla, Inc. | 2023-05 18:10 | Houston, TX | 2021 Tesla Model 3 | ADAS | Passenger Car | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5478 v2 | Level 2 | Tesla, Inc. | 2023-05 05:11 | New York, NY | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5483 v2 | Level 2 | Tesla, Inc. | 2023-05 14:24 | New York, NY | 2023 Tesla Model X | ADAS | Passenger Car | Unknown | 9 | Street | Redacted by NHTSA as confidential business information |
| 13781-5613 | Level 2 | Tesla, Inc. | 2023-05 07:57 | Norman, OK | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 15 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5614 | Level 2 | Tesla, Inc. | 2023-05 20:23 | Marietta, GA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 23 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-5615 | Level 2 | Tesla, Inc. | 2023-05 03:30 | Napa, CA | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 13 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-5616 | Level 2 | Tesla, Inc. | 2023-05 01:25 | Bridgman, MI | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5617 | Level 2 | Tesla, Inc. | 2023-05 23:34 | Brighton, CO | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 57 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5618 | Level 2 | Tesla, Inc. | 2023-05 00:54 | Malibu, CA | 2023 Tesla Model 3 | ADAS | Unknown | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5619 | Level 2 | Tesla, Inc. | 2023-05 01:42 | Conyers, GA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 59 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5620 | Level 2 | Tesla, Inc. | 2023-05 11:39 | Seattle, WA | 2022 Tesla Model 3 | ADAS | Unknown | Unknown | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5626 | Level 2 | Tesla, Inc. | 2023-05 18:45 | Arlington, TX | 2021 Tesla Model 3 | ADAS | SUV | Unknown | 40 | Street | Redacted by NHTSA as confidential business information |
| 13781-5627 | Level 2 | Tesla, Inc. | 2023-05 01:05 | Austin, TX | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 28 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-5628 | Level 2 | Tesla, Inc. | 2023-05 15:57 | Dallas, TX | 2016 Tesla Model X | ADAS | Pickup Truck | Unknown | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5629 | Level 2 | Tesla, Inc. | 2023-05 06:48 | Danville, CA | 2023 Tesla Model Y | ADAS | Passenger Car | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5630 | Level 2 | Tesla, Inc. | 2023-05 08:13 | Hillsborough, NC | 2022 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. 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.