The MachineRecord
NHTSA Standing General Order 2021-01

The SGO file, in a form you can search

NHTSA publishes the crash reports as three CSV files of 116 columns each, with several versions of the same report mixed in. This is the same data as one table: driverless systems (ADS) and Level 2 driver assistance side by side, 2021 to today including NHTSA's archive, one row per report at its latest version, every row traceable to its NHTSA report number. Free, CC BY 4.0, refreshed from NHTSA on every pipeline run.

Reports
8612
Fatal
87
Of them Level 2
79
Reporting entities
64
Incidents
2019-08 to 2026-09

8612 reports, showing 7001 to 7100.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
13781-5631Level 2Tesla, Inc.2023-05 05:23Richmond, VA2023 Tesla Model XADASVanUnknown26Highway / FreewayRedacted by NHTSA as confidential business information
13781-5632Level 2Tesla, Inc.2023-05 21:33Mars Hill, NC2021 Tesla Model 3ADASOther Fixed ObjectUnknown60Highway / FreewayRedacted by NHTSA as confidential business information
13781-5634Level 2Tesla, Inc.2023-05 10:20Kingsland, GA2019 Tesla Model 3ADASOther Fixed ObjectUnknownHighway / FreewayRedacted by NHTSA as confidential business information
13781-5635Level 2Tesla, Inc.2023-05 06:08Webster, FL2021 Tesla Model 3ADASUnknownUnknown53UnknownRedacted by NHTSA as confidential business information
13781-5636Level 2Tesla, Inc.2023-05 17:20Flamingo, FL2020 Tesla Model SADASSUVUnknown32Highway / FreewayRedacted by NHTSA as confidential business information
13781-5637Level 2Tesla, Inc.2023-05 22:54Michigan City, IN2022 Tesla Model 3ADASSUVUnknown39StreetRedacted by NHTSA as confidential business information
13781-5638Level 2Tesla, Inc.2023-05 13:54Birmingham, AL2021 Tesla Model YADASPickup TruckUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-5641 v2Level 2Tesla, Inc.2023-05Colfax Township, MI2021 Tesla Model YUnknown, see NarrativePole / TreeMinor48Rural RoadRedacted by NHTSA as confidential business information
13781-5644Level 2Tesla, Inc.2023-05 22:41Winter Springs, FL2021 Tesla Model 3ADASPassenger CarUnknown25StreetRedacted by NHTSA as confidential business information
13781-5645Level 2Tesla, Inc.2023-05 20:42Hinkle, KY2021 Tesla Model 3ADASOther Fixed ObjectUnknown37Rural RoadRedacted by NHTSA as confidential business information
13781-5646Level 2Tesla, Inc.2023-05 02:41Simpsonville, SC2023 Tesla Model 3ADASSUVUnknown49IntersectionRedacted by NHTSA as confidential business information
13781-5647Level 2Tesla, Inc.2023-05 01:23Defiance, MO2022 Tesla Model YADASOther, see NarrativeUnknown63Rural RoadRedacted by NHTSA as confidential business information
13781-5655Level 2Tesla, Inc.2023-05 07:50Denver, CO2022 Tesla Model SADASPassenger CarUnknown29StreetRedacted by NHTSA as confidential business information
13781-5657Level 2Tesla, Inc.2023-05 20:18San Rafael, CA2022 Tesla Model 3ADASUnknownUnknownHighway / FreewayRedacted by NHTSA as confidential business information
13781-5658Level 2Tesla, Inc.2023-05 13:11Hialeah, FL2023 Tesla Model YADASSUVUnknown0IntersectionRedacted by NHTSA as confidential business information
13781-5659Level 2Tesla, Inc.2023-05 17:43Houston, TX2022 Tesla Model 3ADASHeavy TruckUnknown13IntersectionRedacted by NHTSA as confidential business information
13781-5660Level 2Tesla, Inc.2023-05 21:50Magnolia, DE2021 Tesla Model 3ADASUnknownUnknown46UnknownRedacted by NHTSA as confidential business information
13781-6172Level 2Tesla, Inc.2023-05Sealy, TX2019 Tesla Model 3ADASUnknownUnknown44Highway / FreewayRedacted by NHTSA as confidential business information
13781-9480 v2Level 2Tesla, Inc.2023-05 19:59San Leandro, CA2021 Tesla Model 3ADASPassenger CarUnknown65Highway / FreewayRedacted by NHTSA as confidential business information
30270-5429 v2ADSWaymo LLC2023-05 10:32San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported4Street
The content of this report is unchanged from the initial report submitted on May 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle (Waymo AV…The content of this report is unchanged from the initial report submitted on May 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the middle lane on westbound [XXX] between [XXX] and [XXX]. A slower traveling van in the left adjacent lane began to initiate a right lane change in front of the Waymo AV, and the Waymo AV test driver transitioned to manual mode and braked. The SUV traveling behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV and SUV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5456 v2ADSWaymo LLC2023-05 15:27San Francisco, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported0Street
Other than a correction to the reported mileage, the content of this report is unchanged from the initial report submitted on May 8, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at …Other than a correction to the reported mileage, the content of this report is unchanged from the initial report submitted on May 8, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 3:27 PM PDT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was traveling westbound in the left lane on [XXX] and had just passed [XXX] when it detected an oncoming pickup truck traveling eastbound in the Waymo AVs lane. The Waymo AV stopped and the pickup truck re-entered the correct lane for eastbound traffic and passed the Waymo AV. The pickup truck was immediately followed by a large group of cyclists traveling eastbound in multiple lanes of the roadway, including the right lanes and on the wrong side of the double-yellow centerline. The Waymo AV remained stopped as the oncoming cyclists rode around both sides of the Waymo AV. One cyclist then made contact with the front of the stationary Waymo AV, and then immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user was involved. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5611ADSWaymo LLC2023-05 17:54Phoenix, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported10Parking Lot
On May [XXX], 2023 at 5:54 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo A…On May [XXX], 2023 at 5:54 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo AVs undercarriage then made contact with a speed bump (the AV did not contact any vehicle or other road user). At the time of the contact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained undercarriage damage. Waymo is reporting this crash under Request No. 1 of the Second Amended 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-5612ADSWaymo LLC2023-05 17:34Phoenix, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported8Parking Lot
On May [XXX], 2023 at 5:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo A…On May [XXX], 2023 at 5:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with an asphalt speed bump in a parking lot at [XXX]. The Waymo AV entered the parking lot and the Waymo AVs undercarriage then made contact with a speed bump (the AV did not contact any vehicle or other road user). At the time of the contact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained undercarriage damage. Waymo is reporting this crash under Request No. 1 of the Second Amended 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-5756ADSWaymo LLC2023-05 13:37Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported32Street
On [XXX], 2023 at 1:37 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] at S [XXX]. While traveling eastbound on [XXX], a passenger vehi…On [XXX], 2023 at 1:37 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger vehicle on [XXX] at S [XXX]. While traveling eastbound on [XXX], a passenger vehicle in the oncoming lane veered out of their lane and into the eastbound lane. The vehicle made contact with the left rear door of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The other party immediately left the scene without exchanging information. 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-5757ADSWaymo LLC2023-05 21:29Mesa, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported63Highway / Freeway
On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Mesa, Arizona was in a collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right lane…On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Mesa, Arizona was in a collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right lane on a three-lane stretch of the [XXX] when a load of hay bales fell off a truck traveling in the center lane ahead of the Waymo AV. The front left fender of the Waymo AV made contact with a hay bale. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers 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-5758ADSWaymo LLC2023-05 20:48San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported6Street
On[XXX], 2023 at 8:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX}. While traveling west on [XXX}, the Waymo AV was…On[XXX], 2023 at 8:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX}. While traveling west on [XXX}, the Waymo AV was executing a pullover maneuver in autonomous mode and made contact with the left rear bumper of a parked vehicle. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5759ADSWaymo LLC2023-05 23:30Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On [XXX], 2023 at 11:30 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light at the intersect…On [XXX], 2023 at 11:30 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped at a red light at the intersection of [XXX] at [XXX]. A passenger vehicle that had been previously stopped behind the Waymo AV proceeded forward, making contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers 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-5760ADSWaymo LLC2023-05 09:42Phoenix, AZ2021 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Street
On [XXX], 2023 at 09:42 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX], just west of [XXX]. The Waymo AV was traveling westbound on [XXX] whe…On [XXX], 2023 at 09:42 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX], just west of [XXX]. The Waymo AV was traveling westbound on [XXX] when it came to a stop, yielding to a U-Haul box truck that was attempting to reverse into a parking lot to the right of the Waymo AV. The truck exited the lot and re-entered the oncoming eastbound lane, making contact with the left front end of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5762ADSWaymo LLC2023-05 10:56San Francisco, CA2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On [XXX] at 10:56 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small …On [XXX] at 10:56 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog, which did not survive. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers 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.
30412-5422 v3ADSCruise LLC2023-05 02:44San Francisco, CA2022 Cruise AVADSOther Fixed ObjectMinor7IntersectionRedacted by NHTSA as confidential business information
30412-5430 v2ADSCruise LLC2023-05 09:32San Francisco, CA2023 Cruise AVADSOther, see NarrativeMinor5IntersectionRedacted by NHTSA as confidential business information
30412-5624ADSCruise LLC2023-05 21:24San Francisco, CA2022 Cruise AVADSPassenger CarMinor15StreetRedacted by NHTSA as confidential business information
30412-5697ADSCruise LLC2023-05 03:34San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported9StreetRedacted by NHTSA as confidential business information
30412-5708ADSCruise LLC2023-05 00:35Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-5709ADSCruise LLC2023-05 00:35Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported8StreetRedacted by NHTSA as confidential business information
30412-5710ADSCruise LLC2023-05 23:12Austin, TX2022 Cruise AVADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-5711ADSCruise LLC2023-05 00:14Austin, TX2023 Cruise AVADSSUVNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30413-5633ADSMay Mobility2023-05 16:40Grand Rapids, MN2021 Toyota SiennaADSNon-Motorist: OtherNo Injuries Reported0Intersection
On Tuesday May [XXX] at 16:40 local time, the May shuttle was driving Northbound from [XXX] to [XXX] in Grand Rapids, MN, in autonomous mode and was followed by 2 people riding on scooters. As the May shuttle made the tu…On Tuesday May [XXX] at 16:40 local time, the May shuttle was driving Northbound from [XXX] to [XXX] in Grand Rapids, MN, in autonomous mode and was followed by 2 people riding on scooters. As the May shuttle made the turn, the VRUs were traveling in the same direction as the May shuttle on opposite sides of the lane. As the May shuttle completed the turn at 10 MPH, the brakes were applied and the vehicle came to a complete stop because one of the riders attempted to cross over in the lane which caused VRU safety buffer to intersect with vehicle path, which led the vehicle to slow to a stop. The scooter rider contacted the rear left rear bumper of the shuttle. Scooters were traveling at an estimated speed of 12 mph and accelerating.
30531-5440 v2ADSTransdev Alternative Services2023-05 10:32San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported4Street
The content of this report is unchanged from the initial report. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [X…The content of this report is unchanged from the initial report. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was fraveling in autonomous mode in the middle lane on westbound [XXX] between [XXX] and [XXX]. A slower traveling van in the left adjacent lane began to initiate a right lane change in front of the Waymo AV, and the Waymo AV test driver transitioned to manual mode and braked. The SUV traveling behind the Waymo AV then made contact with the rear 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 and SUV sustained damage. This is a duplicate of report 30270-5429-1.
30531-5768ADSTransdev Alternative Services2023-05 21:29Mesa, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported63Highway / Freeway
On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was ina. collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right la…On [XXX], 2023 at 9:29 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was ina. collision involving an object on the [XXX], East of [XXX]. The Waymo AV was traveling eastbound in the far right lane on a three-lane stretch of the [XXX] when a load of hay bales fell off a truck traveling in the center lane ahead of the Waymo AV. The front left fender of the Waymo AV made contact with a hay bale. At the time of the impact, the Waymo WV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA Report ID 30270-5757-1.
30531-5769ADSTransdev Alternative Services2023-05 23:30Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On [XXX] at 11:30 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX] Parkway. The Waymo AV was stopped at a red light at the inter…On [XXX] at 11:30 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] at [XXX] Parkway. The Waymo AV was stopped at a red light at the intersection of [XXX] at [XXX] Parkway. A passenger vehicle that had been previously stopped behind the Waymo AV proceeded forward, making contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA Report ID: 30270-5759-1.
30531-5770ADSTransdev Alternative Services2023-05 10:56San Francisco, CA2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On [XXX], 2023 at 10:56 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when …On [XXX], 2023 at 10:56 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog, which did not survive. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA report ID 30270-5762-1.
30610-5714ADSZoox, Inc.2023-05 10:52Paradise, NV2016 Toyota HighlanderADSPassenger CarMinor0Street
A Zoox vehicle in autonomy was stopped in a merge lane, yielding and waiting for cross traffic, when it was rear ended at low speed by a vehicle behind. A Zoox operator reported "slight shoulder pain." Police were not c…A Zoox vehicle in autonomy was stopped in a merge lane, yielding and waiting for cross traffic, when it was rear ended at low speed by a vehicle behind. A Zoox operator reported "slight shoulder pain." Police were not called.
30610-5716ADSZoox, Inc.2023-05 11:40San Francisco, CA2017 Toyota HighlanderADSSUVMinor1Street
A Zoox vehicle in autonomy was coming to a gradual stop for traffic ahead when it was rear ended by vehicle 2 at low speed. There was minor damage to the striking vehicle and police were not called. A Zoox operator repor…A Zoox vehicle in autonomy was coming to a gradual stop for traffic ahead when it was rear ended by vehicle 2 at low speed. There was minor damage to the striking vehicle and police were not called. A Zoox operator reported "sore neck and back".
30792-5565ADSWeRide Corp2023-05 11:41San Francisco, CA2023 Nissan LeafADSNon-Motorist: CyclistNo Injuries Reported0Street
On Monday May [XXX] at 11:41am a Weride autonomous vehicle (Vehicle 1) was in Autonomous Mode stopped at the intersection of [XXX] towards [XXX] appropriately yielding to a illegally U turning skateboard on [XXX] North t…On Monday May [XXX] at 11:41am a Weride autonomous vehicle (Vehicle 1) was in Autonomous Mode stopped at the intersection of [XXX] towards [XXX] appropriately yielding to a illegally U turning skateboard on [XXX] North to South direction in front of the AV (Vehicle 1). While yielding, a bicyclist was coming from behind our AV (Vehicle 1) head was turned left possibly looking for cross traffic. When the cyclist turned his head forward, it was too late to react in time to our stopped vehicle(Vehicle 1) with the given distance and speed they were traveling at in which the cyclist collided with our vehicle (Vehicle 1). Our Weride safety officer immediately disengaged and hand signaled to the bicyclist to pull over to the closest safe place to park as to not obstruct traffic. As our safety officer parked and got out of the car to check on the bicyclist, the bicyclist was already on in motion on his bicycle and "fist bumped" our safety officer while passing by him and leaving the scene without exchanging any information.
540-5425 v3ADSGeneral Motors, LLC2023-05 02:44San Francisco, CA2022 Cruise AVADSOther Fixed ObjectMinor7Intersection
On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Crui…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5422-3)
540-5445 v2ADSGeneral Motors, LLC2023-05 09:32San Francisco, CA2023 Cruise AVADSOther, see NarrativeMinor5Intersection
On May 10, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured th…On May 10, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5430-2)
540-5639ADSGeneral Motors, LLC2023-05 21:24San Drancisco, CA2022 Cruise AVADSPassenger CarMinor15Street
On May 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured …On May 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5624-1)
540-5726ADSGeneral Motors, LLC2023-05 03:34San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported9Street
On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5697-1)
540-5729ADSGeneral Motors, LLC2023-05 00:35Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported0Street
On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5708-1)
540-5730ADSGeneral Motors, LLC2023-05 00:35Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported8Street
On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5709-1)
540-5731ADSGeneral Motors, LLC2023-05 23:12Austin, TX2022 Cruise AVADSPassenger CarNo Injuries Reported0Street
On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5710-1)
540-5735ADSGeneral Motors, LLC2023-05 00:14Austin, TX2023 Cruise AVADSSUVNo Injuries Reported0Street
On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5711-1)
1306-5424 v2Level 2Toyota Motor Engineering & Manufacturing2023-04 18:59White City, OR2021 Toyota Venza HVADASOther Fixed ObjectUnknown63Highway / Freeway
Toyota received an allegation related to this crash on April 11, 2023, and later on April 14, 2023 from the owner and driver of the vehicle through a call to the Toyota Brand Engagement Center. The contact record indicat…Toyota received an allegation related to this crash on April 11, 2023, and later on April 14, 2023 from the owner and driver of the vehicle through a call to the Toyota Brand Engagement Center. The contact record indicates that the owner alleged he was driving on [XXX] when the vehicle, "veered off the road somehow and crashed into a field." The owner's primary allegation was related to the airbags not deploying. He also mentioned being, "uncomfortable with the steering corrections and with lane departure." The owner described his injuries as a concussion and a partially collapsed lung. Additionally, the owner stated that the White City Police Department responded to the incident and created Police Report # SP23096093. On April 28, 2023, Toyota completed a vehicle inspection and field report for the incident. There were no allegations made related to the Dynamic Radar Cruise Control (DRCC) or Lane Trace Assist (LTA). However, on May 2, 2023, after additional analysis of the recorded vehicle data, Toyota determined the case was reportable under the SGO. Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) data from the subject vehicle. VCH provides an approximately 7 second pre-crash recording, and EDR provides an approximately 4.7 second pre-crash data recording. Based on the data obtained, the following information was observed: The driver seat belt status was OFF (unbuckled) during the recording. LTA was engaged during the recording from approximately 4 seconds until approximately 1.6 seconds prior to the crash event. At the time of LTA disengagement, the driver turned the vehicle left at a steering angle increasing from approximately 4.5 degrees to 88.5 degrees. DRCC was engaged during the recording until approximately 0.8 seconds prior to the crash event. No FCW or AEB activation occurred. As a result of the crash incident, the subject vehicle's curtain shield airbags deployed, the front seatbelt pretensioners deployed and were locked in the retracted position, and it was towed from the crash scene. The front driver and passenger airbags did not deploy. This report is a 10-Day update. The original Report ID is 1306-5424-1.
13781-11303Level 2Tesla, Inc.2023-04 22:40Anaheim, CA2015 TESLA Model SVerified EngagedUnknownUnknown28UnknownRedacted by NHTSA as confidential business information
13781-5177 v2Level 2Tesla, Inc.2023-04 16:02Darlington, SC2023 Tesla Model 3ADASSUVUnknown56IntersectionRedacted by NHTSA as confidential business information
13781-5194 v2Level 2Tesla, Inc.2023-04 19:31Centerville, UT2021 Tesla Model YADASPassenger CarUnknown77Highway / FreewayRedacted by NHTSA as confidential business information
13781-5195 v2Level 2Tesla, Inc.2023-04 22:28Bonita Springs, FL2022 Tesla Model YADASHeavy TruckUnknown81Highway / FreewayRedacted by NHTSA as confidential business information
13781-5199 v2Level 2Tesla, Inc.2023-04 15:19Seattle, WA2020 Tesla Model 3ADASSUVUnknown41StreetRedacted by NHTSA as confidential business information
13781-5228 v2Level 2Tesla, Inc.2023-04 01:21Los Angeles, CA2023 Tesla Model YADASOther Fixed ObjectUnknown53Highway / FreewayRedacted by NHTSA as confidential business information
13781-5244 v2Level 2Tesla, Inc.2023-04 06:46Lutz, FL2022 Tesla Model YADASOther, see NarrativeUnknown40IntersectionRedacted by NHTSA as confidential business information
13781-5245 v2Level 2Tesla, Inc.2023-04 17:26Sharpsburg, GA2022 Tesla Model 3ADASUnknownUnknown42IntersectionRedacted by NHTSA as confidential business information
13781-5246 v2Level 2Tesla, Inc.2023-04 17:13Chicago, IL2021 Tesla Model XADASSUVUnknown3Highway / FreewayRedacted by NHTSA as confidential business information
13781-5247 v2Level 2Tesla, Inc.2023-04 10:25Los Angeles, CA2021 Tesla Model YADASOther Fixed ObjectUnknown57Highway / FreewayRedacted by NHTSA as confidential business information
13781-5255 v2Level 2Tesla, Inc.2023-04 20:21City of New York, NY2022 Tesla Model XADASVanUnknown32Highway / FreewayRedacted by NHTSA as confidential business information
13781-5283 v2Level 2Tesla, Inc.2023-04 23:14Geyserville, CA2022 Tesla Model 3ADASSUVUnknown31StreetRedacted by NHTSA as confidential business information
13781-5303 v2Level 2Tesla, Inc.2023-04 20:03North Whitehall Township, PA2021 Tesla Model YADASUnknownUnknown54Highway / FreewayRedacted by NHTSA as confidential business information
13781-5304 v2Level 2Tesla, Inc.2023-04 23:21Marlton, NJ2020 Tesla Model XADASPassenger CarUnknown25IntersectionRedacted by NHTSA as confidential business information
13781-5305 v2Level 2Tesla, Inc.2023-04 00:53Forest Hills, TN2022 Tesla Model YADASOther, see NarrativeUnknown44IntersectionRedacted by NHTSA as confidential business information
13781-5308 v2Level 2Tesla, Inc.2023-04 08:55Henderson, NV2020 Tesla Model YADASOther, see NarrativeUnknown71StreetRedacted by NHTSA as confidential business information
13781-5309 v2Level 2Tesla, Inc.2023-04 15:49Culver City, CA2023 Tesla Model 3ADASVanUnknown54Highway / FreewayRedacted by NHTSA as confidential business information
13781-5349 v2Level 2Tesla, Inc.2023-04 15:45San Carlos, CA2022 Tesla Model YADASUnknownUnknown45Highway / FreewayRedacted by NHTSA as confidential business information
13781-5354 v2Level 2Tesla, Inc.2023-04 13:25Dandridge, TN2020 Tesla Model 3ADASHeavy TruckUnknown63Highway / FreewayRedacted by NHTSA as confidential business information
13781-5355 v2Level 2Tesla, Inc.2023-04 13:58Franklin Township, NJ2021 Tesla Model YADASSUVUnknown20IntersectionRedacted by NHTSA as confidential business information
13781-5364 v2Level 2Tesla, Inc.2023-04 20:43Dallas, TX2022 Tesla Model YADASUnknownUnknown67Highway / FreewayRedacted by NHTSA as confidential business information
13781-5365 v2Level 2Tesla, Inc.2023-04 03:53Nashville-Davidson, TN2018 Tesla Model 3ADASUnknownUnknown79UnknownRedacted by NHTSA as confidential business information
13781-5366 v2Level 2Tesla, Inc.2023-04 20:51Malibu, CA2021 Tesla Model 3ADASOther Fixed ObjectUnknown24Rural RoadRedacted by NHTSA as confidential business information
13781-5367 v2Level 2Tesla, Inc.2023-04 12:41Wilmington, DE2020 Tesla Model 3ADASSUVUnknown45Highway / FreewayRedacted by NHTSA as confidential business information
13781-5368 v2Level 2Tesla, Inc.2023-04 04:23Greenwich, CT2021 Tesla Model YADASOther, see NarrativeUnknown51Highway / FreewayRedacted by NHTSA as confidential business information
13781-5369 v2Level 2Tesla, Inc.2023-04 01:11Claremont, CA2023 Tesla Model 3ADASPassenger CarUnknown31StreetRedacted by NHTSA as confidential business information
13781-5370 v2Level 2Tesla, Inc.2023-04 14:57Pasadena, CA2021 Tesla Model YADASVanUnknown56IntersectionRedacted by NHTSA as confidential business information
13781-5371 v2Level 2Tesla, Inc.2023-04 09:25Jurupa Valley, CA2023 Tesla Model YADASPassenger CarUnknown54Highway / FreewayRedacted by NHTSA as confidential business information
13781-5372 v2Level 2Tesla, Inc.2023-04 22:12Fallbrook, CA2022 Tesla Model 3ADASPickup TruckFatality48Highway / FreewayRedacted by NHTSA as confidential business information
13781-5391 v2Level 2Tesla, Inc.2023-04 01:06Aurora, IL2017 Tesla Model XADASUnknownUnknown42StreetRedacted by NHTSA as confidential business information
13781-5392 v2Level 2Tesla, Inc.2023-04 00:17Phoenix, AZ2022 Tesla Model YADASPickup TruckUnknown0IntersectionRedacted by NHTSA as confidential business information
13781-5393 v2Level 2Tesla, Inc.2023-04 18:59Cathedral City, CA2020 Tesla Model 3ADASPassenger CarUnknown39IntersectionRedacted by NHTSA as confidential business information
13781-5394 v2Level 2Tesla, Inc.2023-04 20:15Watervliet, NY2021 Tesla Model 3ADASPassenger CarUnknown19Highway / FreewayRedacted by NHTSA as confidential business information
13781-5416 v2Level 2Tesla, Inc.2023-04 05:36Fremont, CA2023 Tesla Model YADASSUVUnknown31Highway / FreewayRedacted by NHTSA as confidential business information
13781-5417 v2Level 2Tesla, Inc.2023-04 14:35Lake Worth, FL2023 Tesla Model 3ADASUnknownUnknown58Highway / FreewayRedacted by NHTSA as confidential business information
13781-5418 v2Level 2Tesla, Inc.2023-04 09:26Vacaville, CA2022 Tesla Model 3ADASPassenger CarUnknown77Highway / FreewayRedacted by NHTSA as confidential business information
13781-5419 v2Level 2Tesla, Inc.2023-04 21:26Irvine, CA2018 Tesla Model XADASSUVUnknown35IntersectionRedacted by NHTSA as confidential business information
13781-5420 v2Level 2Tesla, Inc.2023-04 21:13Stockbridge, GA2019 Tesla Model 3ADASPickup TruckUnknown44IntersectionRedacted by NHTSA as confidential business information
13781-5421 v2Level 2Tesla, Inc.2023-04 07:31San Mateo, CA2023 Tesla Model YADASUnknownUnknown71Highway / FreewayRedacted by NHTSA as confidential business information
13781-5918Level 2Tesla, Inc.2023-04Mountain View, CA2016 Tesla Model SUnknown, see NarrativePickup TruckUnknown20UnknownRedacted by NHTSA as confidential business information
13781-5986 v2Level 2Tesla, Inc.2023-04UNK2021 Tesla Model 3Unknown, see NarrativeNon-Motorist: PedestrianModerateUnknownRedacted by NHTSA as confidential business information
30270-5202 v2ADSWaymo LLC2023-04 10:46San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on April 6, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle (Waym…The content of this report is unchanged from the initial report submitted on April 6, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding south on [XXX] was green for the Waymo AV as it approached the intersection. As the Waymo AV approached, an individual riding a motorized scooter traveling north on [XXX] proceeded to turn left onto westbound [XXX], across the paths of the Waymo AV and other oncoming vehicles. The Waymo AV began to brake, and the Waymo AV test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car traveling directly behind the Waymo AV then made contact with the rear of the Waymo AV. The individual riding the scooter was not contacted by the Waymo AV or any other vehicle. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both the Waymo AV and the passenger car sustained damage, and the individual on the motorized scooter left the scene. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a Vulnerable Road User was involved. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5208 v2ADSWaymo LLC2023-04 10:48San Francisco, CA2021 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Street
The content of this report is unchanged from the initial report submitted on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:48 AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:48 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was proceeding northwest on [XXX] near the intersection with [XXX] when it came to a stop to yield to a heavy truck traveling southeast on [XXX]. As the heavy truck drove past the Waymo AV, the drivers side section of the heavy truck made contact with the rear drivers side sensor of the Waymo AV. The heavy truck then left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5584ADSWaymo LLC2023-04 22:56San Francisco, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Intersection
On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV ca…On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV came to a stop to yield to an oncoming SUV in a narrow passageway. The SUV proceeded around the Waymo AV and made contact with the left rear sensor housing of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The driver of the SUV stopped briefly but left before sharing their information. The Waymo 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-5586ADSWaymo LLC2023-04 17:29Santa Monica, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Intersection
On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in th…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding southwest on [XXX] was red as the Waymo AV approached the intersection and came to a stop. The signal for traffic proceeding southwest on [XXX] then turned green, and traffic in adjacent lanes began moving while the Waymo AV waited for traffic in its lane to begin to move. The SUV that had been stopped directly behind the Waymo AV began moving forward and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo 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-5588ADSWaymo LLC2023-04 15:43Tempe, AZ2017 Chrysler PacificaADSPassenger CarNo Injuries Reported5Intersection
On April [XXX], 2023 at 3:43 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the …On April [XXX], 2023 at 3:43 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. After the Waymo AV entered the right-turn lane, a passenger car began to exit from the shopping center driveway to the right of the Waymo AV. The Waymo AV began to brake as the passenger car began to turn in front of the AV onto [XXX]. The passenger car's front bumper made contact with the front right corner of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV did not sustain damage the passenger car 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.

What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. The themed reading of the driverless narratives is on the reports page.