The SGO file, in a form you can search
NHTSA publishes the crash reports as three CSV files of 116 columns each, with several versions of the same report mixed in. This is the same data as one table: driverless systems (ADS) and Level 2 driver assistance side by side, 2021 to today including NHTSA's archive, one row per report at its latest version, every row traceable to its NHTSA report number. Free, CC BY 4.0, refreshed from NHTSA on every pipeline run.
- Reports
- 8612
- Fatal
- 87
- Of them Level 2
- 79
- Reporting entities
- 64
- Incidents
- 2019-08 to 2026-09
8612 reports, showing 6201 to 6300.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-7310 | ADS | Waymo LLC | 2024-02 1:03 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On February [XXX], 2024 at 1:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in traffic for…On February [XXX], 2024 at 1:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in traffic for a red light on [XXX] southbound when a passenger car 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 drivers seating position). Both vehicles sustained damage and the passenger car left the scene. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-7311 | ADS | Waymo LLC | 2024-02 18:41 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | On February [XXX], 2024 at 6:41 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was stopped at a traffic light on…On February [XXX], 2024 at 6:41 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was stopped at a traffic light on eastbound [XXX] at the intersection with [XXX] and waiting for lead traffic to proceed when a passenger car 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. The Waymo AV sustained damage and the passenger car left the scene. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-7312 | ADS | Waymo LLC | 2024-02 1:42 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 26 | Street | On February [XXX], 2024 at 1:42 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving debris on [XXX] towards [XXX]. The Waymo AV was traveling southbound on [XXX] in t…On February [XXX], 2024 at 1:42 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving debris on [XXX] towards [XXX]. The Waymo AV was traveling southbound on [XXX] in the center lane when the vehicle made contact with a white object that was less than 12" in height and located in the middle of the AVs lane. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-7313 | ADS | Waymo LLC | 2024-02 9:30 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On February [XXX], 2024 at 9:30 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck and trailer near [XXX]. The Waymo AV was traveling east on [XXX] whe…On February [XXX], 2024 at 9:30 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck and trailer near [XXX]. The Waymo AV was traveling east on [XXX] when it came to a stop for a heavy truck that was preparing to back into a driveway on the north side of [XXX]. While the Waymo remained stationary, the heavy truck continued to reverse and the right side of the heavy trucks trailer made contact with the front of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-7315 | ADS | Waymo LLC | 2024-02 13:23 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On February [XXX], 2024 at 1:23 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was departing a parking spa…On February [XXX], 2024 at 1:23 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was departing a parking space on the right side of [XXX] when a heavy truck came to a stop in the rightmost traffic lane in front of the Waymo AV. The Waymo AV came to a stop partially out of the parking space to yield to the stopped truck and await a gap in passing traffic in the center lane to merge and pass the stopped truck. While the Waymo was stopped, the truck reversed towards the parking space that the Waymo was still partially occupying and the rear left corner of the truck made contact with the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-7316 v2 | ADS | Waymo LLC | 2024-02 21:18 | Chandler, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Unknown | 0 | Intersection | This is an update to report 30270-7316-1, originally submitted on March 14, 2024. The original report indicated that law enforcement was not investigating. An Accident Information Exchange Form was completed by the [XXX]…This is an update to report 30270-7316-1, originally submitted on March 14, 2024. The original report indicated that law enforcement was not investigating. An Accident Information Exchange Form was completed by the [XXX]. This information is now reflected in the "Post-Crash Information" section. The remainder of the report remains unchanged. On February [XXX], 2024 at 9:18 PM MST a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped at a red light on eastbound [XXX] at [XXX] when a passenger car 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. Both vehicles sustained damage and the passenger in the Waymo AV reported an unspecified injury. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. |
| 30270-7318 v3 | ADS | Waymo LLC | 2024-02 16:58 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | The content of this report is unchanged from the initial report submitted on March 15, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] A previous version of this 10-Day update incorrectly listed the initia…The content of this report is unchanged from the initial report submitted on March 15, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] A previous version of this 10-Day update incorrectly listed the initial report's submission date as February 20, 2024. On February [XXX], 2024 at 4:58 MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was turning right from eastbound [XXX] onto southbound [XXX] during a green light with the passenger car traveling close behind. The Waymo AV yielded for a pedestrian about to enter the crosswalk facing a "walk" signal, and the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01. |
| 30270-9169 | ADS | Waymo LLC | 2024-02 16:36 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 12 | Street | On February [XXX], 2024 at 4:36 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a fence on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] in the rightmos…On February [XXX], 2024 at 4:36 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a fence on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] in the rightmost lane when it approached a fence that was down partially on the rightmost lane and sidewalk from an abutting construction site. The front of the Waymo AV came in contact with the fence. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The fence 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. |
| 30410-7276 v2 | ADS | Motional | 2024-02 14:30 | Las Vegas, NV | 2024 Hyundai Ioniq 5 | ADS | Other Fixed Object | No Injuries Reported | 15 | Street | Redacted by NHTSA as confidential business information |
| 30413-7307 | ADS | May Mobility | 2024-02 11:40 | Ann Arbor, MI | 2022 Toyota Sienna | ADS | SUV | No Injuries Reported | 29 | Street | The May vehicle was in autonomous mode on experimental test software (not deployed to the Commercial fleet), in light snow conditions. A vehicle behind the AV was traveling approximately the same speed as the May shuttl…The May vehicle was in autonomous mode on experimental test software (not deployed to the Commercial fleet), in light snow conditions. A vehicle behind the AV was traveling approximately the same speed as the May shuttle. The May AV began to slow for an object ahead. Due to weather conditions, the AV misclassified a speed limit sign as a pedestrian, which intersected with the predicted trajectory of the AV. This caused the May AV to apply additional braking to avoid the projected collision with the misclassified object. The following vehicle did not react promptly when the May AV started to slow down, resulting in the following vehicle braking too late to avoid collision and impacting the May AV from behind. The following vehicle then pulled around the May vehicle and drove away. Resimulation of this event with an upcoming software version shows that the May AV would not misidentify the non-exist object so would not have decelerated unnecessarily. This improved software is set to be deployed to the full commercial fleet soon. In addition, per May policy, the commercial fleet would not operate in weather conditions like those present in this incident. |
| 30530-7141 | ADS | Aurora Operations, Inc. | 2024-02 14:03 | Streetman, TX | 2023 Peterbilt 579 | ADS | Heavy Truck | No Injuries Reported | 62 | Highway / 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-7177 | ADS | Transdev Alternative Services | 2024-02 17:01 | Austin, TX | 2024 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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. |
| 30531-7239 | ADS | Transdev Alternative Services | 2024-02 20:08 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 9 | Highway / Freeway | On February [XXX], 2024 at 7:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] whe…On February [XXX], 2024 at 7:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] when it began to brake as it approached a stack of stopped vehicles ahead. The Waymo AV test driver transitioned to manual mode and continued to brake when a passenger car traveling behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage, and the test driver in the Waymo AV reported a minor injury. 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-7237-1. |
| 30610-7291 | ADS | Zoox, Inc. | 2024-02 16:29 | Spring Valley, NV | 2017 Toyota Highlander | ADS | Pickup Truck | Minor | 0 | Intersection | A Zoox vehicle in autonomy was stopped, yielding to cross traffic as it attempted to turn right from westbound [XXX] onto northbound [XXX]. As it began to creep forward, it came to a stop to yield to a vehicle turning le…A Zoox vehicle in autonomy was stopped, yielding to cross traffic as it attempted to turn right from westbound [XXX] onto northbound [XXX]. As it began to creep forward, it came to a stop to yield to a vehicle turning left onto northbound [XXX]. The safety operator disengaged and continued to brake, when the Zoox vehicle was struck by the vehicle behind. The police were not called. The Zoox vehicle sustained minor damage and the safety operator reported back pain a few hours after the collision. |
| 30610-7292 | ADS | Zoox, Inc. | 2024-02 13:52 | San Francisco, CA | 2019 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | A Zoox vehicle (Vehicle 1) in autonomy was traveling southwest on [XXX] and turning right onto [XXX] on a green traffic signal. While executing the turn, the Zoox vehicle braked to achieve a minimal risk condition due to…A Zoox vehicle (Vehicle 1) in autonomy was traveling southwest on [XXX] and turning right onto [XXX] on a green traffic signal. While executing the turn, the Zoox vehicle braked to achieve a minimal risk condition due to an unexpected system fault, the safety operator disengaged, and then was rear ended by a passenger car (Vehicle 2) that was also turning directly behind the Zoox vehicle. The rear bumper cover and rear radar unit on the Zoox vehicle sustained damage. The hood, front grille and front bumper cover on the passenger car appeared to have sustained damage. There were no reported injuries and police were not called. |
| 30610-7293 | ADS | Zoox, Inc. | 2024-02 11:00 | San Francisco, CA | 2019 Toyota Highlander | ADS | Bus | No Injuries Reported | 1 | Street | A Zoox vehicle (Vehicle 1) in autonomy, traveling northeast on [XXX], was stopped in lane for a red traffic light at [XXX]. A SamTrans bus (Vehicle 2), with a front-mounted triple-bike rack extending past the width of th…A Zoox vehicle (Vehicle 1) in autonomy, traveling northeast on [XXX], was stopped in lane for a red traffic light at [XXX]. A SamTrans bus (Vehicle 2), with a front-mounted triple-bike rack extending past the width of the bus on the driver's side, was traveling southeast on [XXX] and attempting a right turn onto [XXX]. The protruding edge of the bike rack was encroaching into the Zoox vehicle's travel lane as the bus was executing the right hand turn. As the light turned green the Zoox vehicle inched forward and attempted to steer away from the bus. Just as the safety operator disengaged from autonomy, the protruding edge of the bike rack made contact with the driver's side fender on the Zoox vehicle. There were no reported injuries and the police were not called. |
| 33175-7402 v2 | Level 2 | Mobileye Vision Technologies | 2024-02 21:50 | San Antonio, TX | Ford Mustang Mach-E SUV | ADAS | SUV | Fatality | Highway / Freeway | Reporter learned about the crash from the media- [XXX] During a project meeting with Ford, the latter advised that the Ford vehicle involved in the crash contains Mobileye EyeQ SoC. However the reporter was not provi…Reporter learned about the crash from the media- [XXX] During a project meeting with Ford, the latter advised that the Ford vehicle involved in the crash contains Mobileye EyeQ SoC. However the reporter was not provided any information indicating whether reporter's SW was involved in any level. Reporter does not know which SW applications are enabled and/or engaged in Ford vehicles, and particularly in the Ford vehicle involved in the accident mentioned in the article. Reporter does not possess any additional information nor does it have access to data from the Ford vehicle. April 8th, 2024 update: no additional information to report. | |
| 33175-9306 | ADS | Mobileye Vision Technologies | 2024-02 11:20 | Austin, TX | 2023 Volkswagen ID.Buzz | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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. |
| 502-7195 v3 | Level 2 | Ford Motor Company | 2024-02 | Orlando, FL | 2023 Ford F150 | ADAS | Other Fixed Object | Serious | 70 | Highway / Freeway | Update to SGO Report 502-7195: The driver of the subject vehicle reported that, while driving with ACC and LCA engaged, the left front tire of the subject vehicle separated from the axle. The driver further reported that…Update to SGO Report 502-7195: The driver of the subject vehicle reported that, while driving with ACC and LCA engaged, the left front tire of the subject vehicle separated from the axle. The driver further reported that this caused them to lose control of the vehicle and that it impacted a guardrail. There were no reported injuries. Based on Ford's inspection of the vehicle and accident scene, Ford believes that the tire/wheel separation occurred because of the collision with the guardrail. The subject vehicle was equipped with both ACC and LCA. Ford has confirmed that some form of cruise control (either standard or ACC) was engaged at the time of the incident but has not been able to confirm whether LCA was also engaged at that time. |
| 502-7268 v4 | Level 2 | Ford Motor Company | 2024-02 21:50 | San Antonio, TX | 2022 Ford Mach-E | ADAS | SUV | Fatality | 70 | Highway / Freeway | On March 8, 2024, an individual posted comments in a social media vehicle forum alleging an incident that occurred while he was driving a Ford Mach-E vehicle. The customer stated that he was traveling at 70 MPH and opera…On March 8, 2024, an individual posted comments in a social media vehicle forum alleging an incident that occurred while he was driving a Ford Mach-E vehicle. The customer stated that he was traveling at 70 MPH and operating the vehicle in hands-free BlueCruise mode. The driver stated that he did not see and the BlueCruise system did not identify an SUV stopped in "the middle of the freeway" and that he crashed into the SUV. On March 8, 2024, Ford obtained a police report regarding this incident which states that the accident occurred on February [XXX], 2024, at approximately 9:50 p.m. and that the driver of the other vehicle (stopped in the middle lane of three lanes with lights off) was pronounced deceased at a hospital that evening. Based on further investigation, the following reflects Ford's understanding of the responsive facts and circumstances regarding this incident. On Saturday, February [XXX], 2024, about 9:50 p.m. central standard time, a 2022 Ford Mustang Mach-E electric-powered sport utility vehicle occupied by a 44-year-old driver was traveling east on [XXX] ([XXX]) in San Antonio, Bexar County, Texas, when it collided with the rear of a stationary 1999 Honda CR-V occupied by a 56-year-old driver. The Mach-E was equipped with advanced driver assistance systems, including those providing partial automation capabilities that Ford refers to a s "BlueCruise" and data obtained from the vehicle post-crash indicates that the vehicle was being operated in BlueCruise mode prior to the crash. The Mach-E was approaching [XXX] and was in the center lane of the roadway when it encountered the Honda. This section of [XXX] consisted of six traffic lanes, three each in the west- and eastbound directions. The opposing lanes were divided by a concrete median barrier and the posted speed limit was 70 mph. Following the collision, the Honda overturned and came to rest in the left lane. The Mach-E continued to the east and came to rest in the right lane. The weather was clear, and some roadway lighting was present in this section of [XXX]. As a result of the crash, the driver of the Honda was fatally injured, and the Ford driver sustained minor injuries. A witness who had been traveling in the center lane of eastbound [XXX] in front of the Ford reported that she encountered the stopped Honda in the center lane and that the vehicle's tail or hazard lights were not illuminated. The witness changed lanes to the right to avoid striking the vehicle and later, in her rearview mirror, saw another vehicle strike the stopped Honda. |
| 502-7283 | Level 2 | Ford Motor Company | 2024-02 11:41 | Libertyville Twp, IL | 2021 Ford Escape | ADAS | Passenger Car | No Injuries Reported | 65 | Highway / Freeway | The driver of the Escape was traveling east on [XXX] while using ACC/LCA. A BMW in the adjacent lane abruptly cut into the driver's lane, resulting in a collision with the front-right of the Escape. The impact caused the…The driver of the Escape was traveling east on [XXX] while using ACC/LCA. A BMW in the adjacent lane abruptly cut into the driver's lane, resulting in a collision with the front-right of the Escape. The impact caused the Escape to veer off the roadway and collide with the center median barrier, leading to additional damage on the front and left side of the vehicle. The driver of the BMW fled the scene. No injuries were reported. The airbags on the Escape deployed, and the vehicle was towed from the scene. |
| 540-7189 | Level 2 | General Motors, LLC | 2024-02 19:04 | Springfield, VA | 2022 Chevrolet Bolt | ADAS | Other, see Narrative | No Injuries Reported | 44 | Highway / Freeway | At 7:04 PM (EST) on February [XXX], 2024, a Bolt EUV was travelling southwest on [XXX] in Springfield, Virginia, with Super Cruise engaged. According to OnStar audio recordings, the driver began making a lane change and…At 7:04 PM (EST) on February [XXX], 2024, a Bolt EUV was travelling southwest on [XXX] in Springfield, Virginia, with Super Cruise engaged. According to OnStar audio recordings, the driver began making a lane change and made contact with the vehicle adjacent to him. According to vehicle telematics, the driver side and frontal airbags and pretensioner deployed. Super Cruise was active 13 seconds prior to the crash. A subject vehicle speed of 44 mph was recorded at the time of impact. |
| 669-7320 | ADS | Hyundai Motor America | 2024-02 14:30 | Las Vegas, NV | 2024 Hyundai IONIQ 5 | ADS | Other Fixed Object | No Injuries Reported | 15 | Street | Redacted by NHTSA as confidential business information |
| 945-7224 v2 | Level 2 | Nissan North America, Inc. | 2024-02 11:30 | Georgetown, TX | 2023 Nissan Rogue | ADAS | Unknown | Minor | 10 | Highway / Freeway | The information contained in this report is based solely on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives. On [XXX], Claimant orally st…The information contained in this report is based solely on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives. On [XXX], Claimant orally stated that the vehicle's air bags did not deploy in a front-end collision. Claimant reported she normally uses the cruise control to engage the brake, but that did not happen this time and she had to manually press the brake. As a result, the vehicle hit another vehicle in front and the air bag did not deploy from the impact. Claimant reports the vehicle was towed. Nissan is attempting to coordinate the investigation with the customer. On [XXX], claimant stated the vehicle was traveling at 5 to 10 miles per hour when the incident occurred. Claimant stated their vehicle "bumped into" an F-150. After the incident, the front passenger sought medical attention for whiplash. Claimant declined the initial request for an inspection. On 2/29/2024, Claimants wife declined a 2nd offer of an inspection. On 3/6/2024, Nissan closed the investigation and sent a "no chance to inspect" letter. |
| 945-7231 v3 | Level 2 | Nissan North America, Inc. | 2024-02 12:53 | See Narative, NJ | 2023 Nissan Ariya | ADAS | Unknown | Unknown | Highway / Freeway | The information contained in this report is based solely on Nissan's notification via telematics that a vehicle equipped with Pro Pilot Assist 2.0 was involved in an incident involving an air bag deployment. The time sta…The information contained in this report is based solely on Nissan's notification via telematics that a vehicle equipped with Pro Pilot Assist 2.0 was involved in an incident involving an air bag deployment. The time stamp on the incident notification is 12:53 UTC. Initial information indicates the vehicle was operating in ProPilot Assist 1.0 mode (hands on mode). Nissan is currently examining its ability to provide additional details that may be protected by consumer privacy laws. While it completes this privacy review, Nissan has provided the general latitude/longitude information above because the text box will not accept a non-numeric answer. Nissan is gathering additional information and will supplement with the 10-day report. Nissan has not been contacted regarding this incident. 10-Day Update (3/8/2024): This incident does not meet the 1-day reporting criteria but was incorrectly filed as such. Subsequently, Nissan is filing a 10-day report to follow the reporting criteria of the 1-day requirement. To date, Nissan has not been contacted regarding this incident. Monthly Report (3/15/2024): Nissan has not been contacted regarding this incident. | |
| 988-7317 | ADS | PACCAR Incorporated | 2024-02 14:03 | Streetman, TX | 2023 Peterbilt 579 | ADS | Heavy Truck | No Injuries Reported | Highway / 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. | |
| 10561-6934 v2 | OTHER | APTIV | 2024-01 09:50 | Las Vegas, NV | 2023 Ford Mustang Mach-E | ADAS | Other, see Narrative | No Injuries Reported | 30 | Intersection | This is a follow up to the e-mail submitted on January 6, 2024, during the portal maintenance period, and to the supplemental disclosure submitted on January 8, 2024, through the portal. This report supplements and clari…This is a follow up to the e-mail submitted on January 6, 2024, during the portal maintenance period, and to the supplemental disclosure submitted on January 8, 2024, through the portal. This report supplements and clarifies the previous submissions. The incident occurred about 09:50 PST on Jan [XXX], 2024 near the intersection of [XXX] and [XXX], Las Vegas, NV. There were no injuries reported to Aptiv as a result of the crash involving the subject vehicle. The subject vehicle with Level 2 ADAS engaged was southbound on [XXX] approaching [XXX]. The subject vehicle was traveling about 30 MPH in the right lane. An e-scooter was southbound ahead of the subject vehicle in the right turn lane of [XXX] (in the roadway). The e-scooter then drove into the pedestrian cross-walk from the designated right turning lane, crossed [XXX] and attempted to enter the north/south sidewalk from the roadway. After entering the sidewalk, the rider of the e-scooter lost control and the rider and e-scooter re-entered the right lane of [XXX]. The rider fell into the road near the curb where he remained, but the e-scooter slid out from under the rider and continued to slide across the roadway until its front wheel reached the middle of the right lane. The subject vehicle was not involved with nor did it contribute to the rider of the e-scooter losing control or with either the e-scooter or rider re-entering the roadway. The subject vehicle driver was monitoring the e-scooter and had prepared to react when he noticed the e-scooter attempting to enter the sidewalk. The subject vehicle driver manually applied the brakes when the e-scooter lost control and entered the roadway from the sidewalk. The driver's application of the brakes automatically disengaged the Level 2 ADAS system. The subject vehicle driver also moved left in lane, but was limited by an adjacent vehicle. The subject vehicle made contact and damaged the front wheel of the e-scooter. The subject vehicle did not contact the e-scooter rider or any other vehicles at any point. |
| 13781-10097 | Level 2 | Tesla, Inc. | 2024-01 02:00 | University Place, WA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 38 | Street | Redacted by NHTSA as confidential business information |
| 13781-10098 | Level 2 | Tesla, Inc. | 2024-01 02:42 | Aurora, CO | 2020 Tesla Model X | ADAS | Passenger Car | Unknown | 39 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6939 | Level 2 | Tesla, Inc. | 2024-01 10:02 | Orlando, FL | 2022 Tesla Model X | ADAS | Passenger Car | Unknown | 49 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6940 | Level 2 | Tesla, Inc. | 2024-01 00:11 | Phoenix, AZ | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6978 | Level 2 | Tesla, Inc. | 2024-01 04:06 | Norman, OK | 2023 Tesla Model 3 | ADAS | Passenger Car | Unknown | 33 | Street | Redacted by NHTSA as confidential business information |
| 13781-7024 | Level 2 | Tesla, Inc. | 2024-01 23:20 | Summit, WA | 2021 Tesla Model S | ADAS | Passenger Car | Unknown | 30 | Street | Redacted by NHTSA as confidential business information |
| 13781-7028 | Level 2 | Tesla, Inc. | 2024-01 10:09 | Commack, NY | 2019 Tesla Model 3 | ADAS | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-7029 | Level 2 | Tesla, Inc. | 2024-01 04:28 | Plano, TX | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 39 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-7030 | Level 2 | Tesla, Inc. | 2024-01 14:14 | Dallas, TX | 2022 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 45 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7035 | Level 2 | Tesla, Inc. | 2024-01 05:51 | Vienna, VA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7040 | Level 2 | Tesla, Inc. | 2024-01 08:50 | Los Angeles, CA | 2022 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 59 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7041 | Level 2 | Tesla, Inc. | 2024-01 23:56 | Colts Neck, NJ | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 44 | Street | Redacted by NHTSA as confidential business information |
| 13781-7042 | Level 2 | Tesla, Inc. | 2024-01 21:56 | San Diego, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 54 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7043 | Level 2 | Tesla, Inc. | 2024-01 09:16 | Denver, CO | 2019 Tesla Model 3 | ADAS | Unknown | Unknown | 41 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-7049 | Level 2 | Tesla, Inc. | 2024-01 16:33 | Escondido, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 27 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7050 | Level 2 | Tesla, Inc. | 2024-01 15:24 | Sealy, TX | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-7051 | Level 2 | Tesla, Inc. | 2024-01 23:08 | San Antonio, TX | 2023 Tesla Model Y | ADAS | SUV | Unknown | 42 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-7059 | Level 2 | Tesla, Inc. | 2024-01 16:37 | Houston, TX | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7061 | Level 2 | Tesla, Inc. | 2024-01 22:05 | Steamboat Springs, CO | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 54 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-7062 | Level 2 | Tesla, Inc. | 2024-01 01:18 | Anaheim, CA | 2019 Tesla Model 3 | ADAS | SUV | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7063 | Level 2 | Tesla, Inc. | 2024-01 20:07 | Colchester, VT | 2019 Tesla Model 3 | ADAS | SUV | Unknown | 3 | Street | Redacted by NHTSA as confidential business information |
| 13781-7070 | Level 2 | Tesla, Inc. | 2024-01 21:42 | Caledonia, WI | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 48 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-7086 | Level 2 | Tesla, Inc. | 2024-01 | Irvine, CA | 2023 Tesla Model 3 | Unknown, see Narrative | Pickup Truck | Unknown | 37 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7181 | Level 2 | Tesla, Inc. | 2024-01 | Nipton, CA | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7184 | Level 2 | Tesla, Inc. | 2024-01 | Tukwila, WA | 2021 Tesla Model Y | ADAS | Passenger Car | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7186 | Level 2 | Tesla, Inc. | 2024-01 17:53 | Camarillo, CA | 2022 Tesla Model X | ADAS | Passenger Car | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7399 | Level 2 | Tesla, Inc. | 2024-01 09:56 | Dallas, TX | 2023 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 48 | Street | Redacted by NHTSA as confidential business information |
| 13781-7783 | Level 2 | Tesla, Inc. | 2024-01 00:03 | Franklin, TN | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 11 | Unpaved Road | Redacted by NHTSA as confidential business information |
| 13781-8730 | Level 2 | Tesla, Inc. | 2024-01 19:17 | Los Angeles, CA | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8731 | Level 2 | Tesla, Inc. | 2024-01 16:34 | Wells, ME | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 35 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-8733 | Level 2 | Tesla, Inc. | 2024-01 05:22 | Bradley, FL | 2022 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 53 | Rural Road | Redacted by NHTSA as confidential business information |
| 1420-7081 | ADS | Volkswagen Group of America, Inc. | 2024-01 9:00 | Austin, TX | 2023 Volkswagen ID.Buzz | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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. |
| 28509-7581 | Level 2 | Polestar Automotive USA, Inc. | 2024-01 02:00 | Long Beach, CA | 2022 Polestar 2 | ADAS | Other Fixed Object | Minor | 71 | Highway / Freeway | The driver of the Polestar 2 was on Northbound left lane of [XXX] near [XXX] traveling at about 71 mph. EDR data shows Pilot Assist was on. EDR data shows driver steering input to the left toward the barrier. Because of …The driver of the Polestar 2 was on Northbound left lane of [XXX] near [XXX] traveling at about 71 mph. EDR data shows Pilot Assist was on. EDR data shows driver steering input to the left toward the barrier. Because of the driver steering input Pilot Assist did not intervene as the driver is in control. The driver and vehicle strike the barrier and there is brake request after the impact. |
| 29990-7002 v2 | Level 2 | Rivian Automotive, LLC | 2024-01 10:35 | Escondido, CA | 2023 Rivian R1S | ADAS | Other Fixed Object | Minor | 77 | Highway / Freeway | Alleged information here directly from customer report, not yet confirmed by Rivian: "As I entered a curve in the road (curving right), the car jerked towards the right-hand k-rail and a red notice popped up that said th…Alleged information here directly from customer report, not yet confirmed by Rivian: "As I entered a curve in the road (curving right), the car jerked towards the right-hand k-rail and a red notice popped up that said that the highway assist feature was now off. I wasn't sure if the cruise control was still on so I returned my foot to the accelerator and tried to get back into the right lane (so as not to hit the k-rail). I think I probably over corrected a bit and veered slightly into the left-hand lane but then I felt the car try to fully jerk us into that left lane. At that point, I lost control of the car as the back started fishtailing." The driver also noted that "I am a petite person, with minimal upper body strength, so I had a really hard time trying to control the heft of the vehicle as it was trying to veer into different lanes". According to the customer report the driver was taken to the hospital and diagnosed with a strained left shoulder and the other 2 occupants, both adults, were not injured. Update: On January [XXX], 2024, at 10:33:20 a.m. PST, the subject vehicle was traveling south on [XXX] at 77 mph with Rivians Level 2 ADAS feature, Highway Assist (HWA), engaged. 25 seconds later, at 10:33:45 a.m. the vehicle notified the driver through a message on the driver display that their lane was merging ahead. 19 seconds later, at 10:34:04 a.m. PST, after no intervention from the driver, HWA disengaged because the subject vehicle moved out of its ODD as a result of insufficient highway markings. At that same time, 10:34:04 a.m., the driver received audio and visual alerts to take over control of the subject vehicle through in-vehicle messaging. At this time the system did not detect hands on the wheel. Less than one second later, at 10:34:05 a.m., the driver put their hands back on the wheel and retook control but input a significant steering angle while still at a high rate of speed (75.4 mph) that started a loss of control. This steering input was not a result of the HWA feature, but an overcorrection by the driver. Over the next nine seconds, from 10:34:05 to 10:34:14 a.m., the driver steered the vehicle to both the left and right trying to regain control, they also applied both the brake and accelerator pedals at various times, sometimes simultaneously, until the vehicle departed the roadway and impacted the side barrier at 10:34:14 a.m. PST, causing damage to the right side of the subject vehicle and deploying the side airbags. |
| 30270-6932 v2 | ADS | Waymo LLC | 2024-01 03:19 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | SUV | Unknown | 12 | Intersection | Waymo is submitting an updated version of this report to correct the narratives incorrectly listed year from 2023 to 2024. The initial report was submitted on January 7, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS …Waymo is submitting an updated version of this report to correct the narratives incorrectly listed year from 2023 to 2024. The initial report was submitted on January 7, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2024 at 2:19 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and approaching the intersection with [XXX] with a green traffic light. As the Waymo AV approached the intersection, it detected a SUV towing a trailer traveling westbound on [XXX] at a high rate of speed. The Waymo AV braked as the SUV approached and entered the intersection against a red traffic light. The Waymo AV made contact with the driver side of the SUV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage and the SUV left the scene. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-6981 v2 | ADS | Waymo LLC | 2024-01 10:52 | San Francisco, CA | 2021 Jaguar I-PACE | ADS | Motorcycle | No Injuries Reported | 0 | Intersection | This report includes the following updates to the initial report submitted on January 14, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]: corrected event year in the narrative from 2023 to 2024 LOCATION A…This report includes the following updates to the initial report submitted on January 14, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]: corrected event year in the narrative from 2023 to 2024 LOCATION ADDRESS / DESCRIPTION field updated to reflect the location listed in the narrative clarifications added to the narrative and correction to the Waymo AVs mileage. The remainder is unchanged from the initial report. On January [XXX], 2024 at 10:52AM PT a rider of a moped lost control of the moped they were operating and fell and slid in front of a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California on [XXX] at [XXX] neither the moped nor its driver made contact with the Waymo AV. The Waymo AV was stopped on northbound [XXX] at the intersection with [XXX] when it started to proceed forward while facing a red traffic light. As the Waymo AV entered the intersection, it detected a moped traveling on eastbound [XXX] and braked. As the Waymo AV braked to a stop, the rider of the moped braked then fell on the wet roadway before sliding to a stop in front of the stationary Waymo AV. There was no contact between the moped or its rider and the Waymo AV. The Waymo AVs Level 4 ADS was engaged in autonomous mode. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a passenger of the Waymo AV reported that the moped may have been damaged. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7034 | ADS | Waymo LLC | 2024-01 3:07 | Chandler, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On January [XXX], 2024 at 2:07 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped for a red light on southbound [XXX…On January [XXX], 2024 at 2:07 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped for a red light on southbound [XXX] when an SUV 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. |
| 30270-7048 | ADS | Waymo LLC | 2024-01 12:35 | Gilbert, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 2 | Parking Lot | On January [XXX], 2024 at 12:35 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Gilbert, Arizona was in an event involving parking lot spikes at a parking lot entrance on [XXX] near [XXX]. The Waymo AV had appro…On January [XXX], 2024 at 12:35 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Gilbert, Arizona was in an event involving parking lot spikes at a parking lot entrance on [XXX] near [XXX]. The Waymo AV had approached an apartment complex parking lot entrance on [XXX] near [XXX], and encountered a closed gate, preventing access to the parking lot. Next to the closed entrance gate lane was an open exit lane, with parking lot spikes preventing wrong-way access. As the Waymo AV attempted a multi-point turn to exit the parking lot driveway and proceed on [XXX], the front passenger side tire drove over the parking lot spikes and deflated. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7054 | ADS | Waymo LLC | 2024-01 17:50 | Phoenix, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 35 | Street | On January [XXX], 2024 at 4:50 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in an event involving a rock in the road on [XXX] past [XXX]. The Waymo AV was traveling northbound on [XXX] in…On January [XXX], 2024 at 4:50 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in an event involving a rock in the road on [XXX] past [XXX]. The Waymo AV was traveling northbound on [XXX] in the far right lane when its front passenger side tire made contact with a rock in the road and immediately deflated. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7058 | ADS | Waymo LLC | 2024-01 09:03 | Scottsdale, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 10 | Parking Lot | On January [XXX], 2024 at 8:03 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was in a collision involving an automatic gate in an apartment complex parking lot entrance on [XXX] near [XXX].…On January [XXX], 2024 at 8:03 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was in a collision involving an automatic gate in an apartment complex parking lot entrance on [XXX] near [XXX]. The Waymo AV attempted to enter the apartment complex parking lot entrance as an automatic gate was closing. As the Waymo AV passed the closing gate, the gate made contact with the rear passenger side corner of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7071 | ADS | Waymo LLC | 2024-01 17:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On January [XXX], 2024 at 5:15 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southboun…On January [XXX], 2024 at 5:15 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the leftmost thru lane, adjacent to a dedicated left turn lane on its left. As the Waymo AV approached the intersection with [XXX], it came to a stop behind its lead vehicle. The passenger vehicle behind the Waymo AV then attempted to change lanes into the dedicated left turn lane, and made contact with the rear driver side corner 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. |
| 30270-7156 | ADS | Waymo LLC | 2024-01 8:24 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | On January [XXX], 2024, at 7:24 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a truck on [XXX] and [XXX]. The Waymo AV was traveling westbound on [XXX] in the lef…On January [XXX], 2024, at 7:24 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a truck on [XXX] and [XXX]. The Waymo AV was traveling westbound on [XXX] in the left lane, and came to a stop behind a stopped construction truck. As the Waymo AV came to a stop, the truck began to reverse and then made contact with the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7157 v3 | ADS | Waymo LLC | 2024-01 12:04 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | SUV | Unknown | 0 | Street | Waymo is submitting a second update to the report for this event, which Waymo submitted to NHTSA originally on February 15, 2024 and updated on April 30, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. Wa…Waymo is submitting a second update to the report for this event, which Waymo submitted to NHTSA originally on February 15, 2024 and updated on April 30, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. Waymo is submitting this update because it has received a claim for injuries for three passengers in the SUV. The claim did not provide more specific information about the nature or severity of the injuries. This change is also reflected in the "Highest Injury Severity Alleged" field. Otherwise, the content of this report is unchanged from the previous report submitted. On January [XXX], 2023 at 12:05 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] when it came to a stop to yield to an oncoming vehicle in a narrow roadway with parked vehicles on both sides of the street. As the oncoming SUV passed the Waymo AV, the driver's side rear of the SUV made contact with the driver's side rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and the passengers were in the process of putting on their seatbelts just after entering the Waymo AV. The Waymo AV sustained damage and the SUV left the scene. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7158 | ADS | Waymo LLC | 2024-01 08:57 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On January [XXX], 2024 at 7:57 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light with multiple other…On January [XXX], 2024 at 7:57 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light with multiple other vehicles on southbound [XXX] at [XXX], when an SUV with a deflated front driver side tire approached the intersection, traveling westbound on [XXX]. The SUV attempted to make a right turn onto northbound [XXX] at a high rate of speed, and entered the oncoming lanes of traffic where the Waymo AV and other vehicles were stopped at southbound [XXX]. The SUV then made contact with another SUV and a passenger vehicle in the left adjacent lane to the Waymo AV, and pushed the other SUV into the side of the Waymo AV (which was still stationary, waiting at the red light). At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The three other vehicles sustained damage, but the Waymo AV did not. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7159 | ADS | Waymo LLC | 2024-01 7:41 | Tempe, AZ | 2021 Jaguar I-Pace | ADAS | SUV | No Injuries Reported | 0 | Intersection | On January [XXX], 2024 at 7:41 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving an SUV on [XXX] at the intersection with the on and off ramps for westbound [XXX]. The …On January [XXX], 2024 at 7:41 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving an SUV on [XXX] at the intersection with the on and off ramps for westbound [XXX]. The Waymo AV was stopped in traffic for a red light on southbound [XXX] when an SUV 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. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7160 | ADS | Waymo LLC | 2024-01 15:51 | Scottsdale, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | Unknown | 7 | Intersection | On January [XXX], 2024 at 2:51 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was alleged to have contributed to a collision involving an SUV and a passenger vehicle on [XXX] at [XXX]. The …On January [XXX], 2024 at 2:51 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, Arizona was alleged to have contributed to a collision involving an SUV and a passenger vehicle on [XXX] at [XXX]. The Waymo AV was facing northbound on [XXX] and yielding to cross traffic on [XXX] while preparing to make a left turn to enter the center turn lane onto westbound [XXX], before merging into westbound traffic. Simultaneously, a silver passenger vehicle was stopped in the center turn lane on westbound [XXX], signaling an intent to turn left onto southbound [XXX]. When there was clearance to proceed, the Waymo AV started to make its left turn onto westbound [XXX], at which point an SUV that was approaching in the leftmost thru lane on westbound [XXX] began to brake. As the SUV braked, a white passenger vehicle, which had been traveling behind the SUV at a high speed, braked and swerved, making contact with the SUV and possibly with the silver vehicle waiting to turn left in the center left turn lane. No contact was made with the Waymo AV. Waymo is reporting this because there was an allegation that the Waymo AV was involved in this collision, submitted through the Waymo website. At the time of the event, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7161 | ADS | Waymo LLC | 2024-01 20:11 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Bus | No Injuries Reported | 0 | Intersection | On January [XXX], 2024 at 8:12 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a bus on westbound [XXX] at [XXX]. The Waymo AV was stopped at a stop sign on…On January [XXX], 2024 at 8:12 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a bus on westbound [XXX] at [XXX]. The Waymo AV was stopped at a stop sign on westbound [XXX] at the intersection with [XXX] when a bus traveling on southbound [XXX] started to make a left turn onto eastbound [XXX], a narrow road. As the bus performed the left turn onto [XXX], the Waymo AV slowly moved forward and to the right, but the left side of the bus made contact with the rear driver side corner of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-7162 | ADS | Waymo LLC | 2024-01 00:41 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On January [XXX], 2024 at 12:41 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving two passenger vehicles in the intersection of [XXX] at [XXX] and [XXX]. The…On January [XXX], 2024 at 12:41 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving two passenger vehicles in the intersection of [XXX] at [XXX] and [XXX]. The Waymo AV was stopped on eastbound [XXX] at a red traffic light with vehicles behind it, preparing to make an unprotected left turn onto eastbound [XXX]. When the light turned green, the Waymo AV proceeded into the intersection on [XXX], then stopped to yield to approaching vehicles. A black passenger vehicle two vehicles behind the Waymo AV then overtook both the Waymo AV and the vehicle behind the Waymo AV, and made contact with the front passenger side corner of a white passenger vehicle turning left in the opposite direction (onto westbound [XXX]). The Waymo AV then moved slightly forward, then came to a stop as the white passenger vehicle then moved backward from the collision with the black passenger vehicle. The rear passenger side corner of the white passenger vehicle made contact with the front passenger side of the Waymo AV. The black passenger vehicle left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV did not sustain damage, but the other two passenger 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. |
| 30291-7039 | ADS | Nuro | 2024-01 10:49 | Houston, TX | 2022 Toyota Prius | ADS | Passenger Car | No Injuries Reported | 18 | Street | 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. |
| 30291-7106 | ADS | Nuro | 2024-01 14:30 | Mountain View, CA | 2022 Toyota Prius | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On Friday, January [XXX], 2024 a Nuro Prius operating autonomously with a safety driver present was stopped at a red light at the intersection of [XXX] and [XXX]. A Mazda approaching the intersection failed to completely…On Friday, January [XXX], 2024 a Nuro Prius operating autonomously with a safety driver present was stopped at a red light at the intersection of [XXX] and [XXX]. A Mazda approaching the intersection failed to completely stop and rear-ended the Nuro Prius. No injuries were reported and no VRUs were involved. Both vehicles sustained minor damage. Law enforcement was not involved. |
| 30291-7107 | ADS | Nuro | 2024-01 19:24 | Palo Alto, CA | 2022 Toyota Prius | ADS | Passenger Car | No Injuries Reported | 24 | Intersection | On Wednesday, January [XXX] at approximately 4:20pm, a Nuro Prius was operating in autonomous mode in Palo Alto. As the Nuro Prius proceeded straight through a three-way intersection with right-of-way, a Honda CR-V on th…On Wednesday, January [XXX] at approximately 4:20pm, a Nuro Prius was operating in autonomous mode in Palo Alto. As the Nuro Prius proceeded straight through a three-way intersection with right-of-way, a Honda CR-V on the perpendicular street failed to stop at the stop sign and ran into the driver-side rear corner of the Nuro vehicle. Both vehicles sustained de minimis damage. Law enforcement was not involved and there were no injuries reported or VRUs present. |
| 30450-6958 | ADS | Ghost Autonomy Inc. | 2024-01 16:48 | San Jose, CA | 2017 Toyota Camry | ADS | Passenger Car | No Injuries Reported | 11 | Highway / Freeway | A Ghost ADS-equipped car was driving engaged Northbound on [XXX]. As always, there were two safety drivers in the car. Traffic was moving in all four lanes at or near the speed limit. The Ghost vehicle was in the right-m…A Ghost ADS-equipped car was driving engaged Northbound on [XXX]. As always, there were two safety drivers in the car. Traffic was moving in all four lanes at or near the speed limit. The Ghost vehicle was in the right-middle lane. Another vehicle (the "lead" car) entered into the Ghost car's lane from the right. While there were numerous vehicles ahead of the Ghost car before that vehicle entered the lane, the lead vehicle blocked the view of the lane before it. Throughout the incident, traffic in the other three lanes continued at a steady pace. When the lead vehicle entered into the lane ahead of the Ghost car, the Ghost car applied the brakes to accommodate the intrusion and then continued to match the speed of the lead car. The lead car suddenly slammed the brakes. The Ghost car followed suit, reducing its speed from 19 mps (42.5 mph) to 4.7 mps (10.5 mph) within the next three seconds. The Ghost car was able to match the rapid speed reduction of the lead car and avoid contact. The driver following the Ghost car was not able to respond as quickly as the Ghost ADS. When the following driver began to apply the brakes, the car was about five meters behind and was traveling at 6.5 mps. At the point of impact, the Ghost vehicle was traveling at 4.78 mps (10.7 mph), matching the lead car. There were no injuries. The vehicles suffered only cosmetic damage, the drivers exchanged information, and the Ghost safety drivers returned to home base in conventional mode. |
| 30531-7176 | ADS | Transdev Alternative Services | 2024-01 3:07 | Chandler, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On January [XXX], 2024 at 2:07 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped for a red light on southbound [X…On January [XXX], 2024 at 2:07 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped for a red light on southbound [XXX] when an SUV 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 with additional information as it may become available. This is a duplicate of report ID: 30270-7034-1. |
| 30610-6950 | ADS | Zoox, Inc. | 2024-01 21:13 | San Francisco, CA | 2017 Toyota Highlander | ADS | SUV | No Injuries Reported | 0 | Intersection | A Zoox vehicle (Vehicle 1) in autonomy was stopped at a red traffic light on northbound [XXX] at the intersection with [XXX] in San Francisco. At that time, an SUV (Vehicle 2), heading southbound on [XXX], failed to sto…A Zoox vehicle (Vehicle 1) in autonomy was stopped at a red traffic light on northbound [XXX] at the intersection with [XXX] in San Francisco. At that time, an SUV (Vehicle 2), heading southbound on [XXX], failed to stop for the red traffic light and entered the intersection, causing a collision with a passenger car (Vehicle 3) that was traveling eastbound on [XXX]. The SUV spun after making contact with the passenger car and collided with the stopped Zoox vehicle, damaging the front bumper on the driver's side and driver's side fender, mirror, and sensors on the Zoox vehicle. The police and EMS personnel were called to the scene. The driver of the SUV left the scene without exchanging information. The passenger car appeared to sustain significant damage to the front end. There were no reported injuries. |
| 30610-7110 | ADS | Zoox, Inc. | 2024-01 14:12 | San Francisco, CA | 2017 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Street | A Zoox vehicle (Vehicle 1) in autonomy was traveling on southbound [XXX] near [XXX] in San Francisco. The Zoox vehicle slowed to a gradual stop with brake and hazard lights activated during a simulated pick up-drop off m…A Zoox vehicle (Vehicle 1) in autonomy was traveling on southbound [XXX] near [XXX] in San Francisco. The Zoox vehicle slowed to a gradual stop with brake and hazard lights activated during a simulated pick up-drop off maneuver when it was rear-ended by a minivan (Vehicle 2). The rear bumper of the Zoox vehicle sustained minor damage. There were no reported injuries, and police were not called. Zoox vehicle camera footage shows that the driver of the minivan may not have been looking ahead at the roadway prior to and at the time of contact. |
| 30610-7111 | ADS | Zoox, Inc. | 2024-01 14:19 | Paradise, NV | 2017 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | A Zoox vehicle (vehicle 1) in autonomy was stopped at a red traffic light on southbound [XXX] at [XXX] when it was rear-ended at low speed by a passenger car (vehicle 2). There was minor damage to the Zoox vehicle. There…A Zoox vehicle (vehicle 1) in autonomy was stopped at a red traffic light on southbound [XXX] at [XXX] when it was rear-ended at low speed by a passenger car (vehicle 2). There was minor damage to the Zoox vehicle. There were no reported injuries and police were not called. Zoox vehicle camera footage shows that the driver of the passenger car may not have been looking ahead at the roadway prior to and at the time of contact. |
| 30792-7147 | ADS | WeRide Corp | 2024-01 12:56 | San Jose, CA | 2023 Nissan LEAF | ADS | Passenger Car | No Injuries Reported | 2 | Street | At approximately 12:56pm, a WeRide vehicle (car 1) was slowing to a stop ( 3mph) on [XXX] at the intersection of [XXX] to turn left in an effort to yield to crossing pedestrians. At this time a Toyota Prius (car 2) trave…At approximately 12:56pm, a WeRide vehicle (car 1) was slowing to a stop ( 3mph) on [XXX] at the intersection of [XXX] to turn left in an effort to yield to crossing pedestrians. At this time a Toyota Prius (car 2) traveling (10mph) had slammed into car 1's rear - causing damage primarily to car 1. Both parties pulled over to a safe location to exchange information but the driver of car 2 could not provide a valid insurance or registration certificate. |
| 33175-9307 | ADS | Mobileye Vision Technologies | 2024-01 09:00 | Austin, TX | 2023 Volkswagen ID.Buzz | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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. |
| 540-6944 | Level 2 | General Motors, LLC | 2024-01 07:50 | St Clair Shores, MI | 2025 Cadillac CT5 | ADAS | SUV | No Injuries Reported | 50 | Highway / Freeway | At 7:50 AM (EST) on January [XXX], 2024, a Cadillac CT5 was travelling in the center lane on [XXX], [XXX] with Super Cruise engaged. The driver made a right hand lane change. The driver noticed the vehicle ahead was sl…At 7:50 AM (EST) on January [XXX], 2024, a Cadillac CT5 was travelling in the center lane on [XXX], [XXX] with Super Cruise engaged. The driver made a right hand lane change. The driver noticed the vehicle ahead was slowing rapidly and made a left hand lane change. The left rear door area of the subject vehicle struck a vehicle already travelling in that lane. Super Cruise was active 6.8 seconds prior to the crash. Super Cruise entered an "off" state at 1.4 seconds prior to the crash. A subject vehicle speed of 50 mph was recorded at the time of impact. |
| 62-7622 v2 | Level 2 | Honda (American Honda Motor Co.) | 2024-01 01:45 | Rosarito, UNK | 2020 Honda Accord | Unknown, see Narrative | Heavy Truck | Serious | 55 | Highway / Freeway | The customer was driving on a freeway in Mexico on a rainy day with Adaptive Cruise Control (ACC) and Lane Keep Assist System (LKAS) engaged, resulting in an accident. He confirmed the accident occurred on 1/[XXX]/24, be…The customer was driving on a freeway in Mexico on a rainy day with Adaptive Cruise Control (ACC) and Lane Keep Assist System (LKAS) engaged, resulting in an accident. He confirmed the accident occurred on 1/[XXX]/24, between 1:45 AM and 2 AM, on [XXX] in Rosarito, Mexico. The customer was driving with the ACC set between 50-55 MPH. He was about to change lanes with the right turn signal on when the LKAS pulled the vehicle to the left. He attempted to correct the steering to the right, but the vehicle hydroplaned, went into a rest stop area, and collided with a semi-truck. The accident resulted in injuries to the customer. It was raining when he was changing lanes on the highway, and the LKAS pulled the steering wheel back. When he pulled the wheel back, the vehicle hydroplaned, causing a collision with a parked semi-truck. All airbags deployed, and he was the only person in the vehicle. He suffered injuries to his head, neck, and hand. His insurance at the time was Statefarm, and he blames the lane assist feature for the incident. The report was updated to correct the time of the incident from 13:45 to 01:45. |
| 10039-6771 v3 | Level 2 | BMW of North America, LLC | 2023-12 | Paramus, NJ | 2021 BMW X5 xDrive45e | ADAS | Other Fixed Object | Minor | 72 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 10039-6833 v4 | Level 2 | BMW of North America, LLC | 2023-12 06:00 | Bel Air, MD | 2023 BMW iX xDrive50 | ADAS | Other Fixed Object | No Injuries Reported | 59 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 12381-6889 | ADS | Daimler Trucks North America, LLC | 2023-12 14:35 | Vega, TX | 2023 Freightliner Cascadia | ADS | Animal | No Injuries Reported | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1243-6797 v2 | Level 2 | Subaru of America, Inc. | 2023-12 17:52 | Hainesport, NJ | 2023 Subaru Ascent | ADAS | Other Fixed Object | Minor | 42 | Street | Redacted by NHTSA as confidential business information |
| 13781-11598 | Level 2 | Tesla, Inc. | 2023-12 15:54 | Victorville, CA | 2017 TESLA Model S | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-6778 | Level 2 | Tesla, Inc. | 2023-12 01:52 | San Jose, CA | 2023 Tesla Model Y | ADAS | Unknown | Unknown | 38 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6779 | Level 2 | Tesla, Inc. | 2023-12 11:20 | Eastvale, CA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 76 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6780 | Level 2 | Tesla, Inc. | 2023-12 20:05 | Danville, CA | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 30 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6781 | Level 2 | Tesla, Inc. | 2023-12 12:30 | Sonoma, CA | 2022 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 31 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-6782 | Level 2 | Tesla, Inc. | 2023-12 06:04 | Saint Petersburg, FL | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 50 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6796 | Level 2 | Tesla, Inc. | 2023-12 23:48 | Atlanta, GA | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 40 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-6798 | Level 2 | Tesla, Inc. | 2023-12 18:30 | Fremont, CA | 2022 Tesla Model Y | ADAS | Van | Unknown | 2 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-6799 | Level 2 | Tesla, Inc. | 2023-12 09:46 | Napa, CA | 2018 Tesla Model 3 | ADAS | Unknown | Unknown | 32 | Unknown | Redacted by NHTSA as confidential business information |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. The themed reading of the driverless narratives is on the reports page.