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 7401 to 7500.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 13781-4557 v2 | Level 2 | Tesla, Inc. | 2022-12 18:12 | Madera, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4558 v2 | Level 2 | Tesla, Inc. | 2022-12 00:18 | Dallas, TX | 2021 Tesla Model Y | ADAS | SUV | Unknown | 14 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4559 v2 | Level 2 | Tesla, Inc. | 2022-12 15:37 | Castro Valley, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4560 v2 | Level 2 | Tesla, Inc. | 2022-12 01:01 | West Covina, CA | 2022 Tesla Model 3 | ADAS | SUV | Unknown | 33 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4564 v2 | Level 2 | Tesla, Inc. | 2022-12 06:25 | Los Angeles, CA | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 18 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4565 v2 | Level 2 | Tesla, Inc. | 2022-12 16:32 | Santa Fe, NM | 2018 Tesla Model 3 | ADAS | SUV | Unknown | 26 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4577 v2 | Level 2 | Tesla, Inc. | 2022-12 23:59 | Edgmont Township, PA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 33 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-4585 v2 | Level 2 | Tesla, Inc. | 2022-12 14:05 | Los Angeles, CA | 2021 Tesla Model 3 | ADAS | Passenger Car | Unknown | 49 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4586 v2 | Level 2 | Tesla, Inc. | 2022-12 15:46 | Natchitoches, LA | 2022 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4588 v2 | Level 2 | Tesla, Inc. | 2022-12 19:27 | Long Beach, CA | 2021 Tesla Model 3 | ADAS | Pickup Truck | Unknown | 26 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4599 v2 | Level 2 | Tesla, Inc. | 2022-12 | Cima, CA | 2021 Tesla Model Y | ADAS | Other, see Narrative | Moderate | 77 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4604 v2 | Level 2 | Tesla, Inc. | 2022-12 04:02 | Marietta, GA | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Minor | 21 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8038 v2 | Level 2 | Tesla, Inc. | 2022-12 20:32 | Goodyear, AZ | 2022 Tesla Model Y | Unknown, see Narrative | Other, see Narrative | Serious | 66 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 28349-4582 v5 | Level 2 | Lucid USA, Inc. | 2022-12 17:04 | Ventura, CA | 2023 Lucid Air (All grades) | ADAS | Other Fixed Object | Unknown | 43 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30270-4363 v2 | ADS | Waymo LLC | 2022-12 21:05 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 11 | Parking Lot | Other than the updated Speed Limit field, the content of this report is unchanged from the initial report submitted on December 5, 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On December [XXX], 2022 …Other than the updated Speed Limit field, the content of this report is unchanged from the initial report submitted on December 5, 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On December [XXX], 2022 at 9:05 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a fixed object in a parking lot on the 4100 block of [XXX]. The Waymo AV was traveling southbound in a parking lot on [XXX] when it approached a parking lot barrier arm. The Waymo AV initially slowed for the arm but then proceeded forward, making contact with it and opening it. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-4505 v2 | ADS | Waymo LLC | 2022-12 13:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | Other than updating the Were All Passengers Belted? field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report submitted on December 18, 2022 [REDACTED, MAY CONTAIN …Other than updating the Were All Passengers Belted? field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report submitted on December 18, 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On December [XXX], 2022 at 1:50 PM PST, a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger car on [XXX] near the intersection with [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it slowed and stopped for a parallel parking vehicle ahead. A passenger car following the Waymo AV did not stop in time and made contact with the rear of the Waymo AV at a speed of about 7 MPH. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode with a test driver present (in the driver's seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30270-4706 | ADS | Waymo LLC | 2022-12 16:54 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing east on [XXX] beh…On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing east on [XXX] behind stopped traffic in the left-most through lane in autonomous mode. An SUV approached from behind and attempted to change lanes into the left turn lane, making 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, and a test driver was present (in the drivers seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-4707 | ADS | Waymo LLC | 2022-12 12:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On December [XXX], 2022 at 12:35 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped facing sou…On December [XXX], 2022 at 12:35 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-4708 | ADS | Waymo LLC | 2022-12 5:18 | Sacaton, AZ | 2021 Peterbilt 579 Epiq | ADS | Other, see Narrative | No Injuries Reported | 51 | Highway / Freeway | On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer operating in Sacaton, Arizona was in a collision involving a Class 8 semi-truck and flat-bed trailer o…On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer operating in Sacaton, Arizona was in a collision involving a Class 8 semi-truck and flat-bed trailer on [XXX], near mile marker [XXX]. The Waymo AV was traveling straight in autonomous mode in the leftmost lane, when the test driver took manual control and attempted a right lane change. As the test driver prepared to make the lane change, there was a Class 8 semi-truck and flat-bed trailer passing in the adjacent right lane. As the Waymo AV test driver initiated the lane change, the Waymo AV made contact with the rear corner of the flat-bed trailer. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained 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-4710 | ADS | Waymo LLC | 2022-12 03:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped facing nor…On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped facing north on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and stopped behind the Waymo AV before eventually proceeding forward and making contact with the rear of the Waymo AV while the AV was still stopped at the red light. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30412-4511 v2 | ADS | Cruise LLC | 2022-12 23:23 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-4540 v2 | ADS | Cruise LLC | 2022-12 08:50 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Unknown | 2 | Street | Redacted by NHTSA as confidential business information |
| 30412-4640 | ADS | Cruise LLC | 2022-12 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information |
| 30412-4642 | ADS | Cruise LLC | 2022-12 23:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 19 | Street | Redacted by NHTSA as confidential business information |
| 30413-4352 | ADS | May Mobility | 2022-12 18:38 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | SUV | No Injuries Reported | 0 | Street | Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle…Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle. No injuries were reported by the operator or the driver of the other vehicle and there was no damage to the SUV and a small crack in the bumper for the subject vehicle. |
| 30413-4378 | ADS | May Mobility | 2022-12 09:02 | Sun City, AZ | 2021 Toyota Sienna | ADS | Motorcycle | No Injuries Reported | 0 | Street | Subject vehicle left the [XXX] headed southwest on [XXX]. Following the [XXX] intersection a motorcycle started following us closely. The subject vehicle came to a stop and the motorcyclist attempted to brake in time, bu…Subject vehicle left the [XXX] headed southwest on [XXX]. Following the [XXX] intersection a motorcycle started following us closely. The subject vehicle came to a stop and the motorcyclist attempted to brake in time, but hit the motorcycle's left mirror/handlebar against the rear passenger-side of the subject vehicle's bumper. |
| 30490-4473 | ADS | Beep, Inc. | 2022-12 17:53 | Port Saint Lucie, FL | 2018 Navya ARMA | Unknown, see Narrative | Passenger Car | No Injuries Reported | 1 | Street | On December [XXX], 2022, a Navya ARMA shuttle operated by Beep (VIN 1N9A1SACXJS[XXX]) was involved in a non-injury collision while operating in manual mode on [XXX] in Port Saint Lucie, FL. While driving along [XXX] und…On December [XXX], 2022, a Navya ARMA shuttle operated by Beep (VIN 1N9A1SACXJS[XXX]) was involved in a non-injury collision while operating in manual mode on [XXX] in Port Saint Lucie, FL. While driving along [XXX] under autonomous control, the shuttle encountered a parked vehicle partially blocking its path, requiring disengagement of the autonomous drive system. The safety driver attempted to manually drive the shuttle around the parked vehicle to reengage the autonomous drive system. While manually steering the shuttle around the parked vehicle blocking its path, the shuttle failed to respond to manual control input and steered to the left, impacting a parked vehicle at a low rate of speed on the opposite side of [XXX]. The six passengers onboard alighted the shuttle, an accident report was filed with the local police, and the shuttle was removed from the scene. Initial reports from the onboard safety driver indicated that while steering around the vehicle blocking the shuttle's path, the shuttle became unresponsive to control input. The safety driver released the operator present button on the vehicle controller, which serves as dead man switch however, the vehicle failed to stop. After the incident, further investigation by Navya confirmed that the root cause of the incident was a failure of the Xbox 360 controller used to manually control the vehicle. Contact with the parked vehicle occurred between the time of failure and the vehicle drive system recognizing that the controller had failed an elapsed time of 4.05 seconds. In response to the incident, Beep suspended operation of all Navya ARMA vehicles pending identification and implementation of appropriate solutions to mitigate the risk of this failure leading to future incidents. Subsequent investigation by Beep and Navya determined that the vehicle control software, NavyaDrive, is limited in its ability to monitor the validity of control signal input received from the Xbox 360 controller. As the safety driver began to manually steer the vehicle, the controller failed, sending constant turning input to the vehicle drive system leading to the collision. Though Navya developed software mitigations due to prior issues encountered with the controller, those mitigations were ineffective with respect to the failure leading to the incident on December [XXX]. Further, due to the short time between the controller failing and the collision (2.34sec), the safety driver was unable to identify the controller failure and trigger the emergency stop before the collision occurred. In response to the incident, Navya is integrating a revised manual control system on the ARMA shuttle platform. The revised manual control system utilizes industrial-grade components for improved electromechanical reliability and allows for active monitoring of the control system health, eliminating the root cause of the failure that led to the incident on December [XXX]. Software upgrades of all Navya ARMA vehicles will further reintroduce automated braking function while the ARMA vehicle is under manual control. Beep is working with Navya to retrofit its fleet of ARMA vehicles with the revised manual control system as well as retrain and recertify its safety driver staff on the updated NavyaDrive software. Discussion of the root cause analysis and solution design for the revised manual control system will be provided to NHTSA as a supplement to this report. |
| 30531-4506 v2 | ADS | Transdev Alternative Services | 2022-12 13:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | Other than updating the "Were All Passengers Belted?" field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report. On December [XXX], 2022 at 1:50 PM PST, a Waymo A…Other than updating the "Were All Passengers Belted?" field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report. On December [XXX], 2022 at 1:50 PM PST, a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a passenger car on [XXX] near the intersection with [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it slowed and stopped for a parallel parking vehicle ahead. A passenger car following the Waymo AV did not stop in time and made contact with the rear of the Waymo AV at a speed of about 7 MPH. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode with a test driver present (in the driver's seating position). Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-20221217-0 (rev.20221217234005). |
| 30531-4719 v4 | ADS | Transdev Alternative Services | 2022-12 16:54 | San Francisco, CA | 2021 Jaguar I- Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers latitude and longitud. On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle ("Waymo AV") o…Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers latitude and longitud. On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX].The Waymo AV was stopped facing east on [XXX] behind stopped traffic in the left-most through lane in autonomous mode. An SUV approached from behind and attempted to change lanes into the left turn lane, making contact with the left rear sensor of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage.Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-20221212-0 (rev.20230117152426). |
| 30531-4720 v2 | ADS | Transdev Alternative Services | 2022-12 12:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 12:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV'') operating in San Franc…Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 12:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV'') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX].The Waymo AV was stopped facing south on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available.This report is a duplicate of Waymo LLC WaymoLLC- 20221213-0 (rev.20230117152233). |
| 30531-4721 v3 | ADS | Transdev Alternative Services | 2022-12 05:18 | Sacaton, AZ | 2021 Peterbilt 579 Epiq | ADS | Heavy Truck | No Injuries Reported | 51 | Highway / Freeway | Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle ("Waymo AV) Peterbilt Class 8 semi-t…Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle ("Waymo AV) Peterbilt Class 8 semi-truck and trailer operating in Sacaton, Arizona was in a collision involving a Class 8 semi-truck and flat-bed trailer on [XXX], near mile marker [XXX]. The Waymo AV was traveling straight in autonomous mode in the leftmost lane, when the test driver took manual control and attempted a right lane change. As the test driver prepared to make the lane change, there was a Class 8 semi-truck and flat-bed trailer passing in the adjacent right lane. As the Waymo AV test driver initiated the lane change, the Waymo AV made contact with the rear corner of the flat-bed trailer. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-20221216-0 (rev.20230117160244). |
| 30531-4726 v2 | ADS | Transdev Alternative Services | 2022-12 03:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francis…Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX].The Waymo AV was stopped facing north on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and stopped behind the Waymo AV before eventually proceeding forward and making contact with the rear of the Waymo AV while the AV was still stopped at the red light. 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 drivers seating position). The Waymo sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-20221229-0 (rev.20230117153132). |
| 30792-4714 | ADS | WeRide Corp | 2022-12 16:31 | Las Vegas, NV | 2023 Nissan Leaf SV Plus | ADS | SUV | No Injuries Reported | 0 | Intersection | At 4:31pm on 12/[XXX]/2023 a Weride safety officer operating a Weride L4 autonomous vehicle (car 1) was in autonomous mode traveling South Bound [XXX] and was stopped at the right turn lane for a red traffic light towar…At 4:31pm on 12/[XXX]/2023 a Weride safety officer operating a Weride L4 autonomous vehicle (car 1) was in autonomous mode traveling South Bound [XXX] and was stopped at the right turn lane for a red traffic light towards [XXX]. While the light was still red, our vehicle slowly moved forward and then yielded for incoming cross traffic. While yielding, the rear vehicle (car 2) behind us accelerated and collided with our vehicle (car 1). The safety driver then disengaged the vehicle as a precautionary measure (car 1) and moved over to examine the minor rear-end collision situation and exchange information with car 2 driver. Since the damage to weride car was minimal, it was driven back in manual mode. |
| 540-4483 v2 | Level 2 | General Motors, LLC | 2022-12 16:27 | Millersville, MA | 2018 Cadillac CT6 | ADAS | SUV | No Injuries Reported | 65 | Highway / Freeway | The subject vehicle, a 2018 Cadillac CT6, was sideswiped by an SUV on a three lane highway. GM's current understanding of the crash is based on OnStar telematics data and the driver's statements after the crash to an On…The subject vehicle, a 2018 Cadillac CT6, was sideswiped by an SUV on a three lane highway. GM's current understanding of the crash is based on OnStar telematics data and the driver's statements after the crash to an OnStar representative. The subject vehicle was traveling northbound on [XXX] in Millersville, Maryland in the center lane of a three lane highway. Super Cruise was functionally engaged and active 8 seconds prior to the crash. There was also an override event 7 seconds prior to the crash, indicating driver took control of steering wheel. An SUV, also traveling northbound on [XXX], departed from the left hand lane and contacted the driver's side of the subject vehicle. The driver of the subject vehicle was buckled at the time of the incident. The driver side roof rail air bag, seat side air bag and seat belt pretensioner deployed. There were no other occupants in the subject vehicle. No injuries were reported. There is no updated information for the 10 day report. |
| 540-4524 v2 | ADS | General Motors, LLC | 2022-12 23:23 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On December 28, 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM…On December 28, 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-4511-2) |
| 540-4541 v3 | ADS | General Motors, LLC | 2022-12 08:50 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Unknown | 2 | Street | On December 30, 2022 GM Cruise Holdings LLC ("Cruise") filed 10 day update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) m…On December 30, 2022 GM Cruise Holdings LLC ("Cruise") filed 10 day update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-4540-2). This 10 day update is a correction to 10 Day Update Report 540-4541-2. The Investigator Name under Post-Crash Information was added. |
| 540-4670 | ADS | General Motors, LLC | 2022-12 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-op…On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-4640-1) |
| 540-4671 | ADS | General Motors, LLC | 2022-12 23:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 19 | Street | On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-op…On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-4642-1) |
| 1243-4347 v3 | Level 2 | Subaru of America, Inc. | 2022-11 07:30 | Covington, LA | 2020 Subaru Forester | ADAS | Pickup Truck | Serious | 84 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1243-4978 v3 | Level 2 | Subaru of America, Inc. | 2022-11 00:30 | Shallotte, NC | 2021 Subaru Outback | ADAS | Other, see Narrative | Moderate | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1306-4286 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-11 13:30 | Hopkins, KY | 2021 Toyota Venza | ADAS | Other Fixed Object | Unknown | 60 | Highway / Freeway | The entries in this report are based on unconfirmed allegations. Toyota received a contact on Nov. [XXX], 2022 in which the customer stated that, "he had an accident, and it was a total loss and he wanted to let Toyota k…The entries in this report are based on unconfirmed allegations. Toyota received a contact on Nov. [XXX], 2022 in which the customer stated that, "he had an accident, and it was a total loss and he wanted to let Toyota know he had a newborn and his wife and him is okay. Guest sts he wanted to thank Toyota and he will buy Toyota again." The customer alleged, "he had the lane assistance on and he was looking at his son and he just flipped 3 times and then someone had to come help." The customer also stated, "The vehicle was towed away from the scene and the customer's wife went to the hospital." Through additional communication with the customer on Nov. [XXX], 2022, Toyota was informed that cruise control was alleged to have been engaged during the incident. This report is a 10-Day update. The original report ID is 1306-4286-1. |
| 1306-4287 v3 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-11 03:28 | McDonald, NC | 2022 Lexus RX450hL | ADAS | Other Fixed Object | Unknown | 69 | Highway / Freeway | The entries in this report are based on unconfirmed allegations. Toyota received a contact on Nov. [XXX], 2022 in which the customer stated that while driving southbound on [XXX], about 1 mile from [XXX], "He fell asleep…The entries in this report are based on unconfirmed allegations. Toyota received a contact on Nov. [XXX], 2022 in which the customer stated that while driving southbound on [XXX], about 1 mile from [XXX], "He fell asleep while using lane assist and cruise control, the vehicle was practically driving itself. He hit 2 highway rails on his drivers side and the passenger side going 70 mph." He indicated that he wanted, "someone at Lexus to explain how his vehicle's airbags did not deploy going 70mph on cruise control and lane assist." Additionally, the customer stated, "He and his friend that was in the passenger seat are slightly injured...he called 911 and they had a local tow service tow the vehicle to a lot." The customer stated that his driver seat belt was on, and that an occupant was in the rear seat laying down without the seat belt fastened. The customer also stated, "He and his friend that was in the passenger seat are slightly injured." and that, "knees are bothering the driver." On Nov. 18, 2022, Toyota conducted further review of the customer's statement and determined that the crash was reportable. On Nov. 30, 2022, Toyota received a field report related to the incident, which included Vehicle Control History (VCH) and Event Data Recording (EDR). VCH provides an approximately 7.7 second pre-crash recording, and EDR provides an approximately 4.8 second pre-crash recording. From the data, Toyota observed that Lane Trace Assist (LTA) and Dynamic Radar Cruise Control (DRCC) were engaged in the moments leading up to the crash event. LTA was engaged from the start of the recording until approximately 6.1 seconds prior to the crash event, at which point driver steering input disengaged the system. Prior to disengagement of LTA, the VCH recording shows the driver's hands were detected on the steering wheel. DRCC was engaged from the start of the recording until the crash event. This report is a Monthly Update. The original report ID is 1306-4287-1. |
| 1306-4389 v2 | ADS | Toyota Motor Engineering & Manufacturing | 2022-11 15:43 | Ann Arbor, MI | 2020 Lexus RX450H | Unknown, see Narrative | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | This report is being submitted because May Mobility notified Toyota on Dec. 9, 2022 of 1-Day Report submission 30413-4170-1,related to an incident that occurred on Nov. [XXX], 2022. Toyota has no additional information o…This report is being submitted because May Mobility notified Toyota on Dec. 9, 2022 of 1-Day Report submission 30413-4170-1,related to an incident that occurred on Nov. [XXX], 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned 1-Day Report. Please refer to the report from May Mobility for details. This report is a 10 Day update. The original report ID is 1306-4389-1. |
| 1306-4427 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-11 13:11 | Novi, MI | 2022 Lexus NX350 | ADAS | Passenger Car | Unknown | 31 | Highway / Freeway | On December 13, 2022 Toyota received a field report related to this crash incident, in which the owner's allegation was related to airbag non-deployment. During the crash event, the vehicle was rear-ended by an SUV, then…On December 13, 2022 Toyota received a field report related to this crash incident, in which the owner's allegation was related to airbag non-deployment. During the crash event, the vehicle was rear-ended by an SUV, then crashed into the back of a passenger car. There were no allegations made related to the operation of the ADAS systems. However, upon obtaining and reviewing VCH and EDR data from the crash event, Toyota became aware that the vehicle was operating with ADAS L2 engagement in the moments leading up to the crash event. VCH provides an approximately 9 second pre-crash data recording, and EDR provides an approximately 4.8 second pre-crash data recording. Based on the data obtained, the following information was observed: Lane Trace Assist (LTA) was engaged during the recording until approximately 4 seconds prior to the crash event. Dynamic Radar Cruise Control (DRCC) was engaged during the recording until approximately 2.4 seconds prior to the crash event, at which point the PCS Alarm (FCW) was activated. The vehicle was traveling at approximately 70 MPH prior to applying the brakes. As a result of the crash incident, the vehicle was towed away from the scene. The owner alleged the vehicle's driver was experiencing, "back pain and headaches." This report is a 10-Day update. The original report ID is 1306-4427-1. |
| 13781-4153 v2 | Level 2 | Tesla, Inc. | 2022-11 22:37 | Sacramento, CA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 21 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4155 v2 | Level 2 | Tesla, Inc. | 2022-11 02:28 | Los Angeles, CA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 42 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4156 v2 | Level 2 | Tesla, Inc. | 2022-11 06:26 | Midland, VA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 40 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-4166 v2 | Level 2 | Tesla, Inc. | 2022-11 20:50 | Stevensville, MD | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 1 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4181 v2 | Level 2 | Tesla, Inc. | 2022-11 23:08 | Princeton, TX | 2017 Tesla Model 3 | ADAS | SUV | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4182 v2 | Level 2 | Tesla, Inc. | 2022-11 09:33 | Los Angeles, CA | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 59 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4183 v2 | Level 2 | Tesla, Inc. | 2022-11 22:04 | Costa Mesa, CA | 2023 Tesla Model X | ADAS | Passenger Car | Unknown | 7 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4184 v2 | Level 2 | Tesla, Inc. | 2022-11 23:10 | Houston, TX | 2021 Tesla Model S | ADAS | Heavy Truck | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4185 v2 | Level 2 | Tesla, Inc. | 2022-11 23:32 | Grants Pass, OR | 2022 Tesla Model S | ADAS | Unknown | Unknown | 16 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4186 v2 | Level 2 | Tesla, Inc. | 2022-11 09:13 | Phoenix, AZ | 2017 Tesla Model X | ADAS | Other Fixed Object | Unknown | 22 | Street | Redacted by NHTSA as confidential business information |
| 13781-4187 v2 | Level 2 | Tesla, Inc. | 2022-11 12:20 | Austin, TX | 2018 Tesla Model X | ADAS | SUV | Unknown | 32 | Street | Redacted by NHTSA as confidential business information |
| 13781-4188 v2 | Level 2 | Tesla, Inc. | 2022-11 20:50 | Daphne, AL | 2022 Tesla Model Y | ADAS | Heavy Truck | Unknown | 4 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4189 v2 | Level 2 | Tesla, Inc. | 2022-11 02:28 | Hawthorne, CA | 2020 Tesla Model Y | ADAS | SUV | Unknown | 21 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4190 v2 | Level 2 | Tesla, Inc. | 2022-11 15:29 | Houston, TX | 2021 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 22 | Street | Redacted by NHTSA as confidential business information |
| 13781-4191 v2 | Level 2 | Tesla, Inc. | 2022-11 13:11 | Fullerton, CA | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 26 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4192 v2 | Level 2 | Tesla, Inc. | 2022-11 11:01 | Los Angeles, CA | 2022 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 36 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4193 v2 | Level 2 | Tesla, Inc. | 2022-11 16:40 | San Bernardino, CA | 2022 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 17 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4194 v2 | Level 2 | Tesla, Inc. | 2022-11 15:26 | Dos Palos, CA | 2021 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 29 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4195 v2 | Level 2 | Tesla, Inc. | 2022-11 23:08 | Marfa, TX | 2022 Tesla Model X | ADAS | Passenger Car | Unknown | 33 | Street | Redacted by NHTSA as confidential business information |
| 13781-4196 v2 | Level 2 | Tesla, Inc. | 2022-11 03:21 | San Diego, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 28 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4197 v2 | Level 2 | Tesla, Inc. | 2022-11 10:06 | Vista, CA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 44 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4205 v2 | Level 2 | Tesla, Inc. | 2022-11 15:23 | San Diego, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4206 v2 | Level 2 | Tesla, Inc. | 2022-11 06:06 | Moscow, ID | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 72 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4265 v2 | Level 2 | Tesla, Inc. | 2022-11 16:27 | Los Angeles, CA | 2021 Tesla Model 3 | ADAS | Passenger Car | Unknown | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4266 v2 | Level 2 | Tesla, Inc. | 2022-11 18:50 | Bethesda, MD | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4279 v2 | Level 2 | Tesla, Inc. | 2022-11 22:04 | Fremont, CA | 2020 Tesla Model 3 | ADAS | Heavy Truck | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4280 v2 | Level 2 | Tesla, Inc. | 2022-11 15:19 | Encinitas, CA | 2020 Tesla Model 3 | ADAS | SUV | Unknown | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4284 v2 | Level 2 | Tesla, Inc. | 2022-11 10:00 | Tinton Falls, NJ | 2021 Tesla Model Y | ADAS | Van | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4288 v2 | Level 2 | Tesla, Inc. | 2022-11 10:36 | West Islip, NY | 2022 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4289 v2 | Level 2 | Tesla, Inc. | 2022-11 19:29 | Fresno, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4290 v2 | Level 2 | Tesla, Inc. | 2022-11 | Morrisdale, PA | 2022 Tesla Model S | ADAS | Unknown | No Injuries Reported | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-4293 v2 | Level 2 | Tesla, Inc. | 2022-11 13:20 | Maumee, OH | 2020 Tesla Model 3 | ADAS | First Responder Vehicle | Unknown | 15 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4296 v2 | Level 2 | Tesla, Inc. | 2022-11 13:20 | Maumee, OH | 2020 Tesla Model 3 | ADAS | First Responder Vehicle | Unknown | 15 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4297 v2 | Level 2 | Tesla, Inc. | 2022-11 10:37 | Norwalk, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 30 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4298 v2 | Level 2 | Tesla, Inc. | 2022-11 01:37 | East Palo Alto, CA | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 26 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4299 v2 | Level 2 | Tesla, Inc. | 2022-11 16:23 | Houston, TX | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4300 v2 | Level 2 | Tesla, Inc. | 2022-11 03:55 | West Palm Beach, FL | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 46 | Traffic Circle | Redacted by NHTSA as confidential business information |
| 13781-4301 v2 | Level 2 | Tesla, Inc. | 2022-11 03:47 | Vancouver, WA | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 19 | Street | Redacted by NHTSA as confidential business information |
| 13781-4302 v2 | Level 2 | Tesla, Inc. | 2022-11 23:18 | Los Angeles, CA | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4304 v2 | Level 2 | Tesla, Inc. | 2022-11 00:52 | Irvine, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 63 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4327 v2 | Level 2 | Tesla, Inc. | 2022-11 16:22 | Commerce, CA | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 18 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4328 v2 | Level 2 | Tesla, Inc. | 2022-11 05:40 | Culver City, CA | 2016 Tesla Model X | ADAS | Unknown | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4333 v2 | Level 2 | Tesla, Inc. | 2022-11 07:08 | Clovis, CA | 2020 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 35 | Street | Redacted by NHTSA as confidential business information |
| 13781-4334 v2 | Level 2 | Tesla, Inc. | 2022-11 15:52 | Charlotte, NC | 2021 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 54 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4335 v2 | Level 2 | Tesla, Inc. | 2022-11 19:32 | Irvine, CA | 2021 Tesla Model 3 | ADAS | SUV | Unknown | 35 | Street | Redacted by NHTSA as confidential business information |
| 13781-4336 v2 | Level 2 | Tesla, Inc. | 2022-11 00:47 | Colorado Springs, CO | 2021 Tesla Model Y | ADAS | Passenger Car | Unknown | 24 | Street | Redacted by NHTSA as confidential business information |
| 13781-4337 v2 | Level 2 | Tesla, Inc. | 2022-11 21:54 | Milpitas, CA | 2020 Tesla Model 3 | ADAS | Passenger Car | Unknown | 46 | Street | Redacted by NHTSA as confidential business information |
| 13781-4338 v2 | Level 2 | Tesla, Inc. | 2022-11 20:39 | San Francisco, CA | 2021 Tesla Model S | ADAS | Passenger Car | Unknown | 7 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4340 v2 | Level 2 | Tesla, Inc. | 2022-11 05:31 | Orlando, FL | 2018 Tesla Model X | ADAS | SUV | Unknown | 45 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4341 v2 | Level 2 | Tesla, Inc. | 2022-11 09:41 | Metairie, LA | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30270-4482 | ADS | Waymo LLC | 2022-11 16:30 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 2 | Street | On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SUV near [XXX]. While reversing in manual on a narrow road, the fr…On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SUV near [XXX]. While reversing in manual on a narrow road, the front right radar of the Waymo AV made contact with the taillight of a parked SUV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both 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-4484 | ADS | Waymo LLC | 2022-11 08:48 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On November [XXX], 2022 at 8:48 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a garbage truck on the 500 block of [XXX]. The Waymo AV was traveling eastbound on […On November [XXX], 2022 at 8:48 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a garbage truck on the 500 block of [XXX]. The Waymo AV was traveling eastbound on [XXX] when it encountered a stopped garbage truck traveling westbound. The Waymo AV pulled to the right side of the street and stopped, unable to proceed past the garbage truck and an SUV parked parallel to the curb. The garbage truck then attempted to pass between the Waymo AV and a parked passenger vehicle to the right of the garbage truck, and the garbage truck made contact with the left rear corner of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode and the Waymo AV was stationary. 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-4485 | ADS | Waymo LLC | 2022-11 09:34 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On November [XXX], 2022 at 9:34 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in traffic on n…On November [XXX], 2022 at 9:34 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in traffic on northbound [XXX] in autonomous mode. A passenger car that had been stopped behind the Waymo AV passed on the left side, crossing the double yellow line and making contact with the Waymo AVs rear left sensor housing. The passenger car immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained 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. |
| 30413-4170 | ADS | May Mobility | 2022-11 15:43 | Ann Arbor, MI | 2020 Lexus RX450H | Unknown, see Narrative | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have …Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have come to a full stop before the stop line and remained stopped until the operator took over. 6 seconds prior to incident, operator took the vehicle over manually before it could have stopped in autonomy. Operator moved the vehicle manually passed the stop line, colliding with a bicyclist's back tire. No injuries reported from the bicyclist or the operator and no damage to the vehicle or bicycle. |
| 30531-4492 v2 | ADS | Transdev Alternative Services | 2022-11 16:30 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 2 | Street | Corrected the latitude and longitude. Nothing else was updated. On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SU…Corrected the latitude and longitude. Nothing else was updated. On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SUV near [XXX]. While reversing in manual on a narrow road, the front right radar of the Waymo AV made contact with the taillight of a parked SUV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-20221103-0 (rev.20221215142403). |
| 30531-4494 | ADS | Transdev Alternative Services | 2022-11 9:34 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On November [XXX], 2022 at 9:34 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in traffic on n…On November [XXX], 2022 at 9:34 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in traffic on northbound [XXX] in autonomous mode. A passenger car that had been stopped behind the Waymo AV passed on the left side, crossing the double yellow line and making contact with the Waymo AVs rear left sensor housing. The passenger car immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained 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 report WaymoLLC-20221108-0 (rev.20221215145119). |
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.