Skip to Content
logologo
AI Incident Database
Open TwitterOpen RSS FeedOpen FacebookOpen LinkedInOpen GitHub
Open Menu
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse

Incident 293: Cruise’s Self-Driving Car Involved in a Multiple-Injury Collision at an San Francisco Intersection

Description: A Cruise autonomous vehicle was involved in a crash at an intersection in San Francisco when making a left turn in front of a Toyota Prius traveling in an opposite direction, which caused occupants in both cars to sustain injuries.

Tools

New ReportNew ReportNew ResponseNew ResponseDiscoverDiscoverView HistoryView History

Entities

View all entities
Alleged: Cruise developed and deployed an AI system, which harmed Cruise passengers and Toyota Prius passengers.

Incident Stats

Incident ID
293
Report Count
7
Incident Date
2022-06-03
Editors
Khoa Lam
Applied Taxonomies
GMF, MIT

MIT Taxonomy Classifications

Machine-Classified
Taxonomy Details

Risk Subdomain

A further 23 subdomains create an accessible and understandable classification of hazards and harms associated with AI
 

7.3. Lack of capability or robustness

Risk Domain

The Domain Taxonomy of AI Risks classifies risks into seven AI risk domains: (1) Discrimination & toxicity, (2) Privacy & security, (3) Misinformation, (4) Malicious actors & misuse, (5) Human-computer interaction, (6) Socioeconomic & environmental harms, and (7) AI system safety, failures & limitations.
 
  1. AI system safety, failures, and limitations

Entity

Which, if any, entity is presented as the main cause of the risk
 

AI

Timing

The stage in the AI lifecycle at which the risk is presented as occurring
 

Post-deployment

Intent

Whether the risk is presented as occurring as an expected or unexpected outcome from pursuing a goal
 

Unintentional

Incident Reports

Reports Timeline

Incident OccurrenceReport of a Traffic Collision Involving an Autonomous Vehicle+2
GM's Cruise Self-Driving Car Crash Injured Multiple People
+2
Part 573 Safety Recall Report
Report of a Traffic Collision Involving an Autonomous Vehicle

Report of a Traffic Collision Involving an Autonomous Vehicle

dmv.ca.gov

GM's Cruise Self-Driving Car Crash Injured Multiple People

GM's Cruise Self-Driving Car Crash Injured Multiple People

insideevs.com

Cruise self-driving crash in San Francisco resulted in injuries; NHTSA investigating

Cruise self-driving crash in San Francisco resulted in injuries; NHTSA investigating

autonews.com

U.S. agency probing self-driving Cruise car crash in California

U.S. agency probing self-driving Cruise car crash in California

reuters.com

Part 573 Safety Recall Report

Part 573 Safety Recall Report

static.nhtsa.gov

Cruise recalls its robotaxis after passenger injured in crash

Cruise recalls its robotaxis after passenger injured in crash

cnn.com

GM's Cruise Recalls Self-Driving Software Involved in June Crash

GM's Cruise Recalls Self-Driving Software Involved in June Crash

wired.com

Report of a Traffic Collision Involving an Autonomous Vehicle
dmv.ca.gov · 2022

A Cruise autonomous vehicle ("Cruise AV") operating in driverless autonomous mode, was traveling eastbound on Geary Boulevard toward the intersection with Spruce Street. As it approached the intersection, the Cruise AV entered the left hand…

GM's Cruise Self-Driving Car Crash Injured Multiple People
insideevs.com · 2022

On June 3, 2022, in San Francisco, California, a Cruise self-driving vehicle that was driving itself autonomously was involved in an accident with a Toyota Prius. People in both cars sustained injuries as a result of the crash.

According to…

Cruise self-driving crash in San Francisco resulted in injuries; NHTSA investigating
autonews.com · 2022

One day after California regulators awarded Cruise a milestone permit in its efforts to commercialize autonomous-driving technology, one of the company's vehicles was involved in a crash that resulted in multiple injuries.

The crash occurre…

U.S. agency probing self-driving Cruise car crash in California
reuters.com · 2022

WASHINGTON, July 7 (Reuters) - The National Highway Traffic Safety Administration has opened a special investigation into a recent crash of a Cruise self-driving vehicle in California that resulted in minor injuries, the agency said on Thur…

Part 573 Safety Recall Report
static.nhtsa.gov · 2022

Description of the Defect: In a rare circumstance described below, a safety feature in the prior version of the subject ADS, known as the reflexive planner, caused the AV to hard brake while performing an unprotected left turn (“UPL”) when …

Cruise recalls its robotaxis after passenger injured in crash
cnn.com · 2022

Washington, DC (CNN Business) — This week Cruise, which counts General Motors as its largest shareholder, became the first robotaxi operator to recall its vehicles, following a June crash involving “major” damage and minor passenger injurie…

GM's Cruise Recalls Self-Driving Software Involved in June Crash
wired.com · 2022

AUTONOMOUS DRIVING COMPANY Cruise and US regulators said today that the General Motors subsidiary had recalled software deployed on 80 vehicles after two people were injured in a June crash involving a Cruise car operating autonomously in S…

Variants

A "variant" is an incident that shares the same causative factors, produces similar harms, and involves the same intelligent systems as a known AI incident. Rather than index variants as entirely separate incidents, we list variations of incidents under the first similar incident submitted to the database. Unlike other submission types to the incident database, variants are not required to have reporting in evidence external to the Incident Database. Learn more from the research paper.

Similar Incidents

By textual similarity

Did our AI mess up? Flag the unrelated incidents

A Collection of Tesla Autopilot-Involved Crashes

A Collection of Tesla Autopilot-Involved Crashes

Jun 2016 · 22 reports
California Regulator Suspended Pony.ai's Driverless Testing Permit Following a Non-Fatal Collision

California Regulator Suspended Pony.ai's Driverless Testing Permit Following a Non-Fatal Collision

Oct 2021 · 10 reports
Google admits its self driving car got it wrong: Bus crash was caused by software

Google admits its self driving car got it wrong: Bus crash was caused by software

Sep 2016 · 28 reports
Previous IncidentNext Incident

Similar Incidents

By textual similarity

Did our AI mess up? Flag the unrelated incidents

A Collection of Tesla Autopilot-Involved Crashes

A Collection of Tesla Autopilot-Involved Crashes

Jun 2016 · 22 reports
California Regulator Suspended Pony.ai's Driverless Testing Permit Following a Non-Fatal Collision

California Regulator Suspended Pony.ai's Driverless Testing Permit Following a Non-Fatal Collision

Oct 2021 · 10 reports
Google admits its self driving car got it wrong: Bus crash was caused by software

Google admits its self driving car got it wrong: Bus crash was caused by software

Sep 2016 · 28 reports

Research

  • Defining an “AI Incident”
  • Defining an “AI Incident Response”
  • Database Roadmap
  • Related Work
  • Download Complete Database

Project and Community

  • About
  • Contact and Follow
  • Apps and Summaries
  • Editor’s Guide

Incidents

  • All Incidents in List Form
  • Flagged Incidents
  • Submission Queue
  • Classifications View
  • Taxonomies

2023 - AI Incident Database

  • Terms of use
  • Privacy Policy
  • Open twitterOpen githubOpen rssOpen facebookOpen linkedin
  • 30ebe76