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 7701 to 7800.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 502-3744 v2 | Level 2 | Ford Motor Company | 2022-08 17:00 | Bloomington, MN | 2022 Ford Expedition | ADAS | SUV | Minor | 0 | Highway / Freeway | 10-Day Update on report 502-3744-1 (reported on Sept [XXX], 2022): Ford has received and updated information on the Incident Scene: Coordinates, Surface Condition, Speed Limit and Weather, and vehicle Mileage. 1-Day (…10-Day Update on report 502-3744-1 (reported on Sept [XXX], 2022): Ford has received and updated information on the Incident Scene: Coordinates, Surface Condition, Speed Limit and Weather, and vehicle Mileage. 1-Day (report# 502-3744-1) Narrative: This SGO Report is the official Portal submission emailed to NHTSA on Sept [XXX], 2022, during that time the NHTSA SGO Portal was undergoing maintenance. The driver reported to Ford that they were traveling South on [XXX] while using Adaptive Cruise Control (ACC) and Lane Centering Assist (LCA), during traffic congestion the Ford driver applied the brakes and came to a complete stop. The Jeep Wrangler directly behind failed to stop and impacted the right rear of the Ford vehicle, within 30 seconds of Ford vehicle ADAS Level 2 feature deactivation due to brake application. The Jeep suffered front end damage and was towed, and the passenger was taken to the hospital for minor injuries. |
| 502-3864 | ADS | Ford Motor Company | 2022-08 17:55 | Miami Beach, FL | 2020 Ford Escape | ADS | Pickup Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 502-3866 | ADS | Ford Motor Company | 2022-08 12:31 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 540-3819 | ADS | General Motors, LLC | 2022-08 07:04 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 14 | Street | On September [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 Cru…On September [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-3801-1) |
| 540-3820 | ADS | General Motors, LLC | 2022-08 03:53 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Street | On September [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 Cru…On September [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-3806-1) |
| 988-3684 v2 | ADS | PACCAR Incorporated | 2022-08 18:00 | Palmer, TX | 2022 Kenworth T680 | ADS | Pickup Truck | No Injuries Reported | 15 | Highway / Freeway | Monthly Report Update: A police report was issued after the original SGO incident reports were submitted and described the cause of the collision as the pick-up truck's failure to control its speed before rear-ending the…Monthly Report Update: A police report was issued after the original SGO incident reports were submitted and described the cause of the collision as the pick-up truck's failure to control its speed before rear-ending the Kodiak AV. The content of this report is otherwise unchanged from the initial incident report submitted on August [XXX], 2022. On August [XXX], 2022, Kodiak Robotics, Inc. ("Kodiak") filed an Incident Report (the "Report") under the Standing General Order 2021-01 (the "Order"). PACCAR, Inc. (Paccar) manufactured the Kodiak-operated motor vehicle involved in the incident summarized in the Incident Report. Because Paccar is also a Reporting Entity under the Order, Paccar is submitting a duplicate of the redacted public copy of the Report. Paccar has selected "Unknown" in the "ADS version" field solely to avoid the second submission of nonpublic Kodiak CBI. Paccar is in possession of Kodiak's response to this field and incorporates Kodiak's response into this submission by reference. Paccar's submission is based on facts supplied to Paccar by Kodiak. Paccar has not investigated the alleged incident and has no independent knowledge of the facts in the Report. |
| 12381-3438 v2 | ADS | Daimler Trucks North America, LLC | 2022-07 16:33 | ALBUQUERQUE, NM | 2021 FREIGHTLINER Cascadia | ADS | Other, see Narrative | No Injuries Reported | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 12381-3536 v2 | Level 2 | Daimler Trucks North America, LLC | 2022-07 03:00 | Keokuk, IA | 2022 Freightliner Cascadia | ADAS | Other, see Narrative | No Injuries Reported | Highway / Freeway | On August [XXX], 2022, Daimler Truck was notified of an alleged fire on the rear of the trailer in a 2022 Freightliner Cascadia, that occurred after the vehicle was leaving a repair facility. The incident was alleged to…On August [XXX], 2022, Daimler Truck was notified of an alleged fire on the rear of the trailer in a 2022 Freightliner Cascadia, that occurred after the vehicle was leaving a repair facility. The incident was alleged to happen somewhere on the [XXX] in Keokuk, Iowa. The vehicle has a Detroit Assurance 5.0 system and would have had to have been towed from the incident, so even though we have no allegation that implicates the ADAS system, we are reporting this out of an abundance of caution. | |
| 12381-3557 | ADS | Daimler Trucks North America, LLC | 2022-07 12:39 | Santa Rosa, NM | 2021 Freightliner Cascadia | ADS | Other, see Narrative | No Injuries Reported | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1243-3577 v3 | Level 2 | Subaru of America, Inc. | 2022-07 08:00 | WV | 2020 Subaru Outback | ADAS | Pole / Tree | Minor | 40 | Unknown | Redacted by NHTSA as confidential business information |
| 1243-3681 v4 | Level 2 | Subaru of America, Inc. | 2022-07 15:13 | Mamaroneck, NY | 2020 Subaru Forester | ADAS | Other Fixed Object | No Injuries Reported | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1306-3711 v3 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-07 02:59 | Goldsboro, NC | 2021 Toyota Corolla | ADAS | Unknown | Unknown | 89 | Highway / Freeway | On August [XXX], 2022 Toyota received a field report related to this crash. The vehicle was reportedly traveling east on [XXX], when it approached a vehicle travelling the wrong way on the road operated by a drunk driver…On August [XXX], 2022 Toyota received a field report related to this crash. The vehicle was reportedly traveling east on [XXX], when it approached a vehicle travelling the wrong way on the road operated by a drunk driver. The Toyota Corolla driver alleged that they attempted to swerve right to miss the oncoming vehicle, but collided with the vehicle on the driver side. As a result of the collision, the Toyota Corolla allegedly rolled over, landed on its wheels, and contacted a highway barrier. Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) data from the subject vehicle. VCH provides an approximately 8 second pre-crash data recording, and EDR provides an approximately 4.80 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 6.7 seconds prior to the crash event and Dynamic Radar Cruise Control (DRCC) was engaged during the recording until approximately 5.5 seconds prior to the crash event. ADAS L2 was disengaged approximately 6.7 seconds prior to the crash due to driver steering input exceeding the steering torque override threshold of LTA. The vehicle was traveling at approximately 89 MPH prior to the crash event. As a result of the crash incident, the subject vehicle was towed away from the scene. Injuries to occupants of the subject vehicle were described by the owner as: Driver: Cerebral fluid leaking from nose, Concussion, whiplash, backpain Front Passenger: No injuries reported. This report is a Monthly Update. The original report ID is 1306-3711-1. |
| 1306-3729 v3 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-07 20:29 | Catonsville, MD | 2022 Toyota RAV4 HV | Unknown, see Narrative | Unknown | No Injuries Reported | 9 | Highway / Freeway | On August [XXX], 2022 Toyota completed a field report related to this crash. The vehicle was reportedly traveling east on [XXX], when it is alleged that it experienced a "loss of stability control" and "swerving back and…On August [XXX], 2022 Toyota completed a field report related to this crash. The vehicle was reportedly traveling east on [XXX], when it is alleged that it experienced a "loss of stability control" and "swerving back and forth" condition, forcing the driver to slow his vehicle. The driver alleged that he brought the vehicle to a stop, and approximately 5 seconds later another vehicle struck the subject vehicle in a rear-end collision. Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) data from the subject vehicle. VCH provides an approximately 7.5 second pre-crash data recording, and EDR provides an approximately 5 second pre-crash data recording. Based on further analysis of the data obtained, the following information was observed: Dynamic Radar Cruise Control (DRCC) and Lane Trace Assist (LTA) were not engaged during the recording. The vehicle was traveling at approximately 53 MPH prior to applying the brakes. The vehicle was impacted in the rear when it was travelling at approximately 9 MPH. The driver's seat belt status was "OFF" (not buckled). As a result of the crash incident, the subject vehicle was towed away from the scene. This report is a Monthly update. The original report ID is 1306-3729-1. |
| 13781-10625 | Level 2 | Tesla, Inc. | 2022-07 01:21 | Chicago, IL | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 24 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-3298 v2 | Level 2 | Tesla, Inc. | 2022-07 21:30 | Sacaton, AZ | 2022 Tesla Model 3 | ADAS | Unknown | Unknown | 61 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-3299 v2 | Level 2 | Tesla, Inc. | 2022-07 11:42 | Blue Springs, MO | 2020 Tesla Model Y | ADAS | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-3300 v2 | Level 2 | Tesla, Inc. | 2022-07 21:43 | DuPont, WA | 2021 Tesla Model 3 | ADAS | Passenger Car | Unknown | 78 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3301 v2 | Level 2 | Tesla, Inc. | 2022-07 11:46 | Santa Monica, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 20 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-3302 v2 | Level 2 | Tesla, Inc. | 2022-07 12:10 | Miami, FL | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 29 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3303 v2 | Level 2 | Tesla, Inc. | 2022-07 06:50 | Brussels, WI | 2020 Tesla Model 3 | ADAS | Animal | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3304 v2 | Level 2 | Tesla, Inc. | 2022-07 06:28 | Weverton, MD | 2019 Tesla Model 3 | ADAS | Animal | Unknown | 73 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-3305 v2 | Level 2 | Tesla, Inc. | 2022-07 08:42 | West Hill, PA | 2014 Tesla Model S | ADAS | Unknown | Unknown | 71 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-3306 v2 | Level 2 | Tesla, Inc. | 2022-07 05:27 | Gallatin, TN | 2020 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3317 v2 | Level 2 | Tesla, Inc. | 2022-07 17:51 | Desert Hot Springs, CA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 41 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-3318 v2 | Level 2 | Tesla, Inc. | 2022-07 18:18 | Emeryville, CA | 2020 Tesla Model Y | ADAS | Passenger Car | Unknown | 18 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3325 | Level 2 | Tesla, Inc. | 2022-07 23:52 | Norcross, GA | 2019 Tesla Model 3 | ADAS | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-3327 v2 | Level 2 | Tesla, Inc. | 2022-07 17:57 | Gainesville, FL | 2015 Tesla Model S | ADAS | Heavy Truck | Fatality | 64 | Parking Lot | Redacted by NHTSA as confidential business information |
| 13781-3331 v2 | Level 2 | Tesla, Inc. | 2022-07 00:51 | New Hope, AZ | 2020 Tesla Model Y | ADAS | Unknown | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3332 v2 | Level 2 | Tesla, Inc. | 2022-07 11:46 | Riverside, CA | 2021 Tesla Model Y | ADAS | Motorcycle | Fatality | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-3333 v2 | Level 2 | Tesla, Inc. | 2022-07 14:50 | Los Angeles, CA | 2021 Tesla Model Y | ADAS | Van | Unknown | 63 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3334 v2 | Level 2 | Tesla, Inc. | 2022-07 04:35 | Fort McDowell, AZ | 2016 Tesla Model S | ADAS | Unknown | Unknown | 62 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3358 v2 | Level 2 | Tesla, Inc. | 2022-07 02:25 | Woodbridge, MD | 2020 Tesla Model 3 | ADAS | Pickup Truck | Unknown | 54 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3359 v2 | Level 2 | Tesla, Inc. | 2022-07 23:00 | Stockton, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 62 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3360 v2 | Level 2 | Tesla, Inc. | 2022-07 07:26 | Atlanta, GA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3361 v2 | Level 2 | Tesla, Inc. | 2022-07 22:07 | Fairhope, AL | 2020 Tesla Model 3 | ADAS | SUV | Unknown | 25 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-3362 v2 | Level 2 | Tesla, Inc. | 2022-07 14:04 | Chicago, IL | 2015 Tesla Model S | ADAS | Unknown | Unknown | 23 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-3363 v2 | Level 2 | Tesla, Inc. | 2022-07 02:50 | Marietta, GA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 14 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3365 v2 | Level 2 | Tesla, Inc. | 2022-07 01:03 | Los Angeles, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 80 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3366 v2 | Level 2 | Tesla, Inc. | 2022-07 21:16 | Dallas, TX | 2018 Tesla Model S | ADAS | Pickup Truck | Unknown | 45 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3390 v2 | Level 2 | Tesla, Inc. | 2022-07 20:55 | Silver Lake, WI | 2020 Tesla Model X | ADAS | Unknown | Unknown | 62 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-3424 v2 | Level 2 | Tesla, Inc. | 2022-07 22:58 | Los Angeles, CA | 2020 Tesla Model 3 | ADAS | Passenger Car | Unknown | 35 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3425 v2 | Level 2 | Tesla, Inc. | 2022-07 17:06 | Irondale, AL | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 47 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3449 v2 | Level 2 | Tesla, Inc. | 2022-07 | Naperville, IL | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 47 | Street | Redacted by NHTSA as confidential business information |
| 13781-3457 v2 | Level 2 | Tesla, Inc. | 2022-07 21:51 | Long Beach, CA | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 59 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3458 v2 | Level 2 | Tesla, Inc. | 2022-07 21:27 | Atwater, CA | 2021 Tesla Model Y | ADAS | Passenger Car | Unknown | 20 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3459 v2 | Level 2 | Tesla, Inc. | 2022-07 09:47 | Freedom Township, OH | 2020 Tesla Model Y | ADAS | Unknown | Unknown | 35 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3460 v2 | Level 2 | Tesla, Inc. | 2022-07 14:28 | Sausalito, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 96 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3461 v2 | Level 2 | Tesla, Inc. | 2022-07 11:24 | South Riding, VA | 2020 Tesla Model 3 | ADAS | Unknown | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3462 v2 | Level 2 | Tesla, Inc. | 2022-07 05:40 | San Ygnacio, TX | 2021 Tesla Model 3 | ADAS | Pole / Tree | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3463 v2 | Level 2 | Tesla, Inc. | 2022-07 04:21 | Land O' Lakes, FL | 2020 Tesla Model 3 | ADAS | Unknown | Unknown | 34 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-3467 v2 | Level 2 | Tesla, Inc. | 2022-07 15:43 | Upton, KY | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3468 v2 | Level 2 | Tesla, Inc. | 2022-07 22:14 | Falmouth, VA | 2016 Tesla Model S | ADAS | Unknown | Unknown | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3469 v2 | Level 2 | Tesla, Inc. | 2022-07 00:28 | Afton, NY | 2021 Tesla Model 3 | ADAS | Unknown | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3480 v2 | Level 2 | Tesla, Inc. | 2022-07 00:47 | Avondale, AZ | 2015 Tesla Model S | ADAS | Unknown | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3485 v2 | Level 2 | Tesla, Inc. | 2022-07 04:20 | UNK | 2018 Tesla Model S | ADAS | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-3488 v2 | Level 2 | Tesla, Inc. | 2022-07 07:08 | Bluffdale, UT | 2020 Tesla Model 3 | ADAS | Motorcycle | Fatality | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3489 v2 | Level 2 | Tesla, Inc. | 2022-07 18:58 | Pleasant Hill, CA | 2018 Tesla Model X | ADAS | Unknown | Unknown | 79 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3490 v2 | Level 2 | Tesla, Inc. | 2022-07 20:54 | Athens, NY | 2016 Tesla Model S | ADAS | Unknown | Unknown | 55 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-3506 v2 | Level 2 | Tesla, Inc. | 2022-07 14:47 | Diamond Bar, CA | 2016 Tesla Model X | ADAS | Unknown | Unknown | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3509 v2 | Level 2 | Tesla, Inc. | 2022-07 14:52 | Orlando, FL | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3510 v2 | Level 2 | Tesla, Inc. | 2022-07 21:29 | Creola, AL | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 78 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3511 v2 | Level 2 | Tesla, Inc. | 2022-07 13:01 | Dallas, TX | 2021 Tesla Model 3 | ADAS | Pickup Truck | Unknown | 44 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-3512 v2 | Level 2 | Tesla, Inc. | 2022-07 09:14 | Camarillo, CA | 2020 Tesla Model 3 | ADAS | Unknown | Unknown | 34 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-3517 v2 | Level 2 | Tesla, Inc. | 2022-07 19:29 | Sandia Park, NM | 2019 Tesla Model 3 | ADAS | SUV | Unknown | 20 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-3518 v2 | Level 2 | Tesla, Inc. | 2022-07 09:36 | Dallas, TX | 2017 Tesla Model X | ADAS | First Responder Vehicle | Unknown | 15 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 28349-3493 v4 | Level 2 | Lucid USA, Inc. | 2022-07 03:58 | Belmont, CA | 2022 Lucid Dream | ADAS | Passenger Car | No Injuries Reported | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30270-3323 v2 | ADS | Waymo LLC | 2022-07 15:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | The content of this report is unchanged from the initial report submitted on July [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 3:26 PM PST a Waymo Autonomous Vehicle (Way…The content of this report is unchanged from the initial report submitted on July [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 3:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it detected a siren from a nearby emergency vehicle. As the Waymo AV slowed, a passenger vehicle 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 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 Eastern time zone on the required date. |
| 30270-3324 v2 | ADS | Waymo LLC | 2022-07 00:57 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | Unknown | 0 | Street | The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 12:57 AM PST a Waymo Autonomous Vehicle ("Wa…The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 12:57 AM PST a Waymo Autonomous Vehicle ("Waymo AV") was traveling eastbound on [XXX] in autonomous mode when a pedestrian entered the roadway from the center median. The test driver then disengaged autonomous mode and braked to a stop as the pedestrian began to run toward the Waymo AV. The pedestrian stood in front of the vehicle, then jumped onto the hood of the Waymo AV and used their body to break the Waymo AV's windshield. The pedestrian was apprehended soon after by nearby police. The Waymo AV test driver was not physically injured but was taken to a nearby hospital out of an abundance of caution. The Waymo AV sustained major damage to its windshield. Waymo is reporting this event to ensure official notification to the agency of a notable event. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-3338 v2 | ADS | Waymo LLC | 2022-07 09:04 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 13 | Intersection | The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waym…The content of this report is unchanged from the initial report submitted on July [XXX] 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode and turning left onto eastbound [XXX]. As the Waymo AV initiated the left turn, a passenger vehicle that had been following the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers 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 and the Waymo AV test driver reported minor injuries. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Eastern time zone on the required date. |
| 30270-3625 | ADS | Waymo LLC | 2022-07 10:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Parking Lot | On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]. The Waymo AV came to a stop whil…On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]. The Waymo AV came to a stop while yielding for an oncoming van in a narrow passageway in a parking lot. While attempting to pass the Waymo AV, the van made contact with the sensor housing on the left rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was stationary and 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. 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 Eastern time zone on the required date. |
| 30270-3628 | ADS | Waymo LLC | 2022-07 06:54 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 0 | Intersection | On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on the [XXX] at [XXX]. The Waymo AV was stopped in the dedicat…On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on the [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane facing north on the [XXX], awaiting a green signal for a protected left turn onto [XXX]. The signal for traffic proceeding north on the [XXX] turned green, and traffic in adjacent lanes began moving. The left turn arrow signal for the dedicated turn lane occupied by the Waymo AV remained red. The passenger car that had been stopped directly behind the Waymo AV began moving forward. The front of the passenger car made contact with the rear of the Waymo AV, immediately after which the passenger car 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 minor damage and the Waymo AV test driver reported lower back pain. 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 Eastern time zone on the required date. |
| 30270-3633 | ADS | Waymo LLC | 2022-07 23:23 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 9 | Street | On July [XXX], 2022 at 11:23 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 traveling north on [XXX] i…On July [XXX], 2022 at 11:23 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 traveling north on [XXX] in the rightmost lane when a passenger car approached the Waymo AV from behind on the left. Just after passing the Waymo AV, the passenger car veered across the path of the Waymo AV into the entrance of a gas station on the right hand side of the roadway. The right rear corner of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car 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 Eastern time zone on the required date. |
| 30270-3635 | ADS | Waymo LLC | 2022-07 02:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 12 | Intersection | On July [XXX], 2022 at 2:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and…On July [XXX], 2022 at 2:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and preparing to make a left turn onto [XXX] to travel south. A passenger car passed the Waymo AV and the vehicle directly behind the Waymo AV by crossing into and driving in the opposing lane of traffic. As the passenger vehicle passed the Waymo on the left, the right side of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. At the time of 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 Eastern time zone on the required date. |
| 30270-3636 | ADS | Waymo LLC | 2022-07 02:50 | Tempe, AZ | 2017 Chrysler Pacifica | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was st…On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was stopped to pick up a passenger when a passenger vehicle, parked perpendicular and to the right of the Waymo AV, reversed out of a parking spot. The rear of the passenger vehicle made contact with the front passenger side corner of the Waymo AV as the passenger was closing the door on the driver side of the Waymo AV prior to fastening their seat belt. 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. This report was submitted from the Eastern time zone on the required date. |
| 30330-3482 v2 | ADS | TORC Robotics, Inc. | 2022-07 16:33 | ALBUQUERQUE, NM | 2021 FREIGHTLINER CASCADIA | ADS | Other, see Narrative | No Injuries Reported | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30330-3561 | ADS | TORC Robotics, Inc. | 2022-07 12:39 | Santa Rosa, NM | 2021 FREIGHTLINER CASCADIA | ADS | Other, see Narrative | No Injuries Reported | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30412-3580 | ADS | Cruise LLC | 2022-07 2:57 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-3581 | ADS | Cruise LLC | 2022-07 22:46 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 6 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-3582 | ADS | Cruise LLC | 2022-07 1:39 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 12 | Street | Redacted by NHTSA as confidential business information |
| 30412-3584 | ADS | Cruise LLC | 2022-07 00:27 | San Francisco, CA | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30531-3328 v2 | OTHER | Transdev Alternative Services | 2022-07 15:26 | San Francisco, CA | 2021 Jaguar I-Pace | Unknown, see Narrative | Passenger Car | No Injuries Reported | 3 | Intersection | The content of this report is unchanged from the initial report submitted. On July [XXX], 2022 at 3:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger …The content of this report is unchanged from the initial report submitted. On July [XXX], 2022 at 3:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it detected a siren from a nearby emergency vehicle. As the Waymo AV slowed, a passenger vehicle 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 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 to the report submitted by Waymo LLC WaymoLLC-[XXX]. |
| 30531-3329 v2 | OTHER | Transdev Alternative Services | 2022-07 00:57 | Tempe, AZ | 2021 Jaguar I-Pace | Unknown, see Narrative | Other, see Narrative | Unknown | 0 | Street | The content of this report is unchanged from the initial report submitted. On July [XXX], 2022 at 12:57 AM PST a Waymo Autonomous Vehicle (Waymo AV) was traveling eastbound on [XXX] in autonomous mode when a pedestrian e…The content of this report is unchanged from the initial report submitted. On July [XXX], 2022 at 12:57 AM PST a Waymo Autonomous Vehicle (Waymo AV) was traveling eastbound on [XXX] in autonomous mode when a pedestrian entered the roadway from the center median. The test driver then disengaged autonomous mode and braked to a stop as the pedestrian began to run toward the Waymo AV. The pedestrian stood in front of the vehicle, then jumped onto the hood of the Waymo AV and used their body to break the Waymo AVs windshield. The pedestrian was apprehended soon after by nearby police. The Waymo AV test driver was not physically injured but was taken to a nearby hospital out of an abundance of caution. The Waymo AV sustained major damage to its windshield. Transdev Alternative Services is reporting this event to ensure official notification to the agency of a notable event. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-[XXX]. |
| 30531-3342 v2 | ADS | Transdev Alternative Services | 2022-07 9:04 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 13 | Intersection | The content of this report is unchanged from the original report. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on…The content of this report is unchanged from the original report. On July [XXX], 2022 at 9:04 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode and turning left onto eastbound [XXX]. As the Waymo AV initiated the left turn, a passenger vehicle that had been following the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers 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 and the Waymo AV test driver reported minor injuries. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX]. |
| 30531-3661 | ADS | Transdev Alternative Services | 2022-07 02:50 | Tempe, AZ | 2017 Chrysler Pacifica | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehice ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was s…On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehice ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was stopped to pick up a passenger when a passenger vehicle, parked perpendicular and to the right of the Waymo AV, reversed out of a parking spot. The rear of the passenger vehicle made contact with the front passenger side corner of the Waymo AV as the passenger was closing the door on the driver side of the Waymo AV prior to fastening their seat belt. 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 30270-3636-1. |
| 30531-3662 | ADS | Transdev Alternative Services | 2022-07 02:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 12 | Intersection | On July [XXX], 2022 at 2:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and…On July [XXX], 2022 at 2:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and preparing to make a left turn onto [XXX] to travel south. A passenger car passed the Waymo AV and the vehicle directly behind the Waymo AV by crossing into and driving in the opposing lane of traffic. As the passenger vehicle passed the Waymo on the left, the right side of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. At the time of 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 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 30270-3635-1. |
| 30531-3663 | ADS | Transdev Alternative Services | 2022-07 23:23 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 9 | Street | On July [XXX], 2022 at 11:23 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 traveling north on [XXX] i…On July [XXX], 2022 at 11:23 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 traveling north on [XXX] in the rightmost lane when a passenger car approached the Waymo AV from behind on the left. Just after passing the Waymo AV, the passenger car veered across the path of the Waymo AV into the entrance of a gas station on the right hand side of the roadway. The right rear corner of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. 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 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 30270-3633-1. |
| 30531-3664 | ADS | Transdev Alternative Services | 2022-07 06:54 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 0 | Intersection | On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehice (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on the [XXX] at [XXX]. The Waymo AV was stopped in the dedicated…On July [XXX], 2022 at 6:54 AM PST a Waymo Autonomous Vehice (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on the [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane facing north on the [XXX], awaiting a green signal for a protected left turn onto [XXX]. The signal for traffic proceeding north on the [XXX] turned green, and traffic in adjacent lanes began moving. The left turn arrow signal for the dedicated turn lane occupied by the Waymo AV remained red. The passenger car that had been stopped immediately after which the passenger car left the scene. 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 and the Waymo AV test driver reported lower back pain. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3628-1. |
| 30531-3665 | ADS | Transdev Alternative Services | 2022-07 10:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Parking Lot | On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]t. The Waymo AV came to a stop while…On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]t. The Waymo AV came to a stop while yielding for an oncoming van in a narrow passageway in a parking lot. While attempting to pass the Waymo AV, the van made contact with the sensor housing on the left rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was stationary and 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 of 30270-3625-1. |
| 30610-3508 v2 | ADS | Zoox, Inc. | 2022-07 14:30 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, Ca when a passenger vehicle turning left from [XXX] on to [XXX] struck the rear of the Zoox vehicle damaging the sensors. There were no injuri…A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, Ca when a passenger vehicle turning left from [XXX] on to [XXX] struck the rear of the Zoox vehicle damaging the sensors. There were no injuries and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. |
| 540-3643 | ADS | General Motors, LLC | 2022-07 2:57 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On August [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-…On August [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-3580-1) |
| 540-3644 | ADS | General Motors, LLC | 2022-07 22:46 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 6 | Intersection | On August [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-…On August [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-3581-1) |
| 540-3645 | ADS | General Motors, LLC | 2022-07 1:39 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 12 | Street | On August [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…On August [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-3582-1) |
| 540-3647 | ADS | General Motors, LLC | 2022-07 00:27 | San Francisco, CA | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 0 | Street | On August [XXX], GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On August [XXX], 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-3584-1) |
| 62-3538 | Level 2 | Honda (American Honda Motor Co.) | 2022-07 | Chicago, IL | 2020 Honda Civic | Unknown, see Narrative | Pickup Truck | No Injuries Reported | Highway / Freeway | The customer reported that a speeding truck rear-ended him while driving on a highway. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged. | |
| 945-3951 v2 | Level 2 | Nissan North America, Inc. | 2022-07 17:00 | UNK | 2021 Nissan Rogue SV | ADAS | Other Fixed Object | Minor | 45 | Unknown | 8/[XXX]/2022: The customer called Consumer Affairs to report an incident on 7/[XXX]/2022. The customer alleged an "autopilot malfunction" caused the vehicle to move to the opposite side of traffic flow and hit two curves…8/[XXX]/2022: The customer called Consumer Affairs to report an incident on 7/[XXX]/2022. The customer alleged an "autopilot malfunction" caused the vehicle to move to the opposite side of traffic flow and hit two curves. There was no report of transport to a hospital for medical treatment, fatality, vehicle tow-away, air bag deployment, or vulnerable road user. Customer refused to respond to additional questions to schedule an inspection and terminated the call. 9/[XXX]/2022: The customer called Consumer Affairs alleging that while traveling 45-47 mph she attempted to disengage "autopilot" by pressing the brake in order to make a left turn. The speed was not reduced and the vehicle traveled to the left side of the road in the oncoming lane and hit the curb with the left side of the vehicle. There was no report of transport to a hospital for medical treatment, fatality, vehicle tow-away, air bag deployment, or vulnerable road user. 10/[XXX]/2022: The customer was called by Consumer Affairs to discuss a vehicle inspection. During the call, she reported the vehicle hit some items on the side of the road, the wheels were bent, and the driver's door would not open properly. The customer reported that the vehicle was towed and that repairs are close to being completed. In addition, she reported that although she was not injured, she went to the doctor and hospital for exacerbation of pre-existing conditions. 10/[XXX]/2022 Update: On October [XXX], 2022, Nissan inspected the vehicle at an independent repair facility, which is the location that the customer had the vehicle directly towed to after the incident. From pictures provided by the repair facility, Nissan identified possible damage to the center of the vehicle's left front wheel, a broken lower front control arm, a bent tie rod end, and the strut. No other incident-related body damage is visible in the photographs. The photos appear to show that the vehicle experienced a localized impact to the wheel, which generated force into in the location of the lower control arm. During Nissan's in-person inspection of the vehicle, the vehicle repairs were near completion. In particular, the left front wheel was not available to Nissan at the time of inspection. Vehicle mileage at the time of inspection was 14,326. No data retrieval or ECU resets were performed by Nissan. As of this report, the vehicle has not been taken to a Nissan dealer. Based on the photos reviewed and Nissan's inspection, the localized impact was insufficient to trigger an EDR recordable event. Therefore, Nissan is unable to determine customer inputs to the vehicle at the time of the incident. Separately, no event was recorded within the PPA system, indicating that PPA was not active at the time of the event. |
| 945-4252 | Level 2 | Nissan North America, Inc. | 2022-07 17:00 | Grovetown, GA | 2021 Nissan Rogue SV | ADAS | Other Fixed Object | Minor | 45 | Unknown | 8/[XXX]/2022: The customer called Consumer Affairs to report an incident on 7/[XXX]/2022. The customer alleged an autopilot malfunction caused the vehicle to move to the opposite side of traffic flow and hit two curves. …8/[XXX]/2022: The customer called Consumer Affairs to report an incident on 7/[XXX]/2022. The customer alleged an autopilot malfunction caused the vehicle to move to the opposite side of traffic flow and hit two curves. There was no report of transport to a hospital for medical treatment, fatality, vehicle tow-away, air bag deployment, or vulnerable road user. Customer refused to respond to additional questions to schedule an inspection and terminated the call. 9/[XXX]/2022: The customer called Consumer Affairs alleging that while traveling 45-47 mph she attempted to disengage autopilot by pressing the brake in order to make a left turn. The speed was not reduced and the vehicle traveled to the left side of the road in the oncoming lane and hit the curb with the left side of the vehicle. There was no report of transport to a hospital for medical treatment, fatality, vehicle tow-away, air bag deployment, or vulnerable road user. 10/[XXX]/2022: The customer was called by Consumer Affairs to discuss a vehicle inspection. During the call, she reported the vehicle hit some items on the side of the road, the wheels were bent, and the drivers door would not open properly. The customer reported that the vehicle was towed and that repairs are close to being completed. In addition, she reported that although she was not injured, she went to the doctor and hospital for exacerbation of pre-existing conditions. On October [XXX], 2022, Nissan inspected the vehicle at an independent repair facility, which is the location that the customer had the vehicle directly towed to after the incident. From pictures provided by the repair facility, Nissan identified possible damage to the center of the vehicles left front wheel, a broken lower front control arm, a bent tie rod end, and the strut. No other incident-related body damage is visible in the photographs. The photos appear to show that the vehicle experienced a localized impact to the wheel, which generated force into in the location of the lower control arm. During Nissans in-person inspection of the vehicle, the vehicle repairs were near completion. In particular, the left front wheel was not available to Nissan at the time of inspection. Vehicle mileage at the time of inspection was 14,326. No data retrieval or ECU resets were performed by Nissan. As of this report, the vehicle has not been taken to a Nissan dealer. Based on the photos reviewed and Nissans inspection, the localized impact was insufficient to trigger an EDR recordable event. Therefore, Nissan is unable to determine customer inputs to the vehicle at the time of the incident. Separately, no event was recorded within the PPA system, indicating that PPA was not active at the time of the event. November [XXX], 2022: Based on the information provided from the customer, the PPA system was not being used on a limited access road, which is outside of the limitations of the ODD. |
| 10039-3261 v4 | Level 2 | BMW of North America, LLC | 2022-06 13:27 | Watermill, NY | 2022 BMW 540i | Unknown, see Narrative | Heavy Truck | Minor | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 1243-4332 v2 | Level 2 | Subaru of America, Inc. | 2022-06 12:24 | Younger Creek, KY | 2021 Subaru Outback | ADAS | Animal | No Injuries Reported | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1306-3573 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2022-06 07:00 | Fairfield, TX | 2021 Toyota Sienna HV | ADAS | Passenger Car | Unknown | 77 | Highway / Freeway | One June [XXX], 2022 Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. At the time of initial contact and description of the incident,…One June [XXX], 2022 Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. At the time of initial contact and description of the incident, no allegations related to the operation of Lane Trace Assist, lane centering, or ADAS L2 functions were communicated. On July [XXX], 2022 a field report regarding this crash incident was completed. On August [XXX], as part of a review of a field report created for the incident, Toyota became aware of vehicle data indicating that the vehicle was operating with ADAS L2 engagement in the moments leading up to the crash event. Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) data from the subject vehicle. VCH provides an approximately 6.75 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 observed: Dynamic Radar Cruise Control (DRCC) and Lane Trace Assist (LTA) were engaged during the recording until approximately 1.75 seconds prior to the crash event, at which point the Pre-Collision System Alarm activated, disengaging the DRCC and LTA. The vehicle was traveling at approximately 77 MPH prior to the crash event. The owner of the subject vehicle alleged that the passenger vehicle it impacted was "a slow moving vehicle." As a result of the crash incident, multiple airbags deployed in the subject vehicle and it was towed away from the scene. Injuries to occupants of the subject vehicle were described by the owner as: Driver: bruising, Front Passenger: burst fracture in spine, Rear Passenger 1: Bruising, Rear Passenger 2: Bruising. This report is a 10 Day update. The original report ID is 1306-3573-1. |
| 13781-3077 v2 | Level 2 | Tesla, Inc. | 2022-06 13:56 | Carrboro, NC | 2015 Tesla Model S | ADAS | Unknown | Unknown | 36 | 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.