Anatomy of a Self-Inflicted Wound

In October 2023, a Cruise autonomous vehicle was involved in a serious pedestrian accident in San Francisco. The sequence of events that followed—and Cruise's handling of the information surrounding it—led to the suspension of the company's driverless deployment license by the California DMV on 2023-10-24. A subsequent 200-page investigation by the law firm Quinn Emanuel, commissioned by Cruise's boards of directors, provides an unusually detailed public look at how a technology company managed (and mismanaged) a safety-critical incident.

Clearing Up the Record

Most summaries of the report miss the full picture, and notably, the report itself contains material both more damning and more favorable to Cruise than most coverage suggests. The central issue is not whether Cruise's vehicle caused the accident, but what the company did—and failed to do—in communicating about it afterward.

The sequence of events that matters for understanding the report is this: a human-driven Nissan struck a pedestrian on 2023-10-02, putting that pedestrian into the path of a Cruise AV. The AV stopped, then resumed movement, dragging the pedestrian approximately 20 feet before stopping again. By the morning of 10-03, Cruise leadership and over 100 employees knew about the dragging.

The plan was to disclose the dragging by showing the full video of the incident, letting it "speak for itself." Cruise assumed regulators would ask questions and that Cruise would provide further information in response. In practice, the report concludes the company's leadership was "fixated on correcting the inaccurate media narrative" that the Cruise AV itself had caused the initial accident. That fixation led Cruise to emphasize the Nissan's role while omitting other important information about the secondary movement, in communications with media, regulators, and government officials.

The evidence suggests Cruise did attempt to play the full video in meetings with regulators. However, in three meetings, internet connectivity issues may have prevented regulators from seeing the accident in full, and Cruise personnel did not explicitly point out that the dragging had occurred. Cruise employees note the NHTSA received the full video immediately after a 10-03 meeting, and that the CPUC declined an offer to see it. In meetings on 10-03 with the SF MTA, SFPD, and SFFD, the full video was played without technical issues and discussed thoroughly.

The DMV's suspension order stated that Cruise failed to disclose the AV's forward movement after impact, that the video Cruise played showed only part of the accident without the dragging, and that the DMV learned of the dragging from another government agency. NHTSA and CPUC took actions against Cruise with similar claims. Media outlets also said they were misled.

Cruise leadership concedes it never notified the media of the dragging, but held that its obligations to journalists differ from its obligations to regulators.

What the Report Covere

The investigation reviewed approximately 205,000 documents—including emails, texts, Slack messages, and internal company documents—and interviewed 88 current and former employees and contractors. It also reviewed a third-party report from Exponent Inc. The review excluded some former employees unavailable due to personal circumstances or Cruise's wide-scale Reduction in Force, but those interviews were not deemed important to the findings.

The report does not attempt to evaluate the broader safety of Cruise's AV operations, noting those questions are "more appropriately evaluated by those with engineering and technical safety expertise."

Root Causes and Lessons

The report attributes Cruise's failures to several factors: poor leadership, mistakes in judgment, lack of coordination, an "us versus them" mentality toward regulators, and what the authors describe as "a fundamental misapprehension of Cruise's obligations of accountability and transparency to the government and the public."

The most striking conclusion is that the DMV suspension was not the result of the accident itself but of Cruise's response to it. As one Cruise employee texted another: "leaders have failed us."

The report is blunt about the strategic error: taking the position that a video of an accident causing serious injury provides all necessary information to regulators—without affirmatively explaining all relevant facts—is not how a regulated business should interact with its regulators.

What's notable from an engineering culture perspective is how ordinary much of Cruise's behavior appears by tech industry standards. The report describes as "unconscionable" conduct that, while certainly more transparent than what the report's authors might see at typical tech companies, would be unremarkable in much of the industry. The gap between safety-critical systems culture and tech culture is a recurring theme in post-incident analyses, and this report is a rare public example of that clash documented in detail.

Incident reports at this depth are common in safety-critical fields like aviation and medicine but almost unheard of for technology companies, whose post-mortems typically stay internal and narrowly scoped. The public nature of this report—and its willingness to describe conduct and decision-making in detail—makes it a valuable document for anyone interested in how technology companies handle serious incidents and regulatory interaction.

What Happened on October 2

