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
36 reports, showing 1 to 36.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-11016 v2 | ADS | Waymo LLC | 2025-06 07:50 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Non-Motorist: Other | Moderate | 0 | Street | This report includes removal of a reference to the Waymo AV sustaining damage (upon further inspection, the Waymo AV was not damaged) and an update reflecting an alleged injury that Waymo received notice of on June 10, 2…This report includes removal of a reference to the Waymo AV sustaining damage (upon further inspection, the Waymo AV was not damaged) and an update reflecting an alleged injury that Waymo received notice of on June 10, 2025. The remaining content of this report is unchanged from the initial report submitted on June 5, 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On June [XXX], 2025 at 7:50 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a scooterist on [XXX] at [XXX]. The Waymo AV was traveling northbound in the rightmost lane on [XXX] and came to a stop in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, the passenger in the Waymo AV opened the rear passenger side door. A scooterist traveling northbound on [XXX] proceeded to pass to the right of the Waymo AV, and the scooterist made contact with the open rear passenger door of the stationary Waymo AV. The passenger was not belted at the time of the collision, as the passenger was preparing to exit the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. There was an allegation of damage to the scooter. 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. | |
| 30270-9860 v2 | ADS | Waymo LLC | 2025-02 21:56 | Los Angeles, CA | 2024 Jaguar I-Pace | ADS | SUV | Moderate | 20 | Street | Other than updating the highest injury severity alleged from "unknown" to "moderate", the content of this report is unchanged from the initial report submitted on February [XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL …Other than updating the highest injury severity alleged from "unknown" to "moderate", the content of this report is unchanged from the initial report submitted on February [XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2025 at 9:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX]. The Waymo AV was traveling southwest in the rightmost lane of [XXX]with its right turn signal activated, preparing to proceed into an upcoming dedicated right turn lane prior to the intersection with [XXX] While the Waymo AV proceeded into the right turn lane, an SUV traveling in the rightmost lane approached the Waymo AV from behind, 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. The SUV left the scene and reportedly was involved in a subsequent collision approximately one block away. Both the Waymo AV and the SUV sustained damage, and three passengers in the Waymo AV were transported to a hospital for medical treatment. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved 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. | |
| 30270-9987 v2 | ADS | Waymo LLC | 2025-02 12:10 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | Non-Motorist: Cyclist | Moderate | 0 | Street | Other than an update to the highest injury severity alleged from "minor" to "moderate" and an update to reflect that property damage did result from the collision, the content of this report is unchanged from the initial…Other than an update to the highest injury severity alleged from "minor" to "moderate" and an update to reflect that property damage did result from the collision, the content of this report is unchanged from the initial report submitted on February [XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2025 at 12:10 PM PT two Waymo Autonomous Vehicles ("Waymo AVs") operating in San Francisco, CA were involved in a collision involving a cyclist on [XXX]. The first Waymo AV was parked at the northwest-bound curb on [XXX]for passenger dropoff. A second Waymo AV (2024 Jaguar I-PACE SADHW2S17R1[XXX], 38,609 miles) was also parked for a separate passenger dropoff, located adjacent to the first Waymo AV with the bicycle lane of northwest-bound [XXX] between the two Waymo AVs. A bicyclist was traveling northwest-bound on [XXX] and approaching the two Waymo AVs from the rear. As the cyclist was passing between the two Waymo AVs, the rear driver side passenger of the first Waymo AV opened the door of the first Waymo AV into the cyclist. The cyclist then fell into the passenger side of the second Waymo AV. At the time of the impact, both Waymo AVs' Level 4 ADS were engaged in autonomous mode. Neither Waymo AV sustained damage. The cyclist was able to move out of the roadway independently and was then transported from the scene in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved 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. | |
| 30270-9992 v2 | ADS | Waymo LLC | 2025-02 13:39 | Phoenix, AZ | 2024 Jaquar I-PACE | ADS | Passenger Car | Moderate | 0 | Intersection | The content of this report is unchanged from the initial report submitted on February [XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2025 at 1:39 PM MT a Waymo Autonomous Vehic…The content of this report is unchanged from the initial report submitted on February [XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2025 at 1:39 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] in the dedicated left turn lane preparing to make an unprotected left turn onto [XXX] when it came to a stop behind a passenger car also waiting to make an unprotected left turn. While the Waymo AV remained stopped, the passenger car proceeded to make an unprotected left turn onto [XXX], crossing in front of an oncoming SUV traveling west on [XXX]. The passenger car was struck on its passenger side by the oncoming SUV, causing the passenger car to rotate counter-clockwise. After impact, the passenger car then continued turning left, circling back towards the Waymo AV. The front passenger side of the passenger car then made contact with the front driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the Waymo AV and the driver of the passenger car were transported to the hospital from the scene in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved 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. | |
| 30270-9634 | ADS | Waymo LLC | 2025-01 16:04 | Phoenix, AZ | 2024 JLR I-PACE | ADS | Passenger Car | Moderate | 2 | Intersection | On January [XXX], 2025 at 4:04 PM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling in the rightmost lane o…On January [XXX], 2025 at 4:04 PM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling in the rightmost lane of northbound [XXX] when it entered the dedicated right turn lane as it approached the intersection with [XXX]. The Waymo AV slowed to a stop to yield to traffic traveling east on [XXX] as it prepared to make a right turn onto [XXX]. As the Waymo AV initiated a right turn onto eastbound [XXX], a passenger car traveling directly behind the Waymo AV approached the Waymo AV from behind. The front passenger side of the passenger car made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The passenger in the Waymo AV reported a moderate injury. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-0 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-9476 v2 | ADS | Waymo LLC | 2024-12 20:28 | Los Angeles, CA | 2021 Jaguar I-PACE | ADS | SUV | Moderate | 0 | Intersection | Since the initial report [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] was submitted on December 21, 2024, the content of the report has been clarified with changes pertaining to the other vehicles involved a…Since the initial report [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] was submitted on December 21, 2024, the content of the report has been clarified with changes pertaining to the other vehicles involved and the Waymo Autonomous Vehicles autonomy state at the time of the collision. On December [XXX], 2024 at 8:28 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, CA was in a collision involving two SUVs, a passenger car, and a pick up truck on [XXX] at [XXX]. The Waymo AV was stopped in autonomous mode facing south at a red light as the lead vehicle in the second from the right lane when an SUV traveling northbound in an oncoming traffic lane ran the red light. As the oncoming SUV entered the intersection, it made contact with a passenger car traveling east on [XXX]. The oncoming SUV continued through the intersection and swerved to narrowly miss a pedestrian before making contact with the front of the Waymo AV and the front driver side of a stationary pickup truck to the right of the Waymo AV. The impact from the oncoming SUV caused the Waymo AV to contact another SUV that was also stationary to the left of the Waymo AV at the red traffic light. The Waymo AV test driver transitioned to manual mode immediately before the oncoming SUV made contact. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage to the front and rear of the vehicle, necessitating a tow from the scene. The oncoming SUV sustained damage to the front and driver side. The stationary SUV that was contacted sustained damage to the passenger side. The Waymo test driver was transported to a local hospital for medical treatment. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, a vehicle involved was towed away, and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-9597 | ADS | Waymo LLC | 2024-12 17:48 | Atlanta, GA | 2024 JLR I-PACE | ADS | Other, see Narrative | Moderate | 8 | Street | On December [XXX], 2024 at 5:48 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia made contact with the pavement at the elevated entrance to [XXX]. near [XXX]. The Waymo AV was traveling south…On December [XXX], 2024 at 5:48 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia made contact with the pavement at the elevated entrance to [XXX]. near [XXX]. The Waymo AV was traveling south on [XXX] when it approached [XXX] ahead on its left. As the Waymo AV turned left onto [XXX], the Waymo AV's undercarriage made contact with the raised pavement of the side walk where [XXX] meets [XXX]. 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 test driver in the Waymo AV reported a moderate injury. 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. | |
| 30531-9520 | ADS | Transdev Alternative Services | 2024-12 20:28 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | SUV | Moderate | 0 | Intersection | Since the initial report [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] was submitted on December 21, 2024, the content of the report has been clarified with changes pertaining to the other vehicles involved a…Since the initial report [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] was submitted on December 21, 2024, the content of the report has been clarified with changes pertaining to the other vehicles involved and the Waymo Autonomous Vehicle's autonomy state at the time of the collision. On December [XXX], 2024 at 8:28 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, CA was in a collision involving two SUV's, a passenger car, and a pick up truck on [XXX] at [XXX]. The Waymo AV was stopped in autonomous mode facing south at a red light as the lead vehicle in the second from the right lane when an SUV traveling northbound in an oncoming traffic lane ran the red light. As the oncoming SUV entered the intersection, it made contact with a passenger car traveling east on [XXX]. The oncoming SUV continued through the intersection and swerved to narrowly miss a pedestrian before making contact with the front of the Waymo AV and the front driver side of a stationary pickup truck to the right of the Waymo AV. The impact from the oncoming SUV caused the Waymo AV to contact another SUV that was also stationary to the left of the Wayo AV at the red traffic light. The Waymo AV test driver transitioned to manual mode immediately before the oncoming SUV made contact. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage to the front and rear of the vehicle, necessitating a tow from the scene. The oncoming SUV sustained damage to the front and driver side. The stationary SUV that was contacted sustained damage to the passenger side. The Waymo test driver was transported to a local hospital for medical treatment. Transdev Alternative Services is reporting this crash under Request no. 1 of Standing General order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, a vehicle involved was towed away, and because of airbag deployment. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA Report ID: 30270-9476-2. | |
| 30531-9697 | ADS | Transdev Alternative Services | 2024-12 17:48 | Atlanta, GA | 2024 JLR I-PACE | ADS | Other, see Narrative | Moderate | 8 | Street | On December [XXX], 2024 at 5:48 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia made contact with the pavement at the elevated entrance to [XXX] near [XXX]. The Waymo AV was traveling south on…On December [XXX], 2024 at 5:48 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia made contact with the pavement at the elevated entrance to [XXX] near [XXX]. The Waymo AV was traveling south on [XXX] when it approached [XXX] ahead on its left. As the Waymo AV turned left onto [XXX], the Waymo AV's undercarriage made contact with the raised pavement of the side walk where [XXX] meets [XXX]. 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 test driver in the Waymo AV reported a moderate injury. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA Report ID 30270-9597-1. | |
| 30270-9081 v2 | ADS | Waymo LLC | 2024-11 08:50 | Phoenix, AZ | 2024 Jaguar I-Pace | ADS | Pickup Truck | Moderate | 0 | Intersection | Waymo received notice that passengers in the Waymo AV alleged injuries of varying severity. One passenger alleged to have sustained a moderate injury, while the other passenger alleged an injury of unspecified severity. …Waymo received notice that passengers in the Waymo AV alleged injuries of varying severity. One passenger alleged to have sustained a moderate injury, while the other passenger alleged an injury of unspecified severity. This report is being submitted as an update to the initial report submitted on November 12, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. Otherwise, the content of this report is unchanged. On November [XXX], 2024 at 8:50 AM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XX]. The Waymo AV was stopped for a red light in the leftmost northbound lane of [XXX], preparing to make a U-turn at the intersection with [XXX]. While the Waymo AV remained stopped, a pickup truck traveling at a high rate of speed approached the Waymo AV from behind. The front driver side of the pickup truck made contact with the rear passenger side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30412-9268 | ADS | Cruise LLC | 2024-11 09:10 | Houston, TX | 2023 Cruise AV | ADS | Heavy Truck | Moderate | 0 | Intersection | On November [XXX], 2024, at 9:10am CST, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode in Houston, Texas was traveling westbound on [XXX] between [XXX] and [XXX]. The AV came to a complete sto…On November [XXX], 2024, at 9:10am CST, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode in Houston, Texas was traveling westbound on [XXX] between [XXX] and [XXX]. The AV came to a complete stop behind a semi-trailer truck stopped at a traffic signal at the intersection with [XXX]. The semi-trailer truck reversed into the AV, making contact with the front of the AV twice. Prior to contact, the AV operator honked the horn to attempt to alert the truck driver After contact, the AV operator got out of the car to attempt to flag down the truck driver. However, the driver of the semi-trailer truck left the scene without exchanging information. The impact resulted in damage to the front end of the AV. The AV was driven away from the scene, and a police report was filed to document the incident. The AV operator later reported moderate injuries. | |
| 540-9365 | ADS | General Motors, LLC | 2024-11 09:10 | Houston, TX | 2023 Cruise AV | ADS | Heavy Truck | Moderate | 0 | Intersection | On December 13, 2024, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On December 13, 2024, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-9268-1). | |
| 30410-8493 v2 | ADS | Motional | 2024-09 13:00 | Las Vegas, NV | 2024 Hyundai Ioniq 5 | ADS | Passenger Car | Moderate | 0 | Intersection | A Motional AV with VIN PFDKB4AE6RF[XXX] was operating in autonomous mode in Las Vegas, Nevada at approximately 1 PM PT, with a safety driver at the wheel, an engineer in the front passenger seat, and two other employees …A Motional AV with VIN PFDKB4AE6RF[XXX] was operating in autonomous mode in Las Vegas, Nevada at approximately 1 PM PT, with a safety driver at the wheel, an engineer in the front passenger seat, and two other employees in the rear seats. The AV was in a right-turn only lane, turning onto [XXX] from [XXX]. The AV stopped at a yield sign in the right-turn only lane before merging onto [XXX], and a silver Toyota rear-ended the stopped AV at approximately 15 MPH. There were three occupants of the silver Toyota, one in the front seat and two in the back, with one verbally reporting an injury to the face area. An ambulance was traveling on [XXX] at the time of the incident and stopped at the scene. The ambulance transported the affected occupant of the silver Toyota, and another occupant (believed to be the individuals sister) rode in the ambulance. It is unknown where these individuals were taken. Two minor injuries were later reported from the occupants in the AV, and both have returned to work. . Both vehicles were damaged and required towing from the scene. No airbags were deployed in either vehicle. Las Vegas Metro Police were called to the scene. It is unknown if the other driver was cited. A police report will be supplied when available. | |
| 669-8496 v2 | ADS | Hyundai Motor America | 2024-09 13:00 | Las Vegas, NV | 2024 Hyundai IONIQ 5 | ADS | Passenger Car | Moderate | 0 | Intersection | In conjunction with Motional's filing of the subject incident, and according to statement(s) provided in Motional's incident report: A Motional AV with VIN PFDKB4AE6RF[XXX] was operating in autonomous mode in Las Vegas, …In conjunction with Motional's filing of the subject incident, and according to statement(s) provided in Motional's incident report: A Motional AV with VIN PFDKB4AE6RF[XXX] was operating in autonomous mode in Las Vegas, Nevada at approximately 1PM PT, with a safety driver at the wheel, an engineer in the front passenger seat, and two other employees in the rear seats. The AV was in a right-turn lane, turning onto [XXX] from [XXX]. The AV stopped at a yield sign in the right-turn only lane before merging onto [XXX] and a silver Toyota rear-ended the AV at approximately 15 MPH. There were three occupants of the silver Toyota, one in the front seat and two in the back, with one verbally reporting an injury to the face area. An ambulance was traveling on [XXX]. at the time of the incident and stopped at the scene. The ambulance transported the complaining occupant of the silver Toyota and another occupant (believed to the individual's sister) rode in the ambulance. It is unknown where these individuals were taken. No injuries were reported from the occupants in the AV. Both vehicles were damaged and required towing from the scene. No airbags were deployed in either vehicle. Las Vegas Metro Police were called to the scene. It is unknown if the other driver was cited. A police report will be supplied when available. 9/16/2024 Update: No new information available at this time. | |
| 30270-8343 v2 | ADS | Waymo LLC | 2024-08 10:03 | Scottsdale, AZ | 2021 Jaguar I-Pace | ADS | SUV | Moderate | 0 | Street | The content of this report is unchanged from the initial report submitted on August 13, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2024 at 10:03 AM MT a Waymo Autonomous Vehicle (Wa…The content of this report is unchanged from the initial report submitted on August 13, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2024 at 10:03 AM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the leftmost lane on northbound [XXX] when it detected a large shrub in its lane. The Waymo AV test driver transitioned to manual mode and braked to a stop in front of the shrub. Moments later, an SUV approached the stopped Waymo AV from behind and began to slow. As the SUV was slowing, another SUV behind the first SUV made contact with the rear of the first SUV. The front of the first SUV then 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. All vehicles sustained damage and Waymo received notice that a passenger in the second SUV may have sustained a moderate injury. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, a vehicle involved was towed away, and airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30531-8345 v2 | ADS | Transdev Alternative Services | 2024-08 10:03 | Scottsdale, AZ | 2021 Jaguar I-Pace | ADS | SUV | Moderate | 0 | Street | The content of this report is unchanged from the initial report submitted on August 13, 2024. On August [XXX], 2024 at 10:03 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collisi…The content of this report is unchanged from the initial report submitted on August 13, 2024. On August [XXX], 2024 at 10:03 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the leftmost lane on northbound [XXX] when it detected a large shrub in its lane. The Waymo AV test driver transitioned to manual mode and braked to a stop in front of the shrub. Moments later, an SUV approached the stopped Waymo AV from behind and began to slow. As the SUV was slowing, another SUV behind the first SUV made contact with the rear of the first SUV. The front of the first 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 not engaged and a test driver was operating the Waymo AV in manual mode. All vehicles sustained damage and Waymo received notice that a passenger in the second SUV may have sustained a moderate injury. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, a vehicle involved was towed away, and airbag deployment. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30270-8343-1. | |
| 30270-7959 | ADS | Waymo LLC | 2024-06 23:31 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Passenger Car | Moderate | 1 | Intersection | On June [XXX], 2024 at 11:31 PM PT 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 south on [XXX]…On June [XXX], 2024 at 11:31 PM PT 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 south on [XXX] and stopped at a stop sign at [XXX]. After the stop as the Waymo AV started to enter the intersection, a passenger car traveling behind the Waymo AV 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. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30412-7840 v2 | ADS | Cruise LLC | 2024-06 04:55 | Phoenix, AZ | 2023 Cruise AV | ADS | Passenger Car | Moderate | 0 | Street | Cruise submits this updated report to add that the driver of the Chrysler PT Cruiser later claimed injuries related to the event. There are no other changes to Cruise's previous submission. On June [XXX], 2024 at 4:55AM …Cruise submits this updated report to add that the driver of the Chrysler PT Cruiser later claimed injuries related to the event. There are no other changes to Cruise's previous submission. On June [XXX], 2024 at 4:55AM MT, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode with three Cruise AV test operators onboard was traveling southbound on [XXX] in [XXX], Arizona when it approached a red light at the intersection with [XXX]. As the AV was stopping at the red light, a Chrysler PT Cruiser approached the AV from the rear but failed to stop and struck the rear of the nearly-stopped AV, causing severe damage to the Cruise AV and damage to the Chrysler PT Cruiser. The impact of the collision pushed the AV into the center of the intersection before the pair came to a stop. Police and Emergency Medical Services (EMS) were called and came to the scene. The three Cruise AV test operators reported minor injuries. No parties were transported to the hospital from the scene of the collision, but the three AVTOs were later examined at a health care facility. The Cruise AV was towed from the scene. | |
| 540-7876 v2 | ADS | General Motors, LLC | 2024-06 04:55 | Phoenix, AZ | 2023 Cruise AV | ADS | Passenger Car | Moderate | 0 | Street | On July 12, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manuf…On July 12, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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. [XXX] | |
| 30270-7733 v2 | ADS | Waymo LLC | 2024-05 11:02 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | SUV | Moderate | 19 | Intersection | On May 24, 2024, Waymo received notice that passengers in the other involved vehicle alleged moderate injuries. This report is being submitted as an update to the initial report submitted on May 17, 2024 [REDACTED, MAY C…On May 24, 2024, Waymo received notice that passengers in the other involved vehicle alleged moderate injuries. This report is being submitted as an update to the initial report submitted on May 17, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. Otherwise, the content of this report is unchanged. On May [XXX], 2024 at 11:02 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] in the far right lane approaching the intersection with [XXX]. An SUV in the lane directly to the left of and adjacent to the Waymo AV passed and overtook the Waymo AV on the left, then initiated a right turn onto [XXX], crossing in front of the Waymo AV. The passenger side of the SUV made contact with the front driver side corner of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode.Both vehicles sustained damage. Waymo is reporting this crash under Request No. 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. | |
| 753-7780 v2 | ADS | Kia America, Inc. | 2024-04 02:50 | ST. CLAIR TOWNSHIP, MI | 2023 KIA SPORTAGE | ADAS | Passenger Car | Moderate | 55 | Street | **1-Day Incident Report 5/25/2024** Customer contacted Kia Customer Care (KCC) to report an incident involving his 2023MY Kia Sportage. Specifically, the customer called to thank Kia "for saving [REDACTED, MAY CONTAIN CO…**1-Day Incident Report 5/25/2024** Customer contacted Kia Customer Care (KCC) to report an incident involving his 2023MY Kia Sportage. Specifically, the customer called to thank Kia "for saving [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] life." Customer explained he was in a head-on collision when a drunk driver suddenly veered into his lane. Customer reported he suffered "cuts, bumps & bruises" and stated he "believes that [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] lack of injuries is due to the plethora of safety features my Sportage had." KCC subsequently contacted the customer to obtain additional details regarding the incident. Customer stated that he was driving on a two-lane highway around 3AM, with cruise control engaged, when the car he was following veered into a ditch and a drunk driver veered into his lane. Customer did not see the drunk driver until the last second and as a result did not have time react. When asked by KCC, the customer responded that Highway Driving Assist (HDA) was not engaged, but that his Smart Cruise Control and Lane Following Assist were engaged at the time of the incident. The customer reported that the Sportage's airbags deployed, both the customer and driver of the other vehicle (unclear if the drunk driver or the driver of the vehicle that veered into the ditch) were transported to the hospital and that the Sportage was towed. Customer stated he was not asking anything from Kia and that he had called only to share his appreciation. This incident is being reported as precautionary measure since the incident meets the requirements under the SGO. However, based on the description of the incident provided by the customer, the incident was not caused by a failure and/or disengagement of smart cruise control and/or LFA. **10-Day Update 6/3/2024** No additional information to be provided as the 1-Day was reported as a precautionary measure and submitting this 10-Day Update per the reporting requirements under the SGO. | |
| 30412-6528 v2 | ADS | Cruise LLC | 2023-10 19:32 | San Francisco, CA | 2023 Cruise AV | ADS | Motorcycle | Moderate | 2 | Street | Redacted by NHTSA as confidential business information | |
| 540-6530 v2 | ADS | General Motors, LLC | 2023-10 19:32 | San Francisco, CA | 2023 Cruise AV | ADS | Motorcycle | Moderate | 2 | Street | On October 26, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (…On October 26, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6528-1). | |
| 30412-6159 v2 | ADS | Cruise LLC | 2023-08 00:19 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Moderate | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6175 v2 | ADS | Cruise LLC | 2023-08 01:42 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Pedestrian | Moderate | 1 | Intersection | Redacted by NHTSA as confidential business information | |
| 540-6162 v2 | ADS | General Motors, LLC | 2023-08 00:19 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Moderate | 0 | Intersection | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) m…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6159-2) | |
| 540-6178 v2 | ADS | General Motors, LLC | 2023-08 01:42 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Pedestrian | Moderate | 1 | Intersection | On September 5, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (…On September 5, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6175-2). | |
| 30270-5650 v2 | ADS | Waymo LLC | 2023-06 13:17 | Phoenix, AZ | 2021 Jaguar I-PACE | ADS | Passenger Car | Moderate | 13 | Highway / Freeway | After submitting the previous 1-Day report on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], Waymo received notice that the test driver was not transported from the scene to the hospital for medic…After submitting the previous 1-Day report on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], Waymo received notice that the test driver was not transported from the scene to the hospital for medical treatment, but did seek medical treatment at a hospital at a later time. As such, this event could have qualified for a 5-Day report. The narrative below has been updated to reflect this information. This updated report also now lists the Highest Injury Severity Alleged as moderate, and Transdev Alternative Services as an entity that may be aware of this incident. On [XXX], 2023 at 1:17 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, AZ was in a collision involving a passenger car on [XXX] in the southbound direction near the [XXX]. The Waymo AV was traveling in the rightmost lane (out of 5 lanes) in the southbound direction of [XXX], and the left 3 lanes were closed due to a work zone. The vehicle traveling ahead in the same lane as the ADV made an abrupt lane change to the left, revealing a stack of slow-moving vehicles in the Waymo AVs lane. The test driver of the Waymo AV took manual control of the vehicle and started to decelerate and steer toward the right shoulder in response to slow traffic ahead. A passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver (in the drivers seating position) was operating the Waymo AV in manual mode. The Waymo AV and the other vehicle sustained damage. The test driver reported an injury, for which they later sought medical treatment. Waymo reported this crash under Request No. 1 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30792-5747 | ADS | WeRide Corp | 2023-06 14:06 | san jose, CA | 2019 NISSAN LEAF | ADS | Heavy Truck | Moderate | 0 | Street | At 2:06pm a WeRide driverless vehicle (car 1) was stopped behind a big rig truck (vehicle 2). As our vehicle (car 1) was stopped behind the big rig truck, the big rig truck proceeded to reverse backwards and eventually c…At 2:06pm a WeRide driverless vehicle (car 1) was stopped behind a big rig truck (vehicle 2). As our vehicle (car 1) was stopped behind the big rig truck, the big rig truck proceeded to reverse backwards and eventually collided into the WeRide vehicle (car 1). Both parties pulled over both involved vehicles and cooperated to exchange information. The damage sustained to the WeRide vehicle was moderate and the big rig truck did not have any damage. | |
| 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. | |
| 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. | |
| 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) | |
| 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 | |
| 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.] | |
| 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 | |
| 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). |
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.