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 6501 to 6600.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-6385 v2 | ADS | Waymo LLC | 2023-10 17:47 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | Other than correcting the Pre-Crash Speed of the Waymo AV, the content of this report is unchanged from the initial report submitted on October 2, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On Octob…Other than correcting the Pre-Crash Speed of the Waymo AV, the content of this report is unchanged from the initial report submitted on October 2, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2023 at 5:47 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX] and [XXX]. The Waymo AV was traveling westbound on [XXX] near [XXX]. The Waymo AV then began to turn right from [XXX] into a parking lot at [XXX]. As the Waymo AV began to enter the parking lot, it stopped for an approaching skateboarder. The passenger car traveling 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 vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user influenced the driving task of a vehicle involved. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-6529 v2 | ADS | Waymo LLC | 2023-10 9:24 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 13 | Intersection | The content of this report is unchanged from the initial report submitted on October 18, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle (W…The content of this report is unchanged from the initial report submitted on October 18, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode on eastbound [XXX] preparing to make a right turn onto southbound [XXX] and had stopped to yield, first for pedestrians to cross [XXX] and then for a cyclist approaching from behind traveling eastbound on the sidewalk of [XXX]. As the pedestrians finished crossing [XXX] but before the cyclist had reached [XXX], the Waymo AV test driver took manual control of the Waymo AV and began to accelerate and perform the right turn onto [XXX]. After the Waymo AV entered the crosswalk, the cyclist entered the crosswalk and made contact with the passengers rear quarter panel of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. 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-6542 | ADS | Waymo LLC | 2023-10 08:59 | Scottsdale, AZ | 2023 Jaguar I-Pace | ADS | Other, see Narrative | Unknown | 6 | Street | On October [XXX], 2023 at 8:59 AM PT a collision occurred in Scottsdale, Arizona involving two passenger vehicles traveling behind a Waymo Autonomous Vehicle (Waymo AV) on [XXX] near [XXX]. The Waymo AV was traveling nor…On October [XXX], 2023 at 8:59 AM PT a collision occurred in Scottsdale, Arizona involving two passenger vehicles traveling behind a Waymo Autonomous Vehicle (Waymo AV) on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the far left lane, with an SUV approaching from behind in the adjacent right lane, when the Waymo AV detected fallen tree branches in the left adjacent median, partially obstructing its own lane. As the Waymo AV approached and passed the tree branches, and as the SUV passed the Waymo AV, the Waymo AV braked. The passenger vehicle behind the Waymo AV was then impacted by the passenger vehicle traveling behind it. At the time of the impact between the two passenger vehicles, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The two passenger vehicles sustained damage, but the Waymo AV did not. Waymo became aware of the collision on October 19, 2023 during an internal review process. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because video appears to show that airbags deployed in the striking vehicle. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-6548 | ADS | Waymo LLC | 2023-10 18:53 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 8 | Street | On October [XXX], 2023 at 6:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona experienced underbody damage in a construction zone on [XXX] near [XXX]. The Waymo AV was traveling through a const…On October [XXX], 2023 at 6:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona experienced underbody damage in a construction zone on [XXX] near [XXX]. The Waymo AV was traveling through a construction zone on eastbound [XXX] and prepared to make a left turn onto northbound [XXX]. The Waymo AV entered a lane undergoing construction on [XXX], encountered a section of roadway that had been removed, and the front drivers side wheel dropped off the paved roadway. At the time of the event, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-6561 | ADS | Waymo LLC | 2023-10 13:29 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 19 | Street | On October [XXX], 2023 at 1:29 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving an automatic gate in a parking lot driveway at Central High School. The Waymo AV exit…On October [XXX], 2023 at 1:29 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving an automatic gate in a parking lot driveway at Central High School. The Waymo AV exited a parking lot at Central High School and was traveling eastbound toward [XXX], when the passengers side sensors and side mirror made contact with an automatic gate that was in the process of closing. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-6566 | ADS | Waymo LLC | 2023-10 19:18 | Chandler, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 50 | Street | On October [XXX], 2023 at 7:18 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XX…On October [XXX], 2023 at 7:18 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the far left lane. As it passed [XXX], it detected a passenger vehicle approaching from behind and traveling at a higher rate of speed. The Waymo AV briefly accelerated because it recognized the speed of the vehicle approaching from behind, but the passenger vehicle 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 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. |
| 30270-6661 | ADS | Waymo LLC | 2023-10 08:03 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On October [XXX], 2023 at 8:03 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding north on [XXX]…On October [XXX], 2023 at 8:03 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding north on [XXX] in the rightmost lane when it came to a stop at the intersection with [XXX] as a result of a stop sign that had been leaned against a barrier near the corner of the intersection and was visible from the roadway. The front of the pickup truck traveling behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-6662 | ADS | Waymo LLC | 2023-10 17:42 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On October [XXX], 2023 at 5:42 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 came to a stop in the rightmo…On October [XXX], 2023 at 5:42 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 came to a stop in the rightmost travel lane heading south on [XXX] at [XXX], behind a van that was unloading passengers and cargo in the travel lane. As the Waymo AV was awaiting an opportunity to maneuver into the left lane to pass the van, the passenger car behind the Waymo AV maneuvered into the left lane to pass both vehicles. As the passenger car passed the Waymo AV, the drivers side of the passenger car made contact with the rear left corner 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. 2 of Standing General Order 2021-01. |
| 30270-6663 | ADS | Waymo LLC | 2023-10 16:10 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Street | On October [XXX], 2023 at 4:10 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger car on [XXX] at [XXX]. As the Waymo AV was traveling northeast on [XXX] …On October [XXX], 2023 at 4:10 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger car on [XXX] at [XXX]. As the Waymo AV was traveling northeast on [XXX] approaching the intersection with [XXX], it began passing a passenger car that was stopped on the other half of the roadway with its front partially in a perpendicular parking space and the rest of the vehicle perpendicular across part of the travel lane. While the Waymo AV was passing the passenger car, the passenger car initiated a reversing maneuver into the lane where the Waymo AV was passing, and the rear right corner of the passenger car made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-6664 | ADS | Waymo LLC | 2023-10 18:02 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Parking Lot | On October [XXX], 2023 at 6:02 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a shuttle van in a parking lot at [XXX]. The Waymo AV was stopped in the parking lot …On October [XXX], 2023 at 6:02 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a shuttle van in a parking lot at [XXX]. The Waymo AV was stopped in the parking lot at [XXX] when a shuttle van passed the Waymo AV. As the van was passing behind the Waymo AV, the right side of the van made contact with the rear left corner of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-6665 | ADS | Waymo LLC | 2023-10 07:48 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 23 | Intersection | On October [XXX], 2023 at 7:48 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in…On October [XXX], 2023 at 7:48 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in the rightmost lane. As the SUV in the left adjacent lane traveling alongside the Waymo AV initiated a right lane change, the front passengers side of the SUV made contact with the front drivers side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged as the test driver transitioned the Waymo AV to manual mode just before the contact. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-6666 | ADS | Waymo LLC | 2023-10 17:14 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Street | On October [XXX], 2023 at 5:14 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX] The Waymo AV had stopped for a drop-off on northbo…On October [XXX], 2023 at 5:14 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX] The Waymo AV had stopped for a drop-off on northbound [XXX] and yielded to a van traveling south on [XXX] after the passengers had exited. The van attempted to slowly pass the Waymo AV, and as it did so, the rear drivers side tire and rear bumper of the van made contact with the front drivers side tire of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The van sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-6667 | ADS | Waymo LLC | 2023-10 03:11 | San Francisco, CA | 2023 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Street | On October [XXX], 2023 at 3:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling slowly (less than 5 …On October [XXX], 2023 at 3:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling slowly (less than 5 miles per hour) west on [XXX] near [XXX] in heavy pedestrian traffic in the street when it stopped to yield to a crossing pedestrian. The front of the passenger car traveling behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-6668 | ADS | Waymo LLC | 2023-10 11:04 | Tempe, AZ | 2023 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | On October [XXX], 2023 at 11:04 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, AZ was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling southeast on [XXX] when it s…On October [XXX], 2023 at 11:04 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, AZ was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling southeast on [XXX] when it slowed to stop for a red traffic light at the intersection with [XXX]. The front of the passenger car that was traveling behind the Waymo AV made contact with the rear of the Wamyo 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. 2 of Standing General Order 2021-01. |
| 30391-6563 | ADS | Kodiak Robotics | 2023-10 15:08 | Fort Worth, TX | 2019 Kenworth Motor Truck Co T680 | ADS | Heavy Truck | No Injuries Reported | 34 | Highway / Freeway | On October [XXX], 2023 at 3:08 PM CT a tractor-trailer entered the lane of a Kodiak Autonomous Vehicle (Kodiak AV) Kenworth Class 8 semi-truck and made minor contact. The Kodiak AV was driving westbound on [XXX] in Fort …On October [XXX], 2023 at 3:08 PM CT a tractor-trailer entered the lane of a Kodiak Autonomous Vehicle (Kodiak AV) Kenworth Class 8 semi-truck and made minor contact. The Kodiak AV was driving westbound on [XXX] in Fort Worth, Texas near [XXX]. The Kodiak AV was operating with a safety driver (in the drivers seating position), who transitioned the vehicle from autonomous to manual mode approximately 5 seconds prior to impact, due to the other truck encroaching on the Kodiak AVs lane. At the time of impact, the Kodiak AV was in manual mode. No injuries occurred in the incident. The Kodiak AV pulled over after the incident, and the other driver continued down the road. The Kodiak AV's mirror-mounted SensorPod sustained minor scratches. Kodiak may supplement or correct its reporting with additional information as it may become available. |
| 30412-6395 v4 | ADS | Cruise LLC | 2023-10 21:29 | San Francisco, CA | 2023 Cruise AV | ADS | Non-Motorist: Pedestrian | Serious | 14 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6525 | ADS | Cruise LLC | 2023-10 16:31 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 13 | Street | Redacted by NHTSA as confidential business information |
| 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 |
| 30412-6596 | ADS | Cruise LLC | 2023-10 05:01 | Austin, TX | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6597 | ADS | Cruise LLC | 2023-10 02:24 | Houston, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 5 | Street | Redacted by NHTSA as confidential business information |
| 30412-6598 | ADS | Cruise LLC | 2023-10 11:37 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-6613 | ADS | Cruise LLC | 2023-10 22:19 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 22 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6614 | ADS | Cruise LLC | 2023-10 01:51 | Austin, TX | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6616 | ADS | Cruise LLC | 2023-10 08:23 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-6617 | ADS | Cruise LLC | 2023-10 23:40 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-6618 | ADS | Cruise LLC | 2023-10 01:29 | Santa Monica, CA | 2022 Cruise AV | ADS | SUV | No Injuries Reported | 12 | Intersection | Redacted by NHTSA as confidential business information |
| 30413-6684 | ADS | May Mobility | 2023-10 10:03 | Grand Rapids, MN | 2021 Toyota Sienna | ADS | Other Fixed Object | No Injuries Reported | 27 | Street | The May vehicle was traveling eastbound on [XXX] in autonomy. The vehicles internal facing cameras show that the operator started to fall asleep while applying physical input to the steering wheel. The road started to be…The May vehicle was traveling eastbound on [XXX] in autonomy. The vehicles internal facing cameras show that the operator started to fall asleep while applying physical input to the steering wheel. The road started to bend to the left. The physical input from the operator was enough to deviate the vehicle from its intended path but not enough to trigger an intervention and take the vehicle out of autonomy. The vehicle, going straight as the road curved, then struck the curb, resulting in minor vehicle damage. Due to the vehicle being off path, the vehicle begins to stop. This occurs as the operator wakes up. The operator was not injured and no third parties were impacted or otherwise affected by the incident. The local May Mobility site staff did not notice any signs of fatigue from this operator prior to going out in the vehicle. The operator had responded to audio check-ins from site staff at a regular interval. We are exploring additional risk mitigation options for in-cabin health monitoring, in addition to the existing cameras and radio check-ins. |
| 30531-6532 v2 | ADS | Transdev Alternative Services | 2023-10 9:24 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 13 | Intersection | The content of this report is unchanged from the initial report submitted [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating …The content of this report is unchanged from the initial report submitted [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode on eastbound [XXX] preparing to make a right turn onto southbound [XXX] and had stopped to yield, first for pedestrians to cross [XXX] and then for a cyclist approaching from behind traveling eastbound on the sidewalk of [XXX]. As the pedestrians finished crossing [XXX] but before the cyclist had reached [XXX], the Waymo AV test driver took manual control of the Waymo AV and began to accelerate and perform the right turn onto [XXX]. After the Waymo AV entered the crosswalk, the cyclist entered the crosswalk and made contact with the passenger's rear quarter panel of the Waymo AVE. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the vehicle. Transdev Alternative Services is reporting a duplicate report from report number: 30270-6529-1. |
| 30531-6691 | ADS | Transdev Alternative Services | 2023-10 07:48 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 23 | Intersection | On October [XXX], 2023 at 7:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] i…On October [XXX], 2023 at 7:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in the rightmost lane. As the SUV in the left adjacent lane traveling alongside the Waymo AV initiated a right lane change, the front passenger's side of the SUV made contact with the front driver's side of the Waymo AV. At the time of the impact, the Waymo's Level 4 ADS was not engaged as the test driver transitioned the Waymo AV to manual mode just before the contact. Both vehicles sustained damage. This report is a duplicate of NHTSA Report ID: 30270-6665-1. |
| 30610-6635 | ADS | Zoox, Inc. | 2023-10 09:53 | Seattle, WA | 2017 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 12 | Street | A Zoox vehicle in autonomy was traveling in the left travel lane of westbound [XXX] between [XXX] and [XXX] while passing a parked wide delivery truck, when a passenger car traveling ahead in the right lane abruptly stee…A Zoox vehicle in autonomy was traveling in the left travel lane of westbound [XXX] between [XXX] and [XXX] while passing a parked wide delivery truck, when a passenger car traveling ahead in the right lane abruptly steered into the Zoox travel lane without using a turn indicator. The Zoox vehicle braked aggressively in autonomy and the safety operator disengaged and conducted additional manual braking, but the collision was unavoidable. The driver of the passenger car left the scene without exchanging information. The Zoox vehicle sustained moderate damage. There were no injuries reported and the police were not called. |
| 30610-6638 | ADS | Zoox, Inc. | 2023-10 20:12 | San Francisco, CA | 2017 Toyota Highlander | ADS | SUV | No Injuries Reported | 17 | Street | A Zoox vehicle was being driven in manual mode eastbound on [XXX] between [XXX] and [XXX] when contact was made with the left side mirror of a parked car. There was minor damage to the Zoox vehicle's sensor housing and p…A Zoox vehicle was being driven in manual mode eastbound on [XXX] between [XXX] and [XXX] when contact was made with the left side mirror of a parked car. There was minor damage to the Zoox vehicle's sensor housing and passenger side mirror. There were no injuries and police were not called. |
| 31101-7044 v2 | ADS | Avride Inc. | 2023-10 12:50 | Austin, TX | 2020 Hyundai Sonata | ADS | Passenger Car | No Injuries Reported | 25 | Street | Our car was moving down the street with approximate speed 25mph when it was tailgated. Our driver was not injured, and the driver in the other car showed no visible injuries. However, she called an ambulance due to her p…Our car was moving down the street with approximate speed 25mph when it was tailgated. Our driver was not injured, and the driver in the other car showed no visible injuries. However, she called an ambulance due to her pregnancy. The airbags did not deploy in either vehicle. The police report says following: AFTER VIEWING VIDEO FROM UNIT 2 WEEKS LATER, IT WAS DISCOVERED THAT UNIT 1 WAS TRAVELING EAST ON [XXX] IN THE LEFT LANE. UNIT 2 WAS IN FRONT OF UNIT 1 TRAVELING EAST ON [XXX] IN THE LEFT LANE. UNIT 2 SLOWED TO TURN LEFT INTO A DRIVE WAY. UNIT 1 THEN STRUCK THE BACK RIGHT OF UNIT 2. THIS DIFFERED FROM STATEMENTS GIVEN ON SCENE. There is also code 44 in the police report, which stays for Followed Too Closely |
| 33495-6726 | ADS | Apollo Autonomous Driving USA | 2023-10 12:01 | San Francisco, CA | 2016 Lincoln MKZ Hybrid | Unknown, see Narrative | Other, see Narrative | No Injuries Reported | 15 | Intersection | An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in conventional mode with a safety operator driving. At the intersection with [XXX], the right front of the AV made contact with the …An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in conventional mode with a safety operator driving. At the intersection with [XXX], the right front of the AV made contact with the curb and the AV traveled onto the curb. The safety operator was able to drive off the curb and back onto the street. No other vehicles or property were involved. There were no injuries and the police were not called. The AV sustained minor damage to right wheel fender shield and the right lower bumper. |
| 540-6400 v4 | ADS | General Motors, LLC | 2023-10 21:29 | San Francisco, CA | 2023 Cruise AV | ADS | Non-Motorist: Pedestrian | Serious | 14 | Intersection | On December 15, 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) ma…On December 15, 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-6395-4). |
| 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). |
| 540-6531 | ADS | General Motors, LLC | 2023-10 16:31 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 13 | Street | On October 18, 2023, 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) manufactur…On October 18, 2023, 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-6525-1). |
| 540-6629 | ADS | General Motors, LLC | 2023-10 01:51 | Austin, TX | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On November 13, 2023, 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 November 13, 2023, 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-6614-1) |
| 540-6630 | ADS | General Motors, LLC | 2023-10 08:23 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On November 13, 2023, 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 November 13, 2023, 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-6616-1) |
| 540-6632 | ADS | General Motors, LLC | 2023-10 23:40 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On November 13, 2023, 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 November 13, 2023, 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-6617-1) |
| 540-6633 | ADS | General Motors, LLC | 2023-10 01:29 | Santa Monica, CA | 2022 Crui9se AV | ADS | SUV | No Injuries Reported | 12 | Intersection | On November 13, 2023, 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 November 13, 2023, 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-6618) |
| 540-6642 | ADS | General Motors, LLC | 2023-10 05:01 | Austin, TX | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On November 13, 2023, 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 November 13, 2023, 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-6596-1). . |
| 540-6644 | ADS | General Motors, LLC | 2023-10 02:24 | Houston, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 5 | Street | On November 13, 2023, 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 November 13, 2023, 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-6597-1). |
| 540-6645 | ADS | General Motors, LLC | 2023-10 11:37 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 0 | Street | On November 13, 2023, 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 November 13, 2023, 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-6598-1). |
| 540-6646 | ADS | General Motors, LLC | 2023-10 22:19 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 22 | Intersection | On November 13, 2023, 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 November 13, 2023, 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-6613-1). |
| 753-6415 v3 | Level 2 | Kia America, Inc. | 2023-10 12:30 | JOPPA, MD | 2023 KIA SPORTAGE | Unknown, see Narrative | Other, see Narrative | No Injuries Reported | 25 | Highway / Freeway | *10/6/23: 5-Day Incident Report* Customer contacted Kia's Customer Care Center on October 3, 2023 indicating she "hit the vehicle in front of her "while driving her 2023 Kia Sportage and that the by the time she realized…*10/6/23: 5-Day Incident Report* Customer contacted Kia's Customer Care Center on October 3, 2023 indicating she "hit the vehicle in front of her "while driving her 2023 Kia Sportage and that the by the time she realized it, the vehicle did not stop and was not able to apply the brakes quick enough. Specifically, the customer reported that she was driving on in traffic on [XXX] for about 10 mins and cruise control was on and set to 65mph and "was fine before with slowing down and picking back up." Customer indicated she was going 25mph when she hit an 18 wheeler truck in front of her. She reported the front was of Sportage was "caved in" and that she could not drive the vehicle. The airbags did not deploy. There were no reported injuries. The vehicle was towed. When asked by Customer Care, the customer reported that HDA and cruise control were engaged at the time of the incident but customer did not allege that either of those systems caused the accident. Customer requested that Kia repair the vehicle if not totaled by her insurance company. The subject Kia Sportage is equipped with Highway Driving Assist (HDA). HDA is a supplemental system that helps maintain a set distance and speed from the vehicle ahead when driving on a highway and helps keep the vehicle between lanes while driving. HDA may not be able to recognize all traffic situations and may not detect possible collisions due to limitations of the system. Obstacles such as vehicles, motorcycles, bicycles, pedestrians, unspecified objects and structures that may collide with the vehicle may not be detected. Based on the customer's comment of "by the time she realized it, I was not able to apply the brakes quick enough", it appears that the customer may have been distracted at the time of the incident. Kia is currently working with the customer to retrieve the vehicle's ACU but has no further information at this time. * 10/13/23: 10- Day Update* There are no new updates. Kia continues to work to obtain the ACU. * 2/15/23: February Monthly Update* On 2/15/2024, Kia submitted an update to Mr. Teitelman via NHTSA's SLFTS portal. The update stated that the EDR report has not yet been retrieved from the customer and Kia will send the EDR report to Mr. Teitelman when it is received. In addition, as of 1/23/2024, the dealership requested and was provided the customer's information, and Kia Customer Care notified the customer that the dealership will contact the customer to schedule a new appointment. |
| 753-7087 v2 | Level 2 | Kia America, Inc. | 2023-10 22:30 | BRICK TOWNSHIP, NJ | 2022 KIA K5 | ADAS | Other, see Narrative | No Injuries Reported | 75 | Highway / Freeway | Customer contacted Kia's Customer Care Center on February 6, 2024 to provide details regarding an incident that had occurred on October [XXX], 2023 involving his 2022MY Kia K5. Customer reported that while driving northb…Customer contacted Kia's Customer Care Center on February 6, 2024 to provide details regarding an incident that had occurred on October [XXX], 2023 involving his 2022MY Kia K5. Customer reported that while driving northbound on the [XXX], between [XXX] and [XXX], a vehicle merged into the customer's lane. Customer "slammed on the brakes," "hydroplaned," and rear ended the other vehicle. The vehicle was towed, but there were no injuries alleged. Customer alleged that the vehicle's airbags did not deploy and requested payment or replacement of the vehicle. The subject Kia K5 is equipped with Highway Driving Assist (HDA) and Smart Cruise Control (SCC). HDA is a supplemental system that helps maintain a set distance and speed from the vehicle ahead when driving on a highway and helps keep the vehicle between lanes while driving. HDA may not be able to recognize all traffic situations and may not detect possible collisions due to limitations of the system. Customer indicated that HDA was on at the time of the accident or in the 30 seconds immediately prior to the accident. However, customer also indicated that the SCC was not in the same timeframe. One of the requirements for HDA to be activated is that SCC must already be activated. Kia's Customer Care Center has attempted to contact the customer to request clarification, but the customer has not responded. Despite no allegation about a defect or malfunction in the HDA, Kia is reporting this incident out of an abundance of caution based on the information currently available. *3/15/2024: Monthly Update* Following submission of the report to NHTSA, customer requested that Kia Customer Care assist her with her insurance company. Customer specifically stated "I know my airbags didn't deploy but that doesn't concern me. I'm really just seeing what you guys can do to help me with my insurance." Kia advised customer of options for handling. No further information provided regarding HDA. As previously indicated, customer did not identify a failure or malfunction with HDA. No further contact from customer. |
| 753-7109 v2 | Level 2 | Kia America, Inc. | 2023-10 3:30 | Culver, CA | 2024 KIA K5 | ADAS | Other Fixed Object | Minor | 75 | Highway / Freeway | ***10-Day Update*** On February 15th, Kia removed the subject 2024MY K5 vehicles ACU and downloaded the EDR data. According to the EDR Report, the driver had SCC set at 85 MPH, which was overridden by the driver applying…***10-Day Update*** On February 15th, Kia removed the subject 2024MY K5 vehicles ACU and downloaded the EDR data. According to the EDR Report, the driver had SCC set at 85 MPH, which was overridden by the driver applying moderate accelerator pedal directly before impact. The EDR Report recorded steering input by the driver of +30 degrees, then +70 degrees directly before impact, which exceeds the ability of Lane Following Assist. About a half of a second before impact, the stability controls were engaged, which disables SCC. The EDR Report also indicates that the driver was not wearing a seat belt, causing severe loading of the steering wheel, gear shift lever, and other internal components. The driver did not press the brake pedal at any point in the recorded data. Kia did not identify any vehicle or manufacturing concerns during inspection of the vehicle or review of the EDR data. The cause of the incident appears to be driver error. |
| 988-6565 | ADS | PACCAR Incorporated | 2023-10 15:08 | Fort Worth, TX | 2019 KENWORTH T680 | ADS | Heavy Truck | No Injuries Reported | 34 | Highway / Freeway | On October 30, 2023, PACCAR was informed by Kodiak, Inc of the incident that occurred October [XXX]. On October [XXX], 2023 at 3:08 PM CT, a tractor-trailer entered the lane of Kodiak Autonomous Vehicle ("Kodiak AV"), K…On October 30, 2023, PACCAR was informed by Kodiak, Inc of the incident that occurred October [XXX]. On October [XXX], 2023 at 3:08 PM CT, a tractor-trailer entered the lane of Kodiak Autonomous Vehicle ("Kodiak AV"), Kenworth Class 8 semi-truck and made minor contact. The Kodiak AV was driving westbound on [XXX] in Fort Worth, Texas, near [XXX]. The Kodiak AV was operating with a safety driver (in the driver's seating position), who transitioned the vehicle from autonomous to manual mode approximately 5 seconds prior to impact, due to the other truck encroaching on the Kodiak AV's lane. At the time of impact, the Kodiak AV was in manual mode. No injuries occurred in the incident. The Kodiak AV pulled over after the incident, and the other driver continued down the road. The Kodiak AV's mirror-mounted SensorPod sustained minor scratches. PACCAR may supplement or correct reporting with additional information as it may become available from Kodiak. |
| 12381-8659 v2 | Level 2 | Daimler Trucks North America, LLC | 2023-09 09:04 | Louisville, KY | 2023 FREIGHTLINER Cascadia | ADAS | Heavy Truck | Serious | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-10012 | Level 2 | Tesla, Inc. | 2023-09 22:50 | East Cobb, GA | 2016 Tesla Model X | ADAS | Unknown | Unknown | 27 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-10013 | Level 2 | Tesla, Inc. | 2023-09 10:17 | Holmdel, NJ | 2023 Tesla Model 3 | ADAS | Animal | Unknown | 78 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-10014 | Level 2 | Tesla, Inc. | 2023-09 06:36 | Kent, WA | 2023 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 24 | Street | Redacted by NHTSA as confidential business information |
| 13781-6226 | Level 2 | Tesla, Inc. | 2023-09 08:11 | Bellevue, WA | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 20 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6227 | Level 2 | Tesla, Inc. | 2023-09 08:30 | Los Angeles, CA | 2023 Tesla Model Y | ADAS | SUV | Unknown | 28 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6228 | Level 2 | Tesla, Inc. | 2023-09 04:28 | Davie, FL | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 50 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6229 | Level 2 | Tesla, Inc. | 2023-09 20:02 | North Miami, FL | 2022 Tesla Model Y | ADAS | SUV | Unknown | 16 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6241 | Level 2 | Tesla, Inc. | 2023-09 22:11 | Detroit, MI | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6251 | Level 2 | Tesla, Inc. | 2023-09 19:06 | Santa Rosa Beach, FL | 2022 Tesla Model 3 | ADAS | SUV | Unknown | 49 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6252 | Level 2 | Tesla, Inc. | 2023-09 07:15 | Rancho Santa Margarita, CA | 2023 Tesla Model 3 | ADAS | First Responder Vehicle | Unknown | 43 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6266 | Level 2 | Tesla, Inc. | 2023-09 23:34 | Mountain View, CA | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 18 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6267 | Level 2 | Tesla, Inc. | 2023-09 00:57 | Halloran Springs, CA | 2022 Tesla Model 3 | ADAS | Unknown | Unknown | 79 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6364 | Level 2 | Tesla, Inc. | 2023-09 01:40 | Mission Viejo, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 71 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6365 | Level 2 | Tesla, Inc. | 2023-09 13:18 | Morris Plains, NJ | 2021 Tesla Model S | ADAS | SUV | Unknown | 33 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6366 | Level 2 | Tesla, Inc. | 2023-09 00:23 | Roxborough, CO | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6367 | Level 2 | Tesla, Inc. | 2023-09 00:17 | Chicago, IL | 2019 Tesla Model 3 | ADAS | SUV | Unknown | 63 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6374 | Level 2 | Tesla, Inc. | 2023-09 16:20 | Hayward Acres, CA | 2023 Tesla Model Y | ADAS | Van | Unknown | 4 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6375 | Level 2 | Tesla, Inc. | 2023-09 16:28 | Las Vegas, NV | 2023 Tesla Model X | ADAS | SUV | Unknown | 25 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6377 | Level 2 | Tesla, Inc. | 2023-09 16:31 | Sacramento, CA | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6378 | Level 2 | Tesla, Inc. | 2023-09 02:07 | West Bridgewater, MA | 2020 Tesla Model 3 | ADAS | Passenger Car | Unknown | 73 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6379 | Level 2 | Tesla, Inc. | 2023-09 23:47 | Oklahoma City, OK | 2020 Tesla Model Y | ADAS | Pickup Truck | Unknown | 42 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-6380 | Level 2 | Tesla, Inc. | 2023-09 09:31 | Kent, WA | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6381 | Level 2 | Tesla, Inc. | 2023-09 16:13 | Rochester, MN | 2022 Tesla Model 3 | ADAS | SUV | Unknown | 12 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6386 | Level 2 | Tesla, Inc. | 2023-09 01:09 | Sparta Township, NJ | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 31 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6387 | Level 2 | Tesla, Inc. | 2023-09 12:25 | Livermore, CA | 2023 Tesla Model 3 | ADAS | Passenger Car | Unknown | 77 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6388 | Level 2 | Tesla, Inc. | 2023-09 18:24 | Katonah, NY | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 44 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-6389 | Level 2 | Tesla, Inc. | 2023-09 21:26 | Lehi, UT | 2019 Tesla Model 3 | ADAS | Unknown | Unknown | 49 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-6390 | Level 2 | Tesla, Inc. | 2023-09 05:32 | Bellingham, WA | 2023 Tesla Model X | ADAS | Other Fixed Object | Unknown | 138 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6391 | Level 2 | Tesla, Inc. | 2023-09 04:03 | Mercedes, TX | 2018 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6392 | Level 2 | Tesla, Inc. | 2023-09 11:30 | Tampa, FL | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6397 | Level 2 | Tesla, Inc. | 2023-09 17:04 | Bulverde, TX | 2021 Tesla Model Y | ADAS | Pole / Tree | Unknown | 15 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6398 | Level 2 | Tesla, Inc. | 2023-09 01:30 | Dulles, VA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 35 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6399 | Level 2 | Tesla, Inc. | 2023-09 07:11 | Santa Monica, CA | 2022 Tesla Model S | ADAS | Other Fixed Object | Unknown | 49 | Street | Redacted by NHTSA as confidential business information |
| 13781-6410 | Level 2 | Tesla, Inc. | 2023-09 15:45 | Millbury, MA | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 35 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6753 | Level 2 | Tesla, Inc. | 2023-09 | Austin, TX | 2023 Tesla Model Y | ADAS | Van | Unknown | 10 | Street | Redacted by NHTSA as confidential business information |
| 13781-7781 | Level 2 | Tesla, Inc. | 2023-09 19:05 | Memphis, TN | 2023 Tesla Model Y | ADAS | Passenger Car | Unknown | 46 | Street | Redacted by NHTSA as confidential business information |
| 13781-8263 v2 | Level 2 | Tesla, Inc. | 2023-09 17:04 | Los Angeles, CA | 2022 Tesla Model 3 | ADAS | Heavy Truck | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8296 v3 | Level 2 | Tesla, Inc. | 2023-09 | AR | 2019 Tesla Model 3 | Unknown, see Narrative | First Responder Vehicle | Serious | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-9832 | Level 2 | Tesla, Inc. | 2023-09 03:25 | Norwalk, CT | 2019 Tesla Model X | ADAS | Other Fixed Object | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9833 | Level 2 | Tesla, Inc. | 2023-09 15:30 | Hartford, CT | 2022 Tesla Model Y | ADAS | SUV | Unknown | 80 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-9834 | Level 2 | Tesla, Inc. | 2023-09 13:45 | San Marcos, CA | 2023 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 73 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9835 | Level 2 | Tesla, Inc. | 2023-09 22:17 | Houston, TX | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 69 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-9922 | Level 2 | Tesla, Inc. | 2023-09 21:28 | Nashua, NH | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 39 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9923 | Level 2 | Tesla, Inc. | 2023-09 06:21 | Santa Fe Springs, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 79 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9924 | Level 2 | Tesla, Inc. | 2023-09 22:50 | Dallas, TX | 2018 Tesla Model X | ADAS | Pickup Truck | Unknown | 16 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-9925 | Level 2 | Tesla, Inc. | 2023-09 21:44 | Kanab, UT | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 57 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9928 | Level 2 | Tesla, Inc. | 2023-09 10:30 | San Marcos, TX | 2023 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 73 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30270-6351 | ADS | Waymo LLC | 2023-09 20:34 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the righ…On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the right lane on northbound [XXX], an SUV that was passing the parked Waymo AV made contact with the rear drivers side 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. 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. |
| 30270-6352 | ADS | Waymo LLC | 2023-09 18:26 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On September [XXX], 2023 at 6:26 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]. While the Waymo AV was stopped in park …On September [XXX], 2023 at 6:26 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]. While the Waymo AV was stopped in park waiting to pick up a passenger near the right side curb of the road on westbound [XXX], a passenger car that was passing the stopped Waymo AV 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. 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. |
| 30270-6368 | ADS | Waymo LLC | 2023-09 17:02 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 12 | Street | On September [XXX], 2023 at 5:02 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] towa…On September [XXX], 2023 at 5:02 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] toward [XXX] when a pickup truck drove alongside the Waymo AV. The passengers side of the pickup truck made contact with the drivers side of the Waymo AV. The pickup truck had been following and overtaking the Waymo AV for several minutes, and the pickup truck passengers occasionally threw items at 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. |
| 30270-6405 | ADS | Waymo LLC | 2023-09 19:12 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 8 | Intersection | On September [XXX], 2023 at 7:12 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 westbound on …On September [XXX], 2023 at 7:12 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 westbound on [XXX] and approached the stop sign intersection at [XXX]. As the Waymo AV came to a full stop, a city bus was proceeding through the intersection, traveling eastbound on [XXX]. As the city bus continued to proceed through the intersection, the Waymo AV began to proceed forward. The Waymo AV entered the intersection as the city bus proceeded through and exited the intersection, and at the same time, a passenger car traveling northbound on [XXX] that had been occluded by the city bus had also entered the intersection. The passenger car and the Waymo AV then made contact in the middle of the intersection. 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. |
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.