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 7301 to 7400.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
13781-4625 v2Level 2Tesla, Inc.2023-01 18:16Harrisburg, PA2023 Tesla Model XADASUnknownUnknown18StreetRedacted by NHTSA as confidential business information
13781-4626 v2Level 2Tesla, Inc.2023-01 17:23Los Altos, CA2021 Tesla Model YADASOther Fixed ObjectUnknown61Highway / FreewayRedacted by NHTSA as confidential business information
13781-4627 v2Level 2Tesla, Inc.2023-01 16:40Solana Beach, CA2020 Tesla Model YADASPassenger CarUnknown43Highway / FreewayRedacted by NHTSA as confidential business information
13781-4637 v2Level 2Tesla, Inc.2023-01 14:33Tyler, TX2018 Tesla Model 3ADASVanUnknown53IntersectionRedacted by NHTSA as confidential business information
13781-4638 v2Level 2Tesla, Inc.2023-01 14:39Austin, TX2021 Tesla Model 3ADASSUVUnknown8StreetRedacted by NHTSA as confidential business information
13781-4639 v2Level 2Tesla, Inc.2023-01 21:13Woodside, CA2021 Tesla Model YADASOther Fixed ObjectUnknown72Highway / FreewayRedacted by NHTSA as confidential business information
13781-4693 v2Level 2Tesla, Inc.2023-01 15:40Sausalito, CA2021 Tesla Model YADASOther Fixed ObjectUnknown40Highway / FreewayRedacted by NHTSA as confidential business information
13781-4694 v2Level 2Tesla, Inc.2023-01 15:10Mt. Hope, NY2022 Tesla Model 3ADASUnknownUnknown53Rural RoadRedacted by NHTSA as confidential business information
13781-4695 v2Level 2Tesla, Inc.2023-01 10:15Atlanta, GA2019 Tesla Model 3ADASOther Fixed ObjectUnknown72Highway / FreewayRedacted by NHTSA as confidential business information
13781-4696 v2Level 2Tesla, Inc.2023-01 15:41Sunol, CA2018 Tesla Model 3ADASOther Fixed ObjectUnknown59Highway / FreewayRedacted by NHTSA as confidential business information
13781-4698 v2Level 2Tesla, Inc.2023-01 19:52Belmont, CA2021 Tesla Model YADASOther Fixed ObjectUnknown37Highway / FreewayRedacted by NHTSA as confidential business information
13781-4699 v2Level 2Tesla, Inc.2023-01 10:35Los Angeles, CA2021 Tesla Model 3ADASOther Fixed ObjectUnknown46Highway / FreewayRedacted by NHTSA as confidential business information
13781-4700 v2Level 2Tesla, Inc.2023-01 09:21Houston, TX2022 Tesla Model YADASSUVUnknown70IntersectionRedacted by NHTSA as confidential business information
13781-4709 v2Level 2Tesla, Inc.2023-01 14:27San Jose, CA2018 Tesla Model 3ADASOther Fixed ObjectUnknown15Highway / FreewayRedacted by NHTSA as confidential business information
13781-4724 v2Level 2Tesla, Inc.2023-01 21:44Cumming, GA2021 Tesla Model YUnknown, see NarrativeUnknownUnknown49Highway / FreewayRedacted by NHTSA as confidential business information
13781-4725 v2Level 2Tesla, Inc.2023-01 20:37Weymouth, MA2019 Tesla Model 3ADASSUVUnknown31IntersectionRedacted by NHTSA as confidential business information
13781-4727 v2Level 2Tesla, Inc.2023-01 07:40Woodside, CA2018 Tesla Model 3ADASOther Fixed ObjectUnknown39Highway / FreewayRedacted by NHTSA as confidential business information
13781-4733 v2Level 2Tesla, Inc.2023-01 08:17La Mesa, CA2022 Tesla Model 3ADASOther Fixed ObjectUnknown67Highway / FreewayRedacted by NHTSA as confidential business information
13781-4747 v2Level 2Tesla, Inc.2023-01 12:47Atlanta, GA2020 Tesla Model 3ADASPickup TruckUnknown51Highway / FreewayRedacted by NHTSA as confidential business information
13781-4748 v2Level 2Tesla, Inc.2023-01 23:35Berryville, VA2021 Tesla Model YADASVanUnknown39Highway / FreewayRedacted by NHTSA as confidential business information
13781-4749 v2Level 2Tesla, Inc.2023-01 03:26Boca Raton, FL2020 Tesla Model 3ADASSUVUnknown33IntersectionRedacted by NHTSA as confidential business information
13781-4753 v2Level 2Tesla, Inc.2023-01 11:54Nashville-Davidson, TN2021 Tesla Model 3ADASOther Fixed ObjectUnknown42Highway / FreewayRedacted by NHTSA as confidential business information
13781-4754 v2Level 2Tesla, Inc.2023-01 18:40Carlsbad, CA2018 Tesla Model 3ADASUnknownUnknown78Highway / FreewayRedacted by NHTSA as confidential business information
13781-4755 v2Level 2Tesla, Inc.2023-01 17:48Leander, TX2022 Tesla Model YADASOther Fixed ObjectUnknown68Highway / FreewayRedacted by NHTSA as confidential business information
13781-4776 v2Level 2Tesla, Inc.2023-01 21:56Phoenix, AZ2021 Tesla Model YADASPickup TruckUnknown28Highway / FreewayRedacted by NHTSA as confidential business information
13781-4777 v2Level 2Tesla, Inc.2023-01 02:21Lynnwood, WA2023 Tesla Model YADASPassenger CarUnknown11StreetRedacted by NHTSA as confidential business information
13781-4778 v2Level 2Tesla, Inc.2023-01 17:46San Jose, CA2023 Tesla Model 3ADASPickup TruckUnknown59Highway / FreewayRedacted by NHTSA as confidential business information
13781-4786 v2Level 2Tesla, Inc.2023-01 17:40Del Mar, CA2021 Tesla Model 3ADASOther, see NarrativeUnknown48Highway / FreewayRedacted by NHTSA as confidential business information
13781-4787 v2Level 2Tesla, Inc.2023-01 18:18Greenville, VA2022 Tesla Model SADASUnknownUnknown46Highway / FreewayRedacted by NHTSA as confidential business information
13781-4788 v2Level 2Tesla, Inc.2023-01 15:53Linden, VA2023 Tesla Model YADASHeavy TruckUnknown69Highway / FreewayRedacted by NHTSA as confidential business information
13781-4789 v2Level 2Tesla, Inc.2023-01 05:23Boynton Beach, FL2022 Tesla Model YADASOther Fixed ObjectUnknown65Highway / FreewayRedacted by NHTSA as confidential business information
13781-4822 v2Level 2Tesla, Inc.2023-01 23:59Mendota, MN2018 Tesla Model XADASSUVUnknown54IntersectionRedacted by NHTSA as confidential business information
13781-4823 v2Level 2Tesla, Inc.2023-01 09:37Greenbelt, MD2022 Tesla Model XADASUnknownUnknown55Highway / FreewayRedacted by NHTSA as confidential business information
13781-7185 v2Level 2Tesla, Inc.2023-01 08:14Los Angeles, CA2022 Tesla Model 3ADASAnimalUnknown84Highway / FreewayRedacted by NHTSA as confidential business information
28349-4648 v8Level 2Lucid USA, Inc.2023-01 06:52Los Alamitos, CA2022 Lucid AirADASHeavy TruckUnknown61Highway / FreewayRedacted by NHTSA as confidential business information
30270-4768 v2ADSWaymo LLC2023-01 13:38Phoenix, AZ2021 Jaguar I-PaceADSMotorcycleNo Injuries Reported8Intersection
Other than updating the Law Enforcement Investigating? field, the content of this report is unchanged from the initial report submitted on January 25, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On J…Other than updating the Law Enforcement Investigating? field, the content of this report is unchanged from the initial report submitted on January 25, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2023 at 1:38 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision with a minibike whose rider was no longer on it on [XXX] at [XXX]. The Waymo AV was traveling in the leftmost lane on eastbound [XXX], with a group of smaller motorcycles, more commonly known as minibikes, traveling in the right adjacent lane next to and ahead of the Waymo AV. A minibike rider in the group lost control and fell off the minibike a short distance ahead of the Waymo AV in the adjacent lane and the minibike, without a rider, tumbled into the Waymo AV's lane. The Waymo AV applied maximum brake force but made contact with the riderless minibike just before coming to a stop. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The minibike was damaged but it is not possible to determine whether all or some of that damage occurred when the minibike fell to the road before the collision. Because we checked on the minibike riders well-being shortly after the crash, Waymo is aware that the individual sustained minor injuries when they fell from the minibike but the subsequent collision with the riderless minibike did not cause those injuries. Although we do not believe this event falls under Request No. 1 of Standing General Order 2021-01, we consulted NHTSA and submitted this report at the agencys request on the day of the consultation. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-4880ADSWaymo LLC2023-01 17:36Phoenix, AZ2021 Jaguar I-PaceADSFirst Responder VehicleNo Injuries Reported0Parking Lot
On January [XXX], 2023 at 5:36 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a tow truck in a parking lot near [XXX] and [XXX]. While the Waymo AV stopped in a pa…On January [XXX], 2023 at 5:36 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a tow truck in a parking lot near [XXX] and [XXX]. While the Waymo AV stopped in a parking lot in autonomous mode, a tow truck approached from behind the Waymo and attempted to complete a multi-point turn. While performing a multi-point turn, the tow truck reversed into the rear left sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo 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-4881ADSWaymo LLC2023-01 17:08San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported34Intersection
On January [XXX], 2023 at 5:08 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling north on […On January [XXX], 2023 at 5:08 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] when, upon entering the intersection at [XXX], a passenger vehicle which had previously been stopped at a red light, proceeded through the red light. The passenger vehicle approached from the left and made contact with the left rear bumper of the Waymo AV. The other vehicle immediately left the scene of the collision. 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-4882ADSWaymo LLC2023-01 13:53Chandler, AZ2017 Chrysler PacificaADSPickup TruckNo Injuries Reported0Intersection
On January [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a pickup truck on [XXX] and [XXX]. While attempting a right turn from [XXX] onto [XX…On January [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a pickup truck on [XXX] and [XXX]. While attempting a right turn from [XXX] onto [XXX], the Waymo AV was stopped at a stop sign while yielding to traffic approaching from the left. A truck that had previously been stopped behind the Waymo AV proceeded 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. 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-7598ADSWaymo LLC2023-01 17:08San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported34Intersection
On January [XXX], 2023 at 5:08 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling north on […On January [XXX], 2023 at 5:08 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] when, upon entering the intersection at [XXX], a passenger vehicle which had previously been stopped at a red light, proceeded through the red light. The passenger vehicle approached from the left and made contact with the left rear bumper of the Waymo AV. The other vehicle immediately left the scene of the collision. 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. This is an update to the previously submitted report 30270-7257 submitted on 2/15/2023, which had incorrectly provided the DRIVER / OPERATOR TYPE as "None and the MILEAGE as 22991.
30410-4799ADSMotional2023-01 13:17Las Vegas, NV2021 Hyundai Ioniq 5ADSPassenger CarNo Injuries Reported18StreetRedacted by NHTSA as confidential business information
30531-4883ADSTransdev Alternative Services2023-01 17:08San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported34Intersection
On January [XXX], 2023 at 5:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling north on…On January [XXX], 2023 at 5:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] when, upon entering the intersection at [XXX], a passenger vehicle which had previously been stopped at a red light, proceeded through the red light. The passenger vehicle approached from the left and made contact with the left rear bumper of the Waymo AV. The other vehicle immediately left the scene of the collision. 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. 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.
30610-4814 v2ADSZoox, Inc.2023-01 15:00Las Vegas, NV2016 Toyota HighlanderADSPassenger CarNo Injuries Reported24Street
A Zoox vehicle was proceeding northbound on [XXX]. towards [XXX]. when a passenger vehicle in the right adjacent lane swerved into the Zoox vehicles lane and made contact with the right passenger side door. The other veh…A Zoox vehicle was proceeding northbound on [XXX]. towards [XXX]. when a passenger vehicle in the right adjacent lane swerved into the Zoox vehicles lane and made contact with the right passenger side door. The other vehicle also made contact with the vehicle in front of them after contacting the Zoox vehicle. There were no injuries reported at that time and police were not called. Zoox is submitting this updated report to include new information of a claim dated [XXX], 2023, including unspecified "personal injury." This update provides complete information to date for this incident.
30610-4815ADSZoox, Inc.2023-01 18:40San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported3Street
A Zoox vehicle in autonomous mode was proceeding straight in its lane on [XXX] in San Francisco, CA when an occupant of a parallel parked car (Vehicle 2) abruptly opened its rear passenger side door into the side of the …A Zoox vehicle in autonomous mode was proceeding straight in its lane on [XXX] in San Francisco, CA when an occupant of a parallel parked car (Vehicle 2) abruptly opened its rear passenger side door into the side of the Zoox vehicle, causing minor damage to both vehicles. The Zoox operator disengaged as a result of the contact. There were no injuries and the police were not called. This a resubmission of the same report and information submitted February 14, 2023.
30690-4793ADSRobotic Research2023-01 11:01Peachtree Corners, GA2018 Local Motors 2.0ADSOther Fixed ObjectNo Injuries Reported9Street
On January [XXX], 2023, RRAI received a support request through their Customer Support Portal from Beep, Inc., the owner of the vehicle, regarding their Olli 2.0 vehicle bumping into the curb in Peachtree Corners, GA. At…On January [XXX], 2023, RRAI received a support request through their Customer Support Portal from Beep, Inc., the owner of the vehicle, regarding their Olli 2.0 vehicle bumping into the curb in Peachtree Corners, GA. At 11:01 am, while running the normal route, the Olli contacted the adjacent curb on the front right side, causing tie rod and cosmetic damage. No one was injured and the only damage was to the vehicle itself. The customer contacted RRAI through the client support portal shortly after the incident. No injuries occurred, there were no passengers besides the safety operator, no other vehicles were involved, and no emergency systems were engaged. Olli 2.0 (S/N 2-18) is an 8-passenger shuttle that is no longer manufactured. The vehicle manufacturer, Local Motors, dissolved in 2022. Local Motors contracted RRAI to install autonomy kits for several Olli shuttles during the period of 2018 - 2020. RRAI provided some support for initial site deployment and ensured customer safety operators were trained on the autonomy system. Since the Local Motors dissolution in 2022, almost all Olli vehicles have been decommissioned. To date, we have concluded the following: 1. There were no updates or alterations made by RRAI in the months prior to Jan [XXX]. In previous operations, including the immediately preceding operations on January 20th, 2023, Olli 2-18 ran the route as normal with no anomalies. There were no software updates or other system changes before it was run again on January [XXX], 2023, the date of curb contact. 2. The root cause of the curb contact was a communication error with the HD Map registration module. HD Map registration utilizes real-time lidar and positioning data and compares that to a-priori HD maps stored within the autonomy system. A communication problem occurred between the computer running the map registration software and the computer running the navigation algorithms. The cause for the communication problem has been identified and a fix has been implemented to prevent the issue from happening again (see below). 3. Steering was out of calibration. It was noted through data collection that the steering was out of calibration at time of incident. The autonomy system was attempting to correct this issue, but the vehicular steering system could not achieve the required turn radius. This is a vehicular maintenance concern managed by the customer. It was determined that the HD map registration issue had not been observed during autonomous operations in the previous four years. The solution to prevent further occurrences includes: 1. Implementing a self-diagnostic routine upon system boot, which ensures the communication connection is established. If the connection is not established, this diagnostic will prevent the vehicle from driving autonomously. 2. Updating the error checks to ensure that during run time, the vehicle will come to a controlled stop in event of a communication problem. 3. Working with the customer to recalibrate the steering, and assisting in reviewing customer's vehicle maintenance checks for steering calibration if necessary. 4. Continuing to review data to determine other concerns or improvements.
62-11736Level 2Honda (American Honda Motor Co.)2023-01Buffalo, NY2023 HONDA CR-VAlleged EngagedOther Fixed ObjectNo Injured Reported65Highway / Freeway
Honda customer service contacted and confirmed with the customer that the vehicle was in an accident and that the passenger side airbags deployed. The customer stated there were no injuries. I empathized with the custome…Honda customer service contacted and confirmed with the customer that the vehicle was in an accident and that the passenger side airbags deployed. The customer stated there were no injuries. I empathized with the customer and stated I was glad no injuries were sustained. I asked the customer to provide a brief description of the accident. The customer stated he was on an 8-hour drive and was on a two-way road and to not get tired he had LKAS and ACC on. The customer stated that ACC was set to 65 MPH and the distance was set to two bars. The customer stated there was only a line in the middle of the road since it was only a two-way road but can't remember the color of the line. The customer stated that suddenly the vehicle steered to the right, and he hit a fence. The customer can't remember if the LKAS indicator line were filled or blank but stated that it was hard to control the steering as it was steering itself. The customer stated he drove the vehicle away from that and when he got to a railroad crossing, he stepped on the brakes and the vehicle did not stop and he lost control of the vehicle. The customer stated that this is after the first incident of hitting the fence and ACC and LKAS were not on at this time because there were errors on the dash. The customer stated he contacted his insurance company, and they said this will be a total loss but hadn't not processed the total loss yet. NOTE: We recently let NHTSA's Office of Chief Council know about this past incident from 2023.
62-11747Level 2Honda (American Honda Motor Co.)2023-01 05:08Alice, TX2022 HONDA CivicAlleged EngagedHeavy TruckFatalityUnknown
On Wednesday, January [XXX], 2023, at approximately 5:08 a.m., [XXX] was operating his Honda Civic traveling eastbound on [XXX], in rural Alice, Jim Wells County, Texas.[XXX] is a four-lane highway with two (2) lanes ru…On Wednesday, January [XXX], 2023, at approximately 5:08 a.m., [XXX] was operating his Honda Civic traveling eastbound on [XXX], in rural Alice, Jim Wells County, Texas.[XXX] is a four-lane highway with two (2) lanes running east and two (2) lanes running west that are divided by a grassy median. [XXX] was traveling in the eastbound inside lane. [XXX] was the sole occupant of his Honda Civic. The Honda Civic's CMB and ACC systems were "turned on" and "engaged." At that time, a 2015 Mack Granite gin pole tractor (VIN 1.[XXX]) in combination with a commercial flatbed 1982 Lufkin Industries trailer (VIN [XXX]) was traveling ahead of [XXX] also in the eastbound inside lane. The Mack tractor was traveling at 20-25 m.p.h. [XXX] was driving the Mack tractor. [XXX] was transporting a large, gray, skid mounted flowback tank that was loaded onto the Lufkin trailer (collectively "Tractor-Trailer"). As [XXX] Honda Civic approached the Tractor- Trailer, the Honda Civic's CMBS and/or ACC system failed to stop or decelerate the Honda Civic and/or alert him of an impending frontal collision. NOTE: We recently let NHTSA's Office of Chief Council know about this past incident from 2023.
62-4600Level 2Honda (American Honda Motor Co.)2023-01Livonia, MI2020 Honda CRVADASUnknownNo Injuries Reported65Highway / Freeway
The customer was driving on a freeway on a rainy day with his Adaptive Cruise Control (ACC) and Lane Keep Assist System (LKAS) engaged. The customer explained that when he changed lanes, the LKAS indicator was not filled…The customer was driving on a freeway on a rainy day with his Adaptive Cruise Control (ACC) and Lane Keep Assist System (LKAS) engaged. The customer explained that when he changed lanes, the LKAS indicator was not filled due to the vehicle not detecting the lane markings on the road due to the weather. After completing the lane change, the customer approached a vehicle that was slowing down. The customer alleged that he thought his vehicle's ACC would slow his vehicle down due to the slowing vehicle in front of him. The customer stated that he did not engage the vehicle's brake until he realized that his vehicle did not slow down. As a result, the customer crashed into the vehicle in front of him. The customer reported that both the driver and passenger airbags deployed and no injuries occurred.
669-5395 v3Level 2Hyundai Motor America2023-01 12:00Redwood City, CA2023 Hyundai PalisadeADASOther Fixed ObjectMinorHighway / Freeway
A customer was operating the subject Palisade vehicle in the right-most lane of [XXX], a major California highway, at an alleged 65 MPH. The Highway Drive Assist ("HDA") feature allegedly caused the vehicle to inadverten…A customer was operating the subject Palisade vehicle in the right-most lane of [XXX], a major California highway, at an alleged 65 MPH. The Highway Drive Assist ("HDA") feature allegedly caused the vehicle to inadvertently steer into the highway divider, resulting in a collision and minor injuries sustained by the operator. NASO is in process of reaching out to the customer for additional information. 10-day Update to 669-5395-1: No new information from customer. Vehicle is on HOLD for potential inspection in salvage yard. Monthly Update to 669-5395-2: No new information. HMA has requested additional documentation from the owner.
10003-6050 v2Level 2Navistar, Inc.2022-12 08:20Natural Bridge, VA2022 International LT625Unknown, see NarrativeOther Fixed ObjectNo Injuries Reported55Highway / Freeway
This vehicle is equipped with Lane Keep Assist (LKA) feature. At this time, the status of the LKA system during this event is unknown. Vehicle 1 (V1) was Northbound on [XXX] in [XXX] County near Natural Bridge, Virginia.…This vehicle is equipped with Lane Keep Assist (LKA) feature. At this time, the status of the LKA system during this event is unknown. Vehicle 1 (V1) was Northbound on [XXX] in [XXX] County near Natural Bridge, Virginia. As stated in the police report, V1 ran off road left, struck the guardrail, went over embankment, and struck several trees. V1 was towed from the scene and operator of V1 was issued a citation. The road at the crash location curves to the right. Available EDR data indicates no significant changes in speed or direction in the 7 seconds prior to the incident.
10039-4636 v4Level 2BMW of North America, LLC2022-12 07:05Fairfield, CA2022 BMW X5ADASOther Fixed ObjectMinor70Highway / FreewayRedacted by NHTSA as confidential business information
1243-4601 v3Level 2Subaru of America, Inc.2022-12 17:31Blue Grass, IA2020 Subaru OutbackADASPickup TruckMinor67Highway / Freeway
The customer is not alleging any defect with any ADAS related system. According to the customer's statement, the subject vehicle was proceeding southbound on [XXX] in the LH lane traveling at 67 MPH with adaptive cruise …The customer is not alleging any defect with any ADAS related system. According to the customer's statement, the subject vehicle was proceeding southbound on [XXX] in the LH lane traveling at 67 MPH with adaptive cruise control (ACC) and lane centering (LC) engaged when a pickup truck entering the highway merged into the customer's lane of travel with an estimated spacing of less than 50 feet. The customer stated that the pre-collision braking did apply and he was also able to depress the brake pedal. The customer's evasive steering and braking was not sufficient to avoid a crash. The customer's vehicle rear-ended the merging vehicle and as a result of the collision the customer's vehicle left the roadway and caught fire. The subject vehicle was towed to a Copart facility in Eldridge, IA. According the police accident report, the Ford F-150 pickup truck was positioned on [XXX] facing northbound. The driver failed to see the approaching subject vehicle and made a LH turn into the LH lane of [XXX]. The subject vehicle impacted the rear of the pickup truck. The pickup truck sustained damage but was drivable. The subject vehicle sustained heavy damage and was on fire. Subaru inspected the subject vehicle on 1/26/2023. The vehicle had sustained damage consistent with the accident details. No data could be collected from the vehicle. There was thermal damage to the ACM module to the point that the case was breached and the internal PCB was exposed.
1243-4796 v4Level 2Subaru of America, Inc.2022-12 15:47Cedar Park, TX2021 Subaru CrosstrekADASSUVMinor45Street
The customer is not alleging any defect with the vehicle. The customer was directed by a retailer to contact Subaru with a request for Goodwill Loyalty Purchase Assistance to be used toward the purchase of a new Subaru …The customer is not alleging any defect with the vehicle. The customer was directed by a retailer to contact Subaru with a request for Goodwill Loyalty Purchase Assistance to be used toward the purchase of a new Subaru vehicle. According to the customer's statement, the subject vehicle was proceeding at 45 MPH in Cedar Park, TX when another vehicle pulled out in front of the subject vehicle and the customer did not have enough time to react to avoid the collision. The customer's response to an incident questionnaire indicates that Adaptive Cruise Control (ACC) and Lane Centering (LC) were engaged at the time of the incident. The customer further stated the Automatic Emergency Brake (AEB) did engage to reduce the speed at the time of impact. As a result of the collision, no airbags deployed and subject vehicle was towed from the location of the incident. A police report confirms the location of the accident on northeast bound lanes of [XXX] in Cedar Park Texas at 3:47 PM on [XXX]. The report indicates that the driver of the other vehicle failed to yield the right of way while leaving a private driveway (parking lot exit).
1306-4390 v2ADSToyota Motor Engineering & Manufacturing2022-12 09:02Sun City, AZ2021 Toyota SiennaADSMotorcycleNo Injuries Reported0Street
This report is being submitted because May Mobility notified Toyota on Dec. 9, 2022 of 1-Day Report submission 30413-4378-1,related to an incident that occurred on Dec. [XXX], 2022. Toyota has no additional information o…This report is being submitted because May Mobility notified Toyota on Dec. 9, 2022 of 1-Day Report submission 30413-4378-1,related to an incident that occurred on Dec. [XXX], 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned 1-Day Report. Please refer to the report from May Mobility for details. This report is a 10-Day update. The original report ID is 1306-4390-1.
13781-4344 v2Level 2Tesla, Inc.2022-12 16:45Woodside, CA2018 Tesla Model 3ADASOther Fixed ObjectUnknown49Highway / FreewayRedacted by NHTSA as confidential business information
13781-4353 v3Level 2Tesla, Inc.2022-12 09:00Tacoma, WA2019 Tesla Model 3ADASOther Fixed ObjectUnknown35Highway / FreewayRedacted by NHTSA as confidential business information
13781-4354 v3Level 2Tesla, Inc.2022-12 05:31Mercer Island, WA2020 Tesla Model YADASOther, see NarrativeUnknown22StreetRedacted by NHTSA as confidential business information
13781-4355 v2Level 2Tesla, Inc.2022-12 09:59Claremont, CA2020 Tesla Model 3ADASPassenger CarUnknown80Highway / FreewayRedacted by NHTSA as confidential business information
13781-4356 v2Level 2Tesla, Inc.2022-12 22:37Redwood City, CA2020 Tesla Model 3ADASOther Fixed ObjectUnknown56Highway / FreewayRedacted by NHTSA as confidential business information
13781-4357 v2Level 2Tesla, Inc.2022-12 23:37Livermore, CA2021 Tesla TeslaADASOther Fixed ObjectUnknown26Highway / FreewayRedacted by NHTSA as confidential business information
13781-4358 v2Level 2Tesla, Inc.2022-12 05:37Chula Vista, CA2022 Tesla Model XADASPassenger CarUnknown26StreetRedacted by NHTSA as confidential business information
13781-4359 v2Level 2Tesla, Inc.2022-12 22:01Seattle, WA2021 Tesla Model YADASOther Fixed ObjectUnknown57Highway / FreewayRedacted by NHTSA as confidential business information
13781-4361 v2Level 2Tesla, Inc.2022-12 08:26Fresno, CA2019 Tesla Model 3ADASOther Fixed ObjectUnknown35Highway / FreewayRedacted by NHTSA as confidential business information
13781-4376 v2Level 2Tesla, Inc.2022-12 23:13Los Angeles, CA2021 Tesla Model YADASPassenger CarUnknown60Highway / FreewayRedacted by NHTSA as confidential business information
13781-4380 v2Level 2Tesla, Inc.2022-12 03:05El Monte, CA2022 Tesla Model 3ADASPassenger CarUnknown17Highway / FreewayRedacted by NHTSA as confidential business information
13781-4381 v2Level 2Tesla, Inc.2022-12 13:51Mansfield, NJ2022 Tesla Model YADASOther Fixed ObjectUnknown60Highway / FreewayRedacted by NHTSA as confidential business information
13781-4387 v2Level 2Tesla, Inc.2022-12 04:40Oklahoma City, OK2018 Tesla Model 3ADASUnknownUnknown63UnknownRedacted by NHTSA as confidential business information
13781-4402 v2Level 2Tesla, Inc.2022-12 16:58McKinney, TX2021 Tesla Model YADASOther Fixed ObjectUnknown60Highway / FreewayRedacted by NHTSA as confidential business information
13781-4403 v2Level 2Tesla, Inc.2022-12 08:16Long Beach, CA2022 Tesla Model YADASPole / TreeUnknown8Highway / FreewayRedacted by NHTSA as confidential business information
13781-4404 v2Level 2Tesla, Inc.2022-12 09:46Los Angeles, CA2018 Tesla Model 3ADASOther Fixed ObjectUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-4407 v2Level 2Tesla, Inc.2022-12 12:38South El Monte, CA2021 Tesla Model YADASOther Fixed ObjectUnknown8Highway / FreewayRedacted by NHTSA as confidential business information
13781-4408 v2Level 2Tesla, Inc.2022-12 04:13Westminster, CA2021 Tesla Model 3ADASSUVUnknown68Highway / FreewayRedacted by NHTSA as confidential business information
13781-4409 v2Level 2Tesla, Inc.2022-12 18:57Redlands, CA2021 Tesla Model 3ADASOther Fixed ObjectUnknown31Highway / FreewayRedacted by NHTSA as confidential business information
13781-4410 v2Level 2Tesla, Inc.2022-12 00:30Alpine, NJ2021 Tesla Model YADASSUVUnknown11IntersectionRedacted by NHTSA as confidential business information
13781-4411 v2Level 2Tesla, Inc.2022-12 18:36Danville, CA2022 Tesla TeslaADASOther Fixed ObjectUnknown44Highway / FreewayRedacted by NHTSA as confidential business information
13781-4412 v2Level 2Tesla, Inc.2022-12 18:05Houston, TX2021 Tesla Model YADASSUVUnknown28StreetRedacted by NHTSA as confidential business information
13781-4413 v2Level 2Tesla, Inc.2022-12 08:21Austin, TX2020 Tesla Model 3ADASPassenger CarUnknown29IntersectionRedacted by NHTSA as confidential business information
13781-4414 v2Level 2Tesla, Inc.2022-12 00:12Union City, CA2022 Tesla Model YADASUnknownNo Injuries ReportedUnknownRedacted by NHTSA as confidential business information
13781-4420 v2Level 2Tesla, Inc.2022-12 05:24San Mateo, CA2017 Tesla Model XADASOther, see NarrativeUnknown68Highway / FreewayRedacted by NHTSA as confidential business information
13781-4421 v2Level 2Tesla, Inc.2022-12 22:12Short Hills, NJ2018 Tesla Model XADASUnknownUnknown52UnknownRedacted by NHTSA as confidential business information
13781-4423 v2Level 2Tesla, Inc.2022-12 16:59Del Mar, CA2021 Tesla Model YADASOther Fixed ObjectUnknown31Highway / FreewayRedacted by NHTSA as confidential business information
13781-4424 v2Level 2Tesla, Inc.2022-12 14:45Los Angeles, CA2022 Tesla Model YADASOther, see NarrativeUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-4440 v2Level 2Tesla, Inc.2022-12 15:11Evansville, IN2022 Tesla Model 3ADASUnknownUnknown49Highway / FreewayRedacted by NHTSA as confidential business information
13781-4443 v2Level 2Tesla, Inc.2022-12 21:53Vista, CA2022 Tesla Model YADASPassenger CarUnknown53IntersectionRedacted by NHTSA as confidential business information
13781-4444 v2Level 2Tesla, Inc.2022-12 12:17Tonganoxie, KS2018 Tesla Model 3ADASUnknownUnknown65UnknownRedacted by NHTSA as confidential business information
13781-4445 v2Level 2Tesla, Inc.2022-12 01:12Kent, WA2020 Tesla Model YADASPassenger CarUnknown40StreetRedacted by NHTSA as confidential business information
13781-4446 v2Level 2Tesla, Inc.2022-12 00:55Tucson, AZ2022 Tesla Model YADASUnknownUnknown64Highway / FreewayRedacted by NHTSA as confidential business information
13781-4479 v2Level 2Tesla, Inc.2022-12 18:00Inglewood, CA2018 Tesla Model XADASSUVUnknown35Highway / FreewayRedacted by NHTSA as confidential business information
13781-4501 v2Level 2Tesla, Inc.2022-12 13:08Melbourne, FL2018 Tesla Model 3ADASPassenger CarUnknown34IntersectionRedacted by NHTSA as confidential business information
13781-4502 v2Level 2Tesla, Inc.2022-12 23:16Denver, PA2020 Tesla Model YADASOther Fixed ObjectUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-4503 v2Level 2Tesla, Inc.2022-12 10:40Annandale, VA2022 Tesla Model YADASPassenger CarUnknown58Highway / FreewayRedacted by NHTSA as confidential business information
13781-4504 v2Level 2Tesla, Inc.2022-12 16:02Carnesville, GA2021 Tesla Model YADASUnknownUnknown43Highway / FreewayRedacted by NHTSA as confidential business information
13781-4513 v2Level 2Tesla, Inc.2022-12 01:56Chelmsford, MA2022 Tesla Model YADASPassenger CarUnknown25IntersectionRedacted by NHTSA as confidential business information
13781-4538 v2Level 2Tesla, Inc.2022-12 14:48Fort Collins, CO2019 Tesla Model 3ADASPickup TruckUnknown0IntersectionRedacted by NHTSA as confidential business information
13781-4539 v2Level 2Tesla, Inc.2022-12 17:23Tappan, NY2020 Tesla Model YADASSUVUnknown51Highway / FreewayRedacted by NHTSA as confidential business information
13781-4542 v2Level 2Tesla, Inc.2022-12 08:04Garden Grove, CA2019 Tesla Model 3ADASPassenger CarUnknown59Highway / FreewayRedacted by NHTSA as confidential business information
13781-4543 v2Level 2Tesla, Inc.2022-12 18:08Burlington, NC2019 Tesla Model 3ADASOther Fixed ObjectUnknown70Highway / FreewayRedacted by NHTSA as confidential business information
13781-4552 v2Level 2Tesla, Inc.2022-12 04:04Auburn, CA2022 Tesla Model YADASOther Fixed ObjectUnknown59Highway / FreewayRedacted by NHTSA as confidential business information
13781-4553 v2Level 2Tesla, Inc.2022-12 03:52North Royalton, OH2018 Tesla Model 3ADASPickup TruckUnknown35Rural RoadRedacted by NHTSA as confidential business information
13781-4556 v2Level 2Tesla, Inc.2022-12 15:38Vallejo, CA2021 Tesla Model YADASOther, see NarrativeUnknown45Highway / FreewayRedacted 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.