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
80 reports, showing 1 to 80.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-16548 | ADS | Waymo LLC | 2026-09 23:09 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Motorcycle | Property Damage. No Injured Reported | 56 | Highway / Freeway | On September [XXX], 2026 at 11:09 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a motorcycle on Interstate [XXX] near exit [XXX]. The Waymo AV was traveling nort…On September [XXX], 2026 at 11:09 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a motorcycle on Interstate [XXX] near exit [XXX]. The Waymo AV was traveling northbound in the leftmost lane on Interstate [XXX] when a motorcycle traveling northbound, partially in the adjacent second lane from the left and partially in the leftmost lane, approached the AV from behind. As the motorcycle proceeded forward, it passed the Waymo AV to the right, and the left side of the motorcycle made contact with the right 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. 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. | |
| 13781-16674 | ADS | Tesla, Inc. | 2026-08 22:46 | Tampa, FL | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 4 | Parking Lot | Summary: The ADS was stopped at the exit of a parking lot with the right turn signal activated. The ADS proceeded with its right turn to follow the navigation route and at approximately 4MPH made contact with a low-hangi…Summary: The ADS was stopped at the exit of a parking lot with the right turn signal activated. The ADS proceeded with its right turn to follow the navigation route and at approximately 4MPH made contact with a low-hanging metal chain with an octagonal sign hanging from the chain that was blocking the exit. The ADS had no passengers present in the vehicle. | |
| 30270-16276 | ADS | Waymo LLC | 2026-08 14:54 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | First Responder Vehicle | Property Damage. No Injured Reported | 0 | Street | On August [XXX], 2026 at 2:54 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling westbound o…On August [XXX], 2026 at 2:54 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling westbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions, when it maneuvered to the right and slowed to a stop in-lane to yield to a fire truck traveling eastbound [XXX]. While the Waymo AV was stopped, the fire truck proceeded forward and attempted to pass the Waymo AV to the left, and the rear left side of the fire truck made contact with the rear left 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 became aware of the tow on August 17, 2026 after an additional review of available information. 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-16461 | ADS | Waymo LLC | 2026-08 13:53 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 8 | Parking Lot | On August [XXX], 2026 at 1:53 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving raised pavement at the entrance of a parking lot on Northwest [XXX] near Northwest [XX…On August [XXX], 2026 at 1:53 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving raised pavement at the entrance of a parking lot on Northwest [XXX] near Northwest [XXX]. The Waymo AV was traveling northbound on Northwest [XXX] when it initiated a left turn into a parking lot on the left side of the roadway. As the Waymo AV was completing the left turn into the entrance of the parking lot, the undercarriage of the Waymo AV made contact with raised pavement at the entrance. 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-16490 | ADS | Waymo LLC | 2026-08 20:19 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 4 | Street | On August [XXX], 2026 at 8:19 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on Northwest [XXX] near Northwest [XXX]. The Waymo AV was stopped fac…On August [XXX], 2026 at 8:19 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on Northwest [XXX] near Northwest [XXX]. The Waymo AV was stopped facing west in the rightmost lane on Northwest [XXX] in a queue of traffic for a red light at the intersection with Northwest [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV began to proceed forward, and a passenger car traveling westbound in the same lane maneuvered to the left as it approached the Waymo AV from behind, and the front right side 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-15830 | ADS | Waymo LLC | 2026-07 20:56 | Miami Beach, FL | 2024 JAGUAR I-PACE | Verified Engaged | Non-Motorist: Cyclist | Serious W/ Hospitalization | 0 | Street | On July [XXX], 2026 at 8:56 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami Beach, Florida was in a collision involving a bicycle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] at a…On July [XXX], 2026 at 8:56 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami Beach, Florida was in a collision involving a bicycle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] at a low rate of speed, yielding to a pedestrian walking southbound along the east curb in the parking lane. A passenger car, initially stopped facing southeast in the parking lane along the west curb of [XXX], proceeded to enter the roadway in their lane of travel, and the Waymo AV slowed to a stop. The passenger car then initiated a U-turn, and the front left side of the passenger car made contact with a cyclist traveling southbound in the left lane on [XXX]. The cyclist and bicycle fell to the ground and the bicycle was propelled forward towards the Waymo AV, making 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. No damages were reported. The cyclist was transported from the scene to a hospital for medical treatment with serious injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-15934 | ADS | Waymo LLC | 2026-07 16:23 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Engaged | Pole / Tree | No Injured Reported | 4 | Parking Lot | On July [XXX], 2026 at 4:23 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pole in a parking lot at [XXX]. The Waymo AV was traveling northbound in a parking l…On July [XXX], 2026 at 4:23 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pole in a parking lot at [XXX]. The Waymo AV was traveling northbound in a parking lot at [XXX] and approaching a parking area. The Waymo AV initiated a left turn with its left turn signal activated, and the front right side of the Waymo AV made contact with a pole. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damages. Waymo determined that this collision met the criteria for 5-day reporting on July 22th, 2026 after an additional review of available information. 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-15987 | ADS | Waymo LLC | 2026-07 07:42 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | On July [XXX], 2026 at 7:42 AM EDT a Waymo Autonomous Vehicle (âWaymo AVâ) operating in Miami, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was parked facing east at the sou…On July [XXX], 2026 at 7:42 AM EDT a Waymo Autonomous Vehicle (âWaymo AVâ) operating in Miami, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was parked facing east at the south curb on [XXX]. While the Waymo AV was parked, a heavy truck traveling westbound on [XXX] approached the Waymo AV from the front and began to pass the Waymo AV to the left. As the heavy truck was passing the Waymo AV, the heavy truck maneuvered to the left towards the south curb, and the left side of the heavy truck made contact with the rear left side of the parked 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. | |
| 30610-16265 | ADS | Zoox, Inc. | 2026-07 15:26 | Miami, FL | 2019 TOYOTA Highlander | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 0 | Intersection | A Zoox vehicle (Vehicle 1) operating in autonomous mode was stopped in the right lane for a red traffic signal on westbound [XXX] in Miami. As it advanced slightly preparing to turn right onto [XXX] and slowed to a gradu…A Zoox vehicle (Vehicle 1) operating in autonomous mode was stopped in the right lane for a red traffic signal on westbound [XXX] in Miami. As it advanced slightly preparing to turn right onto [XXX] and slowed to a gradual stop to yield to cross traffic, it was rear ended by a pickup truck (Vehicle 2) traveling directly behind. The Zoox vehicle operator disengaged from autonomy after the collision. The Zoox vehicle sustained moderate damage to its rear end. No injuries were reported, and police were notified. The Zoox vehicle's camera footage showed that the driver of Vehicle 2 was not looking ahead before or at the time of the collision. | |
| 30610-16275 | ADS | Zoox, Inc. | 2026-07 9:30 | Miami, FL | 2024 ZOOX Zoox | Verified Engaged | Animal | Property Damage. No Injured Reported | 10 | Street | An unoccupied Zoox autonomous vehicle was traveling east on [XXX] in Miami, when an unleashed dog on the right sidewalk ran into the vehicle's path, resulting in contact with the Zoox vehicle. The Zoox vehicle executed a…An unoccupied Zoox autonomous vehicle was traveling east on [XXX] in Miami, when an unleashed dog on the right sidewalk ran into the vehicle's path, resulting in contact with the Zoox vehicle. The Zoox vehicle executed a hard braking maneuver, coming to a near stop, then slowly resumed motion with the right rear wheel apparently making contact with the dog. The Zoox vehicle did not sustain any damage. The dog owner contacted Zoox support to report contact and stated the dog was injured. Zoox has notified the police of the incident. | |
| 30270-15358 | ADS | Waymo LLC | 2026-06 13:29 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 11 | Street | On June [XXX], 2026 at 1:29 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling westbound in the designa…On June [XXX], 2026 at 1:29 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling westbound in the designated left turn lane on [XXX] with its left turn signal activated in preparation for a left turn at the green light at the intersection with [XXX]. As the Waymo AV completed the left turn and continued traveling northbound in the leftmost lane on [XXX], a pickup truck traveling northbound on [XXX] in the second from the left lane, adjacent and to the right of the Waymo AV, maneuvered left entering the Waymo AV's lane of travel, and the front left side of the pickup truck made contact with the right 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-15468 | ADS | Waymo LLC | 2026-06 14:54 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Engaged | Van | Unknown | 2 | Street | On June [XXX], 2026 at 2:54 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] and approachi…On June [XXX], 2026 at 2:54 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] and approaching a curve in the road to the left, when a van traveling westbound on [XXX] along the curve in the road crossed the double yellow and entered the Waymo AV's lane of travel. The Waymo AV braked, maneuvered to the right and slowed to a stop as the van continued forward, and the left side of the van made contact with the front left 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. The driver of the van was transported to the hospital by ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-15494 | ADS | Waymo LLC | 2026-06 22:05 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Intersection | On June [XXX], 2026 at 10:05 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the designat…On June [XXX], 2026 at 10:05 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the designated left turn lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car traveling southbound at a high rate of speed on [XXX], partially in the second from the right lane and partially in the designated left turn lane, crossed into northbound [XXX] and initiated a left turn onto eastbound [XXX]. As the passenger car was exiting the intersection and turning onto eastbound [XXX], the front of the passenger car made contact with the front of the stationary Waymo AV. The passenger car momentarily reversed then proceeded forward, and the front of the passenger car made subsequent 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. 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-15631 | ADS | Waymo LLC | 2026-06 17:23 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Unknown | On June [XXX], 2026 at 5:23 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car in a hotel loading zone at [XXX]. The Waymo AV was parked facing west in…On June [XXX], 2026 at 5:23 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car in a hotel loading zone at [XXX]. The Waymo AV was parked facing west in a hotel loading zone at [XXX] with its hazard lights activated for a passenger drop off. While the Waymo AV was parked, a Waymo AV passenger opened the rear left door and exited the Waymo AV. At the same time, a passenger car traveling westbound through the hotel loading zone proceeded to pass the Waymo AV to the left, and the front right side of the passenger car made contact with the open rear left door of the parked 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-15640 | ADS | Waymo LLC | 2026-06 06:58 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 9 | Parking Lot | On June [XXX], 2026 at 6:58 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving the pavement at the entrance to a parking lot at [XXX]. The Waymo AV was traveling north…On June [XXX], 2026 at 6:58 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving the pavement at the entrance to a parking lot at [XXX]. The Waymo AV was traveling northbound on [XXX] when it initiated a left turn into a parking lot at [XXX]. As the Waymo AV was completing the left turn into the entrance of the parking lot, the undercarriage of the Waymo AV made contact with the pavement. 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-15653 | ADS | Waymo LLC | 2026-06 17:59 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Parking Lot | On June [XXX], 2026 at 5:59 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV at the entrance to a parking lot at [XXX]. The Waymo AV was stopped facing north…On June [XXX], 2026 at 5:59 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV at the entrance to a parking lot at [XXX]. The Waymo AV was stopped facing north at the entrance to a parking lot at [XXX] behind an SUV stopped at the parking gate ahead. While the Waymo AV was stopped, the SUV reversed, and the rear of the SUV 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. 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-15662 | ADS | Waymo LLC | 2026-06 22:31 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On June [XXX], 2026 at 10:31 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in North Miami, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the se…On June [XXX], 2026 at 10:31 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in North Miami, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the second from right lane on [XXX] for a red light at the intersection with [XXX]. A passenger car traveling westbound on [XXX] in the second from right lane 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 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. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-14978 | ADS | Waymo LLC | 2026-05 14:20 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 38 | Street | On May [XXX], 2026 at 2:20 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the left lane on [X…On May [XXX], 2026 at 2:20 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the left lane on [XXX] when an SUV facing west, and stopped at the stop sign at the intersection of [XXX] and [XXX], initiated a left turn onto southbound [XXX]. The Waymo AV began to slow and maneuver to the right as the SUV continued turning left and entered the Waymo AV's lane of travel, and the front right side of the SUV made contact with the front left 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-15260 | ADS | Waymo LLC | 2026-05 23:14 | Miami Beach, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On May [XXX], 2026 at 11:14 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami Beach, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked facing west near the …On May [XXX], 2026 at 11:14 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami Beach, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked facing west near the north curb, partially in-lane, on [XXX] with its hazard lights activated, with a queue of traffic passing the Waymo AV to the left. While the Waymo AV was parked, a passenger car traveling northbound in the left lane, a straight-only lane, on [XXX] proceeded to turn left onto [XXX] and approached the Waymo AV from behind. The passenger car then maneuvered to the left and proceeded to pass the Waymo AV to the left, and the front right side of the passenger car made contact with the rear left side of the parked 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. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-15263 | ADS | Waymo LLC | 2026-05 15:18 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | On May [XXX], 2026 at 3:18 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on eastbound [XXX] near [XXX]. The Waymo AV was traveling eastbound in the second …On May [XXX], 2026 at 3:18 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on eastbound [XXX] near [XXX]. The Waymo AV was traveling eastbound in the second from the right lane on [XXX] when it slowed to a stop in-lane to yield to an animal crossing [XXX] from the right side of the road. As the Waymo AV came to a stop, an SUV traveling eastbound in the leftmost lane on [XXX] and changing lanes to the adjacent second from the right lane, approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. 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-15292 | ADS | Waymo LLC | 2026-05 16:26 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Van | Property Damage. No Injured Reported | 1 | Street | On May [XXX], 2026 at 4:26 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when it began …On May [XXX], 2026 at 4:26 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when it began to slow for a stop sign located at the intersection with [XXX]. While the Waymo AV was slowing, a van parked within a parking stall along the west curb of [XXX], to the left of the Waymo AV, reversed out of the parking stall and maneuvered to the right, and the rear right side of the van 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 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. | |
| 30610-15480 | ADS | Zoox, Inc. | 2026-05 13:38 | Miami, FL | 2019 TOYOTA Highlander | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 1 | Street | A Zoox vehicle operating in autonomous mode was gradually slowing for oncoming traffic while preparing to turn left onto westbound [XXX] from [XXX] in Miami, when a pickup truck (Vehicle 2) rear-ended it while executing …A Zoox vehicle operating in autonomous mode was gradually slowing for oncoming traffic while preparing to turn left onto westbound [XXX] from [XXX] in Miami, when a pickup truck (Vehicle 2) rear-ended it while executing a right turn from [XXX] onto [XXX]. The Zoox vehicle sustained moderate damage, and no injuries were reported. Law enforcement was notified but did not arrive at the scene. | |
| 30270-14584 | ADS | Waymo LLC | 2026-04 02:26 | Miami, FL | 2021 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 6 | Intersection | On April [XXX], 2026 at 2:26 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south in the second from the …On April [XXX], 2026 at 2:26 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south in the second from the left lane in autonomous mode for a red light at the intersection with [XXX]. After the light turned green, the Waymo AV proceeded forward, and an SUV traveling westbound in the right lane on [XXX] began to enter the intersection at [XXX] against a red light without stopping. The test driver of the Waymo AV then transitioned to manual mode and began to brake as the SUV proceeded forward, and the front of the Waymo AV made contact with the right side of the SUV. 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. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-14617 | ADS | Waymo LLC | 2026-04 23:01 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 11:01 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in t…On April [XXX], 2026 at 11:01 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in the rightmost designated right turn lane on [XXX] when it slowed to a stop for a queue of traffic stopped for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car traveling northeastbound in the rightmost designated right turn lane on [XXX] 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-14717 | ADS | Waymo LLC | 2026-04 22:28 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 10:28 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southbound in the sec…On April [XXX], 2026 at 10:28 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southbound in the second from the right lane on [XXX] when it slowed to a stop to yield to a queue of traffic. While the Waymo AV was stopped, a pickup traveling southbound in the second from the right lane on [XXX], and partially in the adjacent right lane, approached the Waymo AV from behind, and the front left side of the pickup truck made contact with the rear right side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-14827 | ADS | Waymo LLC | 2026-04 12:54 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 12:54 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling westbound in the rightm…On April [XXX], 2026 at 12:54 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling westbound in the rightmost lane on [XXX] when it activated its left turn signal in preparation for a lane change to the second from the rightmost lane and then slowed to a stop for a queue of traffic ahead. The Waymo AV then initiated the lane change to the left but slowed to a stop, partially in the rightmost lane and partially in the adjacent left lane, to yield to the queue of traffic ahead. At the same time, a heavy truck was stopped in the second to the rightmost lane, also yielding to the queue of traffic ahead. As the queue of traffic ahead began to proceed, the Waymo began to proceed in its lane change and the heavy truck began to proceed forward. The Waymo AV again came to a stop, and the front right side of the heavy truck made contact with the left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-14833 | ADS | Waymo LLC | 2026-04 00:18 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 12:18 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked in-lane facing south on …On April [XXX], 2026 at 12:18 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked in-lane facing south on [XXX]. While the Waymo AV was parked, a passenger car traveling southbound on [XXX] approached the Waymo AV from behind, and the front right side of the passenger car made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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. | |
| 35021-16401 v2 | ADS | MOIA America LLC | 2026-04 12:42 | Orlando, FL | 2023 Volkswagen ID.Buzz | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 10 | Parking Lot | Other than a correction to the model year field, the content of this report remains unchanged from the initial report submitted on August [XXX], 2026 [Report ID 35021-16401-1]. On April [XXX], 2026, in Orlando, Florida…Other than a correction to the model year field, the content of this report remains unchanged from the initial report submitted on August [XXX], 2026 [Report ID 35021-16401-1]. On April [XXX], 2026, in Orlando, Florida, a MOIA America autonomous test vehicle ("MOIA AV") made contact with a curb while completing a left turn. The MOIA AV was operating on a curved section of roadway within the Lake Nona medical campus during validation testing of a new map release. While following the curve through the left turn, the rear driver-side wheel made contact with the adjacent curb. At the time of contact, the MOIA AV's automated driving system was engaged. The MOIA AV sustained abrasion to the outer rim lip and the spoke faces of the rear driver-side wheel, consistent with curb contact. No other vehicle, pedestrian, cyclist, or other road user was involved. No damage to third-party property was identified and no injuries were reported. MOIA America is reporting this crash under Request No. 2 of Standing General Order 2021-01. MOIA America may supplement or correct this report with additional information as it becomes available. This curb contact event initially was not identified as a property damage crash requiring SGO reporting. However, during a recent internal review of past incidents, this incident was escalated for further analysis of its reportability. On August [XXX], 2026, MOIA America spoke with NHTSA to seek clarification about this incident. NHTSA indicated its opinion that the incident should be reported, so MOIA America is submitting this report in accordance with that guidance. | |
| 30270-14197 | ADS | Waymo LLC | 2026-03 02:32 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | Van | Property Damage. No Injured Reported | 0 | Street | On March [XXX], 2026 at 2:32 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was stopped facing north in the right lane on [X…On March [XXX], 2026 at 2:32 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was stopped facing north in the right lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a van traveling northbound on [XXX], partially in the left lane and partially in the Waymo AV's lane of travel, began to maneuver to the left lane as it approached the Waymo AV from behind and and the front right side of the van made contact with the left side of the stationary Waymo AV. At the time of 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. 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-14335 | ADS | Waymo LLC | 2026-03 06:28 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 3 | Street | On March [XXX], 2026 at 6:28 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it slowe…On March [XXX], 2026 at 6:28 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it slowed to a stop in-lane to yield to an SUV stopped facing east in-lane. While the SUV was stopped, the Waymo AV proceeded slowly forward and began to pass the SUV to the right. While the Waymo AV was passing the SUV, a passenger in the SUV opened the rear right door of the SUV, and the rear right door of the SUV made contact with the left 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-14441 | ADS | Waymo LLC | 2026-03 21:53 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 9 | Street | On March [XXX], 2026 at 9:53 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a tree branch on [XXX] near [XXX]. The Waymo AV was traveling southwestbound in the r…On March [XXX], 2026 at 9:53 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a tree branch on [XXX] near [XXX]. The Waymo AV was traveling southwestbound in the right lane on [XXX] when a tree branch broke off from a tree situated directly above the roadway, and fell into the Waymo AV's lane of travel. The Waymo AV braked as it approached the tree branch, and the front right side of the Waymo AV made contact with the fallen tree branch. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Three of the four passengers were not belted at the time of the collision. 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. | |
| 30610-14554 | ADS | Zoox, Inc. | 2026-03 11:24 | Miami, FL | 2019 TOYOTA Highlander | Verified Engaged | Heavy Truck | Unknown | 17 | Street | A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching…A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching Zoox vehicle. The door struck the Zoox vehicle's right-side A-pillar, windshield, and sensor assembly. After the impact, the trailer's door rebounded and struck the operator behind it. The Zoox vehicle operator then disengaged from autonomous mode. The police and emergency personnel arrived at the scene. The operator was transported by an ambulance from the scene. | |
| 35021-16400 | ADS | MOIA America LLC | 2026-03 11:55 | Orlando, FL | 2023 Volkswagen ID.Buzz | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 9 | Parking Lot | On March [XXX], 2026, in Orlando, Florida, a MOIA America autonomous test vehicle ("MOIA AV") made contact with a curb while completing a left turn. The MOIA AV was operating on a curved section of roadway within the [XX…On March [XXX], 2026, in Orlando, Florida, a MOIA America autonomous test vehicle ("MOIA AV") made contact with a curb while completing a left turn. The MOIA AV was operating on a curved section of roadway within the [XXX] medical campus during validation testing of a new map release. While following the curve through the left turn, the rear driver-side wheel made contact with the adjacent curb. At the time of contact, the MOIA AV's automated driving system was engaged. The MOIA AV sustained abrasion along the rim lip of the rear driver-side wheel. No other vehicle, pedestrian, cyclist, or other road user was involved. No damage to third-party property was identified and no injuries were reported. MOIA America is reporting this crash under Request No. 2 of Standing General Order 2021-01. MOIA America may supplement or correct this report with additional information as it becomes available. This curb contact event initially was not identified as a property damage crash requiring SGO reporting. However, during a recent internal review of past incidents, this incident was escalated for further analysis of its reportability. On August 25, 2026, MOIA America spoke with NHTSA to seek clarification about this incident. NHTSA indicated its opinion that the incident should be reported, so MOIA America is submitting this report in accordance with that guidance. | |
| 30270-13976 | ADS | Waymo LLC | 2026-02 07:40 | Orlando, FL | 2021 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Intersection | On February [XXX], 2026 at 7:40 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound in the des…On February [XXX], 2026 at 7:40 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound in the designated right turn lane on [XXX] when it slowed to make a right turn onto northbound [XXX]. As the Waymo AV was proceeding through the right turn, the Waymo AV slowed to a stop in response to a school bus that was stopped facing south in the second from the left lane on southbound [XXX]. While the Waymo AV was stopped, a passenger car traveling westbound on [XXX] and turning right onto northbound [XXX] approached the Waymo AV from behind, and the front right side 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-14201 | ADS | Waymo LLC | 2026-02 13:48 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On February [XXX], 2026 at 1:48 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing west on [XXX…On February [XXX], 2026 at 1:48 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing west on [XXX] in the third from the right lane in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car traveling westbound on [XXX] in the third from the right lane 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 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. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-13812 | ADS | Waymo LLC | 2026-01 14:50 | Orlando, FL | 2021 JAGUAR I-PACE | Verified Not Engaged | Pickup Truck | Property Damage. No Injured Reported | 1 | Street | On January [XXX], 2026 at 2:50 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing north on [XXX],…On January [XXX], 2026 at 2:50 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing north on [XXX], in autonomous mode in the fourth from the right lane in a queue of traffic for a red light at the intersection with [XXX]. The test driver of the Waymo AV transitioned the Waymo AV to manual mode, and the Waymo AV began to roll backwards. The rear of the Waymo AV then made contact with the front of a pickup truck stopped directly behind 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 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-13471 | ADS | Waymo LLC | 2025-12 04:13 | Miami, FL | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 56 | Highway / Freeway | On December [XXX], 2025 at 4:13 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] near Exit [XXX]. The Waymo AV was traveling westbound on [XXX] in th…On December [XXX], 2025 at 4:13 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving an SUV on [XXX] near Exit [XXX]. The Waymo AV was traveling westbound on [XXX] in the rightmost lane. An SUV was traveling westbound on [XXX] in the second to right lane, to the left of and behind the Waymo AV. While the Waymo AV continued to proceed straight, the SUV approached the Waymo AV on the left side and changed lanes into the Waymo AV's lane of travel. 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 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-13508 | ADS | Waymo LLC | 2025-12 02:08 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Not Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | On December [XXX], 2025 at 2:08 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling northbound in autono…On December [XXX], 2025 at 2:08 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling northbound in autonomous mode on [XXX] in the third from the right lane when it came to a stop behind a heavy truck in a queue of traffic at the intersection with [XXX]. The heavy truck began to reverse and the Waymo AV activated its horn. As the heavy truck continued to reverse, the test driver transitioned the Waymo AV to manual mode and the rear of the heavy truck made contact with the front 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 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. | |
| 30490-13120 | ADS | Beep, Inc. | 2025-11 15:49 | Jacksonville, FL | 2024 FORD Transit | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 20 | Street | On November [XXX], 2025, a Beep-operated Ford E-Transit (003Câ) equipped with an automated driving system (ADS) develop by Oxa Autonomy Ltd. was involved in a collision with a third-party vehicle in Jacksonville, FL.…On November [XXX], 2025, a Beep-operated Ford E-Transit (003Câ) equipped with an automated driving system (ADS) develop by Oxa Autonomy Ltd. was involved in a collision with a third-party vehicle in Jacksonville, FL. While navigating eastbound on [XXX], vehicle 003C was struck on the driver-side rear quarter panel by a 2020 Toyota Prius performing an illegal U-turn from the opposing lane. No passengers were on board at the time of the incident. There were no injuries reported at the scene, and both vehicles were driven away from the site of the collision. Given construction in this area, vehicle 003C was under manual control while driving along [XXX]. The operator engaged the automated driving system as they exited the construction area, approximately one second prior to the collision. Vehicle data and dashcam video indicate the operator attempted to intervene but was unable to avoid contact by the other vehicle. The [XXX] responded to the scene. The driver of the other vehicle was cited for making an improper turn, and the responding officer noted that vehicle 003C was not at fault for the accident. | |
| 30610-13377 | ADS | Zoox, Inc. | 2025-11 13:32 | Miami, FL | 2019 TOYOTA Highlander | Verified Engaged | Motorcycle | Unknown | 1 | Intersection | A Zoox retrofitted test vehicle (Vehicle 1) in autonomous mode was stopped, yielding to cross-traffic, on westbound [XXX] at [XXX] in Miami while waiting for an opportunity to proceed through the intersection and continu…A Zoox retrofitted test vehicle (Vehicle 1) in autonomous mode was stopped, yielding to cross-traffic, on westbound [XXX] at [XXX] in Miami while waiting for an opportunity to proceed through the intersection and continue west on [XXX]. The Zoox vehicle inched forward and then stopped again for cross-traffic. The Zoox vehicle operator then disengaged from autonomous mode and proceeded to begin to cross [XXX]. While crossing, a motorcyclist traveling northbound on [XXX] at a high rate of speed collided with the driver's side front fender and door of the Zoox vehicle. The motorcycle and its operator fell to the ground. After the collision, the Zoox vehicle operator cleared the intersection and pulled over. Both the Zoox vehicle and the motorcycle sustained damage. Police and EMT personnel arrived at the scene, but the motorcycle operator was not transported from the scene. | |
| 30610-11903 | ADS | Zoox, Inc. | 2025-09 14:25 | Miami, FL | 2017 TOYOTA Highlander | Verified Engaged | Non-Motorist: Other | Minor W/O Hospitalization | 0 | Intersection | A Zoox vehicle operating in autonomous mode was traveling in the right lane on southbound [XXX] and preparing to turn right onto [XXX] in Miami when it slowed to a stop in the crosswalk to properly yield to a left-turnin…A Zoox vehicle operating in autonomous mode was traveling in the right lane on southbound [XXX] and preparing to turn right onto [XXX] in Miami when it slowed to a stop in the crosswalk to properly yield to a left-turning vehicle in the oncoming lane. At that time, an e-scooterist westbound on [XXX] entered the crosswalk against the light at [XXX], then swerved and brushed the rear corner of the stopped Zoox vehicle. The e-scooter and the rider remained upright and continued onto the sidewalk along [XXX]. The Zoox vehicle operator then disengaged from autonomous mode and completed the turn shortly after. The Zoox vehicle operator checked on the e-scooterist, who appeared to have stopped to pick up something they dropped. Law enforcement and EMS were called as the e-scooterist reported injury. The EMS personnel provided the e-scooterist with an ice pack and then left the scene. Neither the Zoox vehicle nor the e-scooter sustained any damage. | |
| 30270-11518 | ADS | Waymo LLC | 2025-08 16:41 | Miami, FL | 2024 JAGUAR I-PACE | Verified Not Engaged | Other Fixed Object | Property Damage. No Injured Reported | 9 | Parking Lot | On August [XXX], 2025 at 4:41 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving the exterior wall of a gas station store at [XXX]. The Waymo AV was traveling westbou…On August [XXX], 2025 at 4:41 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving the exterior wall of a gas station store at [XXX]. The Waymo AV was traveling westbound in autonomous mode on [XXX] when the Waymo AV test driver transitioned to manual mode near [XXX]. The test driver continued westbound on [XXX] and made a right turn at the intersection with [XXX] and then a left turn into the [XXX] at [XXX]. The test driver traveled westbound within the gas station and then made a right turn towards a parking stall in front of the gas station store. As the test driver was about to complete the parking maneuver, they accelerated forward towards the exterior wall of the gas station store and the front of the Waymo AV made contact with the cement bumper and pillars in front of the gas station store and the exterior wall of the store. 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, the pillar, and the exterior wall 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. | |
| 30490-11693 | ADS | Beep, Inc. | 2025-08 12:10 | Jacksonville, FL | 2022 FORD Transit | Verified Not Engaged | Pole / Tree | Property Damage. No Injured Reported | 25 | Street | On August [XXX], 2025, a Beep-operated Ford E-Transit (002B) equipped with an automated driving system developed by Oxa Autonomy Ltd. was involved in a collision with a stationary object in Jacksonville, FL. While navig…On August [XXX], 2025, a Beep-operated Ford E-Transit (002B) equipped with an automated driving system developed by Oxa Autonomy Ltd. was involved in a collision with a stationary object in Jacksonville, FL. While navigating westbound on [XXX] along a predefined route, vehicle 002B began to slowly veer towards the right curb. The vehicle eventually climbed the curb with the right front and rear wheels and the passenger-side mirror contacted a stationary light pole. There was one passenger onboard at the time of the incident, an employee of the Jacksonville Transportation Authority. There were no reported injuries, and the vehicle was driven from the scene. Review of the automated driving system logs as well as onboard video footage determined that the operator disengaged the automated driving system 7.5 seconds prior to the vehicle mounting the curb. Further examination of the onboard video footage noted that the operator appeared to be drowsy and inattentive prior to the incident. Beep confirmed that the operators shift was in compliance with anti-fatigue policies for this operation. The operator was referred for a post-accident drug and alcohol testing following the incident and tested negative for any impairment. Following the conclusion of the investigation into this incident, the operator was separated from employment. | |
| 30270-11472 | ADS | Waymo LLC | 2025-07 16:17 | Miami Beach, FL | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Intersection | On July [XXX], 2025 at 4:17 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami Beach, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX]…On July [XXX], 2025 at 4:17 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami Beach, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the right lane and slowed to a stop for a red light at the intersection with [XXX]. A passenger car traveling directly behind the Waymo AV 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, and a test driver was present (in the driver's seating position). 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-11215 | ADS | Waymo LLC | 2025-06 21:22 | Miami, FL | 2024 JAGUAR I-PACE | Verified Not Engaged | Passenger Car | Property Damage. No Injured Reported | 4 | Street | On June [XXX], 2025 at 9:22 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in au…On June [XXX], 2025 at 9:22 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode in the left lane when it approached a passenger car stopped in the left lane with its left turn signal activated at the intersection with [XXX]. The Waymo AV merged into the right lane to pass the passenger car and the test driver disengaged the Waymo AV's ADS as the Waymo AV began to merge back into the left lane. As the test driver attempted to merge in front of the passenger car, the passenger car proceeded straight and the passenger side of the passenger car made contact with the front driver 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. 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-11294 | ADS | Beep, Inc. | 2025-06 07:57 | Jacksonville, FL | 2024 FORD Transit | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 20 | Intersection | On June [XXX], 2025, a Beep-operated Ford E-Transit (004D) equipped with an automated driving system developed by Oxa Autonomy Ltd. was involved in a collision with a third-party vehicle in Jacksonville, FL. While navi…On June [XXX], 2025, a Beep-operated Ford E-Transit (004D) equipped with an automated driving system developed by Oxa Autonomy Ltd. was involved in a collision with a third-party vehicle in Jacksonville, FL. While navigating northbound on [XXX], vehicle 004D approached the intersection of [XXX] under automated control. As vehicle 004D proceeded through the intersection, a 2020 Nissan Pathfinder navigating eastbound on [XXX] entered the intersection and struck vehicle 004D on the drivers door. Vehicle 004D had right of way through the intersection with no stop or yield the other vehicle had been stopped at a stop sign prior to the collision. There were no injuries reported at the scene, and both vehicles were driven away from the site of the collision. Prior to the collision, the safety operator in vehicle 004D stated that they noticed the other vehicle entering the intersection, applied the vehicles brakes, and steered away from the path of the other vehicle. Though they were able to bring vehicle 004D to a complete stop, they were unable to completely avoid the collision. Review of dashcam footage and of CCTV footage covering the intersection corroborate this narrative. The safety operator was referred for a post-accident drug and alcohol testing after the incident. They tested negative for any impairment. Analysis of the ADS logs determined that the ADS had detected the potential collision and had planned an emergency braking action. The safety operators intervention revoked control of the vehicle from the ADS preventing any automated braking actions. The [XXX] responded to the accident scene. The driver of the other vehicle was cited for failing to stop at the stop sign, and the JSO CSO noted that vehicle 004D was not at fault for the accident. | |
| 33475-11343 | ADS | Oxbotica | 2025-06 07:58 | Jacksonville, FL | 2024 FORD Transit | Verified Engaged | SUV | Property Damage. No Injured Reported | 11 | Intersection | Please refer to the description provided by Beep in incident report number 30490-11294-1. | |
| 30413-8218 | ADS | May Mobility | 2024-07 13:57 | Miami, FL | 2022 Toyota Sienna | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | May vehicle was parked in autonomous mode at a rider stop when a VRU on a bicycle approached from the north, coming towards the vehicle. Bicycle was on the wrong side of the road and appeared to be weaving. There were no…May vehicle was parked in autonomous mode at a rider stop when a VRU on a bicycle approached from the north, coming towards the vehicle. Bicycle was on the wrong side of the road and appeared to be weaving. There were no other vehicles nearby and the bicycle had significant room to avoid the May vehicle. However, the bicyclist came into contact with the driver side of the May vehicle, resulting in some minor damage to the May vehicle. After contact, the bicyclist appeared uninjured, got up and left the scene on the bicycle. | |
| 30413-8305 | ADS | May Mobility | 2024-07 08:40 | Miami, FL | 2022 Toyota Siennaa | ADS | Van | No Injuries Reported | 0 | Street | May vehicle was waiting at the red light of [XXX] and [XXX]. The May vehicle was stopped and was 2nd behind the stop line. The van behind the May vehicle was also stopped. Van driver removed their foot from the brake ped…May vehicle was waiting at the red light of [XXX] and [XXX]. The May vehicle was stopped and was 2nd behind the stop line. The van behind the May vehicle was also stopped. Van driver removed their foot from the brake pedal, idling into the May vehicle at a low rate of speed. | |
| 30413-8306 | ADS | May Mobility | 2024-07 12:57 | Miami, FL | 2022 Toyota Sienna | ADS | SUV | No Injuries Reported | 15 | Street | The May vehicle is approaching a lane change. It signals the lane change appropriately early and begins to gradually decelerate for the change. The trailing SUV continues to accelerate while the May vehicle is simultaneo…The May vehicle is approaching a lane change. It signals the lane change appropriately early and begins to gradually decelerate for the change. The trailing SUV continues to accelerate while the May vehicle is simultaneously decelerating, and eventually changes lanes directly into the May vehicle. Trailing SUV drives away without slowing meaningfully, disappearing around an upcoming turn. May vehicle deceleration never exceeds -1.3m/s2, so there is no plausible reason a responsible driver would not have had adequate time to adjust their speed or path to avoid a collision. | |
| 30490-8091 | ADS | Beep, Inc. | 2024-06 13:57 | Jacksonville, FL | 2020 Local Motors (LOCM) Olli 2.0 Shuttle | ADS | Van | No Injuries Reported | 0 | Parking Lot | Redacted by NHTSA as confidential business information | |
| 33475-8060 | ADS | Oxbotica | 2024-06 13:51 | Jacksonville, FL | Local Motors Olli 2.0 | ADS | Van | No Injuries Reported | 0 | Parking Lot | Redacted by NHTSA as confidential business information | |
| 30413-7880 | ADS | May Mobility | 2024-05 17:05 | Miami, FL | 2022 Toyota Sienna | ADS | Motorcycle | No Injuries Reported | 0 | Street | While in traffic and stopped at 0mph in autonomy, a motorized scooter riding between the 2 lanes of traffic clipped the May Mobility vehicle's mirror with their own mirror. The scooter proceeded along its way, seemingly …While in traffic and stopped at 0mph in autonomy, a motorized scooter riding between the 2 lanes of traffic clipped the May Mobility vehicle's mirror with their own mirror. The scooter proceeded along its way, seemingly unaware of the mirror clip. | |
| 30413-7704 | ADS | May Mobility | 2024-04 11:35 | Miami, FL | 2022 Toyota Sienna | ADS | Van | No Injuries Reported | 5 | Intersection | The May vehicle was traveling through an intersection with a van in the oncoming left turn lane. As the May vehicle enters the intersection, the van creeps towards its turn. Predicting that the two will get too close, t…The May vehicle was traveling through an intersection with a van in the oncoming left turn lane. As the May vehicle enters the intersection, the van creeps towards its turn. Predicting that the two will get too close, the May vehicle elects to stop hard. As vehicle is coming to a stop in the stop-hard policy, the turning van fails to respond in time and collides with the rear left corner of the vehicle. In the new software, deploying within the next month, agent-proximity has been replaced with agent-clearance. Performing resimulations of the incident with the latest branch verifies that this issue does not persist. | |
| 30490-6590 | ADS | Beep, Inc. | 2023-11 11:02 | Orlando, FL | Navya ARMA Autonom | ADS | Bus | No Injuries Reported | 6 | Intersection | At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting i…At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting in moderate damage to the shuttle and minor damage to the Lynx bus. There were no injuries reported. Local police responded to the scene and conducted a traffic investigation. The Beep shuttle was towed from the scene for transport to the maintenance facility. The LYNX bus did not require towing and drove from the scene. | |
| 30490-6821 | ADS | Beep, Inc. | 2023-11 11:02 | Orlando, FL | 2020 Navya ARMA | ADS | Bus | No Injuries Reported | 6 | Intersection | At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting i…At approximately 11:02 a.m. on Saturday, November [XXX], 2023, at [XXX] near [XXX] in the City of Orlando, a Beep-operated autonomous shuttle (P139) was involved in a collision with a City of Orlando LYNX bus resulting in moderate damage to the shuttle and minor damage to the Lynx bus. There were no injuries reported. Local police responded to the scene and conducted a traffic investigation. The Beep shuttle was towed from the scene for transport to the maintenance facility. The LYNX bus did not require towing and drove from the scene. Monthly update to previously submitted report 30490-6590-1. | |
| 30490-6165 v2 | ADS | Beep, Inc. | 2023-08 12:54 | Orlando, FL | Navya ARMA Autonom DL | ADS | Bus | No Injuries Reported | Street | Redacted by NHTSA as confidential business information | ||
| 30490-6360 | ADS | Beep, Inc. | 2023-08 13:54 | Orlando, FL | Navya Arma Autonom DL | ADS | Bus | No Injuries Reported | 9 | Street | At Approximately 12:39 PM, the Beep Command Center (BCC) informed the LYNX dispatch center that another autonomous shuttle operating on the same route (VIN: VG9A2CB2CJV[XXX]) was being taken out of service due to insuffi…At Approximately 12:39 PM, the Beep Command Center (BCC) informed the LYNX dispatch center that another autonomous shuttle operating on the same route (VIN: VG9A2CB2CJV[XXX]) was being taken out of service due to insufficient battery charge to continue operation. The BCC later informed LYNX dispatch at 12:49PM that the second shuttle operating on route, P131, would also be returning to storage after the operator completed its current loop. At Approximately 12:52 PM, P131 approached the [XXX] stop within the designated Bus Rapid Transit (BRT) operating lane. The shuttle remained stopped for approximately two (2) and a half minutes while three (3) passengers alighted, and two (2) additional passengers boarded the shuttle. During that period, approximately two (2) minutes after stopping to service passengers, a LYNX bus pulled behind P131. Approximately thirty (30) seconds later, the LYNX bus exited the BRT lane and proceeded into the public travel lane alongside the BRT lane. As the LYNX bus entered the public travel lane, the safety driver onboard P131 engaged the autonomous drive system, and the shuttle proceeded in the BRT lane. After both vehicles had begun moving, P131 in the BRT lane and the LYNX bus in the public travel lane, the LYNX bus reentered the BRT lane encroaching on the shuttles path. The bus failed to provide adequate clearance and contacted the left front side of P131. Both vehicles stopped in the BRT lane after the collision. Within five (5) minutes of the collision, all passengers had safely alighted from the shuttle with no reported injuries and left the scene without giving statements. At approximately 2:20PM, the City of Orlando Police Department (OPD) arrived on scene to investigate the incident. Beep and LYNX supervisors were on scene to support the investigation. OPD collected statements from both the Beep safety driver and LYNX bus driver. The LYNX supervisor provided OPD access to the LYNX bus camera footage on scene, at which point the investigating officer made a verbal indication that the LYNX bus driver appeared to be at fault for the collision. Beeps safety driver was subsequently subjected to a standard post-collision drug and alcohol screening. 1.The safety driver did not exhibit complete situational awareness and per their after-incident interview, failed to notice the bus prior to departing the station. Had the attendant continued to look and check behind/alongside P131 prior to departing the station, the collision may have been avoided. 2.The safety driver attempted to stop the shuttle by disengaging the ADS using the HMI rather than using the emergency stop button. Use of the emergency stop would have increased the deceleration rate to 5 m/s2, decreasing the stopping distance of the shuttle. However, it is not clear whether use of the emergency stop would have fully avoided the collision given the point at which the LYNX LYMMO bus entered the BRT lane. 3.Deficiencies in the standard operating procedures (SOP) between LYNX and Beep allowed for a bus to be deployed onto the service at the same time as P131. Beep communicated to LYNX that both shuttles were exiting the service area. However, LYNX did not wait for final confirmation that both vehicles had left the route prior to dispatching the LYMMO bus involved in the incident, nor did LYNX notify Beep that a bus had been dispatched. Additional information available upon request. | |
| 30490-4473 | ADS | Beep, Inc. | 2022-12 17:53 | Port Saint Lucie, FL | 2018 Navya ARMA | Unknown, see Narrative | Passenger Car | No Injuries Reported | 1 | Street | On December [XXX], 2022, a Navya ARMA shuttle operated by Beep (VIN 1N9A1SACXJS[XXX]) was involved in a non-injury collision while operating in manual mode on [XXX] in Port Saint Lucie, FL. While driving along [XXX] und…On December [XXX], 2022, a Navya ARMA shuttle operated by Beep (VIN 1N9A1SACXJS[XXX]) was involved in a non-injury collision while operating in manual mode on [XXX] in Port Saint Lucie, FL. While driving along [XXX] under autonomous control, the shuttle encountered a parked vehicle partially blocking its path, requiring disengagement of the autonomous drive system. The safety driver attempted to manually drive the shuttle around the parked vehicle to reengage the autonomous drive system. While manually steering the shuttle around the parked vehicle blocking its path, the shuttle failed to respond to manual control input and steered to the left, impacting a parked vehicle at a low rate of speed on the opposite side of [XXX]. The six passengers onboard alighted the shuttle, an accident report was filed with the local police, and the shuttle was removed from the scene. Initial reports from the onboard safety driver indicated that while steering around the vehicle blocking the shuttle's path, the shuttle became unresponsive to control input. The safety driver released the operator present button on the vehicle controller, which serves as dead man switch however, the vehicle failed to stop. After the incident, further investigation by Navya confirmed that the root cause of the incident was a failure of the Xbox 360 controller used to manually control the vehicle. Contact with the parked vehicle occurred between the time of failure and the vehicle drive system recognizing that the controller had failed an elapsed time of 4.05 seconds. In response to the incident, Beep suspended operation of all Navya ARMA vehicles pending identification and implementation of appropriate solutions to mitigate the risk of this failure leading to future incidents. Subsequent investigation by Beep and Navya determined that the vehicle control software, NavyaDrive, is limited in its ability to monitor the validity of control signal input received from the Xbox 360 controller. As the safety driver began to manually steer the vehicle, the controller failed, sending constant turning input to the vehicle drive system leading to the collision. Though Navya developed software mitigations due to prior issues encountered with the controller, those mitigations were ineffective with respect to the failure leading to the incident on December [XXX]. Further, due to the short time between the controller failing and the collision (2.34sec), the safety driver was unable to identify the controller failure and trigger the emergency stop before the collision occurred. In response to the incident, Navya is integrating a revised manual control system on the ARMA shuttle platform. The revised manual control system utilizes industrial-grade components for improved electromechanical reliability and allows for active monitoring of the control system health, eliminating the root cause of the failure that led to the incident on December [XXX]. Software upgrades of all Navya ARMA vehicles will further reintroduce automated braking function while the ARMA vehicle is under manual control. Beep is working with Navya to retrofit its fleet of ARMA vehicles with the revised manual control system as well as retrain and recertify its safety driver staff on the updated NavyaDrive software. Discussion of the root cause analysis and solution design for the revised manual control system will be provided to NHTSA as a supplement to this report. | |
| 1422-4087 v2 | ADS | Volvo Car USA, LLC | 2022-10 08:23 | FL | 2022 Polestar Polestar 2 | ADAS | Other Fixed Object | No Injuries Reported | 55 | Highway / Freeway | The initial submission was by email and electronic form to SGO Mailbox on 10/18/2022 at 10:09PM. This is a resubmission of data using the SGO portal with Volvo Cars USA, LLC account on behalf of Polestar Automotive USA.…The initial submission was by email and electronic form to SGO Mailbox on 10/18/2022 at 10:09PM. This is a resubmission of data using the SGO portal with Volvo Cars USA, LLC account on behalf of Polestar Automotive USA. Volvo Cars USA, LLC is submitting this report on behalf of Polestar Automotive USA and Polestar Performance AB. The vehicle was a company vehicle (owned by Polestar Automotive USA) driven by a company employee, with no known modifications to the factory hardware condition or software updates or changes not released to the public. Subject vehicle was traveling around a curve on the freeway interchange at approximately 55mph, recommended speed in that portion of exchange was 50mph. Driver looked down and took attention off the road. The vehicle continued slightly straight, running up and grazing off the concrete barrier, before coming back into the lane. The vehicle's rear suspension, rear and front wheel/tire were damaged. Vehicle was towed from the scene. We have recovered data from the vehicle and are currently reviewing what information was stored for the incident and will update this report. 10 Day update: After review of the EDR data the technical team was able to determine the following: Pilot Assist was disengaged due to the lateral acceleration exceeded the system limit and the available steering torque system input exceeding the limit. The vehicle could not steer enough to follow the lane. Several warnings were issued: visually in the DIM (Drivers Information Module, display), haptically in the steering wheel, before Pilot Assist was disengaged. The driver is always responsible for ensuring that the vehicle is driven in a safe manner. The driver failed to take control of the vehicle when the vehicles Pilot Assist gave the warnings. | |
| 30290-3985 | ADS | Argo AI | 2022-09 10:23 | Miami, FL | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-4026 | ADS | Ford Motor Company | 2022-09 10:23 | Miami, FL | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30290-3797 | ADS | Argo AI | 2022-08 17:55 | Miami Beach, FL | 2020 Ford Escape | ADS | Pickup Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30290-3800 | ADS | Argo AI | 2022-08 12:31 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-3864 | ADS | Ford Motor Company | 2022-08 17:55 | Miami Beach, FL | 2020 Ford Escape | ADS | Pickup Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-3866 | ADS | Ford Motor Company | 2022-08 12:31 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30290-3346 | ADS | Argo AI | 2022-06 14:48 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 502-3413 | ADS | Ford Motor Company | 2022-06 14:48 | Miami, FL | 2020 Ford Escape | ADS | Passenger Car | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 30490-3168 | ADS | Beep, Inc. | 2022-05 12:30 | Dunedin, FL | Navya | ADS | Bus | No Injuries Reported | 7 | Intersection | Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Tel…Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Telemetry/Video: Requested and received Vehicle taken out of service: Yes temporary safety hold Photographs: Yes Substantial damage: No damages to report Vehicle placed on safety hold: Yes vehicle has been inspected and available for service Lead Investigator: Chief Safety Officer The Beep shuttle attendant was traveling Southbound on [XXX] at approx 7-12 mph in ADS and headed towards the intersection of [XXX]. Beep vehicle stopped at red light at intersection. As the Beep vehicle was crossing the intersection in manual and slowing to a stop to return to ADS in a southbound direction, the trailing bus made light contact with its bicycle rack to the Beep shuttle rear end. The trailing vehicle is a bus owned and operated by the Pinellas Suncoast Transit Authority (PSTA). According to video, as reported by the shuttle attendant and the PSTA Road Supervisor, the bus was tailgating. Root Cause: Trailing vehicle following too closely and not observing Navya slowing to a stop. | |
| 30290-2481 v2 | ADS | Argo AI | 2022-03 12:39 | Coral Gables, FL | 2020 Ford Escape | ADS | SUV | Moderate | 0 | Traffic Circle | Redacted by NHTSA as confidential business information | |
| 30290-2696 | ADS | Argo AI | 2022-03 12:50 | Miami, FL | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 502-2479 v2 | ADS | Ford Motor Company | 2022-03 12:39 | Coral Gables, FL | 2020 Ford Escape | ADS | SUV | Moderate | 0 | Traffic Circle | Redacted by NHTSA as confidential business information | |
| 502-2751 | ADS | Ford Motor Company | 2022-03 12:50 | Miami, FL | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30290-2180 v2 | ADS | Argo AI | 2022-01 12:22 | Miami, FL | 2020 Ford Escape | ADS | SUV | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-2178 v2 | ADS | Ford Motor Company | 2022-01 12:22 | Miami, FL | 2020 Ford Escape | ADS | SUV | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30290-1161 v2 | ADS | Argo AI | 2021-09 13:18 | Miami Beach, FL | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 8 | Street | Redacted by NHTSA as confidential business information | |
| 30415-1317 | ADS | NAVYA Inc. | 2021-09 16:43 | Orlando, FL | 2016 NAVYA Arma | ADS | Other, see Narrative | No Injuries Reported | Street | Shuttle P115 (Vin#VG9A2CB2CIV[XXX]) Shuttle was operating autonomously on route when it approached a pallet in the roadway. The shuttle made contact with the pallet prior to the attendant stopping the shuttle.According t…Shuttle P115 (Vin#VG9A2CB2CIV[XXX]) Shuttle was operating autonomously on route when it approached a pallet in the roadway. The shuttle made contact with the pallet prior to the attendant stopping the shuttle.According to Beep, the pallet height was just below that of the bottom most front LiDAR sensor.no severe damage, only light scratches on the underside of the shuttle grill.Beep was not able to provide any additional information, they did not take any photos of the pallet or UI events interface at the time of the incident. | ||
| 502-1163 v3 | ADS | Ford Motor Company | 2021-09 13:18 | Miami Beach, FL | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 8 | Street | Redacted by NHTSA as confidential business information | |
| 30290-1279 | ADS | Argo AI | 2021-08 08:10 | Miami, FL | 2019 Ford Fusion | ADS | SUV | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30290-1072 | ADS | Argo AI | 2021-07 09:50 | Miami, FL | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 2 | Street | Redacted by NHTSA as confidential business information |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.