At 9:29pm on October 2, a human-driven Nissan Sentra struck a pedestrian in a crosswalk at 5th and Market Streets in San Francisco. The pedestrian had entered the crosswalk against a red light and a "Do Not Walk" signal and paused in the Nissan's lane; police cited both parties and found the human driver "most at fault." The impact threw the pedestrian into the path of a Cruise autonomous vehicle (AV), which braked but still hit the pedestrian.

After coming to a complete stop, the AV executed what Cruise calls a "minimal risk condition" pullover maneuver — a secondary movement to find a safe place to stop. That maneuver drove the AV up to 7.7mph for roughly 20 feet, dragging the pedestrian underneath. The Nissan driver fled the scene.

Internal timeline: what Cruise knew and when

From the moment of the collision, Cruise's internal handling of the accident unfolded in distinct phases:

  • 9:29pm — The AV transmitted a low-resolution 3-second video (Offload 1), confirming the collision to Cruise's Remote Assistance Center. At 9:32pm, it sent a 14-second medium-resolution video (Offload 2) of the collision, but this clip did not capture the pullover maneuver or the dragging.
  • 9:40pm — The San Francisco Fire Department used heavy rescue tools to remove the pedestrian from under the AV.
  • 9:49pm — Cruise's Incident Response team labeled the event a "Sev-1" (minor collision) and set up a virtual "war room" on Google Meet with a dedicated Slack channel and about 20 employees.
  • 10:17pm — Contractors arrived at the scene. One took more than 100 photos and videos, noting blood and skin patches on the ground showing the AV had moved from the point of impact to its final resting position.
  • 11:31pm — Cruise escalated the incident to "Sev-0," reserved for "major vehicle incident with moderate to major injury or fatality." Severity of the event; roughly 200 additional employees were paged to the war room.

The overnight scramble over video

Shortly after midnight, Cruise's focus shifted to media strategy. At 12:15am, an incident management meeting convened with 140 invites to share updates and discuss rebutting articles claiming the AV caused the accident. At 12:53am, Cruise issued a press release stating the Nissan was at fault. CEO Kyle Vogt and Communications VP Aaron McLear heavily edited the statement. It made no mention of the pullover maneuver or the dragging; employees involved said they were not aware of those facts at the time.

The AV returned to Cruise's facility at 1:30am and engineers began downloading full collision data, including complete video. By 2:14am, a 45-second video depicting the pullover maneuver and dragging was available, but no employee received notification that it was ready until more than four hours later, when all data processing had completed.

At 3:21am, at the request of government affairs, Director of Systems Integrity Matt Wood created a 12-second video showing the Nissan hitting the pedestrian and the pedestrian landing in front of the Cruise AV — cutting off before the AV's own impact. At 3:45am, Wood posted the first known internal communication about the pullover maneuver and dragging to the war room Slack channel, writing that the AV "drives forward another 1–2 car lengths before coming to its final position."

The 6am meetings: dragging confirmed internally

By 6:00am on October 3, dragging was being actively discussed. The Crisis Management Team (CMT) meeting — with more than 100 people including COO Gil West, co-founder and Chief Product Officer Dan Kan, and the VP of Communications — covered the pullover and dragging. Slack messages from 6:17am, 6:25am, and 6:56am confirmed the discussion. At 6:28am, the 45-second, 9-pane "full video" of the pullover and dragging was posted to the war room Slack channel.

The 6:45am Senior Leadership Team (SLT) meeting, attended by Vogt and McLear, included explicit discussion of whether to share the full video with media or amend the existing press statement. The decision was to do neither. The group reasoned that revising the earlier statement would cost them credibility. Despite this, members of the communications team knew by this point that the phrase "AV came to a complete stop immediately after impacting the struck pedestrian" was inaccurate, yet continued providing it to press. The claim was not removed from public materials until October 13, after a comms employee flagged it to legal, which responded, "I don't think we can say this."

Regulatory briefings with an incomplete picture

Wood showed the full video at several meetings with regulators and officials on October 3, without proactively raising the pullover maneuver or dragging. At 10:05am, he and VP of Global Government Affairs Prashanthi Raman met virtually with the Mayor of San Francisco's transportation advisor. At 10:30am, they met with the National Highway Traffic Safety Administration (NHTSA). At 11:30am, a hybrid meeting with the DMV and California Highway Patrol (CHP) took place. In the first two sessions, Wood reportedly experienced internet connectivity issues causing the video to freeze or black out in key places, including immediately after the initial impact. Neither Wood nor Raman raised the pullover or dragging in any of these meetings.

