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 7901 to 8000.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 13781-3060 v2 | Level 2 | Tesla, Inc. | 2022-05 01:22 | Phoenix, AZ | 2021 Tesla Model Y | ADAS | Other, see Narrative | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-3061 v2 | Level 2 | Tesla, Inc. | 2022-05 04:06 | Maysville, NC | 2018 Tesla Model 3 | ADAS | Animal | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3062 v2 | Level 2 | Tesla, Inc. | 2022-05 20:46 | Greenacres, FL | 2018 Tesla Model 3 | ADAS | Van | Unknown | 48 | Street | Redacted by NHTSA as confidential business information |
| 13781-3069 v2 | Level 2 | Tesla, Inc. | 2022-05 22:50 | Saint Petersburg, FL | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 38 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3070 v2 | Level 2 | Tesla, Inc. | 2022-05 16:34 | San Jose, CA | 2021 Tesla Model Y | ADAS | Passenger Car | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3071 v2 | Level 2 | Tesla, Inc. | 2022-05 16:39 | Gladeview, FL | 2022 Tesla Model Y | ADAS | Van | Unknown | 25 | Street | Redacted by NHTSA as confidential business information |
| 13781-3074 v2 | Level 2 | Tesla, Inc. | 2022-05 | Evergreen, CO | 2021 Tesla Model 3 | ADAS | Pole / Tree | Fatality | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-3075 v2 | Level 2 | Tesla, Inc. | 2022-05 21:36 | CA | 2022 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-3279 v2 | Level 2 | Tesla, Inc. | 2022-05 05:51 | Mission Viejo, CA | 2018 Tesla Model 3 | ADAS | Non-Motorist: Pedestrian | Fatality | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-3483 v3 | Level 2 | Tesla, Inc. | 2022-05 07:40 | UNK | 2022 Tesla Model 3 | ADAS | Unknown | Serious | Unknown | Redacted by NHTSA as confidential business information | |
| 1420-2863 v2 | Level 2 | Volkswagen Group of America, Inc. | 2022-05 18:00 | Phoenix, AZ | 2023 Audi S8L | Unknown, see Narrative | Passenger Car | No Injuries Reported | 7 | Highway / Freeway | The pre-series MY 2023 Audi S8L was undergoing road testing at the time of the incident. The vehicle was decelerating in heavy traffic on northbound [XXX] in Phoenix, AZ, and, while traveling at approximately 7mph, was …The pre-series MY 2023 Audi S8L was undergoing road testing at the time of the incident. The vehicle was decelerating in heavy traffic on northbound [XXX] in Phoenix, AZ, and, while traveling at approximately 7mph, was rear-ended by a Chevrolet Malibu that was traveling at a high rate of speed. The impact caused front end damage to the Malibu, and rear end damage to the Audi, and also pushed the Audi into a BMW Z4, causing minor front end damage to the Audi, and minor rear end damage to the BMW. EDR data retrieved from the Audi indicate that ADAS systems were not active at the time that it was rear-ended by the Chevrolet. The driver of the Audi was belted, and the airbag did not deploy. There were no injuries, but the damage to the Audi was severe enough that towaway was necessary. This incident was part of a multi-car collision, involving five vehicles in total the Audi came into contact with two of those vehicles (Chevrolet and BMW). Because the EDR data indicates that ADAS systems were not active at the time of the incident and the Audi vehicle appears to have performed as designed, VWGoA has no plans for further investigation and considers this matter closed. |
| 30270-2895 v2 | ADS | Waymo LLC | 2022-05 15:11 | Ennis, TX | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | Moderate | 62 | Highway / Freeway | Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-[XXX]-1…Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-[XXX]-1]. On May [XXX], 2022 at 3:11 PM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound Interstate [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the rightmost lane on Interstate [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it encountered tire debris in its lane, executed a right lane change, and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. The Waymo AV exited the roadway to the right shoulder of the road and came to a stop off of the roadway. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained moderate damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. The Waymo AV test driver was transported for medical care and the Waymo AV software operator, seated in the passenger seat, later sought medical attention. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved in the crash was transported from the scene to a hospital for medical treatment and 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-3055 v2 | ADS | Waymo LLC | 2022-05 01:16 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | Motorcycle | No Injuries Reported | 0 | Intersection | The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. 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-3056 v2 | ADS | Waymo LLC | 2022-05 01:43 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AVs undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor undercarriage damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV 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-3057 v2 | ADS | Waymo LLC | 2022-05 02:30 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Unknown | 0 | Intersection | The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-3057-1]. On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Ari…The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-3057-1]. On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] at the [XXX] onramp. While the Waymo AV was stopped at a red light on southbound [XXX] in the rightmost through lane, a passenger vehicle approached the Waymo AV from behind and the right front of the passenger vehicle made contact with the left 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). Both vehicles sustained major damage. The driver of the other vehicle was transported from the scene to a hospital for medical treatment. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away, the crash resulted in airbag deployment, and the driver of the other vehicle was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30270-3219 | ADS | Waymo LLC | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30270-3220 | ADS | Waymo LLC | 2022-05 09:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX] while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30270-3221 | ADS | Waymo LLC | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] at [XXX]. , [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car 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). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30290-3119 | ADS | Argo AI | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30410-3043 | ADS | Motional | 2022-05 12:58 | Las Vegas, NV | 2022 Hyundai Ioniq 5 | ADS | Other, see Narrative | No Injuries Reported | 8 | Street | Redacted by NHTSA as confidential business information |
| 30412-3073 | ADS | Cruise LLC | 2022-05 4:37 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30413-3138 | ADS | May Mobility | 2022-05 16:11 | Arlington, TX | 2020 Lexus RX450H | ADS | Pickup Truck | No Injuries Reported | 11 | Street | The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passe…The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passenger-side mirror to contact the parked vehicle's driver-side mirror. The May vehicle's ground mapping module had fallen significantly behind in its processing of lidar data. As a result, actual objects were being filtered out of the lidar data during object detection. This filtering caused the truck to oscillate between being detected, detecting only the cab, detecting the cab and mirror, and not being detected at all. After assessing the issue, it has been determined that ground map latency alone will not cause safety issues. There is no risk to VRUs, or anything at ground level. The issue was with something in the air (mirror), above the ground. A permanent fix to address the ground map latency issue is in process and will be implemented in the entire fleet within the next 30 days. The second factor in the collision is that we were artificially constraining the vehicle to the right side of the road due to ambiguous and unpainted roadway. If we change that constraint to an advisory line (and allow the vehicle to cross the line to the left), we would have been far enough to the left to avoid collision (simulation success). Solution Implementation: AVO training for extra caution related to protruding items like mirrors (short term), software changes coming in the next update and hotfix (within 30 days), and further improvement in the following update (within 60 days). Until the tested software changes are implemented, we have advised the AVOs to take extra caution in these scenarios and to continue to disengage autonomy when desired. As always, we sacrifice autonomy for safety, as needed. |
| 30490-3168 | ADS | Beep, Inc. | 2022-05 12:30 | Dunedin, FL | Navya | ADS | Bus | No Injuries Reported | 7 | Intersection | Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Tel…Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Telemetry/Video: Requested and received Vehicle taken out of service: Yes temporary safety hold Photographs: Yes Substantial damage: No damages to report Vehicle placed on safety hold: Yes vehicle has been inspected and available for service Lead Investigator: Chief Safety Officer The Beep shuttle attendant was traveling Southbound on [XXX] at approx 7-12 mph in ADS and headed towards the intersection of [XXX]. Beep vehicle stopped at red light at intersection. As the Beep vehicle was crossing the intersection in manual and slowing to a stop to return to ADS in a southbound direction, the trailing bus made light contact with its bicycle rack to the Beep shuttle rear end. The trailing vehicle is a bus owned and operated by the Pinellas Suncoast Transit Authority (PSTA). According to video, as reported by the shuttle attendant and the PSTA Road Supervisor, the bus was tailgating. Root Cause: Trailing vehicle following too closely and not observing Navya slowing to a stop. |
| 30531-2902 v2 | ADS | Transdev Alternative Services | 2022-05 15:11 | Ennis, TX | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | Moderate | 62 | Highway / Freeway | Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30531-[XXX]-1…Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30531-[XXX]-1] On May [XXX], 2022 at 3:11 PM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the rightmost lane on Interstate [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it executed a right lane change and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. The Waymo AV exited the roadway to the right shoulder of the road and came to a stop off of the roadway. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained moderate damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. The Waymo AV test driver was transported for medical care and the Waymo AV software operator, seated in the passenger seat, later sought medical attention. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved in the crash was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is identical to WaymoLLC-202205[XXX]-0 (rev.202205[XXX]603622) |
| 30531-3063 v2 | OTHER | Transdev Alternative Services | 2022-05 02:30 | Phoenix, AZ | 2021 Jaguar I-Pace | Unknown, see Narrative | Passenger Car | Unknown | 0 | Intersection | The content of this report is unchanged from the originally submitted report (Report ID#: 30531-3063-1). On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a co…The content of this report is unchanged from the originally submitted report (Report ID#: 30531-3063-1). On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a passenger vehicle on North [XXX] at the [XXX] onramp. While the Waymo AV was stopped at a red light on southbound North [XXX] in the rightmost through lane, a passenger vehicle approached the Waymo AV from behind and the right front of the passenger vehicle made contact with the left 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). Both vehicles sustained major damage. The driver of the other vehicle was transported from the scene to a hospital for medical treatment. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away, the crash resulted in airbag deployment, and the driver of the other vehicle was transported from the scene to a hospital for medical treatment. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202205[XXX]-0 (rev.202205[XXX]223404). |
| 30531-3064 v2 | ADS | Transdev Alternative Services | 2022-05 01:16 | San Francisco, CA | 2021 Jaguar I-Pace | Unknown, see Narrative | Motorcycle | No Injuries Reported | 0 | Intersection | Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Sa…Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202205[XXX]-0 (rev.202205[XXX]215904). |
| 30531-3065 v2 | ADS | Transdev Alternative Services | 2022-05 01:43 | Phoenix, AZ | 2021 Jaguar I-Pace | Unknown, see Narrative | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact …The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AVE did not contact any vehicle or road user). At the time of contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV 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-202205[XXX]-0 (rev.202205[XXX]213041). |
| 30531-3225 | ADS | Transdev Alternative Services | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor 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 to WaymoLLC-[XXX]. |
| 30531-3226 | ADS | Transdev Alternative Services | 2022-05 09:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX]. while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. 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 minor 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-[XXX]. |
| 30531-3227 | ADS | Transdev Alternative Services | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] …On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was proceeding south on [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car 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). Both vehicles sustained minor 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 to WaymoLLC-2022[XXX]-0 (rev.20220615[XXX]) |
| 30610-3158 v2 | ADS | Zoox, Inc. | 2022-05 13:30 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 25 | Street | A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is su…A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. |
| 30711-3157 | ADS | Pony.ai | 2022-05 15:00 | Irvine, CA | 2021 Hyundai Kona EV | ADS | Passenger Car | No Injuries Reported | 4 | Street | On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of t…On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of the Pony.ai vehicle. The Pony.ai vehicle did not suffer damage. There were no injuries, the police were not called to the scene, and the Pony.ai vehicle was driven back to Pony.ai's Irvine-area facility. Please note that the "UNK" checkbox was selected for the Pony.ai vehicle in the grid as there is no option to select "no damage" for the subject vehicle. The only minor damage in the incident was to the passenger vehicle. |
| 502-2973 v2 | ADS | Ford Motor Company | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 540-3123 | ADS | General Motors, LLC | 2022-05 4:37 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | On June [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order").General Motors LLC (GM) manufactured the Cruise-op…On June [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order").General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3073-1) |
| 62-2875 | Level 2 | Honda (American Honda Motor Co.) | 2022-05 | Henrietta, NY | 2020 Honda HRV | Unknown, see Narrative | Unknown | Moderate | Highway / Freeway | The customer was driving on a highway when a drunk driver rear-ended her. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged. | |
| 62-2876 v2 | Level 2 | Honda (American Honda Motor Co.) | 2022-05 00:30 | Hopkinton, MA | 2018 Honda Odyssey | Unknown, see Narrative | Other, see Narrative | Minor | Unknown | The customer was driving with the Lane Keep Assist System (LKAS) and cruise control on when she drove into a ravine. The customer alleges that the LKAS did not vibrate or warn her before the crash. 5/[XXX] - Additional I…The customer was driving with the Lane Keep Assist System (LKAS) and cruise control on when she drove into a ravine. The customer alleges that the LKAS did not vibrate or warn her before the crash. 5/[XXX] - Additional Information gathered from customer: Confirmed both the LKAS and ACC were engaged at the time of the incident. The customer's wife stated her husband let go of the wheel to see if it was going to work after he activated the controls. Location of Incident: On Interstate [XXX] north in Hopkinton, MA, right before exit [XXX] Time of Incident: May [XXX], 2020, 12:30 AM Road Conditions at the time of the incident: Clear night Injuries sustained in the incident: A nick on husband's right palm by his wrist, minor laceration and bruising Police Report: Accident report is available and has been requested Retrieval of EDR Data: The vehicle has been declared a total loss by Allstate Insurance. It is currently at [XXX] Inc, [XXX], Milford, MA 01757. Insurance name: Allstate Insurance Agent name: [XXX] Claim number: [XXX] Policy #: [XXX] Insurance phone number: (774) 200-1698 | |
| 62-2955 | Level 2 | Honda (American Honda Motor Co.) | 2022-05 | Campbell, CA | 2021 Honda CRV | Unknown, see Narrative | Passenger Car | Moderate | Street | The customer was driving when a Tesla sedan crashed into the customer's passenger-side tire, causing the vehicle to flip multiple times. The customer called to thank Honda for the vehicle's safety features, airbags and d…The customer was driving when a Tesla sedan crashed into the customer's passenger-side tire, causing the vehicle to flip multiple times. The customer called to thank Honda for the vehicle's safety features, airbags and design. The customer alleged that the Lane Keep Assist System and Adaptive Cruise Control were engaged. | |
| 62-3082 | Level 2 | Honda (American Honda Motor Co.) | 2022-05 | Dallas, TX | 2021 Honda Accord Hybrid | Unknown, see Narrative | Unknown | No Injuries Reported | Unknown | The customer reported that while driving, another vehicle crashed into the customer's on the driver's side door, totaling the vehicle. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control wer…The customer reported that while driving, another vehicle crashed into the customer's on the driver's side door, totaling the vehicle. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged. | |
| 62-3127 | Level 2 | Honda (American Honda Motor Co.) | 2022-05 | NJ | 2021 Honda Accord Hybrid | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | Unknown | The customer's boyfriend was making a turn when the steering wheel would not turn and the brakes malfunctioned. As a result, the customer's vehicle hit a curb. The customer alleges that the Lane Keep Assist System and Ad…The customer's boyfriend was making a turn when the steering wheel would not turn and the brakes malfunctioned. As a result, the customer's vehicle hit a curb. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged. | |
| 62-3128 | Level 2 | Honda (American Honda Motor Co.) | 2022-05 | New York, NY | 2021 Honda HRV | Unknown, see Narrative | Passenger Car | No Injuries Reported | Unknown | The customer rear ended another vehicle causing her windshield break. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged. | |
| 62-3139 | Level 2 | Honda (American Honda Motor Co.) | 2022-05 | Rockwall, TX | 2017 Honda Pilot | Unknown, see Narrative | Unknown | Unknown | Intersection | The customer's vehicle was hit by another vehicle that ran a stop sign at an intersection. The customer alleged that the Lane Keep Assist System and Adaptive Cruise Control were engaged. | |
| 855-3183 v2 | ADS | Mercedes-Benz USA, LLC | 2022-05 15:05 | Commerce, CA | 2022 Mercedes-Benz S350D | ADS | Heavy Truck | No Injuries Reported | Highway / Freeway | While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resu…While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resulted in two minor scratches and two indentations on the rear bumper of the Mercedes-Benz. The driver of the truck did not pull over after the collision. The Mercedes-Benz was driven from the incident location, and further inspection of the vehicle concluded no additional damage beyond the cosmetic dents and surface scratches. | |
| 10003-3210 | ADS | Navistar, Inc. | 2022-04 15:52 | Tucson, AZ | 2021 International LT625 | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | 65 | Highway / Freeway | All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event doe…All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrier. The event occurred as follows: As the truck was being operated on the highway, within its mapped ODD, the driver and test engineer attempted to engage the ADS. However, the ADS was not functional at that moment due to the computer unit not having been initialized, and should not have been attempted to be activated. In short, this was a failed attempt to engage the system as a result of human error. The system has now been modified to prevent the ADS from attempting to engage unless the health of the system is fully functional to prevent human error from repeating this event. When the erroneous attempt to engage occurred, the uninitialized vehicle control unit rotated the steering to the left, causing the truck to veer left. The safety driver took control of the steering, and was able to steer accordingly, but not before the left front truck tire and left front quarter panel came into contact with the concrete barrier to the left of the lanes of travel. |
| 1306-2797 v3 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-04 13:18 | Eniat, WA | 2021 Toyota RAV4 | ADAS | Other Fixed Object | Unknown | 14 | Rural Road | As reported by Argo AI to Ford on July [XXX], 2022 (Report # 30290-3346-1), An Argo AI Autonomous Vehicle ("Argo AV") was impacted in the rear while traveling north on [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMA…As reported by Argo AI to Ford on July [XXX], 2022 (Report # 30290-3346-1), An Argo AI Autonomous Vehicle ("Argo AV") was impacted in the rear while traveling north on [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. The Argo AV came to a complete stop at the red traffic light. While the traffic light remained red (turns on red are permitted at this intersection), the Argo AV pulled forward to view cross traffic. The vehicle directly behind the Argo AV failed to fully stop and contacted the Argo AV's rear bumper. [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] "Other" data availability: test vehicle data. |
| 1306-2911 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-04 22:30 | Fife, WA | 2019 Toyota RAV4 | Unknown, see Narrative | Other Fixed Object | Unknown | 65 | Highway / Freeway | In this report, the entries above are based on unconfirmed allegations received from the customer through Toyota Consumer Relations Department. The customer alleged they were driving in the carpool lane on [XXX] south ne…In this report, the entries above are based on unconfirmed allegations received from the customer through Toyota Consumer Relations Department. The customer alleged they were driving in the carpool lane on [XXX] south near iExit [XXX], near Fife, WA. Customer states cruise control was set at 70 and lane departure was on. Customer states the vehicle drifted him into the embankment and he hit a dept of safety (construction) plastic barrier. Customer states he received small abrasions near his left leg from the airbag deployment. As of May [XXX], 2022 Toyota has not received new information regarding this allegation. |
| 1306-3076 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-04 22:30 | Fife, WA | 2019 Toyota RAV4 | ADAS | Other Fixed Object | Unknown | 62 | Highway / Freeway | 5/[XXX]/2022: In this report, the entries above are based on unconfirmed allegations. The customer alleged they were driving in the carpool lane on [XXX] south near exit [XXX], near Fife, WA. Customer states cruise contr…5/[XXX]/2022: In this report, the entries above are based on unconfirmed allegations. The customer alleged they were driving in the carpool lane on [XXX] south near exit [XXX], near Fife, WA. Customer states cruise control was set at 70 and lane departure was on. Customer states the vehicle drifted him into the embankment and he hit a dept. of safety (construction) plastic barrier. Customer states he received small abrasions near his left leg from the airbag deployment. 6/[XXX]/2022: Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) from the subject vehicle. VCH provides an approximately 7.6 second pre-crash data recording, and EDR provides an approximately 4.85 second pre-crash data recording. Based on the data obtained, the following information was confirmed: Dynamic Radar Cruise Control (DRCC) was engaged during the recording leading up to the crash event. Lane Trace Assist (LTA) was engaged during the recording until approximately 6.4 seconds prior to the crash event, at which point it was disengaged. The vehicle was traveling straight (steering angle of 0 degrees) during the recordings with no registered driver or system steering input or brake pedal application leading up to the crash event. As a result of the crash, multiple airbags deployed and the vehicle was towed away from the scene. |
| 13781-2630 v2 | Level 2 | Tesla, Inc. | 2022-04 05:08 | Seattle, WA | 2017 Tesla Model 3 | ADAS | SUV | Unknown | 62 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2631 v2 | Level 2 | Tesla, Inc. | 2022-04 15:56 | Sayreville, NJ | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2639 v3 | Level 2 | Tesla, Inc. | 2022-04 11:26 | Pinole, CA | 2015 Tesla Model S | ADAS | Pickup Truck | Minor | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2641 v2 | Level 2 | Tesla, Inc. | 2022-04 09:28 | Hickory Hills, IL | 2015 Tesla Model S | ADAS | Unknown | Unknown | 32 | Street | Redacted by NHTSA as confidential business information |
| 13781-2642 v2 | Level 2 | Tesla, Inc. | 2022-04 00:46 | Janesville, WI | 2016 Tesla Model S | ADAS | Unknown | Unknown | 10 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2643 v2 | Level 2 | Tesla, Inc. | 2022-04 15:05 | Chandler, AZ | 2021 Tesla Model Y | ADAS | Pickup Truck | Unknown | 8 | Street | Redacted by NHTSA as confidential business information |
| 13781-2650 v2 | Level 2 | Tesla, Inc. | 2022-04 19:18 | Brentwood, TN | 2022 Tesla Model 3 | ADAS | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-2656 v2 | Level 2 | Tesla, Inc. | 2022-04 22:02 | Springettsbury Township, PA | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2667 v2 | Level 2 | Tesla, Inc. | 2022-04 08:39 | Sugar Land, TX | 2020 Tesla Model 3 | ADAS | Passenger Car | Unknown | 20 | Street | Redacted by NHTSA as confidential business information |
| 13781-2668 v2 | Level 2 | Tesla, Inc. | 2022-04 21:21 | San Antonio, TX | 2021 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2669 v2 | Level 2 | Tesla, Inc. | 2022-04 04:13 | Virginia Beach, VA | 2020 Tesla Model 3 | ADAS | Passenger Car | Unknown | 24 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-2697 v2 | Level 2 | Tesla, Inc. | 2022-04 03:35 | Las Vegas, NV | 2017 Tesla Model S | ADAS | Unknown | Unknown | 12 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2727 v2 | Level 2 | Tesla, Inc. | 2022-04 19:52 | Livermore, CA | 2018 Tesla Model 3 | ADAS | Pickup Truck | Unknown | 4 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-2729 v2 | Level 2 | Tesla, Inc. | 2022-04 03:15 | Seattle, WA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2740 v2 | Level 2 | Tesla, Inc. | 2022-04 05:00 | Fort Lauderdale, FL | 2016 Tesla Model X | ADAS | First Responder Vehicle | Minor | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2780 v2 | Level 2 | Tesla, Inc. | 2022-04 20:21 | New Castle, DE | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 46 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-2781 v2 | Level 2 | Tesla, Inc. | 2022-04 05:59 | Marengo, OH | 2020 Tesla Model Y | ADAS | Van | Unknown | 81 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2782 v2 | Level 2 | Tesla, Inc. | 2022-04 00:47 | Washington Township, PA | 2020 Tesla Model Y | ADAS | Other, see Narrative | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-2796 v2 | Level 2 | Tesla, Inc. | 2022-04 04:44 | Conshohocken, PA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 34 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2801 v2 | Level 2 | Tesla, Inc. | 2022-04 13:46 | Napa, CA | 2019 Tesla Model 3 | ADAS | SUV | Unknown | 9 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2804 v2 | Level 2 | Tesla, Inc. | 2022-04 20:32 | Pittsburgh, PA | 2021 Tesla Model 3 | ADAS | Passenger Car | Unknown | 27 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-2805 v2 | Level 2 | Tesla, Inc. | 2022-04 11:16 | Ayden, NC | 2022 Tesla Model 3 | ADAS | SUV | Unknown | 56 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-2806 v2 | Level 2 | Tesla, Inc. | 2022-04 14:18 | Miami, FL | 2019 Tesla Model S | ADAS | Passenger Car | Unknown | 32 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-2817 v2 | Level 2 | Tesla, Inc. | 2022-04 06:55 | Montrose, CA | 2021 Tesla Model Y | ADAS | SUV | Unknown | 25 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2824 v2 | Level 2 | Tesla, Inc. | 2022-04 05:42 | Anaheim, CA | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 40 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-2825 v2 | Level 2 | Tesla, Inc. | 2022-04 04:13 | Miami, FL | 2021 Tesla Model Y | ADAS | SUV | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2826 v2 | Level 2 | Tesla, Inc. | 2022-04 13:32 | San Antonio, TX | 2015 Tesla Model S | ADAS | Unknown | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2828 v3 | Level 2 | Tesla, Inc. | 2022-04 20:46 | Coxs Creek, KY | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 28 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-2829 v2 | Level 2 | Tesla, Inc. | 2022-04 15:04 | Rothsay, MN | 2019 Tesla Model 3 | ADAS | Unknown | Unknown | 76 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2831 v2 | Level 2 | Tesla, Inc. | 2022-04 19:20 | Oak Hill, TN | 2017 Tesla Model S | ADAS | Other Fixed Object | Unknown | 83 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2832 v2 | Level 2 | Tesla, Inc. | 2022-04 13:40 | Minnetonka, MN | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 50 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2833 v2 | Level 2 | Tesla, Inc. | 2022-04 22:08 | Sunnyvale, CA | 2022 Tesla Model 3 | ADAS | Heavy Truck | Unknown | 31 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2840 v2 | Level 2 | Tesla, Inc. | 2022-04 11:40 | Shelbyville, KY | 2020 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 39 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2841 v2 | Level 2 | Tesla, Inc. | 2022-04 06:44 | Palm Bay, FL | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 33 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-2842 v2 | Level 2 | Tesla, Inc. | 2022-04 04:25 | Lake Worth, FL | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 29 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-2845 v2 | Level 2 | Tesla, Inc. | 2022-04 19:11 | San Antonio, TX | 2016 Tesla Model X | ADAS | Unknown | Unknown | 20 | Street | Redacted by NHTSA as confidential business information |
| 13781-3470 v2 | Level 2 | Tesla, Inc. | 2022-04 | FL | 2020 Tesla Model Y | ADAS | Motorcycle | Fatality | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-3486 | Level 2 | Tesla, Inc. | 2022-04 | UNK | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 273-2632 v2 | ADS | Chrysler (FCA US, LLC) | 2022-04 03:30 | Saint Clair, MI | 2022 Jeep Grand Cherokee | ADAS | Other Fixed Object | No Injuries Reported | 50 | Unknown | Redacted by NHTSA as confidential business information |
| 30270-2610 v2 | ADS | Waymo LLC | 2022-04 02:27 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 20 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 AM 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 in autonomous mode and proceeding southbound on [XXX] in the rightmost lane, with a passenger vehicle traveling parallel in the left adjacent lane. As the two vehicles approached [XXX], the passenger vehicle cut into the Waymo's lane and braked before turning right on [XXX]. As the passenger vehicle executed the right turn, the Waymo AV test driver transitioned to manual mode, applied the brakes, but made contact with the passenger side rear corner of the passenger vehicle. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The other party immediately left the scene of the event. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. 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-2646 v2 | ADS | Waymo LLC | 2022-04 19:55 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger car on [XXX] at [XXX] The Waymo AV came to a stop at a stop sign on [XXX] at [XXX] and as it was about to proceed, a passenger vehicle behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. 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-2657 v2 | ADS | Waymo LLC | 2022-04 18:29 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Motorcycle | No Injuries Reported | 3 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was preparing to make a right turn from southbound [XXX] onto westbound [XXX], when it slowed to yield to a pedestrian crossing [XXX]. As the Waymo AV yielded, a motorcycle directly behind the Waymo AV was rear-ended by a pick-up truck. The motorcycle was pushed forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV and the motorcycle sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and a motorcycle was damaged. 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-2743 v2 | ADS | Waymo LLC | 2022-04 14:53 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | Minor | 0 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2743-1]. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2743-1]. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling in autonomous mode in the slip lane on northbound [XXX] at [XXX]. As the Waymo AV slowed to yield to a pedestrian pushing a shopping cart in a crosswalk, the Waymo AV test driver transitioned to manual mode and stopped the Waymo AV. The Waymo AV test driver then proceeded forward but had to yield to approaching traffic in the merge between northbound [XXX] and northbound [XXX]. As the Waymo AV came to a stop, a pickup truck traveling behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and the Waymo AV test driver was transported from the scene for medical treatment due to reported injuries. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30270-2793 v2 | ADS | Waymo LLC | 2022-04 02:31 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Auto…Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA made contact with a parking lot driveway on the 200 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage 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-2818 v2 | ADS | Waymo LLC | 2022-04 16:36 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2818-1]. On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2818-1]. On April [XXX], 2022 at 4:36 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 in autonomous mode and traveling on westbound [XXX], when it slowed for the vehicle directly in front of the Waymo AV, which stopped shortly after passing [XXX]. Shortly after the Waymo AV came to a stop, the SUV behind the Waymo AV was rear-ended by a pickup truck, and the SUV then 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). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. 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-3009 | ADS | Waymo LLC | 2022-04 8:14 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On April [XXX], 2022 at 8:14 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 at a red l…On April [XXX], 2022 at 8:14 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 at a red light facing northeast on [XXX] in autonomous mode. While the light was still red, a passenger vehicle that had been stopped behind the Waymo AV began to move forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30270-3010 | ADS | Waymo LLC | 2022-04 23:30 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Animal | No Injuries Reported | 24 | Street | On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode o…On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode on northbound [XXX] and had just passed [XXX] when a cat entered the street from the adjacent right curb. The Waymo AV then made contact with the cat. The Waymo AV braked and the Waymo AV test driver took manual control and brought the Waymo AV to a stop. 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 did not sustain any damage and the cat was found to be deceased; the cat did not have any identification tags or other signs of ownership. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30270-3011 | ADS | Waymo LLC | 2022-04 06:37 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 17 | Street | On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in ma…On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in manual in the left lane of [XXX] (a one-way street). After passing through the [XXX] intersection, a parked pickup truck on the left side of [XXX] pulled out of the parked position and made contact with the front left fender of the passing Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. |
| 30351-2872 | OTHER | comma.ai | 2022-04 18:10 | Carmel Valley, CA | Toyota Prius | ADAS | Other Fixed Object | Minor | Highway / Freeway | Without agreeing with NHTSA's interpretations or conceding that comma is obligated to respond to the General Order, per General Order Request No. 1, comma provides this information: Video: [XXX] NOTE: DEVICE WAS NOT RUNN…Without agreeing with NHTSA's interpretations or conceding that comma is obligated to respond to the General Order, per General Order Request No. 1, comma provides this information: Video: [XXX] NOTE: DEVICE WAS NOT RUNNING COMMA SOFTWARE AT TIME OF INCIDENT. SEE ADAS VERSION DETAILS ABOVE. | |
| 30370-2949 | ADS | TuSimple | 2022-04 15:52 | Tucson, AZ | 2021 INTERNATIONAL LT 625 | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | 65 | Highway / Freeway | TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrie…TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrier. The event occurred as follows: As the truck was being operated on the highway, within its mapped ODD, the driver and test engineer attempted to engage the ADS. However, the ADS was not functional at that moment due to the computer unit not having been initialized, and should not have been attempted to be activated. In short, this was a failed attempt to engage the system as a result of human error. The system has now been modified to prevent the ADS from attempting to engage unless the health of the system is fully functional to prevent human error from repeating this event. When the erroneous attempt to engage occurred, the uninitialized vehicle control unit rotated the steering to the left, causing the truck to veer left. The safety driver took control of the steering, and was able to steer accordingly, but not before the left front truck tire and left front quarter panel came into contact with the concrete barrier to the left of the lanes of travel. The contact resulted in a scuff to the left tire and damage to the radar unit extending from the left quarter panel. |
| 30412-2823 v2 | ADS | Cruise LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-2884 | ADS | Cruise LLC | 2022-04 00:43 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 5 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-2885 | ADS | Cruise LLC | 2022-04 01:55 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-2886 | ADS | Cruise LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 22 | Street | Redacted by NHTSA as confidential business information |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. 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.