# Cruise safety record

12 incident(s) on file for Cruise, rolled up across its models and deployments (operated or manufactured). Retracted claims are excluded from this count but remain reachable at their own canonical URLs.

[Back to Cruise](/companies/cruise.md)

## Incidents (12)

- [Cruise admits a false report to a federal investigation; $500K DOJ deferred-prosecution agreement](/incidents/cruise-doj-dpa-false-report-2024.md) (2024-11-14): Regulatory action · severity: serious · DOJ (N.D. Cal.) · consent decree
- [NHTSA fines Cruise $1.5M for failing to fully report the Oct 2023 pedestrian-dragging crash](/incidents/cruise-nhtsa-consent-order-2024.md) (2024-09-30): Regulatory action · severity: serious · NHTSA · fine
- [Cruise recalls its entire 1,194-vehicle fleet over unexpected hard braking](/incidents/cruise-fleet-braking-recall-2024.md) (2024-08-22): Recall · severity: moderate · NHTSA · recall ordered
- [Software May Cause Unexpected Braking](/incidents/nhtsa-cruise-recall-24e067000.md) (2024-08-09): Recall · NHTSA
- [Cruise recalls 950 ADS units (NHTSA 23E-086) over post-crash pullover behavior](/incidents/nhtsa-cruise-collision-detection-recall-2023.md) (2023-11-07): Recall · severity: critical · NHTSA · recall ordered
- [ADS Software May Improperly Respond After a Crash](/incidents/nhtsa-cruise-recall-23e086000.md) (2023-11-07): Recall · NHTSA
- [California DMV suspends Cruise's driverless deployment and testing permits as not safe for public operation](/incidents/cruise-ca-dmv-permit-suspension-2023-10-24.md) (2023-10-24): Regulatory action · severity: serious · California DMV · suspension
- [Cruise driverless robotaxi dragged a pedestrian ~20 feet in San Francisco](/incidents/cruise-sf-pedestrian-dragging-2023-10-02.md) (2023-10-02): Injury · severity: critical · California DMV · suspension
- [Cruise robotaxi collided with an SF fire truck responding to an emergency; one passenger injured](/incidents/cruise-sf-firetruck-collision-2023.md) (2023-08-17): Collision · severity: moderate · California DMV · investigation
- [Cruise recalls 300 ADS units (NHTSA 23E-029) over articulated-vehicle misprediction](/incidents/nhtsa-cruise-articulated-vehicle-recall-2023.md) (2023-04-03): Recall · severity: moderate · NHTSA · recall ordered
- [ADS Software Error May Cause Crash](/incidents/nhtsa-cruise-recall-23e029000.md) (2023-04-03): Recall · NHTSA
- [Cruise recalls 80 ADS units (NHTSA 22E-072) over unprotected-left hard-braking software](/incidents/nhtsa-cruise-reflexive-planner-recall-2022.md) (2022-08-29): Recall · severity: moderate · NHTSA · recall ordered

## Exposure

DEPLOY does not have exposure data (deployment-hours, miles driven, or rides given) on file for Cruise's 1 recorded deployment(s). No incident count above can be turned into a defensible rate without it. NHTSA's SGO dataset itself does not publish exposure denominators; there is no standardized, regulator-verified nationwide source for AV fleet mileage or ride counts today.

## A note on NHTSA's crash-reporting data

Many of the incidents below are drawn from NHTSA's Standing General Order (SGO) 2021-01 crash-reporting program, which requires manufacturers and operators of automated driving systems (ADS) and advanced driver-assistance systems (ADAS) to report qualifying crashes. It is the only nationwide, cross-operator crash dataset that exists for this industry, and it is also, by NHTSA's own design and Consumer Reports' public assessment, an imperfect one.

Reporting companies may redact narrative fields as confidential business information (CBI). In practice this means narrative completeness is uneven across manufacturers in the underlying dataset: some incident reports read as full prose descriptions of what happened, others are replaced with boilerplate redacted text. This is a property of the source data, not of DEPLOY's editorial process; DEPLOY publishes what the filing discloses and states plainly when a fuller account is not publicly available.

The SGO dataset also does not publish exposure denominators (miles driven, hours operated, rides given) alongside crash counts, so a raw incident count cannot be turned into a rate without an independently sourced denominator. See "Exposure" below for what DEPLOY does and does not have on file for this company.

- [NHTSA: Standing General Order on Crash Reporting](https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting)
- [Consumer Reports: comments to NHTSA on incident reporting for ADS and Level 2 ADAS](https://advocacy.consumerreports.org/research/consumer-reports-comments-to-nhtsa-on-incident-reporting-for-automated-driving-systems-and-level-2-adas/)
- [Consumer Reports: statement on crash-reporting underreporting](https://advocacy.consumerreports.org/press_release/transportation-department-keeps-in-place-vital-car-crash-reporting-program-but-misses-chance-to-address-underreporting-consumer-reports-statement/)

## Common questions

**What is Cruise's safety record?**

DEPLOY has 12 incidents on file for Cruise, drawn from NHTSA's Standing General Order crash-reporting program and press coverage. Each incident below is individually sourced and dated; see the incident list for details.

**Is Cruise safer than a human driver?**

DEPLOY does not have exposure data (miles driven or hours operated) on file for Cruise, so no per-mile or per-hour safety rate can be computed from this registry today. This is a documented industry-wide data gap, not unique to DEPLOY: NHTSA's own SGO dataset does not publish exposure denominators alongside crash counts. Any rate comparison you see elsewhere may rely on a company's self-published mileage figures, which are not independently audited.

**Does DEPLOY redact or omit crash details for Cruise?**

No. DEPLOY does not redact incident narratives. Where a source narrative is itself incomplete (for example, a NHTSA SGO filing redacted as confidential business information), DEPLOY states that plainly rather than filling the gap. See "A note on NHTSA's crash-reporting data" below.


_API: GET /v1/safety/companies/ce8ff680-3fe7-4398-b31b-f85dc3073f3a/profile (bearer-gated) · canonical URL: /companies/cruise/safety-record_