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
Clear filters

127 reports, showing 101 to 127.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
30413-1206ADSMay Mobility2021-08 11:16Indianapolis, IN2020 Lexus RX450HADSOther, see NarrativeNo Injuries Reported6Street
Vehicle made a right turn and struck the curb, causing a blown tire. Vehicle elected a controller path mid corner, which caused the curb strike. We have assessed the localities where this could occur and are taking those…Vehicle made a right turn and struck the curb, causing a blown tire. Vehicle elected a controller path mid corner, which caused the curb strike. We have assessed the localities where this could occur and are taking those turns in manual operation. We are currently testing a fix that will make our controller more aware of the curb to prevent future occurrences.
30413-1207ADSMay Mobility2021-08 11:30Ann Arbor, MI2020 Lexus RX450HADSOther, see NarrativeNo Injuries Reported22Street
Vehicle was moving forward and veered slightly to the left, making contact with the curb, resulting in a blown tire. Curb strike occurred during testing. There was human error involved in defining the desired vehicle pos…Vehicle was moving forward and veered slightly to the left, making contact with the curb, resulting in a blown tire. Curb strike occurred during testing. There was human error involved in defining the desired vehicle pose in the lane, which led to a curb strike. We have since resolved this by fixing the desired pose.
30490-1314ADSBeep, Inc.2021-08 17:00Mammoth, WY2019 Local Motors Olli 1.0ADSPassenger CarNo Injuries Reported7Parking Lot
A Local Motors electric Olli shuttle (V1.0), VIN equipped with the Robotic Research autonomy kit (enabling autonomous steering, acceleration, deceleration, and braking (AutoDrive)), was proceeding forward in autonomous m…A Local Motors electric Olli shuttle (V1.0), VIN equipped with the Robotic Research autonomy kit (enabling autonomous steering, acceleration, deceleration, and braking (AutoDrive)), was proceeding forward in autonomous mode through a parking lot in Yellowstone National Park. A parked passenger vehicle began reversing into the path of the Olli without signaling or yielding the right of way to oncoming shuttle. The autonomy system detected the encroaching vehicle and commanded a braking event, which began deceleration of the Olli. Though the Olli was nearly stopped by the time the of the accident, a collision still occurred, causing damage to the right rear of the passenger vehicle. For reference this incident is under review with the Box-7 Team at NHTSA.
30531-1191 v3ADSTransdev Alternative Services2021-08 17:41San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported2Street
On August [XXX], 2021 at 5:21PM, PDT, Waymo autonomous vehicles (Waymo AV) operating in San Francisco, was involved in a collision with a parked unoccupied passenger vehicle at [XXX]. While performing a multi point turn …On August [XXX], 2021 at 5:21PM, PDT, Waymo autonomous vehicles (Waymo AV) operating in San Francisco, was involved in a collision with a parked unoccupied passenger vehicle at [XXX]. While performing a multi point turn and the North end of [XXX] (a dead end read) the Waymo AV was in reverse at approximately 2mph, when it made contact with front driver side door of the the unoccupied parked passenger vehicle. The Waymo AV was in autonomous mode just before making contact, when the test drivers transitioned the vehicle back to manual mode. The contact caused minor scuffing and a small dent to the door handle on the drivers side door, and minor damage to the plastic sensor housing of the Waymo AV's rear passenger side. Transdev Alternative Services is reporting this under the request of No. 1 of the Standing General Order 2021-01 also as a duplicate report to the report submitted by Waymo LLC-202108[XXX]-0 (rev. 202109[XXX]223124). Transdev may correct or supplement it's reporting with additional information as it may become available. No monthly update to narrative.
30531-1326ADSTransdev Alternative Services2021-08 08:04San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported2Street
On August [XXX], 2021 at 8:04 AM PDT, a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco was in a collision involving a van at [XXX] and [XXX]. While in manual mode and traveling northwest on [XXX], the W…On August [XXX], 2021 at 8:04 AM PDT, a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco was in a collision involving a van at [XXX] and [XXX]. While in manual mode and traveling northwest on [XXX], the Waymo AV was approaching slower lead traffic at the stop sign intersection at [XXX]. As the Waymo AV's operator (in the driver's seating position) slowed the Waymo AV, a van made contact with the rear of the Waymo AV. The Waymo AV sustained minor damage to the underside of its rear bumper; the van did not appear to sustain 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.
30531-1327ADSTransdev Alternative Services2021-08 16:15San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On August [XXX], 2021 at 4:15 PM PDT, a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco was in a collision involving a pickup at [XXX] and [XXX]. The Waymo AV was stopped at a red light in autonomous mod…On August [XXX], 2021 at 4:15 PM PDT, a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco was in a collision involving a pickup at [XXX] and [XXX]. The Waymo AV was stopped at a red light in autonomous mode when the pickup behind the Waymo AV made contact with the rear of the Waymo vehicle. The Waymo AV sustained minor damage to the rear bumper. The pickup appeared to sustain minor scuffing. 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.
30531-1328ADSTransdev Alternative Services2021-08 07:30San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported8Intersection
On August [XXX], 2021 at 7:30 AM PDT, a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup near the intersection of [XXX] at [XXX]. The Waymo AV was stopped…On August [XXX], 2021 at 7:30 AM PDT, a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup near the intersection of [XXX] at [XXX]. The Waymo AV was stopped near the end of [XXX] toward [XXX] after having executed a pull-over in autonomous mode, at which time the operator of the Waymo AV took manual control of the Waymo AV and proceeded into the driving lane. The Waymo AV then made contact with the right rear fender of a pickup passing the Waymo AV on the left side. Both vehicles incurred 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.
30531-33 v3ADSTransdev Alternative Services2021-08 16:48San Francisco, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported1IntersectionNo update to narrative. Please refer to Transdev report - TransdevAl-202108[XXX]-0 (rev.202108[XXX]111749) submitted on Aug, 4th, 2021.
30610-1091ADSZoox, Inc.2021-08 22:18Las Vegas, NV2016 Toyota HighlanderADSPassenger CarNo Injuries Reported5Street
A Zoox vehicle was in autonomous mode within its ODD (SAE L3), then transitioned out of its ODD into manual mode 10 seconds before the contact in the right-turn lane while making a right from [XXX] onto [XXX]. As the Zoo…A Zoox vehicle was in autonomous mode within its ODD (SAE L3), then transitioned out of its ODD into manual mode 10 seconds before the contact in the right-turn lane while making a right from [XXX] onto [XXX]. As the Zoox driver inched out to see traffic,?the Zoox?vehicle made contact with the passenger vehicle ahead.
30690-1286ADSRobotic Research2021-08 20:00Yellowstone National Park, WY2019 Local Motors OlliADSPassenger CarNo Injuries Reported8Parking Lot
A Local Motors electric Olli shuttle (V1.0) (VIN Number [XXX]), equipped with the Robotic Research autonomy kit (enabling autonomous steering, acceleration, deceleration, and braking (AutoDrive)), was proceeding forward …A Local Motors electric Olli shuttle (V1.0) (VIN Number [XXX]), equipped with the Robotic Research autonomy kit (enabling autonomous steering, acceleration, deceleration, and braking (AutoDrive)), was proceeding forward in autonomous mode through a parking lot in Yellowstone National Park. A parked passenger vehicle began reversing into the path of the Olli without signaling or yielding the right of way to oncoming shuttle. The autonomy system detected the encroaching vehicle and commanded a braking event, which began deceleration of the Olli. Though the Olli was nearly stopped by the time the of the accident, a collision still occurred, causing damage to the right rear of the passenger vehicle. The safety operator inside the Olli also pulled the handbrake when they became aware of the oncoming collision, but this was not performed in time to avoid the collision. For reference this incident is under review with the Box-7 Team at NHTSA.
30830-1297ADSLocal Motors Industries2021-08WY2019 OLLI 1.0ADSPassenger CarNo Injuries Reported6Parking Lot
A Local Motors electric Olli shuttle (V1.0), equipped with the Robotic Research autonomy kit (enabling autonomous steering, acceleration, deceleration, and braking (AutoDrive)), was proceeding forward in autonomous mo…A Local Motors electric Olli shuttle (V1.0), equipped with the Robotic Research autonomy kit (enabling autonomous steering, acceleration, deceleration, and braking (AutoDrive)), was proceeding forward in autonomous mode through a parking lot in Yellowstone National Park. A parked passenger vehicle began reversing into the path of the Olli without signaling or yielding the right of way to the oncoming shuttle. The autonomy system detected the encroaching vehicle and commanded a braking event, which began deceleration of the Olli. Though the Olli was nearly stopped by the time the of the accident, a collision still occurred, causing damage to the right rear of the passenger vehicle. For reference this incident is under review with the Box-7 Team at NHTSA.
540-1517 v2ADSGeneral Motors, LLC2021-08 12:58San Francisco, CA2020 Chevrolet BoltADSPickup TruckNo Injuries Reported22Intersection
On July 12, 2024, GM Cruise Holdings LLC (Cruise) filed an updated Incident Report (the Report) under the Standing General Order 2021-01 dated June 29, 2021 (the Order). General Motors LLC (GM) manufactured the Cruise-ow…On July 12, 2024, GM Cruise Holdings LLC (Cruise) filed an updated Incident Report (the Report) under the Standing General Order 2021-01 dated June 29, 2021 (the Order). General Motors LLC (GM) manufactured the Cruise-owned and operated motor vehicle involved in the alleged 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: [XXX].
1306-1065ADSToyota Motor Engineering & Manufacturing2021-07 16:15Indianapolis, IN2020 Lexus RX450HADSSUVNo Injuries Reported18Street
- The subject vehicle of this report was procured by and up-fitted to ADS L4 by May Mobility with a May Mobility automated driving kit. - The content of this report, including the summary of incident below, is the inform…- The subject vehicle of this report was procured by and up-fitted to ADS L4 by May Mobility with a May Mobility automated driving kit. - The content of this report, including the summary of incident below, is the information as Toyota received from May Mobility on Aug [XXX], 2021. Summary of incident (as Toyota received from May Mobility): Leading up to the event, the autonomy system functioned as expected, following the route through the intersection, slowing appropriately for other road users and the red light. Vehicle autonomous behavior was performing as expected and did not require a takeover. Description of event: 16:17:30 May vehicle, traveling East on [XXX], in full working order with no errors, autonomously navigates the [XXX] and [XXX] intersection. 16:17:35 May vehicle autonomously begins to slow to match the speed of a vehicle several car lengths ahead merging into our lane from the right. 16:17:37 By means of an accelerator pedal push the vehicle is moved into manual mode by the safety operator - from this point forward, the vehicle remains under control of the safety operator. 16:17:43 Manual acceleration command via the pedal increases. 16:17:44 Safety operator manually continues straight which, due to the slight change in angle of the road, brings the May vehicle into contact with the first vehicle to the right. 16:17:44 Safety operator manually applies brake. 16:17:45 With the manual brake command now at maximum the May vehicle makes contact with the second vehicle. Vehicle indicators for manual or autonomy mode: The visual indicator for autonomy was functioning properly and as expected in the time leading up to and during the event. The audio communication device in the vehicle was functioning properly and was used to call for assistance and to report the incident. The audio beep to indicate a state change was functioning properly. The safety operator had some audio indication that he had exited autonomy and entered manual operation, and he had full visual indication on his dashboard.
30270-1 v2ADSWaymo LLC2021-07 15:10San Francisco, CA2017 Chrysler PacificaADSVanNo Injuries ReportedIntersectionNo update to narrative. Please refer to Waymo LLC Report - 202107[XXX]-0 (rev.202107[XXX]170406) submitted on July [XXX], 2021.
30270-4 v2ADSWaymo LLC2021-07 16:47San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported18StreetNo update to narrative. Please refer to Waymo LLC Report - 202107[XXX]-0 (rev.202107[XXX]170340) submitted on July [XXX], 2021.
30290-1071ADSArgo AI2021-07 16:33Austin, TX2019 Ford FusionADSOther, see NarrativeNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30290-1072ADSArgo AI2021-07 09:50Miami, FL2019 Ford FusionADSPassenger CarNo Injuries Reported2StreetRedacted by NHTSA as confidential business information
30290-15 v2ADSArgo AI2021-07 09:26Washington DC, DC2019 Ford FusionADSPickup TruckMinor0StreetRedacted by NHTSA as confidential business information
30412-1089ADSCruise LLC2021-07 21:38San Francisco, CA2020 Chevrolet BoltADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-16 v2ADSCruise LLC2021-07 13:15San Francisco, CA2020 Cruise AVADSNon-Motorist: OtherMinor13StreetRedacted by NHTSA as confidential business information
30413-1130ADSMay Mobility2021-07 16:15Indianapolis, IN2020 Lexus RX450HADSSUVNo Injuries Reported18Street
Summary of incidentLeading up to the event, the autonomy system functioned as expected, following the route through the intersection, slowing appropriately for other road users and the red light. Vehicle autonomous beha…Summary of incidentLeading up to the event, the autonomy system functioned as expected, following the route through the intersection, slowing appropriately for other road users and the red light. Vehicle autonomous behavior was performing as expected and did not require a takeover.Description of event:16:17:30 May vehicle, traveling East on [XXX], in full working order with no errors, autonomously navigates the [XXX] and [XXX] intersection.16:17:35 May vehicle autonomously begins to slow to match the speed of a vehicle several car lengths ahead merging into our lane from the right.16:17:37 By means of an accelerator pedal push the vehicle is moved into manual mode by the safety operator - from this point forward, the vehicle remains under control of the safety operator.16:17:43 Manual acceleration command via the pedal increases.16:17:44 Safety operator manually continues straight which, due to the slight change in angle of the road, brings the May vehicle into contact with the first vehicle to the right.16:17:44 Safety operator manually applies brake.16:17:45 With the manual brake command now at maximum the May vehicle makes contact with the second vehicle.Vehicle indicators for manual or autonomy mode:The visual indicator for autonomy was functioning properly and as expected in the time leading up to and during the event.The audio communication device in the vehicle was functioning properly and was used to call for assistance and to report the incident.The audio beep to indicate a state change was functioning properly.The safety operator had some audio indication that he had exited autonomy and entered manual operation, and he had full visual indication on his dashboard.
30531-2 v3ADSTransdev Alternative Services2021-07 15:10San Francisco, CA2017 Chrysler PacificaADSVanNo Injuries ReportedIntersectionNo update to narrative. Please refer to Transdev report - TransdevAl-202107[XXX]-0 (rev.202107[XXX]225225) submitted on July, [XXX}, 2021.
30531-6 v3ADSTransdev Alternative Services2021-07 16:47San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported18StreetNo update to narrative. Please refer to Transdev report - TransdevAl-202107[XXX]-0 (rev.202107[XXX]223447) submitted on July, [XXX], 2021.
30610-1080ADSZoox, Inc.2021-07 08:44Las Vegas, NV2016 Toyota HighlanderADSPassenger CarNo Injuries Reported3StreetWhile merging in a slip lane onto [XXX] from [XXX], the Zoox vehicle yielded for left cross traffic. Then the passenger vehicle collided with the Zoox rear bumper. Operators disengaged the autonomous mode after contact.
30610-1083ADSZoox, Inc.2021-07 23:34Las Vegas, NV2016 Toyota HighlanderADSPassenger CarNo Injuries Reported0StreetA Zoox vehicle in autonomy began to slow in traffic and was rear-ended when a?passenger vehicle from behind?changed lanes?and made contact with the Zoox vehicle.
30792-1031ADSWeRide Corp2021-07 11:35San Jose, CA2017 Lincoln MKZADSSUVNo Injuries Reported3Street
At about 11:35 am our vehicle (car 1) was waiting behind a USPS truck to make an unprotected left turn, meanwhile one other vehicle (car 2) waited behind our vehicle. Another non involved vehicle notices the queue of v…At about 11:35 am our vehicle (car 1) was waiting behind a USPS truck to make an unprotected left turn, meanwhile one other vehicle (car 2) waited behind our vehicle. Another non involved vehicle notices the queue of vehicles and passes on the right in the bike lane. As the USPS truck begins to make the turn, car 1 begins to move forward at 7 MPH then slowed to 3 MPH when yielding to the vehicle passing in the bike lane. Car 2 directly behind us strikes our passenger rear bumper. The safety driver then disengaged the vehicle (car 1) and moved into a nearby parking lot to exchange information.
502-18 v2ADSFord Motor Company2021-07 09:26Washington DC, DC2019 Ford FusionADSPickup TruckMinor0StreetRedacted 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. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. 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. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.