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
1674 reports, showing 1301 to 1400.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 540-5261 | ADS | General Motors, LLC | 2023-03 04:23 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-5229-1) | |
| 540-5262 | ADS | General Motors, LLC | 2023-03 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-5240-1) | |
| 540-5263 | ADS | General Motors, LLC | 2023-03 21:49 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-5241-1) | |
| 540-5264 | ADS | General Motors, LLC | 2023-03 03:20 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 12 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-5242-1) | |
| 540-5265 | ADS | General Motors, LLC | 2023-03 23:30 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-5243-1) | |
| 988-5310 | ADS | PACCAR Incorporated | 2023-03 8:01 | Weatherford, TX | 2022 Peterbilt 579 | Unknown, see Narrative | Passenger Car | No Injuries Reported | 65 | Highway / Freeway | At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicl…At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicle encroaching on the lane. This vehicle continued to veer toward Aurora's truck at over 65 miles per hour, causing a collision. Aurora disengaged autonomy before impact and pulled to the shoulder along with the involved vehicle. Both vehicles were able to be driven from the scene, and there were no reported injuries. | |
| 30270-4906 v2 | ADS | Waymo LLC | 2023-02 13:08 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 13 | Highway / Freeway | Other than removing the time zone from the narrative below and correcting the total number of lanes on the highway, the content of this report is unchanged from the initial report submitted on February 19, 2023 [REDACTED…Other than removing the time zone from the narrative below and correcting the total number of lanes on the highway, the content of this report is unchanged from the initial report submitted on February 19, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2023 at 1:08 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, AZ was in a collision involving a Passenger Car on [XXX] near [XXX] ([XXX]). The Waymo AV was traveling in the second lane from the right (lane 5 out of 6 lanes) in the eastbound direction of [XXX] when it started to decelerate in response to slow traffic ahead in the AVs lane. A passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. The other vehicle left the scene without exchanging information. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5081 | ADS | Waymo LLC | 2023-02 05:44 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 12 | Intersection | On February [XXX], 2023 at 5:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving road debris on [XXX] at [XXX]. The Waymo AV was proceeding East on [XXX] …On February [XXX], 2023 at 5:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving road debris on [XXX] at [XXX]. The Waymo AV was proceeding East on [XXX] through the intersection with [XXX] when the front of the Waymo AV made contact with cardboard debris. At the time of the impact, the Waymo AV's 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-5082 | ADS | Waymo LLC | 2023-02 17:27 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 40 | Street | On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the rightmost…On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the rightmost lane. As the Waymo AV approached the intersection of [XXX], traffic in the two lanes to the left of the Waymo AV was backed up and moving slowly or stopped. A SUV attempted to merge from the leftmost lane across a gap in traffic in the center lane and into the rightmost lane. While attempting to enter the Waymo AV's lane, the front right of the SUV made contact with the rear left 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. 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-5083 | ADS | Waymo LLC | 2023-02 00:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 14 | Intersection | On February [XXX], 2023 at 12:15 AM 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 southw…On February [XXX], 2023 at 12:15 AM 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 southwest on [XXX] in autonomous mode. While the Waymo AV was making a left turn onto [XXX], a passenger vehicle proceeded into the intersection from the left and made contact with the left side of the Waymo AV. The other vehicle immediately left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5085 v2 | ADS | Waymo LLC | 2023-02 07:23 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | On February [XXX], 2023 at 7:23 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was proceeding East on [XX…On February [XXX], 2023 at 7:23 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was proceeding East on [XXX] near the intersection with [XXX] when it came to a stop to yield to a heavy truck traveling West on [XXX]. As the heavy truck moved past the Waymo AV, the front left tire of the heavy truck made contact with the rear left sensor of the Waymo AV. The heavy truck then left the scene. At the time of the impact, the Waymo AV's 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 is submitting this correction to the GENERAL DAMAGE / CONTACT AREA for the Heavy Truck from Report 30270-5085-1 which was submitted earlier today. | |
| 30391-4811 v2 | ADS | Kodiak Robotics | 2023-02 10:15 | Waxahachie, TX | 2023 Kenworth Motor Truck Co T680 | ADS | SUV | No Injuries Reported | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30391-5009 | ADS | Kodiak Robotics | 2023-02 10:15 | Waxahachie, TX | 2023 Kenworth Motor Truck Co T680 | ADS | SUV | No Injuries Reported | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30410-5003 | ADS | Motional | 2023-02 14:18 | Las Vegas, NV | 2021 Hyundai Ioniq 5 | ADAS | Passenger Car | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information | |
| 30412-4829 v2 | ADS | Cruise LLC | 2023-02 00:39 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 7 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5035 | ADS | Cruise LLC | 2023-02 02:05 | San Francisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5036 | ADS | Cruise LLC | 2023-02 00:29 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 24 | Street | Redacted by NHTSA as confidential business information | |
| 30531-4907 v2 | ADS | Transdev Alternative Services | 2023-02 13:08 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 13 | Highway / Freeway | On February [XXX], 2023 at 1:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, AZ was in a collision involving a Passenger Car on [XXX] near [XXX] ([XXX]). The Waymo AV was traveling in the second lan…On February [XXX], 2023 at 1:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, AZ was in a collision involving a Passenger Car on [XXX] near [XXX] ([XXX]). The Waymo AV was traveling in the second lane from the right (lane 5 out of 6 lanes) in the eastbound direction of [XXX] when it started to decelerate in response to slow traffic ahead in the AV's lane. A passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. The other vehicle left the scene without exchanging information. 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: 30270-4906-1 | |
| 30531-5088 | ADS | Transdev Alternative Services | 2023-02 17:27 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 40 | Street | On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the right most…On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the right most lane. As the Waymo AV approached the intersection of [XXX], traffic in the two lanes to the left of the Waymo AV was backed up and slow or stopped. A SUV attempted to merge from the leftmost lane across a gap in traffic in the center lane and into the rightmost lane. While attempting to enter the Waymo AV's lane, the front right of the SUV made contact with the rear left of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request no. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. | |
| 30610-4993 v2 | ADS | Zoox, Inc. | 2023-02 14:28 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 7 | Intersection | A Zoox vehicle in autonomous mode was making a right turn to travel southwest onto [XXX] from [XXX] from lane 1 when Vehicle 2 crossed from lane 3 into the Zoox vehicle's lane and made contact with the Zoox vehicle's fro…A Zoox vehicle in autonomous mode was making a right turn to travel southwest onto [XXX] from [XXX] from lane 1 when Vehicle 2 crossed from lane 3 into the Zoox vehicle's lane and made contact with the Zoox vehicle's front sensors before making the right turn. Vehicle 2 did not stop before leaving the scene. No information was exchanged. There were no injuries and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. | |
| 30610-4994 v2 | ADS | Zoox, Inc. | 2023-02 13:27 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Street | A Zoox vehicle in autonomy was stopped with brake lights illuminated in traffic southbound on [XXX] towards [XXX]. When traffic ahead began to move the Zoox vehicle was appropriately following the car ahead at low speed …A Zoox vehicle in autonomy was stopped with brake lights illuminated in traffic southbound on [XXX] towards [XXX]. When traffic ahead began to move the Zoox vehicle was appropriately following the car ahead at low speed when it was rear ended by Vehicle #2 at low speed. The other party did not stop to exchange information and left the scene. There were no injuries and police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. | |
| 30610-4995 v2 | ADS | Zoox, Inc. | 2023-02 18:06 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Street | A Zoox vehicle in autonomous mode was slowing to a stop with brake lights illuminated behind traffic on northbound [XXX] near [XXX] when a vehicle behind made contact at approximately 10mph. There were no injuries and po…A Zoox vehicle in autonomous mode was slowing to a stop with brake lights illuminated behind traffic on northbound [XXX] near [XXX] when a vehicle behind made contact at approximately 10mph. There were no injuries and police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. | |
| 540-4832 v2 | ADS | General Motors, LLC | 2023-02 00:39 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 7 | Intersection | On February 17, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day 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 February 17, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day 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-4829-2) | |
| 540-5060 | ADS | General Motors, LLC | 2023-02 02:05 | San Fancisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On March 14, 2023 GM Cruise Holdings LLC ("Cruise") filed 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-oper…On March 14, 2023 GM Cruise Holdings LLC ("Cruise") filed 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-5035-1) | |
| 540-5061 | ADS | General Motors, LLC | 2023-02 00:29 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 24 | Street | On March 14, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-ope…On March 14, 2023, GM Cruise Holdings LLC ("Cruise") filed 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-5036-1) | |
| 855-5055 | ADS | Mercedes-Benz USA, LLC | 2023-02 08:25 | Downey, CA | 2021 Mercedes-Benz S580 | ADS | Heavy Truck | No Injuries Reported | Highway / Freeway | Mercedes-Benz has conducted a review of the incident and the following is based on that review. The subject Mercedes-Benz Drive Pilot test vehicle was traveling between 15-20 mph in the #2 northbound lane on the [XXX] in…Mercedes-Benz has conducted a review of the incident and the following is based on that review. The subject Mercedes-Benz Drive Pilot test vehicle was traveling between 15-20 mph in the #2 northbound lane on the [XXX] in California in stop and go traffic with the L3 ADS activated by the driver. The vehicle's ADS determined that a truck traveling in the adjacent lane had a trajectory towards the Drive Pilot's lane, and so the Mercedes-Benz test vehicle autonomously applied the brakes to avoid a collision. After applying the brakes and bringing itself to a standstill, the Mercedes-Benz was then struck in the rear bumper by a trailing semi-truck that did not stop in time. No injuries were reported, no airbags deployed in either vehicle, and both vehicles were able to be driven from the scene of the incident. The Mercedes-Benz vehicle experienced minor damage to the rear bumper, and no damage was observed on the semi-truck at the scene. The CA Traffic Collision Report for the subject incident noted a violation of California Vehicle Code 22350 (unsafe speed for traffic conditions) by the semi-truck in the #2 lane that struck the rear bumper of the Mercedes-Benz. | ||
| 855-5058 | ADS | Mercedes-Benz USA, LLC | 2023-02 15:10 | Gardena, CA | 2022 Mercedes-Benz S580 | Unknown, see Narrative | SUV | No Injuries Reported | Highway / Freeway | The subject Mercedes-Benz vehicle was driving in stop and go traffic on the [XXX] in Gardena, California with the L3 ADS activated. The test route selected by the driver in the vehicle's navigation system indicated an up…The subject Mercedes-Benz vehicle was driving in stop and go traffic on the [XXX] in Gardena, California with the L3 ADS activated. The test route selected by the driver in the vehicle's navigation system indicated an upcoming exit, so the driver began to prepare for a lane change towards the highway exit by deactivating the L3 ADS and activating the turn signal. Once the vehicle was in conventional driving mode, the driver looked for a gap in the adjacent lane to merge towards the exit lane, applied the brakes, and slowed the vehicle down. The SUV following the Mercedes-Benz vehicle did not respond in time to the vehicle's braking and contacted the rear of the Mercedes-Benz approximately 10 seconds after the L3 ADS was deactivated. The Mercedes-Benz vehicle experienced minor damage to the rear bumper. No injuries were reported, no airbags deployed in either vehicle, and both vehicles were driven from the scene of the incident. | ||
| 988-4816 | ADS | PACCAR Incorporated | 2023-02 10:15 | Waxahachie, TX | 2023 Kenworth Motor Truck Co T680 | ADS | SUV | No Injuries Reported | 56 | Highway / Freeway | A police report was issued after the 1-Day SGO incident report was submitted. It determined the driver of the crossover SUV to be at fault and noted that the crossover SUV's driver advised officers that he fell asleep wh…A police report was issued after the 1-Day SGO incident report was submitted. It determined the driver of the crossover SUV to be at fault and noted that the crossover SUV's driver advised officers that he fell asleep while driving and caused the accident. The content of this incident report is otherwise unchanged from the initial incident report submitted on February 7, 2023. On February 7, 2023, Kodiak Robotics, Inc. ("Kodiak") filed an Incident Report (the "Report") under the Standing General Order 2021-01 (the "Order"). PACCAR, Inc. (Paccar) manufactured the Kodiak-operated motor vehicle involved in the incident summarized in the Incident Report. Because Paccar is also a Reporting Entity under the Order, Paccar is submitting a duplicate of the redacted public copy of the Report. Paccar has selected "Unknown" in the "ADS version" field solely to avoid a second submission of nonpublic Kodiak CBI. Paccar is in possession of Kodiak's response to this field and incorporates Kodiak's response into this submission by reference. Paccar's submission is based on facts supplied to Paccar by Kodiak. Paccar 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. | |
| 30270-4768 v2 | ADS | Waymo LLC | 2023-01 13:38 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Motorcycle | No Injuries Reported | 8 | Intersection | 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-4880 | ADS | Waymo LLC | 2023-01 17:36 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | First Responder Vehicle | No Injuries Reported | 0 | Parking 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-4881 | ADS | Waymo LLC | 2023-01 17:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 34 | Intersection | 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-4882 | ADS | Waymo LLC | 2023-01 13:53 | Chandler, AZ | 2017 Chrysler Pacifica | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | 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-7598 | ADS | Waymo LLC | 2023-01 17:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 34 | Intersection | 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-4799 | ADS | Motional | 2023-01 13:17 | Las Vegas, NV | 2021 Hyundai Ioniq 5 | ADS | Passenger Car | No Injuries Reported | 18 | Street | Redacted by NHTSA as confidential business information | |
| 30531-4883 | ADS | Transdev Alternative Services | 2023-01 17:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 34 | Intersection | 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 v2 | ADS | Zoox, Inc. | 2023-01 15:00 | Las Vegas, NV | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 24 | Street | 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-4815 | ADS | Zoox, Inc. | 2023-01 18:40 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 3 | Street | 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-4793 | ADS | Robotic Research | 2023-01 11:01 | Peachtree Corners, GA | 2018 Local Motors 2.0 | ADS | Other Fixed Object | No Injuries Reported | 9 | Street | 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. | |
| 1306-4390 v2 | ADS | Toyota Motor Engineering & Manufacturing | 2022-12 09:02 | Sun City, AZ | 2021 Toyota Sienna | ADS | Motorcycle | No Injuries Reported | 0 | Street | 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. | |
| 30270-4363 v2 | ADS | Waymo LLC | 2022-12 21:05 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 11 | Parking Lot | Other than the updated Speed Limit field, the content of this report is unchanged from the initial report submitted on December 5, 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On December [XXX], 2022 …Other than the updated Speed Limit field, the content of this report is unchanged from the initial report submitted on December 5, 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On December [XXX], 2022 at 9:05 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a fixed object in a parking lot on the 4100 block of [XXX]. The Waymo AV was traveling southbound in a parking lot on [XXX] when it approached a parking lot barrier arm. The Waymo AV initially slowed for the arm but then proceeded forward, making contact with it and opening it. 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-4505 v2 | ADS | Waymo LLC | 2022-12 13:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | Other than updating the Were All Passengers Belted? field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report submitted on December 18, 2022 [REDACTED, MAY CONTAIN …Other than updating the Were All Passengers Belted? field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report submitted on December 18, 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On December [XXX], 2022 at 1:50 PM PST, a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger car on [XXX] near the intersection with [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it slowed and stopped for a parallel parking vehicle ahead. A passenger car following the Waymo AV did not stop in time and made contact with the rear of the Waymo AV at a speed of about 7 MPH. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode with a test driver present (in the driver's 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 Pacific time zone on the required date. | |
| 30270-4706 | ADS | Waymo LLC | 2022-12 16:54 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing east on [XXX] beh…On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing east on [XXX] behind stopped traffic in the left-most through lane in autonomous mode. An SUV approached from behind and attempted to change lanes into the left turn lane, making contact with the left 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). 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-4707 | ADS | Waymo LLC | 2022-12 12:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On December [XXX], 2022 at 12:35 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 stopped facing sou…On December [XXX], 2022 at 12:35 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 stopped facing south on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo 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-4708 | ADS | Waymo LLC | 2022-12 5:18 | Sacaton, AZ | 2021 Peterbilt 579 Epiq | ADS | Other, see Narrative | No Injuries Reported | 51 | Highway / Freeway | On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer operating in Sacaton, Arizona was in a collision involving a Class 8 semi-truck and flat-bed trailer o…On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer operating in Sacaton, Arizona was in a collision involving a Class 8 semi-truck and flat-bed trailer on [XXX], near mile marker [XXX]. The Waymo AV was traveling straight in autonomous mode in the leftmost lane, when the test driver took manual control and attempted a right lane change. As the test driver prepared to make the lane change, there was a Class 8 semi-truck and flat-bed trailer passing in the adjacent right lane. As the Waymo AV test driver initiated the lane change, the Waymo AV made contact with the rear corner of the flat-bed 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 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-4710 | ADS | Waymo LLC | 2022-12 03:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped facing nor…On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped facing north on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and stopped behind the Waymo AV before eventually proceeding forward and making contact with the rear of the Waymo AV while the AV was still stopped at the red light. 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 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. | |
| 30412-4511 v2 | ADS | Cruise LLC | 2022-12 23:23 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-4640 | ADS | Cruise LLC | 2022-12 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information | |
| 30412-4642 | ADS | Cruise LLC | 2022-12 23:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 19 | Street | Redacted by NHTSA as confidential business information | |
| 30413-4352 | ADS | May Mobility | 2022-12 18:38 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | SUV | No Injuries Reported | 0 | Street | Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle…Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle. No injuries were reported by the operator or the driver of the other vehicle and there was no damage to the SUV and a small crack in the bumper for the subject vehicle. | |
| 30413-4378 | ADS | May Mobility | 2022-12 09:02 | Sun City, AZ | 2021 Toyota Sienna | ADS | Motorcycle | No Injuries Reported | 0 | Street | Subject vehicle left the [XXX] headed southwest on [XXX]. Following the [XXX] intersection a motorcycle started following us closely. The subject vehicle came to a stop and the motorcyclist attempted to brake in time, bu…Subject vehicle left the [XXX] headed southwest on [XXX]. Following the [XXX] intersection a motorcycle started following us closely. The subject vehicle came to a stop and the motorcyclist attempted to brake in time, but hit the motorcycle's left mirror/handlebar against the rear passenger-side of the subject vehicle's bumper. | |
| 30490-4473 | ADS | Beep, Inc. | 2022-12 17:53 | Port Saint Lucie, FL | 2018 Navya ARMA | Unknown, see Narrative | Passenger Car | No Injuries Reported | 1 | Street | On December [XXX], 2022, a Navya ARMA shuttle operated by Beep (VIN 1N9A1SACXJS[XXX]) was involved in a non-injury collision while operating in manual mode on [XXX] in Port Saint Lucie, FL. While driving along [XXX] und…On December [XXX], 2022, a Navya ARMA shuttle operated by Beep (VIN 1N9A1SACXJS[XXX]) was involved in a non-injury collision while operating in manual mode on [XXX] in Port Saint Lucie, FL. While driving along [XXX] under autonomous control, the shuttle encountered a parked vehicle partially blocking its path, requiring disengagement of the autonomous drive system. The safety driver attempted to manually drive the shuttle around the parked vehicle to reengage the autonomous drive system. While manually steering the shuttle around the parked vehicle blocking its path, the shuttle failed to respond to manual control input and steered to the left, impacting a parked vehicle at a low rate of speed on the opposite side of [XXX]. The six passengers onboard alighted the shuttle, an accident report was filed with the local police, and the shuttle was removed from the scene. Initial reports from the onboard safety driver indicated that while steering around the vehicle blocking the shuttle's path, the shuttle became unresponsive to control input. The safety driver released the operator present button on the vehicle controller, which serves as dead man switch however, the vehicle failed to stop. After the incident, further investigation by Navya confirmed that the root cause of the incident was a failure of the Xbox 360 controller used to manually control the vehicle. Contact with the parked vehicle occurred between the time of failure and the vehicle drive system recognizing that the controller had failed an elapsed time of 4.05 seconds. In response to the incident, Beep suspended operation of all Navya ARMA vehicles pending identification and implementation of appropriate solutions to mitigate the risk of this failure leading to future incidents. Subsequent investigation by Beep and Navya determined that the vehicle control software, NavyaDrive, is limited in its ability to monitor the validity of control signal input received from the Xbox 360 controller. As the safety driver began to manually steer the vehicle, the controller failed, sending constant turning input to the vehicle drive system leading to the collision. Though Navya developed software mitigations due to prior issues encountered with the controller, those mitigations were ineffective with respect to the failure leading to the incident on December [XXX]. Further, due to the short time between the controller failing and the collision (2.34sec), the safety driver was unable to identify the controller failure and trigger the emergency stop before the collision occurred. In response to the incident, Navya is integrating a revised manual control system on the ARMA shuttle platform. The revised manual control system utilizes industrial-grade components for improved electromechanical reliability and allows for active monitoring of the control system health, eliminating the root cause of the failure that led to the incident on December [XXX]. Software upgrades of all Navya ARMA vehicles will further reintroduce automated braking function while the ARMA vehicle is under manual control. Beep is working with Navya to retrofit its fleet of ARMA vehicles with the revised manual control system as well as retrain and recertify its safety driver staff on the updated NavyaDrive software. Discussion of the root cause analysis and solution design for the revised manual control system will be provided to NHTSA as a supplement to this report. | |
| 30531-4506 v2 | ADS | Transdev Alternative Services | 2022-12 13:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | Other than updating the "Were All Passengers Belted?" field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report. On December [XXX], 2022 at 1:50 PM PST, a Waymo A…Other than updating the "Were All Passengers Belted?" field, which was initially submitted incorrectly, the content of this report is unchanged from the initial report. On December [XXX], 2022 at 1:50 PM PST, a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving a passenger car on [XXX] near the intersection with [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it slowed and stopped for a parallel parking vehicle ahead. A passenger car following the Waymo AV did not stop in time and made contact with the rear of the Waymo AV at a speed of about 7 MPH. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode with a test driver 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 WaymoLLC-20221217-0 (rev.20221217234005). | |
| 30531-4719 v4 | ADS | Transdev Alternative Services | 2022-12 16:54 | San Francisco, CA | 2021 Jaguar I- Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers latitude and longitud. On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle ("Waymo AV") o…Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers latitude and longitud. On December [XXX], 2022 at 4:54 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX].The Waymo AV was stopped facing east on [XXX] behind stopped traffic in the left-most through lane in autonomous mode. An SUV approached from behind and attempted to change lanes into the left turn lane, making contact with the left 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). 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-20221212-0 (rev.20230117152426). | |
| 30531-4720 v2 | ADS | Transdev Alternative Services | 2022-12 12:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 12:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV'') operating in San Franc…Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 12:35 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 stopped facing south on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo 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 Waymo LLC WaymoLLC- 20221213-0 (rev.20230117152233). | |
| 30531-4721 v3 | ADS | Transdev Alternative Services | 2022-12 05:18 | Sacaton, AZ | 2021 Peterbilt 579 Epiq | ADS | Heavy Truck | No Injuries Reported | 51 | Highway / Freeway | Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle ("Waymo AV) Peterbilt Class 8 semi-t…Updated: LATITUDE should read: [XXX] and LONGITUDE should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 5:18 AM PST a Waymo Autonomous Vehicle ("Waymo AV) Peterbilt Class 8 semi-truck and trailer operating in Sacaton, Arizona was in a collision involving a Class 8 semi-truck and flat-bed trailer on [XXX], near mile marker [XXX]. The Waymo AV was traveling straight in autonomous mode in the leftmost lane, when the test driver took manual control and attempted a right lane change. As the test driver prepared to make the lane change, there was a Class 8 semi-truck and flat-bed trailer passing in the adjacent right lane. As the Waymo AV test driver initiated the lane change, the Waymo AV made contact with the rear corner of the flat-bed 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 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-20221216-0 (rev.20230117160244). | |
| 30531-4726 v2 | ADS | Transdev Alternative Services | 2022-12 03:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francis…Update: Latitude should read: [XXX] and longitude should read: [XXX]. Previous updates did not save correct numbers. On December [XXX], 2022 at 3:15 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX].The Waymo AV was stopped facing north on [XXX] for a red light in the right lane of the three-lane street while in autonomous mode. A passenger vehicle approached from behind and stopped behind the Waymo AV before eventually proceeding forward and making contact with the rear of the Waymo AV while the AV was still stopped at the red light. 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 drivers seating position). The Waymo 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-20221229-0 (rev.20230117153132). | |
| 30792-4714 | ADS | WeRide Corp | 2022-12 16:31 | Las Vegas, NV | 2023 Nissan Leaf SV Plus | ADS | SUV | No Injuries Reported | 0 | Intersection | At 4:31pm on 12/[XXX]/2023 a Weride safety officer operating a Weride L4 autonomous vehicle (car 1) was in autonomous mode traveling South Bound [XXX] and was stopped at the right turn lane for a red traffic light towar…At 4:31pm on 12/[XXX]/2023 a Weride safety officer operating a Weride L4 autonomous vehicle (car 1) was in autonomous mode traveling South Bound [XXX] and was stopped at the right turn lane for a red traffic light towards [XXX]. While the light was still red, our vehicle slowly moved forward and then yielded for incoming cross traffic. While yielding, the rear vehicle (car 2) behind us accelerated and collided with our vehicle (car 1). The safety driver then disengaged the vehicle as a precautionary measure (car 1) and moved over to examine the minor rear-end collision situation and exchange information with car 2 driver. Since the damage to weride car was minimal, it was driven back in manual mode. | |
| 540-4524 v2 | ADS | General Motors, LLC | 2022-12 23:23 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On December 28, 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day 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…On December 28, 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day 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-4511-2) | |
| 540-4670 | ADS | General Motors, LLC | 2022-12 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed 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-op…On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed 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-4640-1) | |
| 540-4671 | ADS | General Motors, LLC | 2022-12 23:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 19 | Street | On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed 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-op…On January 13, 2023 GM Cruise Holdings LLC ("Cruise") filed 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-4642-1) | |
| 1306-4389 v2 | ADS | Toyota Motor Engineering & Manufacturing | 2022-11 15:43 | Ann Arbor, MI | 2020 Lexus RX450H | Unknown, see Narrative | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | This report is being submitted because May Mobility notified Toyota on Dec. 9, 2022 of 1-Day Report submission 30413-4170-1,related to an incident that occurred on Nov. [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-4170-1,related to an incident that occurred on Nov. [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-4389-1. | |
| 30270-4482 | ADS | Waymo LLC | 2022-11 16:30 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 2 | Street | On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SUV near [XXX]. While reversing in manual on a narrow road, the fr…On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SUV near [XXX]. While reversing in manual on a narrow road, the front right radar of the Waymo AV made contact with the taillight of a parked SUV. 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. 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-4484 | ADS | Waymo LLC | 2022-11 08:48 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On November [XXX], 2022 at 8:48 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a garbage truck on the 500 block of [XXX]. The Waymo AV was traveling eastbound on […On November [XXX], 2022 at 8:48 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a garbage truck on the 500 block of [XXX]. The Waymo AV was traveling eastbound on [XXX] when it encountered a stopped garbage truck traveling westbound. The Waymo AV pulled to the right side of the street and stopped, unable to proceed past the garbage truck and an SUV parked parallel to the curb. The garbage truck then attempted to pass between the Waymo AV and a parked passenger vehicle to the right of the garbage truck, and the garbage truck made contact with the left rear corner of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode and the Waymo AV was stationary. 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-4485 | ADS | Waymo LLC | 2022-11 09:34 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On November [XXX], 2022 at 9:34 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 stopped in traffic on n…On November [XXX], 2022 at 9:34 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 stopped in traffic on northbound [XXX] in autonomous mode. A passenger car that had been stopped behind the Waymo AV passed on the left side, crossing the double yellow line and making contact with the Waymo AVs rear left sensor housing. The passenger car immediately left the scene. 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. | |
| 30413-4170 | ADS | May Mobility | 2022-11 15:43 | Ann Arbor, MI | 2020 Lexus RX450H | Unknown, see Narrative | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have …Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have come to a full stop before the stop line and remained stopped until the operator took over. 6 seconds prior to incident, operator took the vehicle over manually before it could have stopped in autonomy. Operator moved the vehicle manually passed the stop line, colliding with a bicyclist's back tire. No injuries reported from the bicyclist or the operator and no damage to the vehicle or bicycle. | |
| 30531-4492 v2 | ADS | Transdev Alternative Services | 2022-11 16:30 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 2 | Street | Corrected the latitude and longitude. Nothing else was updated. On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SU…Corrected the latitude and longitude. Nothing else was updated. On November [XXX], 2022 at 4:30 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a parked SUV near [XXX]. While reversing in manual on a narrow road, the front right radar of the Waymo AV made contact with the taillight of a parked SUV. 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. 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-20221103-0 (rev.20221215142403). | |
| 30531-4494 | ADS | Transdev Alternative Services | 2022-11 9:34 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On November [XXX], 2022 at 9:34 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 stopped in traffic on n…On November [XXX], 2022 at 9:34 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 stopped in traffic on northbound [XXX] in autonomous mode. A passenger car that had been stopped behind the Waymo AV passed on the left side, crossing the double yellow line and making contact with the Waymo AVs rear left sensor housing. The passenger car immediately left the scene. 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. 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 report WaymoLLC-20221108-0 (rev.20221215145119). | |
| 30571-4399 v2 | ADS | NVIDIA CORP | 2022-11 17:20 | San Jose, CA | 2021 Mercedes-Benz S450 | ADS | Pickup Truck | No Injuries Reported | 19 | Highway / Freeway | The Mercedes-Benz vehicle was traveling northbound on [XXX] in lane one, near [XXX], with the vehicles L3 ADS system engaged. Traffic ahead began slowing, and the operator attempted a right lane change into lane two. The…The Mercedes-Benz vehicle was traveling northbound on [XXX] in lane one, near [XXX], with the vehicles L3 ADS system engaged. Traffic ahead began slowing, and the operator attempted a right lane change into lane two. The Mercedes-Benz vehicle operator was unable to complete the lane change and instead applied the brakes. The Mercedes-Benz operator was unable to avoid contact with the Ford vehicle that was in front of it, and the Mercedes-Benz front bumper contacted the rear bumper of the Ford vehicle. | |
| 30610-4362 | ADS | Zoox, Inc. | 2022-11 22:18 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | A Zoox vehicle in autonomy was fully stopped with brake lights illuminated in the left turn lane at a red traffic light waiting to complete a left hand turn from [XXX] onto [XXX] in San Francisco, Ca. As the light turned…A Zoox vehicle in autonomy was fully stopped with brake lights illuminated in the left turn lane at a red traffic light waiting to complete a left hand turn from [XXX] onto [XXX] in San Francisco, Ca. As the light turned green, the Zoox vehicle appropriately yielded to oncoming traffic when Vehicle 2 attempted to make a lane change to the right and struck the rear of the Zoox vehicle. The Zoox vehicle incurred minor damage to the rear sensors and bumper. There were no injuries and police were not called. | |
| 30610-4383 | ADS | Zoox, Inc. | 2022-11 13:24 | San Francisco, CA | 2016 Toyota Highlander | ADS | Van | No Injuries Reported | 0 | Street | A Zoox vehicle in autonomy was stopped at a red light waiting for traffic ahead on [XXX] with brake lights illuminated. When the traffic light changed to green, surrounding traffic began to move. The Zoox vehicle appropr…A Zoox vehicle in autonomy was stopped at a red light waiting for traffic ahead on [XXX] with brake lights illuminated. When the traffic light changed to green, surrounding traffic began to move. The Zoox vehicle appropriately continued to wait for a stopped lead vehicle immediately ahead when vehicle 2 struck the Zoox vehicle from the rear. Zoox vehicle camera footage shows the driver of vehicle 2 holding their cellphone raised in their hand at the time of contact. There were no injuries and police were not called. | |
| 30610-4384 | ADS | Zoox, Inc. | 2022-11 18:06 | Las Vegas, NV | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 9 | Street | A Zoox vehicle in autonomy was completing a lane change from lane 4 into lane 3 with turn signals illuminated, when Vehicle #2 suddenly swerved from lane 2 into lane 3 making light contact with the left front of the Zoox…A Zoox vehicle in autonomy was completing a lane change from lane 4 into lane 3 with turn signals illuminated, when Vehicle #2 suddenly swerved from lane 2 into lane 3 making light contact with the left front of the Zoox vehicle. No injuries were reported and police were not called to the scene. | |
| 30610-4385 | ADS | Zoox, Inc. | 2022-11 20:22 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 5 | Street | A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA when a leading vehicle in the lane began to slow down prompting the Zoox vehicle to slow correspondingly. The Zoox vehicle, with brake ligh…A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA when a leading vehicle in the lane began to slow down prompting the Zoox vehicle to slow correspondingly. The Zoox vehicle, with brake lights illuminated, had slowed to 5 mph when it was struck from the rear by vehicle 2. Zoox vehicle camera footage shows the driver of vehicle 2 holding their cellphone raised in their right hand. There were no injuries and police were not called. | |
| 855-4460 | ADS | Mercedes-Benz USA, LLC | 2022-11 17:20 | San Jose, CA | 2021 Mercedes-Benz S450 | Unknown, see Narrative | Pickup Truck | No Injuries Reported | 19 | Highway / Freeway | The Mercedes-Benz vehicle was traveling northbound on [XXX] in lane one, near [XXX], with the vehicle's L3 ADS engaged. Traffic ahead began slowing, and the operator attempted a right lane change into lane two. The Merce…The Mercedes-Benz vehicle was traveling northbound on [XXX] in lane one, near [XXX], with the vehicle's L3 ADS engaged. Traffic ahead began slowing, and the operator attempted a right lane change into lane two. The Mercedes-Benz vehicle operator was unable to complete the lane change and instead applied the brakes. The Mercedes-Benz operator was unable to avoid contact with the Ford vehicle that was in front of it, and the Mercedes-Benz front bumper contacted the rear bumper of the Ford vehicle. | |
| 1422-4087 v2 | ADS | Volvo Car USA, LLC | 2022-10 08:23 | FL | 2022 Polestar Polestar 2 | ADAS | Other Fixed Object | No Injuries Reported | 55 | Highway / Freeway | The initial submission was by email and electronic form to SGO Mailbox on 10/18/2022 at 10:09PM. This is a resubmission of data using the SGO portal with Volvo Cars USA, LLC account on behalf of Polestar Automotive USA.…The initial submission was by email and electronic form to SGO Mailbox on 10/18/2022 at 10:09PM. This is a resubmission of data using the SGO portal with Volvo Cars USA, LLC account on behalf of Polestar Automotive USA. Volvo Cars USA, LLC is submitting this report on behalf of Polestar Automotive USA and Polestar Performance AB. The vehicle was a company vehicle (owned by Polestar Automotive USA) driven by a company employee, with no known modifications to the factory hardware condition or software updates or changes not released to the public. Subject vehicle was traveling around a curve on the freeway interchange at approximately 55mph, recommended speed in that portion of exchange was 50mph. Driver looked down and took attention off the road. The vehicle continued slightly straight, running up and grazing off the concrete barrier, before coming back into the lane. The vehicle's rear suspension, rear and front wheel/tire were damaged. Vehicle was towed from the scene. We have recovered data from the vehicle and are currently reviewing what information was stored for the incident and will update this report. 10 Day update: After review of the EDR data the technical team was able to determine the following: Pilot Assist was disengaged due to the lateral acceleration exceeded the system limit and the available steering torque system input exceeding the limit. The vehicle could not steer enough to follow the lane. Several warnings were issued: visually in the DIM (Drivers Information Module, display), haptically in the steering wheel, before Pilot Assist was disengaged. The driver is always responsible for ensuring that the vehicle is driven in a safe manner. The driver failed to take control of the vehicle when the vehicles Pilot Assist gave the warnings. | |
| 30270-4104 v2 | ADS | Waymo LLC | 2022-10 13:35 | Tempe, AZ | 2022 Peterbilt 579 Epiq | ADS | Passenger Car | No Injuries Reported | 59 | Highway / Freeway | The content of this report is unchanged from the initial report submitted on October [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2022 at 1:35 PM PST a Waymo Autonomous Vehicl…The content of this report is unchanged from the initial report submitted on October [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2022 at 1:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode on southbound [XXX] and an SUV was traveling ahead of the Waymo AV in the right adjacent lane. The SUV approached stopped traffic in its lane and struck a passenger vehicle. The Waymo AV test driver then transitioned to manual mode. The passenger vehicle that was struck by the SUV spun 90 degrees counterclockwise and was pushed partially into the Waymo AV's lane, making contact with the right side of the Waymo AV and 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, trailer, and passenger vehicle sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an airbag deployed (in the passenger vehicle) and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-4274 | ADS | Waymo LLC | 2022-10 08:27 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 6 | Intersection | On October [XXX], 2022 at 8:27 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California made contact with the pavement on a steep hill on [XXX] at [XXX]. The Waymo AV was on a steep hill, turni…On October [XXX], 2022 at 8:27 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California made contact with the pavement on a steep hill on [XXX] at [XXX]. The Waymo AV was on a steep hill, turning from [XXX] onto [XXX], when the Waymo AV's undercarriage made contact with the pavement (the AV did not contact any vehicle or road user). 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. | |
| 30290-4127 | ADS | Argo AI | 2022-10 13:14 | Austin, TX | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 11 | Street | Redacted by NHTSA as confidential business information | |
| 30290-4128 | ADS | Argo AI | 2022-10 08:00 | Austin, TX | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30530-4264 | ADS | Aurora Operations, Inc. | 2022-10 10:55 | Shenandoah, TX | 2022 Peterbilt 579 | ADAS | Other, see Narrative | No Injuries Reported | 64 | Highway / Freeway | At 10:55am on 10/[XXX]/22, an Aurora Class 8 truck was traveling southbound in manual mode in normal traffic conditions on [XXX] when an approximately 3-foot long 2x4 piece of wood was kicked up into the Aurora truck's w…At 10:55am on 10/[XXX]/22, an Aurora Class 8 truck was traveling southbound in manual mode in normal traffic conditions on [XXX] when an approximately 3-foot long 2x4 piece of wood was kicked up into the Aurora truck's windshield after going under the wheels of a truck to the left of the Aurora truck. The Aurora truck's windshield cracked on the lower right side as a result of the strike, but did not shatter. To be clear, the Aurora Driver was not in autonomous mode at the time of the incident or for 16 seconds prior to the incident. There were no injuries as a result of the incident. | |
| 30531-4108 v2 | ADS | Transdev Alternative Services | 2022-10 13:35 | Tempe, AZ | 2022 Peterbilt 579 Epiq | ADS | Passenger Car | No Injuries Reported | 59 | Highway / Freeway | The content of this report is unchanged from the initial report submitted on October [XXX], 2022 (30531-4108-1). On October [XXX], 2022 at 1:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-tr…The content of this report is unchanged from the initial report submitted on October [XXX], 2022 (30531-4108-1). On October [XXX], 2022 at 1:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode on southbound [XXX] and an SUV was traveling ahead of the Waymo AV in the right adjacent lane. The SUV approached stopped traffic in its lane and struck a passenger vehicle. The Waymo AV test driver then transitioned to manual mode. The passenger vehicle that was struck by the SUV spun 90 degrees counterclockwise and was pushed partially into the Waymo AV's lane, making contact with the right side of the Waymo AV and 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, trailer, and passenger vehicle sustained damage. Transdev Alternative Services is reporting this crash under Request no. 1 of Standing General Order 2021-01 because an airbag deployed (in the passenger vehicle) and a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-20221023-0 (rev.20221024203214). | |
| 30531-4278 | ADS | Transdev Alternative Services | 2022-10 08:27 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 6 | Intersection | On October [XXX], 2022 at 8:27 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California made contact with the pavement on a steep hill on [XXX] at [XXX]. The Waymo AV was on a steep hill, tur…On October [XXX], 2022 at 8:27 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California made contact with the pavement on a steep hill on [XXX] at [XXX]. The Waymo AV was on a steep hill, turning from [XXX] onto [XXX], when the Waymo AV's undercarriage made contact with the pavement (the AV did not contact any vehicle or road user). 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-20221021-0 (rev.20221115172608). | |
| 30610-4215 | ADS | Zoox, Inc. | 2022-10 14:02 | San Francisco, CA | 2016 Toyota Highlander | ADS | Van | No Injuries Reported | 0 | Street | A Zoox vehicle was in autonomy proceeding straight on [XXX] in San Francisco, CA when it encountered a double parked vehicle in lane (vehicle 2). The Zoox vehicle came to a complete stop while waiting for an opportunity …A Zoox vehicle was in autonomy proceeding straight on [XXX] in San Francisco, CA when it encountered a double parked vehicle in lane (vehicle 2). The Zoox vehicle came to a complete stop while waiting for an opportunity to merge around vehicle 2. Vehicle 2 then rolled backwards into the Zoox vehicle, causing minor damage to front sensors and Vehicle 2 rear bumper. There were no injuries and first responders were not notified. Post incident review did not observe any brake lights or reverse lights on vehicle 2 while it was rolling backwards. | |
| 30610-4217 | ADS | Zoox, Inc. | 2022-10 13:52 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 24 | Intersection | A Zoox vehicle was proceeding straight in autonomy through an intersection with a green light and right of way when vehicle 2 attempted an illegal left turn across lanes of traffic into Zooxs right of way. The safety dri…A Zoox vehicle was proceeding straight in autonomy through an intersection with a green light and right of way when vehicle 2 attempted an illegal left turn across lanes of traffic into Zooxs right of way. The safety driver disengaged and applied max braking effort which allowed Zoox to mitigate but not completely prevent the unavoidable collision. The Zoox vehicle struck the right front corner of vehicle 2. No injuries were reported and the police were not called to the scene. | |
| 502-4131 | ADS | Ford Motor Company | 2022-10 13:14 | Austin, TX | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 11 | Street | Redacted by NHTSA as confidential business information | |
| 502-4132 | ADS | Ford Motor Company | 2022-10 08:00 | Austin, TX | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 1306-4235 | ADS | Toyota Motor Engineering & Manufacturing | 2022-09 09:02 | Sun City, AZ | 2021 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | This report is being submitted because May Mobility notified Toyota on Oct. 4, 2022 of Monthly Report submission 30413-3943-1,related to an incident reported in September 2022. Toyota has no additional information on thi…This report is being submitted because May Mobility notified Toyota on Oct. 4, 2022 of Monthly Report submission 30413-3943-1,related to an incident reported in September 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. | |
| 30270-4051 | ADS | Waymo LLC | 2022-09 12:57 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | 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-4072 | ADS | Waymo LLC | 2022-09 09:42 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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-4073 | ADS | Waymo LLC | 2022-09 06:38 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | 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-4074 | ADS | Waymo LLC | 2022-09 04:03 | Huntsville, TX | 2022 Peterbilt 579 Epiq | ADS | Other, see Narrative | No Injuries Reported | 35 | Highway / 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 v2 | ADS | Argo AI | 2022-09 17:24 | Palo Alto, CA | 2020 Ford Escape | ADS | Non-Motorist: Cyclist | No Injuries Reported | 21 | Street | 2022-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-3985 | ADS | Argo AI | 2022-09 10:23 | Miami, FL | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-3978 v3 | ADS | Cruise LLC | 2022-09 05:14 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | 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-3943 | ADS | May Mobility | 2022-09 09:02 | Sun City, AZ | 2021 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Parking 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-4077 | ADS | Transdev Alternative Services | 2022-09 04:03 | Huntsville, TX | 2022 Peterbilt 579 Epiq | ADS | Other, see Narrative | No Injuries Reported | 35 | Highway / 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-4079 | ADS | Transdev Alternative Services | 2022-09 12:57 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | 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-4080 | ADS | Transdev Alternative Services | 2022-09 09:42 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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-4081 | ADS | Transdev Alternative Services | 2022-09 06:38 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | 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). | |
| 30610-3752 v2 | ADS | Zoox, Inc. | 2022-09 11:30 | San Francisco, CA | 2016 Toyota Highlander | ADS | Non-Motorist: Cyclist | No Injuries Reported | 2 | Street | 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-3914 v2 | ADS | Ford Motor Company | 2022-09 17:24 | Palo Alto, CA | 2020 Ford Escape | ADS | Non-Motorist: Cyclist | No Injuries Reported | 21 | Street | 2022-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. |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.