At 3:30pm, a meeting with SF MTA, SFPD, and SFFD had no technical problems. Wood showed the full video several times. Cruise did not bring up the pullover or dragging, but officials saw it on screen and asked questions about it.

Engineering findings and the grounding decision

During the 12:00pm CMT meeting, engineers presented findings including a chart detailing the AV's movement. After the initial collision, the AV moved forward again, dragging the pedestrian roughly 20 feet. The AV was programmed to move up to 100 feet in such a maneuver, but internal systems flagged a failed wheel speed sensor — the wheels were rotating at different speeds because one was spinning on the pedestrian's leg — which stopped the car early.

At the 12:40pm SLT meeting, attended by Vogt, West, and Chief Legal Officer Jeff Bleich, the safety and engineering teams raised the question of grounding the fleet until a fix could be deployed. Vogt and West said no. Vogt reportedly stated it was good the AV stopped after 20 feet upon detecting wheel interference, rather than continuing as programmed for up to 100 feet or one full block.

Regulatory response and aftermath

The timeline of submissions and investigations shows gaps between what Cruise knew and what it reported:

  • October 3, 2:37pm — Cruise submits its 1-day report to NHTSA; no mention of the pullover or dragging.
  • October 5, 10:46am — Forbes asks Cruise to comment on the dragging. Cruise declines and stands by its October 3 press release.
  • October 6 — Forbes publishes "Cruise Robotaxi Dragged Woman 20 Feet in Recent Accident, Local Politician Says."
  • October 11, 12:48pm — A Cruise paralegal submits the 10-day NHTSA report; it omits the pullover and dragging because "no one told the paralegal these facts needed to be added."
  • October 12 — NHTSA notifies Cruise it intends to open a Preliminary Evaluation (PE) covering the October 2 accident and three other pedestrian-related events.
  • October 13 — Cruise meets with DMV and CHP, sharing a 9-minute, 6-pane video. DMV clarifies it wants the 45-second, 9-pane full video, which Cruise uploads at 12:19pm.
  • October 16 — NHTSA officially opens the PE. DMV and CHP state they don't believe they were shown the full video during the October 3 meeting.
  • October 19 — Cruise provides the full video in response to the CPUC's October 5 request for information.
  • October 24, 10:28am — DMV suspends Cruise's driverless permit. Cruise publishes a blog post claiming it "proactively shared information" with regulators "including the full video."
  • November 2 — Cruise's 30-day NHTSA report includes discussion of the pullover and dragging. Cruise recalls 950 systems.
  • December 1 — CPUC issues an Order to Show Cause for "failing to provide complete information and for making misleading public comments regarding the October 2, 2023 Cruise related incident."

The role of the video clips

Six video clips emerged from the accident, each showing a different slice of events:

  • Offload 1 (9:29pm) — Low resolution, 3 seconds, 4-pane; captures audio immediately after the collision.
  • Offload 2 (9:32pm) — 14 seconds, 9-pane, no audio; shows the Nissan-pedestrian collision and the pedestrian entering the Cruise AV's path.
  • Media Video (10:04pm) — 21 seconds, 4-pane; derived from Offload 2 but slowed down.
  • 4-second clip (1:06am) — Cut by Vogt from Offload 2, showing only the Nissan hitting the pedestrian from a single front-left pane. Sent to government affairs and legal with the note "this is the cut I was thinking of." No evidence this short clip was shown at any regulatory meeting.
  • 12-second video (3:21am) — Created by Wood at the request of Raman and Estrada, who wanted a clip showing "the impact and the person landing in front of us and then cut it there." The video stops before the AV hits the pedestrian.
  • Full video (6:28am) — 45 seconds, 9-pane, no audio; shows the pullover maneuver and the pedestrian being dragged.

Internal warnings from engineering

Several engineers within Cruise saw the discrepancy between internal knowledge and public statements and flagged the risk. During the 6:00am CMT meeting, one engineer noted in the war room Slack channel that "someone who has access to our AV video... could see later that the AV traveled about this distance post-collision, because there is a video on social media which shows the AV stopped with the pedestrian underneath." The same engineer later wrote after the DMV suspension that they had "pointed out in the channel that it was not hard to conclude there was movement after the initial stop." Following the suspension, he added: "it seems the DMV fully understanding the entire details was predictable."

