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
Clear filters

520 reports, showing 401 to 500.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
1420-7995ADSVolkswagen Group of America, Inc.2024-06 12:54Austin, TX2023 Volkswagen ID.BuzzADSSUVNo Injuries Reported9Street
The subject vehicle (autonomous vehicle - AV) was stopped at a red traffic light, in a queue of vehicles, heading west on [XXX], with autonomous driving (AD) mode engaged. Once the light turned green, the queue of vehicl…The subject vehicle (autonomous vehicle - AV) was stopped at a red traffic light, in a queue of vehicles, heading west on [XXX], with autonomous driving (AD) mode engaged. Once the light turned green, the queue of vehicles started to move forward, the AV started to move forward with the queue, and prior to crossing the intersection, the AV was struck from behind by an SUV. After impact the safety driver of the AV applied the brakes to disengage AD mode and then proceeded to find a safe spot to assess the incident by turning right onto [XXX]. The driver of the SUV followed the AV to a safe location to assess the incident and exchange contact information. There were no reported injuries, airbag deployments, or tow-aways between either party involved. The AV sustained minor damage to the rear of the vehicle including the rear bumper cover, rear bumper carrier, and a rear facing camera. The SUV damage was reported as scratches and dents to the front bumper cover. Both vehicles were able to safely drive away from the scene. VWGoA does not plan to investigate the incident any further as the facts and circumstances do not indicate any issue with the vehicle's performance.
30291-7981ADSNuro2024-06 17:10Houston, TX2022 Toyota PriusADSPassenger CarNo Injuries Reported14Intersection
At approximately 5:10pm CDT, a passenger vehicle collided with a Nuro Prius operating in manual mode in Houston, Texas. Prior to the collision, the Nuro Prius operating autonomously came to a stop at the intersection of…At approximately 5:10pm CDT, a passenger vehicle collided with a Nuro Prius operating in manual mode in Houston, Texas. Prior to the collision, the Nuro Prius operating autonomously came to a stop at the intersection of [XXX] and [XXX]. The Nuro operator disengaged autonomy, switched to manual, and proceeded to make a left turn. A passenger vehicle collided with the Nuro Prius before the driver completed the turn. No injuries were reported. Both vehicles sustained damage. Law enforcement was not involved.
30530-7891ADSAurora Operations, Inc.2024-06 13:19SPRING, TX2024 Peterbilt 579ADSOther, see NarrativeNo Injuries Reported55Highway / Freeway
On June [XXX], 2024, at approximately 1:19 PM CDT, an Aurora truck struck a blown-out tire/rim assembly that suddenly moved into the lane of travel on [XXX] near Oak Ridge North, TX. Aurora vehicle operators were not inj…On June [XXX], 2024, at approximately 1:19 PM CDT, an Aurora truck struck a blown-out tire/rim assembly that suddenly moved into the lane of travel on [XXX] near Oak Ridge North, TX. Aurora vehicle operators were not injured. Aurora disengaged autonomy before impact and pulled to the shoulder to inspect the vehicle. The inspection revealed minor damage to the truck's front bumper and a torn air brake hose. The Aurora truck was towed from the scene.
30530-8087ADSAurora Operations, Inc.2024-06 23:14Huntsville, TX2024 Peterbilt 579ADSOther, see NarrativeNo Injuries Reported65Highway / Freeway
On June [XXX] at approximately 11:14 PM CDT, an Aurora truck traveling southbound on [XXX] near mile [XXX] struck an unknown object in the lane. A vehicle immediately in front of the Aurora truck swerved abruptly to avoi…On June [XXX] at approximately 11:14 PM CDT, an Aurora truck traveling southbound on [XXX] near mile [XXX] struck an unknown object in the lane. A vehicle immediately in front of the Aurora truck swerved abruptly to avoid the object, leaving the vehicle operators and the Aurora Driver minimal time to avoid it. The Aurora truck was operating in autonomy at the time. The vehicle operators stopped at a safe location to inspect the vehicle, but initially found no damage. During a subsequent fuel stop a few hours later, they noticed minor damage to the right fairing of the truck which wasn't previously visible. The vehicle operators reported the damage and continued the mission in manual.
33175-9303ADSMobileye Vision Technologies2024-06 12:54Austin, TX2023 Volkswagen ID.BuzzADSSUVNo Injuries ReportedStreet
On JUL-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7995 - the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO").…On JUL-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7995 - the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO"). The subject vehicle referred to in the Report contains the Reporter's software and hardware. Since the Reporter is also a Reporting Entity under the SGO, the Reporter hereby submits this report. In order to avoid duplications and additional CBI requests, this submission includes the publicly available information of the Report and incorporates the Report by reference. This submission is based on the information provided to the Reporter by VW. The Reporter currently believes that it has no independent knowledge of the information in this report. From Volkswagen: The subject vehicle (autonomous vehicle - AV) was stopped at a red traffic light, in a queue of vehicles, heading west on [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], with autonomous driving (AD) mode engaged. Once the light turned green, the queue of vehicles started to move forward, the AV started to move forward with the queue, and prior to crossing the intersection, the AV was struck from behind by an SUV. After impact the safety driver of the AV applied the brakes to disengage AD mode and then proceeded to find a safe spot to assess the incident by turning right onto [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. The driver of the SUV followed the AV to a safe location to assess the incident and exchange contact information. There were no reported injuries, airbag deployments, or tow-aways between either party involved. The AV sustained minor damage to the rear of the vehicle including the rear bumper cover, rear bumper carrier, and a rear facing camera. The SUV damage was reported as scratches and dents to the front bumper cover. Both vehicles were able to safely drive away from the scene. VWGoA does not plan to investigate the incident any further as the facts and circumstances do not indicate any issue with the vehicle's performance.
988-7915ADSPACCAR Incorporated2024-06 13:19SPRING, TX2024 Peterbilt 579ADSOther, see NarrativeNo Injuries Reported55Highway / Freeway
On June [XXX], 2024, at approximately 1:19 PM CDT, an Aurora truck struck a blown-out tire/rim assembly that suddenly moved into the lane of travel on [XXX] near Oak Ridge North, TX. Aurora vehicle operators were not inj…On June [XXX], 2024, at approximately 1:19 PM CDT, an Aurora truck struck a blown-out tire/rim assembly that suddenly moved into the lane of travel on [XXX] near Oak Ridge North, TX. Aurora vehicle operators were not injured. Aurora disengaged autonomy before impact and pulled to the shoulder to inspect the vehicle. The inspection revealed minor damage to the truck's front bumper and a torn air brake hose. The Aurora truck was towed from the scene
988-8119ADSPACCAR Incorporated2024-06 23:14Huntsville, TX2024 Peterbilt 579ADSOther, see NarrativeNo Injuries Reported65Highway / Freeway
On June [XXX] at approximately 11:14 PM CDT, an Aurora truck traveling southbound on [XXX] near mile marker [XXX] struck an unknown object in the lane. A vehicle immediately in front of the Aurora truck swerved abruptly …On June [XXX] at approximately 11:14 PM CDT, an Aurora truck traveling southbound on [XXX] near mile marker [XXX] struck an unknown object in the lane. A vehicle immediately in front of the Aurora truck swerved abruptly to avoid the object, leaving the vehicle operators and the Aurora Driver minimal time to avoid it. The Aurora truck was operating in autonomy at the time. The vehicle operators stopped at a safe location to inspect the vehicle, but initially found no damage. During a subsequent fuel stop a few hours later, they noticed minor damage to the right fairing of the truck which wasn't previously visible. The vehicle operators reported the damage and continued the mission in manual.
1420-7914ADSVolkswagen Group of America, Inc.2024-05 14:23Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Parking Lot
The subject vehicle (autonomous vehicle - AV) was proceeding through a parking garage while engaged in autonomous driving (AD) mode. The AV detected an oncoming passenger vehicle (PV), made adjustments to its route by m…The subject vehicle (autonomous vehicle - AV) was proceeding through a parking garage while engaged in autonomous driving (AD) mode. The AV detected an oncoming passenger vehicle (PV), made adjustments to its route by moving to the right, and slowed to a stop to provide additional space for the PV. As the PV passed, it attempted to make a left-hand turn behind the AV, but the PV's driver side mirror scraped the rear driver's side LiDAR housing of the AV. The passenger vehicle continued driving without stopping. After noticing the contact, the safety driver of the subject vehicle manually disengaged AD mode to assess the incident. There were no reported injuries, airbag deployments, or tow-aways. The damage to the subject vehicle was a scuff to the driver's side Short Range LiDAR trim cover. VWGoA does not plan to investigate the incident any further as the facts and circumstances do not indicate any issue with the vehicle's performance.
30291-7677ADSNuro2024-05 12:04Houston, TX2022 Toyota PriusADSPassenger CarNo Injuries Reported1Intersection
At approximately 12pm CST, May [XXX], 2024, a passenger vehicle rear-ended a Nuro Prius operating in autonomous mode at the intersection of [XXX] and [XXX] in Houston, Texas. The Nuro Prius was coming to a stop as the tr…At approximately 12pm CST, May [XXX], 2024, a passenger vehicle rear-ended a Nuro Prius operating in autonomous mode at the intersection of [XXX] and [XXX] in Houston, Texas. The Nuro Prius was coming to a stop as the traffic signal changed from yellow to red. Shortly after the light turned red, a passenger vehicle rear-ended the Nuro Prius. No injuries were reported at the scene and law enforcement were not involved. Both vehicles sustained minimal damage.
30530-7892ADSAurora Operations, Inc.2024-05 03:09RICE, TX2024 Peterbilt 579ADSAnimalNo Injuries Reported65Highway / Freeway
On May [XXX], 2024, at 3:09 AM CDT, an Aurora truck struck a small animal on [XXX] near Corsicana, TX. Aurora disengaged autonomy before impact. Aurora vehicle operators were not injured. The Aurora truck sustained mino…On May [XXX], 2024, at 3:09 AM CDT, an Aurora truck struck a small animal on [XXX] near Corsicana, TX. Aurora disengaged autonomy before impact. Aurora vehicle operators were not injured. The Aurora truck sustained minor damage to its front bumper, and the truck continued to its final destination in Palmer, TX.
33175-9304ADSMobileye Vision Technologies2024-05 14:23Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Parking Lot
On JUN-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7914- the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO"). …On JUN-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7914- the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO"). The subject vehicle referred to in the Report contains the Reporter's software and hardware. Since the Reporter is also a Reporting Entity under the SGO, the Reporter hereby submits this report. In order to avoid duplications and additional CBI requests, this submission includes the publicly available information of the Report and incorporates the Report by reference. This submission is based on the information provided to the Reporter by VW. The Reporter currently believes that it has no independent knowledge of the information in this report. From Volkswagen: The subject vehicle (autonomous vehicle - AV) was proceeding through a parking garage while engaged in autonomous driving (AD) mode. The AV detected an oncoming passenger vehicle (PV), made adjustments to its route by moving to the right, and slowed to a stop to provide additional space for the PV. As the PV passed, it attempted to make a left-hand turn behind the AV, but the PV's driver side mirror scraped the rear driver's side LiDAR housing of the AV. The passenger vehicle continued driving without stopping. After noticing the contact, the safety driver of the subject vehicle manually disengaged AD mode to assess the incident. There were no reported injuries, airbag deployments, or tow-aways. The damage to the subject vehicle was a scuff to the driver's side Short Range LiDAR trim cover. VWGoA does not plan to investigate the incident any further as the facts and circumstances do not indicate any issue with the vehicle's performance.
988-7916ADSPACCAR Incorporated2024-05 03:09Rice, TX2024 Peterbilt 579ADSAnimalNo Injuries ReportedHighway / Freeway
On May [XXX], 2024, at 3:09 AM CDT, an Aurora truck struck a small animal on [XXX] near Corsicana, TX. Aurora disengaged autonomy before impact. Aurora vehicle operators were not injured. The Aurora truck sustained minor…On May [XXX], 2024, at 3:09 AM CDT, an Aurora truck struck a small animal on [XXX] near Corsicana, TX. Aurora disengaged autonomy before impact. Aurora vehicle operators were not injured. The Aurora truck sustained minor damage on its front bumper, and the truck continued to its final destination in Palmer, TX.
1420-7671ADSVolkswagen Group of America, Inc.2024-04 10:20Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Street
The subject vehicle (autonomous vehicle- AV) was stopped, in the far right turn lane on westbound [XXX], waiting to turn right onto northbound [XXX]. The other vehicle was a 2021 Mercedes Benz GLE (MB) that was noted as …The subject vehicle (autonomous vehicle- AV) was stopped, in the far right turn lane on westbound [XXX], waiting to turn right onto northbound [XXX]. The other vehicle was a 2021 Mercedes Benz GLE (MB) that was noted as being stopped prior to making contact with the rear right bumper of the subject vehicle. The AV, while remaining stationary, was struck from the rear by the MB. The driver of the AV signaled to the other vehicle to pull over safely in the adjacent parking lot. The driver's of both vehicles exchanged information and assessed the damage. Both vehicles had one occupant and there were no reported injuries, airbag deployments, or tow-aways. The damage to the subject vehicle is stated as scratches/markings of the right rear bumper, and the damage to the other vehicle is a bent frontal license plate. Both vehicles were able to safely leave the scene. VWGoA does not plan to investigate the incident any further as the AV was within its ODD at the time of the incident and was struck from behind while waiting for traffic to clear to safely complete a turn.
30530-7680ADSAurora Operations, Inc.2024-04 10:56Conroe, TX2024 Peterbilt Peterbilt 579ADSOther, see NarrativeNo Injuries Reported62Highway / Freeway
On April [XXX], at 10:56 CDT, an Aurora truck was in autonomy traveling southbound on [XXX] in Conroe, Texas. The Aurora truck made contact with a shovel on the roadway, cracking the front left headlight. The vehicle ope…On April [XXX], at 10:56 CDT, an Aurora truck was in autonomy traveling southbound on [XXX] in Conroe, Texas. The Aurora truck made contact with a shovel on the roadway, cracking the front left headlight. The vehicle operator proceeded in manual mode to the next exit and inspected the truck. The vehicle operator determined the truck was drivable and resumed the mission in autonomy. We are not aware of any injuries or additional damage to the truck or trailer.
33175-9305ADSMobileye Vision Technologies2024-04 10:20Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Street
On MAY-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7671 - the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO").…On MAY-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7671 - the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO"). The subject vehicle referred to in the Report contains the Reporter's software and hardware. Since the Reporter is also a Reporting Entity under the SGO, the Reporter hereby submits this report. In order to avoid duplications and additional CBI requests, this submission includes the publicly available information of the Report and incorporates the Report by reference. This submission is based on the information provided to the Reporter by VW. The Reporter currently believes that it has no independent knowledge of the information in this report. From Volkswagen: The subject vehicle (autonomous vehicle- AV) was stopped, in the far right turn lane on westbound [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], waiting to turn right onto northbound [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. The other vehicle was a 2021 Mercedes Benz GLE (MB) that was noted as being stopped prior to making contact with the rear right bumper of the subject vehicle. The AV, while remaining stationary, was struck from the rear by the MB. The driver of the AV signaled to the other vehicle to pull over safely in the adjacent parking lot. The driver's of both vehicles exchanged information and assessed the damage. Both vehicles had one occupant and there were no reported injuries, airbag deployments, or tow-aways. The damage to the subject vehicle is stated as scratches/markings of the right rear bumper, and the damage to the other vehicle is a bent frontal license plate. Both vehicles were able to safely leave the scene. VWGoA does not plan to investigate the incident any further as the AV was within its ODD at the time of the incident and was struck from behind while waiting for traffic to clear to safely complete a turn.
988-7703ADSPACCAR Incorporated2024-04 10:56Conroe, TX2024 Peterbilt 579ADSOther, see NarrativeNo Injuries Reported62Highway / Freeway
On April [XXX], at 10:56 CDT, an Aurora truck was in autonomy traveling southbound on [XXX] in Conroe, Texas. The Aurora truck made contact with a shovel on the roadway, cracking the front left headlight. The vehicle ope…On April [XXX], at 10:56 CDT, an Aurora truck was in autonomy traveling southbound on [XXX] in Conroe, Texas. The Aurora truck made contact with a shovel on the roadway, cracking the front left headlight. The vehicle operator proceeded in manual mode to the next exit and inspected the truck. The vehicle operator determined the truck was drivable and resumed the mission in autonomy. We are not aware of any injuries or additional damage to the truck or trailer.
30270-7541ADSWaymo LLC2024-03 10:03Austin, TX2024 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Intersection
On March [XXX], 2024 at 10:03 AM CDT a Waymo Autonomous Vehicle (Waymo AV) operating in Austin, Texas was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling south-eastbound on [XXX] i…On March [XXX], 2024 at 10:03 AM CDT a Waymo Autonomous Vehicle (Waymo AV) operating in Austin, Texas was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling south-eastbound on [XXX] in autonomous mode when it came to a stop behind a heavy truck stopped at a stop sign at the intersection of [XXX]. The heavy truck then began reversing, and the Waymo AV test driver transitioned to manual mode. While the Waymo AV remained stopped, the heavy truck continued reversing and made contact with the front 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 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.
30530-7475ADSAurora Operations, Inc.2024-03 13:52Barstow, TX2023 Peterbilt 579ADSPassenger CarNo Injuries Reported64Highway / Freeway
This incident occurred on March [XXX], 2024 at approximately 13:52 CT near Barstow, TX on [XXX]. The Aurora truck was operating in autonomy at the time. Weather and road conditions were clear. A white passenger car veere…This incident occurred on March [XXX], 2024 at approximately 13:52 CT near Barstow, TX on [XXX]. The Aurora truck was operating in autonomy at the time. Weather and road conditions were clear. A white passenger car veered into the lane of the Aurora truck and made contact with the left rear of the trailer. The Aurora Driver detected the collision and both the passenger car and the Aurora truck pulled over to the shoulder. Aurora notified law enforcement who arrived on the scene. We have no reports of injuries. The Aurora truck had damage to its rear left impact guard (ICC bar). The white passenger car had damage to its right side front quarter panel. Both vehicles departed the scene.
30531-7548ADSTransdev Alternative Services2024-03 10:03Austin, TX2024 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Intersection
On March [XXX], 2024 at 10:03 AM CDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling sout-eastbound on [XXX] i…On March [XXX], 2024 at 10:03 AM CDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling sout-eastbound on [XXX] in autonomous mode when it came to a stop behind a heavy truck stopped at a stop sign at the intersection of [XXX]. The heavy truck then began reversing, and the Waymo AV test driver transitioned to manual mode. While the Waymo AV remained stopped, the heavy truk continued reversing and made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. This is a duplicate of report ID 30270-7541-1.
988-7550ADSPACCAR Incorporated2024-03 13:52Barstow, TX2023 Peterbilt 579ADSPassenger CarNo Injuries ReportedHighway / Freeway
This incident occurred on March [XXX], 2024 at approximately 13:52 CT near Barstow, TX on [XXX]. The Aurora truck was operating in autonomy at the time. Weather and road conditions were clear. A white passenger car veere…This incident occurred on March [XXX], 2024 at approximately 13:52 CT near Barstow, TX on [XXX]. The Aurora truck was operating in autonomy at the time. Weather and road conditions were clear. A white passenger car veered into the lane of the Aurora truck and made contact with the left rear of the trailer. The Aurora Driver detected the collision and both the passenger car and the Aurora truck pulled over to the shoulder. Aurora notified law enforcement who arrived on the scene. We have no reports of injuries. The Aurora truck had damage to its rear left impact guard (ICC bar). The white passenger car had damage to its right side front quarter panel. Both vehicles departed the scene.
1420-7244ADSVolkswagen Group of America, Inc.2024-02 11:20Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Intersection
The subject vehicle was stopped at the intersection of [XXX] and [XXX] with the ADS system engaged, waiting for the traffic light to turn green. The passenger car (Toyota Tacoma, equipped with front grille/brush guard) a…The subject vehicle was stopped at the intersection of [XXX] and [XXX] with the ADS system engaged, waiting for the traffic light to turn green. The passenger car (Toyota Tacoma, equipped with front grille/brush guard) approached from behind, honked the horn, and struck the stationary subject vehicle. The driver of the subject vehicle proceed through the intersection and pulled over into an empty parking lot to safely assess the incident. The passenger car is noted as remaining at the light for an additional cycle of the traffic light before driving off and not pulling over with the vehicle it just struck. The subject vehicle's 3 occupants reported feeling the impact but report no injuries, airbag deployments, or tow-aways. The subject vehicle's damage was to the right rear bumper, including the right rear sensor and mounting bracket.
30270-7164 v2ADSWaymo LLC2024-02 17:01Austin, TX2024 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
This report is being submitted to correct a clerical error in the Driver / Operator Type field that was originally reported on February 15, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. Otherwise, the c…This report is being submitted to correct a clerical error in the Driver / Operator Type field that was originally reported on February 15, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. Otherwise, the content of this report is unchanged. On February [XXX], 2024 at 3:01 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Austin, Texas was in a collision involving a passenger vehicle on a slip-lane between [XXX] and [XXX]. The Waymo AV was in the slip-lane connecting [XXX] and [XXX], preparing to merge onto northbound [XXX] with a passenger vehicle behind it. As the Waymo AV proceeded forward, actively yielding to approaching traffic, it stopped for additional approaching traffic. The passenger vehicle 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. 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.
30530-7141ADSAurora Operations, Inc.2024-02 14:03Streetman, TX2023 Peterbilt 579ADSHeavy TruckNo Injuries Reported62Highway / Freeway
This incident occurred near Streetman, TX on [XXX] at approximately 3:03 PM CT on February [XXX], 2024. The Aurora vehicle was operating in autonomy at the time. Conditions were clear. As the Aurora vehicle was driving i…This incident occurred near Streetman, TX on [XXX] at approximately 3:03 PM CT on February [XXX], 2024. The Aurora vehicle was operating in autonomy at the time. Conditions were clear. As the Aurora vehicle was driving in its lane at 62 mph, a box truck veered into the lane of the Aurora vehicle. The box truck's mirror appeared to make contact with the back of the trailer that the Aurora Driver was pulling. At this time, we are not aware of any injuries, and camera footage appears to show that the box truck continued to drive. From the post-trip inspection, there was not any visible trailer damage. Before the collision, the Aurora Driver was driving straight in its lane and passing the box truck. Shortly thereafter, the box truck began to encroach into the lane of the Aurora Driver. The Aurora Driver detected the box truck's encroachment into the Aurora vehicle's lane and initiated a nudge away from the box truck to provide space. The Aurora Driver detected the collision and made the decision to initiate an incident response, but before it could execute that response, the Vehicle Operator took over control of the system and proceeded in manual. The Aurora vehicle then re-engaged in autonomy approximately two minutes later. The Vehicle Operator did not visually observe the collision, assumed the reaction of the Aurora Driver to be a software anomaly, and reported the vehicle nudge through our standard annotation protocol rather than through our incident response protocols. We identified the incident at approximately 1:03 PM CT on February [XXX], 2024 through a review of our data logs.
30531-7177ADSTransdev Alternative Services2024-02 17:01Austin, TX2024 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On February [XXX], 2024 at 3:01 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger vehicle on a slip-lane between [XXX] and [XXX]. The Waymo AV was in a slip…On February [XXX], 2024 at 3:01 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger vehicle on a slip-lane between [XXX] and [XXX]. The Waymo AV was in a slip-lane connecting [XXX] and [XXX], preparing to merge onto northbound [XXX] with a passenger vehicle behind it. As the Waymo AV proceeded forward, actively yielding to approaching traffic, it stopped for additional approaching traffic. The passenger vehicle traveling behind the Waymo AV the made contact with the rear of the Waymo AV. At the time of the impact, the Waymo's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30270-7164-1.
33175-9306ADSMobileye Vision Technologies2024-02 11:20Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Intersection
On MAR-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7244 - the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO").…On MAR-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7244 - the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO"). The subject vehicle referred to in the Report contains the Reporter's software and hardware. Since the Reporter is also a Reporting Entity under the SGO, the Reporter hereby submits this report. In order to avoid duplications and additional CBI requests, this submission includes the publicly available information of the Report and incorporates the Report by reference. This submission is based on the information provided to the Reporter by VW. The Reporter currently believes that it has no independent knowledge of the information in this report. From Volkswagen: The subject vehicle was stopped at the intersection of [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] and [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] with the ADS system engaged, waiting for the traffic light to turn green. The passenger car (Toyota Tacoma, equipped with front grille/brush guard) approached from behind, honked the horn, and struck the stationary subject vehicle. The driver of the subject vehicle proceed through the intersection and pulled over into an empty parking lot to safely assess the incident. The passenger car is noted as remaining at the light for an additional cycle of the traffic light before driving off and not pulling over with the vehicle it just struck. The subject vehicle's 3 occupants reported feeling the impact but report no injuries, airbag deployments, or tow-aways. The subject vehicle's damage was to the right rear bumper, including the right rear sensor and mounting bracket.
988-7317ADSPACCAR Incorporated2024-02 14:03Streetman, TX2023 Peterbilt 579ADSHeavy TruckNo Injuries ReportedHighway / Freeway
This incident occurred near Streetman, TX on [XXX] at approximately 3:03 PM CT on February [XXX], 2024. The Aurora vehicle was operating in autonomy at the time. Conditions were clear. As the Aurora vehicle was driving i…This incident occurred near Streetman, TX on [XXX] at approximately 3:03 PM CT on February [XXX], 2024. The Aurora vehicle was operating in autonomy at the time. Conditions were clear. As the Aurora vehicle was driving in its lane at 62 mph, a box truck veered into the lane of the Aurora vehicle. The box truck's mirror appeared to make contact with the back of the trailer that the Aurora Driver was pulling. At this time, we are not aware of any injuries, and camera footage appears to show that the box truck continued to drive. From the post-trip inspection, there was not any visible trailer damage. Before the collision, the Aurora Driver was driving straight in its lane and passing the box truck. Shortly thereafter, the box truck began to encroach into the lane of the Aurora Driver. The Aurora Driver detected the box truck's encroachment into the Aurora vehicle's lane and initiated a nudge away from the box truck to provide space. The Aurora Driver detected the collision and made the decision to initiate an incident response, but before it could execute that response, the Vehicle Operator took over control of the system and proceeded in manual. The Aurora vehicle then re-engaged in autonomy approximately two minutes later. The Vehicle Operator did not visually observe the collision, assumed the reaction of the Aurora Driver to be a software anomaly, and reported the vehicle nudge through the standard annotation protocol rather than through the incident response protocols. The incident was identified at approximately 1:03 PM CT on February 2, 2024, through a review of Aurora's data logs.
1420-7081ADSVolkswagen Group of America, Inc.2024-01 9:00Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Intersection
The subject vehicle was stopped at a traffic light at the corner of [XXX] and [XXX] (Austin,TX) while traveling westbound on [XXX] While ADS was engaged, the subject vehicle was stationary, the passenger car behind the …The subject vehicle was stopped at a traffic light at the corner of [XXX] and [XXX] (Austin,TX) while traveling westbound on [XXX] While ADS was engaged, the subject vehicle was stationary, the passenger car behind the subject vehicle proceeded forward from a stationary position and bumped into the rear bumper of the subject vehicle. The passenger vehicle reversed away from the subject vehicle. The operator of the subject vehicle then turned on the hazard lights, proceeded through the intersection once the light changed to green and turned right onto [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] in order to check for a safe spot to park. The passenger vehicle, after reversing away from the subject vehicle, did not follow the subject vehicle and instead proceeded to turn right onto [XXX]. Once the operator pulled over they then followed protocol to call in the incident, took photos to document, and waited for manager and service to arrive at the scene to verify the damage. There were no known injuries, airbag deployments, or tow-away of anyone involved. There was no significant damage to the subject vehicle and it was driven back to the depot to debrief and provide information to incident response team on the incident.
30291-7039ADSNuro2024-01 10:49Houston, TX2022 Toyota PriusADSPassenger CarNo Injuries Reported18Street
On January [XXX], 2024 a Nuro Prius operating in manual mode side-swiped a parked passenger vehicle. The Nuro human operator reported no injuries and the passenger vehicle did not have occupants. No other individuals wer…On January [XXX], 2024 a Nuro Prius operating in manual mode side-swiped a parked passenger vehicle. The Nuro human operator reported no injuries and the passenger vehicle did not have occupants. No other individuals were involved. The Nuro operator, with assistance from nearby neighbors, was able to contact the vehicle owner and exchange information. The damage to both vehicles was minor, and law enforcement was not contacted. Upon further review of the incident data the week of January 22, Nuro determined that the Prius was in autonomous mode approximately 25 seconds prior to the incident. There was no evidence that the autonomous operation had any impact on the incident.
33175-9307ADSMobileye Vision Technologies2024-01 09:00Austin, TX2023 Volkswagen ID.BuzzADSPassenger CarNo Injuries Reported0Intersection
On FEB-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7081- the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO"). …On FEB-2024, Volkswagen Group of America, Inc. ("VW") filed an Incident Report (NHTSA-provided Report ID-1420-7081- the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "SGO"). The subject vehicle referred to in the Report contains the Reporter's software and hardware. Since the Reporter is also a Reporting Entity under the SGO, the Reporter hereby submits this report. In order to avoid duplications and additional CBI requests, this submission includes the publicly available information of the Report and incorporates the Report by reference. This submission is based on the information provided to the Reporter by VW. The Reporter currently believes that it has no independent knowledge of the information in this report. From Volkswagen: The subject vehicle was stopped at a traffic light at the corner of [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] and [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] (Austin,TX) while traveling westbound on [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] While ADS was engaged, the subject vehicle was stationary, the passenger car behind the subject vehicle proceeded forward from a stationary position and bumped into the rear bumper of the subject vehicle. The passenger vehicle reversed away from the subject vehicle. The operator of the subject vehicle then turned on the hazard lights, proceeded through the intersection once the light changed to green and turned right onto [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] in order to check for a safe spot to park. The passenger vehicle, after reversing away from the subject vehicle, did not follow the subject vehicle and instead proceeded to turn right onto [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. Once the operator pulled over they then followed protocol to call in the incident, took photos to document, and waited for manager and service to arrive at the scene to verify the damage. There were no known injuries, airbag deployments, or tow-away of anyone involved. There was no significant damage to the subject vehicle and it was driven back to the depot to debrief and provide information to incident response team on the incident.
12381-6889ADSDaimler Trucks North America, LLC2023-12 14:35Vega, TX2023 Freightliner CascadiaADSAnimalNo Injuries Reported65Highway / FreewayRedacted by NHTSA as confidential business information
30330-6882ADSTORC Robotics, Inc.2023-12 14:35Vega, TX2023 Freightliner CascadiaADSAnimalNo Injuries Reported65Highway / FreewayRedacted by NHTSA as confidential business information
30270-6853ADSWaymo LLC2023-11 04:06Austin, TX2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and sto…On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and stopped at a red light on [XXX], preparing to make a right turn onto southbound [XXX]. A pickup truck approached from behind and 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. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30530-6818ADSAurora Operations, Inc.2023-11 09:56Ranger, TX2023 Peterbilt 579ADSPickup TruckNo Injuries Reported67Highway / Freeway
This incident occurred near Ranger, TX on [XXX] at approximately 9:56 am CT on Nov. [XXX], 2023. The Aurora vehicle was operating in autonomy at the time. Conditions were overcast, with light rain. As the Aurora vehicle …This incident occurred near Ranger, TX on [XXX] at approximately 9:56 am CT on Nov. [XXX], 2023. The Aurora vehicle was operating in autonomy at the time. Conditions were overcast, with light rain. As the Aurora vehicle was driving in its lane at 67 mph, a Ford pick-up truck overtaking the Aurora vehicle in the rightmost lane at approximately 80 mph appears to have hydroplaned, lost control, and hit the passenger-side rear portion of the trailer. Before the collision, the Aurora Driver detected the pick-up trucks encroachment into the Aurora vehicles lane and initiated a nudge to the left to provide space. This was insufficient to completely avoid the collision, and the pick-up truck made contact with the passenger side rear of the trailer. The Aurora Driver detected the collision and made the decision to initiate an incident response, but before it could execute that response, the Vehicle Operator took over control of the system and proceeded in manual. The Vehicle Operator received the notification that a collision had been detected and was initiating an incident response. The Vehicle Operator did not visually observe the collision and therefore assumed the reaction of the Aurora Driver to be a software anomaly worth escalated attention, rather than the correct detection of a collision and thus reported the incident through our escalated annotation protocol, rather than through our incident response protocols. We identified the incident at approximately 8:45 am CT on December [XXX], 2023, through a review of our data logs. At this time, we are not aware of any injuries and, from camera footage, the pick-up truck also appears to have left the scene of the incident. There is also no indication of any cargo or major trailer damage.
30531-6863ADSTransdev Alternative Services2023-11 04:06Austin, TX2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and s…On November [XXX], 2023 at 4:06 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and stopped at a red light on [XXX], preparing to make a right turn onto southbound [XXX]. A pickup truck approached from behind and 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. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting in the future. This report is a duplicate of report ID 30270-6853-1.
988-6859ADSPACCAR Incorporated2023-11 09:56Ranger, TX2023 Peterbilt 579ADSPickup TruckNo Injuries Reported67Highway / Freeway
Reference: Aurora Operations, Inc. NHTSA-Provided Report # 30530-6818-1 This incident occurred near Ranger, TX on [XXX] approximately 9:56 am CT on November [XXX], 2023. The Aurora vehicle was operating in autonomy at t…Reference: Aurora Operations, Inc. NHTSA-Provided Report # 30530-6818-1 This incident occurred near Ranger, TX on [XXX] approximately 9:56 am CT on November [XXX], 2023. The Aurora vehicle was operating in autonomy at the time. Conditions were overcast, with light rain. As the Aurora vehicle was driving in its lane at 67 mph, a Ford pick-up truck overtaking the Aurora vehicle in the rightmost lane at approximately 80 mph appears to have hydroplaned, lost control, and hit the passenger-side rear portion of the trailer. Before the collision, the Aurora Driver detected the pick-up truck's encroachment into the Aurora vehicle's lane and initiated a nudge to the left to provide space. This was insufficient to completely avoid the collision, and the pickup truck made contact with the passenger side rear of the trailer. The Aurora Driver detected the collision and made the decision to initiate an incident response, but before it could execute that response, the Vehicle Operator took over control of the system and proceeded in manual. The Vehicle Operator received the notification that a collision had been detected and was initiating an incident response. The Vehicle Operator did not visually observe the collision and therefore assumed the reaction of the Aurora Driver to be a software anomaly worth escalated attention, rather than the correct detection of a collision and thus reported the incident through our escalated annotation protocol, rather than through our incident response protocols. We identified the incident at approximately 8:45 am CT on December [XXX], 2023 through a review of our data logs. At this time, we are not aware of any injuries and, from camera footage, the pick-up truck also appears to have left the scene of the incident. There is also no indication of any cargo or major trailer damage.
30391-6563ADSKodiak Robotics2023-10 15:08Fort Worth, TX2019 Kenworth Motor Truck Co T680ADSHeavy TruckNo Injuries Reported34Highway / Freeway
On October [XXX], 2023 at 3:08 PM CT a tractor-trailer entered the lane of a Kodiak Autonomous Vehicle (Kodiak AV) Kenworth Class 8 semi-truck and made minor contact. The Kodiak AV was driving westbound on [XXX] in Fort …On October [XXX], 2023 at 3:08 PM CT a tractor-trailer entered the lane of a Kodiak Autonomous Vehicle (Kodiak AV) Kenworth Class 8 semi-truck and made minor contact. The Kodiak AV was driving westbound on [XXX] in Fort Worth, Texas near [XXX]. The Kodiak AV was operating with a safety driver (in the drivers seating position), who transitioned the vehicle from autonomous to manual mode approximately 5 seconds prior to impact, due to the other truck encroaching on the Kodiak AVs lane. At the time of impact, the Kodiak AV was in manual mode. No injuries occurred in the incident. The Kodiak AV pulled over after the incident, and the other driver continued down the road. The Kodiak AV's mirror-mounted SensorPod sustained minor scratches. Kodiak may supplement or correct its reporting with additional information as it may become available.
30412-6596ADSCruise LLC2023-10 05:01Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6597ADSCruise LLC2023-10 02:24Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported5StreetRedacted by NHTSA as confidential business information
30412-6614ADSCruise LLC2023-10 01:51Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
31101-7044 v2ADSAvride Inc.2023-10 12:50Austin, TX2020 Hyundai SonataADSPassenger CarNo Injuries Reported25Street
Our car was moving down the street with approximate speed 25mph when it was tailgated. Our driver was not injured, and the driver in the other car showed no visible injuries. However, she called an ambulance due to her p…Our car was moving down the street with approximate speed 25mph when it was tailgated. Our driver was not injured, and the driver in the other car showed no visible injuries. However, she called an ambulance due to her pregnancy. The airbags did not deploy in either vehicle. The police report says following: AFTER VIEWING VIDEO FROM UNIT 2 WEEKS LATER, IT WAS DISCOVERED THAT UNIT 1 WAS TRAVELING EAST ON [XXX] IN THE LEFT LANE. UNIT 2 WAS IN FRONT OF UNIT 1 TRAVELING EAST ON [XXX] IN THE LEFT LANE. UNIT 2 SLOWED TO TURN LEFT INTO A DRIVE WAY. UNIT 1 THEN STRUCK THE BACK RIGHT OF UNIT 2. THIS DIFFERED FROM STATEMENTS GIVEN ON SCENE. There is also code 44 in the police report, which stays for Followed Too Closely
540-6629ADSGeneral Motors, LLC2023-10 01:51Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On November 13, 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) manufactu…On November 13, 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-6614-1)
540-6642ADSGeneral Motors, LLC2023-10 05:01Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On November 13, 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) manufactu…On November 13, 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-6596-1). .
540-6644ADSGeneral Motors, LLC2023-10 02:24Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported5Street
On November 13, 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) manufactu…On November 13, 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-6597-1).
988-6565ADSPACCAR Incorporated2023-10 15:08Fort Worth, TX2019 KENWORTH T680ADSHeavy TruckNo Injuries Reported34Highway / Freeway
On October 30, 2023, PACCAR was informed by Kodiak, Inc of the incident that occurred October [XXX]. On October [XXX], 2023 at 3:08 PM CT, a tractor-trailer entered the lane of Kodiak Autonomous Vehicle ("Kodiak AV"), K…On October 30, 2023, PACCAR was informed by Kodiak, Inc of the incident that occurred October [XXX]. On October [XXX], 2023 at 3:08 PM CT, a tractor-trailer entered the lane of Kodiak Autonomous Vehicle ("Kodiak AV"), Kenworth Class 8 semi-truck and made minor contact. The Kodiak AV was driving westbound on [XXX] in Fort Worth, Texas, near [XXX]. The Kodiak AV was operating with a safety driver (in the driver's seating position), who transitioned the vehicle from autonomous to manual mode approximately 5 seconds prior to impact, due to the other truck encroaching on the Kodiak AV's lane. At the time of impact, the Kodiak AV was in manual mode. No injuries occurred in the incident. The Kodiak AV pulled over after the incident, and the other driver continued down the road. The Kodiak AV's mirror-mounted SensorPod sustained minor scratches. PACCAR may supplement or correct reporting with additional information as it may become available from Kodiak.
30412-6242ADSCruise LLC2023-09 21:42Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-6262ADSCruise LLC2023-09 02:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported2IntersectionRedacted by NHTSA as confidential business information
30412-6363ADSCruise LLC2023-09 03:49Austin, TX2023 Cruise AVADSSUVNo Injuries Reported3IntersectionRedacted by NHTSA as confidential business information
30412-6371ADSCruise LLC2023-09 20:14Houston, TX2023 Cruise AVADSSUVNo Injuries Reported16IntersectionRedacted by NHTSA as confidential business information
30412-6384ADSCruise LLC2023-09 09:20Houston, TX2023 Cruise AVADSSUVNo Injuries Reported8IntersectionRedacted by NHTSA as confidential business information
30412-6437ADSCruise LLC2023-09 23:02Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported6StreetRedacted by NHTSA as confidential business information
30412-6440ADSCruise LLC2023-09 04:59Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-6441ADSCruise LLC2023-09 10:54Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6444ADSCruise LLC2023-09 23:44Austin, TX2023 Cruise AVADSSUVNo Injuries Reported25IntersectionRedacted by NHTSA as confidential business information
30412-6445 v2ADSCruise LLC2023-09 22:36Austin, TX2023 Cruise AVADSSUVNo Injuries Reported24IntersectionRedacted by NHTSA as confidential business information
540-6244ADSGeneral Motors, LLC2023-09 21:42Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported1Street
On September 12, 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) manufact…On September 12, 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-6242-1).
540-6290ADSGeneral Motors, LLC2023-09 02:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported2Intersection
On September 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) manufact…On September 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-6262-1)
540-6369ADSGeneral Motors, LLC2023-09 03:49Austin, TX2023 Cruise AVADSSUVNo Injuries Reported3Intersection
On September 22, 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) manufact…On September 22, 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-6363-1)
540-6372ADSGeneral Motors, LLC2023-09 20:14Houston, TX2023 Cruise AVADSSUVNo Injuries Reported16Intersection
On September 28, 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) manufact…On September 28, 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-6371-1)
540-6393ADSGeneral Motors, LLC2023-09 09:20Houston, TX2023 Cruise AVADSSUVNo Injuries Reported8Intersection
On October 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) manufacture…On October 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-6384-1).
540-6452ADSGeneral Motors, LLC2023-09 23:02Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported6Street
On October 12, 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) manufactur…On October 12, 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-6437-1)
540-6455ADSGeneral Motors, LLC2023-09 04:59Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported1Street
On October 12, 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) manufactur…On October 12, 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-6440-1).
540-6461ADSGeneral Motors, LLC2023-09 10:54Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On October 12, 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) manufactur…On October 12, 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-6441-1).
540-6467ADSGeneral Motors, LLC2023-09 23:44Austin, TX2023 Cruise AVADSSUVNo Injuries Reported25Intersection
On October 12, 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) manufactur…On October 12, 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-6444-1).
540-6468 v2ADSGeneral Motors, LLC2023-09 22:36Austin, TX2023 Cruise AVADSSUVNo Injuries Reported24Intersection
On November 15, 2023, 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) m…On November 15, 2023, 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-6445-2)
30412-6179ADSCruise LLC2023-08 00:36Austin, TX2024 Cruise OriginADSOther Fixed ObjectNo Injuries Reported6StreetRedacted by NHTSA as confidential business information
30412-6191ADSCruise LLC2023-08 00:39Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported5StreetRedacted by NHTSA as confidential business information
30412-6273ADSCruise LLC2023-08 23:36Austin, TX2023 Cruise AVADSSUVNo Injuries Reported10StreetRedacted by NHTSA as confidential business information
30412-6274ADSCruise LLC2023-08 00:21Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30413-6257ADSMay Mobility2023-08 10:10Arlington, TX2021 Toyota SiennaUnknown, see NarrativePassenger CarNo Injuries Reported18Street
The vehicle operator took the vehicle out of autonomy while driving NB on [XXX]. In manual the operator clipped the May vehicle's right sensor with the trunk of a diagonally parked car. The operator did not report the in…The vehicle operator took the vehicle out of autonomy while driving NB on [XXX]. In manual the operator clipped the May vehicle's right sensor with the trunk of a diagonally parked car. The operator did not report the incident, however based on video footage they were aware of physical damage to the May vehicle. Local staff noticed a vehicle health error regarding that sensor and called the operator back to base, where they saw the damage. The operator was sent home immediately and terminated upon video review due to not following proper procedure.
540-6188ADSGeneral Motors, LLC2023-08 00:36Austin, TX2024 Cruise OriginADSOther Fixed ObjectNo Injuries Reported6Street
On August 29, 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 29, 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-6179-1)
540-6199ADSGeneral Motors, LLC2023-08 00:39Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported5Street
On September 1, 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) manufactu…On September 1, 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-6191-1)
540-6305ADSGeneral Motors, LLC2023-08 23:36Austin, TX2023 Cruise AVADSSUVNo Injuries Reported10Street
On September 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) manufact…On September 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-6273-1)
540-6310ADSGeneral Motors, LLC2023-08 00:21Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On September 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) manufact…On September 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-6274-1)
30412-5980ADSCruise LLC2023-07 19:50Austin, TX2023 Cruise AVADSSUVNo Injuries Reported20IntersectionRedacted by NHTSA as confidential business information
30412-5992ADSCruise LLC2023-07 05:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported22IntersectionRedacted by NHTSA as confidential business information
30412-6043ADSCruise LLC2023-07 02:29Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
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.
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-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-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).
30412-5836ADSCruise LLC2023-06 21:04Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
540-5951ADSGeneral Motors, LLC2023-06 21:04Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On July 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 July 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-5836-1)
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
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)
30412-5287 v2ADSCruise LLC2023-04 03:15Austin, TX2022 Cruise AVADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-5288 v2ADSCruise LLC2023-04 03:15Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported9StreetRedacted by NHTSA as confidential business information
540-5296 v2ADSGeneral Motors, LLC2023-04 03:15Austin, TX2022 Cruise AVADSPassenger CarNo Injuries Reported0Street
On April 24, 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 …On April 24, 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-5287-2)
540-5297 v2ADSGeneral Motors, LLC2023-04 03:15Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported9Street
On April 24, 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 …On April 24, 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-5288-2)
30530-5289ADSAurora Operations, Inc.2023-03 08:01Weatherford, TX2022 Peterbilt 579mADSPassenger CarNo Injuries Reported65Highway / Freeway
At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicl…At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicle encroaching on the lane. This vehicle continued to veer toward Aurora's truck at over 65 miles per hour, causing a collision. Aurora disengaged autonomy before impact and pulled to the shoulder along with the involved vehicle. Both vehicles were able to be driven from the scene, and there were no reported injuries.
988-5310ADSPACCAR Incorporated2023-03 8:01Weatherford, TX2022 Peterbilt 579Unknown, see NarrativePassenger CarNo Injuries Reported65Highway / Freeway
At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicl…At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicle encroaching on the lane. This vehicle continued to veer toward Aurora's truck at over 65 miles per hour, causing a collision. Aurora disengaged autonomy before impact and pulled to the shoulder along with the involved vehicle. Both vehicles were able to be driven from the scene, and there were no reported injuries.
30391-4811 v2ADSKodiak Robotics2023-02 10:15Waxahachie, TX2023 Kenworth Motor Truck Co T680ADSSUVNo Injuries Reported56Highway / FreewayRedacted by NHTSA as confidential business information
30391-5009ADSKodiak Robotics2023-02 10:15Waxahachie, TX2023 Kenworth Motor Truck Co T680ADSSUVNo Injuries Reported56Highway / FreewayRedacted by NHTSA as confidential business information
988-4816ADSPACCAR Incorporated2023-02 10:15Waxahachie, TX2023 Kenworth Motor Truck Co T680ADSSUVNo Injuries Reported56Highway / Freeway
A police report was issued after the 1-Day SGO incident report was submitted. It determined the driver of the crossover SUV to be at fault and noted that the crossover SUV's driver advised officers that he fell asleep wh…A police report was issued after the 1-Day SGO incident report was submitted. It determined the driver of the crossover SUV to be at fault and noted that the crossover SUV's driver advised officers that he fell asleep while driving and caused the accident. The content of this incident report is otherwise unchanged from the initial incident report submitted on February 7, 2023. On February 7, 2023, Kodiak Robotics, Inc. ("Kodiak") filed an Incident Report (the "Report") under the Standing General Order 2021-01 (the "Order"). PACCAR, Inc. (Paccar) manufactured the Kodiak-operated motor vehicle involved in the incident summarized in the Incident Report. Because Paccar is also a Reporting Entity under the Order, Paccar is submitting a duplicate of the redacted public copy of the Report. Paccar has selected "Unknown" in the "ADS version" field solely to avoid a second submission of nonpublic Kodiak CBI. Paccar is in possession of Kodiak's response to this field and incorporates Kodiak's response into this submission by reference. Paccar's submission is based on facts supplied to Paccar by Kodiak. Paccar 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.
30290-4127ADSArgo AI2022-10 13:14Austin, TX2020 Ford EscapeADSPassenger CarNo Injuries Reported11StreetRedacted by NHTSA as confidential business information

What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.