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 6801 to 6900.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
13781-6000Level 2Tesla, Inc.2023-07 20:23Wilmington, NC2022 Tesla Model 3ADASUnknownUnknown77Highway / FreewayRedacted by NHTSA as confidential business information
13781-6001Level 2Tesla, Inc.2023-07UNK2021 Tesla Model 3ADASSUVUnknown20Highway / FreewayRedacted by NHTSA as confidential business information
13781-6014Level 2Tesla, Inc.2023-07 11:39Fremont, CA2020 Tesla Model 3ADASOther Fixed ObjectUnknown65Highway / FreewayRedacted by NHTSA as confidential business information
13781-6047Level 2Tesla, Inc.2023-07 19:38Bloomington, IL2020 Tesla Model YADASPickup TruckUnknown22IntersectionRedacted by NHTSA as confidential business information
13781-6118Level 2Tesla, Inc.2023-07 09:16Camp Springs, MD2019 Tesla Model 3ADASOther Fixed ObjectUnknown52Highway / FreewayRedacted by NHTSA as confidential business information
13781-6120Level 2Tesla, Inc.2023-07 01:33Morro Bay, CA2022 Tesla Model 3ADASPassenger CarUnknown41Highway / FreewayRedacted by NHTSA as confidential business information
13781-6122Level 2Tesla, Inc.2023-07 11:23Humble, TX2019 Tesla Model 3ADASPassenger CarUnknown47IntersectionRedacted by NHTSA as confidential business information
13781-6696Level 2Tesla, Inc.2023-07WY2022 Tesla Model YADASAnimalUnknown43Rural RoadRedacted by NHTSA as confidential business information
13781-6777Level 2Tesla, Inc.2023-07Los Angeles, CA2023 Tesla Model 3ADASOther Fixed ObjectUnknown75Highway / FreewayRedacted by NHTSA as confidential business information
13781-8205 v2Level 2Tesla, Inc.2023-07 15:01Hollister, CA2023 Tesla Model 3Unknown, see NarrativeUnknownFatality65Highway / FreewayRedacted by NHTSA as confidential business information
13781-9691Level 2Tesla, Inc.2023-07 20:33Los Angeles, CA2020 Tesla Model XADASPassenger CarUnknown36StreetRedacted by NHTSA as confidential business information
13781-9692Level 2Tesla, Inc.2023-07 19:13McCartys Village, NM2022 Tesla Model YADASOther, see NarrativeUnknown83Highway / FreewayRedacted by NHTSA as confidential business information
13781-9693Level 2Tesla, Inc.2023-07 04:27Rancho Mirage, CA2020 Tesla Model XADASUnknownUnknown25UnknownRedacted by NHTSA as confidential business information
13781-9694Level 2Tesla, Inc.2023-07 12:23Northfield, WI2021 Tesla Model YADASPassenger CarUnknown75Highway / FreewayRedacted by NHTSA as confidential business information
13781-9695Level 2Tesla, Inc.2023-07 10:30Danbury, PA2023 Tesla Model YADASOther Fixed ObjectUnknown79Highway / FreewayRedacted by NHTSA as confidential business information
13781-9696Level 2Tesla, Inc.2023-07 15:22West Windsor Township, NJ2023 Tesla Model 3ADASPassenger CarUnknown24Highway / FreewayRedacted by NHTSA as confidential business information
13781-9709Level 2Tesla, Inc.2023-07 23:22Ogden, UT2022 Tesla Model YADASPassenger CarUnknown44StreetRedacted by NHTSA as confidential business information
13781-9710Level 2Tesla, Inc.2023-07 11:18Downey, CA2022 Tesla Model 3ADASOther Fixed ObjectUnknown79Highway / FreewayRedacted by NHTSA as confidential business information
13781-9711Level 2Tesla, Inc.2023-07 13:39Union City, CA2023 Tesla Model YADASOther Fixed ObjectUnknown53Highway / FreewayRedacted by NHTSA as confidential business information
13781-9712Level 2Tesla, Inc.2023-07 22:08Ventura, CA2023 Tesla Model 3ADASOther Fixed ObjectUnknown73Highway / FreewayRedacted by NHTSA as confidential business information
13781-9713Level 2Tesla, Inc.2023-07 01:53Los Angeles, CA2023 Tesla Model YADASPassenger CarUnknown53StreetRedacted by NHTSA as confidential business information
13781-9714Level 2Tesla, Inc.2023-07 23:51Sunol, CA2023 Tesla Model YADASPassenger CarUnknown27Highway / FreewayRedacted by NHTSA as confidential business information
13781-9770Level 2Tesla, Inc.2023-07 03:13Fremont, CA2023 Tesla Model YADASHeavy TruckUnknown19IntersectionRedacted by NHTSA as confidential business information
13781-9771Level 2Tesla, Inc.2023-07 14:20North Stonington, CT2021 Tesla Model YADASUnknownUnknownHighway / FreewayRedacted by NHTSA as confidential business information
13781-9772Level 2Tesla, Inc.2023-07 00:49Lafayette, CA2021 Tesla Model YADASHeavy TruckUnknown24Highway / FreewayRedacted by NHTSA as confidential business information
13781-9773Level 2Tesla, Inc.2023-07 22:16West Nantmeal Township, PA2021 Tesla Model 3ADASUnknownUnknown33UnknownRedacted by NHTSA as confidential business information
13781-9774 v2Level 2Tesla, Inc.2023-07 17:25Los Angeles, CA2020 Tesla Model XADASPassenger CarUnknown17Highway / FreewayRedacted by NHTSA as confidential business information
13781-9775Level 2Tesla, Inc.2023-07 13:25Charlotte, NC2021 Tesla Model 3ADASPassenger CarUnknown32Highway / FreewayRedacted by NHTSA as confidential business information
13781-9777Level 2Tesla, Inc.2023-07 22:16Vantage, WA2018 Tesla Model XADASUnknownUnknown77UnknownRedacted by NHTSA as confidential business information
13781-9778Level 2Tesla, Inc.2023-07 13:53Costa Mesa, CA2018 Tesla Model 3ADASPickup TruckUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-9779Level 2Tesla, Inc.2023-07 13:15Somerset, PA2021 Tesla Model YADASOther Fixed ObjectUnknownHighway / FreewayRedacted by NHTSA as confidential business information
30270-5855 v2ADSWaymo LLC2023-07 15:08Los Angeles, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported2Intersection
The content of this report is unchanged from the initial report submitted on July 10, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle (Waymo A…The content of this report is unchanged from the initial report submitted on July 10, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and preparing to make a right turn onto westbound [XXX]. As the Waymo AV was yielding to cross-traffic and preparing to make a right turn, a cyclist was traveling eastbound on [XXX] and heading the wrong way in the bike lane. The cyclist then turned left, northbound, onto [XXX], continuing to travel the wrong direction in the bike lane. As the Waymo AV slowly proceeded forward, the cyclist passed the Waymo AV and made contact with the rear passenger side sensor 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 and the cyclist did not stop, leaving the scene without exchanging information. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a cyclist was involved. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5896ADSWaymo LLC2023-07 18:13Chandler, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On July [XXX], 2023 at 6:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and ju…On July [XXX], 2023 at 6:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and just passed [XXX] when an oncoming passenger car crossed into the Waymo AVs lane, toward the Waymo AV. The Waymo AV then stopped as the passenger vehicle continued to approach. The passenger vehicle then made contact with the front of the Waymo AV, and then made contact with the side of the Waymo AV as it left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5997ADSWaymo LLC2023-07 15:34Tempe, AZ2021 Jaguar I-PaceADSPassenger CarMinor3Street
On July [XXX], 2023 at 3:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in …On July [XXX], 2023 at 3:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in the left lane with a vehicle overtaking it in the right adjacent lane when it detected a large, fallen tree branch in part of its lane and applied braking in response. As the Waymo AV was braking and had slowed to 3 mph, a passenger vehicle behind the Waymo made contact with the rear of the Waymo AV. Moments later, an SUV behind the passenger vehicle made contact with the rear of the passenger vehicle. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. All vehicles sustained damage. Rather than wearing the seat belt, the passenger in the Waymo AV was sitting on the buckled seat belt at the time of the collision. The passenger declined medical attention. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5998ADSWaymo LLC2023-07 15:04San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported9Intersection
On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the cu…On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] at [XXX] when it began to pull away from the curb and into traffic. As the Waymo AV pulled away from the curb, a pickup truck that was 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 engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6129ADSWaymo LLC2023-07 13:13San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported4Street
On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XX…On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it began to brake as it approached a stopped van on the oncoming side of the narrow roadway. The Waymo AV test driver transitioned to manual mode and began proceeding straight when the passenger side front sensor housing of the Waymo AV made contact with the driver side mirror of a passenger car parked along the curb on southbound [XXX]. 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. 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-6130ADSWaymo LLC2023-07 10:13San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] i…On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] in autonomous mode, the Waymo AV slowed to a stop while entering a narrow roadway. The test driver transitioned the vehicle to manual mode and proceeded forward, making contact with a parked SUV. 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 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-6131ADSWaymo LLC2023-07 9:02Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On July [XXX], 2023 at 9:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parallel parked along the right-hand …On July [XXX], 2023 at 9:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parallel parked along the right-hand curb on eastbound [XXX] when a passenger car reversed out of a driveway across the street from the Waymo AV and made contact with the driver side rear bumper 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-6132ADSWaymo LLC2023-07 9:51San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On July [XXX], 2023 at 9:51 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The collision occurred while the Waymo AV w…On July [XXX], 2023 at 9:51 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The collision occurred while the Waymo AV was stopped in the leftmost lane of a two-lane, one-way road at the intersection of [XXX] at [XXX]. The Waymo AV was facing a green light, but stopped before entering the intersection because traffic was stacked on the other side of the intersection, leaving no space for the AV. When the light turned yellow, a passenger car that had been stopped behind the Waymo AV passed the Waymo AV on the left and proceeded into the intersection. While passing the Waymo AV, the passenger cars rear passenger side door made contact with the driver side rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The passenger car did not stop but appears to have 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-6133ADSWaymo LLC2023-07 11:11San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Street
On July [XXX], 2023 at 11:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] east of [XXX]. The Waymo AV was facing east, waiting to merge t…On July [XXX], 2023 at 11:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] east of [XXX]. The Waymo AV was facing east, waiting to merge to the left back into eastbound traffic on [XXX], and stopped to the left of the right turn slip lane on [XXX], with stopped traffic to the right. After waiting to merge, the Waymo AV started reversing to reroute and while doing so, a sensor on the right front of the Waymo AV made contact with the left rear side of an SUV in the right turn lane. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The SUV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6134ADSWaymo LLC2023-07 14:57Santa Monica, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported0Street
On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbo…On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbound [XXX] when a cyclist that had been traveling behind the Waymo AV passed the Waymo AV on the right. As the cyclist passed the Waymo AV, the cyclist made contact with the front passenger side sensor 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 and the cyclist did not stop, leaving the scene without exchanging information. 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-5848ADSCruise LLC2023-07 22:47San Francisco, CA2023 Cruise AVADSPickup TruckNo Injuries Reported4StreetRedacted by NHTSA as confidential business information
30412-5968ADSCruise LLC2023-07 23:08San Francisco, CA2023 Cruise AVADSSUVMinor15IntersectionRedacted by NHTSA as confidential business information
30412-5980ADSCruise LLC2023-07 19:50Austin, TX2023 Cruise AVADSSUVNo Injuries Reported20IntersectionRedacted by NHTSA as confidential business information
30412-5981ADSCruise LLC2023-07 01:56San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-5982 v2ADSCruise LLC2023-07 06:41San Francisco, CA2023 Cruise AVADSPassenger CarUnknown0IntersectionRedacted by NHTSA as confidential business information
30412-5989ADSCruise LLC2023-07 20:38Tempe, AZ2022 Cruise AVADSPassenger CarMinor27StreetRedacted by NHTSA as confidential business information
30412-5992ADSCruise LLC2023-07 05:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported22IntersectionRedacted by NHTSA as confidential business information
30412-5993ADSCruise LLC2023-07 14:45San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported10IntersectionRedacted by NHTSA as confidential business information
30412-6006ADSCruise LLC2023-07 23:51San Francisco, CA2022 Cruise AVADSPickup TruckNo Injuries Reported2IntersectionRedacted by NHTSA as confidential business information
30412-6037ADSCruise LLC2023-07 01:52San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported6StreetRedacted by NHTSA as confidential business information
30412-6038ADSCruise LLC2023-07 20:56San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6039 v2ADSCruise LLC2023-07 22:34San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported1Street
A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was at a complete stop in response to a red light in the leftmost turn lane on westbound [XXX] at the intersection with [XXX]. When the light t…A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was at a complete stop in response to a red light in the leftmost turn lane on westbound [XXX] at the intersection with [XXX]. When the light turned green, both the AV and a GMC Yukon in the adjacent lane attempted a left turn onto southbound [XXX]. The AV veered slightly to the right into the [XXX] before attempting its left turn, making contact as the Yukon began its turn. This caused damage to the AV's front passenger side radar assembly. The driver of the GMC Yukon left the scene without exchanging information. There were no reported injuries.
30412-6040ADSCruise LLC2023-07 00:07San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported23StreetRedacted by NHTSA as confidential business information
30412-6041ADSCruise LLC2023-07 10:47San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported2StreetRedacted by NHTSA as confidential business information
30412-6042ADSCruise LLC2023-07 16:16San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6043ADSCruise LLC2023-07 02:29Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6044ADSCruise LLC2023-07 22:41San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1IntersectionRedacted by NHTSA as confidential business information
30413-6032ADSMay Mobility2023-07 17:25Grand Rapids, MN2021 Toyota SiennaADSPickup TruckNo Injuries Reported0Street
The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and…The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and slowed down to a stop in a safe manner. The collision was unavoidable from the shuttle side.
30530-6125ADSAurora Operations, Inc.2023-07 09:35BUFFALO, TX2022 Peterbilt 579mADSOther, see NarrativeNo Injuries Reported64Highway / Freeway
At 09:35 AM CDT on July [XXX], 2023, an Aurora Class 8 truck was traveling southbound in autonomy mode on [XXX] near [XXX] when the front windshield was struck by an unknown object. The bottom of the windshield had a ho…At 09:35 AM CDT on July [XXX], 2023, an Aurora Class 8 truck was traveling southbound in autonomy mode on [XXX] near [XXX] when the front windshield was struck by an unknown object. The bottom of the windshield had a hole about 3 inches in diameter. The vehicle operator disengaged autonomy and pulled over. The vehicle was able to be driven from the scene, and there were no reported injuries.
30531-5871 v2ADSTransdev Alternative Services2023-07 15:08Los Angeles, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported2Intersection
The content of this report in unchanged from the initial report submitted on July 10, 2023 (Report ID # 30531-5871-1) On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, Ca…The content of this report in unchanged from the initial report submitted on July 10, 2023 (Report ID # 30531-5871-1) On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and preparing to make a right turn onto westbound [XXX]. As the Waymo AV was yielding to cross-traffic and preparing to make a right turn, a cyclist was traveling eastbound on [XXX] and heading the wrong way in the bike lane. The Cyclist then turned left, northbound, onto [XXX], continuing to travel the wrong direction in the bike lane. As the Waymo AV slowly proceeded forward, the cyclist passed the Waymo AV and made contact with the rear passenger side sensor 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 and the cyclist did not stop. Transdev Alternative Services is reporting a duplicate report from report number: 30270-5855-1.
30531-5999ADSTransdev Alternative Services2023-07 15:04San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported9Intersection
On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the c…On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] at [XXX] when it began to pull away from the curb and into traffic. As the Waymo AV pulled away from the curb, a pickup truck that was 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 engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage.
30531-6136ADSTransdev Alternative Services2023-07 14:57Santa Monica, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported0Street
On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwest…On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbound [XXX] when a cyclist that had been traveling behind the Waymo AV passed the Waymo AV on the right. As the cyclist passed the Waymo AV, the cyclist made contact with the front passenger side sensor 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 and the cyclist did not stop, leaving the scene without exchanging information. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report id: 30270-6134-1.
30531-6137ADSTransdev Alternative Services2023-07 10:13San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX…On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] in autonomous mode, the Waymo AV slowed to a stop while entering a narrow roadway. The test driver transitioned the vehicle to manual mode and proceeded forward, making contact with a parked 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. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-6130-1.
30531-6138ADSTransdev Alternative Services2023-07 13:13San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported4Street
On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [X…On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it began to brake as it approached a stopped van on the oncoming side of the narrow roadway. The Waymo AV test driver transitioned to manual mode and began proceeding straight when the passenger side front sensor housing of the Waymo AV made contact with the driver side mirror of a passenger car parked along the curb on southbound [XXX]. At the time of the impact, the Waymo's 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. 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 report 30270-6129-1.
540-5875ADSGeneral Motors, LLC2023-07 22:47San Francisco, CA2023 Cruise AVADSPickup TruckNo Injuries Reported4Street
On July 11, 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 t…On July 11, 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-5848-1)
540-5971ADSGeneral Motors, LLC2023-07 23:08San Francisco, CA2023 Cruise AVADSSUVMinor15Intersection
On July 19,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 th…On July 19,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-5968-1)
540-5987 v2ADSGeneral Motors, LLC2023-07 06:41San Francisco, CA2023 Cruise AVADSPassenger CarUnknown0Intersection
On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-Day Updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the Order). General Motors LLC (GM)…On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-Day Updated 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-5982-2)
540-5988ADSGeneral Motors, LLC2023-07 19:50Austin, TX2023 Cruise AVADSSUVNo Injuries Reported20Intersection
On July 24, 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 July 24, 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-5980-1)
540-5990ADSGeneral Motors, LLC2023-07 01:56San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On July 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 July 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-5981-1)
540-5991ADSGeneral Motors, LLC2023-07 20:38Tempe, AZ2022 Cruise AVADSPassenger CarMinor27Street
On July 26, 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 Cr…On July 26, 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-5989-1)
540-6002ADSGeneral Motors, LLC2023-07 05:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported22Intersection
On July 27, 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 July 27, 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-5992-1)
540-6003ADSGeneral Motors, LLC2023-07 14:45San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported10Intersection
On July 27, 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 July 27, 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-5993-1).
540-6009Level 2General Motors, LLC2023-07 00:23Cleveland, OH2023 Chevrolet Bolt EUVADASOther Fixed ObjectUnknown9Highway / Freeway
At 12:23 AM, July [XXX], 2023, a Chevrolet Bolt EUV was traveling south on [XXX] near the [XXX] in Cleveland, Ohio. The vehicle struck the right-hand highway cement barrier. Based on the crash data, there was sufficien…At 12:23 AM, July [XXX], 2023, a Chevrolet Bolt EUV was traveling south on [XXX] near the [XXX] in Cleveland, Ohio. The vehicle struck the right-hand highway cement barrier. Based on the crash data, there was sufficient lateral input to deploy the side airbags, suggesting the vehicle's right side front quarter panel and passenger door made contact with the barrier. Crash data indicates that Super Cruise was last active approximately 22 seconds prior to the crash. At that time, steering wheel input caused an override of the Super Cruise system. The crash occurred at 00:23:48. A pre-crash speed of 9.4 mph was the last vehicle speed recorded, approximately 2 seconds prior to the crash.
540-6011ADSGeneral Motors, LLC2023-07 23:51San Francisco, CA2022 Cruise AVADSPickup TruckNo Injuries Reported2Intersection
On August 2, 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 August 2, 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-6006-1)
540-6058ADSGeneral Motors, LLC2023-07 01:52San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported6Street
On August 11, 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) manufacture…On August 11, 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-6037-1).
540-6069ADSGeneral Motors, LLC2023-07 20:56San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On August 11, 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) manufacture…On August 11, 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-6038-1).
540-6070 v2ADSGeneral Motors, LLC2023-07 22:34San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported1Street
On September 26, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) …On September 26, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated 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-6039-2)
540-6072ADSGeneral Motors, LLC2023-07 00:07San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported23Street
On August 11, 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) manufacture…On August 11, 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-6040-1).
540-6073ADSGeneral Motors, LLC2023-07 10:47San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported2Street
On August 11, 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) manufacture…On August 11, 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-6041-1).
540-6074ADSGeneral Motors, LLC2023-07 16:16San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On August 11, 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) manufacture…On August 11, 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-6042-1).
540-6076ADSGeneral Motors, LLC2023-07 02:29Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On August 11, 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) manufacture…On August 11, 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-6043).
540-6079ADSGeneral Motors, LLC2023-07 22:41San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1Intersection
On August 11, 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) manufacture…On August 11, 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-6044-1).
1243-5798 v2Level 2Subaru of America, Inc.2023-06 12:50Mayflower, AR2024 Subaru OutbackADASUnknownNo Injuries Reported50Highway / FreewayRedacted by NHTSA as confidential business information
13781-5673 v2Level 2Tesla, Inc.2023-06 11:08Central Point, OR2015 Tesla Model SADASPole / TreeFatalityHighway / FreewayRedacted by NHTSA as confidential business information
13781-5679Level 2Tesla, Inc.2023-06 19:14Simi Valley, CA2022 Tesla Model 3ADASOther Fixed ObjectUnknown42IntersectionRedacted by NHTSA as confidential business information
13781-5680Level 2Tesla, Inc.2023-06 15:00Harrisville, UT2021 Tesla Model YADASSUVUnknown46StreetRedacted by NHTSA as confidential business information
13781-5681Level 2Tesla, Inc.2023-06 06:35Los Angeles, CA2023 Tesla Model 3ADASUnknownUnknown45StreetRedacted by NHTSA as confidential business information
13781-5682Level 2Tesla, Inc.2023-06 13:35North Manchester, IN2021 Tesla Model YADASOther, see NarrativeUnknown58StreetRedacted by NHTSA as confidential business information
13781-5683Level 2Tesla, Inc.2023-06 22:53Sierra Vista, AZ2020 Tesla Model XADASUnknownUnknown18StreetRedacted by NHTSA as confidential business information
13781-5685 v2Level 2Tesla, Inc.2023-06Brooklyn, NY2021 Tesla Model SADASNon-Motorist: PedestrianFatality44IntersectionRedacted by NHTSA as confidential business information
13781-5703Level 2Tesla, Inc.2023-06 23:39West Chester Township, OH2019 Tesla Model 3ADASUnknownUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-5704Level 2Tesla, Inc.2023-06 18:42Saranac, MI2021 Tesla Model 3ADASPickup TruckUnknown60IntersectionRedacted by NHTSA as confidential business information
13781-5773Level 2Tesla, Inc.2023-06 18:44Alachua, FL2020 Tesla Model 3ADASSUVUnknown34IntersectionRedacted by NHTSA as confidential business information
13781-5774Level 2Tesla, Inc.2023-06 04:16North Miami Beach, FL2022 Tesla Model SADASPassenger CarUnknown72Highway / FreewayRedacted by NHTSA as confidential business information
13781-5775Level 2Tesla, Inc.2023-06 21:12Jackson, GA2022 Tesla Model YADASUnknownUnknown22Highway / FreewayRedacted by NHTSA as confidential business information
13781-5776Level 2Tesla, Inc.2023-06 21:24Bermuda Run, NC2021 Tesla Model 3ADASOther Fixed ObjectUnknown53Highway / FreewayRedacted by NHTSA as confidential business information
13781-5777Level 2Tesla, Inc.2023-06 05:39Long Beach, CA2022 Tesla Model 3ADASUnknownUnknown61UnknownRedacted by NHTSA as confidential business information
13781-5783Level 2Tesla, Inc.2023-06 04:58Redmond, WA2019 Tesla Model 3ADASPole / TreeUnknown36IntersectionRedacted by NHTSA as confidential business information
13781-5784Level 2Tesla, Inc.2023-06 15:31Collinsville, IL2018 Tesla Model 3ADASSUVUnknown25IntersectionRedacted 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. 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.