Internal response processes also broke down. Cruise's incident response playbook — outlining roles for Incident Commander, SLT, and CMT — was not followed and was described as "aborted" because it was "too manually intensive." The 6:05pm CMT meeting on October 3 concluded with Vogt and West ending the Sev-0 war room and disbanding the effort. Some employees expressed concern that no future CMT meetings were scheduled for what was the biggest incident in Cruise's history. Suggestions to continue a "miniature CMT" were supported by Chief Legal Officer Jeff Bleich but never implemented.

How Cruise Briefed Regulators After the October 2 Incident

In the hours and days after the October 2 accident, Cruise's communications with regulators varied significantly by agency. The company proactively reached out to several bodies, but the content of those briefings — and what was left out — became a central issue in the aftermath.

Initial Outreach and the Mayor's Office Meeting

Cruise's first regulatory contact came early on October 3. The company's Head of Regulatory Engagement emailed NHTSA at 7:25am, flagging issues that included whether the ADS or remote assistant could ascertain that a pedestrian was trapped under the vehicle, the vehicle control dynamics leading to the incident, and video of the accident.

That same day, Cruise met with Alexandra Sweet, transportation advisor to the Mayor's office. Cruise employee Matthew Wood played the full video during the meeting — an approach that became the standard presentation from Cruise — though connectivity issues meant the video had to be played twice. Sweet appeared to notice that the vehicle moved again after its initial stop, but did not ask about dragging or why the vehicle moved.

Preparing for NHTSA

Before its NHSTA meeting, Cruise prepared talking points for anticipated questions. On whether the fleet had been stopped, Alicia Fenrick stated: "We have not changed the posture of the fleet. We have not identified a fault in AV response."

On why the vehicle moved after initially stopping, the pre-meeting notes show the topic was marked "[Not discussed]" and Wood's prepared answer described the movement as a collision detection response: "The impact triggered a collision detection and the vehicle is designed to pull over out of lane." Internal notes from an employee capture the concern: "Alicia: Biggest issue candidly. That we moved, and why, is something we are going to need to explain. The facts are what they are." The guidance was to refer to it as "collision detection" rather than qualifying it as a minor collision.

Slack messages from the pre-meeting show discussion of when and which video should be sent. The team decided to play the full video to avoid being "accused of hiding the ball."

The NHTSA Meeting

During the October 3 meeting with NHTSA, Wood played the full video two or three times, but "it kept stopping or blacking- or whiting out because his home computer was having connectivity issues." As a result, "NHTSA did not see the Full Video clearly or in its entirety."

There was no discussion of the pullover or dragging. When NHTSA asked whether the remote assistant could detect that a pedestrian was trapped, Wood answered "Yes." The statement "the last thing you would want to do is move when a pedestrian is underneath" appears to have been said during the call, but recollections disagree on who said it and who concurred.

Post-meeting Slack discussion shows employees grappling with how to handle this. One employee noted: "I think we might need to mention the comment Matt made during the NHTSA call that the last thing you would want to do is move with a pedestrian under the car." Another responded: "lets see where the conversation goes. if it's relevant, we should share it. That's not the main point here though." A Senior Director of Federal Affairs said he "stands by it," believing Cruise employees "have gone beyond their regulatory requirements."

Escalation with NHTSA

NHTSA sent a request for video after the meeting, and Cruise uploaded the full video that same afternoon. On October 12, however, NHTSA informed Cruise it was planning a Preliminary Evaluation. A Cruise employee relayed: "She shared that there was a lot of consternation in the front office about last week's incident. It is going to be a pretty broad investigation into how vehicles react to pedestrians out in the street and people in the roadway."

Cruise's planned response for the October 13 meeting pushed back on the escalation: "We've been extremely cooperative with the Agency and have always provided information that the agency requested. What will be gained by this escalation that we are not already providing?" The agenda also stated: "PEs are punitive means to gather information, and are reputationally harmful, particularly in a nascent industry." Notably, Cruise's Chief Legal Officer and Senior Vice President of Government Affairs did not attend the meeting despite the potential consequences, including a recall.

The Preliminary Evaluation was opened on October 16.

The NHTSA Written Reports

NHTSA's Standing General Order requires three written reports, including "a written description of the pre-crash, crash, and post-crash details." Cruise's first two reports did not mention the pullover or dragging. The third report, filed after consultation with GM, did.

