The MachineRecord
NHTSA Standing General Order 2021-01

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 7801 to 7900.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
13781-3078 v2Level 2Tesla, Inc.2022-06 17:48Riverside, CA2021 Tesla Model YADASPassenger CarUnknown17Highway / FreewayRedacted by NHTSA as confidential business information
13781-3079 v2Level 2Tesla, Inc.2022-06 02:47Olivette, MO2020 Tesla Model 3ADASUnknownUnknown39StreetRedacted by NHTSA as confidential business information
13781-3104 v2Level 2Tesla, Inc.2022-06 23:16Oakland, CA2016 Tesla Model SADASUnknownUnknown10Highway / FreewayRedacted by NHTSA as confidential business information
13781-3129 v2Level 2Tesla, Inc.2022-06 18:36Pentwater, MI2021 Tesla Model YADASAnimalUnknown70Highway / FreewayRedacted by NHTSA as confidential business information
13781-3130 v2Level 2Tesla, Inc.2022-06 17:00Monsey, NY2021 Tesla Model 3ADASUnknownUnknown33StreetRedacted by NHTSA as confidential business information
13781-3144 v2Level 2Tesla, Inc.2022-06 03:59The Crossings, FL2018 Tesla Model 3ADASPassenger CarUnknown43IntersectionRedacted by NHTSA as confidential business information
13781-3145 v2Level 2Tesla, Inc.2022-06 21:01San Antonio, TX2021 Tesla Model YADASPickup TruckUnknown68Highway / FreewayRedacted by NHTSA as confidential business information
13781-3153 v2Level 2Tesla, Inc.2022-06 20:23Le Sueur, MN2021 Tesla Model YADASUnknownUnknown54Highway / FreewayRedacted by NHTSA as confidential business information
13781-3154 v2Level 2Tesla, Inc.2022-06 16:08Harrisburg, NC2020 Tesla Model 3ADASPickup TruckUnknown26StreetRedacted by NHTSA as confidential business information
13781-3155 v2Level 2Tesla, Inc.2022-06 06:06Blue Springs, MS2021 Tesla Model 3ADASUnknownUnknown68Highway / FreewayRedacted by NHTSA as confidential business information
13781-3171 v2Level 2Tesla, Inc.2022-06 06:10Fremont, CA2015 Tesla Model SADASUnknownUnknown59Highway / FreewayRedacted by NHTSA as confidential business information
13781-3217 v2Level 2Tesla, Inc.2022-06 05:42Escondido, CA2021 Tesla Model 3ADASOther, see NarrativeUnknown18StreetRedacted by NHTSA as confidential business information
13781-3223 v2Level 2Tesla, Inc.2022-06 05:55Duluth, GA2020 Tesla Model 3ADASOther, see NarrativeUnknown65Highway / FreewayRedacted by NHTSA as confidential business information
13781-3230 v2Level 2Tesla, Inc.2022-06 01:20Fremont, CA2018 Tesla Model 3ADASPassenger CarUnknown32StreetRedacted by NHTSA as confidential business information
13781-3231 v2Level 2Tesla, Inc.2022-06 22:54Sherman, TX2020 Tesla Model YADASSUVUnknown26IntersectionRedacted by NHTSA as confidential business information
13781-3233 v2Level 2Tesla, Inc.2022-06 10:27Lower Saucon Township, PA2021 Tesla Model YADASUnknownUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-3248 v2Level 2Tesla, Inc.2022-06 16:34Rapid City, SD2021 Tesla Model YADASPickup TruckUnknown40IntersectionRedacted by NHTSA as confidential business information
13781-3249 v2Level 2Tesla, Inc.2022-06 19:51San Diego, CA2020 Tesla Model XADASPassenger CarUnknown21IntersectionRedacted by NHTSA as confidential business information
13781-3250 v2Level 2Tesla, Inc.2022-06 06:43Austin, TX2018 Tesla Model 3ADASSUVUnknown24IntersectionRedacted by NHTSA as confidential business information
13781-3253 v2Level 2Tesla, Inc.2022-06 21:34Mountain View, CA2021 Tesla Model YADASSUVUnknown25Highway / FreewayRedacted by NHTSA as confidential business information
13781-3257 v2Level 2Tesla, Inc.2022-06 09:51Long Beach, CA2022 Tesla Model 3ADASUnknownUnknown52UnknownRedacted by NHTSA as confidential business information
13781-3258 v2Level 2Tesla, Inc.2022-06 00:29San Ramon, CA2018 Tesla Model 3ADASOther Fixed ObjectUnknown34StreetRedacted by NHTSA as confidential business information
13781-3262 v2Level 2Tesla, Inc.2022-06 02:54Chino, CA2020 Tesla Model 3ADASUnknownUnknown83Highway / FreewayRedacted by NHTSA as confidential business information
13781-3270 v2Level 2Tesla, Inc.2022-06 06:15Ballinger, TX2022 Tesla Model 3ADASUnknownUnknown24UnknownRedacted by NHTSA as confidential business information
13781-3271 v2Level 2Tesla, Inc.2022-06 15:19Elmhurst, IL2021 Tesla Model YADASOther Fixed ObjectUnknown44Highway / FreewayRedacted by NHTSA as confidential business information
13781-3272 v2Level 2Tesla, Inc.2022-06 20:53Tice, FL2021 Tesla Model YADASOther Fixed ObjectUnknown22Highway / FreewayRedacted by NHTSA as confidential business information
13781-3273 v2Level 2Tesla, Inc.2022-06 23:35Mountain View, CA2022 Tesla Model 3ADASUnknownUnknown64Highway / FreewayRedacted by NHTSA as confidential business information
13781-3274 v2Level 2Tesla, Inc.2022-06 14:48San Antonio, TX2019 Tesla Model 3ADASOther Fixed ObjectUnknown64Highway / FreewayRedacted by NHTSA as confidential business information
13781-3275 v2Level 2Tesla, Inc.2022-06 01:09Santa Clara, CA2019 Tesla Model SADASOther Fixed ObjectUnknown31StreetRedacted by NHTSA as confidential business information
13781-3276 v2Level 2Tesla, Inc.2022-06 20:37Las Vegas, NV2022 Tesla Model 3ADASUnknownUnknown62UnknownRedacted by NHTSA as confidential business information
13781-3285 v2Level 2Tesla, Inc.2022-06 18:40Green River, UT2021 Tesla Model YADASOther Fixed ObjectUnknown51Highway / FreewayRedacted by NHTSA as confidential business information
13781-3288 v2Level 2Tesla, Inc.2022-06 08:24Torrance, CA2015 Tesla Model SADASUnknownUnknown78UnknownRedacted by NHTSA as confidential business information
13781-3295 v2Level 2Tesla, Inc.2022-06Middletown, NJ2022 Tesla Model 3ADASUnknownUnknownUnknownRedacted by NHTSA as confidential business information
13781-3513 v2Level 2Tesla, Inc.2022-06 00:06NJ2018 Tesla Model 3ADASUnknownFatalityUnknownRedacted by NHTSA as confidential business information
13781-6214Level 2Tesla, Inc.2022-06 13:08North Andover, MA2022 Tesla Model SADASPassenger CarUnknown4IntersectionRedacted by NHTSA as confidential business information
30270-3255 v2ADSWaymo LLC2022-06 12:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] A Waymo Autonomous Vehicle ("Waymo AV") operating in San Fra…A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] between [XXX] and [XXX]. 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-3435ADSWaymo LLC2022-06 07:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on ea…On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX], a pickup that had previously been stopped behind the Waymo AV rolled forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV 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-3437ADSWaymo LLC2022-06 10:07San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On June [XXX], 2022 at 10:07 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 in autonomous…On June [XXX], 2022 at 10:07 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 in autonomous mode behind stopped traffic facing east on [XXX]. The passenger vehicle ahead of the Waymo AV transitioned into reverse and began to accelerate, making contact with the front sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained 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-3655ADSWaymo LLC2022-06 16:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeMinor18Intersection
On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] a…On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] at [XXX], according to a claim by the driver of the passenger vehicle. The Waymo AV was in autonomous mode and preparing to enter southbound [XXX] via the slip lane at southbound [XXX]. The Waymo AV proceeded to merge onto [XXX] as a passenger vehicle on [XXX] approached from behind. A pickup truck was traveling next to the passenger vehicle in the adjacent left lane. As the passenger vehicle approached the Waymo AV from behind, the passenger vehicle entered the adjacent left lane that was occupied by the pickup truck and maneuvered around the Waymo AV. The pickup truck proceeded without stopping, and the passenger vehicles driver shortly after signaled to the Waymo AV test driver to pull over. The Waymo AV test driver then transitioned to manual mode and pulled over. Waymo has no data or knowledge of any contact between any of the three vehicles. There was no contact or collision between the Waymo AV and any other vehicle. However, the driver and passenger in the passenger vehicle have subsequently alleged injuries based on alleged contact between the pick-up truck and passenger vehicle, which contact their allegations attribute to the behavior of Waymos AV in a bodily injury claim under Waymos insurance policy. Waymo received notice of this insurance claim on July [XXX]. Waymo is reporting this event 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.
30290-3135 v2ADSArgo AI2022-06 16:35Austin, TX2020 Ford EscapeADSNon-Motorist: CyclistNo Injuries Reported0Street2022-06-[XXX] - Submission of 10 Day Update for Report 30290-3135-1: Argo AI has not received notice of any material new or materially different information about this incident.
30290-3346ADSArgo AI2022-06 14:48Miami, FL2020 Ford EscapeADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30290-3347ADSArgo AI2022-06 13:30Pittsburgh, PA2020 Ford EscapeADSSUVNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-3080 v2ADSCruise LLC2022-06 1:54San Francisco, CA2020 Cruise AVADSNon-Motorist: PedestrianUnknown5StreetRedacted by NHTSA as confidential business information
30412-3084 v2ADSCruise LLC2022-06 23:00San Francisco, CA2022 Cruise AVADSPassenger CarMinor0IntersectionRedacted by NHTSA as confidential business information
30412-3281 v2ADSCruise LLC2022-06 10:49San Francisco, CA2020 Cruise AVADSNon-Motorist: CyclistMinor19StreetRedacted by NHTSA as confidential business information
30531-3256 v2ADSTransdev Alternative Services2022-06 12:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. As the Waymo AV turned left and into the parking lot, the Waymo AV's…A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. 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 no 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. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX].
30531-3445ADSTransdev Alternative Services2022-06 7:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on ea…On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX], a pickup that had previously been stopped behind the Waymo AV rolled forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV 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-3446ADSTransdev Alternative Services2022-06 10:07San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On June [XXX], 2022 at 10:07 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 in autonomous…On June [XXX], 2022 at 10:07 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 in autonomous mode behind stopped traffic facing east on [XXX]. The passenger vehicle ahead of the Waymo AV transitioned into reverse and began to accelerate, making contact with the front sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained 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-3660ADSTransdev Alternative Services2022-06 16:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeMinor18Intersection
On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] a…On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] at [XXX], according to a claim by the driver of the passenger vehicle. The Waymo AV was in autonomous mode and preparing to enter southbound [XXX] as a passenger vehicle on [XXX] approached from behind. A pickup truck was traveling next to the passenger vehicle in the adjacent left lane. As the passenger vehicle approached the Waymo AV from behind, the passenger vehicle entered the adjacent left lane that was occupied by the pickup truck and maneuvered around the Waymo AV. The pickup truck proceeded without stopping, and the passenger vehicle's driver shortly after signaled to the Waymo AV test driver to pull over. The Waymo AV test driver then transitioned to manual mode and pulled over. Transdev has no data or knowledge of any contact between any of the three vehicles. There was no contact or collision between the Waymo AV and any other vehicle. However, the driver and passenger in the passenger vehicle have subsequently alleged injuries based on alleged contact between the pick-up truck and passenger vehicle, which contact their allegations attribute to the behavior of Waymo's AV in a bodily injury claim under Waymo's insurance policy. Waymo received notice of this insurance claim on July [XXX]. Transdev Alternative Services is reporting this event 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-3655-1.
30590-3431ADSApple Inc.2022-06 15:15Mountain View, CA2016 Lexus RX 450hADSPassenger CarNo Injuries Reported0Intersection
Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's …Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's designated seating position, and with a safety operator in the front passenger seating position. Subject vehicle approached a red light to make a right turn East-bound onto [XXX]. The safety operator suggested that the safety driver disengage the ADS and make the turn in manual mode because the vehicle was hesitant in approaching the intersection. The safety driver disengaged the ADS, and, approximately 250ms later, subject vehicle was lightly struck from behind by a white Mazda3. Having seen debris on the roadway, the driver and operator believed they had run over a rock and did not realize they were hit by the vehicle. After concluding the mission, the driver and operator found damage to a sensor during an inspection. A subsequent review of video led to discovery of the crash. No injuries were reported, and law enforcement was not called to the scene. In addition to telematics and video, we also have photographs of the vehicle's damaged sensor.
30610-3072 v2ADSZoox, Inc.2022-06 13:15San Francisco, CA2016 Toyota HighlanderADSNon-Motorist: OtherModerate12Intersection
A Zoox vehicle in autonomous mode was proceeding westbound with the right of way on a green traffic light at the six way intersection of [XXX], [XXX], and [XXX], when a person operating an electric scooter ran a red ligh…A Zoox vehicle in autonomous mode was proceeding westbound with the right of way on a green traffic light at the six way intersection of [XXX], [XXX], and [XXX], when a person operating an electric scooter ran a red light and proceeded northbound into the intersection. The scooter made contact with the left rear quarter panel of the Zoox vehicle, at which time the Zoox vehicle had disengaged from autonomous mode. The Zoox vehicle pulled over, and police and emergency services arrived at the scene. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field and to update for additional information received in August 2022. This update provides complete information for this incident.
30610-3215 v2ADSZoox, Inc.2022-06 10:45San Mateo, CA2016 Toyota HighlanderADSSUVNo Injuries Reported6Street
A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the seco…A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the second vehicle and cut in abruptly from the left, making contact with the front left side and sensors of the Zoox vehicle as it was exiting the space. The Zoox operator disengaged to manual mode just before the contact. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
30610-3320ADSZoox, Inc.2022-06 14:36San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported25Street
A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor dama…A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor damage to both vehicles. The Zoox vehicle had disengaged for unrelated traffic within 30 seconds of the contact. There were no injuries and the police were not called.
502-3140 v2ADSFord Motor Company2022-06 16:35Austin, TX2020 Ford EscapeADSNon-Motorist: CyclistNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
502-3413ADSFord Motor Company2022-06 14:48Miami, FL2020 Ford EscapeADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
502-3416ADSFord Motor Company2022-06 13:30Pittsburgh, PA2020 Ford EscapeADSSUVNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
540-3083 v2ADSGeneral Motors, LLC2022-06 1:54San Francisco, CA2020 Cruise AVADSNon-Motorist: PedestrianUnknown5Street
On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3080-2)
540-3085 v2ADSGeneral Motors, LLC2022-06 23:00San Francisco, CA2022 Cruise AVADSPassenger CarMinor0Intersection
On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3084-2)
540-3283 v2ADSGeneral Motors, LLC2022-06 10:49San Francisco, CA2020 Cruise AVADSNon-Motorist: CyclistMinor19Street
On July [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured…On July [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3281-2)
62-3161Level 2Honda (American Honda Motor Co.)2022-06NC2019 Honda PassportUnknown, see NarrativeSUVMinorIntersectionA SUV ran a red light and collided with the drivers side passenger door. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-3280Level 2Honda (American Honda Motor Co.)2022-06Washington, DC2019 Honda CRVUnknown, see NarrativeUnknownNo Injuries ReportedHighway / FreewayThe customer was driving on a highway when another vehicle rear-ended the customer. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-3282Level 2Honda (American Honda Motor Co.)2022-06Mandeville, LA2019 Honda CivicUnknown, see NarrativePickup TruckModerateHighway / Freeway
The customer's son was driving on a 65 miles per hour parkway with the adaptive cruise control engaged when a truck drove in front of the customer's vehicle. The customer alleges that the vehicle did not slow down on its…The customer's son was driving on a 65 miles per hour parkway with the adaptive cruise control engaged when a truck drove in front of the customer's vehicle. The customer alleges that the vehicle did not slow down on its own and did not react to his son pressing on the brakes, causing the customer's son to rear-end the truck. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-3514Level 2Honda (American Honda Motor Co.)2022-06PA2020 Honda CivicUnknown, see NarrativeUnknownNo Injuries ReportedUnknown
The customer reported that another vehicle crashed into his passenger side front wheel, causing him to lose control and hit a guard rail. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control …The customer reported that another vehicle crashed into his passenger side front wheel, causing him to lose control and hit a guard rail. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
669-3126 v3Level 2Hyundai Motor America2022-06 14:20Chikaming Twp, MI2022 Genesis GV70Unknown, see NarrativePassenger CarUnknownStreet
According to testimony provided by the vehicle operator, a HATCI engineer, the subject prototype GV70 vehicle was undergoing an evaluation of different drive modes (ECO, Comfort, Sport, etc) while driving westbound on [X…According to testimony provided by the vehicle operator, a HATCI engineer, the subject prototype GV70 vehicle was undergoing an evaluation of different drive modes (ECO, Comfort, Sport, etc) while driving westbound on [XXX] in the left lane. The roadway condition was allegedly wet due to heavy rain that just subsided to a light drizzle. While approaching a Lincoln vehicle with the Highway Drive Assist ("HDA") engaged, the operator alleged the following: 1) The operator decided to actively brake to disengage the HDA mode. 2) The operator then switched to the right lane successfully. 3) The vehicle's Lane Keep Assist ("LKA") applied steering input during the lane change while the operator manually managed the steering completing the lane change. 4) Within a few seconds of the lane change, the vehicle began to rotate counter-clockwise and the front of the vehicle made contact with the rear passenger side of the Lincoln vehicle in the left lane. 5) After making contact, the GV70 rotated clockwise and travelled off the roadway eventually coming to a stop in a wooded area. The Lincoln vehicle also left the roadway and came to a stop near the GV70 vehicle in the same wooded area. 6) The GV70 vehicle airbags did not deploy during the incident. 7) Police and first responder medical teams arrived at the incident and the GV70 car was towed away. HMA, HATCI, and NHTSA's SCI inspected the vehicle on June [XXX], 2022. An EDR event record was downloaded. The EDR report indicated the Adaptive Cruise Control (ACC) was not engaged within the 5 seconds recorded prior to the crash event. A copy of the EDR report was retained by SCI. Because ACC is a mandatory component of the vehicle's HDA function, the inactive state of the ACC in the EDR report inferred that the HDA was not engaged at the time of crash. A follow-up interview with the vehicle operator was held with members from HMA, HATCI, and NHTSA's SCI. Details obtained during the interview confirmed that neither HDA, nor any other of the vehicle's equipped Level 2 ADAS functionality, was engaged at the time of the crash. Based on this information, Hyundai has determined that this event was not caused or influenced by the operation of any Level 2 ADAS equipped on the subject vehicle. This concludes Hyundai's reporting obligation for this event.
10039-3997 v3Level 2BMW of North America, LLC2022-05 22:25Refugio, TX2020 BMW X5 sDrive40iADASPole / TreeSerious82Highway / FreewayRedacted by NHTSA as confidential business information
1243-3278 v3Level 2Subaru of America, Inc.2022-05 8:36Warrenville Heights, OH2020 Subaru OutbackADASPassenger CarMinor65Highway / Freeway
The customer was not alleging any defect with the vehicle. According to the customer, the subject vehicle was proceeding westbound on [XXX] in Warrenville Heights, Ohio at 65 MPH when it was struck in the right-rear by …The customer was not alleging any defect with the vehicle. According to the customer, the subject vehicle was proceeding westbound on [XXX] in Warrenville Heights, Ohio at 65 MPH when it was struck in the right-rear by another vehicle. During the standard accident questionnaire, the customer indicated that Adaptive Cruise Control and Lane Centering Function were both engaged at the time of collision. The customer is not alleging any vehicle or system defect, and the purpose of the initial call was to compliment the vehicle performance in the incident and inquire about body shop post-repair information. According to the Traffic Crash Report, the subject vehicle was traveling in the left-center lane when it was struck in the rear by a second vehicle. The second vehicle was traveling in the far left lane. The driver of the second vehicle stated that he lost control of the vehicle due to hydroplaning and struck the subject vehicle.
1306-3355ADSToyota Motor Engineering & Manufacturing2022-05 16:11Arlington, TX2020 Lexus RX450HADSPickup TruckNo Injuries Reported11Street
This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 2022. Toyota has no additional information on this…This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned Monthly Report. Please refer to the report from May Mobility for details.
1306-3507 v2Level 2Toyota Motor Engineering & Manufacturing2022-05 18:48Altadena, CA2022 Lexus NX 350ADASSUVUnknown72Highway / Freeway
On June [XXX], 2022 Toyota received an allegation related to this crash incident through a call from the Consumer's insurance provider to the Toyota Brand Engagement Center. At the time of initial contact and description…On June [XXX], 2022 Toyota received an allegation related to this crash incident through a call from the Consumer's insurance provider 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 June [XXX], a field report regarding this crash incident was completed. On [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 7.35 second pre-crash data recording, and EDR provides an approximately 4.9 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 2.55 seconds prior to the crash event, at which point the driver applied the brakes, disengaging the DRCC and LTA. The vehicle was traveling at approximately 72 MPH prior to applying the brakes. As a result of the crash incident, multiple airbags deployed and the vehicle was towed away from the scene. This report is a 10 Day update. The original report ID is 1306-3507-1.
13781-2844 v2Level 2Tesla, Inc.2022-05 22:47Sacramento, CA2018 Tesla Model XADASPassenger CarUnknown35Highway / FreewayRedacted by NHTSA as confidential business information
13781-2846 v2Level 2Tesla, Inc.2022-05 02:41Marlborough, MA2016 Tesla Model SADASUnknownUnknown57Highway / FreewayRedacted by NHTSA as confidential business information
13781-2858 v2Level 2Tesla, Inc.2022-05 01:16Boca Raton, FL2020 Tesla Model 3ADASPassenger CarUnknown34IntersectionRedacted by NHTSA as confidential business information
13781-2868 v2Level 2Tesla, Inc.2022-05 12:20Columbus, OH2020 Tesla Model 3Unknown, see NarrativeOther Fixed ObjectUnknownUnknownRedacted by NHTSA as confidential business information
13781-2873 v2Level 2Tesla, Inc.2022-05 18:44Columbus, OH2021 Tesla Model YADASOther Fixed ObjectUnknown49Highway / FreewayRedacted by NHTSA as confidential business information
13781-2874 v2Level 2Tesla, Inc.2022-05 22:39Salinas, CA2021 Tesla Model YADASPassenger CarUnknownHighway / FreewayRedacted by NHTSA as confidential business information
13781-2877 v2Level 2Tesla, Inc.2022-05 12:23Waukegan, IL2020 Tesla Model YADASUnknownUnknown62Highway / FreewayRedacted by NHTSA as confidential business information
13781-2878 v2Level 2Tesla, Inc.2022-05 02:03West Covina, CA2022 Tesla Model YADASPassenger CarUnknown61Highway / FreewayRedacted by NHTSA as confidential business information
13781-2879 v2Level 2Tesla, Inc.2022-05 13:55Huber Heights, OH2021 Tesla Model YADASOther Fixed ObjectUnknown62Highway / FreewayRedacted by NHTSA as confidential business information
13781-2880 v2Level 2Tesla, Inc.2022-05 06:18Los Angeles, CA2020 Tesla Model 3ADASHeavy TruckUnknown24StreetRedacted by NHTSA as confidential business information
13781-2882 v2Level 2Tesla, Inc.2022-05 22:27Lawnside, NJ2018 Tesla Model SADASOther, see NarrativeUnknown34Highway / FreewayRedacted by NHTSA as confidential business information
13781-2883 v2Level 2Tesla, Inc.2022-05 21:20Panama City Beach, FL2018 Tesla Model 3ADASSUVUnknown46Highway / FreewayRedacted by NHTSA as confidential business information
13781-2905 v2Level 2Tesla, Inc.2022-05 16:46New Salisbury, IN2018 Tesla Model 3ADASSUVUnknown26Rural RoadRedacted by NHTSA as confidential business information
13781-2917 v2Level 2Tesla, Inc.2022-05 05:10Naples, FL2015 Tesla Model SADASUnknownUnknownUnknownRedacted by NHTSA as confidential business information
13781-2924 v2Level 2Tesla, Inc.2022-05 04:00Medford, NY2021 Tesla Model YADASOther, see NarrativeNo Injuries ReportedHighway / FreewayRedacted by NHTSA as confidential business information
13781-2989 v2Level 2Tesla, Inc.2022-05 06:14Milwaukee, WI2016 Tesla Model SADASUnknownUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-2990 v2Level 2Tesla, Inc.2022-05 18:55Framingham, MA2019 Tesla Model SADASSUVUnknown31Highway / FreewayRedacted by NHTSA as confidential business information
13781-2991 v2Level 2Tesla, Inc.2022-05 23:23Darien, CT2021 Tesla Model YADASOther Fixed ObjectUnknown41Highway / FreewayRedacted by NHTSA as confidential business information
13781-3019 v2Level 2Tesla, Inc.2022-05 16:00Romeoville, IL2021 Tesla Model SADASPassenger CarUnknown31StreetRedacted by NHTSA as confidential business information
13781-3020 v2Level 2Tesla, Inc.2022-05 19:35Missoula, MT2021 Tesla Model 3ADASUnknownUnknown39StreetRedacted by NHTSA as confidential business information
13781-3021 v2Level 2Tesla, Inc.2022-05 14:28Phoenix, AZ2018 Tesla Model XADASUnknownUnknown54Highway / FreewayRedacted by NHTSA as confidential business information
13781-3026 v2Level 2Tesla, Inc.2022-05 18:40Mountain View, CA2022 Tesla Model 3ADASSUVUnknown22Highway / FreewayRedacted by NHTSA as confidential business information
13781-3027 v2Level 2Tesla, Inc.2022-05 16:52Franklin Township, PA2018 Tesla Model 3ADASPassenger CarUnknown55IntersectionRedacted by NHTSA as confidential business information
13781-3035 v2Level 2Tesla, Inc.2022-05 20:58San Diego, CA2019 Tesla Model 3ADASSUVUnknown20IntersectionRedacted by NHTSA as confidential business information
13781-3036 v2Level 2Tesla, Inc.2022-05 09:57Inglewood, CA2018 Tesla Model 3ADASOther, see NarrativeUnknown57Highway / FreewayRedacted by NHTSA as confidential business information
13781-3037 v2Level 2Tesla, Inc.2022-05 21:29Tinton Falls School District, NJ2020 Tesla Model YADASOther, see NarrativeUnknown21Highway / FreewayRedacted by NHTSA as confidential business information
13781-3039 v2Level 2Tesla, Inc.2022-05 08:36Rockville, MD2021 Tesla Model YADASOther, see NarrativeUnknown48Highway / FreewayRedacted by NHTSA as confidential business information
13781-3040 v2Level 2Tesla, Inc.2022-05 19:47San Francisco, CA2020 Tesla Model YADASOther, see NarrativeUnknown28Highway / FreewayRedacted by NHTSA as confidential business information
13781-3041 v2Level 2Tesla, Inc.2022-05 21:05Centerville, OH2020 Tesla Model 3ADASPickup TruckUnknown13StreetRedacted by NHTSA as confidential business information
13781-3042 v2Level 2Tesla, Inc.2022-05 20:25Hauppauge, NY2020 Tesla Model 3ADASUnknownUnknown40StreetRedacted by NHTSA as confidential business information
13781-3058 v2Level 2Tesla, Inc.2022-05 18:24Renfro Valley, KY2021 Tesla Model YADASOther Fixed ObjectUnknown60Highway / FreewayRedacted by NHTSA as confidential business information
13781-3059 v2Level 2Tesla, Inc.2022-05 23:34Jackson, MI2018 Tesla Model SADASUnknownUnknown40StreetRedacted 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.