Reported to NHTSAWashington, DC
Operators running driving automation here have filed 6 crash reports with the federal regulator. 1 of them record an injury that reached hospitalisation or worse.
Reading the numbers
Waymo LLC filed 5 of the 6 reports (83%), Beep, Inc. 1. The most common outcome recorded is "Property Damage. No Injured Reported" (4). 1 report records an injury that reached hospitalisation or worse; those are the ones that enter the register as cases. The other party is most often suv (4).
By outcome
- Property Damage. No Injured Reported4
- Minor W/ Hospitalization1
- Minor W/O Hospitalization1
Crash with
- SUV4
- Other Fixed Object1
- Passenger Car1
30270-15667Waymo LLC2026-07Minor W/ Hospitalizationwith suv
On July [XXX], 2026 at 10:51 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] NW near [XXX] NW.
The Waymo AV was traveling northwestbound in the right lane on [XXX] NW in autonomous mode when it began to slow for a van, ahead in lane, turning right into a shopping center. While the Waymo AV was slowing, the test driver transitioned the Waymo…
On July [XXX], 2026 at 10:51 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] NW near [XXX] NW.
The Waymo AV was traveling northwestbound in the right lane on [XXX] NW in autonomous mode when it began to slow for a van, ahead in lane, turning right into a shopping center. While the Waymo AV was slowing, the test driver transitioned the Waymo AV into manual mode and continued to slow, and an SUV traveling northwestbound on [XXX] NW, partially in the right lane and partially in the left lane, maneuvered to the left as it approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left 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 test driver of the Waymo AV alleged minor injuries.
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-14625Waymo LLC2026-03Minor W/O Hospitalizationwith suv
On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX].
The Waymo AV was traveling southbound in the rightmost lane on [XXX] when it began to slow for an emergency vehicle siren from an ambulance traveling northbound. While the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the…
On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX].
The Waymo AV was traveling southbound in the rightmost lane on [XXX] when it began to slow for an emergency vehicle siren from an ambulance traveling northbound. While the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). 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.
30490-14064Beep, Inc.2026-01Property Damage. No Injured Reportedwith passenger car
On January [XXX], 2026, a Beep-operated Karsan EJEST (BEEP-EJEST-0001) equipped with an automated driving system (ADS) develop by ADASTEC Corporation (ADASTEC) was involved in a collision with a third-party vehicle in Washington, D.C.
While traveling in autonomous mode westbound on [XXX] in the left-hand lane, the vehicle encountered a double-parked vehicle partially intruded into BEEP-EJEST-0001's lane of travel.…
On January [XXX], 2026, a Beep-operated Karsan EJEST (BEEP-EJEST-0001) equipped with an automated driving system (ADS) develop by ADASTEC Corporation (ADASTEC) was involved in a collision with a third-party vehicle in Washington, D.C.
While traveling in autonomous mode westbound on [XXX] in the left-hand lane, the vehicle encountered a double-parked vehicle partially intruded into BEEP-EJEST-0001's lane of travel. BEEP-EJEST-0001 began to slow from its planned speed, and as decelerated, a human-driven Tesla Model Y (VEHICLE2) traveling parallel to BEEP-EJEST-0001 in the right-hand lane attempted to pull behind BEEP-EJEST-0001 to pass the double-parked vehicle in its lane of travel. VEHICLE2 encroached upon BEEP-EJEST-0001's predefined safety area of 5 cm, triggering an automated deceleration by BEEP-EJEST-0001 of approximately –2 m/s^2. VEHICLE2 began to further encroach upon BEEP-EJEST-0001's lane, triggering a higher-rate automated braking response consistent with system design. VEHICLE2 subsequently made contact with the rear of BEEP-EJEST-0001.
Beep confirmed that the operator performed his duties as trained and expected by Beep's established policies and procedures. The vehicle operator was not referred for a post-accident drug and alcohol testing after the incident as the DOT criteria for such testing were not met.
Available data indicated that VEHICLE2 followed BEEP-EJEST-0001 at a distance insufficient to respond to rapid deceleration and initiated a lane transition across a solid lane line immediately prior to contact.
BEEP-EJEST-0001 reacted as expected to the environment it encountered, slowing down to appropriate speeds and operated within its defined ODD at the time of the incident. There were (7) seven passengers on board. No injuries were reported. Both vehicles sustained minor damage, no airbags were deployed, and both vehicles were driven from the scene. No law enforcement attended to the scene.
Following the incident, the vehicle was inspected for damages to the vehicle or sensors. It has been determined that any damage incurred was minor and did not impact the operational integrity of the vehicle.
30270-13379Waymo LLC2025-12Property Damage. No Injured Reportedwith suv
On December [XXX], 2025 at 6:25 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] and [XXX] approaching the [XXX] overpass.
The Waymo AV was traveling southbound on [XXX] and [XXX] in the left lane when it began to slow for traffic ahead. While the Waymo AV was slowing, an SUV that was traveling southbound behind the Waymo AV continued to proceed…
On December [XXX], 2025 at 6:25 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] and [XXX] approaching the [XXX] overpass.
The Waymo AV was traveling southbound on [XXX] and [XXX] in the left lane when it began to slow for traffic ahead. While the Waymo AV was slowing, an SUV that was traveling southbound behind the Waymo AV continued to proceed forward and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). 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-13252Waymo LLC2025-11Property Damage. No Injured Reportedwith other fixed object
On November [XXX], 2025 at 6:55 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving a curb on [XXX] at [XXX].
The Waymo AV was traveling eastbound on [XXX] in autonomous mode when it began to turn right at the intersection with [XXX]. As the Waymo AV proceeded to turn right, it approached the right hand curb. The test driver transitioned the Waymo AV to manual…
On November [XXX], 2025 at 6:55 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving a curb on [XXX] at [XXX].
The Waymo AV was traveling eastbound on [XXX] in autonomous mode when it began to turn right at the intersection with [XXX]. As the Waymo AV proceeded to turn right, it approached the right hand curb. The test driver transitioned the Waymo AV to manual mode and the front right tire of the Waymo AV made contact with the curb. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage.
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-13026Waymo LLC2025-10Property Damage. No Injured Reportedwith suv
On October [XXX], 2025 at 1:28 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] near [XXX].
The Waymo AV was stopped facing south in the left lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV began to proceed forward at a low rate of speed…
On October [XXX], 2025 at 1:28 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] near [XXX].
The Waymo AV was stopped facing south in the left lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV began to proceed forward at a low rate of speed and an SUV that was initially stopped directly behind the Waymo AV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. 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.
A filing records that a crash happened and who was involved. It does not establish fault. Reports are amended as an operator learns more, and the register keeps the latest version. How this is verified.
Weekly digestNew cases, once a week, by email
Every case added to the register in the last seven days, with its sources. Free, no account, and the register is the only sender.