The 1-day report's original draft described the sequence: the pedestrian passed through the AV's lane of travel but stopped mid-crosswalk in the adjacent lane, the Nissan Sentra made contact with the pedestrian, "launching the pedestrian in front of the AV," and the AV braked aggressively but made contact. Suggested edits from GM included changing "launching" to "deflecting" and removing "this caused no damage to the AV." No one discussed including the pullover or dragging.

A drafted but unused response to an employee question about the omission stated: "The purpose of the NHTSA reporting requirement is to notify the agency of the occurrence of crashes. Consistent with that objective and our usual practice, our report notified NHTSA that the crash had occurred. Additionally, we had already met with NHTSA, including showing the full video to them, prior to submission of the report." Quinn Emanuel's review noted the difficulty of squaring this with the regulation's plain language requiring post-crash details.

The 10-day report was filed by a paralegal who checked for updates from three employees and the RINO database, found none, and submitted a report stating: "There are no updates related to this incident since the original submission on October 3, 2023." For the 30-day report, GM urged comprehensiveness. Cruise's Chief Legal Officer Bleich said "[t]he most important thing now is simply to be complete and accurate in our reporting of this event to our regulators" and directed that the pullover and dragging be included, despite objection from Rubenstein.

The DMV: A Different Trajectory

Cruise's interactions with the California DMV followed a separate path with more contentious outcomes. Internally, there was disagreement over which video to show. CEO Kyle Vogt "wanted to focus solely on the Nissan's role in causing the Accident and avoid showing the pedestrian's injuries." An employee suggested: "show the impact and the person landing in front of us. Cut it there. That's all that is needed." Others, including Raman and Danko, pushed for showing the most complete video available.

Fenrick attended the DMV pre-meeting to have overlapping attendees between the NHTSA and DMV meetings, though neither Bleich nor Estrada attended despite planning to meet in-person with the DMV Director.

The October 3 DMV Meeting and Aftermath

DMV regulators do not believe the full video was played at the October 3 meeting. Cruise employees have different recollections, but many believe it was played with significant connectivity issues. There was no discussion of the pullover or dragging.

Post-meeting Slack reflections show relief that the second movement went unnoticed. One employee wrote: "the car moved and they didn't ask and we're kind of lucky they didn't ask." Another noted: "Bigger concern is that no regulator has really clued in that we moved after rolling over the pedestrian."

The DMV asked for a video by October 11; Cruise did not provide it. On October 13, Cruise shared a 9-minute, 6-pane video created by Wood. Notably, "the camera angles did not include the lower frontal camera angles that most clearly showed the AV's impact with the pedestrian and pullover maneuver." The DMV's tone "felt very mistrustful," according to interviewees, and officials had questions about missing or misleading video. Cruise then uploaded the full video to the DMV portal.

At an October 16 meeting scheduled for a different topic, the conversation turned to the DMV being misled. Cruise interviewees recalled that "the DMV and CHP attendees were angry about the October 3 presentation, saying their collective memory was that they were not shown the Full Video."

Revocation and Suspension

By October 23, Cruise was concerned about DMV silence on expanding the San Francisco fleet. A political consultant reported the DMV was "pissed" and considering revoking Cruise's license. There was internal disagreement on this possibility. Estrada messaged Bleich that he had talked to the DMV Director with "[n]o indication whatsoever that they are considering revoking," but the consultant repeated that the DMV was very angry and may revoke.

The October 24 suspension order followed. Estrada called DMV Director Steve Gordon and was stonewalled. Vogt joined and made a personal appeal, saying he'd been "committed to this since he was 13 to try and improve driver safety." The appeal failed.

Internal Slack messages after the suspension show Bleich's assessment: "This will be a difficult fight to win. DMV and CHP have credibility and Steve Gordon seems to swear that he did not see the end of the video. The word of Cruise employees won't be trusted." Estrada disagreed, arguing: "We have proof. If we prove with facts a false statement that is important reputation saving."

Vogt later posted a blog titled "A detailed review of the recent SF hit-and-run incident" that did discuss the pullover and dragging, stating: "The AV detected a collision, bringing the vehicle to a stop; then attempted to pull over to avoid causing further road safety issues, pulling the individual forward approximately 20 feet."

Other Agencies and Reflections

Cruise's meeting with the SF MTA, Fire Department, and Police took a different turn when a government official asked: "this car moves with the woman underneath it, is that what we are seeing?" Two of the four Cruise employees in the meeting reported being shocked to see the pullover and dragging, apparently not having realized this had happened.

