The SGO file, in a form you can search
NHTSA publishes the crash reports as three CSV files of 116 columns each, with several versions of the same report mixed in. This is the same data as one table: driverless systems (ADS) and Level 2 driver assistance side by side, 2021 to today including NHTSA's archive, one row per report at its latest version, every row traceable to its NHTSA report number. Free, CC BY 4.0, refreshed from NHTSA on every pipeline run.
- Reports
- 8612
- Fatal
- 87
- Of them Level 2
- 79
- Reporting entities
- 64
- Incidents
- 2019-08 to 2026-09
8612 reports, showing 7101 to 7200.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-5591 | ADS | Waymo LLC | 2023-04 8:02 | Phoenix, AZ | 2021 Jaguar I-PACE | ADS | Van | No Injuries Reported | 1 | Intersection | On April [XXX], 2023 at 8:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] in the leftmost…On April [XXX], 2023 at 8:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding north on [XXX] was yellow as the Waymo AV approached the intersection. The Waymo AV slowed, preparing to stop, and a van traveling directly behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both the Waymo AV and the van sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5592 | ADS | Waymo LLC | 2023-04 17:29 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Street | On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] between [XXX…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] between [XXX] and [XXX] when it approached an SUV that was stopped in the lane in front of the Waymo AV. The Waymo AV began passing the stopped SUV on the left when the SUV began reversing in the lane. The Waymo AV then stopped behind and to the left of the SUV, and the SUV continued reversing and began a turning maneuver to enter a parking space. The left side of the SUV made contact with the front right corner of the Waymo AV. At the time of the impact, the Waymo AV was stopped and the AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5593 | ADS | Waymo LLC | 2023-04 13:53 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While the Waymo AV was parked at the right side cu…On April [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While the Waymo AV was parked at the right side curb of the road on [XXX], an SUV that was passing the parked Waymo AV in the rightmost lane made contact with the rear drivers side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV did not sustain damage the SUV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30412-5220 v2 | ADS | Cruise LLC | 2023-04 4:45 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5287 v2 | ADS | Cruise LLC | 2023-04 03:15 | Austin, TX | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-5288 v2 | ADS | Cruise LLC | 2023-04 03:15 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 9 | Street | Redacted by NHTSA as confidential business information |
| 30412-5458 | ADS | Cruise LLC | 2023-04 00:35 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-5459 | ADS | Cruise LLC | 2023-04 23:35 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5460 | ADS | Cruise LLC | 2023-04 20:13 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-5461 | ADS | Cruise LLC | 2023-04 21:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 4 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5462 | ADS | Cruise LLC | 2023-04 14:58 | Mesa, AZ | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 34 | Street | Redacted by NHTSA as confidential business information |
| 30413-5396 | ADS | May Mobility | 2023-04 16:16 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | Passenger Car | No Injuries Reported | 18 | Street | On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice a…On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice as fast as the May shuttle and catching up to the May shuttle from behind. The May shuttle began to slow for traffic ahead, which was stopping for a red light, but the following vehicle did not decelerate. While slowing, the May shuttle identified a bollard on the side of the road as a likely pedestrian and added a safety buffer which intersected with the predicted trajectory of the shuttle. This caused the shuttle to increase deceleration to avoid the projected collision with the buffer. The following vehicle started braking late and impacted the May shuttle from behind with a relative velocity of 6.2 m/s. Re-simulation of this event with a future software version shows that the May shuttle would have decelerated less abruptly. |
| 30531-5205 v2 | ADS | Transdev Alternative Services | 2023-04 10:46 | 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. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenge…The content of this report is unchanged from the initial report. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding south on [XXX] was green for the Waymo AV as it approached the intersection. As the Waymo AV approached, an individual riding a motorized scooter traveling north on [XXX] proceeded to turn left onto westbound [XXX], across the paths of the Waymo AV and other oncoming vehicles. The Waymo AV began to brake, and the Waymo AV test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car traveling directly behind the Waymo AV then made contact with the rear of the Waymo AV. The individual riding the scooter was not contacted by the Waymo AV or any other 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. Both the Waymo AV and the passenger car sustained damage, and the individual on the motorized scooter left the scene. Transdev Alternative Services is reporting this crash under Request No 1 of Standing General Order 2021 01 because a Vulnerable Road User was involved. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30531-5088-1. |
| 30531-5604 | ADS | Transdev Alternative Services | 2023-04 17:29 | Santa Monica, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in th…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding southwest on [XXX] was red as the Waymo AV approached the intersection and came to a stop. The signal for traffic proceeding southwest on [XXX] then turned green, and traffic in adjacent lanes began moving while the Waymo AV waited for traffic in its lane to begin to move. The SUV that had been stopped directly behind the Waymo AV began moving forward and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report ID 30270-5586-1. |
| 30531-5605 | ADS | Transdev Alternative Services | 2023-04 22:56 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 0 | Intersection | On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV …On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV came to a stop to yield to an oncoming SUV in a narrow passageway. The SUV proceeded around the Waymo AV 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 driver of the SUV stopped briefly but left before sharing their information. The Waymo sustained damage. Transdev Alternative Serivces is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30270-5584-1. |
| 30610-5232 v2 | ADS | Zoox, Inc. | 2023-04 11:19 | San Francisco, CA | 2017 Toyota Highlander | ADS | Other, see Narrative | No Injuries Reported | 0 | Intersection | A Zoox vehicle in autonomy was proceeding northbound on [XXX] in stop-and-go traffic through an active construction zone. At the same time, an e-scooter traveling near the right curb was passing other slow traffic behind…A Zoox vehicle in autonomy was proceeding northbound on [XXX] in stop-and-go traffic through an active construction zone. At the same time, an e-scooter traveling near the right curb was passing other slow traffic behind the Zoox vehicle. Before the e-scooter could also pass the Zoox vehicle on the right, the e-scooter weaved away from the curb, seemingly to avoid a drainage grate, and came within a close following distance behind the Zoox vehicle. As the Zoox vehicle came to a stop again for traffic ahead the e-scooter rider did not stop, and the e-scooter made contact with the right rear tail light of the Zoox vehicle. The e-scooter rider remained upright, did not stop to exchange information, and immediately rode off while the Zoox vehicle was still stopped. There were no injuries and police were not called. The damage to the Zoox vehicle was limited to a cracked tail light lens. This 10-Day update provides complete information for this incident. |
| 540-5193 v2 | Level 2 | General Motors, LLC | 2023-04 12:24 | Haverhill, MA | 2023 GMC Yukon | ADAS | Passenger Car | No Injuries Reported | Highway / Freeway | GM has no updates from the original submission on April 4, 2023. A 2023 Yukon Denali was traveling eastbound in the left lane on [XXX] at the time of the crash. At 12:21:44 PM EST Super Cruise was engaged and active. A…GM has no updates from the original submission on April 4, 2023. A 2023 Yukon Denali was traveling eastbound in the left lane on [XXX] at the time of the crash. At 12:21:44 PM EST Super Cruise was engaged and active. According to OnStar audio recordings, at some point thereafter, a BMW sedan that was traveling eastbound in the right adjacent lane veered in front of the Yukon. Five seconds before the crash occurred, at 12:24:14 PM EST, the telematics data indicates a Super Cruise override, so that the feature was engaged but not active. Crash data includes one reported frontal impact at 12:24:19 PM EST. The data indicates the driver of the Yukon was belted at the time of the crash and that the driver's airbag deployed. A second occupant of the Yukon was seated in the vehicle's second row. It is unknown if the second-row occupant was belted. | |
| 540-5227 v2 | ADS | General Motors, LLC | 2023-04 4:45 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | On April 18, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufact…On April 18, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day 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-5220-2) |
| 540-5296 v2 | ADS | General Motors, LLC | 2023-04 03:15 | Austin, TX | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5287-2) |
| 540-5297 v2 | ADS | General Motors, LLC | 2023-04 03:15 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 9 | Street | On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured …On April 24, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5288-2) |
| 540-5488 | ADS | General Motors, LLC | 2023-04 00:35 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5458-1) |
| 540-5489 | ADS | General Motors, LLC | 2023-04 23:35 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Intersection | On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5459-1) |
| 540-5490 | ADS | General Motors, LLC | 2023-04 20:13 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5460-1) |
| 540-5491 | ADS | General Motors, LLC | 2023-04 21:59 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 4 | Intersection | On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5461-1) |
| 540-5492 | ADS | General Motors, LLC | 2023-04 14:58 | Mesa, AZ | 2020 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 34 | Street | On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5462-1) |
| 669-5206 v3 | ADS | Hyundai Motor America | 2023-04 15:45 | Gahanna, OH | 2023 Hyundai Santa Fe | ADAS | SUV | No Injuries Reported | 70 | Highway / Freeway | A company associate was operating the subject Santa Fe vehicle heading north on the [XXX] with the Highway Drive Assist ("HDA") feature engaged. A Nissan vehicle merged into the subject vehicle's lane and made contact wi…A company associate was operating the subject Santa Fe vehicle heading north on the [XXX] with the Highway Drive Assist ("HDA") feature engaged. A Nissan vehicle merged into the subject vehicle's lane and made contact with the driver's side of the Santa Fe resulting in a crash. The Hyundai vehicle was immobilized requiring towing assistance. No airbags allegedly deployed during the crash. A police report was filed with Gahanna Police Department and the report number is 23GAH.8195.AC. NASO is in process of retrieving the police report. 10-Day Update to 669-5206-1: No new information received. Monthly Update to 669-5206-2: According to the police report, the Santa Fe was travelling in the left lane of the road when the Nissan vehicle attempted a lane change directly into their lane of travel making contact with the Santa Fe's right side. The police report also indicated that no autonomous driving function was engaged in the Santa Fe vehicle at the time of the incident. The operator of the Nissan vehicle was cited for an unspecified charge. |
| 669-5249 v3 | Level 2 | Hyundai Motor America | 2023-04 | Springfield, NJ | 2023 Hyundai IONIQ 5 | ADAS | Other Fixed Object | No Injuries Reported | 50 | Highway / Freeway | A customer was operating the subject IONIQ 5 vehicle on [XXX] near Springfield, NJ. The Highway Drive Assist ("HDA") feature was allegedly deactivated due to an unspecified reason during driving. The vehicle struck a con…A customer was operating the subject IONIQ 5 vehicle on [XXX] near Springfield, NJ. The Highway Drive Assist ("HDA") feature was allegedly deactivated due to an unspecified reason during driving. The vehicle struck a construction barricade resulting in front passenger side damage. Damage to the right wheel in provided photos indicate the vehicle may not have been drivable post-crash. HMA is submitting this report in advance of confirming 1) the approximate time at which the ADAS became disengaged prior to the crash, and 2) if the vehicle required towing. 10-day Update to 669-5249-1: No new information. Monthly Update to 669-5249-2: Hyundai inspected the vehicle on April 19, 2023. HDA was confirmed engaged at the time of the incident. Forward Collision Warning and Avoidance systems were also confirmed operational. No abnormalities indicating a defect or malfunction of the HDA system was found. Hyundai's HDA is designed to deactivate itself upon detection of limiting environmental factors such as road curvatures or weather. Based on the incident details provided by the owner, the vehicle's HDA likely deactivated itself due to detection of the curving road. Owners are expected to be ready at all times to resume driving tasks even while HDA is engaged, as prescribed in the owner's manual and other materials detailing usage of the HDA feature. |
| 945-5351 v2 | Level 2 | Nissan North America, Inc. | 2023-04 10:30 | Myrtle Beach, SC | 2020 Nissan Rogue | ADAS | Pole / Tree | Minor | 74 | Highway / Freeway | The information contained in this report is based solely on Nissan's understanding of the allegations received during customer's discussions with Nissan Consumer Affairs representatives. Nissan has requested inspection …The information contained in this report is based solely on Nissan's understanding of the allegations received during customer's discussions with Nissan Consumer Affairs representatives. Nissan has requested inspection of the subject vehicle and will be investigating further. On April [XXX], the customer reported her daughter was driving the subject vehicle in the center lane of a 3-lane highway at a speed between 65-75 miles per hour with ICC and steering assist active. Customer reported a vehicle traveling in the right lane began to merge to the left toward the customer's vehicle. The customer reported the vehicle began to slow down and steering assist took control of the vehicle causing it to swerve back and forth from the far right lane to the far left lane until the vehicle left the road and impacted an embankment and a tree. The customer reported the tree fell onto the vehicle and her daughter sustained injuries including: concussion, abrasions to collar bone and left hip from seat belt, and chemical burns on lower back and right lower forearm from the airbags. On April 19th Nissan requested a vehicle inspection and identified this matter as a reportable incident. Customer is to coordinate with her insurer to arrange an inspection. This 10-day report supplements Report ID # 945-5351-1: On April 24th, Nissan inspected the subject vehicle. For the 2020 Rogue, the maximum amount of time that can be recorded is 5 seconds preceding and 5 seconds following an air bag deployment (event trigger). With this available data, there is no indication that ProPilot Assist was active at the time of the recorded steering inputs and resulting vehicle exit from the roadway and collision with the trees. |
| 10039-5057 v4 | Level 2 | BMW of North America, LLC | 2023-03 | Phoenix, AZ | 2022 BMW X5 M50i | ADAS | Van | Moderate | 84 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1243-5133 v2 | Level 2 | Subaru of America, Inc. | 2023-03 21:40 | Flat Top, WV | 2020 Subaru Outback | ADAS | Animal | No Injuries Reported | 70 | Highway / Freeway | The customer is not alleging any vehicle defect and had contacted Subaru to inquire whether her maintenance policy would cover the cost of necessary repairs. The subject vehicle was traveling southbound on [XXX] in WV ne…The customer is not alleging any vehicle defect and had contacted Subaru to inquire whether her maintenance policy would cover the cost of necessary repairs. The subject vehicle was traveling southbound on [XXX] in WV near [XXX] at 9:40 PM EST when it struck two animals crossing in front. The customer confirmed that Adaptive Cruise Control (ACC) and the Lane Centering Function (LCF) were both engaged at the time of the incident. The police were contacted but did not respond to the incident. The vehicle was towed from the location. The customer confirmed that there were no injuries and stated that they were very happy with the performance of the vehicle. |
| 1243-5173 v3 | Level 2 | Subaru of America, Inc. | 2023-03 16:58 | Marthasville, MO | 2021 Subaru Forester | ADAS | Unknown | Minor | 60 | Rural Road | Redacted by NHTSA as confidential business information |
| 1243-5197 v2 | Level 2 | Subaru of America, Inc. | 2023-03 16:00 | Indianapolis, IN | 2021 Subaru Crosstrek | ADAS | Other, see Narrative | No Injuries Reported | 0 | Highway / Freeway | The customer is not alleging any vehicle defect and had contacted Subaru to inquire whether Subaru would reimburse hotel costs. Based on the limited information provided by the customer, the subject vehicle was travellin…The customer is not alleging any vehicle defect and had contacted Subaru to inquire whether Subaru would reimburse hotel costs. Based on the limited information provided by the customer, the subject vehicle was travelling southbound on a highway in the greater Indianapolis area when traffic came to a sudden stop. After the subject vehicle came to a complete stop, a vehicle following behind the subject vehicle failed to stop and struck the subject vehicle in the left hand rear bumper and wheel. The customer estimated the speed of the other vehicle to be 40 MPH. During a conversation with a Subaru Customer Advocacy representative, the customer answered in the affirmative that Adaptive Cruise Control (ACC) and Lane Centering (LC) were engaged. The customer also responded affirmatively to the question "Were any vehicles (including other vehicles) towed?". This vehicle is not equipped with a telematics system. Upon the suggestion that she would need to contact her insurance company in order to provide reimbursement for a hotel stay, the customer disconnected from the conversation. |
| 1306-5170 v3 | Level 2 | Toyota Motor Engineering & Manufacturing | 2023-03 07:19 | Vega Baja, PR | 2022 Toyota Camry | ADAS | Other Fixed Object | Unknown | 67 | Highway / Freeway | On March 23, 2023, Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. On March 31, 2023, after additional analysis of the alleged incid…On March 23, 2023, Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. On March 31, 2023, after additional analysis of the alleged incident details, Toyota determined this case was reportable under the SGO. The contact record indicates that the customer alleged the following: He was on his way to work travelling east from Manai to Dorado on [XXX] with the sun in front of him, and he was looking to change lanes. He stated that the lane assist option cannot be turned off, and he had the vehicle in cruise control. He also stated that the vehicle pulled hard to the left, and he lost control. The vehicle hit a highway divider, then crossed the road to the right and hit another divider. The vehicle was airborne at some point in the crash event. No SRS deployment occurred as a result of the crash event, and the vehicle was not drivable. As a result of the crash event, he had injuries to his ribs, knee, hips, right foot, elbows, and head. Toyota completed a vehicle inspection and field report for the incident on April 14, 2023. From the field report, Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) data from the subject vehicle. VCH provides an approximately 8 second pre-crash recording, and EDR provides an approximately 5 second pre-crash recording. Based on the data obtained, the following information was observed: The driver seat belt status was OFF (unbuckled) during the recording. Lane Trace Assist (LTA) was engaged during the recording from approximately 6.35 seconds until approximately 3.6 seconds prior to the crash event, and again from approximately 2.35 to 1.15 seconds prior to the crash event. LTA was disengaged due to Lane Departure Alert (LDA) activation and sudden steering. At the time of LTA disengagement, the vehicle steering angle changed from 113 degrees (left) to approximately -95 degrees (right) before the collision with the highway divider. Dynamic Radar Cruise Control (DRCC) was engaged from approximately 6.75 seconds until 0.35 seconds prior to the crash event. No FCW or AEB activation occurred. This is a (monthly) Update Report. Please see Report 1306-5170-1 for the 1-Day Report submission. |
| 13781-4949 v2 | Level 2 | Tesla, Inc. | 2023-03 17:12 | Costa Mesa, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 59 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4952 v2 | Level 2 | Tesla, Inc. | 2023-03 05:53 | Los Angeles, CA | 2022 Tesla Model 3 | ADAS | SUV | Unknown | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4954 v2 | Level 2 | Tesla, Inc. | 2023-03 02:17 | Redwood, TX | 2023 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 52 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4956 v2 | Level 2 | Tesla, Inc. | 2023-03 18:52 | Big Pool, MD | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 47 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4957 v2 | Level 2 | Tesla, Inc. | 2023-03 17:03 | Greensboro, NC | 2021 Tesla Model Y | ADAS | Heavy Truck | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4961 v2 | Level 2 | Tesla, Inc. | 2023-03 22:08 | Fremont, CA | 2019 Tesla Model 3 | ADAS | SUV | Unknown | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4962 v2 | Level 2 | Tesla, Inc. | 2023-03 20:59 | Dixon, CA | 2021 Tesla Model Y | ADAS | SUV | Unknown | 36 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4966 v2 | Level 2 | Tesla, Inc. | 2023-03 16:09 | Redlands, CA | 2023 Tesla Model Y | ADAS | SUV | Unknown | 57 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4967 v2 | Level 2 | Tesla, Inc. | 2023-03 06:39 | Rainbow, CA | 2021 Tesla Model Y | ADAS | SUV | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4968 v2 | Level 2 | Tesla, Inc. | 2023-03 22:24 | Dearborn, MI | 2020 Tesla Model 3 | ADAS | Unknown | Unknown | 46 | Street | Redacted by NHTSA as confidential business information |
| 13781-4983 v2 | Level 2 | Tesla, Inc. | 2023-03 11:46 | Cincinnati, OH | 2020 Tesla Model Y | ADAS | Passenger Car | Unknown | 29 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4986 v2 | Level 2 | Tesla, Inc. | 2023-03 22:47 | Tracy, CA | 2022 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 29 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4987 v2 | Level 2 | Tesla, Inc. | 2023-03 23:58 | Sugar Land, TX | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 41 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4988 v2 | Level 2 | Tesla, Inc. | 2023-03 19:09 | Castle Rock, CO | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5010 v2 | Level 2 | Tesla, Inc. | 2023-03 18:02 | Woodside, CA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5011 v2 | Level 2 | Tesla, Inc. | 2023-03 19:12 | Belmont, CA | 2020 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-5012 v2 | Level 2 | Tesla, Inc. | 2023-03 12:36 | Cumming, GA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-5013 v2 | Level 2 | Tesla, Inc. | 2023-03 19:51 | Richmond Heights, FL | 2023 Tesla Model 3 | ADAS | Passenger Car | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5014 v2 | Level 2 | Tesla, Inc. | 2023-03 01:33 | Milford, TX | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 36 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5015 v2 | Level 2 | Tesla, Inc. | 2023-03 17:24 | Fremont, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5016 v2 | Level 2 | Tesla, Inc. | 2023-03 07:38 | Bremerton, WA | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 32 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5017 v2 | Level 2 | Tesla, Inc. | 2023-03 22:54 | Glendora, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5018 v2 | Level 2 | Tesla, Inc. | 2023-03 23:10 | Toppenish, WA | 2021 Tesla Model Y | ADAS | Passenger Car | Unknown | 32 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5019 v2 | Level 2 | Tesla, Inc. | 2023-03 04:59 | Quartzsite, AZ | 2020 Tesla Model 3 | ADAS | Pickup Truck | Unknown | 81 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5037 v2 | Level 2 | Tesla, Inc. | 2023-03 09:28 | Citrus Heights, CA | 2022 Tesla Model S | ADAS | Unknown | Unknown | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5038 v2 | Level 2 | Tesla, Inc. | 2023-03 01:20 | Walnut Creek, CA | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 20 | Street | Redacted by NHTSA as confidential business information |
| 13781-5039 v2 | Level 2 | Tesla, Inc. | 2023-03 10:04 | Princeton, NJ | 2023 Tesla Model Y | ADAS | SUV | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5040 v2 | Level 2 | Tesla, Inc. | 2023-03 01:40 | Monroe, WA | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 35 | Street | Redacted by NHTSA as confidential business information |
| 13781-5059 v2 | Level 2 | Tesla, Inc. | 2023-03 15:35 | Woodside, CA | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 66 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5090 v2 | Level 2 | Tesla, Inc. | 2023-03 17:54 | Mesa, AZ | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 47 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5091 v2 | Level 2 | Tesla, Inc. | 2023-03 07:48 | Denver, CO | 2020 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5097 v2 | Level 2 | Tesla, Inc. | 2023-03 13:24 | Pittsburg, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 80 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5100 v2 | Level 2 | Tesla, Inc. | 2023-03 19:35 | Hollister, NC | 2022 Tesla Model Y | ADAS | Non-Motorist: Pedestrian | Serious | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5104 v2 | Level 2 | Tesla, Inc. | 2023-03 17:30 | Morgan, PA | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 29 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5105 v2 | Level 2 | Tesla, Inc. | 2023-03 19:23 | Crawfordville, GA | 2020 Tesla Model Y | ADAS | Unknown | Unknown | 55 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5106 v2 | Level 2 | Tesla, Inc. | 2023-03 11:29 | Austin, TX | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5107 v2 | Level 2 | Tesla, Inc. | 2023-03 02:28 | South El Monte, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5108 v2 | Level 2 | Tesla, Inc. | 2023-03 11:17 | Manteca, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 45 | Street | Redacted by NHTSA as confidential business information |
| 13781-5113 v2 | Level 2 | Tesla, Inc. | 2023-03 20:27 | Trumbull, CT | 2018 Tesla Model X | ADAS | Unknown | Unknown | 31 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5115 v2 | Level 2 | Tesla, Inc. | 2023-03 21:45 | Belmont, CA | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5135 v2 | Level 2 | Tesla, Inc. | 2023-03 05:12 | San Mateo, CA | 2023 Tesla Model 3 | ADAS | Passenger Car | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5147 v2 | Level 2 | Tesla, Inc. | 2023-03 02:08 | Los Angeles, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5148 v2 | Level 2 | Tesla, Inc. | 2023-03 22:45 | Revere, MA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5149 v2 | Level 2 | Tesla, Inc. | 2023-03 22:37 | Schaumburg, IL | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 41 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5150 v2 | Level 2 | Tesla, Inc. | 2023-03 02:05 | Sandwich, MA | 2023 Tesla Model Y | ADAS | Unknown | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-5151 v2 | Level 2 | Tesla, Inc. | 2023-03 06:04 | Bethesda, MD | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 43 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5162 v2 | Level 2 | Tesla, Inc. | 2023-03 07:16 | Redding, CA | 2021 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 79 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5163 v2 | Level 2 | Tesla, Inc. | 2023-03 21:38 | Oakland Park, CA | 2018 Tesla Model X | ADAS | Unknown | Unknown | 50 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-5165 v2 | Level 2 | Tesla, Inc. | 2023-03 05:15 | Corona, CA | 2023 Tesla Model Y | ADAS | Pickup Truck | Fatality | 47 | Street | Redacted by NHTSA as confidential business information |
| 13781-5166 v2 | Level 2 | Tesla, Inc. | 2023-03 23:47 | Channahon, IL | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 62 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5167 v2 | Level 2 | Tesla, Inc. | 2023-03 08:39 | San Bernardino, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5168 v2 | Level 2 | Tesla, Inc. | 2023-03 00:38 | Rancho Cordova, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 16 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-5169 v2 | Level 2 | Tesla, Inc. | 2023-03 17:02 | Delaware Township, PA | 2021 Tesla Model 3 | ADAS | Pole / Tree | Unknown | 27 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-5664 v2 | Level 2 | Tesla, Inc. | 2023-03 | Prince George's, MD | 2018 Tesla Model S | ADAS | Pole / Tree | Minor | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30270-5114 v2 | ADS | Waymo LLC | 2023-03 20:04 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | Street | The content of this report is unchanged from the initial report submitted on March 21, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On March [XXX], 2023 at approximately 8:04 PM PST a Waymo Autonomous…The content of this report is unchanged from the initial report submitted on March 21, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On March [XXX], 2023 at approximately 8:04 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pothole on [XXX] near [XXX]. The Waymo AV was traveling in the second lane on a four-lane section of northbound [XXX] when the passenger side rear tire made contact with a pothole. The tire began to deflate and the Waymo AV pulled over on a side street. At the time of impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5318 | ADS | Waymo LLC | 2023-03 20:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 2 | Parking Lot | On March [XXX], 2023 at 8:27 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco was in a collision involving a fixed object on [XXX] near [XXX]. As the Waymo AV was leaving a parking lot to turn left…On March [XXX], 2023 at 8:27 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco was in a collision involving a fixed object on [XXX] near [XXX]. As the Waymo AV was leaving a parking lot to turn left onto [XXX], the front of the Waymo AV made contact with a chain that was connected between a parking lot road sign and a temporary pole. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The road sign fell down due to tension on the chain. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5319 | ADS | Waymo LLC | 2023-03 12:03 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On March [XXX], 2023 at 12:03 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling southbound …On March [XXX], 2023 at 12:03 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling southbound on [XXX] when it approached a heavy truck and trailer that was positioning to reverse perpendicularly across [XXX] to back into an adjacent driveway. The Waymo AV stopped and the truck and trailer began reversing across [XXX]. The rear passengers side corner of the truck then made contact with the front drivers side corner of the stationary Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5320 | ADS | Waymo LLC | 2023-03 21:28 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 9:28 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 stopped in the dedicated l…On March [XXX], 2023 at 9:28 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 stopped in the dedicated left turn lane facing west on [XXX], awaiting a green signal to turn onto [XXX]. The signal for traffic proceeding west on [XXX] turned green, and traffic in adjacent lanes began moving. The left turn arrow signal for the dedicated turn lane occupied by the Waymo AV remained red. The passenger car that had been stopped directly behind the Waymo AV began moving forward. The front of the passenger car 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 passenger car sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5322 | ADS | Waymo LLC | 2023-03 2:19 | San Bruno, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 64 | Highway / Freeway | On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was travelin…On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was traveling south on [XXX] in the rightmost exit lane for [XXX] towards [XXX] when it made contact with road debris (tire scrap). At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5323 | ADS | Waymo LLC | 2023-03 17:10 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 8 | Intersection | On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling …On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] in autonomous mode, merging into the rightmost lane. As the Waymo AV merged, the test driver transitioned from autonomous mode to manual mode and began accelerating. The front of the Waymo AV made contact with the rear of a passenger car that was stopped in the rightmost lane. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both the Waymo AV and the passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5324 | ADS | Waymo LLC | 2023-03 19:00 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 1 | Street | On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] b…On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] behind traffic that was backed up from the intersection with [XXX]. As the Waymo AV was accelerating from a stop, a passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV test driver reported having a minor injury and the passenger vehicle left the scene. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5325 | ADS | Waymo LLC | 2023-03 10:43 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a thre…On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a three-lane road behind a passenger vehicle for a red light facing southwest on [XXX] at [XXX] in autonomous mode. The light turned green while cross-traffic remained backed up in the intersection. The Waymo AV nudged forward and slowed to a stop, yielding for the blocking cross traffic. An SUV that had been stopped behind the Waymo AV proceeded forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5326 | ADS | Waymo LLC | 2023-03 13:35 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 2 | Intersection | On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode from…On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode from westbound [XXX] onto northbound [XXX], the Waymo AV was yielding to traffic approaching from the left. As the Waymo AV attempted to proceed, the test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car behind the Waymo AV proceeded forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV and the passenger vehicle sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30412-4960 v2 | ADS | Cruise LLC | 2023-03 01:06 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-4996 v2 | ADS | Cruise LLC | 2023-03 13:01 | Tempe, AZ | 2023 Cruise AV | ADS | Passenger Car | Minor | 6 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5101 v2 | ADS | Cruise LLC | 2023-03 3:26 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 21 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5136 v2 | ADS | Cruise LLC | 2023-03 04:29 | San Francisco, CA | 2022 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 15 | Street | 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. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. The themed reading of the driverless narratives is on the reports page.