A robotaxi drags a pedestrian while pulling over
A driverless robotaxi struck a pedestrian, stopped, and then, having misclassified the collision as a side impact, began to pull over with her beneath it. Cruise’s written reports to regulators did not describe the dragging.
What happened
On 2 October 2023 in San Francisco, a car driven by a person struck a pedestrian and threw her into the path of a Cruise robotaxi, which braked hard but could not avoid hitting her. According to the engineering analysis Cruise commissioned, the robotaxi “incorrectly classified the collision with the pedestrian as a side-impact collision.” It then began a pullover maneuver instead of an emergency stop, dragging her about 20 feet.
Cruise’s first two reports to NHTSA did not describe what the vehicle did after it first stopped. The California DMV suspended Cruise’s driverless permits on 24 October 2023, finding that the company had misrepresented safety information. In November 2024 Cruise admitted, in a deferred prosecution agreement, to submitting a false record to NHTSA with the intent to influence its investigation.
What allowed the action to take effect
G13 Self-reported record
After the action, the only account of what the system did, or of what could be undone, came from the system itself or from the party that ran it, and that account was wrong or incomplete.
Each account of the crash came from Cruise. It gave NHTSA video of the crash the same day, but the one-day report “did not disclose that the Cruise vehicle had dragged the pedestrian,” and Cruise admitted to submitting a false record to NHTSA.
Kind of evidence: admission. Sources: U.S. Attorney’s Office, Northern District of California, 14 November 2024; National Highway Traffic Safety Administration, September 2024. References: Justice Department release; consent order ¶¶ 9–12.
Related guidance: P7 Tamper-evident receipts and P6 Signer independence. Contract clauses C-6 and C-7.
Considered and left out
- G6 No independent evidence
- The decision to pull over was based on the vehicle’s own misreading of the collision. As with entry 5 and entry 3, the perception error is treated as what triggered the action, because the sources do not show any independent evidence that the vehicle had and failed to consult.
- G10 No independent stop
- The vehicle had no driver, and the sources do not say whether a remote operator could have stopped the pullover in the seconds it took.
Entries with gaps in common
Sources
- Official recordCruise Admits To Submitting A False Report To Influence A Federal Investigation And Agrees To Pay $500,000
- Official recordConsent Order, In re Cruise, LLC, Standing General Order 2021-01 Reporting
- Company statementQ4 2023 Earnings Deck
- Company statementReport to the Boards of Directors of Cruise LLC, GM Cruise Holdings LLC, and General Motors Holdings LLC Regarding the October 2, 2023 Accident in San Francisco
- Official recordDMV Statement on Cruise LLC Suspension
Cite this entry
External Control Layer. (2026). Entry 13: A robotaxi drags a pedestrian while pulling over. In Control Gap Record (Version 0.3). G-14, Inc. https://externalcontrollayer.ai/record-13
@misc{ecl_cgr_13,
author = {{External Control Layer}},
title = {Entry 13: A robotaxi drags a pedestrian while pulling over},
howpublished = {Control Gap Record, version 0.3},
publisher = {G-14, Inc.},
year = {2026},
url = {https://externalcontrollayer.ai/record-13},
note = {Released 2 November 2026}
}Correct this entry
Email ecl@g14.ai with “ECL record 13” in the subject line.
Write the email with the subject ECL record 13