# Anatomy of a Robotaxi Crash: Lessons from the Cruise Pedestrian Dragging Mishap

arXiv: https://arxiv.org/abs/2402.06046 · HTML: https://mlsanity.com/paper/2402.06046/

## Key facts

- Cited by 5 papers in the map (data through 14 Oct 2026).
- Builds on 0 of its 30 references that are in the map.
- First posted on arXiv 8 Feb 2024.

## Built on by (most cited first, 5 of 5)

- [Navigating the Edge with the State-of-the-Art Insights into Corner Case Identification and Generation for Enhanced Autonomous Vehicle Safety](https://mlsanity.com/paper/2503.00077/) (2025)
- [Flight Testing an Optionally Piloted Aircraft: a Case Study on Trust Dynamics in Human-Autonomy Teaming](https://mlsanity.com/paper/2503.16227/) (2025)
- [CORTEX-AVD: A Framework for CORner Case Testing and EXploration in Autonomous Vehicle Development](https://mlsanity.com/paper/2504.03989/) (2025)
- [RENEW: Towards Learning World Models and Repairing Model Exploitation from Preferences](https://mlsanity.com/paper/2607.14180/) (2026)
- [Evaluating Fuzz Testing for Reinforcement Learning Agents](https://mlsanity.com/paper/2607.24577/) (2026)

## Abstract (arXiv)

An October 2023 crash between a GM Cruise robotaxi and a pedestrian in San Francisco resulted not only in a severe injury, but also dramatic upheaval at that company that will likely have lasting effects throughout the industry. Is-sues stem not just from the loss events themselves, but also from how Cruise mishandled dealing with their robotaxi dragging a pedestrian under the vehicle after the initial post-crash stop. External investigation reports provide raw material describing the incident and critique the company's response from a regulatory point of view, but exclude safety engineering recommendations from scope. We highlight specific facts and relationships among events by tying together different pieces of the external report material. We then explore safety lessons that might be learned related to: recognizing and responding to nearby mishaps, building an accurate world model of a post-collision scenario, the in-adequacy of a so-called "minimal risk condition" strategy in complex situations, poor organizational discipline in responding to a mishap, overly aggressive post-collision automation choices that made a bad situation worse, and a reluctance to admit to a mishap causing much worse organizational harm down-stream.