The MachineRecord
Get access
Menu
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
Download these 8612 rows as CSVFull file, all versions

8612 reports, showing 6401 to 6500.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
13781-6701Level 2Tesla, Inc.2023-11 17:48Chino, CA2020 Tesla Model YADASOther Fixed ObjectUnknown64Highway / FreewayRedacted by NHTSA as confidential business information
13781-6703Level 2Tesla, Inc.2023-11 07:25Miami, FL2021 Tesla Model 3ADASSUVUnknown38IntersectionRedacted by NHTSA as confidential business information
13781-6704Level 2Tesla, Inc.2023-11 17:57Carson, CA2023 Tesla Model YADASUnknownUnknown35Highway / FreewayRedacted by NHTSA as confidential business information
13781-6705Level 2Tesla, Inc.2023-11 06:19Escondido, CA2022 Tesla Model YADASUnknownUnknown67IntersectionRedacted by NHTSA as confidential business information
13781-6706Level 2Tesla, Inc.2023-11 01:00Lake Worth Beach, FL2023 Tesla Model 3ADASOther Fixed ObjectUnknown47Highway / FreewayRedacted by NHTSA as confidential business information
13781-6707Level 2Tesla, Inc.2023-11 18:27Grand Blanc, MI2020 Tesla Model YADASHeavy TruckUnknown40Rural RoadRedacted by NHTSA as confidential business information
13781-6708Level 2Tesla, Inc.2023-11 16:24Solana Beach, CA2023 Tesla Model YADASSUVUnknown73Highway / FreewayRedacted by NHTSA as confidential business information
13781-6709Level 2Tesla, Inc.2023-11 18:43Riverside, CA2017 Tesla Model SADASUnknownUnknown54Highway / FreewayRedacted by NHTSA as confidential business information
13781-6710Level 2Tesla, Inc.2023-11 09:53Henrico, VA2021 Tesla Model YADASOther, see NarrativeUnknown53Highway / FreewayRedacted by NHTSA as confidential business information
13781-6711Level 2Tesla, Inc.2023-11 00:32Cozad, NE2023 Tesla Model YADASUnknownUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-6712Level 2Tesla, Inc.2023-11 16:14Malden, WV2021 Tesla Model YADASOther Fixed ObjectUnknown63Highway / FreewayRedacted by NHTSA as confidential business information
13781-6713Level 2Tesla, Inc.2023-11 20:58Snellville, GA2022 Tesla Model YADASUnknownUnknown38Highway / FreewayRedacted by NHTSA as confidential business information
13781-6714Level 2Tesla, Inc.2023-11 18:57Miami, FL2023 Tesla Model YADASSUVUnknown34StreetRedacted by NHTSA as confidential business information
13781-6715Level 2Tesla, Inc.2023-11 13:29Templeton, CA2022 Tesla Model 3ADASOther Fixed ObjectUnknown27Highway / FreewayRedacted by NHTSA as confidential business information
13781-6716Level 2Tesla, Inc.2023-11 07:52Meredithville, VA2023 Tesla Model 3ADASUnknownUnknown78UnknownRedacted by NHTSA as confidential business information
13781-6717Level 2Tesla, Inc.2023-11 05:00Raleigh, NC2020 Tesla Model YADASPole / TreeUnknown50Highway / FreewayRedacted by NHTSA as confidential business information
13781-6718Level 2Tesla, Inc.2023-11 02:38Hayward, CA2022 Tesla Model XADASUnknownUnknown10IntersectionRedacted by NHTSA as confidential business information
13781-6719Level 2Tesla, Inc.2023-11 03:45San Jose, CA2021 Tesla Model 3ADASPassenger CarUnknown35StreetRedacted by NHTSA as confidential business information
13781-6745Level 2Tesla, Inc.2023-11 01:29Aptos, CA2020 Tesla Model YADASPassenger CarUnknown16StreetRedacted by NHTSA as confidential business information
13781-6746Level 2Tesla, Inc.2023-11 02:25Wildwood, FL2020 Tesla Model 3ADASAnimalUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-6747Level 2Tesla, Inc.2023-11 15:13Cumberland, RI2021 Tesla Model YADASOther Fixed ObjectUnknown60Highway / FreewayRedacted by NHTSA as confidential business information
13781-6748Level 2Tesla, Inc.2023-11 03:42Atlanta, GA2022 Tesla Model SADASVanUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-6749Level 2Tesla, Inc.2023-11 19:09Golden, CO2023 Tesla Model YADASOther Fixed ObjectUnknown50Highway / FreewayRedacted by NHTSA as confidential business information
13781-6750Level 2Tesla, Inc.2023-11 18:05Webber Township, MI2022 Tesla Model YADASPole / TreeUnknown55Rural RoadRedacted by NHTSA as confidential business information
13781-6751Level 2Tesla, Inc.2023-11 22:01El Monte, CA2021 Tesla Model 3ADASOther Fixed ObjectUnknown58Highway / FreewayRedacted by NHTSA as confidential business information
13781-6752Level 2Tesla, Inc.2023-11 10:39St Clair Shores, MI2020 Tesla Model 3ADASPassenger CarUnknown65Highway / FreewayRedacted by NHTSA as confidential business information
13781-6754Level 2Tesla, Inc.2023-11 22:15Pleasanton, CA2018 Tesla Model SADASPole / TreeUnknown42UnknownRedacted by NHTSA as confidential business information
13781-6775Level 2Tesla, Inc.2023-11 06:12Los Angeles, CA2020 Tesla Model 3ADASOther Fixed ObjectUnknown72Highway / FreewayRedacted by NHTSA as confidential business information
13781-6776Level 2Tesla, Inc.2023-11 12:23Castro Valley, CA2020 Tesla Model 3ADASOther Fixed ObjectUnknown63Highway / FreewayRedacted by NHTSA as confidential business information
13781-6902Level 2Tesla, Inc.2023-11Anaheim, CA2021 Tesla Model YADASPassenger CarUnknown55Highway / FreewayRedacted by NHTSA as confidential business information
13781-7187Level 2Tesla, Inc.2023-11Jefferson County, CO2020 Tesla Model XADASOther, see NarrativeUnknown42Rural RoadRedacted by NHTSA as confidential business information
13781-7197 v4Level 2Tesla, Inc.2023-11Onamia, MNUnknownUnknown, see NarrativeNon-Motorist: PedestrianFatalityHighway / Freeway
Summary: Information provided as an update to 13781-7197-2. Based on a determination by local law enforcement as part of their investigation, this incident did not involve the original vehicle of interest, and there is n…Summary: Information provided as an update to 13781-7197-2. Based on a determination by local law enforcement as part of their investigation, this incident did not involve the original vehicle of interest, and there is no information, indication or continued allegation relating to the operation of an ADAS-equipped vehicle of any make. Tesla requests removal of this report and its count from the SGO reporting. Source: Media.
13781-8004 v2Level 2Tesla, Inc.2023-11 00:03Rimrock, AZ2021 Tesla Model YADASNon-Motorist: PedestrianFatality55Highway / FreewayRedacted by NHTSA as confidential business information
273-6769 v2Level 2Chrysler (FCA US, LLC)2023-11 14:15Findley, OH2023 Jeep Grand Cherokee Overland 4xEADASOther Fixed ObjectNo Injuries Reported65Highway / FreewayRedacted by NHTSA as confidential business information
30270-6579 v2ADSWaymo LLC2023-11 22:43San Francisco, CA2021 Jaguar I-PaceADSPassenger CarSerious18Intersection
Other than correcting the Mileage to 64,204, adding law enforcement investigation details, adding the ADS Software Version, and adding the Waymo AVs Pre-Crash Speed, the content of this report is unchanged from the initi…Other than correcting the Mileage to 64,204, adding law enforcement investigation details, adding the ADS Software Version, and adding the Waymo AVs Pre-Crash Speed, the content of this report is unchanged from the initial report submitted on November 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On November [XXX], 2023 at 10:43 PM PT 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 northbound in the left lane on [XXX] and stopped at a red light at the intersection with [XXX] alongside a passenger vehicle in the right lane. After the light turned green, both the Waymo AV and the adjacent passenger car proceeded into the intersection. While in the intersection, a passenger car traveling west on [XXX] ran the red light and the front left corner and left side of this vehicle made contact with the front right of the Waymo AV and the front of the adjacent passenger car. After impact, the vehicle that ran the red light struck pedestrians that had been standing on the sidewalk on the northwest corner of the intersection. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage and were towed from the scene. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6765ADSWaymo LLC2023-11 17:40Scottsdale, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On November [XXX], 2023 at 5:40 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling northbound on [XXX…On November [XXX], 2023 at 5:40 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling northbound on [XXX] and was approaching the intersection with [XXX], when it detected an approaching emergency vehicle, which was traveling southbound on [XXX] and approaching the intersection with [XXX]. The Waymo AV braked to a stop soon after passing the nearside crosswalk in an attempt to keep the intersection clear for the emergency vehicle. A passenger vehicle approached from behind and then 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. 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.
30270-6838ADSWaymo LLC2023-11 10:09Tempe, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported2Parking Lot
On November [XXX] , 2023 at 10:09 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a chain in a parking lot at [XXX]. The Waymo AV was traveling in a parking lot at [XX…On November [XXX] , 2023 at 10:09 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a chain in a parking lot at [XXX]. The Waymo AV was traveling in a parking lot at [XXX] when it made contact with a hanging chain separating a section of the parking lot. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6839ADSWaymo LLC2023-11 15:44San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On November [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the rightmost…On November [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the rightmost non-HOV lane on northbound [XXX] waiting for the intersection at [XXX] to clear during a green light. The passenger car behind the Waymo AV was rear-ended by a pickup truck, causing the front of the passenger car to make 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). All three vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6853ADSWaymo LLC2023-11 04:06Austin, TX2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and sto…On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and stopped at a red light on [XXX], preparing to make a right turn onto southbound [XXX]. A pickup truck approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6854ADSWaymo LLC2023-11 21:36Tempe, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported10Parking Lot
On November [XXX], 2023 at 8:36 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving an automatic gate at [XXX]. The Waymo AV was traveling northbound through a parking lot…On November [XXX], 2023 at 8:36 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving an automatic gate at [XXX]. The Waymo AV was traveling northbound through a parking lot at an apartment complex, heading toward [XXX]. An automatic gate was closing as the Waymo AV approached, and the gate made contact with the rear side sensors of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6855ADSWaymo LLC2023-11 15:46San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Street
On November [XXX], 2023 at 3:46 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] i…On November [XXX], 2023 at 3:46 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane in stop-and-go traffic. It had just passed [XXX] when it initiated a left lane change, planning to proceed ahead of a van in the adjacent left lane. As the Waymo AV nudged into the adjacent lane, the van accelerated and its front passenger side quarter panel made contact with the Waymo AVs driver side quarter panel. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6857ADSWaymo LLC2023-11 19:59Los Angeles, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On November [XXX], 2023 at 7:59 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped for a red ligh…On November [XXX], 2023 at 7:59 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped for a red light facing southeast on [XXX] at [XXX] when a passenger vehicle approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30490-6590ADSBeep, Inc.2023-11 11:02Orlando, FLNavya ARMA AutonomADSBusNo Injuries Reported6Intersection
At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting i…At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting in moderate damage to the shuttle and minor damage to the Lynx bus. There were no injuries reported. Local police responded to the scene and conducted a traffic investigation. The Beep shuttle was towed from the scene for transport to the maintenance facility. The LYNX bus did not require towing and drove from the scene.
30490-6821ADSBeep, Inc.2023-11 11:02Orlando, FL2020 Navya ARMAADSBusNo Injuries Reported6Intersection
At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting i…At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting in moderate damage to the shuttle and minor damage to the Lynx bus. There were no injuries reported. Local police responded to the scene and conducted a traffic investigation. The Beep shuttle was towed from the scene for transport to the maintenance facility. The LYNX bus did not require towing and drove from the scene. Monthly update to previously submitted report 30490-6590-1.
30530-6818ADSAurora Operations, Inc.2023-11 09:56Ranger, TX2023 Peterbilt 579ADSPickup TruckNo Injuries Reported67Highway / Freeway
This incident occurred near Ranger, TX on [XXX] at approximately 9:56 am CT on Nov. [XXX], 2023. The Aurora vehicle was operating in autonomy at the time. Conditions were overcast, with light rain. As the Aurora vehicle …This incident occurred near Ranger, TX on [XXX] at approximately 9:56 am CT on Nov. [XXX], 2023. The Aurora vehicle was operating in autonomy at the time. Conditions were overcast, with light rain. As the Aurora vehicle was driving in its lane at 67 mph, a Ford pick-up truck overtaking the Aurora vehicle in the rightmost lane at approximately 80 mph appears to have hydroplaned, lost control, and hit the passenger-side rear portion of the trailer. Before the collision, the Aurora Driver detected the pick-up trucks encroachment into the Aurora vehicles lane and initiated a nudge to the left to provide space. This was insufficient to completely avoid the collision, and the pick-up truck made contact with the passenger side rear of the trailer. The Aurora Driver detected the collision and made the decision to initiate an incident response, but before it could execute that response, the Vehicle Operator took over control of the system and proceeded in manual. The Vehicle Operator received the notification that a collision had been detected and was initiating an incident response. The Vehicle Operator did not visually observe the collision and therefore assumed the reaction of the Aurora Driver to be a software anomaly worth escalated attention, rather than the correct detection of a collision and thus reported the incident through our escalated annotation protocol, rather than through our incident response protocols. We identified the incident at approximately 8:45 am CT on December [XXX], 2023, through a review of our data logs. At this time, we are not aware of any injuries and, from camera footage, the pick-up truck also appears to have left the scene of the incident. There is also no indication of any cargo or major trailer damage.
30531-6862ADSTransdev Alternative Services2023-11 15:44San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On November [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the rightmo…On November [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the rightmost non-HOV lane on northbound [XXX] waiting for the intersection at [XXX] to clear during a green light. The passenger car behind the Waymo AV was rear-ended by a pickup truck, causing the front of the passenger car to make contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). All three 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. This is a duplicate of report ID 30270-6839-1.
30531-6863ADSTransdev Alternative Services2023-11 04:06Austin, TX2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and s…On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and stopped at a red light on [XXX], preparing to make a right turn onto southbound [XXX]. A pickup truck approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained 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 in the future. This report is a duplicate of report ID 30270-6853-1.
30531-6864ADSTransdev Alternative Services2023-11 19:59Los Angeles, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On November [XXX], 2023 at 7:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped for a red li…On November [XXX], 2023 at 7:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped for a red light facing southeast on [XXX] at [XXX] when a passenger vehicle approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting in the future. This is a duplicate of report ID: 30270-6857-1.
30610-6592 v2ADSZoox, Inc.2023-11 22:16Seattle, WA2017 Toyota HighlanderADSOther, see NarrativeMinor0Street
A Zoox vehicle in autonomy was stopped at a stop sign on southbound [XXX] at [XXX] waiting for a crossing vehicle to clear the intersection, when it was rear-ended by an e-scooter rider. The e-scooter rider initially pas…A Zoox vehicle in autonomy was stopped at a stop sign on southbound [XXX] at [XXX] waiting for a crossing vehicle to clear the intersection, when it was rear-ended by an e-scooter rider. The e-scooter rider initially passed the slowing Zoox vehicle while traveling on northbound [XXX], but then made a mid-block U-turn and rode into the rear of the then-stopped Zoox vehicle in a visibly deliberate manner. The contact resulted in minor scratches on the rear bumper of the Zoox vehicle. The e-scooter rider did not initially indicate that they were injured, and the Zoox operator drove through the intersection to a safe pullover location to assess the damage however, the e-scooter rider later indicated that their "foot hurts". The Police and EMS were then called to the scene, and the e-scooter rider apparently received medical attention and was released. This update provides complete information to date for this incident.
540-6702Level 2General Motors, LLC2023-11 12:02New Albany, OH2023 GMC Sierra 1500ADASAnimalNo Injuries Reported72Highway / Freeway
At 12:02:16 PM, a GMC Sierra 1500 Crew Cab was travelling east on [XXX] east of [XXX] in New Albany, Ohio and struck a deer crossing the road. The driver front airbag and seat belt pretensioner deployed. ADAS telematic…At 12:02:16 PM, a GMC Sierra 1500 Crew Cab was travelling east on [XXX] east of [XXX] in New Albany, Ohio and struck a deer crossing the road. The driver front airbag and seat belt pretensioner deployed. ADAS telematic data indicates that Super Cruise was active up until 5 seconds prior to crash. A pre-crash speed of 72.9 mph was the last vehicle speed recorded, approximately 17 seconds prior to crash.
62-11741Level 2Honda (American Honda Motor Co.)2023-11 12:00UNK2024 HONDA CR-VUnknown - see NarrativeOther Fixed ObjectMinor W/O Hospitalization78Unknown
Honda Customer Service contacted the customer to confirm the accident on [XXX], customer was driving on the[XXX] highway going eastbound, near [XXX]. He had ACC on, and it was sent to 78. There were no cars in front of h…Honda Customer Service contacted the customer to confirm the accident on [XXX], customer was driving on the[XXX] highway going eastbound, near [XXX]. He had ACC on, and it was sent to 78. There were no cars in front of him. Customer also had the lane keep assist on, which he recalls was green prior to the accident. The vehicle started pulling to the right and then collided with metal divider on the passenger side. Both the driver front airbag and driver knee airbags deployed. Honda asked how he was doing, which he informed me better. Honda asked if he had any injuries, which he said he had a scratch on his wrist. He did not know what scratched him. Honda asked about the damage to the vehicle, which he informed that the vehicle is not drivable. The right rear tire was flat, damage to the right side of fender, also right-side bumper in front, left front bumper as well, scratches on both passenger side front and rear door. Driver side, he mentioned that there was plastic piece that fell off, not sure what that was. Honda asked him about ACC, how long he had been using, and what speed it was sent for. Customer started he was using the ACC about half hour after he started his drive. It was sent to 78 MPH. Honda asked what the speed limit was for that area of highway, which he advised about 70MPH. Honda asked him about LKAS, how long has been using it, and if he recalled what the LKAS icon was prior to the accident. He also said that he turned LKAS on about half hour after he started his drive. He said prior the accident it was green. Honda asked if he recalls the conditions or markings on the road, which he could recall partially as it happened all so fast. Since it was a two-lane highway going east, his vehicle was on the right side. The left side he recalls the lines being white and dashed. Honda asked about the right side, but he could not recall, maybe solid white, but he was not sure. He mentioned there was a downside hill when he goes off the road, so road was higher than side of road. Honda asked around what time this occurred and weather conditions, which he advised around 12 PM, and it was sunny. Honda asked about the vehicle starting to go right if he recalls the steering conditions at the time. The vehicle was driving straight, then started going right. He mentioned he had his hand on the steering wheel. Honda asked once it started pulling right, did he apply steering correction, but he did not recall. Honda asked if he recalled putting his foot on the brake pedal, either right before hitting the railing or after. He does not think he did right before hit railing. He does recall after hitting the railing as that is probably what stopped the vehicle. Honda asked him if he recalls how long it was from vehicle starting to go right, to hitting the barrier, which he did not recall. Honda asked if metal barrier was solid, like one metal strip, or if there were two, with a gap in between, but he could not recall. After the accident, police did come out, and he received a $210 citation ticket, and a copy of the report. NOTE: We recently let NHTSA's Office of Chief Council know about this past incident from 2023.
753-6768 v5Level 2Kia America, Inc.2023-11 07:40Aurora, CO2024 KIA K5Unknown, see NarrativeOther, see NarrativeModerate65Highway / Freeway
The owner (father of the driver) of a 2024MY Kia K5 contacted Kia's Customer Care Center on 12/5/2023 indicating his son was driving the subject vehicle when the traffic slowed down suddenly and was involved in an accide…The owner (father of the driver) of a 2024MY Kia K5 contacted Kia's Customer Care Center on 12/5/2023 indicating his son was driving the subject vehicle when the traffic slowed down suddenly and was involved in an accident. The father was not a passenger or witness to the accident. The father reported his son was traveling approximately 60-65mph when a "Ford Explorer may have cut him off, [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] he had no time to brake, and hit the [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]". The "car did [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] alert or brake" prior to impact. The father indicated his son did not remember if he had hit the brakes. The subject Kia K5 is equipped with Highway Driving Assist (HDA), Lane Following Assist (LFA) and Smart Cruise Control (SCC). HDA is a supplemental system that helps maintain a set distance and speed from the vehicle ahead when driving on a highway and helps keep the vehicle between lanes while driving. HDA may not be able to recognize all traffic situations and may not detect possible collisions due to limitations of the system. LFA is also a supplemental system that helps to detect lane markings and/or vehicles on the road, and assists the driver's steering to help keep the vehicle between lanes. LFA does not operate at all times and it is the responsibility of the driver to safely steer the vehicle and to maintain the vehicle in its lane. The father reported that HDA and LFA were engaged but SCC was not. It is unclear whether HDA was in fact engaged since the father reported SCC was not. Kia is currently working with the father to retrieve the vehicle's ACU but has no further information at this time. *10-Day Update* After Kia's 1-Day report was submitted, the customer provided Kia with photos of the vehicle. Kia has no further update at this time. *1/16/2024: Monthly Update* On 12/18/2023, ODI engineer Joseph Teitelman requested some additional information regarding the vehicle. Kia responded on the same day. The ACU for the subject vehicle was shipped to Kia America on 1/11/2024 and is currently in transit. Once received, Kia will download the EDR and provide to Joe Teitelman per his request via the provided SLFTS link. *2/15/2024: Monthly Update* On 1/23/2024, Kia submitted the requested EDR report to Mr. Teitelman via NHTSA's SLFTS portal. *3/15/2024: Monthly Update* Kia engineer reviewed the EDR data previously submitted to NHTSA and identified the following: 1) Vehicle was travelling 111-112 kph pre-crash (69-70 mph) 2) Smart Cruise Control was off during the entire 5 seconds pre-crash and was not being operated in L2 mode during this time 3) Driver pressed brakes at 0.5 seconds pre-crash in conjunction with FCA providing braking force which activated ABS 4) Forward Collision Avoidance Assist provided Level 1 warning from -0.8 to -0.7 seconds before the crash 5) FCA provided Level 2 warning from -0.6 to 0.0 seconds before the crash and 6) Brake pressure was recorded at 154.2 bar at 0.5 seconds pre-crash. The vehicle systems appear to have operated as designed.
753-6807 v3Level 2Kia America, Inc.2023-11 06:58DUPONT, WA2023 KIA NIROADASHeavy TruckModerate65Highway / Freeway
12/12/2023: The customer contacted Kias Customer Care Center on 12/11/2023 to report his 2023MY Kia Niro was involved in accident following a clutch repair by the dealer. Specifically, the customer stated that he had le…12/12/2023: The customer contacted Kias Customer Care Center on 12/11/2023 to report his 2023MY Kia Niro was involved in accident following a clutch repair by the dealer. Specifically, the customer stated that he had left the dealer after a clutch repair and got hit by a semi-truck due to [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] clutch not working, stopped in middle of highway and could not move. Customer stated the dealers faulty repair caused the accident. In response to the Kia Customer Care agent, the customer reported that Highway Driving Assist (HDA) and Cruise Control engaged at the time of the accident. Customer requested compensation for the clutch not working and for the rental he had to pay for. The subject Kia Niro is equipped with HDA. HDA is a supplemental system that helps maintain a set distance and speed from the vehicle ahead when driving on a highway and helps keep the vehicle between the lanes while driving. Based on the facts currently available, there is no indication that the HDA system was not working properly. Kia is submitting this report as a precautionary measure because the customer reported HDA was engaged at the time of the incident and and it appeared to meet the other requirements under the SGO. 12/21/2023: Kia has attempted to contact the customer multiple times for additional information, but has not received a response to date. Kia has located photos of the subject Kia Niro, which suggest the vehicle suffered a minor, offset frontal crash with minimal damage to thin sheet metal and plastic at the right front corner. The apparent damage is potentially inconsistent with the customers account of being hit by a semi-truck, which may be indicated by damage at the rear or pushing panels forward. In addition, Kias records show that the repair was performed on [XXXX] and the incident occurred on November 20, 2023, which appears to contradict the customers statement that the incident occurred shortly after leaving the dealer. Kia has no further information at this time. *** 1/16/24: Monthly Update*** Following submission of this incident, ODI engineer, Joseph Teitelman reached out to Kia and requested additional information including photos, invoice/estimate of repair to subject vehicle, police report, EDR report and vehicle telematics relating to the subject incident. On 1/8/24, Kia uploaded photos and the repair order identified by the customer in their statement. Kia does not have a copy of the police report or any telematics data. Kia further advised that the subject vehicle was sold at auction. As a result, Kia was unable to gain access to the vehicle to download the EDR. Kia has no further information at this time.
988-6859ADSPACCAR Incorporated2023-11 09:56Ranger, TX2023 Peterbilt 579ADSPickup TruckNo Injuries Reported67Highway / Freeway
Reference: Aurora Operations, Inc. NHTSA-Provided Report # 30530-6818-1 This incident occurred near Ranger, TX on [XXX] approximately 9:56 am CT on November [XXX], 2023. The Aurora vehicle was operating in autonomy at t…Reference: Aurora Operations, Inc. NHTSA-Provided Report # 30530-6818-1 This incident occurred near Ranger, TX on [XXX] approximately 9:56 am CT on November [XXX], 2023. The Aurora vehicle was operating in autonomy at the time. Conditions were overcast, with light rain. As the Aurora vehicle was driving in its lane at 67 mph, a Ford pick-up truck overtaking the Aurora vehicle in the rightmost lane at approximately 80 mph appears to have hydroplaned, lost control, and hit the passenger-side rear portion of the trailer. Before the collision, the Aurora Driver detected the pick-up truck's encroachment into the Aurora vehicle's lane and initiated a nudge to the left to provide space. This was insufficient to completely avoid the collision, and the pickup truck made contact with the passenger side rear of the trailer. The Aurora Driver detected the collision and made the decision to initiate an incident response, but before it could execute that response, the Vehicle Operator took over control of the system and proceeded in manual. The Vehicle Operator received the notification that a collision had been detected and was initiating an incident response. The Vehicle Operator did not visually observe the collision and therefore assumed the reaction of the Aurora Driver to be a software anomaly worth escalated attention, rather than the correct detection of a collision and thus reported the incident through our escalated annotation protocol, rather than through our incident response protocols. We identified the incident at approximately 8:45 am CT on December [XXX], 2023 through a review of our data logs. At this time, we are not aware of any injuries and, from camera footage, the pick-up truck also appears to have left the scene of the incident. There is also no indication of any cargo or major trailer damage.
1243-7991 v2Level 2Subaru of America, Inc.2023-10 14:41New Kent, VA2020 Subaru LegacyADASHeavy TruckModerate75Highway / FreewayRedacted by NHTSA as confidential business information
13781-10015 v2Level 2Tesla, Inc.2023-10 03:05East Hanover, NJ2023 TESLA Model YVerified EngagedPassenger CarUnknown21StreetRedacted by NHTSA as confidential business information
13781-10016Level 2Tesla, Inc.2023-10 06:55Jacksonville, FL2020 Tesla Model SADASOther, see NarrativeUnknown20StreetRedacted by NHTSA as confidential business information
13781-10017Level 2Tesla, Inc.2023-10 08:24Oceanside, CA2018 Tesla Model XADASUnknownUnknown43UnknownRedacted by NHTSA as confidential business information
13781-10020Level 2Tesla, Inc.2023-10 02:28San Francisco, CA2017 Tesla Model XADASUnknownUnknown6UnknownRedacted by NHTSA as confidential business information
13781-10021Level 2Tesla, Inc.2023-10 10:36Carlsbad, CA2022 Tesla Model YADASOther Fixed ObjectUnknown62Highway / FreewayRedacted by NHTSA as confidential business information
13781-10022Level 2Tesla, Inc.2023-10 00:43Thousand Oaks, CA2017 Tesla Model XADASPassenger CarUnknown29Rural RoadRedacted by NHTSA as confidential business information
13781-10023Level 2Tesla, Inc.2023-10 23:38Los Angeles, CA2018 Tesla Model XADASUnknownUnknown59UnknownRedacted by NHTSA as confidential business information
13781-15684OTHERTesla, Inc.2023-10 10:35Sumter, SC2016 TESLA Model XAlleged EngagedPole / TreeFatalityStreetRedacted by NHTSA as confidential business information
13781-6411Level 2Tesla, Inc.2023-10 00:24Reno, NV2023 Tesla Model SADASSUVUnknown61Highway / FreewayRedacted by NHTSA as confidential business information
13781-6412Level 2Tesla, Inc.2023-10 23:04Glendale, CA2022 Tesla Model XADASPassenger CarUnknown32Highway / FreewayRedacted by NHTSA as confidential business information
13781-6423Level 2Tesla, Inc.2023-10 05:20Portland, OR2022 Tesla Model 3ADASPassenger CarUnknown37Highway / FreewayRedacted by NHTSA as confidential business information
13781-6424Level 2Tesla, Inc.2023-10 03:46San Mateo, CA2023 Tesla Model YADASAnimalUnknown66Highway / FreewayRedacted by NHTSA as confidential business information
13781-6425Level 2Tesla, Inc.2023-10 19:40Asheboro, NC2022 Tesla Model YADASPickup TruckUnknown29Rural RoadRedacted by NHTSA as confidential business information
13781-6426Level 2Tesla, Inc.2023-10 23:49Duluth, GA2023 Tesla Model XADASUnknownUnknown15StreetRedacted by NHTSA as confidential business information
13781-6480Level 2Tesla, Inc.2023-10San Francisco, CA2023 Tesla Model 3ADASOther Fixed ObjectUnknown30IntersectionRedacted by NHTSA as confidential business information
13781-6482Level 2Tesla, Inc.2023-10 10:11Los Angeles, CA2020 Tesla Model YADASOther Fixed ObjectUnknown70Highway / FreewayRedacted by NHTSA as confidential business information
13781-6483Level 2Tesla, Inc.2023-10 01:44Schaumburg, IL2020 Tesla Model YADASPassenger CarUnknown88Highway / FreewayRedacted by NHTSA as confidential business information
13781-6537Level 2Tesla, Inc.2023-10 16:31Somerville, OH2020 Tesla Model 3ADASPickup TruckUnknown35Rural RoadRedacted by NHTSA as confidential business information
13781-6538Level 2Tesla, Inc.2023-10 11:17Denton, TX2020 Tesla Model YADASPassenger CarUnknown39IntersectionRedacted by NHTSA as confidential business information
13781-6539Level 2Tesla, Inc.2023-10 02:07Nashville-Davidson, TN2018 Tesla Model 3ADASUnknownUnknown48UnknownRedacted by NHTSA as confidential business information
13781-6540Level 2Tesla, Inc.2023-10 17:00North Attleborough, MA2020 Tesla Model 3ADASUnknownUnknown69Highway / FreewayRedacted by NHTSA as confidential business information
13781-6543Level 2Tesla, Inc.2023-10 23:13Grand Prairie, TX2021 Tesla Model YADASOther Fixed ObjectUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-6544Level 2Tesla, Inc.2023-10 20:29Frisco, TX2023 Tesla Model YADASPassenger CarUnknown37IntersectionRedacted by NHTSA as confidential business information
13781-6545Level 2Tesla, Inc.2023-10 19:59Reno, NV2022 Tesla Model YADASPassenger CarUnknown22IntersectionRedacted by NHTSA as confidential business information
13781-6546Level 2Tesla, Inc.2023-10 01:45Duncanville, TX2018 Tesla Model 3ADASUnknownUnknown40UnknownRedacted by NHTSA as confidential business information
13781-6547Level 2Tesla, Inc.2023-10 08:01San Carlos, CA2018 Tesla Model 3ADASAnimalUnknown80Highway / FreewayRedacted by NHTSA as confidential business information
13781-6552Level 2Tesla, Inc.2023-10 23:28Midlothian, VA2023 Tesla Model YADASUnknownUnknown34Highway / FreewayRedacted by NHTSA as confidential business information
13781-6553Level 2Tesla, Inc.2023-10 13:09Rocky Hill, CT2021 Tesla Model YADASOther Fixed ObjectUnknown65Highway / FreewayRedacted by NHTSA as confidential business information
13781-6554Level 2Tesla, Inc.2023-10 04:17Carson, VA2020 Tesla Model 3ADASPickup TruckUnknown75Highway / FreewayRedacted by NHTSA as confidential business information
13781-6557Level 2Tesla, Inc.2023-10 13:11Reno, OK2022 Tesla Model 3ADASUnknownUnknown83UnknownRedacted by NHTSA as confidential business information
13781-6558Level 2Tesla, Inc.2023-10 11:56Los Altos Hills, CA2023 Tesla Model SADASAnimalUnknown62Highway / FreewayRedacted by NHTSA as confidential business information
13781-6559Level 2Tesla, Inc.2023-10 11:42Highland Mills, NY2022 Tesla Model XADASUnknownUnknown24Rural RoadRedacted by NHTSA as confidential business information
13781-6560Level 2Tesla, Inc.2023-10 02:28Sunnyvale, CA2023 Tesla Model 3ADASSUVUnknown19StreetRedacted by NHTSA as confidential business information
13781-6569Level 2Tesla, Inc.2023-10 00:03Holmdel, NJ2018 Tesla Model 3ADASPassenger CarUnknown47Highway / FreewayRedacted by NHTSA as confidential business information
13781-6570Level 2Tesla, Inc.2023-10 06:11Miami, FL2022 Tesla Model YADASPassenger CarUnknown33StreetRedacted by NHTSA as confidential business information
13781-6571Level 2Tesla, Inc.2023-10 11:28Horn Lake, MS2021 Tesla Model 3ADASBusUnknown44Rural RoadRedacted by NHTSA as confidential business information
13781-6572Level 2Tesla, Inc.2023-10 04:42Oakland, CA2020 Tesla Model 3ADASSUVUnknown69Highway / FreewayRedacted by NHTSA as confidential business information
13781-6573Level 2Tesla, Inc.2023-10 23:38Mays Landing, NJ2023 Tesla Model 3ADASSUVUnknown48IntersectionRedacted by NHTSA as confidential business information
13781-6574Level 2Tesla, Inc.2023-10 16:35Livermore, CA2018 Tesla Model 3ADASUnknownUnknown37UnknownRedacted by NHTSA as confidential business information
13781-6575Level 2Tesla, Inc.2023-10 06:31St. Louis, MO2023 Tesla Model 3ADASUnknownUnknown51Highway / FreewayRedacted by NHTSA as confidential business information
13781-6576Level 2Tesla, Inc.2023-10 04:25Long Beach, CA2023 Tesla Model 3ADASPassenger CarUnknown59Highway / FreewayRedacted by NHTSA as confidential business information
13781-6583Level 2Tesla, Inc.2023-10 17:37Lake Elsinore, CA2023 Tesla Model 3ADASUnknownUnknown68Highway / FreewayRedacted by NHTSA as confidential business information
13781-6903Level 2Tesla, Inc.2023-10Hellertown, PA2023 Tesla Model YADASUnknownUnknown38UnknownRedacted by NHTSA as confidential business information
29990-6636Level 2Rivian Automotive, LLC2023-10 14:35Bradley, CA2023 Rivian R1SADASOther Fixed ObjectNo Injuries Reported75Highway / Freeway
On October [XXX], 2023, at 2:35 p.m. PST, the subject vehicle was traveling north on [XXX] at approximately 75 mph with Rivians Level 2 ADAS feature, Highway Assist (HWA), engaged. While traveling across an overpass at 2…On October [XXX], 2023, at 2:35 p.m. PST, the subject vehicle was traveling north on [XXX] at approximately 75 mph with Rivians Level 2 ADAS feature, Highway Assist (HWA), engaged. While traveling across an overpass at 2:35:18 p.m. PST, HWA disengaged because the subject vehicle moved out of its ODD as a result of insufficient highway markings. At 2:35:18 p.m. PST, the driver received audio and visual alerts to take over the subject vehicle through in-vehicle messaging. The driver did not heed the warnings and the vehicle began to drift to the right, at which point Lane Keep Assist intervened and guided the vehicle back to the left to avoid crossing over the lane boundary. After this automatic vehicle intervention, the driver finally retook control of the wheel but overcorrected, steering the vehicle to the left until it left the roadway and impacted the side marker at 2:35:21 p.m. PST, causing minor damage to the subject vehicle.
29990-6637Level 2Rivian Automotive, LLC2023-10 17:00Mountain View, CA2023 Rivian R1SADASOther, see NarrativeNo Injuries Reported16Highway / Freeway
On October [XXX], 2023, at 5 p.m. PST, the subject vehicle was being operated at low speeds in stop and go traffic, on a highway with Rivians Level 2 ADAS feature Highway Assist (HWA) engaged. According to the driver, a …On October [XXX], 2023, at 5 p.m. PST, the subject vehicle was being operated at low speeds in stop and go traffic, on a highway with Rivians Level 2 ADAS feature Highway Assist (HWA) engaged. According to the driver, a vehicle to the right of the subject vehicle attempted to merge in front of the subject vehicle, underestimating the distance needed to complete the merger and the other vehicle crashed into the subject vehicle. The crash resulted in minor damage to the subject vehicle. The state of the other vehicle is unknown but believed to also have minor damage. Data indicates that the driver of the subject vehicle did not have hands on the wheel for approximately 45 seconds before the crash or at the time of impact. Data indicates that the vehicle did not malfunction and performed as designed in response to driver inputs.

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.