What happened?
On October 2, 2023, a human-driven vehicle hit a pedestrian in San Francisco, propelling her into the path of a nearby driverless Cruise vehicle. The Cruise vehicle also struck the pedestrian and initially stopped, but then attempted to pull over, dragging her approximately 20 feet beneath the vehicle before coming to a final stop.
Cruise briefed regulators the following day. However, its briefings did not adequately communicate the vehicle’s secondary movement and the dragging. On October 24, California’s Department of Motor Vehicles suspended Cruise’s driverless operating permits.
This article draws on the 105-page main Quinn Emanuel report, dated January 24, 2024 and released by Cruise after an investigation commissioned by the Cruise and GM boards. The PDF has 195 pages including a separate technical appendix. The main investigation addresses Cruise’s response to the accident and its disclosures to regulators and the public, rather than independently reconstructing the accident’s technical causes.
Nine passages that stood out
Different cuts of the same video, a large online war room, regulator briefings interrupted by freezing video, and a Slack reply that two employees understood differently. The notes below focus on those concrete records and operating practices rather than simply recounting the aftermath in chronological order.
The investigative team interviewed 88 current or former Cruise employees and contractors, but did not interview regulators and could not conclusively establish which video frames were displayed at some briefings. This article distinguishes Cruise employees’ recollections, regulators’ reported positions and the investigators’ findings. Page references are to the printed pages of Quinn Emanuel’s main report; the PDF also contains a separate technical appendix.
The CEO made a four-second video. It showed only the other car striking the pedestrian
Immediately after the accident, the 14-second video available to Cruise showed a human-driven car hitting the pedestrian and propelling her into the Cruise AV’s path. It did not show the AV moving again after its subsequent collision with the pedestrian.
At 1:06 a.m., then-CEO Kyle Vogt made a four-second cut from that video, showing only the other car striking the pedestrian, and sent it to senior government-affairs and legal executives.
The government-affairs executive agreed that, if a video was released, this cut should be the primary one. He also suggested showing it first to regulators, followed by a wider view.
At that time, Cruise had not yet made its full recording of the pedestrian dragging available internally. Crucially, the investigators found no evidence that the four-second cut was actually shown at a regulatory briefing.
More than 200 people cycled through the emergency war room. One witness said the playbook was abandoned as too manual
Cruise paged employees across the country and set up an online emergency war room using Google Meet and a dedicated Slack channel.
When the incident was escalated to its highest severity level, Sev-0, up to 200 additional employees were paged. More than 200 people joined and left the war room over the night and following day.
Cruise had a Sev-0 incident-response playbook assigning responsibilities and outlining the phases from mobilization through recovery.
At least one interviewee said the playbook had been “aborted” for this accident because it was “too manually intensive.”
That is an interviewee’s account; the investigators said other circumstances appeared to support it.
Even after learning about the dragging, PR kept showing media a clip ending at impact and using the 'complete stop' line
By the morning of October 3, senior Cruise leaders had discussed the vehicle’s secondary movement and the pedestrian dragging. Their communications team was also working to correct initial news coverage that had omitted the other car’s role in causing the first collision.
A communications executive recommended not changing the original public messaging, partly to avoid triggering another news cycle. In an internal Slack message, he said they had shared the information with regulators and investigators and had no obligation to share everything with the press.
Even after learning about the secondary movement, the communications team continued screen-sharing a 21-second clip that ended before it, while telling reporters the AV had come to a complete stop immediately after striking the pedestrian.
On October 13, when another employee proposed reusing the prepared “complete stop” line, legal and technical colleagues objected and the sentence was removed.
Engineering and safety raised a fleet pause. Executives said the available evidence did not justify one
Shortly after noon on October 3, engineers and safety staff showed leadership a detailed graph of the vehicle’s post-collision movements. It made the interval between the initial impact and final stop visible.
According to the report, the CEO commented that it was fortunate the vehicle had stopped after approximately 20 feet when it detected interference with a tire, rather than continuing to search for somewhere to pull over.
The engineering and safety teams raised the question of grounding the fleet until a rapid software fix could improve the vehicles’ ability to detect people near or beneath them.
The CEO and COO decided that the evidence, considered alongside Cruise’s overall driving and safety record, did not justify a shutdown then. The CEO reportedly called the incident an extremely rare “edge case.” This was the decision on October 3. On October 27, Cruise notified NHTSA that it had decided to pause driverless operations in all its markets.
'Video worth a thousand words' — but it cut out before the car moved again
During an October 3 video call with the National Highway Traffic Safety Administration (NHTSA), Cruise attempted to show the complete 45-second, nine-camera recording. The engineer presenting from home experienced repeated connectivity problems: the video froze, went black or turned white.
Interviewees also recalled an instance when the presenter stopped the video after the initial impact to take questions and did not resume it. Cruise did not verbally explain the subsequent movement or dragging during the meeting.
Afterward, a lawyer who attended wrote on Slack that the regulators had said the “video was worth a thousand words” — but also that the video had cut out before the vehicle started moving again.
He expected questions once the complete file was sent. Cruise did provide the full file to NHTSA that day, but the investigators criticized its failure to explain the material facts during the briefing itself.
'We did show them the full video. But they did not notice': the internal account of a DMV briefing
Also on October 3, Cruise briefed California’s Department of Motor Vehicles (DMV). Some Cruise attendees recalled showing the full video; DMV officials said they did not see the part depicting the vehicle’s secondary movement and were not told about it.
Quinn Emanuel could not conclusively determine from forensic evidence what was shown on screen. It found that Cruise likely attempted to play the full recording, but connectivity problems probably prevented the relevant portion from being seen.
In an October 16 Slack exchange during another DMV meeting, looking back at the October 3 briefing, a Cruise employee said they remembered showing the complete recording and added: “But they did not notice.”
Other interviewees reported hearing that a meeting attendee had expressed relief that DMV did not ask about the dragging. These are second-hand interview accounts, not definitive records of an identified attendee’s exact words.
City officials asked for repeated showings of the full video. Two Cruise employees were seeing it for the first time
On the afternoon of October 3, Cruise met with San Francisco transportation, police and fire officials. Here the full video played without technical interruptions. City officials noticed the movement, asked questions and requested replays; one account put the number of plays as high as six.
But two of the four Cruise employees at this meeting told investigators that they, too, were seeing the full video for the first time.
One recalled how obvious the vehicle’s movement was when the recording played. Another described seeing the vehicle move again as a “jolt of lightning.”
The report notes that other members of the same government-affairs organization had attended earlier regulator briefings and an internal debrief, yet the employees about to meet city officials had not received a full handover.
The ten-day incident report said 'no updates' after two employees interpreted the same Slack reply differently
For Cruise’s ten-day NHTSA incident report, a paralegal was allowed to retain the previous narrative without secondary legal review if he determined there was no new information.
He asked colleagues on Slack whether the incident had any updates, particularly news of the pedestrian’s condition. A colleague who dealt with law enforcement replied that he had contacted the investigating officer but had heard nothing back.
The colleague later said he had answered only the question about the pedestrian’s condition; the paralegal said he took the reply to mean there were no updates about the incident as a whole.
After also checking the incident database, the paralegal submitted the ten-day report without checking again with legal or government affairs. The report repeated the original narrative and still omitted the movement and dragging already known inside Cruise.
DMV wanted the original 45-second, nine-pane video. Cruise brought a new nine-minute, six-pane version
On October 10, the DMV requested nine-camera footage from 60 seconds before contact with the pedestrian until law enforcement instructed Remote Assistance to disable the autonomous technology. Rather than send it that night, Cruise asked to show the material first in another meeting, which took place on October 13.
Cruise presented a newly assembled, approximately nine-minute video with six camera panes. DMV officials wanted the original 45-second recording with nine camera panes.
The longer video came in two parts: footage beginning 60 seconds before the collision, and footage of the police and fire response. However, it omitted the lower frontal camera angles that showed the AV’s impact and post-collision movement most clearly.
DMV officials questioned whether part of the footage had been skipped and asked again for the original nine-camera recording. Cruise uploaded that full version to the DMV portal at 12:19 p.m. that day.
What the report says about the background
Quinn Emanuel did not conclude that Cruise deliberately concealed the dragging in its initial regulator briefings. Based on the evidence available at the time of its investigation, it said intent to mislead had not been established, noting attempts to show the full video and the provision of that video to NHTSA later on October 3.
The investigation nevertheless faulted Cruise for assuming that a video could communicate all necessary facts without an affirmative verbal explanation — particularly when transmissions failed — and for not correcting earlier briefings after more internal information became available. It also found that leadership’s focus on correcting inaccurate news coverage about who caused the first collision overshadowed the need to communicate the vehicle’s subsequent movement.
Corrections to this article
Clarified that the article uses the 105-page Quinn Emanuel main report within a 195-page PDF including a technical appendix. Recast the later fleet pause as the October 27 notification to NHTSA documented in that report, corrected who requested video replays and the attribution of second-hand DMV accounts, and expanded page references for full-video availability, delivery and forensic limitations.