Cruise robotaxis investigated after sudden braking led to rear-end collisions

In December 2022 U.S. regulators opened a probe after reports that Cruise autonomous taxis braked suddenly and were rear-ended. The National Highway Traffic Safety Administration's Office of Defects Investigation (ODI) initiated a preliminary evaluation after receiving multiple reports of unexpected braking and immobilizations. News outlets and an incident database documented the events and the regulatory review.

Cruise · Incident Dec 12, 2022 · Indexed Jun 10, 2026 · 5 sources

The autonomous driving system allegedly initiated unexpected hard braking and immobilizations that created roadside hazards.
What
In December 2022 U.S.
Incident date
Dec 12, 2022
Who
Cruise
Failure mode
Agentic Action Error
AI surface
Autonomous System
Severity
High

What happened

In December 2022 multiple news outlets reported that Cruise autonomous taxis slowed suddenly or braked hard while in traffic. Those maneuvers were reported to have led to rear-end collisions and created traffic disruptions. Following those reports the NHTSA Office of Defects Investigation opened a preliminary evaluation after receiving multiple reports of unexpected braking and immobilizations by Cruise vehicles.

What broke inside the model

Failure path · mode profile · Agentic Action Error
  1. 01 · TriggerAn agent plans a multi-step task.
  2. 02 · Model stepIt chooses a wrong or destructive action.
  3. 03 · Control gapNo confirmation gate guards the write.
  4. 04 · FailureThe action commits to a system of record.
  5. 05 · ConsequenceData is changed or destroyed irreversibly.

A wrong action commits, and the step is written before anything can stop it.

Reports describe unexpected hard braking and vehicle immobilizations initiated by the Cruise autonomous driving system. The failing mechanism was the vehicle control/behavioral response that produced abrupt decelerations or stops, which then created roadside hazards when other drivers collided with or avoided the vehicles. Investigations by regulators sought to determine whether a software or system control defect caused the braking behavior.

Public visibilityHigh
Regulatory exposureActive
Customer impactFew customers
Financial impactUnknown
Time to disclosureDays
  1. PressCruise's robotaxis are under investigation for sudden braking and clogging traffictheverge.com
  2. PressGM recalls entire Cruise fleet for unexpected braking - WardsAutowardsauto.com
  3. PressVIDEO: Cruise self-driving taxi being investigated after stopping too quicklyabc7news.com
  4. PressUS opens probe of Cruise robotaxi braking, clogging trafficcbs8.com
  5. Reader-SubmittedCruise Taxis' Sudden Braking Allegedly Put People at Riskincidentdatabase.ai
Permalinkhttps://failureindex.ai/failures/cruise-robotaxis-investigated-sudden-braking-led
CitationAI Failure Index. "Cruise robotaxis investigated after sudden braking led to rear-end collisions" (FI-0412). Realm Labs. https://failureindex.ai/failures/cruise-robotaxis-investigated-sudden-braking-led (indexed Jun 10, 2026).
Share cardA branded image of this record for posts and slides.

Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0412. Full dataset at /data.

Note from Realm Labs, the Index steward

How Realm fits

Controls for this failure mode
  • Prism
  • OmniGuard
  • AgentRealm

This entry sits in the index's predictive wing: a system that scores, ranks, perceives, or steers rather than generates. Realm's runtime layer is built for the generative and agentic systems now moving into these same decision seats, where it watches a model's internal state and holds an unsupported claim or an unchecked action before it commits. The control gap on this record, an automated decision that reached people with no runtime check in front of it, is the same gap. The index keeps predictive failures on the record because the pattern carries straight into the systems shipping today.