The MachineRecord
NHTSA Standing General Order 2021-01

The SGO file, in a form you can search

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

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

8612 reports, showing 8001 to 8100.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
30412-2887ADSCruise LLC2022-04 00:13San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-2888ADSCruise LLC2022-04 03:35San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported2StreetRedacted by NHTSA as confidential business information
30531-2617 v2OTHERTransdev Alternative Services2022-04 02:27San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativePassenger CarNo Injuries Reported20Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30531-2617-2]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30531-2617-2]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was in autonomous mode and proceeding southbound on [XXX] in the rightmost lane, with a passenger vehicle traveling parallel in the left adjacent lane. As the two vehicles approached [XXX], the passenger vehicle cut into the Waymo's lane and braked before turning right on [XXX]. As the passenger vehicle executed the right turn, the Waymo AV test driver transitioned to manual mode, applied the brakes, but made contact with the passenger side rear corner of the passenger vehicle. 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 other party immediately left the scene of the event. The Waymo AV sustained minor 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 report is a duplicate to WaymoLLC-202204[XXX]-0 (rev.202204[XXX]155518).
30531-2648 v2OTHERTransdev Alternative Services2022-04 19:55San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativePassenger CarNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger car on [XXX] at [XXX] . The Waymo AV came to a stop at a stop sign on [XXX] at [XXX] , and as it was about to proceed, a passenger vehicle behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor 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 report is a duplicate to WaymoLLC-202204[XXX]-0 (rev.202204[XXX]183825).
30531-2672 v2OTHERTransdev Alternative Services2022-04 18:29Phoenix, AZ2021 Jaguar I-PaceUnknown, see NarrativeMotorcycleNo Injuries Reported3Intersection
On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was preparing to make a right turn from…On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was preparing to make a right turn from southbound [XXX] onto westbound [XXX], when it slowed to yield to a pedestrian crossing [XXX]. As the Waymo AV yielded, a motorcycle directly behind the Waymo AV was rear-ended by a pick-up truck. The motorcycle was pushed forward 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). The Waymo AV and the motorcycle 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 and a motorcycle was damaged. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-202204[XXX]-0 (rev.202204[XXX]154618).
30531-2786 v2OTHERTransdev Alternative Services2022-04 14:53San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativePickup TruckMinor0Intersection
The content of this report is unchanged from the initial report submitted previously. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision…The content of this report is unchanged from the initial report submitted previously. On April [XXX], 2022 at 2:53 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling in autonomous mode in the slip lane on northbound [XXX] at [XXX]. As the Waymo AV slowed to yield to a pedestrian pushing a shopping cart in a crosswalk, the Waymo AV test driver transitioned to manual mode and stopped the Waymo AV. The Waymo AV test driver then proceeded forward but had to yield to approaching traffic in the merge between northbound [XXX] and northbound [XXX]. As the Waymo AV came to a stop, a pickup truck 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 minor 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 and the Waymo AV test driver was transported from the scene for medical treatment due to reported injuries. Transdev may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30531-2794 v2OTHERTransdev Alternative Services2022-04 02:31San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativeOther, see NarrativeNo Injuries Reported9Parking Lot
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30531-2794-1] On April [XXX], 2022 at 2:31 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Franc…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30531-2794-1] On April [XXX], 2022 at 2:31 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA made contact with a parking lot driveway on the 200 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage 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 report is a duplicate to WaymoLLC-202204[XXX] (rev.202204[XXX]).
30531-2822 v2ADSTransdev Alternative Services2022-04 16:36San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Street
The content of this report is unchanged from the initial report (Report ID 30531-2822-1) On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collisi…The content of this report is unchanged from the initial report (Report ID 30531-2822-1) On April [XXX], 2022 at 4:36 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was in autonomous mode and traveling on westbound [XXX], when it slowed for the vehicle directly in front of the Waymo AV, which stopped shortly after passing [XXX]. Shortly after the Waymo AV came to a stop, the SUV behind the Waymo AV was rear-ended by a pickup truck, and the SUV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor 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 report is identical to WaymoLLC-202204[XXX]-0 (rev.202204[XXX]190125)
30531-3015OTHERTransdev Alternative Services2022-04 06:37San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativePickup TruckNo Injuries Reported17Street
On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in ma…On April [XXX], 2022 at 6:37 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was proceeding straight in manual in the left lane of [XXX] (a one-way street). After passing through the [XXX] intersection, a parked pickup truck on the left side of [XXX] pulled out of the parked position and made contact with the front left fender of the passing 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-202204[XXX]-0 (rev.202205[XXX]214710).
30531-3016OTHERTransdev Alternative Services2022-04 23:30Phoenix, AZ2021 Jaguar I-PaceUnknown, see NarrativeAnimalNo Injuries Reported24Street
On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode o…On April [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving an animal on [XXX] just past [XXX]. The Waymo AV was operating in autonomous mode on northbound [XXX] and had just passed [XXX] when a cat entered the street from the adjacent right curb. The Waymo AV then made contact with the cat. The Waymo AV braked and the Waymo AV test driver took manual control and brought the Waymo AV to a stop. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV did not sustain any damage and the cat was found to be deceased; the cat did not have any identification tags or other signs of ownership. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-202204[XXX]-0 (rev.202205[XXX]220648).
30531-3018OTHERTransdev Alternative Services2022-04 08:14San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativePassenger CarNo Injuries Reported0Intersection
On April [XXX], 2022 at 8:14 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped at a red l…On April [XXX], 2022 at 8:14 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped at a red light facing northeast on [XXX] in autonomous mode. While the light was still red, a passenger vehicle that had been stopped behind the Waymo AV began to move forward 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). The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-202204[XXX]-0 (rev.202205[XXX]215001).
30610-2913ADSZoox, Inc.2022-04 05:55San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported8Intersection
A Zoox vehicle in autonomous mode was proceeding straight through the intersection of [XXX]. and [XXX]. when it was rear-ended by a passenger vehicle that was switching lanes and made contact with the Zoox vehicle's rear…A Zoox vehicle in autonomous mode was proceeding straight through the intersection of [XXX]. and [XXX]. when it was rear-ended by a passenger vehicle that was switching lanes and made contact with the Zoox vehicle's rear sensors. The other party left the scene. The police were not called, and there were no injuries.
30711-2862ADSPony.ai2022-04 9:00Miliptas, CA2020 Hyundai Kona EVADSPassenger CarNo Injuries Reported0Parking Lot
On April [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was parked in a parking lot when a passenger vehicle reversed into the Pony.ai vehicle. T…On April [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was parked in a parking lot when a passenger vehicle reversed into the Pony.ai vehicle. The Pony.ai vehicle sustained minor damage to the driver's side rear door. There were no injuries, the police were not called to the scene, and the Pony.ai vehicle was driven back to Pony.ai's Fremont facility.
540-2827 v2ADSGeneral Motors, LLC2022-04 23:21San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On May [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manuf…On May [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed a 10 day report to an 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-2823-2)
540-2907ADSGeneral Motors, LLC2022-04 00:43San Francisco, CA2020 Cruise AVADSSUVNo Injuries Reported5Intersection
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order").?General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an 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-2884-1)
540-2925ADSGeneral Motors, LLC2022-04 01:55San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an 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-2885-1)
540-2926ADSGeneral Motors, LLC2022-04 23:21San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported22Street
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an 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-2886-1)
540-2927ADSGeneral Motors, LLC2022-04 00:13San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported1Street
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an 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-2887-1)
540-2928ADSGeneral Motors, LLC2022-04 03:35San Francisco, CA2020 Cruise AVADSPassenger CarUnknown2Street
On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On May [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an 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-2888-1)
62-2783Level 2Honda (American Honda Motor Co.)2022-04Bethlehem, PA2020 Honda CivicUnknown, see NarrativeUnknownNo Injuries ReportedHighway / FreewayThe customer was exiting on an off-ramp when another driver merged into the customer's lane and causing a crash. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-2865Level 2Honda (American Honda Motor Co.)2022-04Weslaco, TX2021 Honda PilotUnknown, see NarrativeUnknownMinorIntersection
The customer was at an intersection when two drunk drivers hit a vehicle, causing it to spin, catch on fire and then hit the customer's vehicle. Then, the customer's vehicle caught on fire. The customer alleges that the …The customer was at an intersection when two drunk drivers hit a vehicle, causing it to spin, catch on fire and then hit the customer's vehicle. Then, the customer's vehicle caught on fire. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
13781-2445 v3Level 2Tesla, Inc.2022-03Fillmore, CA2021 Tesla Model YUnknown, see NarrativeUnknownUnknown49Rural RoadRedacted by NHTSA as confidential business information
13781-2461 v2Level 2Tesla, Inc.2022-03 15:57Mountain View, CA2019 Tesla Model 3ADASOther Fixed ObjectUnknown56Highway / FreewayRedacted by NHTSA as confidential business information
13781-2480 v2Level 2Tesla, Inc.2022-03 09:14Miami, FL2021 Tesla Model YADASPassenger CarUnknown57Highway / FreewayRedacted by NHTSA as confidential business information
13781-2499 v2Level 2Tesla, Inc.2022-03 10:32San Diego, CA2021 Tesla Model YADASOther Fixed ObjectUnknown12Highway / FreewayRedacted by NHTSA as confidential business information
13781-2543 v2Level 2Tesla, Inc.2022-03 2:46Marina Del Rey, CA2021 Tesla Model 3ADASOther Fixed ObjectMinor20StreetRedacted by NHTSA as confidential business information
13781-2567 v2Level 2Tesla, Inc.2022-03 13:07Newport News, VA2021 Tesla Model YADASOther Fixed ObjectUnknown24Highway / FreewayRedacted by NHTSA as confidential business information
13781-2573 v2Level 2Tesla, Inc.2022-03 19:08St Matthews, SC2021 Tesla Model YADASUnknownUnknown70Highway / FreewayRedacted by NHTSA as confidential business information
13781-2580 v3Level 2Tesla, Inc.2022-03 02:03Fremont, CA2021 Tesla Model 3ADASPassenger CarUnknown20Highway / FreewayRedacted by NHTSA as confidential business information
13781-2600 v2Level 2Tesla, Inc.2022-03 22:23Castro Valley, CA2021 Tesla Model YADASUnknownFatalityHighway / FreewayRedacted by NHTSA as confidential business information
13781-2601 v2Level 2Tesla, Inc.2022-03 16:55Pasadena, CA2021 Tesla Model YADASOther Fixed ObjectUnknown70Highway / FreewayRedacted by NHTSA as confidential business information
13781-2602 v2Level 2Tesla, Inc.2022-03 07:07Fontana, CA2021 Tesla Model YADASOther Fixed ObjectUnknown48Highway / FreewayRedacted by NHTSA as confidential business information
13781-2603 v2Level 2Tesla, Inc.2022-03 23:57Concord, NC2021 Tesla Model YADASPassenger CarUnknown56Highway / FreewayRedacted by NHTSA as confidential business information
13781-2624 v2Level 2Tesla, Inc.2022-03 20:05Houston, TX2019 Tesla Model 3ADASOther, see NarrativeUnknown28Highway / FreewayRedacted by NHTSA as confidential business information
13781-2625 v2Level 2Tesla, Inc.2022-03 13:02Los Angeles, CA2016 Tesla Model SADASUnknownUnknown9Highway / FreewayRedacted by NHTSA as confidential business information
13781-2626 v2Level 2Tesla, Inc.2022-03 15:39Seal Beach, CA2016 Tesla Model SADASUnknownUnknown12Highway / FreewayRedacted by NHTSA as confidential business information
13781-2627 v2Level 2Tesla, Inc.2022-03 20:00Lebec, CA2018 Tesla Model XADASUnknownUnknown19Highway / FreewayRedacted by NHTSA as confidential business information
13781-2628 v2Level 2Tesla, Inc.2022-03 16:56Santa Clarita, CA2021 Tesla Model YADASOther Fixed ObjectUnknown29Highway / FreewayRedacted by NHTSA as confidential business information
13781-2629 v2Level 2Tesla, Inc.2022-03 02:30Altamonte Springs, FL2022 Tesla Model YADASUnknownUnknown61Highway / FreewayRedacted by NHTSA as confidential business information
13781-2638 v2Level 2Tesla, Inc.2022-03 16:26Kansas City, MO2020 Tesla Model 3ADASUnknownUnknown39StreetRedacted by NHTSA as confidential business information
13781-2640 v2Level 2Tesla, Inc.2022-03 23:41Marshall, VA2021 Tesla Model YADASOther, see NarrativeUnknown35Highway / FreewayRedacted by NHTSA as confidential business information
13781-4752 v2Level 2Tesla, Inc.2022-03 13:18Potomac, MD2020 Tesla Model YADASNon-Motorist: PedestrianUnknown8StreetRedacted by NHTSA as confidential business information
1712-2474 v2ADSRobert Bosch, LLC2022-03 08:50Los Angeles, CAEQS 450 4maticADSUnknownMinorParking LotRedacted by NHTSA as confidential business information
30270-2465 v2ADSWaymo LLC2022-03 21:39Phoenix, AZ2021 Jaguar I-PaceADSVanNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2465-1]. On March [XXX], 2022 at 9:39 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix…The content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2465-1]. On March [XXX], 2022 at 9:39 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, AZ was in a collision involving a van on N. [XXX] at [XXX]. The Waymo AV was stopped at a red light on southbound N. [XXX] when a van behind the Waymo AV failed to stop and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The van and Waymo AV sustained moderate 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. This report was submitted from the Pacific time zone on the required date.
30270-2591 v2ADSWaymo LLC2022-03 14:57Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarUnknown0Intersection
Other than an update to the narrative to describe oncoming vehicle's separate collision and a correction to the 'Notice Received Date', the content of this report is unchanged from the initial report submitted on March […Other than an update to the narrative to describe oncoming vehicle's separate collision and a correction to the 'Notice Received Date', the content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2465-1]. On March [XXX], 2022 at 15:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. 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 was stationary at a 4-way stop sign intersection when an oncoming car was involved in a separate collision, departed from its lane, and struck the Waymo AV. Both vehicles sustained damage in the front of the vehicle. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and a vehicle's airbag(s) deployed. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2605 v2ADSWaymo LLC2022-03 01:16San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported9Intersection
The description of the event in this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2605-1]. On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') ope…The description of the event in this report is unchanged from the initial report submitted on March [XXX], 2022 [Report ID # 30270-2605-1]. On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was slowing for a stop sign while traveling westbound on [XXX] in autonomous mode. An SUV approached from behind and made contact with the rear of the Waymo AV. The other party immediately left the scene of the event. 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 moderate 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. This report was submitted from the Pacific time zone on the required date.
30270-2609 v2ADSWaymo LLC2022-03 11:07San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported4Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2609-1]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fr…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2609-1]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on the 1000 block of [XXX]. The Waymo AV was stopped at a red traffic light on southbound [XXX] when a pedestrian entered the crosswalk. When the traffic light turned green, the Waymo AV remained stopped for a crossing pedestrian who had just reached the pedestrian island in the middle of the crosswalk. After a brief pause, the ADV started to proceed, when the SUV behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor 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. This report was submitted from the Pacific time zone on the required date.
30270-2773ADSWaymo LLC2022-03 07:35San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported3Intersection
On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on …On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on [XXX] in manual mode in a narrow passageway. The Waymo AV approached a stop sign and the test driver steered to the right around a parked vehicle with oncoming traffic approaching. The right rear sensor housing of the Waymo AV made contact with a parked SUV on the right side of the road. 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 minor 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. This report was submitted from the Pacific time zone on the required date.
30270-2774ADSWaymo LLC2022-03 18:14Phoenix, AZ2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On March [XXX], 2022 at 6:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, AZ was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was in autonomous mode on southbound [XXX] and stop…On March [XXX], 2022 at 6:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, AZ was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was in autonomous mode on southbound [XXX] and stopped at a red light to make an unprotected left onto eastbound [XXX]. When the traffic light turned green, the Waymo AV slowly proceeded into the intersection and stopped to yield to oncoming traffic. The Waymo AV test driver transitioned to manual mode just before an SUV 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 minor 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. This report was submitted from the Pacific time zone on the required date.
30270-2775ADSWaymo LLC2022-03 12:22San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic…On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic, eastbound on [XXX] in autonomous mode. A parked car to the right of the Waymo AV began reversing into the street and made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor 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. This report was submitted from the Pacific time zone on the required date.
30290-2481 v2ADSArgo AI2022-03 12:39Coral Gables, FL2020 Ford EscapeADSSUVModerate0Traffic CircleRedacted by NHTSA as confidential business information
30290-2696ADSArgo AI2022-03 12:50Miami, FL2019 Ford FusionADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-2588 v2ADSCruise LLC2022-03 13:24San Francisco, CA2022 Cruise AVADSNon-Motorist: CyclistSerious4StreetRedacted by NHTSA as confidential business information
30412-2593 v2ADSCruise LLC2022-03 02:07San Francisco, CA2020 Cruise AVADSPickup TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-2654 v2ADSCruise LLC2022-03 12:26San Francisco, CA2020 Cruise AVADSPassenger CarModerate10Street
A Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound in the rightmost lane on [XXX] between [XXX] and [XXX]. Ahead of the Cruise AV, a delivery truck was double-park…A Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound in the rightmost lane on [XXX] between [XXX] and [XXX]. Ahead of the Cruise AV, a delivery truck was double-parked in the rightmost lane of westbound [XXX]. The Cruise AV began to maneuver around the double-parked vehicle by changing lanes. At the same time, a 2010 Honda Civic traveling behind the Cruise AV in the rightmost lane also began to maneuver and increase speed into the leftmost lane. Shortly thereafter, contact was made with the Cruise AV's side door, damaging the front driver side door and radar assembly. There were no reported injuries at the scene by either party and police were not called. The driver of the Honda Civic later claimed injuries related to the event. [Cruise processes ADS compute data regarding the incident.]
30531-2473 v2OTHERTransdev Alternative Services2022-03 21:39Phoenix, AZ2021 Jaguar I-PaceUnknown, see NarrativeVanNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Waymo Report ID # 30270-2465-1]. On March [XXX], 2022 at 9:39 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in P…The content of this report is unchanged from the initial report submitted on March [XXX], 2022 [Waymo Report ID # 30270-2465-1]. On March [XXX], 2022 at 9:39 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, AZ was in a collision involving a van on N. [XXX] at [XXX]. The Waymo AV was stopped at a red light on southbound N. [XXX] when a van behind the Waymo AV failed to stop and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The van and Waymo AV sustained moderate 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 report is a duplicate to WaymoLLC-202203[XXX]-70 (rev.202203[XXX]213142).
30531-2595 v2OTHERTransdev Alternative Services2022-03 14:57Phoenix, AZ2021 Jaguar I-PaceUnknown, see NarrativePassenger CarUnknown0Intersection
On March [XXX], 2022 at 15:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Airozna was in a collision involving a passenger car on [XXX] at [XXX]. At the time of the impact, the Waymo AV's Level …On March [XXX], 2022 at 15:14 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Airozna was in a collision involving a passenger car on [XXX] at [XXX]. 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 was stationary at a 4-way stop sign intersection when an oncoming car departed from its lane and struck the Waymo AV. Both vehicles sustained damage in the front of the vehicle. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and a vehicle's airbag(s) deployed. Transdev may supplement or correct its reporting with additional information as it may become available. This repot is a duplicate to WaymoLLC-202203[XXX]-0 (rev.202203[XXX]213142).
30531-2615 v2OTHERTransdev Alternative Services2022-03 01:16San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativeSUVNo Injuries Reported9Intersection
On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was slowing for a stop sign while tra…On March [XXX], 2022 at 1:16 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was slowing for a stop sign while traveling westbound on [XXX] in autonomous mode. An SUV approached from behind and made contact with the rear of the Waymo AV. The other party immediately left the scene of the event. 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 moderate 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. Waymo's initial internal report mistakenly indicated that this event occurred in manual mode but a routine review of collision data revealed that the ADS was engaged. Waymo immediately submitted this report the same day this was discovered. Transdev may supplement or correct its reporting with additional information as it may become available. This report in is a duplicate to WaymoLLC-202203[XXX]-0 (rev.202203[XXX]175529).
30531-2616 v2OTHERTransdev Alternative Services2022-03 11:07San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativeSUVNo Injuries Reported4Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30531-2616-2]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30531-2616-2]. On March [XXX], 2022 at 11:07 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on the 1000 block of [XXX]. The Waymo AV was stopped at a red traffic light on southbound [XXX] when a pedestrian entered the crosswalk. When the traffic light turned green, the Waymo AV remained stopped for a crossing pedestrian who had just reached the pedestrian island in the middle of the crosswalk. After a brief pause, the ADV started to proceed, when the SUV behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor 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 report is a duplicate to WaymoLLC-2022031[XXX]-0 (rev.202204[XXX]165049).
30531-2788OTHERTransdev Alternative Services2022-03 12:22San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativePassenger CarNo Injuries Reported0Intersection
On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic…On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic, eastbound on [XXX] in autonomous mode. A parked car to the right of the Waymo AV began reversing into the street and made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Transdev Alternative is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-202203[XXX]-0 (rev.202204[XXX]184129).
30531-2789OTHERTransdev Alternative Services2022-03 12:22San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativePassenger CarNo Injuries Reported0Intersection
On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic…On March [XXX], 2022 at 12:22 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped in traffic, eastbound on [XXX] in autonomous mode. A parked car to the right of the Waymo AV began reversing into the street and made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-202203[XXX]-0 (rev.202204[XXX]184129).
30531-2791OTHERTransdev Alternative Services2022-03 07:35San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativeSUVNo Injuries Reported3Intersection
On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on …On March [XXX], 2022 at 7:35 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX] and [XXX]. The Waymo AV was traveling northeast on [XXX] in manual mode in a narrow passageway. The Waymo AV approached a stop sign and the test driver steered to the right around a parked vehicle with oncoming traffic approaching. The right rear sensor housing of the Waymo AV made contact with a parked SUV on the right side of the road. 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-202203[XXX]-0 (rev.202204[XXX]170647).
30610-2584 v2ADSZoox, Inc.2022-03 15:00San Francisco, CA2016 Toyota HighlanderADSNon-Motorist: OtherMinor2Intersection
A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right a…A Zoox vehicle in manual mode was proceeding with the right of way through a four-way stop, when a person operating an electric scooter failed to stop at the stop sign and proceeded into the intersection from the right and made contact with the rear corner of the Zoox vehicle at low speed. Police were not called. The Zoox vehicle was in autonomy in the 30 second period prior to contact.
30610-2651ADSZoox, Inc.2022-03 08:20San Francisco, CA2016 Toyota HighlanderADSPassenger CarMinor1IntersectionA Zoox vehicle in autonomous mode was stopped in traffic when a passenger vehicle from behind made contact with the rear of the Zoox vehicle at low speed. The police were not called.
30711-2666ADSPony.ai2022-03 11:30Tustin, CA2019 Hyundai Kona EVADSOther, see NarrativeNo Injuries Reported23Street
On March [XXX], 2022, while in supervised ("Drivered") autonomous mode traveling eastbound in the right lane of [XXX] in Tustin, CA, a Pony.ai Autonomous Vehicle drove over a temporary sign that had previously fallen ove…On March [XXX], 2022, while in supervised ("Drivered") autonomous mode traveling eastbound in the right lane of [XXX] in Tustin, CA, a Pony.ai Autonomous Vehicle drove over a temporary sign that had previously fallen over and was lying flat on its side in the travel lane. The impact redirected the vehicle towards the curb. The Safety Operator took control, disengaging autonomous mode, braked, and steered the vehicle away from the direction of the curb. The right front tire scraped the right curb. The vehicle sustained minor damage to the right front strut and control arm. There were no injuries and no other vehicles involved. The Safety Operator drove the vehicle back to Pony.ai's Irvine facility. Explanation for "Roadway Description": There was a sign lying flat on its side in the travel lane. Explanation for "Crash With" Description: The subject vehicle's tire made contact with the right curb.
502-2479 v2ADSFord Motor Company2022-03 12:39Coral Gables, FL2020 Ford EscapeADSSUVModerate0Traffic CircleRedacted by NHTSA as confidential business information
502-2751ADSFord Motor Company2022-03 12:50Miami, FL2019 Ford FusionADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
540-2590 v2ADSGeneral Motors, LLC2022-03 13:24San Francisco, CA2022 Cruise AVADSNon-Motorist: CyclistSerious4Street
On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruis…On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an 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-2588-2).
540-2594 v2ADSGeneral Motors, LLC2022-03 02:07San Francisco, CA2020 Cruise AVADSPickup TruckNo Injuries Reported0Street
On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") manufactured the Cruis…On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an 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-2593-2).
540-2706 v2ADSGeneral Motors, LLC2022-03 12:26San Francisco, CA2020 Cruise AVADSPassenger CarModerate10Street
On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an updated report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC ("GM") m…On April [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an updated report to an 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-2654-2).
62-2483Level 2Honda (American Honda Motor Co.)2022-03Waco, TX2021 Acura ILXUnknown, see NarrativePickup TruckModerate80Unknown
The customer was driving with the cruise control engaged at 80 miles per hour. The customer alleges that the automatic braking failed, causing the customer to rear-end a truck, resulting in injuries. The customer alleges…The customer was driving with the cruise control engaged at 80 miles per hour. The customer alleges that the automatic braking failed, causing the customer to rear-end a truck, resulting in injuries. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-2575Level 2Honda (American Honda Motor Co.)2022-03Irving, TX2021 Honda AccordUnknown, see NarrativeUnknownNo Injuries ReportedIntersectionThe customer was driving through an intersection when another vehicle crashed into him. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-2634Level 2Honda (American Honda Motor Co.)2022-03Escondido, CA2020 Honda CivicUnknown, see NarrativeUnknownMinorIntersection
The customer was stopped at an intersection and began driving through the intersection on a green light. When entering the intersection, another driver T-boned the customer on the driver-side of the vehicle. The customer…The customer was stopped at an intersection and began driving through the intersection on a green light. When entering the intersection, another driver T-boned the customer on the driver-side of the vehicle. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-2691Level 2Honda (American Honda Motor Co.)2022-03Baltimore, MD2017 Honda AccordUnknown, see NarrativeUnknownModerateUnknown
Customer called to praise Honda Sensing system. Customer stated they were the victim of a hit-and-run incident and stated Collision Mitigation Braking System was monumental in saving their life. Customer is requesting …Customer called to praise Honda Sensing system. Customer stated they were the victim of a hit-and-run incident and stated Collision Mitigation Braking System was monumental in saving their life. Customer is requesting assistance in locating a replacement Honda vehicle. Customer alleges that Lane Keeping Assist System and Adaptive Cruise Control were engaged at the time of the incident.
62-2802Level 2Honda (American Honda Motor Co.)2022-03PA2020 Honda CRVUnknown, see NarrativeUnknownNo Injuries ReportedStreet
Customer was driving down a road and crashed into a stopped vehicle in the middle of the road. Customer was unable to avoid the vehicle due to the snowstorm conditions. Customer alleges that the Lane Keep Assist System a…Customer was driving down a road and crashed into a stopped vehicle in the middle of the road. Customer was unable to avoid the vehicle due to the snowstorm conditions. Customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-3350Level 2Honda (American Honda Motor Co.)2022-03The Colony, TX2020 Honda CRV HybridUnknown, see NarrativeUnknownNo Injuries ReportedUnknownThe customer was hit from behind, causing her to hit the vehicle in front of her. The customer alleges that the Lane Keep Assist System and the Adaptive Cruise Control were engaged.
62-3382Level 2Honda (American Honda Motor Co.)2022-03Pacific Palisades, CA2016 Honda CivicUnknown, see NarrativeOther Fixed ObjectNo Injuries ReportedStreetThe customer was driving when another passenger drove too close, causing the customer to swerve and crash into a curb. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
62-3542Level 2Honda (American Honda Motor Co.)2022-03Nashville, TN2019 Honda CRVUnknown, see NarrativeNon-Motorist: PedestrianNo Injuries ReportedHighway / Freeway
The customer reported that while driving on a highway, a lady from a mental facility escaped her caregiver and ran into the customer's vehicle. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Co…The customer reported that while driving on a highway, a lady from a mental facility escaped her caregiver and ran into the customer's vehicle. The customer alleges that the Lane Keep Assist System and Adaptive Cruise Control were engaged.
753-3117 v3Level 2Kia America, Inc.2022-03 18:00Forked River, NJ2022 Kia TellurideADASOther Fixed ObjectMinor65Highway / Freeway
Customer contacted Kia's Consumer Affairs (CA) Department on June [XXX], 2022 indicating that her husband was involved in an accident and the airbags in their 2022 Kia Telluride did not deploy. Customer reported her hus…Customer contacted Kia's Consumer Affairs (CA) Department on June [XXX], 2022 indicating that her husband was involved in an accident and the airbags in their 2022 Kia Telluride did not deploy. Customer reported her husband was driving the subject Telluride at 65mph through a toll southbound on [XXX] when a second vehicle behind the Telluride went through the toll and attempted to squeeze in between the Telluride and a third vehicle on the highway. Customer's husband moved the Telluride to the right to evade the second vehicle and made contact with the right shoulder guardrail. No other vehicles were involved in the incident. The vehicle was towed. When asked by CA, the customer reported that HDA and cruise control were engaged at the time of the incident but customer did not allege that either of those systems caused the accident. The subject Kia Telluride is equipped with the ADAS Level 2 feature Highway Driving Assist (HDA). HDA is a supplemental system that helps maintain a set distance and speed from the vehicle ahead when driving on a highway and helps keep the vehicle between lanes while driving. HDA may not be able to recognize all traffic situations and may not detect possible collisions due to limitations of the system. Obstacles such as vehicles, motorcycles, bicycles, pedestrians, unspecified objects and structures that may collide with the vehicle may not be detected. Based on the description of provided by the customer, the accident was not caused by a failure and/or disengagement of HDA. Kia has no further information at this time. ***6/[XXX]/22 10-Day Update Incident Report*** On 6/[XXX]/22, Kia spoke with customer's husband regarding the incident. Customer's husband reiterated that his concern was that he believed the airbags should have deployed when he side-swiped the guardrails after he was "cut-off" by another vehicle. ***7/[XXX]/22 Monthly Update Incident Report*** Since Kia's updates on the 10-Day Update Incident Report, Kia has not received any material new, or materially different information related to this incident.
855-2464 v2ADSMercedes-Benz USA, LLC2022-03 08:50Los Angeles, CAMercedes-Benz EQS 450 4MaticADSOther, see NarrativeMinor1Parking LotNo additional information to report at this time.
1042-2343 v3Level 2Porsche Cars North America, Inc.2022-02UNK2021 Porsche Taycan 4 Cross TurismoADASUnknownNo Injuries Reported40Unknown
UPDATE 3/[XXX]/2022: This report was submitted in error, the Level 0 ADAS which was active at the time of the crash does not meet the SGO reporting criteria threshold. Subject vehicle was traveling at 40mph and another v…UPDATE 3/[XXX]/2022: This report was submitted in error, the Level 0 ADAS which was active at the time of the crash does not meet the SGO reporting criteria threshold. Subject vehicle was traveling at 40mph and another vehicle stopped in front of the subject vehicle in the path of the subject vehicle. Customer states that the subject vehicle did not stop as it should have. Customer Complaint statement: "Customer states that he was traveling at 40mph and a truck stopped in front of him. The car did not react or brake and he had to swerve to the right to miss the truck and hit another object. Customer states that car did not stop the collision as it should have."
13781-2229 v2Level 2Tesla, Inc.2022-02 07:48Simi Valley, CA2020 Tesla Model 3ADASPassenger CarUnknown70Highway / FreewayRedacted by NHTSA as confidential business information
13781-2230 v2Level 2Tesla, Inc.2022-02 06:14New Bern, NC2019 Tesla Model 3ADASPole / TreeUnknown26Rural RoadRedacted by NHTSA as confidential business information
13781-2239 v2Level 2Tesla, Inc.2022-02 17:35Murfreesboro, TN2019 Tesla Model 3ADASUnknownUnknown36Highway / FreewayRedacted by NHTSA as confidential business information
13781-2251 v2Level 2Tesla, Inc.2022-02 15:42Mountain View, CA2018 Tesla Model 3ADASPassenger CarUnknown12Highway / FreewayRedacted by NHTSA as confidential business information
13781-2252 v2Level 2Tesla, Inc.2022-02 16:17Saratoga, CA2022 Tesla Model 3ADASOther Fixed ObjectUnknown23Rural RoadRedacted by NHTSA as confidential business information
13781-2276 v2Level 2Tesla, Inc.2022-02 23:39Calhoun, GA2019 Tesla Model XADASSUVUnknown46IntersectionRedacted by NHTSA as confidential business information
13781-2277 v2Level 2Tesla, Inc.2022-02 07:05Belton, MO2020 Tesla Model YADASOther Fixed ObjectUnknown18StreetRedacted by NHTSA as confidential business information
13781-2278 v2Level 2Tesla, Inc.2022-02 23:16Tinton Falls, NJ2020 Tesla Model YADASPassenger CarUnknown11Highway / FreewayRedacted by NHTSA as confidential business information
13781-2324 v2Level 2Tesla, Inc.2022-02 3:02Emporia, VA2022 Tesla Model YUnknown, see NarrativeUnknownUnknown67Highway / FreewayRedacted by NHTSA as confidential business information
13781-2332 v2Level 2Tesla, Inc.2022-02 16:23Hayward, CA2018 Tesla Model 3ADASPassenger CarUnknown29Highway / FreewayRedacted by NHTSA as confidential business information
13781-2333 v2Level 2Tesla, Inc.2022-02 02:37Los Angeles, CA2021 Tesla Model 3ADASPassenger CarUnknown19Highway / FreewayRedacted by NHTSA as confidential business information
13781-2334 v2Level 2Tesla, Inc.2022-02 19:55Clifton, NJ2015 Tesla Model SADASUnknownUnknown36Highway / FreewayRedacted by NHTSA as confidential business information
13781-2341 v2Level 2Tesla, Inc.2022-02 14:08Great Falls, VA2019 Tesla Model 3ADASOther, see NarrativeUnknown35Rural RoadRedacted by NHTSA as confidential business information
13781-2355 v2Level 2Tesla, Inc.2022-02 08:39Rochester, NY2021 Tesla Model YADASOther Fixed ObjectUnknown51Highway / FreewayRedacted by NHTSA as confidential business information
13781-2369 v2Level 2Tesla, Inc.2022-02 05:37La Mesa, CA2017 Tesla Model SADASOther Fixed ObjectUnknown7Highway / FreewayRedacted by NHTSA as confidential business information
13781-2370 v3Level 2Tesla, Inc.2022-02 04:58San Diego, CA2019 Tesla Model 3ADASOther Fixed ObjectUnknown31Highway / FreewayRedacted by NHTSA as confidential business information
13781-2371 v2Level 2Tesla, Inc.2022-02 06:41Corona, CA2019 Tesla Model 3ADASOther Fixed ObjectUnknown29Highway / FreewayRedacted by NHTSA as confidential business information
13781-2372 v2Level 2Tesla, Inc.2022-02 20:27Tampa, FL2021 Tesla Model 3ADASSUVUnknown33IntersectionRedacted by NHTSA as confidential business information
13781-2373 v2Level 2Tesla, Inc.2022-02 15:52Fairview Park, OH2021 Tesla Model 3ADASUnknownUnknown57Highway / FreewayRedacted 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.