With the CPUC, there was disagreement over whether Cruise offered to play the full video during its October 3 communications. The CPUC issued a data request on October 5, and Cruise responded on the October 19 deadline — its standard policy — with the video and a summary that included the attempt to achieve "a minimal risk condition (MRC) by pulling out of the lane before coming to its final stop position."

Bleich later summarized the DMV's concerns: "the main concern from DMV was that our vehicle did not distinguish between a person and another object under its carriage originally, and so went into an MRC. Second, they felt that we should have emphasized the AV's second movement right away in our first meeting."

Vogt expressed frustration: "I am very much struggling with the fact that our GA team did not volunteer the info about the secondary movement with the DMV, and that during the handling of the event I remember getting inconsistent reports as to what was shared." Bleich added that he didn't believe there was a deliberate decision, but that the team "was still in the mode from the previous evening where they were pushing back against an assumption that we either were responsible for hitting the pedestrian or that we did not react fast enough."

Overall, the record suggests that the CEO, CLO, and COO were not actively engaged in the regulatory response during the immediate aftermath, and were instead trying to piece together what had been shared and when.

Regulatory Fallout and Internal Failures

The October 2 accident triggered a cascade of regulatory actions. California's DMV suspended Cruise's license to operate driverless vehicles, though the company could still operate with a human driver behind the wheel. The NHTSA opened a preliminary evaluation that led to a safety recall. The California Public Utilities Commission issued a "show cause" ruling. Cruise subsequently installed new senior management and underwent significant downsizing.

What the Investigation Found

A review by the law firm Quinn Emanuel reached several conclusions about Cruise's conduct in the days following the accident. The report's central finding: by the time Cruise employees from legal, government affairs, operations, and systems integrity met with regulators on October 3, they knew or should have known that the Cruise AV had engaged in a pullover maneuver and dragged the pedestrian underneath the vehicle for approximately 20 feet.

Cruise's passive, non-transparent approach to its disclosure obligations reflected a basic misunderstanding of what regulatory authorities need to know and when they need it, the report concluded.

The investigation could not definitively establish whether NHTSA or the DMV were shown the entirety of the full video of the incident, including the pullover maneuver and dragging. However, the weight of the evidence suggests Cruise attempted to play the video in meetings with regulators, but internet connectivity issues impeded or prevented them from seeing it clearly or fully. When the video froze or blacked out, Cruise employees remained silent, failing to ensure that regulators understood what they likely could not see: that the AV had moved forward again after the initial impact, dragging the pedestrian underneath.

Even if some Cruise employees were unaware of the pullover maneuver and dragging at the time of certain briefings, the report notes that leadership and other personnel were informed of the full details during the day on October 3 and should have taken corrective action.

While Cruise employees demonstrated mistakes of judgment and a failure to appreciate the importance of transparency, the evidence did not establish that anyone sought to intentionally mislead government regulators.

Leadership and Coordination Failures

The report describes Cruise's response as reflecting deficient leadership at the highest levels, including among some members of the C-Suite, legal, governmental affairs, systems integrity, and communications teams. This led to a lack of coordination, mistakes of judgment, misapprehension of regulatory requirements, and inconsistent disclosures at critical meetings. The end result: a profound loss of public and governmental trust and suspension of Cruise's business in California.

There was no captain of the ship. No single person or team within Cruise appears to have taken responsibility to ensure a coordinated and fully transparent disclosure of all material facts regarding the October 2 Accident to the DMV, NHTSA, and other governmental officials.

Various members of the senior leadership team were missing-in-action for key meetings, both preparatory and with regulators. Each team prepared independently, different employees attended different regulatory meetings, and no senior official provided overall direction. Senior leadership never convened a meeting after the October 3 briefings to discuss how they went, what questions were asked, or what discussions took place. Had they done so, they would have realized that in only one of the four meetings did officials ask questions about the pullover and dragging.

The report also cites preexisting weaknesses. Cruise lawyers displayed a lack of understanding of what information must be communicated to NHTSA in required reports. Leadership gave a paralegal primary responsibility for preparing and filing such reports, with the legal department exercising little oversight.

