A record, kept in public
The public record of robot and autonomous-system incidents in the United States.
Why this exists
Robots have left the lab. Driverless cars carry paying passengers, delivery robots share sidewalks, drones fly over neighborhoods, and humanoids are starting work in factories. When one of these systems hurts someone or fails in public, the facts end up scattered: a federal docket, a state filing, a lawsuit, a local news story that disappears behind a paywall.
Robo Incidents puts each incident on one page, in the same structure, with its sources. The aim is a record that an engineer, a journalist, a regulator, an insurer or a resident can rely on and cite.
What it is not
It is not a campaign for or against robots, and it is not a safety ranking. Being named in a record means a system was involved in an event, not that anyone was at fault. The record currently holds 62 incidents; it does not claim to hold all of them. The methodology explains what is included and how to read the numbers.
How it is kept
New incidents are found by a daily research process that checks official data sources and news coverage, and byreader reports. Each record is written from sources that were opened and read, checked against the site's rules, and published with its citations. Records are updated as investigations and lawsuits conclude.
Editor
The record is edited by Pradeep Ranwa, who works with robot software and hardware and also edits thePhysical AI Handbook.
Privacy
The site uses Google Analytics to count visits and see which records are read. It sets cookies for that purpose. The site has no accounts, no advertising and no comment system, and it does not sell or share visitor data.
Contact
Corrections, replies from companies or people involved, and tips: pradeepranwa96@gmail.com.