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
3450 reports, showing 3201 to 3300.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30412-3281 v2 | ADS | Cruise LLC | 2022-06 10:49 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 19 | Street | Redacted by NHTSA as confidential business information | |
| 30531-3256 v2 | ADS | Transdev Alternative Services | 2022-06 12:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. As the Waymo AV turned left and into the parking lot, the Waymo AV's…A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did no contact any vehicle or road user). At the time of the contact, 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 minor undercarriage 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-[XXX]. | |
| 30531-3445 | ADS | Transdev Alternative Services | 2022-06 7:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on ea…On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX], a pickup that had previously been stopped behind the Waymo AV rolled 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, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX] | |
| 30531-3446 | ADS | Transdev Alternative Services | 2022-06 10:07 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On June [XXX], 2022 at 10:07 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 in autonomous…On June [XXX], 2022 at 10:07 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 in autonomous mode behind stopped traffic facing east on [XXX]. The passenger vehicle ahead of the Waymo AV transitioned into reverse and began to accelerate, making contact with the front 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX] | |
| 30531-3660 | ADS | Transdev Alternative Services | 2022-06 16:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | Minor | 18 | Intersection | On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] a…On June [XXX], 2022 at approximately 4:50 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California allegedly contributed to a collision between a passenger vehicle and a pickup truck on [XXX] at [XXX], according to a claim by the driver of the passenger vehicle. The Waymo AV was in autonomous mode and preparing to enter southbound [XXX] as a passenger vehicle on [XXX] approached from behind. A pickup truck was traveling next to the passenger vehicle in the adjacent left lane. As the passenger vehicle approached the Waymo AV from behind, the passenger vehicle entered the adjacent left lane that was occupied by the pickup truck and maneuvered around the Waymo AV. The pickup truck proceeded without stopping, and the passenger vehicle's driver shortly after signaled to the Waymo AV test driver to pull over. The Waymo AV test driver then transitioned to manual mode and pulled over. Transdev has no data or knowledge of any contact between any of the three vehicles. There was no contact or collision between the Waymo AV and any other vehicle. However, the driver and passenger in the passenger vehicle have subsequently alleged injuries based on alleged contact between the pick-up truck and passenger vehicle, which contact their allegations attribute to the behavior of Waymo's AV in a bodily injury claim under Waymo's insurance policy. Waymo received notice of this insurance claim on July [XXX]. Transdev Alternative Services is reporting this event 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 30270-3655-1. | |
| 30590-3431 | ADS | Apple Inc. | 2022-06 15:15 | Mountain View, CA | 2016 Lexus RX 450h | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's …Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's designated seating position, and with a safety operator in the front passenger seating position. Subject vehicle approached a red light to make a right turn East-bound onto [XXX]. The safety operator suggested that the safety driver disengage the ADS and make the turn in manual mode because the vehicle was hesitant in approaching the intersection. The safety driver disengaged the ADS, and, approximately 250ms later, subject vehicle was lightly struck from behind by a white Mazda3. Having seen debris on the roadway, the driver and operator believed they had run over a rock and did not realize they were hit by the vehicle. After concluding the mission, the driver and operator found damage to a sensor during an inspection. A subsequent review of video led to discovery of the crash. No injuries were reported, and law enforcement was not called to the scene. In addition to telematics and video, we also have photographs of the vehicle's damaged sensor. | |
| 30610-3072 v2 | ADS | Zoox, Inc. | 2022-06 13:15 | San Francisco, CA | 2016 Toyota Highlander | ADS | Non-Motorist: Other | Moderate | 12 | Intersection | A Zoox vehicle in autonomous mode was proceeding westbound with the right of way on a green traffic light at the six way intersection of [XXX], [XXX], and [XXX], when a person operating an electric scooter ran a red ligh…A Zoox vehicle in autonomous mode was proceeding westbound with the right of way on a green traffic light at the six way intersection of [XXX], [XXX], and [XXX], when a person operating an electric scooter ran a red light and proceeded northbound into the intersection. The scooter made contact with the left rear quarter panel of the Zoox vehicle, at which time the Zoox vehicle had disengaged from autonomous mode. The Zoox vehicle pulled over, and police and emergency services arrived at the scene. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field and to update for additional information received in August 2022. This update provides complete information for this incident. | |
| 30610-3215 v2 | ADS | Zoox, Inc. | 2022-06 10:45 | San Mateo, CA | 2016 Toyota Highlander | ADS | SUV | No Injuries Reported | 6 | Street | A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the seco…A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the second vehicle and cut in abruptly from the left, making contact with the front left side and sensors of the Zoox vehicle as it was exiting the space. The Zoox operator disengaged to manual mode just before the contact. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. | |
| 30610-3320 | ADS | Zoox, Inc. | 2022-06 14:36 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 25 | Street | A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor dama…A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor damage to both vehicles. The Zoox vehicle had disengaged for unrelated traffic within 30 seconds of the contact. There were no injuries and the police were not called. | |
| 502-3140 v2 | ADS | Ford Motor Company | 2022-06 16:35 | Austin, TX | 2020 Ford Escape | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-3413 | ADS | Ford Motor Company | 2022-06 14:48 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 502-3416 | ADS | Ford Motor Company | 2022-06 13:30 | Pittsburgh, PA | 2020 Ford Escape | ADS | SUV | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 540-3083 v2 | ADS | General Motors, LLC | 2022-06 1:54 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Pedestrian | Unknown | 5 | Street | On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update 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-3080-2) | |
| 540-3085 v2 | ADS | General Motors, LLC | 2022-06 23:00 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On June [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an update 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-3084-2) | |
| 540-3283 v2 | ADS | General Motors, LLC | 2022-06 10:49 | San Francisco, CA | 2020 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 19 | Street | On July [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured…On July [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an update 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-3281-2) | |
| 1306-3355 | ADS | Toyota Motor Engineering & Manufacturing | 2022-05 16:11 | Arlington, TX | 2020 Lexus RX450H | ADS | Pickup Truck | No Injuries Reported | 11 | Street | This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 2022. Toyota has no additional information on this…This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 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-2895 v2 | ADS | Waymo LLC | 2022-05 15:11 | Ennis, TX | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | Moderate | 62 | Highway / Freeway | Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-[XXX]-1…Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-[XXX]-1]. On May [XXX], 2022 at 3:11 PM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound Interstate [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the rightmost lane on Interstate [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it encountered tire debris in its lane, executed a right lane change, and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. The Waymo AV exited the roadway to the right shoulder of the road and came to a stop off of the roadway. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained moderate damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. The Waymo AV test driver was transported for medical care and the Waymo AV software operator, seated in the passenger seat, later sought medical attention. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved in the crash was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-3055 v2 | ADS | Waymo LLC | 2022-05 01:16 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | Motorcycle | No Injuries Reported | 0 | Intersection | The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. 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-3056 v2 | ADS | Waymo LLC | 2022-05 01:43 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AVs undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, 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 minor undercarriage damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV 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-3057 v2 | ADS | Waymo LLC | 2022-05 02:30 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Unknown | 0 | Intersection | The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-3057-1]. On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Ari…The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30270-3057-1]. On May [XXX], 2022 at 2:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] at the [XXX] onramp. While the Waymo AV was stopped at a red light on southbound [XXX] in the rightmost through lane, a passenger vehicle approached the Waymo AV from behind and the right front of the passenger vehicle made contact with the left rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode and a test driver was present (in the driver's seating position). Both vehicles sustained major damage. The driver of the other vehicle was transported from the scene to a hospital for medical treatment. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away, the crash resulted in airbag deployment, and the driver of the other vehicle was transported from the scene to a hospital for medical treatment. 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-3219 | ADS | Waymo LLC | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-3220 | ADS | Waymo LLC | 2022-05 09:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX] while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. 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-3221 | ADS | Waymo LLC | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | On May [XXX], 2022 at 1:26 PM 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 proceeding south on [XXX] at…On May [XXX], 2022 at 1:26 PM 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 proceeding south on [XXX] at [XXX]. , [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30290-3119 | ADS | Argo AI | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30410-3043 | ADS | Motional | 2022-05 12:58 | Las Vegas, NV | 2022 Hyundai Ioniq 5 | ADS | Other, see Narrative | No Injuries Reported | 8 | Street | Redacted by NHTSA as confidential business information | |
| 30412-3073 | ADS | Cruise LLC | 2022-05 4:37 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30413-3138 | ADS | May Mobility | 2022-05 16:11 | Arlington, TX | 2020 Lexus RX450H | ADS | Pickup Truck | No Injuries Reported | 11 | Street | The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passe…The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passenger-side mirror to contact the parked vehicle's driver-side mirror. The May vehicle's ground mapping module had fallen significantly behind in its processing of lidar data. As a result, actual objects were being filtered out of the lidar data during object detection. This filtering caused the truck to oscillate between being detected, detecting only the cab, detecting the cab and mirror, and not being detected at all. After assessing the issue, it has been determined that ground map latency alone will not cause safety issues. There is no risk to VRUs, or anything at ground level. The issue was with something in the air (mirror), above the ground. A permanent fix to address the ground map latency issue is in process and will be implemented in the entire fleet within the next 30 days. The second factor in the collision is that we were artificially constraining the vehicle to the right side of the road due to ambiguous and unpainted roadway. If we change that constraint to an advisory line (and allow the vehicle to cross the line to the left), we would have been far enough to the left to avoid collision (simulation success). Solution Implementation: AVO training for extra caution related to protruding items like mirrors (short term), software changes coming in the next update and hotfix (within 30 days), and further improvement in the following update (within 60 days). Until the tested software changes are implemented, we have advised the AVOs to take extra caution in these scenarios and to continue to disengage autonomy when desired. As always, we sacrifice autonomy for safety, as needed. | |
| 30490-3168 | ADS | Beep, Inc. | 2022-05 12:30 | Dunedin, FL | Navya | ADS | Bus | No Injuries Reported | 7 | Intersection | Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Tel…Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Telemetry/Video: Requested and received Vehicle taken out of service: Yes temporary safety hold Photographs: Yes Substantial damage: No damages to report Vehicle placed on safety hold: Yes vehicle has been inspected and available for service Lead Investigator: Chief Safety Officer The Beep shuttle attendant was traveling Southbound on [XXX] at approx 7-12 mph in ADS and headed towards the intersection of [XXX]. Beep vehicle stopped at red light at intersection. As the Beep vehicle was crossing the intersection in manual and slowing to a stop to return to ADS in a southbound direction, the trailing bus made light contact with its bicycle rack to the Beep shuttle rear end. The trailing vehicle is a bus owned and operated by the Pinellas Suncoast Transit Authority (PSTA). According to video, as reported by the shuttle attendant and the PSTA Road Supervisor, the bus was tailgating. Root Cause: Trailing vehicle following too closely and not observing Navya slowing to a stop. | |
| 30531-2902 v2 | ADS | Transdev Alternative Services | 2022-05 15:11 | Ennis, TX | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | Moderate | 62 | Highway / Freeway | Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30531-[XXX]-1…Other than noting that the vehicle that struck the Waymo AV had encountered tire debris in its lane, the content of this report is unchanged from the initial report submitted on May [XXX], 2022 [Report ID # 30531-[XXX]-1] On May [XXX], 2022 at 3:11 PM PST a Waymo Autonomous Vehicle (Waymo AV) Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the rightmost lane on Interstate [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it executed a right lane change and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. The Waymo AV exited the roadway to the right shoulder of the road and came to a stop off of the roadway. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained moderate damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. The Waymo AV test driver was transported for medical care and the Waymo AV software operator, seated in the passenger seat, later sought medical attention. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved in the crash was transported from the scene to a hospital for medical treatment 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 identical to WaymoLLC-202205[XXX]-0 (rev.202205[XXX]603622) | |
| 30531-3064 v2 | ADS | Transdev Alternative Services | 2022-05 01:16 | San Francisco, CA | 2021 Jaguar I-Pace | Unknown, see Narrative | Motorcycle | No Injuries Reported | 0 | Intersection | Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Sa…Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202205[XXX]-0 (rev.202205[XXX]215904). | |
| 30531-3065 v2 | ADS | Transdev Alternative Services | 2022-05 01:43 | Phoenix, AZ | 2021 Jaguar I-Pace | Unknown, see Narrative | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact …The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AVE did not contact any vehicle or road user). At the time of contact, 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 minor undercarriage damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV 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-202205[XXX]-0 (rev.202205[XXX]213041). | |
| 30531-3225 | ADS | Transdev Alternative Services | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-[XXX]. | |
| 30531-3226 | ADS | Transdev Alternative Services | 2022-05 09:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX]. while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. 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-[XXX]. | |
| 30531-3227 | ADS | Transdev Alternative Services | 2022-05 13:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | On May [XXX], 2022 at 1:26 PM 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 proceeding south on [XXX] …On May [XXX], 2022 at 1:26 PM 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 proceeding south on [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-2022[XXX]-0 (rev.20220615[XXX]) | |
| 30610-3158 v2 | ADS | Zoox, Inc. | 2022-05 13:30 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 25 | Street | A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is su…A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. | |
| 30711-3157 | ADS | Pony.ai | 2022-05 15:00 | Irvine, CA | 2021 Hyundai Kona EV | ADS | Passenger Car | No Injuries Reported | 4 | Street | On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of t…On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of the Pony.ai vehicle. The Pony.ai vehicle did not suffer damage. There were no injuries, the police were not called to the scene, and the Pony.ai vehicle was driven back to Pony.ai's Irvine-area facility. Please note that the "UNK" checkbox was selected for the Pony.ai vehicle in the grid as there is no option to select "no damage" for the subject vehicle. The only minor damage in the incident was to the passenger vehicle. | |
| 502-2973 v2 | ADS | Ford Motor Company | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 540-3123 | ADS | General Motors, LLC | 2022-05 4:37 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Minor | 0 | Intersection | On June [XXX], 2022, 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 June [XXX], 2022, 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-3073-1) | |
| 855-3183 v2 | ADS | Mercedes-Benz USA, LLC | 2022-05 15:05 | Commerce, CA | 2022 Mercedes-Benz S350D | ADS | Heavy Truck | No Injuries Reported | Highway / Freeway | While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resu…While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resulted in two minor scratches and two indentations on the rear bumper of the Mercedes-Benz. The driver of the truck did not pull over after the collision. The Mercedes-Benz was driven from the incident location, and further inspection of the vehicle concluded no additional damage beyond the cosmetic dents and surface scratches. | ||
| 10003-3210 | ADS | Navistar, Inc. | 2022-04 15:52 | Tucson, AZ | 2021 International LT625 | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | 65 | Highway / Freeway | All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event doe…All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrier. The event occurred as follows: As the truck was being operated on the highway, within its mapped ODD, the driver and test engineer attempted to engage the ADS. However, the ADS was not functional at that moment due to the computer unit not having been initialized, and should not have been attempted to be activated. In short, this was a failed attempt to engage the system as a result of human error. The system has now been modified to prevent the ADS from attempting to engage unless the health of the system is fully functional to prevent human error from repeating this event. When the erroneous attempt to engage occurred, the uninitialized vehicle control unit rotated the steering to the left, causing the truck to veer left. The safety driver took control of the steering, and was able to steer accordingly, but not before the left front truck tire and left front quarter panel came into contact with the concrete barrier to the left of the lanes of travel. | |
| 273-2632 v2 | ADS | Chrysler (FCA US, LLC) | 2022-04 03:30 | Saint Clair, MI | 2022 Jeep Grand Cherokee | ADAS | Other Fixed Object | No Injuries Reported | 50 | Unknown | Redacted by NHTSA as confidential business information | |
| 30270-2610 v2 | ADS | Waymo LLC | 2022-04 02:27 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 20 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 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 in autonomous mode and proceeding southbound on [XXX] in the rightmost lane, with a passenger vehicle traveling parallel in the left adjacent lane. As the two vehicles approached [XXX], the passenger vehicle cut into the Waymo's lane and braked before turning right on [XXX]. As the passenger vehicle executed the right turn, the Waymo AV test driver transitioned to manual mode, applied the brakes, but made contact with the passenger side rear corner of the passenger vehicle. 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 other party immediately left the scene of the event. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2646 v2 | ADS | Waymo LLC | 2022-04 19:55 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger car on [XXX] at [XXX] The Waymo AV came to a stop at a stop sign on [XXX] at [XXX] and as it was about to proceed, a passenger vehicle behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2657 v2 | ADS | Waymo LLC | 2022-04 18:29 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Motorcycle | No Injuries Reported | 3 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was preparing to make a right turn from southbound [XXX] onto westbound [XXX], when it slowed to yield to a pedestrian crossing [XXX]. As the Waymo AV yielded, a motorcycle directly behind the Waymo AV was rear-ended by a pick-up truck. The motorcycle was pushed forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV and the motorcycle sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and a motorcycle was damaged. 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-2743 v2 | ADS | Waymo LLC | 2022-04 14:53 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | Minor | 0 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2743-1]. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2743-1]. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling in autonomous mode in the slip lane on northbound [XXX] at [XXX]. As the Waymo AV slowed to yield to a pedestrian pushing a shopping cart in a crosswalk, the Waymo AV test driver transitioned to manual mode and stopped the Waymo AV. The Waymo AV test driver then proceeded forward but had to yield to approaching traffic in the merge between northbound [XXX] and northbound [XXX]. As the Waymo AV came to a stop, a pickup truck traveling behind the Waymo AV then 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. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and the Waymo AV test driver was transported from the scene for medical treatment due to reported injuries. 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-2793 v2 | ADS | Waymo LLC | 2022-04 02:31 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Auto…Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA made contact with a parking lot driveway on the 200 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, 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 minor undercarriage 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-2818 v2 | ADS | Waymo LLC | 2022-04 16:36 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2818-1]. On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2818-1]. On April [XXX], 2022 at 4:36 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 in autonomous mode and traveling on westbound [XXX], when it slowed for the vehicle directly in front of the Waymo AV, which stopped shortly after passing [XXX]. Shortly after the Waymo AV came to a stop, the SUV behind the Waymo AV was rear-ended by a pickup truck, and the SUV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-3009 | ADS | Waymo LLC | 2022-04 8:14 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On April [XXX], 2022 at 8:14 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 at a red l…On April [XXX], 2022 at 8:14 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 at a red light facing northeast on [XXX] in autonomous mode. While the light was still red, a passenger vehicle that had been stopped behind the Waymo AV began to move forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-3010 | ADS | Waymo LLC | 2022-04 23:30 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Animal | No Injuries Reported | 24 | Street | On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode o…On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode on northbound [XXX] and had just passed [XXX] when a cat entered the street from the adjacent right curb. The Waymo AV then made contact with the cat. The Waymo AV braked and the Waymo AV test driver took manual control and brought the Waymo AV to a stop. 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 did not sustain any damage and the cat was found to be deceased; the cat did not have any identification tags or other signs of ownership. 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. This report was submitted from the Pacific time zone on the required date. | |
| 30270-3011 | ADS | Waymo LLC | 2022-04 06:37 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 17 | Street | On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in ma…On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in manual in the left lane of [XXX] (a one-way street). After passing through the [XXX] intersection, a parked pickup truck on the left side of [XXX] pulled out of the parked position and made contact with the front left fender of the passing 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. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30370-2949 | ADS | TuSimple | 2022-04 15:52 | Tucson, AZ | 2021 INTERNATIONAL LT 625 | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | 65 | Highway / Freeway | TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrie…TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrier. The event occurred as follows: As the truck was being operated on the highway, within its mapped ODD, the driver and test engineer attempted to engage the ADS. However, the ADS was not functional at that moment due to the computer unit not having been initialized, and should not have been attempted to be activated. In short, this was a failed attempt to engage the system as a result of human error. The system has now been modified to prevent the ADS from attempting to engage unless the health of the system is fully functional to prevent human error from repeating this event. When the erroneous attempt to engage occurred, the uninitialized vehicle control unit rotated the steering to the left, causing the truck to veer left. The safety driver took control of the steering, and was able to steer accordingly, but not before the left front truck tire and left front quarter panel came into contact with the concrete barrier to the left of the lanes of travel. The contact resulted in a scuff to the left tire and damage to the radar unit extending from the left quarter panel. | |
| 30412-2823 v2 | ADS | Cruise LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-2884 | ADS | Cruise LLC | 2022-04 00:43 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 5 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-2885 | ADS | Cruise LLC | 2022-04 01:55 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-2886 | ADS | Cruise LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 22 | Street | Redacted by NHTSA as confidential business information | |
| 30412-2887 | ADS | Cruise LLC | 2022-04 00:13 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 30412-2888 | ADS | Cruise LLC | 2022-04 03:35 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 2 | Street | Redacted by NHTSA as confidential business information | |
| 30531-2822 v2 | ADS | Transdev Alternative Services | 2022-04 16:36 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | The content of this report is unchanged from the initial report (Report ID 30531-2822-1) On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collisi…The content of this report is unchanged from the initial report (Report ID 30531-2822-1) On April [XXX], 2022 at 4:36 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 in autonomous mode and traveling on westbound [XXX], when it slowed for the vehicle directly in front of the Waymo AV, which stopped shortly after passing [XXX]. Shortly after the Waymo AV came to a stop, the SUV behind the Waymo AV was rear-ended by a pickup truck, and the SUV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor 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 identical to WaymoLLC-202204[XXX]-0 (rev.202204[XXX]190125) | |
| 30610-2913 | ADS | Zoox, Inc. | 2022-04 05:55 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 8 | Intersection | A Zoox vehicle in autonomous mode was proceeding straight through the intersection of [XXX]. and [XXX]. when it was rear-ended by a passenger vehicle that was switching lanes and made contact with the Zoox vehicle's rear…A Zoox vehicle in autonomous mode was proceeding straight through the intersection of [XXX]. and [XXX]. when it was rear-ended by a passenger vehicle that was switching lanes and made contact with the Zoox vehicle's rear sensors. The other party left the scene. The police were not called, and there were no injuries. | |
| 30711-2862 | ADS | Pony.ai | 2022-04 9:00 | Miliptas, CA | 2020 Hyundai Kona EV | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | On April [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was parked in a parking lot when a passenger vehicle reversed into the Pony.ai vehicle. T…On April [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was parked in a parking lot when a passenger vehicle reversed into the Pony.ai vehicle. The Pony.ai vehicle sustained minor damage to the driver's side rear door. There were no injuries, the police were not called to the scene, and the Pony.ai vehicle was driven back to Pony.ai's Fremont facility. | |
| 540-2827 v2 | ADS | General Motors, LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On May [XXX], 2022, 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") manuf…On May [XXX], 2022, 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-2823-2) | |
| 540-2907 | ADS | General Motors, LLC | 2022-04 00:43 | San Francisco, CA | 2020 Cruise AV | ADS | SUV | No Injuries Reported | 5 | Intersection | On May [XXX], 2022 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 May [XXX], 2022 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-2884-1) | |
| 540-2925 | ADS | General Motors, LLC | 2022-04 01:55 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On May [XXX], 2022 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 May [XXX], 2022 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-2885-1) | |
| 540-2926 | ADS | General Motors, LLC | 2022-04 23:21 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 22 | Street | On May [XXX], 2022 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 May [XXX], 2022 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-2886-1) | |
| 540-2927 | ADS | General Motors, LLC | 2022-04 00:13 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Street | On May [XXX], 2022 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 May [XXX], 2022 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-2887-1) | |
| 540-2928 | ADS | General Motors, LLC | 2022-04 03:35 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Unknown | 2 | Street | On May [XXX], 2022 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 May [XXX], 2022 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-2888-1) | |
| 1712-2474 v2 | ADS | Robert Bosch, LLC | 2022-03 08:50 | Los Angeles, CA | EQS 450 4matic | ADS | Unknown | Minor | Parking Lot | Redacted by NHTSA as confidential business information | ||
| 30270-2465 v2 | ADS | Waymo LLC | 2022-03 21:39 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Intersection | The content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2465-1]. On March [XXX], 2022 at 9:39 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix…The content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2465-1]. On March [XXX], 2022 at 9:39 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, AZ was in a collision involving a van on N. [XXX] at [XXX]. The Waymo AV was stopped at a red light on southbound N. [XXX] when a van behind the Waymo AV failed to stop and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The van and Waymo AV sustained moderate 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-2591 v2 | ADS | Waymo LLC | 2022-03 14:57 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Unknown | 0 | Intersection | Other than an update to the narrative to describe oncoming vehicle's separate collision and a correction to the 'Notice Received Date', the content of this report is unchanged from the initial report submitted on March […Other than an update to the narrative to describe oncoming vehicle's separate collision and a correction to the 'Notice Received Date', the content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2465-1]. On March [XXX], 2022 at 15:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. 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 was stationary at a 4-way stop sign intersection when an oncoming car was involved in a separate collision, departed from its lane, and struck the Waymo AV. Both vehicles sustained damage in the front of the vehicle. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and a vehicle's airbag(s) deployed. 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-2605 v2 | ADS | Waymo LLC | 2022-03 01:16 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 9 | Intersection | The description of the event in this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2605-1]. On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') ope…The description of the event in this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2605-1]. On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was slowing for a stop sign while traveling westbound on [XXX] in autonomous mode. An SUV approached from behind and made contact with the rear of the Waymo AV. The other party immediately left the scene of the event. 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 moderate 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-2609 v2 | ADS | Waymo LLC | 2022-03 11:07 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 4 | Intersection | The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2609-1]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fr…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2609-1]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on the 1000 block of [XXX]. The Waymo AV was stopped at a red traffic light on southbound [XXX] when a pedestrian entered the crosswalk. When the traffic light turned green, the Waymo AV remained stopped for a crossing pedestrian who had just reached the pedestrian island in the middle of the crosswalk. After a brief pause, the ADV started to proceed, when the SUV behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2773 | ADS | Waymo LLC | 2022-03 07:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 3 | Intersection | On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on …On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on [XXX] in manual mode in a narrow passageway. The Waymo AV approached a stop sign and the test driver steered to the right around a parked vehicle with oncoming traffic approaching. The right rear sensor housing of the Waymo AV made contact with a parked SUV on the right side of the road. 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2774 | ADS | Waymo LLC | 2022-03 18:14 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On March [XXX], 2022 at 6:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, AZ was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was in autonomous mode on southbound [XXX] and stop…On March [XXX], 2022 at 6:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, AZ was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was in autonomous mode on southbound [XXX] and stopped at a red light to make an unprotected left onto eastbound [XXX]. When the traffic light turned green, the Waymo AV slowly proceeded into the intersection and stopped to yield to oncoming traffic. The Waymo AV test driver transitioned to manual mode just before an SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2775 | ADS | Waymo LLC | 2022-03 12:22 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On March [XXX], 2022 at 12:22 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 in traffic…On March [XXX], 2022 at 12:22 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 in traffic, eastbound on [XXX] in autonomous mode. A parked car to the right of the Waymo AV began reversing into the street and made contact with the rear right side 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30290-2481 v2 | ADS | Argo AI | 2022-03 12:39 | Coral Gables, FL | 2020 Ford Escape | ADS | SUV | Moderate | 0 | Traffic Circle | Redacted by NHTSA as confidential business information | |
| 30290-2696 | ADS | Argo AI | 2022-03 12:50 | Miami, FL | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-2588 v2 | ADS | Cruise LLC | 2022-03 13:24 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Cyclist | Serious | 4 | Street | Redacted by NHTSA as confidential business information | |
| 30412-2593 v2 | ADS | Cruise LLC | 2022-03 02:07 | San Francisco, CA | 2020 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-2654 v2 | ADS | Cruise LLC | 2022-03 12:26 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Moderate | 10 | Street | A Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound in the rightmost lane on [XXX] between [XXX] and [XXX]. Ahead of the Cruise AV, a delivery truck was double-park…A Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound in the rightmost lane on [XXX] between [XXX] and [XXX]. Ahead of the Cruise AV, a delivery truck was double-parked in the rightmost lane of westbound [XXX]. The Cruise AV began to maneuver around the double-parked vehicle by changing lanes. At the same time, a 2010 Honda Civic traveling behind the Cruise AV in the rightmost lane also began to maneuver and increase speed into the leftmost lane. Shortly thereafter, contact was made with the Cruise AV's side door, damaging the front driver side door and radar assembly. There were no reported injuries at the scene by either party and police were not called. The driver of the Honda Civic later claimed injuries related to the event. [Cruise processes ADS compute data regarding the incident.] | |
| 30610-2584 v2 | ADS | Zoox, Inc. | 2022-03 15:00 | San Francisco, CA | 2016 Toyota Highlander | ADS | Non-Motorist: Other | Minor | 2 | Intersection | A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right a…A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right and made contact with the rear corner of the Zoox vehicle at low speed. Police were not called. The Zoox vehicle was in autonomy in the 30 second period prior to contact. | |
| 30610-2651 | ADS | Zoox, Inc. | 2022-03 08:20 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | Minor | 1 | Intersection | A Zoox vehicle in autonomous mode was stopped in traffic when a passenger vehicle from behind made contact with the rear of the Zoox vehicle at low speed. The police were not called. | |
| 30711-2666 | ADS | Pony.ai | 2022-03 11:30 | Tustin, CA | 2019 Hyundai Kona EV | ADS | Other, see Narrative | No Injuries Reported | 23 | Street | On March [XXX], 2022, while in supervised ("Drivered") autonomous mode traveling eastbound in the right lane of [XXX] in Tustin, CA, a Pony.ai Autonomous Vehicle drove over a temporary sign that had previously fallen ove…On March [XXX], 2022, while in supervised ("Drivered") autonomous mode traveling eastbound in the right lane of [XXX] in Tustin, CA, a Pony.ai Autonomous Vehicle drove over a temporary sign that had previously fallen over and was lying flat on its side in the travel lane. The impact redirected the vehicle towards the curb. The Safety Operator took control, disengaging autonomous mode, braked, and steered the vehicle away from the direction of the curb. The right front tire scraped the right curb. The vehicle sustained minor damage to the right front strut and control arm. There were no injuries and no other vehicles involved. The Safety Operator drove the vehicle back to Pony.ai's Irvine facility. Explanation for "Roadway Description": There was a sign lying flat on its side in the travel lane. Explanation for "Crash With" Description: The subject vehicle's tire made contact with the right curb. | |
| 502-2479 v2 | ADS | Ford Motor Company | 2022-03 12:39 | Coral Gables, FL | 2020 Ford Escape | ADS | SUV | Moderate | 0 | Traffic Circle | Redacted by NHTSA as confidential business information | |
| 502-2751 | ADS | Ford Motor Company | 2022-03 12:50 | Miami, FL | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 540-2590 v2 | ADS | General Motors, LLC | 2022-03 13:24 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Cyclist | Serious | 4 | Street | On April [XXX], 2022, 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 Cruis…On April [XXX], 2022, 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-2588-2). | |
| 540-2594 v2 | ADS | General Motors, LLC | 2022-03 02:07 | San Francisco, CA | 2020 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Street | On April [XXX], 2022, 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 Cruis…On April [XXX], 2022, 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-2593-2). | |
| 540-2706 v2 | ADS | General Motors, LLC | 2022-03 12:26 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | Moderate | 10 | Street | On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an updated report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") m…On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an updated 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-2654-2). | |
| 855-2464 v2 | ADS | Mercedes-Benz USA, LLC | 2022-03 08:50 | Los Angeles, CA | Mercedes-Benz EQS 450 4Matic | ADS | Other, see Narrative | Minor | 1 | Parking Lot | No additional information to report at this time. | |
| 30270-2248 | ADS | Waymo LLC | 2022-02 17:46 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | On February [XXX], 2022 at 5:46 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a bicyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling…On February [XXX], 2022 at 5:46 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a bicyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling southbound on [XXX] when it came to a stop at [XXX]. As the Waymo AV proceeded, a bicyclist traveling northbound on [XXX] proceeded through the stop sign without stopping in order to make a left turn onto westbound [XXX]. The Waymo AV began to brake and the test driver (in the driver's seating position), disengaged the AV system and continued braking. As the bicyclist attempted to complete their left turn, the bicyclist made contact with the driver side rear corner 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 sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user was involved. 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-2258 | ADS | Waymo LLC | 2022-02 10:30 | Sacaton, AZ | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | No Injuries Reported | 50 | Highway / Freeway | On February [XXX], 2022 at 10:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Sacaton, AZ was in a collision involving a box truck on [XXX] south of [XXX]. The Wa…On February [XXX], 2022 at 10:30 AM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Sacaton, AZ was in a collision involving a box truck on [XXX] south of [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode in the right lane, and a motor coach followed by a box truck were traveling in the adjacent left lane. Traffic in the left lane began to slow and the box truck steered to the right and crossed into the right lane before making contact with the passenger side rear corner of the motor coach and then making contact with the driver side rear axle of the Waymo AV trailer. At the time of the impact, the Waymo AV was in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV trailer, motor coach, and box truck 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-2358 v2 | ADS | Waymo LLC | 2022-02 17:46 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | Other than correcting the towing status of the Waymo AV, which was not towed, the content of this report is unchanged from the initial report submitted on February [XXX], 2022 [Report ID #30270-2248-1]. On February [XXX…Other than correcting the towing status of the Waymo AV, which was not towed, the content of this report is unchanged from the initial report submitted on February [XXX], 2022 [Report ID #30270-2248-1]. On February [XXX], 2022 at 5:46 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a bicyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling southbound on [XXX] when it came to a stop at [XXX]. As the Waymo AV proceeded, a bicyclist traveling northbound on [XXX] proceeded through the stop sign without stopping in order to make a left turn onto westbound [XXX]. The Waymo AV began to brake and the test driver (in the driver's seating position), disengaged the AV system and continued braking. As the bicyclist attempted to complete their left turn, the bicyclist made contact with the driver side rear corner of the Waymo AV. At the time of the impact, the Waymo's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user was involved. 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-2359 v2 | ADS | Waymo LLC | 2022-02 10:30 | Sacaton, AZ | 2022 Peterbilt 579 Epiq | ADS | Heavy Truck | No Injuries Reported | 50 | Highway / Freeway | The content of this report is unchanged from the initial report submitted on February [XXX], 2022 [Report ID #30270-2258-1]. On February [XXX], 2022 at 10:30 AM PST a Waymo Autonomous Vehicle ('Waymo AV') Peterbilt Clas…The content of this report is unchanged from the initial report submitted on February [XXX], 2022 [Report ID #30270-2258-1]. On February [XXX], 2022 at 10:30 AM PST a Waymo Autonomous Vehicle ('Waymo AV') Peterbilt Class 8 semi-truck and trailer, operating in Gila River, AZ was in a collision involving a box truck on [XXX] south of [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode in the right lane, and a motor coach followed by a box truck were traveling in the adjacent left lane. Traffic in the left lane began to slow and the box truck steered to the right and crossed into the right lane before making contact with the passenger side rear corner of the motor coach and then making contact with the driver side rear axle of the Waymo AV trailer. At the time of the impact, the Waymo AV was in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV trailer, motor coach, and box truck 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-2551 | ADS | Waymo LLC | 2022-02 08:44 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On February [XXX], 2022 at 8:44 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was stopped at a stop sign facing …On February [XXX], 2022 at 8:44 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was stopped at a stop sign facing west on [XXX] in autonomous mode while yielding to pedestrians in the crosswalk. After the pedestrians had crossed, the Waymo started to edge forward when an SUV to the Waymo AV's rear passed the Waymo AV by driving in the oncoming traffic lane and made contact with the left rear sensor housing 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2552 | ADS | Waymo LLC | 2022-02 15:05 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Street | On February [XXX], 2022 at 3:05 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pick-up truck on [XXX] near [XXX]. The Waymo AV was traveling westboun…On February [XXX], 2022 at 3:05 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pick-up truck on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode and came to a stop while yielding to an oncoming pick-up truck in a narrow roadway. The oncoming truck continued proceeding straight and made contact with the rear left 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2553 | ADS | Waymo LLC | 2022-02 15:02 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On February [XXX], 2022 at 3:02 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 at a red …On February [XXX], 2022 at 3:02 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 at a red light facing north on [XXX] at the [XXX] intersection in autonomous mode. While the traffic light was still red, the vehicle immediately behind the Waymo AV began to accelerate and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2554 | ADS | Waymo LLC | 2022-02 19:45 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On February [XXX], 2022 at 7:45 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle at the northbound merge lane on the 100 block of [XXX…On February [XXX], 2022 at 7:45 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a vehicle approached from behind and made contact with the rear bumper of the Waymo AV. The other vehicle left the scene without exchanging information. 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2555 | ADS | Waymo LLC | 2022-02 00:49 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On February [XXX], 2022 at 12:49 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 stopped at a red…On February [XXX], 2022 at 12:49 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 stopped at a red light facing west on [XXX] at the [XXX] intersection in the left turn lane in autonomous mode. While the traffic light was still red, the vehicle immediately behind the Waymo AV began to accelerate toward the right side of the Waymo AV and made contact with the right rear bumper of the Waymo AV. The other vehicle left the scene without exchanging information. 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 minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date. | |
| 30270-2556 | ADS | Waymo LLC | 2022-02 13:00 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | On February [XXX], 2022 at 1:00 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]. While traveling southbound on [XXX…On February [XXX], 2022 at 1:00 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]. While traveling southbound on [XXX] at [XXX] in autonomous mode, the Waymo AV approached a green light and signaled for a right turn when a pedestrian entered the adjacent crosswalk in accordance with the pedestrian 'WALK' signal. As the Waymo AV began to slow, the driver transitioned the system into manual mode. A few seconds later, a passenger vehicle approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. 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. | |
| 30290-2471 | ADS | Argo AI | 2022-02 8:51 | Washington DC, DC | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-2476 v2 | ADS | Cruise LLC | 2022-02 00:48 | San Francisco, CA | 2020 Cruise AV | ADS | Passenger Car | No Injuries Reported | 13 | Intersection | Redacted by NHTSA as confidential business information |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.