Recommendations

  • Install new senior leadership
  • Consider creating a dedicated, cross-disciplinary regulatory team that understands regulations, has experience dealing with regulators, and proactively improves reporting processes, reporting directly to the CEO with board oversight
  • Provide training for remaining senior leadership
  • Create a streamlined crisis management team—200 people in a war room cannot manage a crisis, and someone needs to be in charge
  • Review incident response protocol and ensure it is followed
  • Reform the governmental affairs, legal, and public communications functions
  • Have a designated Chief Safety Officer or senior engineer, as well as a regulatory lawyer, review and approve each accident report before filing

Engineering Root Cause

The report's appendix includes an analysis from Exponent, mostly redacted but with significant non-redacted content. The collision detection system incorrectly identified the pedestrian as being on the side of the AV at the time of impact rather than in front of it, and determined the collision to be a side impact. That determination led to a less severe collision response, causing the AV to perform a subsequent outermost lane stop maneuver instead of an emergency stop. The root cause of the AV's post-collision movement was the inaccurate determination that a side collision had occurred. Because of the inaccuracy of the object track and the disparity between that track and the pedestrian's actual position, the ADS failed to accurately determine the pedestrian's location at the time of impact and while underneath the vehicle.

Industry Perspectives

One retired executive who formerly worked on autonomous vehicles offered a comparison between incident management at Cruise and at tech companies. The executive noted that companies become good at handling incidents when they face a steady stream of varying severity and must handle the many small ones. They become terrible at it if they can cover up small incidents until a big one happens. Internet companies, which handle frequent small incidents, often do better than AV companies.

The same executive was skeptical of the "minimal risk condition" pullover maneuver, describing these maneuvers as "magic pixie dust making AVs safe: if something happens, we'll do a safety pullover maneuver." Regarding Cruise's deleted blog post on the incident, the executive noted that the mention of regulatory ADAS test cases did not inspire confidence—"these tests are shit"—while acknowledging that companies naturally cite such tests even if they have better ones.

The executive also observed that people in safety-critical industries care about compliance, not about doing things right. Anything above the state of the art buys no credit with regulators. Conversely, if a poor tool or process exists but is considered state of the art or mandated by a standard, companies will use it regardless of whether it actually helps.

A Hardware Question and an Uneven Comparison

The conversation with the executive also touched on a more general piece of hardware curiosity: why don't the AVs on the road come with upgraded tires and brakes? It's a well-established fact that the simplest safety upgrade for any car is better tires (and brakes, where relevant), which can dramatically shorten stopping distances—especially on the low-performance, commodity vehicles that are often converted into AVs.

While the exec hadn't considered the upgrade before, they acknowledged that better tires and brakes would likely prevent accidents in many other scenarios, and offered a blunt explanation for why it isn't standard practice:

I think if you have a combination of "we want to base AV on commodity cars" and "I am an algorithms guy" mindset you will not go look at what the car should be.

To be clear, however, upgraded hardware would not have changed the outcome in this particular incident. The timeline from the Exponent report shows a very short chain of events:

  • -2.9s: contact between Nissan and Pedestrian
  • -2s: Pedestrian track dropped
  • -1.17s: Pedestrian begins separating from Nissan
  • -0.81s: [redacted]
  • -0.78s: Pedestrian lands in AV's travel lane
  • -0.41s: Collision checker predicts collision
  • -0.25s: AV starts sending braking and steering commands (19.1 mph)
  • 0s: collision (18.6 mph)

Actual accelerometer data from a car with upgraded tires and brakes shows a stopping time of around 0.8s from 19.1 mph. With only 0.25s between the braking command and impact, and given the significant latency that occurs unless brakes are pre-charged, almost no braking could have occurred—evidenced by the speed dropping just 0.5 mph before the collision.

On the broader question of human versus machine reaction, the exec noted that "scene understanding" as a human does it is largely absent from current AVs. While a human who noticed the accident in the adjacent lane would likely drastically slow down or stop—the exec believed most would come to a complete stop—the AV is unsurprisingly unresponsive until the pedestrian is directly in its path. The 530ms latency between the pedestrian landing in the lane and the AV initiating braking wasn't surprising to the exec, even though it struck a layperson as substantial.

When asked about the advantages of AVs and ADAS over a fully attentive human, the exec's assessment was measured:

They mainly never get tired or drink and hopefully also run in that terrible driver's car in the next lane. For [current systems], it's reliability and not peak performance that makes it useful. Peak performance is definitely not superhuman but subhuman.