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 5501 to 5600.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-8890 | ADS | Waymo LLC | 2024-09 05:44 | Tempe, AZ | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On September [XXX], 2024 at 5:44 AM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in a queue of traffic in t…On September [XXX], 2024 at 5:44 AM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in a queue of traffic in the left turn lane of eastbound [XXX] for a red light at the intersection with [XXX]. A passenger car approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-8891 | ADS | Waymo LLC | 2024-09 06:53 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On September 3[XXX], 2024 at 6:53 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was stopped in a queue of t…On September 3[XXX], 2024 at 6:53 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was stopped in a queue of traffic in the single lane of northeastbound [XXX] for a red light at the intersection with [XXX]. A heavy truck approached the Waymo AV from behind, and the front of the heavy truck 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. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-8892 | ADS | Waymo LLC | 2024-09 18:33 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | On September [XXX], 2024 at 6:33 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light with the …On September [XXX], 2024 at 6:33 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light with the left turn signal activated in the northeastbound lane of [XXX] at the intersection with [XXX], preparing to make a left turn onto [XXX]. While the Waymo AV was stationary, an SUV that had been stopped behind the Waymo AV entered the oncoming lane, maneuvering to the left of the Waymo AV. As the SUV was passing the stopped Waymo AV, the passenger side of the SUV 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 SUV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 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. |
| 30413-8861 | ADS | May Mobility | 2024-09 09:06 | Peachtree Corners, GA | 2022 Toyota Sienna | ADS | Other Fixed Object | No Injuries Reported | 30 | Street | A May autonomous vehicle was traveling in the right lane of a two-lane road, maintaining a steady speed of 30 mph, in compliance with the posted speed limit. The road was characterized by light traffic, with a slight cur…A May autonomous vehicle was traveling in the right lane of a two-lane road, maintaining a steady speed of 30 mph, in compliance with the posted speed limit. The road was characterized by light traffic, with a slight curvature that transitioned from a gentle rightward sway to a leftward sway. As the vehicle navigated this transition of curvature, the May vehicle made contact with the curb, causing a flat tire. At the time of the incident, no other vehicles or pedestrians were present in the immediate vicinity, and there were no external factors such as obstructions or adverse weather conditions influencing the vehicles path. Speed was reduced from 30mph to 25mph after this event and tested (and worked to mitigate the problem in that area) and now will be reduced to 22 which is the sweet spot for most areas on the route. The May vehicle chose to maneuver at the curb due to perceived risk from a car in an adjacent lane, so May is increasing the allowed distance to the curb to mitigate how close the vehicles are allowed to get. |
| 30530-8579 | ADS | Aurora Operations, Inc. | 2024-09 13:59 | Ennis, TX | 2023 Peterbilt 579 | ADS | Other, see Narrative | No Injuries Reported | 72 | Highway / Freeway | On September [XXX], at approximately 1:59 pm CDT, an Aurora truck operating in autonomy was traveling northbound on [XXX] near Ennis, TX when a passing truck kicked up a piece of debris that cracked the Aurora windshield…On September [XXX], at approximately 1:59 pm CDT, an Aurora truck operating in autonomy was traveling northbound on [XXX] near Ennis, TX when a passing truck kicked up a piece of debris that cracked the Aurora windshield. Aurora vehicle operators were not injured. As per the companys protocols, the vehicle operators elected to disengage autonomy, reported the damage, and drove to the nearby Aurora terminal for repairs. |
| 30530-8580 | ADS | Aurora Operations, Inc. | 2024-09 09:27 | Buffalo, TX | 2024 Peterbilt 579 | ADS | Other, see Narrative | No Injuries Reported | 65 | Highway / Freeway | On September [XXX], at approximately 9:27 am CDT, an Aurora truck operating in autonomy was traveling southbound on [XXX] near Buffalo, TX when a passing vehicle kicked up a piece of debris that cracked the Aurora windsh…On September [XXX], at approximately 9:27 am CDT, an Aurora truck operating in autonomy was traveling southbound on [XXX] near Buffalo, TX when a passing vehicle kicked up a piece of debris that cracked the Aurora windshield. Aurora vehicle operators were not injured. As per the companys protocol, the vehicle operators elected to disengaged autonomy, reported the damage, and drove to the nearby Aurora terminal for repairs. |
| 30530-8670 | ADS | Aurora Operations, Inc. | 2024-09 22:34 | Huntsville, TX | 2023 Peterbilt 579 | ADS | Other, see Narrative | No Injuries Reported | 60 | Highway / Freeway | On September [XXX}, at approximately 22:34 CDT, an Aurora truck was traveling southbound in autonomy on [XXX] near Huntsville, TX and hit a tire shred, which damaged the lower passenger side fairing. Aurora vehicle opera…On September [XXX}, at approximately 22:34 CDT, an Aurora truck was traveling southbound in autonomy on [XXX] near Huntsville, TX and hit a tire shred, which damaged the lower passenger side fairing. Aurora vehicle operators were not injured. The Aurora Driver attempted an avoidance maneuver but was unable to complete it before hitting the tire shred in its lane. Per the company's protocol, the vehicle operators elected to take control of the vehicle after impact. After inspecting the damage at a nearby truck stop, the vehicle operators drove and continued on their mission. |
| 30531-8798 | ADS | Transdev Alternative Services | 2024-09 22:50 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On September [XXX], 2024 at 10:50 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] wh…On September [XXX], 2024 at 10:50 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it slowed to a stop in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV remained stationary, a passenger car approached from behind the Waymo AV, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30270-8760-1. |
| 30531-8902 | ADS | Transdev Alternative Services | 2024-09 16:26 | Austin, TX | 2024 Jaguar I-Pace | ADS | Passenger Car | Minor | 44 | Street | On September [XXX], 2024 at 4:26 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in…On September [XXX], 2024 at 4:26 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in the middle lane of a three lane road. A passenger car in the left most lane merged onto [XXX] and changed lanes into the Waymo AV in the middle lane. The passenger side and front corner of the passenger car made contact with the driver side of the Waymo AV. At the time of the impact, the Waymo AV's level 4 ADS was engaged in autonomous mode, and a test driver was present. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of NHTSA report ID 30270-8823-1 and 30270-8823-2. |
| 30531-8903 | ADS | Transdev Alternative Services | 2024-09 21:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On September [XXX], 2024 at 9:15 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 southbound …On September [XXX], 2024 at 9:15 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 southbound on [XXX] and came to a stop in a queue of traffic for a red light at the intersection with [XXX]. A passenger vehicle in front of the Waymo AV began to roll backwards, and the rear of the passenger car made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA report ID 30270-8863-1. |
| 30531-8904 | ADS | Transdev Alternative Services | 2024-09 20:44 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Street | On September [XXX], 2024 at 8:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was stopped in a queue of traffic i…On September [XXX], 2024 at 8:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was stopped in a queue of traffic in the leftmost of two through lanes on southbound [XXX] at the intersection with [XXX] when a van traveling behind the Waymo AV passed the Waymo AV on the left to enter the dedicated left turn lane. The passenger side of the van made contact with the rear left sensor of the Waymo AV. Without stopping, the van then crossed the double yellow line to the northbound side of [XXX], turned left onto eastbound [XXX], and left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, a test driver was present (in the driver's seating position). The Waymo AV sustained damage to the near left sensor housing and assembly. 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-8880-1. |
| 30531-8905 | ADS | Transdev Alternative Services | 2024-09 13:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On September [XXX], 2024 at 1:35 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]. The Waymo AV was traveling south wes…On September [XXX], 2024 at 1:35 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]. The Waymo AV was traveling south westbound on [XXX] in the left lane and came to a stop in a queue of traffic. While the Waymo AV remained stationary, a passenger car approached the Waymo AV from behind and the front bumper of the passenger car made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA report ID 30270-8889-1. |
| 33257-8638 | ADS | VinFast Auto, LLC | 2024-09 12:00 | between Hayward and Union City, CA | Vinfast VF8 | ADAS | Passenger Car | No Injuries Reported | 65 | Highway / Freeway | The vehicle in front of the customer's vehicle slowed down abruptly on the freeway and the customer immediately stepped on the brake to slow her vehicle down. The customer's vehicle slowed down in a straight line without…The vehicle in front of the customer's vehicle slowed down abruptly on the freeway and the customer immediately stepped on the brake to slow her vehicle down. The customer's vehicle slowed down in a straight line without locking-up of the wheels, indicating ABS worked as intended. The customer's vehicle was then rear-ended by the vehicle which was unable to stop resulting in a minor fender-bender on the freeway. No injuries were reported and both vehicles sustained only scratches and were able to drive away from the scene. |
| 33257-8867 | ADS | VinFast Auto, LLC | 2024-09 | Poulsbo, WA | 2023 Vinfast VF8 | ADAS | Other Fixed Object | No Injuries Reported | Rural Road | The customer was traveling on a two lane, country road, which was missing lane markings on the sides of the road - only the middle line was properly marked. The speed limit on the country road is 35MPH. The customer noti…The customer was traveling on a two lane, country road, which was missing lane markings on the sides of the road - only the middle line was properly marked. The speed limit on the country road is 35MPH. The customer noticed a pothole on the side of the road, swerved towards the middle of the road to avoid it, but the LKA assist engaged and moved the vehicle back in the lane. By doing so, the vehicle ran over the pothole, with both front and back passenger side tires and damaged both wheel and tires in the process. During our investigation, we determined that in this case the LKA worked as intended. The system is designed to prioritize a solid line, and can't detect a pothole, and since the road is very narrow (our estimate is less than 3m per side) the vehicle unfortunately ran over the pothole. LKA/ELK system limitations throughout the industry are similar: the LKA/ELK systems try to keep vehicle inside the lane, to prevent a vehicle from drifting out, and the system can't predict driver intention, for example: Is the driver crossing solid lane intentionally or by accident, is hard to distinguish. Relevant override conditions in this case are: - Steering wheel speed 200deg/s - Steering torque 3.5Nm In our application, the override force is limited by the EU homologation test and therefore, we feel that the vehicle behaved as expected and should have been over-powered by the driver to avoid the pothole, thus eliminating a costly replacement cost of two wheels and tires. | |
| 502-8686 | Level 2 | Ford Motor Company | 2024-09 5:40 | Wixom, MI | 2025 Ford Explorer | ADAS | Pickup Truck | No Injuries Reported | 0 | Highway / Freeway | On September [XXX], 2024, the driver of the Explorer was traveling east on [XXX] while using BlueCruise hands-free mode. The driver noticed traffic was stopped ahead and took control of the vehicle, bringing it to a stop…On September [XXX], 2024, the driver of the Explorer was traveling east on [XXX] while using BlueCruise hands-free mode. The driver noticed traffic was stopped ahead and took control of the vehicle, bringing it to a stop. A following vehicle (#2) failed to stop and collided with the rear of the Explorer. Subsequently, vehicle #2 was rear-ended by another vehicle (#3). There were no airbags deployed, no injuries reported, and the subject vehicle (Explorer) was towed following the incident. Ford is currently investigating the situation and has confirmed that the vehicle was equipped with ADAS Level 2 and BlueCruise. |
| 502-8738 v2 | Level 2 | Ford Motor Company | 2024-09 13:28 | Novi, MI | 2024 Ford Mach-E | ADAS | Passenger Car | No Injuries Reported | 15 | Highway / Freeway | Update on Report 502-8738-1: Ford received the police report on November 11, 2024, which indicates that a fourth vehicle was involved and left the scene. The police report also notes that one passenger complained of back…Update on Report 502-8738-1: Ford received the police report on November 11, 2024, which indicates that a fourth vehicle was involved and left the scene. The police report also notes that one passenger complained of back pain, but no medical attention was provided at the scene. Additionally, Ford has obtained the EDR data report from the vehicle and has updated the information concerning the pre-collision speed and the time of the incident. On September [XXX], 2024, the driver of the Mach-E reported that they were traveling east on [XXX] near [XXX] while using BlueCruise hands-free mode. An Audi travelling in front of the Mach-E stopped abruptly, prompting the Mach-E driver to take control and apply the brakes. The Mach-E impacted the rear of the Audi and the Audi subsequently struck a GMC vehicle that was directly in front of it. The airbags in the Audi deployed, and both the Mach-E and the Audi were towed from the scene. At this time, Ford's understanding is that there were no injuries involved. Ford has confirmed that the vehicle was equipped with ADAS Level 2 and BlueCruise. |
| 540-8658 v3 | Level 2 | General Motors, LLC | 2024-09 16:40 | Chuckey, TN | 2023 GMC Sierra | Verified Engaged | Pickup Truck | Unknown | 60 | Highway / Freeway | GM is submitting this update report based on obtained EDR data. On September [XXX], 2024, a 2023 Sierra was travelling southwest on [XXX] in the left lane with Super Cruise engaged and active. According to crash data a…GM is submitting this update report based on obtained EDR data. On September [XXX], 2024, a 2023 Sierra was travelling southwest on [XXX] in the left lane with Super Cruise engaged and active. According to crash data and a police report, the Sierra experienced a frontal impact with a 2014 Nissan Titan which, in turn, struck a 2018 Honda Pilot. After striking the Nissan, the Sierra proceeded to rollover on its side, impacting a right highway guard rail, ultimately coming to a rest on all four vehicle wheels. Frontal and side air bags and seat belt pretensioners deployed. The driver was buckled at the time of the crash. A child was restrained in a booster seat in the rear. The police report alleged there were possible injuries to the driver and passenger of the Sierra, but occupants were not transported to a hospital for medical treatment. According to EDR data, driver attention was down in his lap 4.2 seconds prior to the incident for at least 3.5 seconds. A Forward Collision Alert was recorded, notifying the driver of a potential collision 2 seconds prior to the crash. Super Cruise changed state to Disabled / Not Ready 0.8 seconds prior to the incident due to a brake pedal press. |
| 540-8718 | Level 2 | General Motors, LLC | 2024-09 11:37 | Dixon, CA | 2024 Cadillac Lyriq | ADAS | Pole / Tree | No Injuries Reported | 78 | Highway / Freeway | On September [XXX], 2024, a 2024 Cadillac Lyriq was travelling southwest on [XXX] in Dixon, California, with Super Cruise engaged and active. According to OnStar audio recordings, the driver left the highway on the right…On September [XXX], 2024, a 2024 Cadillac Lyriq was travelling southwest on [XXX] in Dixon, California, with Super Cruise engaged and active. According to OnStar audio recordings, the driver left the highway on the right and hit a tree. Crash data indicates a right side impact that deployed the right side airbags and front seat belt pretensioners. The driver was buckled at the time of the crash. According to telematics data, approximately 10 seconds prior to crash, Super Cruise entered an Override state due to a steering wheel torque input. At approximately 5 seconds prior to the crash, Super Cruise entered a Disable/Not Ready state due to a brake pedal input. |
| 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. |
| 988-8590 | ADS | PACCAR Incorporated | 2024-09 13:59 | Ennis, TX | 2023 Peterbilt 579 | ADS | Other, see Narrative | No Injuries Reported | 72 | Highway / Freeway | On September [XXX], at approximately 1:59 pm CDT, an Aurora truck operating in autonomy was traveling northbound on [XXX] near Ennis, TX when a passing truck kicked up a piece of debris that cracked the Aurora windshield…On September [XXX], at approximately 1:59 pm CDT, an Aurora truck operating in autonomy was traveling northbound on [XXX] near Ennis, TX when a passing truck kicked up a piece of debris that cracked the Aurora windshield. Aurora vehicle operators were not injured. As per the companys protocols, the vehicle operators elected to disengage autonomy, reported the damage, and drove to the nearby Aurora terminal for repairs. |
| 988-8592 | ADS | PACCAR Incorporated | 2024-09 09:27 | Buffalo, TX | 2024 Peterbilt 579 | ADS | Other, see Narrative | No Injuries Reported | 65 | Highway / Freeway | On September [XXX], at approximately 9:27 am CDT, an Aurora truck operating in autonomy was traveling southbound on [XXX] near Buffalo, TX when a passing vehicle kicked up a piece of debris that cracked the Aurora windsh…On September [XXX], at approximately 9:27 am CDT, an Aurora truck operating in autonomy was traveling southbound on [XXX] near Buffalo, TX when a passing vehicle kicked up a piece of debris that cracked the Aurora windshield. Aurora vehicle operators were not injured. As per the companys protocol, the vehicle operators elected to disengaged autonomy, reported the damage, and drove to the nearby Aurora terminal for repairs. |
| 988-8810 | ADS | PACCAR Incorporated | 2024-09 22:34 | Huntsville, TX | 2023 Peterbilt 579 | ADS | Other, see Narrative | No Injuries Reported | 60 | Highway / Freeway | On September [XXX], at approximately 22:34 CDT, an Aurora truck was traveling southbound in autonomy on [XXX] near Huntsville, TX, and hit a tire shred, which damaged the lower passenger side fairing. Aurora vehicle oper…On September [XXX], at approximately 22:34 CDT, an Aurora truck was traveling southbound in autonomy on [XXX] near Huntsville, TX, and hit a tire shred, which damaged the lower passenger side fairing. Aurora vehicle operators were not injured. The Aurora Driver attempted an avoidance maneuver but was unable to complete it before hitting the tire shred in its lane. Per the company's protocol, the vehicle operators elected to take control of the vehicle after impact. After inspecting the damage at a nearby truck stop, the vehicle operators drove and continued on their mission. |
| 1243-8299 v2 | Level 2 | Subaru of America, Inc. | 2024-08 20:27 | Edgewood, NM | 2023 Subaru Outback | ADAS | Other Fixed Object | No Injuries Reported | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1243-8428 v2 | Level 2 | Subaru of America, Inc. | 2024-08 10:03 | Stuart, FL | 2022 Subaru Forester | ADAS | Other Fixed Object | No Injuries Reported | 53 | Street | Redacted by NHTSA as confidential business information |
| 1243-8486 v2 | Level 2 | Subaru of America, Inc. | 2024-08 23:00 | Napavine, WA | 2022 Subaru Forester | ADAS | Other Fixed Object | Minor | 25 | Rural Road | According to the customer's statements, the subject vehicle was traveling on [XXX] at 11PM on Sunday, 8/[XXX]/2024 at a speed of 25 MPH with Adaptive Cruise Control (ACC) and Lane Centering (LCF) engaged. The customer al…According to the customer's statements, the subject vehicle was traveling on [XXX] at 11PM on Sunday, 8/[XXX]/2024 at a speed of 25 MPH with Adaptive Cruise Control (ACC) and Lane Centering (LCF) engaged. The customer alleged that the vehicle steered toward a barrier. The vehicle struck the barrier, left the roadway into a ditch and rolled over. The vehicle sustained impact damage to the front left quarter and rollover damage to both sides, roof and hood. The customer stated that she was wearing a seatbelt but remembered regaining consciousness in the rear seat. The customer indicated she was treated for minor injuries but was not transported to the hospital. The curtain airbags deployed. The vehicle was towed from the scene. Subaru was not able to inspect the subject vehicle. The customer was uninsured at the time of the incident and the tow company indicated the vehicle could not be made available as it was scheduled to be sent to auction. The customer did not provide a requested copy of the police report. A review of the incident location indicated that the short section of [XXX] that would have been travelled by the vehicle has been an area of a number of construction/development projects. Subaru was unable to determine the condition of the roadway or lane markings at the time of the incident. |
| 13781-8308 | Level 2 | Tesla, Inc. | 2024-08 08:40 | Sunnyvale, CA | 2021 Tesla Model S | ADAS | Other Fixed Object | Unknown | 30 | Street | Redacted by NHTSA as confidential business information |
| 13781-8309 | Level 2 | Tesla, Inc. | 2024-08 07:02 | Roseville, CA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 60 | Street | Redacted by NHTSA as confidential business information |
| 13781-8312 | Level 2 | Tesla, Inc. | 2024-08 02:48 | Austin, TX | 2023 Tesla Model 3 | ADAS | Unknown | Unknown | 33 | Street | Redacted by NHTSA as confidential business information |
| 13781-8313 | Level 2 | Tesla, Inc. | 2024-08 23:45 | San Bernardino, CA | 2024 Tesla Model 3 | ADAS | Unknown | Unknown | 7 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8314 | Level 2 | Tesla, Inc. | 2024-08 15:33 | Slippery Rock, PA | 2019 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 14 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8315 | Level 2 | Tesla, Inc. | 2024-08 17:53 | Reading, MA | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 51 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8338 | Level 2 | Tesla, Inc. | 2024-08 18:01 | Tracy, CA | 2016 Tesla Model X | ADAS | Unknown | Unknown | 64 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8340 | Level 2 | Tesla, Inc. | 2024-08 2:41 | Ridgefield Park, NJ | 2024 Tesla Model 3 | ADAS | Unknown | Unknown | 27 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8341 | Level 2 | Tesla, Inc. | 2024-08 20:01 | Perry, UT | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8342 | Level 2 | Tesla, Inc. | 2024-08 15:43 | Glendale, AZ | 2024 Tesla Model 3 | Unknown, see Narrative | Other Fixed Object | Unknown | 43 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8419 | Level 2 | Tesla, Inc. | 2024-08 18:51 | Nephi, UT | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 25 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8420 | Level 2 | Tesla, Inc. | 2024-08 04:13 | Garner, NC | 2023 Tesla Model 3 | ADAS | Unknown | Unknown | 48 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8422 | Level 2 | Tesla, Inc. | 2024-08 13:17 | Bridgewater, NJ | 2023 Tesla Model Y | ADAS | Unknown | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-8423 | Level 2 | Tesla, Inc. | 2024-08 22:55 | Houston, TX | 2018 Tesla Model X | ADAS | Unknown | Unknown | 51 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8425 | Level 2 | Tesla, Inc. | 2024-08 02:23 | Orlando, FL | 2020 Tesla Model 3 | ADAS | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8426 | Level 2 | Tesla, Inc. | 2024-08 14:28 | Jasper, FL | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 68 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8427 | Level 2 | Tesla, Inc. | 2024-08 17:05 | Laytonville, CA | 2020 Tesla Model X | ADAS | Other Fixed Object | Unknown | 20 | Parking Lot | Redacted by NHTSA as confidential business information |
| 13781-8429 v2 | Level 2 | Tesla, Inc. | 2024-08 02:10 | Clear Lake, IA | 2023 Tesla Model X | ADAS | Passenger Car | Serious | 3 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8433 | Level 2 | Tesla, Inc. | 2024-08 03:30 | Seguin, TX | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 58 | Street | Redacted by NHTSA as confidential business information |
| 13781-8434 | Level 2 | Tesla, Inc. | 2024-08 17:21 | Chandler, AZ | 2019 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 46 | Street | Redacted by NHTSA as confidential business information |
| 13781-8435 | Level 2 | Tesla, Inc. | 2024-08 00:03 | Danville, CA | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 68 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8436 | Level 2 | Tesla, Inc. | 2024-08 05:30 | San Jose, CA | 2016 Tesla Model X | ADAS | Unknown | Unknown | 39 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8438 | Level 2 | Tesla, Inc. | 2024-08 03:42 | Santa Ana, CA | 2023 Tesla Model S | ADAS | Unknown | Unknown | 63 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8439 | Level 2 | Tesla, Inc. | 2024-08 22:11 | Fayetteville, GA | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 27 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-8440 | Level 2 | Tesla, Inc. | 2024-08 02:44 | Chehalis, WA | 2022 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8441 v2 | Level 2 | Tesla, Inc. | 2024-08 20:33 | Parker, CO | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-8457 | Level 2 | Tesla, Inc. | 2024-08 17:57 | FL | 2016 Tesla Model S | ADAS | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-8458 | Level 2 | Tesla, Inc. | 2024-08 15:32 | San Diego, CA | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 52 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8460 | Level 2 | Tesla, Inc. | 2024-08 19:22 | Grayling, MI | 2023 Tesla Model Y | ADAS | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-8461 | Level 2 | Tesla, Inc. | 2024-08 20:52 | Canonsburg, PA | 2020 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 15 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-8462 | Level 2 | Tesla, Inc. | 2024-08 16:43 | Traverse, MI | 2020 Tesla Model 3 | ADAS | Unknown | Unknown | 6 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8463 | Level 2 | Tesla, Inc. | 2024-08 21:18 | Decatur, CA | 2023 Tesla Model S | ADAS | Unknown | Unknown | 5 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8464 | Level 2 | Tesla, Inc. | 2024-08 12:09 | Rexford, NY | 2021 Tesla Model S | ADAS | Unknown | Unknown | 24 | Street | Redacted by NHTSA as confidential business information |
| 13781-8465 v2 | Level 2 | Tesla, Inc. | 2024-08 20:07 | Orange, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 76 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8466 | Level 2 | Tesla, Inc. | 2024-08 23:06 | Wickenburg, AZ | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8473 | Level 2 | Tesla, Inc. | 2024-08 13:35 | Austin, TX | 2018 Tesla Model 3 | ADAS | Heavy Truck | Unknown | 13 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-8474 | Level 2 | Tesla, Inc. | 2024-08 13:31 | Sacramento, CA | 2023 Tesla Model 3 | ADAS | SUV | Unknown | 37 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8475 | Level 2 | Tesla, Inc. | 2024-08 01:16 | Newton, MA | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8476 v2 | Level 2 | Tesla, Inc. | 2024-08 09:45 | Wickenburg, AZ | 2024 Tesla Model 3 | ADAS | Unknown | Unknown | 27 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-8477 | Level 2 | Tesla, Inc. | 2024-08 07:05 | Santa Ynez, CA | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 36 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8479 | Level 2 | Tesla, Inc. | 2024-08 07:05 | West Palm Beach, FL | 2022 Tesla Model Y | ADAS | Unknown | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-8488 | Level 2 | Tesla, Inc. | 2024-08 08:47 | Perris, CA | 2023 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8489 | Level 2 | Tesla, Inc. | 2024-08 21:27 | McKinney, TX | 2024 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 25 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8490 | Level 2 | Tesla, Inc. | 2024-08 10:50 | Sarasota, FL | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 14 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8491 | Level 2 | Tesla, Inc. | 2024-08 03:15 | Gravois Mills, MO | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 9 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8492 | Level 2 | Tesla, Inc. | 2024-08 17:20 | Nevisdale, KY | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 31 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8497 v2 | Level 2 | Tesla, Inc. | 2024-08 21:09 | Palo Alto, CA | 2024 Tesla Model Y | ADAS | Passenger Car | Moderate | 17 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-8505 | Level 2 | Tesla, Inc. | 2024-08 18:50 | Tomball, TX | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 27 | Street | Redacted by NHTSA as confidential business information |
| 13781-8506 | Level 2 | Tesla, Inc. | 2024-08 22:13 | Boca Raton, FL | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 12 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8507 | Level 2 | Tesla, Inc. | 2024-08 19:30 | Chesterton, IN | 2023 Tesla Model S | ADAS | Unknown | Unknown | 0 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8508 | Level 2 | Tesla, Inc. | 2024-08 00:16 | Llano, CA | 2022 Tesla Model Y | ADAS | Passenger Car | Unknown | 58 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-8509 | Level 2 | Tesla, Inc. | 2024-08 16:28 | Kissimmee, FL | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 2 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8510 | Level 2 | Tesla, Inc. | 2024-08 23:20 | Wickenburg, AZ | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 27 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-8706 | Level 2 | Tesla, Inc. | 2024-08 21:25 | Saratoga, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | No Injuries Reported | 30 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8719 | Level 2 | Tesla, Inc. | 2024-08 01:13 | San Francisco, CA | 2020 Tesla Model X | ADAS | Unknown | No Injuries Reported | 44 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8720 v2 | Level 2 | Tesla, Inc. | 2024-08 06:11 | West Windsor, NJ | 2024 Tesla Model Y | ADAS | Pole / Tree | Fatality | 76 | Street | Redacted by NHTSA as confidential business information |
| 13781-8834 v2 | Level 2 | Tesla, Inc. | 2024-08 06:31 | South Richmond Hill, NY | 2023 Tesla Model Y | Unknown, see Narrative | Unknown | Unknown | 64 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-8836 | Level 2 | Tesla, Inc. | 2024-08 00:24 | Fairfax, VA | 2023 Tesla Model Y | ADAS | Other Fixed Object | No Injuries Reported | 20 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9615 | Level 2 | Tesla, Inc. | 2024-08 15:49 | Tracy, CA | 2023 Tesla Model Y | Unknown, see Narrative | Unknown | No Injuries Reported | 71 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1422-8688 | Level 2 | Volvo Car USA, LLC | 2024-08 08:05 | Chesterfield, NY | 2022 Volvo XC90 | ADAS | Other Fixed Object | No Injuries Reported | 55 | Highway / Freeway | Customer states: "Driving and took eyes off the road for a second. Car hit guard rail. The whole tire came off. The front door and the backdoor (damaged). Driving with auto pilot. The auto pilot didn't stay on the road. …Customer states: "Driving and took eyes off the road for a second. Car hit guard rail. The whole tire came off. The front door and the backdoor (damaged). Driving with auto pilot. The auto pilot didn't stay on the road. No lane assist (support). Feels this is vehicle issue." We have not inspected the vehicle. |
| 28349-8269 v2 | Level 2 | Lucid USA, Inc. | 2024-08 07:15 | LONG BEACH, CA | 2024 LUCID AIR | ADAS | Passenger Car | Unknown | 6 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 28349-8482 v3 | Level 2 | Lucid USA, Inc. | 2024-08 12:47 | Newark, CA | 2022 Lucid Air | ADAS | Heavy Truck | Unknown | 7 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 29990-8415 | Level 2 | Rivian Automotive, LLC | 2024-08 08:01 | CA | 2023 Rivian R1S | Unknown, see Narrative | Other Fixed Object | No Injuries Reported | 76 | Highway / Freeway | On August [XXX], 2024, at approximately 8:01 AM ET the subject vehicle was traveling with adaptive cruise control (ACC) engaged at a speed of approximately 76 mph. ACC is not a level 2 ADAS system, but Rivian is submitti…On August [XXX], 2024, at approximately 8:01 AM ET the subject vehicle was traveling with adaptive cruise control (ACC) engaged at a speed of approximately 76 mph. ACC is not a level 2 ADAS system, but Rivian is submitting this report because there was some uncertainty in the verbal complaint about whether the driver was allegedly using ACC or Highway Assist (HWA), which is a level 2 feature. The driver initially reported that they were using ACC, but the Rivian call center mistakenly assumed HWA was activated and noted it as such. However, vehicle telematics data demonstrates that HWA was not active during the crash or in the 30 seconds prior to this crash and that ACC was the system in use leading up to the crash. The verbal report from the driver was difficult to understand but Rivians takeaway from the incident is that the vehicle was in the left lane with ACC activated when the lane ended. The driver admitted that they did not react to the lane ending in time and the vehicle impacted the center divider with the side of the vehicle. Damage to the vehicle is unknown but the customer reported that the airbags deployed and that the vehicle had to be towed. |
| 30270-8316 v2 | ADS | Waymo LLC | 2024-08 13:58 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | This is an update to report 30270-8316-1 originally submitted on August 9, 2024. The original report indicated in the narrative that the AV was traveling westbound on [XXX]. The AV was traveling eastbound on [XXX]. The c…This is an update to report 30270-8316-1 originally submitted on August 9, 2024. The original report indicated in the narrative that the AV was traveling westbound on [XXX]. The AV was traveling eastbound on [XXX]. The contents of the report are otherwise unchanged. On August [XXX], 2024 at 1:58 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 eastbound on [XXX] and approached the intersection where westbound [XXX] merges with southbound [XXX]. The Waymo AV entered the intersection on a green light but traffic in the intersection slowed to a stop, resulting in a lack of space ahead for the Waymo AV to proceed completely through the intersection. While the Waymo AV was stopped in the intersection, a passenger car traveling in the far left lane of southbound [XXX] proceeded into the intersection, crossed over the center and right lanes of southbound [XXX], heading towards a pedestrianized space area closed to vehicular traffic, and then made contact with the front 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. |
| 30270-8317 | ADS | Waymo LLC | 2024-08 14:21 | Phoenix, AZ | 2024 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Parking Lot | On August [XXX], 2024 at 2:21 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV in a parking lot near [XXX] and [XXX]. The Waymo AV was stopped in a parking …On August [XXX], 2024 at 2:21 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV in a parking lot near [XXX] and [XXX]. The Waymo AV was stopped in a parking lot of an apartment complex when the Waymo AV rider opened the rear driver side door as an SUV was passing to the left side of the Waymo AV. The Waymo AV's rear driver door made contact with the front and rear passenger doors of the SUV. The passenger in the Waymo AV unbuckled their seatbelt shortly before the moment of impact, likely because the AV was at its dropoff location and the passenger was preparing to exit. 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. |
| 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. |
| 30270-8344 | ADS | Waymo LLC | 2024-08 12:24 | Scottsdale, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 44 | Street | On August [XXX], 2024 at 12:24 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving roadway debris on [XXX] at [XXX]. The Waymo AV was traveling south on [XXX] in t…On August [XXX], 2024 at 12:24 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving roadway debris on [XXX] at [XXX]. The Waymo AV was traveling south on [XXX] in the rightmost lane and had just crossed the intersection with [XXX] when the front passenger side wheel struck a piece of wood in the roadway. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained a flat tire. 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-8356 | ADS | Waymo LLC | 2024-08 00:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 1 | Parking Lot | On August [XXX], 2024 at 12:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fence on [XXX] at [XXX]. The Waymo AV was entering a parking lot on [XXX…On August [XXX], 2024 at 12:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fence on [XXX] at [XXX]. The Waymo AV was entering a parking lot on [XXX] between [XXX] and [XXX] when the front right sensor made contact with a fence. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 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-8357 | ADS | Waymo LLC | 2024-08 18:25 | Scottsdale, AZ | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 1 | Parking Lot | On August [XXX], 2024 at 6:25 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a gate at [XXX]. The Waymo AV was proceeding east through an apartment complex pa…On August [XXX], 2024 at 6:25 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a gate at [XXX]. The Waymo AV was proceeding east through an apartment complex parking area and began passing a metal gate as it was closing. The Waymo AV maneuvered to the left and slowed in response to the closing gate but the gate made contact with the front right sensor of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 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-8417 | ADS | Waymo LLC | 2024-08 03:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On August [XXX], 2024 at 3:08 AM 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 north-westboun…On August [XXX], 2024 at 3:08 AM 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 north-westbound on [XXX] in the rightmost lane and entered the intersection with [XXX] on a green light. A passenger car traveling south-westbound on [XXX] at a speed well in excess of the posted speed limit entered the intersection without stopping at the red light, and the front of the passenger vehicle made contact with the front passenger side 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 an airbag in an involved vehicle deployed and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-8443 | ADS | Waymo LLC | 2024-08 07:15 | Atlanta, GA | 2024 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 23 | Street | On August [XXX], 2024 at 7:15 AM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling eastbound on […On August [XXX], 2024 at 7:15 AM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] when the front of the Waymo AV made contact with a fallen utility line hanging from a utility pole on the right edge of the roadway into the travel lane and laying on the ground across the left half of the roadway. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. The Waymo AV sustained damage from contact with the non-live line. 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-8444 v3 | ADS | Waymo LLC | 2024-08 17:49 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | Minor | 0 | Street | The content of this report is unchanged from the initial report submitted on August [XXX], 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2024 at 5:49 PM PT a Waymo Autonomous Vehicle ("…The content of this report is unchanged from the initial report submitted on August [XXX], 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2024 at 5:49 PM 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 traveling south-westbound on [XXX] approaching the intersection with [XXX]. As the Waymo AV came to a stop for a traffic stack ahead of the Waymo AV, partially oriented into the dedicated left turn lane at the location where that lane begins, a cyclist merged out of the bike lane and into the general purpose travel lane, and while the cyclist was looking backwards, the front of the bicycle made contact with the rear passenger side of the stopped Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The cyclist remained upright throughout the interaction and alleged that they had sustained an injury. 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-8469 v2 | ADS | Waymo LLC | 2024-08 16:45 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | The content of this report is unchanged from the initial report submitted on August [XXX], 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2024 at 4:45 PM PT a Waymo Autonomous Vehicle (W…The content of this report is unchanged from the initial report submitted on August [XXX], 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2024 at 4:45 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 stopped at a red light in a one-way, one-lane section of northbound [XXX] at the intersection with [XXX] and was preparing to make a right turn onto eastbound [XXX]. While the Waymo AV remained stopped, yielding to pedestrians crossing [XXX], a passenger car that had been stopped behind the Waymo AV passed the Waymo AV on the left. As the passenger car was passing the stopped Waymo AV, the 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. Both vehicles sustained damage and the passenger car left the scene. 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-8471 | ADS | Waymo LLC | 2024-08 23:19 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 4 | Street | On August [XXX], 2024 at 11:19 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 stopped for a red light …On August [XXX], 2024 at 11:19 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 stopped for a red light on northbound [XXX] at the intersection with [XXX] when a passenger car traveling eastbound on [XXX] made a right turn onto [XXX]. As the Waymo AV remained stopped, the oncoming passenger car pulled very close to the Waymo AV in an attempt to pass it in the narrow roadway with parked vehicles on both sides of the street. The Waymo AV then began reversing to create space between itself and the passenger car. As the Waymo AV was reversing, the Waymo AVs driver side front bumper made contact with the passenger cars driver side front bumper. 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.