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 7601 to 7700.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
13781-3939 v2Level 2Tesla, Inc.2022-09 15:39San Jose, CA2018 Tesla Model XADASPassenger CarUnknown22StreetRedacted by NHTSA as confidential business information
13781-3945 v2Level 2Tesla, Inc.2022-09 14:49Dodson, OR2022 Tesla Model YADASUnknownUnknown59Highway / FreewayRedacted by NHTSA as confidential business information
13781-3948 v2Level 2Tesla, Inc.2022-09 22:19Thonotosassa, FL2021 Tesla Model YADASSUVUnknown12Highway / FreewayRedacted by NHTSA as confidential business information
13781-4011 v2Level 2Tesla, Inc.2022-09CA2018 Tesla Model 3ADASUnknownFatalityUnknownRedacted by NHTSA as confidential business information
13781-5248 v2Level 2Tesla, Inc.2022-09Saint Johns County, FL2022 Tesla Model YUnknown, see NarrativeUnknownFatalityUnknownRedacted by NHTSA as confidential business information
273-3763 v2Level 2Chrysler (FCA US, LLC)2022-09 16:30MI2022 Jeep Grand Cherokee Overland 4x4ADASUnknownUnknownUnknownRedacted by NHTSA as confidential business information
30270-3786 v2ADSWaymo LLC2022-09 13:13Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarUnknown0Intersection
Other than updating the ADS Version to the correct Waymo ADS generation, and correcting the Were All Passengers Belted? and Property Damage? fields, the content of this report is unchanged from the initial report submitt…Other than updating the ADS Version to the correct Waymo ADS generation, and correcting the Were All Passengers Belted? and Property Damage? fields, the content of this report is unchanged from the initial report submitted on September [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On September [XXX], 2022 at 1:13 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving two passenger cars on [XXX] at [XXX]. The Waymo AV was stopped in traffic at a red light facing West on [XXX]. The passenger car immediately behind the Waymo AV slowed and came to a near stop when a second passenger car approaching from behind made contact with the rear of the first passenger car, causing that 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away, because of airbag deployment, and because an occupant in one of the passenger vehicles was transported for medical attention. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-4051ADSWaymo LLC2022-09 12:57San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On September [XXX], 2022 at 12:57 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck in a parking lot at [XXX]. The Waymo AV came to a stop in the park…On September [XXX], 2022 at 12:57 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck in a parking lot at [XXX]. The Waymo AV came to a stop in the parking lot while yielding to both pedestrians and an oncoming pickup truck. While the Waymo AV was stopped, the oncoming pickup truck passed the Waymo AV on the left hand side, making contact with the rear left sensor of the Waymo AV. The pickup truck then left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was stationary and 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.
30270-4072ADSWaymo LLC2022-09 09:42San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On September [XXX], 2022 at 9:42 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on[XXX] at [XXX]. The Waymo AV was traveling east on [XXX]…On September [XXX], 2022 at 9:42 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on[XXX] at [XXX]. The Waymo AV was traveling east on [XXX] in autonomous mode when it stopped at a stop sign at [XXX]. A passenger car approaching from behind 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.
30270-4073ADSWaymo LLC2022-09 06:38San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On September [XXX], 2022 at 6:38 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] and [XXX]. While traveling northbound on [XXX], the Waymo …On September [XXX], 2022 at 6:38 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] and [XXX]. While traveling northbound on [XXX], the Waymo AV changed lanes from the center lane to the right lane before slowing to a stop at a red light at [XXX]. While the Waymo AV was making the lane change, the vehicle immediately behind the Waymo AV in the right lane moved to the center lane and made contact with the right rear sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The SUV 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-4074ADSWaymo LLC2022-09 04:03Huntsville, TX2022 Peterbilt 579 EpiqADSOther, see NarrativeNo Injuries Reported35Highway / Freeway
On September [XXX], 2022 at 4:03 AM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Hunstville, Texas was in a collision involving a loose tire on southbound [XXX] near th…On September [XXX], 2022 at 4:03 AM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Hunstville, Texas was in a collision involving a loose tire on southbound [XXX] near the [XXX]. The Waymo AV was in autonomous mode and in the rightmost lane approaching a slow-moving pickup truck traveling behind a slow-moving box truck, when the Waymo AV test driver transitioned to manual mode. The Waymo AV test driver then made a left lane change to pass the two vehicles. As the Waymo AV passed the pick-up truck and box truck, a loose wheel (including attached tire) appeared from behind the box truck rolling toward the Waymo AVs lane. The wheel/tire made contact with the passenger right side rear corner of the Waymo AVs trailer. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AVs trailer 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.
30290-3913 v2ADSArgo AI2022-09 17:24Palo Alto, CA2020 Ford EscapeADSNon-Motorist: CyclistNo Injuries Reported21Street2022-10-[XXX]- Submission of 10 Day Update for Report 30290-3913-1: Argo AI has not received notice of any material new or materially different information about this incident.
30290-3985ADSArgo AI2022-09 10:23Miami, FL2020 Ford EscapeADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-3748 v3ADSCruise LLC2022-09 18:46San Francisco, CA2022 Cruise AVADSMotorcycleMinor7Street
Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound on [XXX] between [XXX] and [XXX]. At the same time, a motorcyclist approaching from the rear began to merge into t…Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound on [XXX] between [XXX] and [XXX]. At the same time, a motorcyclist approaching from the rear began to merge into the Cruise AV's lane behind the Cruise AV. As the motorcycle approached the AV's rear, the AV braked and the motorcycle subsequently made contact with the Cruise AV's rear passenger side bumper, damaging the motorcycle's front fender. The driver of the motorcycle reported minor injuries and police were not called.
30412-3978 v3ADSCruise LLC2022-09 05:14San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0Street
A Cruise autonomous vehicle ("Cruise AV"), operating in driverless autonomous mode, was traveling eastbound on [XXX] between [XXX] and [XXX]. The Cruise AV approached a semi-trailer truck that was stopped in the left lan…A Cruise autonomous vehicle ("Cruise AV"), operating in driverless autonomous mode, was traveling eastbound on [XXX] between [XXX] and [XXX]. The Cruise AV approached a semi-trailer truck that was stopped in the left lane of traffic. The Cruise AV stopped before maneuvering into the bus and taxi lane to pass the semi-trailer truck. After slowly maneuvering around the semi-trailer truck and merging back into the left lane of traffic, the Cruise AV braked, coming to a complete stop, and a Honda Accord traveling behind the Cruise AV attempted to pass the Cruise AV and made contact with the Cruise AV, damaging the rear passenger side bumper of the Cruise AV. The driver of the Honda Accord left the scene without exchanging information. There were no reported injuries.
30413-3943ADSMay Mobility2022-09 09:02Sun City, AZ2021 Toyota SiennaADSPassenger CarNo Injuries Reported0Parking Lot
The May Mobility vehicle was traveling in autonomy through a parking lot and comes to a stop due to a vehicle backing up. Vehicle begins to reverse further so the operator in the May Mobility vehicle takes over and manua…The May Mobility vehicle was traveling in autonomy through a parking lot and comes to a stop due to a vehicle backing up. Vehicle begins to reverse further so the operator in the May Mobility vehicle takes over and manually reverses. The other vehicle continues backing up and does not stop, contacting the front of the May Mobility vehicle. Other vehicle then proceeds to drive away.
30531-3809 v2ADSTransdev Alternative Services2022-09 13:13Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarUnknown0Intersection
Other than updating the ADS Version to the correct Waymo ADS generation, and correcting the "Were All Passengers Belted?" and "Property Damage?" fields, the content of this report is unchanged from the initial report. On…Other than updating the ADS Version to the correct Waymo ADS generation, and correcting the "Were All Passengers Belted?" and "Property Damage?" fields, the content of this report is unchanged from the initial report. On September [XXX], 2022 at 1:13 PM PST a Waymo Autonomous Vehicle ( Waymo AV ) operating in Phoenix, Arizona was in a collision involving two passenger cars on [XXX] at [XXX]. The Waymo AV was stopped in traffic at a red light facing West on [XXX]. The passenger car immediately behind the Waymo AV slowed and came to a near stop when a second passenger car approaching from behind made contact with the rear of the first passenger car, causing that 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away, because of airbag deployment, and because an occupant in one of the passenger vehicles was transported for medical attention. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report ID 30270-3786-1.
30531-4077ADSTransdev Alternative Services2022-09 04:03Huntsville, TX2022 Peterbilt 579 EpiqADSOther, see NarrativeNo Injuries Reported35Highway / Freeway
On September [XXX], 2022 at 4:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Huntsville, Texas was in a collision involving a loose tire on southbound [XXX] near …On September [XXX], 2022 at 4:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Huntsville, Texas was in a collision involving a loose tire on southbound [XXX] near the [XXX]. The Waymo AV was in autonomous mode and in the rightmost lane approaching a slow-moving pickup truk traveling behind a slow-moving box truck, when the Waymo AV test driver transitioned to manual mode. The Waymo AV test driver then made a left lane change to pass the two vehicles. As the Waymo AV passed the pick-up truck and box truck, a loose wheel (including attached tire) appearted from behind the box truck rolling toward the Waymo AV's lane. The wheel/tire made contact with the passenger right side rear corner of the Waymo AV's trailer. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV's trailer sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of WaymoLLC-20220906-0 (rev.20221017215656).
30531-4079ADSTransdev Alternative Services2022-09 12:57San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On September [XXX], 2022 at 12:57 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a pickup truck in a parking lot at [XXX]. The Waymo AV came to a stop in the pa…On September [XXX], 2022 at 12:57 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a pickup truck in a parking lot at [XXX]. The Waymo AV came to a stop in the parking lot while yielding to both pedestrians and an oncoming pickup truck. While the Waymo AV was stopped, the oncoming pickup truck passed the Waymo AV on the left hand side, making contact with the rear left sensor of the Waymo AV. The pickup truck then left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was stationary and engaged in autonomous mode, and a test driver was present (in the driver's seating position). 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 with additional information as it may become available. This report is a duplicate of WaymoLLC-20220910-0 (rev.20221017164138).
30531-4080ADSTransdev Alternative Services2022-09 09:42San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On September [XXX], 2022 at 9:42 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling east on [X…On September [XXX], 2022 at 9:42 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] in autonomous mode when it stopped at a stop sign at [XXX]. A passenger car approaching from behind 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 with additional information as it may become available. This report is a duplicate of WaymoLLC-20220915-0 (rev.20221017212632).
30531-4081ADSTransdev Alternative Services2022-09 06:38San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On September [XXX], 2022 at 6:38 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] and [XXX]. While traveling northbound on [XXX], the Waym…On September [XXX], 2022 at 6:38 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] and [XXX]. While traveling northbound on [XXX], the Waymo AV changed lanes from the center lane to the right lane before slowing to a stop at a red light at [XXX]. While the Waymo AV was making the lane change, the vehicle immediately behind the Waymo AV in the right lane moved to the center lane and made contact with the right rear sensor 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 SUV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-20220917-0 (rev.20221017214905).
30571-3768Level 2NVIDIA CORP2022-09 18:15San Jose, CA2021 Mercedes-Benz S-ClassADASSUVNo Injuries Reported1Street
Test vehicle 3416 was manually operated while traveling southbound on [XXX], San Jose CA; a two-lane one-way street; when the operator came to a vacant parking space between two parked vehicles. The test operator engaged…Test vehicle 3416 was manually operated while traveling southbound on [XXX], San Jose CA; a two-lane one-way street; when the operator came to a vacant parking space between two parked vehicles. The test operator engaged the ADAS parking assist system to complete a parallel parking maneuver. The test vehicle negotiated the maneuver, reversing into the parking space. When the vehicle shifted from reverse and to drive it was traveling at ~1 MPH when it made contact with the rear bumper of a parked SUV. The test operator disengaged the system and manually completed the parking maneuver. There were no injuries or damage reported.
30571-3815Level 2NVIDIA CORP2022-09 18:15San Jose, CA2021 Mercedes-Benz S-ClassADASSUVNo Injuries Reported1Street
Test vehicle 3416 was manually operated while traveling southbound on [XXX], San Jose CA a two-lane one-way street when the operator came to a vacant parking space between two parked vehicles. The test operator engaged t…Test vehicle 3416 was manually operated while traveling southbound on [XXX], San Jose CA a two-lane one-way street when the operator came to a vacant parking space between two parked vehicles. The test operator engaged the ADAS parking assist system to complete a parallel parking maneuver. The test vehicle negotiated the maneuver, reversing into the parking space. When the vehicle shifted from reverse and to drive it was traveling at 1 MPH when it made contact with the rear bumper of a parked SUV. The test operator disengaged the system and manually completed the parking maneuver. There were no injuries or damage reported.
30610-3752 v2ADSZoox, Inc.2022-09 11:30San Francisco, CA2016 Toyota HighlanderADSNon-Motorist: CyclistNo Injuries Reported2Street
A Zoox vehicle in autonomy was slowing for a right turn from [XXX] to [XXX] in San Francisco, CA with its turn indicator and brake lights illuminated, when a following bicyclist struck the rear right corner of the Zoox v…A Zoox vehicle in autonomy was slowing for a right turn from [XXX] to [XXX] in San Francisco, CA with its turn indicator and brake lights illuminated, when a following bicyclist struck the rear right corner of the Zoox vehicle. The Zoox vehicle camera bracket was damaged. Police were not called and no injuries were reported. This 10-Day update provides complete information for this incident.
502-3906 v2Level 2Ford Motor Company2022-09Portland, MI2021 Ford EdgeADASOther Fixed ObjectNo Injuries ReportedHighway / Freeway
10-Day Update on report 502-3906-1 (reported on Sept [XXX], 2022): Ford updated the vehicle Mileage, and no other information has been received of any material new or materially different information about this inciden…10-Day Update on report 502-3906-1 (reported on Sept [XXX], 2022): Ford updated the vehicle Mileage, and no other information has been received of any material new or materially different information about this incident. 1-Day (report) The driver reported to Ford that they were traveling East on [XXX] (near [XXX]) while using Adaptive Cruise Control (ACC) and Lane Centering Assist (LCA), at approximately 70 mph in the Right-hand lane. The driver reached towards the center console/passenger seat, while keeping their left hand on steering wheel and the driver inadvertently pulled the steering wheel to the right causing the vehicle to cross the lane boundary and scrape down a barrier adjacent to the shoulder. The drivers inadvertent corrections steered the vehicle out if its lane and into the barrier. The driver's interaction (manual steering input) overrides the LCA feature. The vehicle suffered damage to the right wheel and driveshaft and was towed.
502-3914 v2ADSFord Motor Company2022-09 17:24Palo Alto, CA2020 Ford EscapeADSNon-Motorist: CyclistNo Injuries Reported21Street2022-10-[XXX] - Submission of 10-Day Update reported by Argo AI to Ford (Report # 30290-3913-2): Argo AI has not received notice of any material new or materially different information about this incident.
502-4026ADSFord Motor Company2022-09 10:23Miami, FL2020 Ford EscapeADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
540-3753 v3ADSGeneral Motors, LLC2022-09 18:46San Francisco, CA2022 Cruise AVADSMotorcycleMinor7Street
On September 26, 2024 GM Cruise Holdings LLC ("Cruise") filed an update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manu…On September 26, 2024 GM Cruise Holdings LLC ("Cruise") filed an update report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3748-3)
540-4019 v3ADSGeneral Motors, LLC2022-09 05:14San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0Street
On September 26, 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…On September 26, 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-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3978-3)
753-3912 v2Level 2Kia America, Inc.2022-09 13:00Commerce, CA2022 Kia EV6ADASSUVNo Injuries Reported16Highway / Freeway
On September [XXX], 2022, a Kia Customer Care Center (CC) agent was dispatched a case where the customer is alleging the "collision assistance feature did not follow through" resulting in a rear end collision with a 2022…On September [XXX], 2022, a Kia Customer Care Center (CC) agent was dispatched a case where the customer is alleging the "collision assistance feature did not follow through" resulting in a rear end collision with a 2022 Ford Expedition. Customer alleges he was traveling approximately 50mph on [XXX] with a following distance of 60-80ft with various safety features active including lane keeping assist, Forward Collision Avoidance and adaptive cruise control. The customer stated the Expedition had a broken taillight and it was difficult to determine whether the vehicle was slowing down. Customer noticed his Kia EV6 was not slowing down as his vehicle was approaching the Expedition at approximately 40ft causing him to manually pressed on the brakes. Customer reported that after depressing the brakes, the collision avoidance alarm sounded but the brakes felt "spongy". Customer alleges the system did not apply what the customer believed to be maximum braking power, even though he had the brakes fully depressed. Customer rear-ended the Expedition at 15mph. The customer's vehicle was towed. When asked by CC, the customer reported that HDA and cruise control were engaged at the time of the incident but the customer did not allege that either of those systems caused the accident. The subject Kia EV6 is equipped with the ADAS Level 2 Highway Driving Assist (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. However, there is no indication from the facts currently available that the HDA system was not working properly. Kia is currently working on scheduling an inspection of the vehicle. **9/[XXX]/2022 10-Day Update** Kia inspected the subject 2022 EV6 vehicle on September [XXX], 2022 and downloaded the vehicles EDR data. Based upon a review of the data, the subject vehicle did not have Smart Cruise Control with Stop & Go (SCC w/ Stop & Go) engaged at least in the last 5 seconds prior to the crash. In order for HDA to operate, SCC must be engaged. The EDR data identifies the following: 1) Sign of the last accelerator input is 2.5 seconds prior to crash 2) the first sign of brake pedal input is at 1 second prior to crash 3) the vehicles FCA (Frontal Crash Avoidance) system started warning the driver from 1.6 seconds prior to crash all the way to point of crash and went through all 3 levels of FCA warning (Level 1 warning 1.6-1.4 seconds before crash, Level 2 warning 1.3-0.6 seconds before crash, and the last Level 3 0.5 seconds to point of crash.). Based on the EDR data, the accident was not caused by a failure and/or disengagement of HDA.
1306-3876 v3Level 2Toyota Motor Engineering & Manufacturing2022-08 09:16Park Hills, MO2022 Toyota Camry HVADASOther Fixed ObjectUnknown22Highway / Freeway
On August [XXX], 2022, Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. The contact record indicates that the owner alleged that, "hi…On August [XXX], 2022, Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. The contact record indicates that the owner alleged that, "his daughter told him that she was traveling down a hill towards a curb at the bottom of the road when suddenly and unexpectedly the steering assist completely locked up on her preventing her from being able to steer the vehicle." Guest stated that she ended up loosing [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] control of her brand new (2022 Toyota Camry) vehicle causing her to spin out of control and into a ditch." Three other occupants were in the vehicle at the time the incident occurred. On August [XXX], 2022, Toyota completed a vehicle inspection and field report on the incident. On September [XXX], 2022, after additional analysis of the incident details, Toyota determined the case was reportable under the SGO. Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) data from the subject vehicle. VCH provides an approximately 7.9 second pre-crash data recording, and EDR provides an approximately 5 second pre-crash data recording. Based on the data obtained, the following information was observed: Lane Trace Assist (LTA) was engaged during the recording until approximately 5.1 seconds prior to the crash event. ADAS L2 disengagement occurred due to LTA disengagement from driver steering input. The driver turned the vehicle left at a steering angle increasing from 9 degrees to 49.5 degrees. Dynamic Radar Cruise Control (DRCC) was engaged during the recording until the crash event occurred. As a result of the crash incident, no airbags deployed in the subject vehicle and it was driven from the crash scene. 1 occupant was reportedly taken to the ER for headaches and potential concussion. This report is a monthly update. The original report ID is 1306-3876-1.
1306-4010ADSToyota Motor Engineering & Manufacturing2022-08 16:15Arlington, TX2020 Lexus RX450HADSPickup TruckNo Injuries Reported10Intersection
This report is being submitted because May Mobility notified Toyota on Sept. 8, 2022 of Monthly Report submission 1306-3355-1,related to an incident reported in July 2022. Toyota has no additional information on this inc…This report is being submitted because May Mobility notified Toyota on Sept. 8, 2022 of Monthly Report submission 1306-3355-1,related to an incident reported in July 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned Monthly Report. Please refer to the report from May Mobility for details.
13781-3529 v2Level 2Tesla, Inc.2022-08 10:15Mt. Laurel Township, NJ2022 Tesla Model 3ADASOther Fixed ObjectUnknown78Highway / FreewayRedacted by NHTSA as confidential business information
13781-3543 v2Level 2Tesla, Inc.2022-08 08:53Twentynine Palms, CA2022 Tesla Model 3ADASSUVUnknown57Rural RoadRedacted by NHTSA as confidential business information
13781-3544 v2Level 2Tesla, Inc.2022-08 10:29New Haven, CT2021 Tesla Model 3ADASHeavy TruckUnknown67Highway / FreewayRedacted by NHTSA as confidential business information
13781-3552 v2Level 2Tesla, Inc.2022-08 02:47Mobile, AL2020 Tesla Model 3ADASOther, see NarrativeUnknown33StreetRedacted by NHTSA as confidential business information
13781-3553 v2Level 2Tesla, Inc.2022-08 10:56Coconut Creek, FL2021 Tesla Model SADASOther Fixed ObjectUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-3554 v2Level 2Tesla, Inc.2022-08 23:01Alpharetta, GA2021 Tesla Model YADASUnknownUnknown50Highway / FreewayRedacted by NHTSA as confidential business information
13781-3555 v2Level 2Tesla, Inc.2022-08 01:13Wilton, CT2022 Tesla Model YADASUnknownUnknown34Rural RoadRedacted by NHTSA as confidential business information
13781-3565 v2Level 2Tesla, Inc.2022-08 22:15Dallas, TX2021 Tesla Model YADASVanUnknown58Highway / FreewayRedacted by NHTSA as confidential business information
13781-3620 v2Level 2Tesla, Inc.2022-08 15:02North Bethesda, MD2022 Tesla Model YADASUnknownUnknown85UnknownRedacted by NHTSA as confidential business information
13781-3621 v2Level 2Tesla, Inc.2022-08 21:56North Port, FL2021 Tesla Model YADASOther Fixed ObjectUnknown16Highway / FreewayRedacted by NHTSA as confidential business information
13781-3622 v2Level 2Tesla, Inc.2022-08 18:09Los Angeles, CA2020 Tesla Model 3ADASUnknownUnknown40Highway / FreewayRedacted by NHTSA as confidential business information
13781-3673 v2Level 2Tesla, Inc.2022-08 16:39Tracy, CA2021 Tesla Model YADASPassenger CarUnknown13Highway / FreewayRedacted by NHTSA as confidential business information
13781-3674 v2Level 2Tesla, Inc.2022-08 22:33St. Cloud, FL2022 Tesla Model SADASUnknownUnknown58UnknownRedacted by NHTSA as confidential business information
13781-3675 v2Level 2Tesla, Inc.2022-08 19:13Merrick, NY2020 Tesla Model 3ADASPassenger CarUnknown90Highway / FreewayRedacted by NHTSA as confidential business information
13781-3677 v2Level 2Tesla, Inc.2022-08 04:32Kissimmee, FL2022 Tesla Model 3ADASUnknownUnknown42UnknownRedacted by NHTSA as confidential business information
13781-3680 v2Level 2Tesla, Inc.2022-08 10:27Cary, NC2018 Tesla Model 3ADASPole / TreeUnknown29Highway / FreewayRedacted by NHTSA as confidential business information
13781-3686 v2Level 2Tesla, Inc.2022-08 17:46Palm Beach Gardens, FL2021 Tesla Model YADASUnknownUnknown44Highway / FreewayRedacted by NHTSA as confidential business information
13781-3687 v2Level 2Tesla, Inc.2022-08 21:43Wadsworth, IL2021 Tesla Model YADASPassenger CarUnknown77Highway / FreewayRedacted by NHTSA as confidential business information
13781-3700 v2Level 2Tesla, Inc.2022-08 02:46Miami, FL2021 Tesla Model YADASOther Fixed ObjectUnknown53Highway / FreewayRedacted by NHTSA as confidential business information
13781-3701 v2Level 2Tesla, Inc.2022-08 12:06Old Saybrook, CT2021 Tesla Model YADASOther Fixed ObjectUnknown35Highway / FreewayRedacted by NHTSA as confidential business information
13781-3702 v2Level 2Tesla, Inc.2022-08 18:56Brecksville, OH2021 Tesla Model YADASOther, see NarrativeUnknown9Highway / FreewayRedacted by NHTSA as confidential business information
13781-3707 v2Level 2Tesla, Inc.2022-08 21:53Austin, TX2018 Tesla Model 3ADASPassenger CarUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-3708 v2Level 2Tesla, Inc.2022-08 07:42Pasadena, CA2021 Tesla Model YADASUnknownUnknownUnknownRedacted by NHTSA as confidential business information
13781-3709 v2Level 2Tesla, Inc.2022-08 13:55Glendale, CA2021 Tesla Model YADASOther Fixed ObjectUnknown66Highway / FreewayRedacted by NHTSA as confidential business information
13781-3710 v2Level 2Tesla, Inc.2022-08 20:30Charleston, SC2020 Tesla Model 3ADASOther, see NarrativeFatality8Highway / FreewayRedacted by NHTSA as confidential business information
13781-3713 v2Level 2Tesla, Inc.2022-08 06:11Boca Raton, FL2020 Tesla Model 3ADASMotorcycleFatality97StreetRedacted by NHTSA as confidential business information
13781-3714 v2Level 2Tesla, Inc.2022-08 16:01Weston, FL2021 Tesla Model YADASOther Fixed ObjectUnknown21Highway / FreewayRedacted by NHTSA as confidential business information
13781-3715 v2Level 2Tesla, Inc.2022-08 18:33Whittier, FL2018 Tesla Model 3ADASOther Fixed ObjectUnknown39Highway / FreewayRedacted by NHTSA as confidential business information
13781-3716 v2Level 2Tesla, Inc.2022-08 19:09Orlovista, FL2020 Tesla Model YADASOther Fixed ObjectUnknown42Highway / FreewayRedacted by NHTSA as confidential business information
13781-3717 v2Level 2Tesla, Inc.2022-08 04:16Rochester Hills, MI2022 Tesla Model YADASUnknownUnknown43StreetRedacted by NHTSA as confidential business information
13781-3718 v2Level 2Tesla, Inc.2022-08 00:49Long Beach, CA2022 Tesla Model 3ADASSUVUnknown13Highway / FreewayRedacted by NHTSA as confidential business information
13781-3732 v2Level 2Tesla, Inc.2022-08 21:48Oak Forest, IL2022 Tesla Model SADASUnknownUnknown39StreetRedacted by NHTSA as confidential business information
13781-3734 v2Level 2Tesla, Inc.2022-08 20:24Atlanta, GA2021 Tesla Model YADASSUVUnknown13Highway / FreewayRedacted by NHTSA as confidential business information
13781-3935 v2Level 2Tesla, Inc.2022-08 12:15Pembroke Pines, FL2016 Tesla Model SADASUnknownUnknown76UnknownRedacted by NHTSA as confidential business information
13781-4305 v2Level 2Tesla, Inc.2022-08 11:55Sarasota, FL2020 Tesla Model SADASOther Fixed ObjectUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
30270-3545 v2ADSWaymo LLC2022-08 10:25Tempe, AZ2017 Chrysler PacificaADSOther Fixed ObjectNo Injuries Reported18Intersection
The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle…The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a road sign and crosswalk button post on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it passed [XXX]. As the Waymo AV was in the intersection of [XXX] and [XXX], and was approaching the right turn lane at the intersection of [XXX] and [XXX] and following the lane markings, the Waymo AV test driver transitioned the system to manual mode. The Waymo AV then made contact with the right curb on [XXX] as well as a road sign and a crosswalk button post located adjacent to the roadway. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Eastern time zone on the required date.
30270-3595 v2ADSWaymo LLC2022-08 03:09San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 03:09 AM PST a Waymo Autonomous Vehicle…The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 03:09 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving an SUV on [XXX] at [XXX] The Waymo AV was traveling eastbound on [XXX] in autonomous mode when it slowed for a stop sign on [XXX]. As the Waymo AV slowed to almost a complete stop, an SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Eastern time zone on the required date.
30270-3837ADSWaymo LLC2022-08 11:03Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported45Street
On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XX…On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] and had passed [XXX] when a passenger vehicle approached the Waymo AV from behind. The passenger vehicle then made a lane change into its adjacent right lane, and passed the Waymo AV. As it passed the Waymo AV, the passenger vehicle made a lane change back into the left adjacent lane, and its driver side rear quarter panel made contact with the Waymo AV's passenger side front quarter panel. 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.
30270-3838ADSWaymo LLC2022-08 12:23Chandler, AZ2017 Chrysler PacificaADSPickup TruckNo Injuries Reported0Parking Lot
On August [XXX], 2022 at 12:23 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving a pick-up truck at [XXX]. The Waymo AV stopped in a parking lot to drop-off a pas…On August [XXX], 2022 at 12:23 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving a pick-up truck at [XXX]. The Waymo AV stopped in a parking lot to drop-off a passenger. Shortly after the Waymo AV pulled over, a pick-up truck that was parked perpendicular to the Waymo AV moved backward and its rear bumper made contact with the passenger side rear quarter panel of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and the passenger had just unbuckled their seat belt to deboard. 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-3841ADSWaymo LLC2022-08 23:30Phoenix, AZ2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on […On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on [XXX] when a domestic dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog and the dog died at the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). 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-3842ADSWaymo LLC2022-08 17:05San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On August [XXX], 2022 at 5:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While approaching a merge onto southbound [XXX] f…On August [XXX], 2022 at 5:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While approaching a merge onto southbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the left. While the Waymo AV was stopped, an SUV approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-3843ADSWaymo LLC2022-08 18:08San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2022 at 6:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on[XXX] near [XXX]. The Waymo AV was stopped in traffic in…On August [XXX], 2022 at 6:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on[XXX] near [XXX]. The Waymo AV was stopped in traffic in the left-hand lane of [XXX], facing East. The passenger car that had been stopped behind the Waymo AV began moving forward. The front of the passenger car made contact with the rear of the Waymo AV. When the light turned green and traffic began moving, the passenger car left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained 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-3844ADSWaymo LLC2022-08 03:52San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported2Intersection
On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopp…On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopped at the stop sign at the intersection with [XXX]. As the Waymo AV slowed to a stop, a SUV traveling in the opposite lane, East on [XXX], crossed the intersection with [XXX] and came to a stop in the opposite lane, next to the Waymo AV. After stopping, the SUV began moving again and the front left corner of the SUV made contact with the left side of the Waymo AV. The SUV then left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained 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-3848ADSWaymo LLC2022-08 18:33Ennis, TX2021 Peterbilt 579 EpiqADSHeavy TruckNo Injuries Reported61Highway / Freeway
On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound…On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the middle lane on [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it began to execute a right lane change and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. 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-3851ADSWaymo LLC2022-08 00:06Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported10Street
On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when i…On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it approached a passenger vehicle stopped along the right shoulder in the bike lane. As the Waymo AV passed the passenger vehicle, one of the passenger vehicle's driver side doors opened and made contact with 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. 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-3852ADSWaymo LLC2022-08 18:15San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Intersection
On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came …On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came to a stop behind a double-parked vehicle in the right lane. Shortly after coming to a stop, a van approached from behind and made contact with the rear of the Waymo AV. The van then changed lanes and left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with Yadditional information as it may become available.
30290-3797ADSArgo AI2022-08 17:55Miami Beach, FL2020 Ford EscapeADSPickup TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30290-3800ADSArgo AI2022-08 12:31Miami, FL2020 Ford EscapeADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30310-3698ADSFirst Transit2022-08 16:23Rochester, MN2019 Ligier Group EZ10 Gen 3ADSSUVNo Injuries Reported0Intersection
Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in au…Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in autonomous mode. At 16:23 CT, the shuttle entered the intersection of [XXX] and [XXX]. The shuttle experienced an unknown e-stop. The vehicle behind the shuttle was following closely and attempting to pass the shuttle at this time and hit the rear left corner of the shuttle. No injuries reported to the two passengers on-board the shuttle or the operator or other vehicles two passengers. Seatbelts were used by the shuttle passengers at the time of the incident. 911 was called and the Minnesota Department of Public Safety was dispatched to file a report. Details of the event can be provided in video format, a police report and an operator summary. The GPX coordinates above are approximate at the time of the e-stop. The shuttle had experienced an unknown e-stop at 15:59 CT on [XXX] (no passengers).
30391-3678 v2ADSKodiak Robotics2022-08 18:00Palmer, TX2022 Kenworth Motor Truck Co T680ADSPickup TruckNo Injuries Reported15Highway / FreewayRedacted by NHTSA as confidential business information
30391-3808ADSKodiak Robotics2022-08 18:00Palmer, TX2022 Kenworth Motor Truck Co T680ADSPickup TruckNo Injuries Reported15Highway / FreewayRedacted by NHTSA as confidential business information
30412-3801ADSCruise LLC2022-08 07:04San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported14StreetRedacted by NHTSA as confidential business information
30412-3806ADSCruise LLC2022-08 03:53San Francisco, CA2020 Cruise AVADSPassenger CarMinor0StreetRedacted by NHTSA as confidential business information
30413-3764ADSMay Mobility2022-08 16:15Arlington, TX2020 LExus RX450HADSPickup TruckNo Injuries Reported10Intersection
May Mobility vehicle is traveling westbound in autonomous mode on [XXX], stopped at a red light. When the traffic light turns green, the subject vehicle accelerates up to approximately 10mph. Approximately halfway throug…May Mobility vehicle is traveling westbound in autonomous mode on [XXX], stopped at a red light. When the traffic light turns green, the subject vehicle accelerates up to approximately 10mph. Approximately halfway through the intersection of [XXX], the subject vehicle begins to slow down due to construction fencing that is intruding into the lane, eventually coming to a complete stop. The safety operator takes over manual operation via the accelerator pedal, but is struck from the rear by a Toyota pickup that was following. The Toyota was first struck by the Chevy vehicle traveling behind it, pushing the Toyota into the subject vehicle.
30414-3650 v2ADSEasymile Inc.2022-08 16:23Rochester, MN2019 Ligier EZ10 Gen 3ADSSUVNo Injuries Reported0Intersection1- Day Report done in Error, Please delete this report
30414-3903ADSEasymile Inc.2022-08 16:23Rochester, MN2019 Ligier EZ10 Gen 3ADSSUVNo Injuries Reported0Intersection
Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in a…Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in autonomous mode. At 16:23 CT, the shuttle entered the intersection of [XXX] and [XXX]. The shuttle experienced an unknown e-stop. The vehicle behind the shuttle was following closely and attempting to pass the shuttle at this time and hit the rear left corner of the shuttle. No injuries reported to the two passengers on-board the shuttle or the operator or other vehicles two passengers. Seatbelts were used by the shuttle passengers at the time of the incident. 911 was called and the Minnesota Department of Public Safety was dispatched to file a report. Details of the event can be provided in video format, a police report and an operator summary. The GPX coordinates above are approximate at the time of the e-stop. The shuttle had experienced an unknown e-stop at 15:59 CT on [XXX] (no passengers).
30531-3546 v2ADSTransdev Alternative Services2022-08 10:25Tempe, AZ2017 Chrysler PacificaADSOther Fixed ObjectNo Injuries Reported18Intersection
The content of this report in unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle …The content of this report in unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle in Tempe, Arizona was in a collision involving a road sign and crosswalk button post on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it passed [XXX]. As the Waymo AV was in the intersection of [XXX] and [XXX], and was approaching the right turn lane at the intersection of [XXX] and [XXX] and following the land markings, the Waymo AV test driver transitioned the system to manual mode. The Waymo AV then made contact with the right curb on[XXX] as well as a road sign and a crosswalk button post located adjacent to the roadway. At the time of the impact, the Waymo Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle was towed. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report ID 30270-345-1.
30531-3626 v2ADSTransdev Alternative Services2022-08 3:09San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
The content of this report is unchanged from the initial report submitted (30531-3626-1) On August [XXX] 2022 at 3:09 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision invol…The content of this report is unchanged from the initial report submitted (30531-3626-1) On August [XXX] 2022 at 3:09 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] in autonomous mode when it slowed for a stop sign on [XXX]. As the Waymo AV slowed to almost.a complete stop, an SUV 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report ID WaymoLLC-202208[XXX] (rev.202208[XXX]).
30531-3877ADSTransdev Alternative Services2022-08 11:03Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported45Street
On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle approached the Waymo AV from behind. The passenger vehicle then …On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle approached the Waymo AV from behind. The passenger vehicle then made a lane change into its adjacent right lane, and passed the Waymo AV. As it passed the Waymo AV, the passenger vehicle made a lane change back into the left adjacent lane, and its driver side rear quarter panel made contact with the Waymo AV's passenger side front quarter panel. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is identical to WaymoLLC-202208[XXX]-0 (rev.202209[XXX]143732).
30531-3879ADSTransdev Alternative Services2022-08 23:30Phoenix, AZ2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on […On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on [XXX] when a domestic dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog and the dog died at the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX-0 (rev.202209[XXX]162417).
30531-3880ADSTransdev Alternative Services2022-08 18:08San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2022 at 6:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped in traffic in…On August [XXX], 2022 at 6:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped in traffic in the left-hand lane of [XXX], facing East. The passenger car that had been stopped behind the Waymo AV began moving forward. The front of the passenger car made contact with the rear of the Waymo AV. When the light turned green and traffic began moving, the passenger car left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]205107).
30531-3881ADSTransdev Alternative Services2022-08 3:52San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported2Intersection
On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopp…On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopped at the stop sign at the intersection with [XXX]. As the Waymo AV slowed to a stop, a SUV traveling in the opposite lane, East on [XXX], crossed the intersection with [XXX] and came to a stop in the opposite lane, next to the Waymo AV. After stopping, the SUV began moving again and the front left corner of the SUV made contact with the left side of the Waymo AV. The SUV then left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]162446).
30531-3882ADSTransdev Alternative Services2022-08 18:33Ennis, TX2021 Peterbilt 579 EpiqADSHeavy TruckNo Injuries Reported61Highway / Freeway
On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound…On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the middle lane on [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it began to execute a right lane change and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev. 2022019[XXX]185808)
30531-3883ADSTransdev Alternative Services2022-08 00:06Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported10Street
On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it…On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it approached a passenger vehicle stopped along the right shoulder in the bike lane. As the Waymo AV passed the passenger vehicle, one of the passenger vehicle's driver side doors opened and made contact with 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 with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]205246).
30531-3884ADSTransdev Alternative Services2022-08 18:15San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Intersection
On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came …On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came to a stop behind a double-parked vehicle in the right lane. Shortly after coming to a stop, a van approached from behind and made contact with the rear of the Waymo AV. The van then changed lanes and left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]162510).
30610-3703 v3ADSZoox, Inc.2022-08 17:21Menlo Park, CA2019 Toyota HighlanderADSPassenger CarMinor2Street
A Zoox vehicle in autonomy had made a right turn from [XXX] onto [XXX] in Menlo Park, CA and was preparing to make an immediate, unprotected left turn onto [XXX]. The Zoox vehicle was slowing and moving at approximately …A Zoox vehicle in autonomy had made a right turn from [XXX] onto [XXX] in Menlo Park, CA and was preparing to make an immediate, unprotected left turn onto [XXX]. The Zoox vehicle was slowing and moving at approximately 2 mph with its brake lamps and left turn indicator illuminated, yielding to an oncoming vehicle with the right of way. A following vehicle - traveling at approximately 24 mph - then struck the Zoox vehicle's right rear bumper, and that vehicle's driver airbag appeared to have deployed on impact. The Zoox operator disengaged autonomy, proceeded with the left turn, and pulled over. The following vehicle continued its path of travel, veered out of the lane, and collided with a tree on the left side of the road. The Menlo Park Police Department was called to the scene. Two Zoox operators sustained minor injuries and it is unknown if the driver of the other vehicle sustained injuries. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
30610-3719 v2ADSZoox, Inc.2022-08 21:20Las Vegas, CA2016 Toyota HighlanderADSNon-Motorist: PedestrianNo Injuries Reported2Parking Lot
A Zoox vehicle in autonomy was proceeding at approximately 2mph towards an exit of a private hotel driveway in Las Vegas, Nevada when it was struck on its right front fender by two individuals involved in an altercation …A Zoox vehicle in autonomy was proceeding at approximately 2mph towards an exit of a private hotel driveway in Las Vegas, Nevada when it was struck on its right front fender by two individuals involved in an altercation who had darted out from the side of the roadway. The right front fender of the Zoox vehicle was dented. The two individuals fled the scene and Zoox is not aware of any reported injuries. We question whether this interaction meets the reporting requirements nevertheless, we are submitting this report out of an abundance of caution. This 10-Day update provides complete information for this incident.
30610-3751ADSZoox, Inc.2022-08 21:01San Francisco, CA2016 Toyota HighlanderADSVanNo Injuries Reported0Street
A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA, in stop-and-go traffic. The Zoox vehicle came to a stop for a vehicle ahead when a following van made light contact with the Zoox vehicle'…A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA, in stop-and-go traffic. The Zoox vehicle came to a stop for a vehicle ahead when a following van made light contact with the Zoox vehicle's rear bumper from behind. There were no injuries and the police were not called.

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.