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 4701 to 4800.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30410-10072 | ADS | Motional | 2025-02 15:00 | Las Vegas, NV | 2024 Hyundai Ioniq 5 | ADS | SUV | No Injuries Reported | 2 | Intersection | Redacted by NHTSA as confidential business information |
| 30410-9804 | ADS | Motional | 2025-02 21:50 | Las Vegas, NV | 2024 Hyundai Ioniq 5 | ADS | Van | No Injuries Reported | 2 | Intersection | Redacted by NHTSA as confidential business information |
| 30410-9857 | ADS | Motional | 2025-02 14:44 | Las Vegas, NV | 2024 Hyundai Ioniq 5 | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30410-9946 | ADS | Motional | 2025-02 15:38 | Las Vegas, NV | 2024 Hyundai Ioniq 5 | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30531-10293 | ADS | Transdev Alternative Services | 2025-02 16:13 | Atlanta, GA | 2024 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 2 | Street | On February [XXX], 2025 at 4:13 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light in the far left t…On February [XXX], 2025 at 4:13 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light in the far left turn lane on westbound [XXX] preparing to make a protected left turn onto [XXX]. As the light at [XXX] turned green, the Waymo AV began to advance through the intersection and came to a stop for a van that was blocking the intersection. While the Waymo AV remained stopped, the front driver side of an SUV in the process of turning left onto [XXX] from the second from the left lane made contact with the rear passenger side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The SUV sustained damage. This is a duplicate of report ID 30270-10148-1. |
| 30571-10171 | ADS | NVIDIA CORP | 2025-02 14:17 | Santa Clara, CA | 2023 Mercedes-Benz S580 4M | Unknown, see Narrative | Passenger Car | No Injuries Reported | 0 | Parking Lot | The Mercedes-Benz vehicle was traveling southbound in a parking lot located at [XXX], Santa Clara, CA 95051 when the driver engaged L3 ADS system for a few seconds. The driver then disengaged L3 ADS and continued to driv…The Mercedes-Benz vehicle was traveling southbound in a parking lot located at [XXX], Santa Clara, CA 95051 when the driver engaged L3 ADS system for a few seconds. The driver then disengaged L3 ADS and continued to drive in conventional mode. The vehicle was manually braked and came to a complete stop. At this time, a Chevrolet Camaro parked perpendicular to the right of the vehicle, reversed from their parking spot and made contact with the right middle panel of the Mercedes-Benz. |
| 30610-10018 v2 | ADS | Zoox, Inc. | 2025-02 15:37 | Las Vegas, NV | 2019 Toyota Highlander | ADS | Passenger Car | Unknown | 0 | Street | A Zoox vehicle (Vehicle 1) in autonomy was stopped behind traffic in the left turn lane (lane 2) for a red traffic signal on [XXX] approaching[XXX] in Las Vegas. At that time, an SUV (Vehicle 2) was attempting to merge o…A Zoox vehicle (Vehicle 1) in autonomy was stopped behind traffic in the left turn lane (lane 2) for a red traffic signal on [XXX] approaching[XXX] in Las Vegas. At that time, an SUV (Vehicle 2) was attempting to merge onto [XXX] from a parking lot on the right when it entered the travel path of a passenger car (Vehicle 3) traveling north on [XXX] in the left through lane (lane 3). The front end of Vehicle 2 struck the front passenger side area of Vehicle 3. Vehicle 3 was redirected to the right after being impacted by Vehicle 2, and it rear-ended the stopped Zoox vehicle. The Zoox vehicle operator then disengaged from autonomy. The Zoox vehicle operator pulled over into a nearby parking lot and returned to the scene to exchange information. The Zoox vehicle sustained minor damage to the rear bumper and exhaust pipe. Vehicle 2 sustained moderate damage to the front end with an airbag deployment and was towed from the scene. Vehicle 3 sustained major damage to the front end and passenger-side front area with multiple airbag deployments and was towed from the scene. Police and EMS were called to the scene, and the driver of Vehicle 3 was transported by an ambulance. The content of this report is unchanged from the initial report and provides complete information to date for this incident. |
| 30610-10055 | ADS | Zoox, Inc. | 2025-02 01:00 | Las Vegas, NV | 2017 Toyota Highlander | ADS | SUV | Minor | 40 | Intersection | A Zoox vehicle (Vehicle 1) in autonomous mode was in the right lane, traveling east on [XXX] in Las Vegas. An SUV (Vehicle 2) to the left of the Zoox vehicle, was traveling ahead in the same direction in the adjacent lan…A Zoox vehicle (Vehicle 1) in autonomous mode was in the right lane, traveling east on [XXX] in Las Vegas. An SUV (Vehicle 2) to the left of the Zoox vehicle, was traveling ahead in the same direction in the adjacent lane. Just as the Zoox vehicle entered the intersection, the SUV suddenly veered right across the path of the Zoox vehicle. The Zoox vehicle braked hard in response to the encroaching SUV, the Zoox vehicle operator then disengaged from autonomy, and shortly after, the front passenger side of the SUV made contact with the front driver side of the Zoox vehicle. The SUV rotated counterclockwise after impact and the rear passenger side of the SUV made contact with the rear driver side of the Zoox vehicle. The SUV sustained major damage with airbag deployment and the Zoox vehicle sustained moderate damage to the driver side. Both vehicles were towed from the scene. The police and EMS arrived at the scene. The Zoox vehicle operator reported "body soreness" and "limping" a few hours after the collision. |
| 30610-10246 | ADS | Zoox, Inc. | 2025-02 21:31 | San Francisco, CA | 2024 Zoox sedan | ADS | Passenger Car | No Injuries Reported | 0 | Street | A Zoox vehicle (Vehicle 1) in autonomous mode was stopped for a red traffic light on westbound [XXX] at the intersection with [XXX] in San Francisco. An SUV (Vehicle 2) traveling directly behind the Zoox vehicle failed t…A Zoox vehicle (Vehicle 1) in autonomous mode was stopped for a red traffic light on westbound [XXX] at the intersection with [XXX] in San Francisco. An SUV (Vehicle 2) traveling directly behind the Zoox vehicle failed to come to a stop and rear-ended the stopped Zoox vehicle. The SUV driver reversed, then left the scene without attempting to exchange information. After the collision, the Zoox vehicle remained stopped, then later cleared the intersection. The Zoox vehicle sustained minor damage to the license plate bracket. There were no reported injuries and the police were not called. The Zoox vehicle camera footage shows the SUV driver was not looking ahead at the roadway before or at the time of contact. |
| 30610-10251 | ADS | Zoox, Inc. | 2025-02 17:34 | San Francisco, CA | 2017 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 26 | Street | A Zoox vehicle (Vehicle 1) in autonomous mode was traveling in lane 4 on southwest-bound [XXX] in San Francisco. At that time a passenger car (Vehicle 2), traveling in the same direction ahead of the Zoox vehicle in the …A Zoox vehicle (Vehicle 1) in autonomous mode was traveling in lane 4 on southwest-bound [XXX] in San Francisco. At that time a passenger car (Vehicle 2), traveling in the same direction ahead of the Zoox vehicle in the right adjacent lane (lane 5), was attempting to go around a cyclist, on the right side, in lane 5. The Zoox vehicle operator disengaged, Vehicle 2 then swerved left into lane 4 across the path of the Zoox vehicle and the driver-side quarter panel on Vehicle 2 contacted the passenger-side fender and front door of the Zoox vehicle. Both vehicles proceeded a few feet further and pulled over to exchange information. Vehicle 2 appeared to sustain minor damage and the Zoox vehicle did not sustain any damage. There were no reported injuries and the police were not called. |
| 30791-10003 | ADS | AutoX Technologies Inc | 2025-02 18:31 | Santa Clara, CA | 2020 Chrysler Pacifica | ADS | Passenger Car | No Injuries Reported | 16 | Street | On Feb [XXX], 2025 at 06:31 PM PT, the blind spot sensor pod of our autonomous vehicle (AV) made contact with a parked passenger car on [XXX], Santa Clara, CA. The AV was making a right turn along the[XXX], traveling at …On Feb [XXX], 2025 at 06:31 PM PT, the blind spot sensor pod of our autonomous vehicle (AV) made contact with a parked passenger car on [XXX], Santa Clara, CA. The AV was making a right turn along the[XXX], traveling at 16 mph. Due to an inaccurate map version downloaded on the AV causing the AV to drive close to the parked vehicles on the side of the street, the safety driver disengaged the AV. After disengagement, the right side sensor pod of the AV made contact with the left side rear view mirror of a passenger vehicle parked on the side of the Kingsbury Cir. At the time of the impact, the AV's Level 4 ADS was not engaged and the safety driver was operating the AV in manual mode. Both vehicles sustained minor damage. |
| 540-13555 | Level 2 | General Motors, LLC | 2025-02 6:31 | Sand Springs, OK | 2025 GMC Sierra | Verified Engaged | Pickup Truck | Minor W/ Hospitalization | 54 | Highway / Freeway | On February [XXX], 2025, a 2025 GMC Sierra was travelling eastbound in the left lane on [XXX] in Sand Springs, Oklahoma, with Super Cruise engaged and active. Crash data indicates a frontal impact occurred that deployed…On February [XXX], 2025, a 2025 GMC Sierra was travelling eastbound in the left lane on [XXX] in Sand Springs, Oklahoma, with Super Cruise engaged and active. Crash data indicates a frontal impact occurred that deployed the driver's frontal airbag and activated the front seat belt pretensioners. According to OnStar audio recordings, the driver reported that a vehicle entered his lane from an adjacent road on the right. The driver was wearing their seat belt at the time of the crash. Telematic data, which GM received on December 23, 2025, indicates that Super Cruise changed to "Disable/Not Ready" 0.4 seconds prior to the crash due to a driver brake apply. An obtained police report indicates that the other vehicle failed to yield to the subject vehicle when turning southbound onto[XXX]. |
| 540-9813 | Level 2 | General Motors, LLC | 2025-02 09:15 | New Haven, IN | 2024 GMC Acadia | ADAS | Other Fixed Object | Unknown | 58 | Highway / Freeway | On February [XXX], 2025, a 2024 GMC Acadia was traveling northeast on [XXX], in New Haven, Indiana with Super Cruise engaged and active. According to OnStar audio recordings, the driver indicated they lost control of th…On February [XXX], 2025, a 2024 GMC Acadia was traveling northeast on [XXX], in New Haven, Indiana with Super Cruise engaged and active. According to OnStar audio recordings, the driver indicated they lost control of the vehicle and hit the center cement highway barrier. Crash data indicates a frontal impact that deployed the airbags and front seat belt pretensioners. The driver and front passenger were wearing their seat belts at the time of crash. Vehicle data shows that approximately 15 seconds prior to the crash, Super Cruise entered a Disabled/Not Ready state due to a driver take over of the vehicle with a brake pedal press. |
| 669-10257 | ADS | Hyundai Motor America | 2025-02 21:50 | Las Vegas, NV | 2024 Hyundai IONIQ 5 | ADS | Van | No Injuries Reported | 2 | Intersection | In collaboration with Motional, below is a summary based on their statement: On February [XXX], 2025, at approximately 9:50 PM PT, a Motional AV with VIN PFDKB4AE3RF[XXX] was operating in autonomous mode in Las Vegas, Ne…In collaboration with Motional, below is a summary based on their statement: On February [XXX], 2025, at approximately 9:50 PM PT, a Motional AV with VIN PFDKB4AE3RF[XXX] was operating in autonomous mode in Las Vegas, Nevada. The vehicle was stopped in a left-turn lane on [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], preparing to turn left onto [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. A safety driver was in the driver's seat, and an engineer was in the front passenger seat. When the light turned from red to a left green arrow, the AV began making a left turn onto [XXX] when a vehicle, two cars behind the AV, rear-ended the cargo van immediately behind the AV, causing the cargo van to rear-end the AV at approximately 2-5 MPH. Following the impact, the safety driver assumed control of the AV and pulled over safely to the side of Russell Road. No injuries were reported in any of the vehicles, and no airbags deployed. The AV sustained damage to its rear bumper. Both vehicles remained drivable and departed the scene under their own power. Law enforcement was not contacted at the time of the incident if a police report becomes available, a copy will be provided. |
| 669-10258 | ADS | Hyundai Motor America | 2025-02 14:44 | Las Vegas, NV | 2024 Hyundai IONIQ 5 | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | In collaboration with Motional, below is a summary based on their statement: On February [XXX], 2025, at 2:44 PM PT, a Motional AV with VIN PFDKB4AE1RF[XXX] was operating in autonomous mode in Las Vegas, Nevada. A safety…In collaboration with Motional, below is a summary based on their statement: On February [XXX], 2025, at 2:44 PM PT, a Motional AV with VIN PFDKB4AE1RF[XXX] was operating in autonomous mode in Las Vegas, Nevada. A safety driver was in the driver's seat, and a test engineer was in the front passenger seat. The AV was traveling [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], preparing to make a right turn onto [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. While in the right-turn lane, the AV came to a complete stop at a yield sign and a truck rear-ended the AV at approximately 5-10 MPH. Following the impact, the safety driver assumed control of the vehicle and, after a brief conversation with the truck driver, pulled into a nearby gas station to exchange information. No injuries were reported by any of the vehicle occupants, and no airbags deployed. The AV sustained damage to the trunk and rear camera. All vehicles remained drivable and left the scene under their own power without needing a tow truck. Law enforcement was not contacted at the time of the incident however, if a police report becomes available, a copy will be provided. |
| 669-10259 | ADS | Hyundai Motor America | 2025-02 15:38 | Las Vegas, NV | 2024 Hyundai IONIQ 5 | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 669-10260 | ADS | Hyundai Motor America | 2025-02 15:00 | Las Vegas, NV | 2024 Hyundai IONIQ 5 | ADS | SUV | No Injuries Reported | 2 | Intersection | In collaboration with Motional, below is a summary based on their statement: On February [XXX], 2025, at 3:00 PM PT, a Motional AV with VIN PFDKB4AE1RF[XXX] was operating in autonomous mode in Las Vegas, Nevada. A safety…In collaboration with Motional, below is a summary based on their statement: On February [XXX], 2025, at 3:00 PM PT, a Motional AV with VIN PFDKB4AE1RF[XXX] was operating in autonomous mode in Las Vegas, Nevada. A safety driver was in the driver's seat, a test engineer was in the passenger seat, and one Motional employee was in the backseat. The AV was traveling [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], preparing to make a right turn onto [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. While in the right-turn lane, the AV was slowing to stop at a yield sign for cross traffic, and a Cadilac SUV rear-ended the AV at approximately 1-5 MPH. Following the impact, the safety driver assumed control of the vehicle and pulled safety over to exchange information. No injuries were reported by any of the vehicle occupants, and no airbags deployed. The AV sustained damage to the trunk. All vehicles remained drivable and left the scene under their own power without needing a tow truck. Law enforcement was not contacted at the time of the incident however, if a police report becomes available, a copy will be provided |
| 669-9902 | Level 2 | Hyundai Motor America | 2025-02 06:15 | Corona, CA | 2024 Hyundai IONIQ 6 | ADAS | Other, see Narrative | Minor | 0 | Highway / Freeway | A Hyundai Motor America ("HMA") associate was operating a model year 2024 Ioniq 6 employee lease vehicle with the vehicle's Adaptive Cruise Control ("ACC"), and Lane Following Assist ("LFA") features engaged simultaneous…A Hyundai Motor America ("HMA") associate was operating a model year 2024 Ioniq 6 employee lease vehicle with the vehicle's Adaptive Cruise Control ("ACC"), and Lane Following Assist ("LFA") features engaged simultaneously while driving at approximately 20-30MPH on [XXX]near Corona, CA. The ACC allegedly engaged due to traffic slowing down and proceeded to slow the vehicle to a stop when the IONIQ 6 vehicle was struck in the rear by a Hyundai Elantra that had been rear-ended and pushed forward into the IONIQ 6 vehicle. NASO is in process of reaching out to the associate for additional information. |
| 753-10358 v3 | Level 2 | Kia America, Inc. | 2025-02 15:14 | Hermiston, OR | 2023 KIA NIRO | ADAS | SUV | Minor | 65 | Highway / Freeway | The owner of a 2023MY Kia Niro contacted Kia's Customer Care Center on March [XXX], 2025 indicating he was involved in a collision, the airbag did not deploy, and the vehicle's front end sensor went off, but the vehicle …The owner of a 2023MY Kia Niro contacted Kia's Customer Care Center on March [XXX], 2025 indicating he was involved in a collision, the airbag did not deploy, and the vehicle's front end sensor went off, but the vehicle did not stop. The owner reported no injuries on the March [XXX] call. In a subsequent email communication on March 27, 2025, the owner reported he "had the cruise set at 58mph in a 55mph zone. Just before the next intersecting road [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]ell road [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] had sneezed and it often causes me to close my eyes. I had become drowsy and dozed off. At this moment I struck the vehicle in front of me." The subject vehicle's side "headlamp area collided with a 2020 Dodge Durango striking them in the rear passenger area." The owner alleges that a "warning light and sound activated, but the cars collision prevention system did not activate and stop the car before the impact was made," and that the airbags did not deploy. In the March 27 email, the owner reported receiving unspecified "neck, back and head" pains after the incident. The subject Kia Niro is equipped with Highway Driving Assist (HDA), Lane Following Assist (LFA) 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 traffc situations and may not detect possible collisions due to limitations of the system. LFA is also a supplemental system that helps to detect lane markings and/or vehicles on the road, and assists the driver's steering to help keep the vehicle between lanes. LFA does not operate at all times and it is the responsibility of the driver to safely steer the vehicle and to maintain the vehicle in its lane. It appears based on the owner's report that he was asleep at the time of the crash. Kia is working to inspect the vehicle, but has no further information at this time. *** 4/15/2025 Monthly Update *** On 4/14/2025, Kia submitted an email response to Mr. Teitelman's inquiry and requested for NHTSA's SLFTS link to upload currently available material. *** 5/15/2025 Monthly Update *** As communicated to NHTSA ODI engineer Mr. Teitelman on 4/16/2025, Kia extracted the EDR from the subject vehicle on 4/15/2025, which showed that the vehicle was not operating at ADAS Level 2 because Smart Cruise Control was not engaged nor turned on. |
| 855-10223 | ADS | Mercedes-Benz USA, LLC | 2025-02 14:17 | Santa Clara, CA | 2022 Mercedes-Benz S 580 4MATIC | Unknown, see Narrative | Passenger Car | No Injuries Reported | 0 | Parking Lot | The subject Mercedes-Benz vehicle was driving in the back parking lot of the [XXX] in Santa Clara, CA (parallel to the [XXX]). The Mercedes-Benz vehicle was driven in conventional mode when the driver engaged L3 ADS for …The subject Mercedes-Benz vehicle was driving in the back parking lot of the [XXX] in Santa Clara, CA (parallel to the [XXX]). The Mercedes-Benz vehicle was driven in conventional mode when the driver engaged L3 ADS for a few seconds. The driver then disengaged L3 ADS and continued to drive in conventional mode. The vehicle was manually braked to a stop adjacent to vehicles parked in the parking lot, and perpendicular to a parked Chevrolet Camaro. The driver in the Mercedes-Benz then shifted into Park ("P") via the gearshift lever. While the Mercedes-Benz vehicle was stopped, the Chevrolet Camaro reversed out of its parking space and contacted the Mercedes-Benz vehicle at the right rear door. As a result, the right rear corner of the Chevrolet Camaro and the right rear passenger door of the Mercedes-Benz vehicle sustained minor damage. There were no reported injuries to any of the occupants. |
| 988-9975 | ADS | PACCAR Incorporated | 2025-02 19:08 | Thackerville, OK | 2020 Kenworth T680 | ADS | Heavy Truck | No Injuries Reported | 56 | Highway / Freeway | On February [XXX]at 7:08 PM CT, a tractor-trailer encroached into the lane of a Kodiak Driver-equipped autonomous truck traveling Northbound on [XXX]in Thackerville, Oklahoma. The other tractor-trailer was overtaking Kod…On February [XXX]at 7:08 PM CT, a tractor-trailer encroached into the lane of a Kodiak Driver-equipped autonomous truck traveling Northbound on [XXX]in Thackerville, Oklahoma. The other tractor-trailer was overtaking Kodiaks truck in the left lane and three-quarters of their truck was past when it veered out of the left lane into the lane occupied by Kodiak and made light contact with the Kodiak trucks drivers side mirror/SensorPod. The area where this occurred was a construction zone with concrete barrier eliminating the right road shoulder preventing the Kodiak truck driver from being able to make a defensive maneuver to avoid the contact. The driver of the other tractor-trailer continued down the road without stopping. No material property damage occurred, just surface abrasion to the drivers side SensorPod. There were no injuries reported, and no vehicles were towed from the scene. |
| 1306-9766 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2025-01 18:00 | Lake Worth, FL | 2022 Toyota Camry | ADAS | Other, see Narrative | No Injuries Reported | 40 | Unknown | The entry below were submitted on January [XXX], 2025, based on unconfirmed allegations: On January [XXX], 2025, Toyota received an initial contact from the driver of a vehicle involved in a crash in which, "she was driv…The entry below were submitted on January [XXX], 2025, based on unconfirmed allegations: On January [XXX], 2025, Toyota received an initial contact from the driver of a vehicle involved in a crash in which, "she was driving and the vehicle suddenly shifted to the left and then the right and then the left toward a barrier and the vehicle flipped over." The driver also alleged that, "the sensors on the vehicle detected a vehicle near her pushing her to the other lane." She stated cruise control was engaged and that the cruise control and lane keep assist possibly caused the crash. The crash scene was described as, "in front of a [XXX]on[XXX]in Lake Worth, FL." The crash scene was also described as having heavy traffic, construction cones and construction in the area, and a bumpy road. Descriptions of the crash result included front driver and passenger airbag deployment, "entire vehicle damage", a tow-away from the scene, and no injuries. The driver also stated that other vehicles were involved but no damage occurred to those vehicles. The entry below is based on Toyota's vehicle inspection and data recovery from the subject vehicle and incident: On February [XXX], 2025 Toyota completed a field report based on inspection of the subject vehicle. The field report contained EDR and PCS Freeze Frame Data (PCS FFD) from the crash event. The PCS FFD showed that dynamic radar cruise control (DRCC) was not engaged in the recorded moments leading to the crash event. Based on this evidence, Toyota determined this crash event is not reportable under SGO 2021-01, and will not continue updating the submission. |
| 13781-10005 v2 | Level 2 | Tesla, Inc. | 2025-01 6:12 | Torrance, CA | 2025 Tesla Model Y | Unknown, see Narrative | Unknown | Fatality | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-10146 v3 | Level 2 | Tesla, Inc. | 2025-01 14:58 | Frisco, TX | 2021 Tesla Model S | ADAS | Non-Motorist: Cyclist | Unknown | 4 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-13432 | Level 2 | Tesla, Inc. | 2025-01 04:14 | Houston, TX | 2024 TESLA Model 3 | Verified Engaged | Unknown | Serious W/ Hospitalization | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-9617 | Level 2 | Tesla, Inc. | 2025-01 08:25 | Frisco, TX | 2024 Tesla Model 3 | ADAS | Unknown | Unknown | 925 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9618 | Level 2 | Tesla, Inc. | 2025-01 22:40 | Tulsa, OK | 2025 Tesla Model Y | ADAS | Other Fixed Object | No Injuries Reported | 4 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9620 | Level 2 | Tesla, Inc. | 2025-01 11:03 | San Antonio, TX | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 75 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9621 | Level 2 | Tesla, Inc. | 2025-01 03:32 | Tampa, FL | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 59 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9622 | Level 2 | Tesla, Inc. | 2025-01 06:31 | Webster, TX | 2023 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-9623 v2 | Level 2 | Tesla, Inc. | 2025-01 18:12 | Jupiter, FL | 2025 Tesla Model 3 | ADAS | Unknown | Unknown | 15 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9624 | Level 2 | Tesla, Inc. | 2025-01 09:31 | Crystal Lake, IL | 2023 Tesla Model 3 | ADAS | Unknown | Unknown | 32 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9626 | Level 2 | Tesla, Inc. | 2025-01 22:06 | Milpitas, CA | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 20 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9627 | Level 2 | Tesla, Inc. | 2025-01 02:36 | Malvern, PA | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 40 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9628 | Level 2 | Tesla, Inc. | 2025-01 17:43 | Pittsburgh, PA | 2024 Tesla Model Y | ADAS | Passenger Car | No Injuries Reported | 25 | Street | Redacted by NHTSA as confidential business information |
| 13781-9644 v2 | Level 2 | Tesla, Inc. | 2025-01 03:40 | Orlando, FL | 2024 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 34 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9645 | Level 2 | Tesla, Inc. | 2025-01 04:55 | Los Angeles, CA | 2024 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9646 | Level 2 | Tesla, Inc. | 2025-01 23:44 | FL | 2024 Tesla Model Y | Unknown, see Narrative | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9647 | Level 2 | Tesla, Inc. | 2025-01 06:00 | Renton, WA | 2020 Tesla Model Y | ADAS | SUV | Unknown | 35 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9648 v2 | Level 2 | Tesla, Inc. | 2025-01 17:14 | Los Angeles, CA | 2024 Tesla Cybertruck | ADAS | Van | Unknown | 17 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-9716 v2 | Level 2 | Tesla, Inc. | 2025-01 04:58 | Tacoma, WA | 2021 Tesla Model X | ADAS | Unknown | Unknown | 50 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9717 | Level 2 | Tesla, Inc. | 2025-01 05:25 | Chino, CA | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 68 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9718 | Level 2 | Tesla, Inc. | 2025-01 05:58 | Sacramento, CA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9731 | Level 2 | Tesla, Inc. | 2025-01 18:54 | Kansas City, MO | 2023 Tesla Model Y | ADAS | SUV | Unknown | 7 | Street | Redacted by NHTSA as confidential business information |
| 13781-9742 | Level 2 | Tesla, Inc. | 2025-01 17:08 | Rosemead, CA | 2024 Tesla Model 3 | ADAS | Unknown | Unknown | 61 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9743 | Level 2 | Tesla, Inc. | 2025-01 00:14 | Twentynine Palms, CA | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 43 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9744 | Level 2 | Tesla, Inc. | 2025-01 04:10 | Franklin Square, NY | 2024 Tesla Model 3 | ADAS | Unknown | Unknown | 63 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9745 | Level 2 | Tesla, Inc. | 2025-01 22:31 | Enfield, CT | 2024 Tesla Model X | ADAS | Unknown | Unknown | 36 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9746 | Level 2 | Tesla, Inc. | 2025-01 01:26 | Pleasanton, CA | 2018 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 34 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9747 | Level 2 | Tesla, Inc. | 2025-01 10:26 | Hanover, MD | 2023 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 17 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-9749 | Level 2 | Tesla, Inc. | 2025-01 21:23 | Chicago, IL | 2025 Tesla Model Y | ADAS | Passenger Car | Unknown | 1 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9750 | Level 2 | Tesla, Inc. | 2025-01 20:16 | San Francisco, CA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 17 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-9756 | Level 2 | Tesla, Inc. | 2025-01 13:53 | Beaver Falls, PA | 2023 Tesla Model S | ADAS | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9757 | Level 2 | Tesla, Inc. | 2025-01 13:42 | Daytona Beach, FL | 2025 Tesla Model Y | ADAS | Unknown | Unknown | 52 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9758 v2 | Level 2 | Tesla, Inc. | 2025-01 09:31 | Newark, CA | 2023 Tesla Model 3 | ADAS | Passenger Car | Fatality | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9769 v3 | Level 2 | Tesla, Inc. | 2025-01 02:40 | Little Canada, MN | 2024 TESLA Model Y | Verified Engaged | Van | Unknown | 55 | Street | Redacted by NHTSA as confidential business information |
| 13781-9781 | Level 2 | Tesla, Inc. | 2025-01 00:09 | Lewisville, TX | 2024 Tesla Model 3 | ADAS | Unknown | Unknown | 62 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9782 | Level 2 | Tesla, Inc. | 2025-01 07:38 | Pottstown, PA | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-9783 | Level 2 | Tesla, Inc. | 2025-01 16:09 | Fairfield, CA | 2021 Tesla Model 3 | ADAS | Passenger Car | Unknown | 66 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9784 | Level 2 | Tesla, Inc. | 2025-01 12:11 | Terra Ceia, FL | 2020 Tesla Model X | ADAS | Passenger Car | Unknown | 5 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9785 | Level 2 | Tesla, Inc. | 2025-01 15:13 | Drums, PA | 2024 Tesla Model Y | ADAS | Unknown | Unknown | 62 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9786 | Level 2 | Tesla, Inc. | 2025-01 16:42 | El Dorado Hills, CA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9796 | Level 2 | Tesla, Inc. | 2025-01 05:57 | San Francisco, CA | 2022 Tesla Model Y | ADAS | Unknown | No Injuries Reported | 14 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9797 | Level 2 | Tesla, Inc. | 2025-01 18:08 | NY | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 44 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9798 | Level 2 | Tesla, Inc. | 2025-01 05:21 | Hallandale, FL | 2021 Tesla Model S | Unknown, see Narrative | Unknown | No Injuries Reported | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-9799 | Level 2 | Tesla, Inc. | 2025-01 17:17 | Burlingame, CA | 2023 Tesla Model X | ADAS | Unknown | No Injuries Reported | 30 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9801 | Level 2 | Tesla, Inc. | 2025-01 15:42 | Moriches, NY | 2025 Tesla Model 3 | ADAS | Unknown | Unknown | 29 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9802 | Level 2 | Tesla, Inc. | 2025-01 14:46 | Lodi, CA | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 26 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-9803 | Level 2 | Tesla, Inc. | 2025-01 12:56 | Atlanta, GA | 2022 Tesla Model 3 | ADAS | Unknown | Unknown | 64 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9836 | Level 2 | Tesla, Inc. | 2025-01 15:06 | Rogers, AR | 2025 Tesla Model 3 | ADAS | Unknown | Unknown | 32 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9837 | Level 2 | Tesla, Inc. | 2025-01 19:38 | Maumee, OH | 2019 Tesla Model X | ADAS | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9838 | Level 2 | Tesla, Inc. | 2025-01 22:43 | Haydenville, MA | 2023 Tesla Model 3 | ADAS | Unknown | Unknown | 23 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9839 | Level 2 | Tesla, Inc. | 2025-01 11:12 | Alpharetta, GA | 2022 Tesla Model S | ADAS | Pole / Tree | Unknown | 34 | Traffic Circle | Redacted by NHTSA as confidential business information |
| 13781-9930 | Level 2 | Tesla, Inc. | 2025-01 20:31 | Plano, TX | 2016 Tesla Model S | ADAS | Unknown | Unknown | 32 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-9996 v2 | Level 2 | Tesla, Inc. | 2025-01 16:37 | Hollister, CA | 2022 Tesla Model 3 | ADAS | Other Fixed Object | No Injuries Reported | 8 | Parking Lot | Redacted by NHTSA as confidential business information |
| 29990-9652 | Level 2 | Rivian Automotive, LLC | 2025-01 10:33 | Garfield Heights, OH | 2024 Rivian R1T | ADAS | SUV | No Injuries Reported | 60 | Highway / Freeway | On January [XXX], 2025, at approximately 10:33 AM ET the subject vehicle was traveling straight with highway assist (HWA) engaged at a speed of approximately 60 mph in the far right lane. According to the police report a…On January [XXX], 2025, at approximately 10:33 AM ET the subject vehicle was traveling straight with highway assist (HWA) engaged at a speed of approximately 60 mph in the far right lane. According to the police report and as shown in the rear facing video recorded by the Rivian an SUV rapidly approached the Rivian from behind and made an unsafe lane change, striking the left rear quarter panel of the Rivian in the process. Rivian agrees with the assessment of the police report that the unsafe lane change of the other driver was the cause of the accident. The HWA system was not a contributing factor to the incident. |
| 30270-10089 | ADS | Waymo LLC | 2025-01 21:14 | Los Angeles, CA | 2024 Jaguar I-PACE | ADS | SUV | Minor | 28 | Street | On January [XXX], 2025 at 9:14 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX]. The Waymo AV was travelling eastbound on [XXX] in the center…On January [XXX], 2025 at 9:14 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX]. The Waymo AV was travelling eastbound on [XXX] in the center lane when an SUV travelling eastbound in the opposing travel lanes began to approach the Waymo AV from behind and to the left. The SUV then began to maneuver into the left eastbound travel lane, and continued into the center lane occupied by the Waymo AV, and the front passenger side of the SUV made contact with the drivers side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Neither vehicle sustained damage. On February 5, 2025, Waymo received an allegation of a minor injury from the passenger in the Waymo AV. 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-9537 | ADS | Waymo LLC | 2025-01 22:48 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 10:48 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 parked at the curb fa…On January [XXX], 2025 at 10:48 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 parked at the curb facing east on [XXX] when a passenger car traveling east on [XXX] passed the Waymo AV. As the passenger car passed the parked Waymo AV, the sideview mirror on the passenger side of the passenger car made contact with the sideview mirror on 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. The Waymo AV sustained damage and the passenger car left the scene. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01. A vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9552 | ADS | Waymo LLC | 2025-01 20:34 | Austin, TX | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 8:34 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound in the left h…On January [XXX], 2025 at 8:34 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound in the left hand turn lane on [XXX] and stopped in a queue of traffic at a red light. A passenger car traveling directly in front of the Waymo AV started to reverse backwards towards the Waymo AV. The Waymo AV began to reverse to avoid the passenger car, then slowed to a stop. The passenger car continued to reverse and the rear of the passenger car 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. 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-9565 | ADS | Waymo LLC | 2025-01 08:09 | Culver City, CA | 2024 JLR I-PACE | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 8:09 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Culver City, California was in a collision involving a heavy truck (garbage truck) near [XXX]. The Waymo AV was traveling northeast…On January [XXX], 2025 at 8:09 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Culver City, California was in a collision involving a heavy truck (garbage truck) near [XXX]. The Waymo AV was traveling northeast on [XXX] when it came to a stop to yield to an oncoming garbage truck in a narrow roadway with parked vehicles on both sides of the street. As the oncoming garbage truck passed the stopped Waymo AV, the driver side of the garbage truck 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 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-9606 | ADS | Waymo LLC | 2025-01 09:21 | San Francisco, CA | 2024 JLR I-PACE | ADS | Heavy Truck | No Injuries Reported | 1 | Street | On January [XXX], 2025 at 9:21 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped on northwest [XX…On January [XXX], 2025 at 9:21 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped on northwest [XXX] for a passenger drop off, with a heavy truck parked directly in front of it. After the Waymo AV completed the passenger drop off, the operator of the heavy truck began to lower the loading ramp attached to the rear of the heavy truck. The Waymo AV then proceeded to enter the rightmost lane of northwest [XXX] to maneuver around the left side of the heavy truck, but immediately came to a stop to yield to an SUV that was approaching in the rightmost lane. The Waymo AV then began to nudge to the left of the heavy truck at a low rate of speed as the ramp on the heavy truck continued to lower. As the Waymo AV was proceeding forward, the left corner of the ramp made contact with the passenger side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV 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-9631 v2 | ADS | Waymo LLC | 2025-01 14:55 | Phoenix, AZ | 2024 Jaguar I-Pace | ADS | Passenger Car | Minor | 15 | Intersection | The content of this report is unchanged from the initial report submitted on January 10, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2025 at 2:55 PM MT a Waymo Autonomous Vehicle (W…The content of this report is unchanged from the initial report submitted on January 10, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2025 at 2:55 PM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] when it approached the intersection with [XXX]. As the Waymo AV approached the intersection, it slowed to yield to a pedestrian who was traveling south on the sidewalk of [XXX] and had just entered the intersection to cross [XXX]. As the Waymo AV continued to slow, a passenger car traveling directly behind the Waymo AV approached the Waymo AV from behind. 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. Both vehicles sustained damage. The passenger in the Waymo AV reported a minor injury. 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 and because vehicles involved were towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9634 | ADS | Waymo LLC | 2025-01 16:04 | Phoenix, AZ | 2024 JLR I-PACE | ADS | Passenger Car | Moderate | 2 | Intersection | On January [XXX], 2025 at 4:04 PM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling in the rightmost lane o…On January [XXX], 2025 at 4:04 PM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling in the rightmost lane of northbound [XXX] when it entered the dedicated right turn lane as it approached the intersection with [XXX]. The Waymo AV slowed to a stop to yield to traffic traveling east on [XXX] as it prepared to make a right turn onto [XXX]. As the Waymo AV initiated a right turn onto eastbound [XXX], a passenger car traveling directly behind the Waymo AV approached the Waymo AV from behind. The front passenger side of the passenger car made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The passenger in the Waymo AV reported a moderate injury. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-0 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9635 | ADS | Waymo LLC | 2025-01 08:17 | San Francisco, CA | 2024 Jaguar I-PACE | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 8:17 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 in the leftmos…On January [XXX], 2025 at 8:17 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 in the leftmost lane of westbound [XXX] when it slowed to a stop to yield to traffic ahead of it in the same lane. While the Waymo AV remained stopped, a passenger car traveling directly behind the Waymo AV approached the Waymo AV from behind. The front driver side of the passenger car made contact with the rear passenger side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9654 v2 | ADS | Waymo LLC | 2025-01 15:32 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Intersection | The content of this report is unchanged from the initial report submitted on January 14, 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2025 at 3:32 PM PT a Waymo Autonomous Vehicle ("…The content of this report is unchanged from the initial report submitted on January 14, 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2025 at 3:32 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 northbound on [XXX] in the rightmost lane, and came to a stop for a red light at the intersection with [XXX]. While the Waymo AV remained stopped at the intersection, a cyclist traveling southbound against traffic proceeded through the intersection, passing the Waymo AV on the left, and the cyclist made contact with the driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-9721 | ADS | Waymo LLC | 2025-01 13:12 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 1 | Intersection | On January [XXX], 2025 at 1:12 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX], …On January [XXX], 2025 at 1:12 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX], approaching the five-way series of intersections with [XXX], [XXX], and [XXX] in order to proceed on [XXX]. The Waymo AV proceeded straight past the intersection where [XXX] intersects [XXX], with an SUV following behind. Then, the traffic light turned red before the Waymo AV began to cross [XXX]. The Waymo AV began slowing to stop within the crosswalk along [XXX], and the front of the trailing SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-9724 v2 | ADS | Waymo LLC | 2025-01 18:07 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Passenger Car | Fatality | 0 | Street | Since the initial report [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] was submitted on January 20, 2025, the content of the report has been clarified with changes pertaining to the other vehicles involved an…Since the initial report [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] was submitted on January 20, 2025, the content of the report has been clarified with changes pertaining to the other vehicles involved and the zip code at which the collision occurred. On January [XXX], 2025 at 6:07 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger vehicle near the intersection of [XXX] and [XXX]. The Waymo AV, which had no occupants, was traveling northwestbound in the middle of three lanes on [XXX] and came to a stop in a queue of traffic. Shortly after, a passenger vehicle came to a stop behind the Waymo AV. While the Waymo AV and the other passenger vehicle were stopped, an SUV approached from behind at an extreme rate of speed and made contact with the passenger vehicle behind the Waymo AV, which then made contact with the rear bumper of the Waymo AV. According to the San Francisco Police Department, the Waymo AV then began to rotate clockwise and, as it was rotating, the front of the SUV made contact with the passenger side of the Waymo AV. The rear of the Waymo AV then made contact with the rear driver side corner of another passenger car that had just begun to proceed straight on northbound [XXX]. According to the San Francisco Police Department, at least two other vehicles were involved in the crash and one of the occupants of the vehicles involved in the crash and a domestic animal were declared deceased at the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV, the passenger vehicle behind the Waymo AV, and the SUV sustained severe damage. The extent of the damage to the other three vehicles is currently unknown. Waymo received notice that five passengers in four of the vehicles involved sustained injuries of varying severity. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because of a fatality. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9735 | ADS | Waymo LLC | 2025-01 06:42 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 21 | Street | On January [XXX], 2025 at 6:42 AM 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 proceeding south on [XX…On January [XXX], 2025 at 6:42 AM 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 proceeding south on [XXX] when a passenger car in front of the Waymo AV entered the two-way center turn lane on its left. As the Waymo AV neared the passenger car, the passenger car began to maneuver out of the center turn lane and re-enter the singular lane of [XXX]. The passenger side of the passenger car then made contact with the 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. 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-9736 | ADS | Waymo LLC | 2025-01 22:39 | Scottsdale, AZ | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On January [XXX], 2025 at 10:39 PM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped at a stop sign facing …On January [XXX], 2025 at 10:39 PM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped at a stop sign facing east in the rightmost of two lanes on [XXX] at the intersection with [XXX]. While the Waymo AV remained stopped, a passenger car traveling partially in the rightmost lane and partially in the left-adjacent dedicated left turn lane approached the Waymo AV from behind. 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 stationary 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-9737 | ADS | Waymo LLC | 2025-01 03:59 | Los Angeles, CA | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 3:59 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing northea…On January [XXX], 2025 at 3:59 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing northeast on [XXX] after a passenger drop off. While the Waymo AV remained stopped, a passenger car approached the Waymo AV from behind. The front of the passenger car then made contact with the rear driver 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 a vehicle involved was towed away and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9738 | ADS | Waymo LLC | 2025-01 02:12 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 2:12 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 stopped for a red ligh…On January [XXX], 2025 at 2:12 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 stopped for a red light on westbound [XXX] when a passenger car traveling at a high rate of speed approached the Waymo AV from behind. The front of the passenger car then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because vehicles involved were towed away and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9761 v2 | ADS | Waymo LLC | 2025-01 14:02 | Mesa, AZ | 2024 Jaguar I-Pace | ADS | Motorcycle | Minor | 0 | Intersection | The content of this report is unchanged from the initial report submitted on January[XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2025 at 2:02 PM MT a Waymo Autonomous Vehicle …The content of this report is unchanged from the initial report submitted on January[XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2025 at 2:02 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving a motorcycle on [XXX]. The Waymo AV was stopped facing [XXX] at the intersection with [XXX]at a red light. A motorcycle was stopped behind the Waymo AV, and a pickup truck was stopped behind the motorcycle. A passenger car approached the queue of stopped traffic from behind and made contact with the stopped pickup truck, which was pushed into the motorcycle. The motorcycle then made contact with the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The motorcyclist was treated at the scene for an apparent injury. 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-9763 | ADS | Waymo LLC | 2025-01 22:48 | Los Angeles, CA | 2024 Jaguar I-PACE | ADS | Other, see Narrative | No Injuries Reported | 9 | Parking Lot | On January [XXX], 2025 at 10:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California made contact with the pavement at the elevated entrance of a parking lot near [XXX]. The Waymo AV was…On January [XXX], 2025 at 10:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California made contact with the pavement at the elevated entrance of a parking lot near [XXX]. The Waymo AV was traveling westbound on [XXX] and turning left into a parking lot for a passenger pickup. As the Waymo AV turned into the parking lot, the Waymo AV's undercarriage made contact with the raised pavement of the sidewalk and the paved entrance to the parking lot. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Waymo became aware that the Waymo AV sustained damage resulting in a tow at 12:40 AM PT on January 25th, 2025. 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-9764 | ADS | Waymo LLC | 2025-01 02:22 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | SUV | No Injuries Reported | 17 | Street | On January [XXX], 2025 at 2:22 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 northbound on a nar…On January [XXX], 2025 at 2:22 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 northbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions. As the Waymo AV passed a SUV double parked facing southbound on [XXX], the rear driver side door of the SUV opened and 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. 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-9765 | ADS | Waymo LLC | 2025-01 18:53 | Los Angeles, CA | 2024 Jaguar I-PACE | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 6:53 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on the 1500 block of [XXX] near [XXX]. The Waymo AV was trav…On January [XXX], 2025 at 6:53 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on the 1500 block of [XXX] near [XXX]. The Waymo AV was traveling south in the second to the right lane on [XXX] and came to a stop in a queue of traffic. A passenger car approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-9767 | ADS | Waymo LLC | 2025-01 23:28 | Los Angeles, CA | 2024 Jaguar I-PACE | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 11:28 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in …On January [XXX], 2025 at 11:28 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the second from the right lane on East [XXX] and came to a stop for a red light at the intersection of [XXX]. A passenger car approached the Waymo AV from behind, did not appreciably slow down, and the front of the passenger car made contact with the rear driver 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 a vehicle involved was towed away and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-9791 | ADS | Waymo LLC | 2025-01 09:53 | San Francisco, CA | 2024 Jaguar I-PACE | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2025 at 9:53 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was stopped at a red ligh…On January [XXX], 2025 at 9:53 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was stopped at a red light in the rightmost lane of southbound [XXX], preparing to make a right turn onto westbound [XXX]. The light turned green and the Waymo AV remained stopped as it was calculating a turn trajectory around a parked car on the north side of [XXX]. A passenger car that had been stopped behind the Waymo AV attempted to change lanes into the left adjacent lane to maneuver around the Waymo AV, and as the passenger car maneuvered around the Waymo AV, another passenger car was proceeding straight in the same left lane. The front left side of the passenger car that had been behind the Waymo AV made contact with the right side of the other passenger car and then made contact with the left part of the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-9806 | ADS | Waymo LLC | 2025-01 18:42 | San Francisco, CA | 2024 Jaquar I-PACE | ADS | Other, see Narrative | No Injuries Reported | 23 | Street | On January [XXX], 2025 at 6:42 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car and a parked, unattended motorcycle on [XXX] near [XXX]. T…On January [XXX], 2025 at 6:42 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car and a parked, unattended motorcycle on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] when the rear driver side wheel separated from the Waymo AV. The wheel rolled a short distance and then made contact with a passenger car and a motorcycle that were both parked at the curb on the south side of [XXX]. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage from the wheel separation. The passenger car and the motorcycle sustained damage from contact with the separated wheel. 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-9807 v2 | ADS | Waymo LLC | 2025-01 14:48 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | Passenger Car | Minor | 0 | Street | This is an update to report [XXX], originally submitted on February [XXX], 2025. The original report indicated there were no reported injuries. Waymo has since received notice of a minor injury to the passenger in the Wa…This is an update to report [XXX], originally submitted on February [XXX], 2025. The original report indicated there were no reported injuries. Waymo has since received notice of a minor injury to the passenger in the Waymo AV. The narrative below remains unchanged. On January [XXX], 2025 at 2:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV') operating in San Francisco, California was in a collision involving a passenger car on [XXX]. The Waymo AV was traveling southbound on [XXX] and was slowing for a queue of traffic. A passenger car traveling southbound on [XXX] 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 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-9808 | ADS | Waymo LLC | 2025-01 15:22 | San Francisco, CA | 2024 Jaguar I-PACE | ADS | Other, see Narrative | No Injuries Reported | 9 | Intersection | On January 31, 2025 at 3:22 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California made contact with the pavement at the elevated entrance on [XXX] and [XXX]. The Waymo AV was traveling no…On January 31, 2025 at 3:22 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California made contact with the pavement at the elevated entrance on [XXX] and [XXX]. The Waymo AV was traveling northwest bound on [XXX] and turning left onto [XXX] for a passenger drop off. The crosswalk that crosses [XXX] on the southwest side of [XXX] is raised to sidewalk level, and as the Waymo AV turned onto [XXX] the Waymo AV's undercarriage made contact with the raised crosswalk pavement. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Waymo became aware that the Waymo AV sustained damage resulting in a tow at 4:32 PM PT on January [XXX], 2025. 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.