{ "name": "Robo Incidents dataset", "description": "A sourced, neutral record of incidents involving robotaxis, delivery robots, drones, industrial robots and other physical AI systems in the United States.", "homepage": "https://roboincidents.com/data/", "methodology": "https://roboincidents.com/methodology/", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "attribution": "Robo Incidents (https://roboincidents.com)", "generated": "2026-11-13T22:36:22.799Z", "last_record_change": "2026-11-13", "count": 62, "incidents": [ { "id": "2026-08-07-waymo-dallas-maple-avenue-pedestrian-fatality", "url": "https://roboincidents.com/incidents/2026-08-07-waymo-dallas-maple-avenue-pedestrian-fatality/", "title": "Pedestrian hit by SUV is thrown into Waymo robotaxi and dies in Dallas", "summary": "A pedestrian struck by a human-driven SUV on Maple Avenue in Dallas on August 7, 2026, was thrown into an unoccupied Waymo robotaxi in the opposite lanes and later died.", "date": "2026-08-07", "date_precision": "day", "city": "Dallas", "state": "TX", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Waymo LLC", "manufacturer": "Jaguar (vehicle), Waymo (automated driving system)", "system": "Unoccupied Waymo Jaguar I-Pace robotaxi operating in autonomous mode", "companies": [ "Waymo" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "under-investigation", "status_name": "Under investigation", "agencies": [ "Dallas Police Department" ], "official_records": [], "outcomes": [ "Dallas police investigated the crash; local reports on August 10, 2026, described the investigation as ongoing and reported no charges.", "Waymo reported the crash to NHTSA under Standing General Order 2021-01 as a fatality." ], "key_facts": [ "At about 11:30 p.m. on Friday, August 7, 2026, an SUV struck a pedestrian crossing Maple Avenue in Dallas outside a crosswalk, according to police.", "Police said the impact threw the man into the opposite lanes, where he hit an unoccupied Waymo robotaxi.", "Waymo's report to NHTSA says its vehicle was already slowing to yield to the pedestrian and that he contacted its rear left side after hitting the ground.", "The pedestrian was taken to a hospital, where he died.", "The SUV driver stopped and cooperated with police, FOX 4 reported." ], "tags": [ "robotaxi", "pedestrian", "multi-vehicle", "night", "secondary-impact" ], "sources": [ { "title": "Dallas pedestrian dies after being struck by SUV, thrown into Waymo", "publisher": "FOX 4 Dallas-Fort Worth", "url": "https://www.fox4news.com/news/pedestrian-struck-2-vehicles-including-waymo", "date": "2026-08-08" }, { "title": "Dallas pedestrian killed after being hit by SUV, thrown into Waymo", "publisher": "NBC 5 Dallas-Fort Worth", "url": "https://www.nbcdfw.com/news/local/pedestrian-killed-suv-crash-waymo-dallas/4060058/", "date": "2026-08-08" }, { "title": "Standing General Order 2021-01 Incident Reports, ADS (CSV data file; Waymo report 30270-16196)", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/ffdd/sgo-2021-01/SGO-2021-01_Incident_Reports_ADS.csv", "date": null }, { "title": "Waymo involved in a fatal accident in Dallas (not at fault): Everything we know so far", "publisher": "EVwire", "url": "https://evwire.com/p/waymo-fatal-accident-dallas-pedestrian-everything-we-know", "date": "2026-08-11" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2026-04-09-wybotics-wybot-robotic-pool-vacuum-recall-battery-fires", "url": "https://roboincidents.com/incidents/2026-04-09-wybotics-wybot-robotic-pool-vacuum-recall-battery-fires/", "title": "Wybot robotic pool vacuums recalled after ten overheating and fire reports", "summary": "Wybotics recalled about 5,000 Wybot robotic pool vacuums on April 9, 2026 after ten reports of the units overheating or catching fire, nine of which caused property damage.", "date": "2026-04-09", "date_precision": "day", "city": "", "state": "", "country": "US", "category": "consumer-robots", "category_name": "Consumer robots", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Consumer owners", "manufacturer": "Wybotics Co. Ltd. (Tianjin, China); imported by Wybotics Inc. (Arcadia, California)", "system": "Wybot Osprey 700 Max and S1 battery-powered robotic pool vacuums", "companies": [ "Wybotics" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "CPSC" ], "official_records": [], "outcomes": [ "On April 9, 2026, the U.S. Consumer Product Safety Commission announced a recall of about 5,000 Wybot Osprey 700 Max and S1 robotic pool vacuums (recall number 26-372).", "Wybotics offered owners a free replacement WYBOT C2 robotic pool vacuum and a prepaid return label." ], "key_facts": [ "About 5,000 Wybot Osprey 700 Max and S1 robotic pool vacuums were recalled in the United States on April 9, 2026 for burn and fire hazards.", "Wybotics had received ten reports of the pool vacuums overheating or catching fire, both while charging and while not charging.", "Nine of the ten reports involved property damage; no injuries were reported.", "The Consumer Product Safety Commission said the lithium-ion battery in the recalled units can overheat." ], "tags": [ "recall", "pool-robot", "lithium-ion", "fire", "cpsc" ], "sources": [ { "title": "Wybotics Recalls Robotic Pool Vacuums Due to Burn and Fire Hazards", "publisher": "U.S. Consumer Product Safety Commission", "url": "https://www.cpsc.gov/Recalls/2026/Wybotics-Recalls-Robotic-Pool-Vacuums-Due-to-Burn-and-Fire-Hazards", "date": "2026-04-09" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2026-03-22-serve-robotics-chicago-west-town-bus-shelter", "url": "https://roboincidents.com/incidents/2026-03-22-serve-robotics-chicago-west-town-bus-shelter/", "title": "Serve Robotics delivery robot shatters CTA bus shelter glass in Chicago", "summary": "A Serve Robotics delivery robot drove through a glass panel of a CTA bus shelter at Grand and Racine in Chicago's West Town. No one was hurt and Serve paid for the repair.", "date": "2026-03-22", "date_precision": "day", "city": "Chicago", "state": "IL", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Serve Robotics", "manufacturer": "Serve Robotics", "system": "Serve Robotics autonomous sidewalk delivery robot", "companies": [ "Serve Robotics" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Chicago Department of Business Affairs and Consumer Protection", "Chicago Department of Transportation" ], "official_records": [], "outcomes": [ "Serve Robotics cleaned up the glass, said it was reviewing the crash and paid for the shelter repair; the glass was replaced by March 25, 2026.", "A Coco Robotics robot broke the glass of a second bus shelter, at North Avenue and Larrabee Street, on March 24, 2026.", "Chicago added a 311 category for complaints about personal delivery devices.", "Serve placed an apology advertisement on the repaired shelter in April 2026." ], "key_facts": [ "A Serve Robotics delivery robot crashed through a glass panel of a CTA bus shelter at Grand and Racine avenues in Chicago's West Town in March 2026.", "No one was injured; broken glass was scattered across the sidewalk.", "Serve Robotics said its robot made impact with the glass, called such events extremely rare and said it would pay for the repair.", "Within days of the Serve crash, a Coco Robotics robot broke the glass of another Chicago bus shelter in Old Town.", "Chicago officials said both companies were responsible for repair costs under the city's delivery robot pilot program." ], "tags": [ "serve-robotics", "bus-shelter", "sidewalk", "pilot-program", "coco-robotics" ], "sources": [ { "title": "Video shows delivery robot crash into CTA bus shelter in West Town", "publisher": "ABC7 Chicago (WLS)", "url": "https://abc7chicago.com/post/video-shows-serve-robotics-delivery-robot-crash-cta-bus-shelter-racine-outside-centre-construction-group-west-town/18763333/", "date": "2026-03-25" }, { "title": "Delivery robot goes viral after crashing into West Town bus shelter, shattering glass onto sidewalk", "publisher": "CBS Chicago", "url": "https://www.cbsnews.com/chicago/news/delivery-robot-crashes-into-west-town-bus-shelter", "date": "2026-03-23" }, { "title": "Food Delivery Robots Shatter Bus Shelters in Chicago", "publisher": "Chicago Tribune (via Government Technology)", "url": "https://www.govtech.com/transportation/food-delivery-robots-shatter-bus-shelters-in-chicago", "date": "2026-03-26" }, { "title": "Delivery robots keep crashing into bus shelters", "publisher": "Popular Science", "url": "https://www.popsci.com/technology/delivery-robots-crash-bus-shelters", "date": "2026-03-26" }, { "title": "Delivery robot 'apologizes' after viral CTA bus stop crash: 'Nasir is sorry'", "publisher": "ABC7 Chicago (WLS)", "url": "https://abc7chicago.com/post/chicago-bus-shelter-ad-apologizes-video-shows-food-delivery-robots-serve-robotics-crash-grand-racine-stop/18885510/", "date": "2026-04-14" }, { "title": "Delivery robot goes viral after shattering West Town bus shelter glass", "publisher": "NBC Chicago", "url": "https://www.nbcchicago.com/news/local/delivery-robot-goes-viral-after-shattering-west-town-bus-shelter-glass/3913225/?amp=1", "date": "2026-03-24" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2026-02-04-amazon-prime-air-mk30-richardson-apartment-building", "url": "https://roboincidents.com/incidents/2026-02-04-amazon-prime-air-mk30-richardson-apartment-building/", "title": "Amazon MK30 delivery drone hits apartment building in Richardson, Texas", "summary": "An Amazon Prime Air MK30 struck the outside of an apartment building in Richardson, Texas, during a delivery and fell onto a walkway. No one was hurt; damage was minor.", "date": "2026-02-04", "date_precision": "day", "city": "Richardson", "state": "TX", "country": "US", "category": "drones", "category_name": "Drones", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Amazon Prime Air", "manufacturer": "Amazon", "system": "Amazon Prime Air MK30 autonomous delivery drone", "companies": [ "Amazon" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "under-investigation", "status_name": "Under investigation", "agencies": [ "FAA" ], "official_records": [], "outcomes": [ "Amazon apologized, said it was investigating the cause and arranged repairs to the building.", "CBS News reported that the FAA was investigating." ], "key_facts": [ "An Amazon Prime Air MK30 delivery drone hit an apartment building on Routh Creek Parkway in Richardson, Texas, at about 5 p.m. on February 4, 2026.", "The drone fell onto a walkway beside the building with its propellers still turning; no one was injured.", "Richardson firefighters checked the drone and said it did not catch fire, although a witness reported smoke.", "Officials described the damage to the building as minimal, and Amazon said it was arranging repairs.", "Amazon had started drone deliveries in Richardson in December 2025, about two months earlier." ], "tags": [ "amazon-prime-air", "mk30", "building-strike", "residential-delivery" ], "sources": [ { "title": "VIDEO: Amazon delivery drone crashes in North Texas", "publisher": "FOX 4 News Dallas-Fort Worth", "url": "https://www.fox4news.com/news/video-amazon-delivery-drone-crashes-texas", "date": "2026-02-05" }, { "title": "Amazon Drone Crashes Into Texas Apartment Building", "publisher": "AVweb", "url": "https://avweb.com/flight-safety/accidents-ntsb/amazon-drone-crashes-into-texas-apartment", "date": "2026-02-09" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2026-01-23-waymo-santa-monica-school-zone-child-struck", "url": "https://roboincidents.com/incidents/2026-01-23-waymo-santa-monica-school-zone-child-struck/", "title": "Waymo robotaxi strikes child near Santa Monica elementary school", "summary": "A driverless Waymo struck a 9-year-old who crossed mid-block from between stopped cars near a Santa Monica elementary school on January 23, 2026. NHTSA and the NTSB opened probes.", "date": "2026-01-23", "date_precision": "day", "city": "Santa Monica", "state": "CA", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Waymo LLC", "manufacturer": "Jaguar (vehicle), Waymo (automated driving system)", "system": "2024 Jaguar I-Pace with Waymo's 5th Generation Automated Driving System, unoccupied", "companies": [ "Waymo" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "under-investigation", "status_name": "Under investigation", "agencies": [ "NTSB", "NHTSA", "Santa Monica Police Department" ], "official_records": [], "outcomes": [ "NHTSA opened Preliminary Evaluation PE26001 on January 28, 2026, to examine whether the vehicle exercised appropriate caution near the school.", "The NTSB opened investigation HWY26FH008 and released preliminary information on March 3, 2026; no probable cause has been published." ], "key_facts": [ "The collision happened at about 8:30 a.m. on January 23, 2026, on 24th Street near Pearl Street in Santa Monica, during school drop-off.", "The NTSB said a 9-year-old student got out of a car in a queue and crossed mid-block at a rapid pace between two stopped vehicles.", "The unoccupied Waymo was traveling 17 mph when it braked, and Waymo said it slowed to about 6 mph before contact.", "The child reported minor injuries and did not need medical transport, according to the NTSB.", "NHTSA opened a preliminary evaluation covering an estimated 3,067 Waymo vehicles." ], "tags": [ "robotaxi", "child-pedestrian", "school-zone", "nhtsa-investigation", "ntsb" ], "sources": [ { "title": "Automated Driving System-Equipped Vehicle Collision with Student Pedestrian", "publisher": "NTSB", "url": "https://www.ntsb.gov/investigations/Pages/HWY26FH008.aspx", "date": "2026-03-03" }, { "title": "ODI Resume: Investigation PE26001, Waymo AV striking a child in the area of a school", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/inv/2026/INOA-PE26001-10005.pdf", "date": "2026-01-28" }, { "title": "NHTSA investigating report of Waymo striking child at low speed near Santa Monica school", "publisher": "NBC Los Angeles", "url": "https://www.nbclosangeles.com/news/local/waymo-strikes-child-santa-monica-nhtsa/3838160/", "date": "2026-01-29" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2026-01-15-coco-robotics-miami-brightline-train-strike", "url": "https://roboincidents.com/incidents/2026-01-15-coco-robotics-miami-brightline-train-strike/", "title": "Brightline train destroys Coco delivery robot stalled on tracks in Miami", "summary": "A Coco delivery robot stopped on railroad tracks in Miami and was hit and destroyed by a Brightline passenger train. No one was hurt. Coco blamed a rare hardware failure.", "date": "2026-01-15", "date_precision": "day", "city": "Miami", "state": "FL", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Coco Robotics", "manufacturer": "Coco Robotics", "system": "Coco sidewalk delivery robot used for Uber Eats orders", "companies": [ "Coco Robotics" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Coco Robotics attributed the stall to a rare hardware failure.", "On January 28, 2026, U.S. Rep. Jimmy Patronis wrote to the NTSB chair asking whether the collision triggered reporting requirements and what the agency planned to do." ], "key_facts": [ "A Brightline passenger train struck and destroyed a Coco delivery robot that had stopped on the tracks in Miami on the evening of January 15, 2026.", "A witness said the robot had been stuck on the tracks for about 15 minutes before the train arrived.", "No injuries were reported.", "Coco Robotics said the robot suffered a rare hardware failure and was not carrying a delivery at the time.", "A member of Congress asked the NTSB on January 28, 2026, whether it would look into the collision." ], "tags": [ "coco-robotics", "railroad-crossing", "brightline", "hardware-failure", "uber-eats" ], "sources": [ { "title": "Caught on camera: Brightline train crushes delivery robot stuck on tracks in Miami", "publisher": "FOX 35 Orlando", "url": "https://www.fox35orlando.com/news/caught-camera-brightline-train-crushes-delivery-robot-stuck-tracks-miami", "date": "2026-01-16" }, { "title": "Delivery Robot Gets Stuck on Train Tracks, Gets Obliterated by Locomotive", "publisher": "Futurism", "url": "https://futurism.com/robots-and-machines/delivery-robot-obliterated-by-train", "date": "2026-01-28" }, { "title": "Letter from Rep. Jimmy Patronis to NTSB Chairwoman Jennifer Homendy", "publisher": "Office of U.S. Rep. Jimmy Patronis", "url": "https://patronis.house.gov/sites/evo-subsites/patronis.house.gov/files/evo-media-document/ntsb-letter-61.pdf", "date": "2026-01-28" }, { "title": "Robot de reparto es impactado por tren de Brightline tras quedar atascado en las vías en Fort Lauderdale", "publisher": "Local 10 (WPLG)", "url": "https://www.local10.com/espanol/2026/01/17/robot-de-reparto-es-impactado-por-tren-de-brightline-tras-quedar-atascado-en-las-vias-en-fort-lauderdale/", "date": "2026-01-17" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-12-06-tesla-optimus-miami-autonomy-visualized-demo-fall", "url": "https://roboincidents.com/incidents/2025-12-06-tesla-optimus-miami-autonomy-visualized-demo-fall/", "title": "Tesla Optimus humanoid falls backward during public demo in Miami", "summary": "A Tesla Optimus robot handing out water bottles at a Tesla event in Miami knocked bottles over and fell backward on December 6, 2025. No injuries were reported.", "date": "2025-12-06", "date_precision": "day", "city": "Miami", "state": "FL", "country": "US", "category": "humanoid-robots", "category_name": "Humanoid robots", "severity": "disruption", "severity_name": "Disruption", "fatalities": 0, "injuries": 0, "operator": "Tesla", "manufacturer": "Tesla", "system": "Tesla Optimus humanoid robot", "companies": [ "Tesla" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Video of the fall was posted to Reddit and reported by Electrek on December 7, 2025.", "Tesla did not respond to questions from Gizmodo and Fortune about whether a person was remotely operating the robot." ], "key_facts": [ "A Tesla Optimus humanoid robot fell backward while handing out water bottles at a Tesla event in Miami called Autonomy Visualized in early December 2025.", "Video shows the robot knocking bottles over, raising both hands toward its head, then going limp and falling backward.", "The hand motion led commentators to speculate that a remote operator had removed a virtual-reality headset; Tesla has not confirmed that the robot was teleoperated.", "No injuries were reported in coverage of the Miami fall." ], "tags": [ "public-demo", "fall", "teleoperation-question", "optimus" ], "sources": [ { "title": "Tesla Optimus robot takes a suspicious tumble in new demo", "publisher": "Electrek", "url": "https://electrek.co/2025/12/07/tesla-optimus-robot-takes-suspicious-tumble-in-new-demo/", "date": "2025-12-07" }, { "title": "Elon Musk's Optimus Robot Collapses in a Hilariously Suspicious Way", "publisher": "Gizmodo", "url": "https://gizmodo.com/elon-musks-optimus-robot-collapses-in-a-hilariously-suspicious-way-2000696760", "date": "2025-12-08" }, { "title": "Tesla promotes Optimus as its next big breakthrough, but one robot's collapse has sparked doubts about their current level of autonomy", "publisher": "Fortune", "url": "https://fortune.com/2025/12/09/tesla-optimus-robots-fall-autonomous-demonstration-elon-musk/", "date": "2025-12-09" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-11-21-figure-ai-lawsuit-alleges-humanoid-struck-refrigerator-near-worker", "url": "https://roboincidents.com/incidents/2025-11-21-figure-ai-lawsuit-alleges-humanoid-struck-refrigerator-near-worker/", "title": "Lawsuit alleges Figure AI humanoid punched refrigerator beside a worker", "summary": "A former Figure AI safety engineer's November 2025 lawsuit alleges an F.02 humanoid malfunctioned and punched a refrigerator beside an employee. Figure denies the allegation.", "date": "2025-11-21", "date_precision": "day", "city": "", "state": "CA", "country": "US", "category": "humanoid-robots", "category_name": "Humanoid robots", "severity": "near-miss", "severity_name": "Near miss", "fatalities": 0, "injuries": 0, "operator": "Figure AI", "manufacturer": "Figure AI", "system": "Figure 02 (F.02) general-purpose humanoid robot", "companies": [ "Figure AI" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "alleged", "status_name": "Alleged", "agencies": [], "official_records": [], "outcomes": [ "On November 21, 2025, Figure AI's former head of product safety filed a wrongful-termination and retaliation suit in the U.S. District Court for the Northern District of California (case 5:25-cv-10094).", "A Figure spokesperson told CNBC in November 2025 that the engineer was terminated for poor performance and that his allegations were falsehoods the company would discredit in court.", "On January 16, 2026, Figure filed an answer denying the refrigerator allegation and filed counterclaims against the engineer, including trade secret misappropriation.", "On August 10, 2026, the court approved the parties' stipulation to use private alternative dispute resolution; the docket showed the case still open in November 2026." ], "key_facts": [ "A lawsuit filed on November 21, 2025 alleges that a Figure 02 humanoid robot malfunctioned and punched a refrigerator while an employee stood next to it, narrowly missing the employee.", "The complaint says the robot left a quarter-inch-deep gash in the refrigerator's stainless-steel door; it does not say when or where the event took place.", "The same complaint alleges that an F.02 impact test on July 28, 2025 produced forces the engineer estimated at more than twice what is needed to fracture an adult human skull.", "Figure AI denied the refrigerator allegation in its January 16, 2026 court answer and has said the engineer was dismissed for poor performance.", "No injury to any person is alleged in connection with the refrigerator event or the impact test." ], "tags": [ "lawsuit", "whistleblower", "near-miss", "workplace", "figure-02" ], "sources": [ { "title": "Gruendel v. Figure AI, Inc., 5:25-cv-10094 – CourtListener.com", "publisher": "CourtListener (Free Law Project)", "url": "https://www.courtlistener.com/docket/71948915/gruendel-v-figure-ai-inc/", "date": "2025-11-21" }, { "title": "Complaint, Gruendel v. Figure AI, Inc., No. 5:25-cv-10094 (N.D. Cal.), Document 1", "publisher": "U.S. District Court for the Northern District of California (via CourtListener RECAP)", "url": "https://storage.courtlistener.com/recap/gov.uscourts.cand.460223/gov.uscourts.cand.460223.1.0.pdf", "date": "2025-11-21" }, { "title": "Defendant Figure AI's Answer to Complaint, Gruendel v. Figure AI, Inc., No. 5:25-cv-10094 (N.D. Cal.), Document 21", "publisher": "U.S. District Court for the Northern District of California (via CourtListener RECAP)", "url": "https://storage.courtlistener.com/recap/gov.uscourts.cand.460223/gov.uscourts.cand.460223.21.0.pdf", "date": "2026-01-16" }, { "title": "Figure AI sued by whistleblower who warned that startup's robots could 'fracture a human skull'", "publisher": "CNBC", "url": "https://www.cnbc.com/2025/11/21/figure-ai-sued.html", "date": "2025-11-21" }, { "title": "Meet Figure AI: The company behind the humanoid robot hosted by Melania Trump", "publisher": "CNBC", "url": "https://www.cnbc.com/2026/03/26/figure-ai-the-robotics-company-hosted-by-melania-trump.html", "date": "2026-03-26" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-11-18-amazon-prime-air-mk30-waco-internet-cable", "url": "https://roboincidents.com/incidents/2025-11-18-amazon-prime-air-mk30-waco-internet-cable/", "title": "Amazon MK30 delivery drone snags overhead internet cable in Waco", "summary": "An Amazon MK30 drone clipped an overhead internet cable while climbing away from a backyard delivery in Waco, Texas, then landed itself. The FAA opened an investigation.", "date": "2025-11-18", "date_precision": "day", "city": "Waco", "state": "TX", "country": "US", "category": "drones", "category_name": "Drones", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Amazon Prime Air", "manufacturer": "Amazon", "system": "Amazon Prime Air MK30 autonomous delivery drone (N139PA)", "companies": [ "Amazon" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "FAA" ], "official_records": [], "outcomes": [ "Amazon reported the event to the FAA, paid for the cable repair and apologized to the customer.", "The FAA said it was investigating; the NTSB said the event did not meet its threshold for an investigation." ], "key_facts": [ "An Amazon Prime Air MK30 delivery drone struck an overhead internet cable in Waco, Texas, at about 12:45 p.m. on November 18, 2025.", "The drone had just completed a delivery to a customer's backyard and was climbing away when it clipped the cable.", "The drone then performed what Amazon calls a safe contingent landing; no injuries were reported.", "The FAA opened an investigation, while the NTSB declined to investigate.", "Amazon said it paid to repair the cable and that there was no widespread internet outage." ], "tags": [ "amazon-prime-air", "mk30", "wire-strike", "residential-delivery" ], "sources": [ { "title": "Amazon investigated by FAA after delivery drone strikes internet cable", "publisher": "Fox Business", "url": "https://www.foxbusiness.com/retail/amazon-investigated-faa-after-delivery-drone-strikes-internet-cable", "date": "2025-11-26" }, { "title": "NTSB Will Not Investigate Amazon Drone Incident in Texas", "publisher": "FLYING Magazine", "url": "https://www.flyingmag.com/ntsb-amazon-drone-delivery-incident-texas/", "date": "2025-11-26" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-10-27-waymo-san-francisco-mission-store-cat-killed", "url": "https://roboincidents.com/incidents/2025-10-27-waymo-san-francisco-mission-store-cat-killed/", "title": "Waymo robotaxi kills neighborhood store cat in San Francisco", "summary": "A Waymo robotaxi ran over and killed KitKat, a well-known store cat, outside a market on 16th Street in San Francisco's Mission District late on October 27, 2025.", "date": "2025-10-27", "date_precision": "day", "city": "San Francisco", "state": "CA", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Waymo LLC", "manufacturer": "Waymo (automated driving system)", "system": "Driverless Waymo robotaxi stopped for a passenger pickup", "companies": [ "Waymo" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Waymo confirmed its vehicle was involved, expressed sympathy and said it would donate to a local animal rights organization.", "Neighbors built a sidewalk memorial outside the market." ], "key_facts": [ "A Waymo robotaxi struck and killed a store cat named KitKat outside Randa's Market on 16th Street in San Francisco late on Monday, October 27, 2025.", "Waymo said the vehicle had stopped to pick up passengers and that the cat darted under it as it was pulling away.", "The cat was taken to a veterinarian but did not survive, the store's owner said.", "Waymo said it would make a donation to a local animal rights organization in the cat's honor.", "No people were injured." ], "tags": [ "robotaxi", "animal", "pickup", "community-reaction" ], "sources": [ { "title": "San Francisco's Mission District mourns beloved store cat killed by Waymo", "publisher": "CBS San Francisco", "url": "https://www.cbsnews.com/sanfrancisco/news/sf-mission-district-mourns-store-cat-killed-by-waymo", "date": "2025-10-30" }, { "title": "SF bodega cat struck and killed by Waymo, store owner says", "publisher": "KTVU FOX 2", "url": "https://ktvu.com/news/sf-bodega-cat-struck-killed-waymo-store-owner-says", "date": "2025-10-30" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-10-22-avride-uber-eats-jersey-city-cyclist-collision", "url": "https://roboincidents.com/incidents/2025-10-22-avride-uber-eats-jersey-city-cyclist-collision/", "title": "Cyclist injured in collision with Avride delivery robot in Jersey City", "summary": "A cyclist says an Avride delivery robot working for Uber Eats moved into a Jersey City bike lane and caused a crash that broke his collarbone. He is suing both companies.", "date": "2025-10-22", "date_precision": "day", "city": "Jersey City", "state": "NJ", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "serious-injury", "severity_name": "Serious injury", "fatalities": 0, "injuries": 1, "operator": "Avride (delivering for Uber Eats)", "manufacturer": "Avride", "system": "Avride four-wheeled autonomous sidewalk delivery robot", "companies": [ "Avride", "Uber" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "alleged", "status_name": "Alleged", "agencies": [], "official_records": [], "outcomes": [ "The cyclist retained a lawyer and announced a lawsuit against Uber and Avride in May 2026.", "Avride said it was aware of the October 2025 collision but would not comment on an active legal matter." ], "key_facts": [ "A cyclist says an Avride delivery robot entered the bike lane on Varick Street in Jersey City at about 5 p.m. on October 22, 2025, causing him to crash.", "The cyclist said he was thrown over his handlebars and suffered a concussion and a broken collarbone.", "A witness said the robot started to continue on its way after the crash and that she blocked it and photographed it.", "Avride acknowledged an October 2025 collision between a cyclist and one of its robots but declined to discuss it, citing the legal case.", "The cyclist's lawyer said it appeared to be the first reported delivery robot crash in New Jersey." ], "tags": [ "avride", "uber-eats", "cyclist", "bike-lane", "lawsuit" ], "sources": [ { "title": "Bicyclist to sue after crash with robot that allegedly tried to flee", "publisher": "Newsweek", "url": "https://www.newsweek.com/bicyclist-suing-crash-delivery-robot-new-jersey-lawsuit-11952852", "date": null }, { "title": "New Jersey cyclist sues after delivery robot 'hit-and-run' leaves him with broken shoulder, head injury", "publisher": "News 12 New Jersey", "url": "https://newjersey.news12.com/new-jersey-cyclist-sues-after-delivery-robot-hit-and-run-leaves-him-with-broken-shoulder-head-injury", "date": "2026-05-11" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-10-01-amazon-prime-air-mk30-tolleson-crane-collision", "url": "https://roboincidents.com/incidents/2025-10-01-amazon-prime-air-mk30-tolleson-crane-collision/", "title": "Two Amazon Prime Air MK30 delivery drones strike crane in Tolleson", "summary": "Two Amazon MK30 delivery drones flying the same route hit the raised boom of a construction crane minutes apart in Tolleson, Arizona. One battery burned; no one was hurt.", "date": "2025-10-01", "date_precision": "day", "city": "Tolleson", "state": "AZ", "country": "US", "category": "drones", "category_name": "Drones", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Amazon Prime Air (Amazon.com Services LLC)", "manufacturer": "Amazon", "system": "Amazon Prime Air MK30 autonomous delivery drones (N579PA and N791PA) on Part 135 delivery flights", "companies": [ "Amazon" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "under-investigation", "status_name": "Under investigation", "agencies": [ "NTSB", "FAA" ], "official_records": [], "outcomes": [ "Amazon paused drone deliveries in the Phoenix area on October 2, 2025, and said flights would resume on October 3.", "Amazon said its internal review found no fault with the drones and that it added visual inspections for moving obstructions such as cranes.", "The NTSB issued a preliminary report in October 2025 describing the crane's setup and Amazon's morning obstacle scan." ], "key_facts": [ "Two Amazon Prime Air MK30 delivery drones struck the boom of a construction crane in Tolleson, Arizona, on the morning of October 1, 2025.", "The crane operator felt the first impact at about 9:49 a.m. and had stopped work to check it when a second drone hit the stationary crane, according to the NTSB's preliminary report.", "The crane was raised between about 7:30 and 8:00 a.m., after Amazon's ground crew had completed a rooftop scan for obstructions at about 6:58 a.m.", "A battery ejected from one drone caught fire on the ground; no injuries were reported.", "Amazon said its own review found no problem with the drones or the technology supporting them." ], "tags": [ "amazon-prime-air", "mk30", "crane", "obstacle-detection", "ntsb", "battery-fire" ], "sources": [ { "title": "NTSB Preliminary Report N579PA & N791PA AMAZON MK30 delivery drones", "publisher": "sUAS News (reproducing NTSB preliminary report)", "url": "https://www.suasnews.com/2025/10/ntsb-preliminary-report-n579pa-n791pa-amazon-mk30-delivery-drones/", "date": "2025-10-25" }, { "title": "Amazon delivery drones crash into crane, prompting NTSB, FAA investigation", "publisher": "Fox Business", "url": "https://www.foxbusiness.com/economy/amazon-delivery-drones-crash-crane-prompting-ntsb-faa-investigation", "date": "2025-10-03" }, { "title": "Amazon grounds drone deliveries in Arizona after crash", "publisher": "The Register", "url": "https://www.theregister.com/2025/10/02/amazon_drone_crash/", "date": "2025-10-02" }, { "title": "Amazon Resumes Drone Deliveries Days After Tolleson Crane Crash and Fire", "publisher": "DroneXL", "url": "https://dronexl.co/2025/10/03/amazon-resumes-drone-deliveries-days-after-tolleson-crane-crash-and-fire", "date": "2025-10-03" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-09-22-waymo-atlanta-stopped-school-bus-pass", "url": "https://roboincidents.com/incidents/2025-09-22-waymo-atlanta-stopped-school-bus-pass/", "title": "Waymo robotaxi drives around stopped school bus in Atlanta", "summary": "A driverless Waymo drove around a school bus stopped with red lights flashing and stop arm out in Atlanta on September 22, 2025, starting a federal probe and a 3,067-car recall.", "date": "2025-09-22", "date_precision": "day", "city": "Atlanta", "state": "GA", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "near-miss", "severity_name": "Near miss", "fatalities": 0, "injuries": 0, "operator": "Waymo LLC", "manufacturer": "Waymo (automated driving system)", "system": "Waymo robotaxi running the 5th Generation Automated Driving System with no safety operator", "companies": [ "Waymo" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "under-investigation", "status_name": "Under investigation", "agencies": [ "NHTSA" ], "official_records": [], "outcomes": [ "NHTSA opened Preliminary Evaluation PE25013 on October 17, 2025.", "Waymo deployed a software fix between November 5 and 17, 2025, and filed recall 25E084 covering 3,067 vehicles on December 10, 2025.", "Austin Independent School District reported 19 instances of Waymo vehicles not stopping for its buses in the 2025-2026 school year and asked Waymo to stop operating during school travel hours.", "On November 6, 2026, NHTSA opened Recall Query RQ26006 to assess whether the recall remedy was adequate." ], "key_facts": [ "NHTSA opened an investigation after a media report showed a Waymo vehicle passing a stopped school bus in Atlanta on September 22, 2025.", "NHTSA said the Waymo initially stopped, then drove around the front of the bus and past its extended stop arm while students were getting off.", "Waymo's recall report said a software release deployed in mid-September 2025 could cause vehicles to proceed past a stopped school bus because they judged they were blocking it.", "Waymo recalled 3,067 vehicles on December 10, 2025, and said no collisions resulted from the behavior.", "In November 2026 NHTSA said most of the school bus incidents it identified happened after the recall fix was completed, and opened a recall query." ], "tags": [ "robotaxi", "school-bus", "traffic-law", "recall", "nhtsa-investigation" ], "sources": [ { "title": "ODI Resume: Investigation PE25013, Waymo AV drives around a stopped school bus", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/inv/2025/INOA-PE25013-23069.pdf", "date": "2025-10-17" }, { "title": "Part 573 Safety Recall Report 25E084", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/rcl/2025/RCLRPT-25E084-7732.pdf", "date": "2025-12-10" }, { "title": "ODI Resume: Investigation RQ26006, Effectiveness of recall remedy for Waymo AVs passing stopped school buses", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/inv/2026/INOA-RQ26006-19477.pdf", "date": "2026-11-06" }, { "title": "Waymo recalls certain models after reports of vehicles not stopping for school buses", "publisher": "KSAT", "url": "https://www.ksat.com/news/local/2025/12/10/waymo-recalls-certain-models-due-to-possibly-not-stopping-for-school-buses-nhtsa-reports", "date": "2025-12-10" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-09-17-palermos-pizza-west-milwaukee-robotic-machine-fatality", "url": "https://roboincidents.com/incidents/2025-09-17-palermos-pizza-west-milwaukee-robotic-machine-fatality/", "title": "Palermo's Pizza worker crushed by robotic machine in West Milwaukee", "summary": "A 45-year-old employee at the Palermo's Pizza plant in West Milwaukee, Wisconsin, was crushed by a robotic machine on September 17, 2025, the medical examiner's office said.", "date": "2025-09-17", "date_precision": "day", "city": "West Milwaukee", "state": "WI", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Palermo's Pizza", "manufacturer": "", "system": "Robotic machine at a pizza manufacturing plant (type not publicly identified)", "companies": [ "Palermo's Pizza" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "under-investigation", "status_name": "Under investigation", "agencies": [ "West Milwaukee Police Department", "OSHA", "Milwaukee County Medical Examiner's Office" ], "official_records": [], "outcomes": [ "West Milwaukee police opened an investigation and notified OSHA on the day of the death.", "Palermo's said it was investigating, cooperating with government officials and offering counseling to employees." ], "key_facts": [ "On September 17, 2025, a 45-year-old employee died at the Palermo's Pizza manufacturing plant in West Milwaukee, Wisconsin.", "The Milwaukee County Medical Examiner's Office said the worker was crushed by a robotic machine.", "Police said the incident happened at about 6:30 a.m. and that OSHA had been contacted.", "Palermo's said the accident was being fully investigated and that it was cooperating with government officials.", "The type of machine and how the worker came to be caught in it had not been made public in the reports reviewed." ], "tags": [ "food-processing", "under-investigation", "osha" ], "sources": [ { "title": "Palermo's Pizza employee death investigation at West Milwaukee facility", "publisher": "FOX6 News Milwaukee", "url": "https://www.fox6now.com/news/palermos-pizza-employee-death-investigation-west-milwaukee-facility", "date": "2025-09-17" }, { "title": "Wisconsin pizza factory worker crushed to death by robotic machine in horrific industrial accident", "publisher": "Fox News", "url": "https://www.foxnews.com/us/wisconsin-pizza-factory-worker-crushed-death-robotic-machine-horrific-industrial-accident", "date": "2025-09-18" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-09-12-serve-robotics-west-hollywood-mobility-scooter", "url": "https://roboincidents.com/incidents/2025-09-12-serve-robotics-west-hollywood-mobility-scooter/", "title": "Serve delivery robot blocks mobility scooter user in West Hollywood", "summary": "A man with cerebral palsy said a Serve Robotics robot repeatedly cut off his mobility scooter on a West Hollywood sidewalk before they made contact. He was not injured.", "date": "2025-09-12", "date_precision": "day", "city": "West Hollywood", "state": "CA", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "near-miss", "severity_name": "Near miss", "fatalities": 0, "injuries": 0, "operator": "Serve Robotics", "manufacturer": "Serve Robotics", "system": "Serve Robotics autonomous sidewalk delivery robot", "companies": [ "Serve Robotics" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Serve Robotics said it regretted the encounter and that the robot's yielding behavior had ended up blocking the man's path.", "The Los Angeles County Sheriff's Department said it was aware of the event but was not investigating because no crime had occurred." ], "key_facts": [ "In September 2025 a man with cerebral palsy riding a mobility scooter filmed a Serve Robotics delivery robot blocking his path on a West Hollywood sidewalk.", "The man said the robot cut him off when he tried to pass, braked suddenly and made contact with his scooter; he was not injured.", "Serve Robotics said a safety system meant to anticipate and yield to pedestrians instead caused the robot to block him, after which it came to a full stop.", "The Los Angeles County Sheriff's Department said it was not investigating because no crime occurred.", "Video of the encounter drew wide attention online and prompted debate about sidewalk robots and accessibility." ], "tags": [ "serve-robotics", "accessibility", "mobility-scooter", "sidewalk" ], "sources": [ { "title": "West Hollywood man with cerebral palsy voices concerns after collision with delivery robot", "publisher": "CBS Los Angeles", "url": "https://www.cbsnews.com/losangeles/news/west-hollywood-delivery-robot-crash-pedestrian-cerebral-palsy", "date": "2025-09-21" }, { "title": "Delivery robot collides with man with cerebral palsy on mobility scooter in West Hollywood", "publisher": "ABC7 Los Angeles (KABC)", "url": "https://abc7.com/post/delivery-robot-hits-man-cerebral-palsy-mobility-scooter-west-hollywood/17866465/", "date": "2025-09-22" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-07-tesla-robotaxi-austin-remote-operator-fence-collision", "url": "https://roboincidents.com/incidents/2025-07-tesla-robotaxi-austin-remote-operator-fence-collision/", "title": "Remote operator drives Tesla Robotaxi into fence in Austin", "summary": "In July 2025, weeks after Tesla's Robotaxi service began in Austin, a remote operator who took over a stalled vehicle drove it over a curb and into a metal fence, Tesla told NHTSA.", "date": "2025-07", "date_precision": "month", "city": "Austin", "state": "TX", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Tesla, Inc.", "manufacturer": "Tesla", "system": "2026 Tesla Model Y in Tesla's Robotaxi service, with an on-board safety monitor and remote teleoperator support", "companies": [ "Tesla" ], "autonomy_mode": "autonomous-with-safety-operator", "autonomy_mode_name": "Autonomous, safety operator present", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NHTSA" ], "official_records": [], "outcomes": [ "Tesla reported the crash to NHTSA under Standing General Order 2021-01 and initially withheld the narrative as confidential.", "In March 2026 Tesla filed updated reports that made its crash narratives public." ], "key_facts": [ "Tesla reported to NHTSA that in July 2025 a teleoperator took control of a stopped Robotaxi in Austin and drove it up a curb and into a metal fence.", "A safety monitor was in the vehicle and no passengers were on board, according to Tesla's report.", "NHTSA's data lists the highest injury severity for the crash as minor, without hospitalization, and a pre-crash speed of 8 mph.", "Electrek counted 17 Tesla Robotaxi crashes reported to NHTSA in Austin from July 2025 through March 2026, two of them with a remote operator in control.", "Tesla's crash narratives were redacted in NHTSA's public data until Tesla filed updated reports in March 2026." ], "tags": [ "tesla", "robotaxi", "teleoperation", "safety-monitor", "fixed-object" ], "sources": [ { "title": "Standing General Order 2021-01 Incident Reports, ADS (CSV data file; Tesla report 13781-11459)", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/ffdd/sgo-2021-01/SGO-2021-01_Incident_Reports_ADS.csv", "date": null }, { "title": "Tesla finally reveals what happened in 17 'Robotaxi' crashes", "publisher": "Electrek", "url": "https://electrek.co/2026/05/15/tesla-unredacts-robotaxi-crash-narratives-nhtsa/", "date": "2026-05-15" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2025-04-08-zoox-las-vegas-robotaxi-passenger-car-collision", "url": "https://roboincidents.com/incidents/2025-04-08-zoox-las-vegas-robotaxi-passenger-car-collision/", "title": "Zoox robotaxi collides with passenger car in Las Vegas", "summary": "An unoccupied Zoox robotaxi collided with a passenger car in Las Vegas on April 8, 2025, after mispredicting the car's movement. Zoox paused operations and recalled software.", "date": "2025-04-08", "date_precision": "day", "city": "Las Vegas", "state": "NV", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Zoox, Inc. (Amazon subsidiary)", "manufacturer": "Zoox", "system": "Purpose-built Zoox robotaxi operating autonomously with no occupants", "companies": [ "Zoox" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NHTSA" ], "official_records": [], "outcomes": [ "Zoox paused all driverless operations on April 8, 2025, and resumed fully after releasing updated software on April 16 and 17, 2025.", "On May 1, 2025, Zoox filed recall 25E-029 covering automated driving software on 270 vehicles.", "Zoox filed a further recall, 25E037, on May 22, 2025, after a separate May 8 incident in San Francisco involving an e-scooter rider." ], "key_facts": [ "On April 8, 2025, an unoccupied Zoox robotaxi operating autonomously in Las Vegas collided with a passenger car; no one was injured.", "Zoox said the car approached from a driveway and then stopped, while the robotaxi had predicted it would continue into its lane.", "Zoox told NHTSA the prediction problem occurred only at speeds above 40 mph.", "Zoox paused driverless operations the same day and filed recall 25E-029 for 270 vehicles on May 1, 2025.", "Both vehicles sustained minor damage, according to TechCrunch." ], "tags": [ "robotaxi", "prediction-error", "recall", "operations-paused", "no-injuries" ], "sources": [ { "title": "Part 573 Safety Recall Report 25E-029", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/rcl/2025/RCLRPT-25E029-4731.PDF", "date": "2025-05-01" }, { "title": "Amazon-owned Zoox issues recall following robotaxi crash", "publisher": "TechCrunch", "url": "https://techcrunch.com/2025/05/06/amazon-owned-zoox-issues-recall-following-robotaxi-crash", "date": "2025-05-06" }, { "title": "Part 573 Safety Recall Report 25E037", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/rcl/2025/RCLRPT-25E037-4912.pdf", "date": "2025-05-22" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-12-31-lightyear-drones-folly-beach-drone-show", "url": "https://roboincidents.com/incidents/2024-12-31-lightyear-drones-folly-beach-drone-show/", "title": "Drones fall during New Year's Eve show in Folly Beach, injuring spectator", "summary": "About three minutes into a 250-drone New Year's Eve show at Folly Beach, drones began dropping from the sky. One man was struck and treated at the scene for minor scrapes.", "date": "2024-12-31", "date_precision": "day", "city": "Folly Beach", "state": "SC", "country": "US", "category": "drones", "category_name": "Drones", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Lightyear Drones", "manufacturer": "", "system": "250-drone light show swarm", "companies": [ "Lightyear Drones" ], "autonomy_mode": "remotely-piloted", "autonomy_mode_name": "Remotely piloted", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "FAA" ], "official_records": [], "outcomes": [ "The remaining drones were brought down in a controlled descent and the show was ended early.", "Folly Beach police said the FAA was notified and would lead the investigation." ], "key_facts": [ "Drones began falling about three minutes into a 250-drone New Year's Eve light show in Folly Beach, South Carolina, on December 31, 2024.", "One man was hit by a falling drone and treated at the scene for two minor scrapes.", "Drones fell for about 30 seconds before the rest of the swarm made a controlled descent to its landing zone, according to city public safety officials.", "The show was flown by Lightyear Drones for the Folly Association of Business.", "The failure came ten days after a drone show in Orlando seriously injured a child." ], "tags": [ "drone-show", "spectator", "new-years-eve", "lightyear-drones" ], "sources": [ { "title": "Expert says more regulation needed following Folly Beach drone show malfunction", "publisher": "Live 5 News (WCSC)", "url": "https://www.live5news.com/2025/01/01/expert-says-more-regulation-needed-following-folly-beach-drone-show-malfunction/?outputType=amp", "date": "2025-01-01" }, { "title": "Man injured by falling drones during New Year's drone show", "publisher": "WBTV (Gray News)", "url": "https://www.wbtv.com/2025/01/01/falling-drones-injure-man-during-new-years-show/?outputType=amp", "date": "2025-01-01" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-12-27-waymo-serve-robotics-los-angeles-intersection-collision", "url": "https://roboincidents.com/incidents/2024-12-27-waymo-serve-robotics-los-angeles-intersection-collision/", "title": "Waymo robotaxi and Serve delivery robot collide at Los Angeles intersection", "summary": "A driverless Waymo making a right turn hit a Serve Robotics delivery robot that was trying to mount a curb. The impact was about 4 mph and neither vehicle was damaged.", "date": "2024-12-27", "date_precision": "day", "city": "Los Angeles", "state": "CA", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "disruption", "severity_name": "Disruption", "fatalities": 0, "injuries": 0, "operator": "Serve Robotics; Waymo", "manufacturer": "Serve Robotics (delivery robot); Waymo (automated driving system)", "system": "Serve Robotics sidewalk delivery robot under remote supervisor control; Waymo driverless robotaxi with no passengers", "companies": [ "Serve Robotics", "Waymo" ], "autonomy_mode": "teleoperated", "autonomy_mode_name": "Teleoperated", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Waymo and Serve Robotics said they were in contact with each other to prevent similar collisions." ], "key_facts": [ "A Waymo robotaxi and a Serve Robotics sidewalk delivery robot collided at an intersection in the Los Angeles area on the night of December 27, 2024.", "Waymo said its vehicle braked hard and was traveling about 4 mph at impact; neither vehicle was damaged.", "The Waymo was driving without passengers.", "Serve Robotics said the robot was under the control of a remote supervisor, which is its usual practice for street crossings.", "Serve Robotics said it was the first time one of its robots had collided with a robotaxi." ], "tags": [ "serve-robotics", "waymo", "robotaxi", "intersection", "remote-supervisor" ], "sources": [ { "title": "A Waymo robotaxi and a Serve delivery robot collided in Los Angeles", "publisher": "TechCrunch", "url": "https://techcrunch.com/2024/12/31/a-waymo-robotaxi-and-a-serve-delivery-robot-collided-in-los-angeles", "date": "2024-12-31" }, { "title": "Self-Driving Waymo Cab Smashes Into Delivery Robot", "publisher": "Futurism", "url": "https://futurism.com/robotaxi-smashes-delivery-robot", "date": "2025-01-02" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-12-21-sky-elements-orlando-lake-eola-drone-show", "url": "https://roboincidents.com/incidents/2024-12-21-sky-elements-orlando-lake-eola-drone-show/", "title": "Drone show collision at Orlando's Lake Eola seriously injures child", "summary": "Drones in a 500-aircraft Sky Elements holiday show collided on liftoff at Lake Eola and one flew into the crowd, seriously injuring a child. The NTSB cited setup errors.", "date": "2024-12-21", "date_precision": "day", "city": "Orlando", "state": "FL", "country": "US", "category": "drones", "category_name": "Drones", "severity": "serious-injury", "severity_name": "Serious injury", "fatalities": 0, "injuries": 1, "operator": "Sky Elements Drone Shows (Sky Elements LLC)", "manufacturer": "Uvify", "system": "Swarm of 500 Uvify IFO light-show drones flown under an FAA Part 107 waiver", "companies": [ "Sky Elements" ], "autonomy_mode": "remotely-piloted", "autonomy_mode_name": "Remotely piloted", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NTSB", "FAA" ], "official_records": [], "outcomes": [ "The city canceled the second show scheduled for 8 p.m. on December 21, 2024.", "The FAA suspended Sky Elements' authorization to fly drone shows, and several shows around the country were canceled, News4JAX reported on December 31, 2024.", "The NTSB published its final report on September 15, 2026, citing the remote pilot's setup errors and the operator's lack of oversight.", "The child's family sued Sky Elements and the City of Orlando; a confidential proposed settlement was reported in September 2026.", "Sky Elements now requires two certified pilots per show, signed checklists and a 155-foot buffer between the geofence and spectators." ], "key_facts": [ "On December 21, 2024, drones in a 500-drone holiday light show over Lake Eola in Orlando collided during liftoff, and several fell or flew into the crowd.", "A child in the audience was struck in the face and chest by one drone and seriously injured, according to the NTSB.", "The NTSB found the show's center position and heading were entered incorrectly, shifting the flight area about 59 feet closer to spectators.", "The NTSB determined the probable cause was the remote pilot's failure to place the show center over the drones' actual launch position.", "The drone that hit the child reached about 58 knots before crossing the geofence, and its last recorded speed was about 43 knots." ], "tags": [ "drone-show", "child", "spectator", "geofence", "ntsb", "sky-elements" ], "sources": [ { "title": "Aviation Investigation Final Report DCA25LA065", "publisher": "NTSB", "url": "https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199458/pdf", "date": "2026-09-15" }, { "title": "Investigation Docket DCA25LA065", "publisher": "NTSB", "url": "https://data.ntsb.gov/Docket?ProjectID=199458", "date": "2026-09-15" }, { "title": "Orlando drone show errors led to Lake Eola crash that seriously injured 7-year-old: NTSB", "publisher": "FOX 35 Orlando", "url": "https://www.fox35orlando.com/news/orlando-drone-show-errors-led-lake-eola-crash-seriously-injured-7-year-old-ntsb", "date": "2026-09-16" }, { "title": "NTSB, FAA investigating after drones collide, fall into crowd during downtown Orlando holiday show", "publisher": "ClickOrlando (WKMG)", "url": "https://www.clickorlando.com/news/local/2024/12/22/faa-investigating-after-drones-collide-fall-into-crowd-during-downtown-orlando-holiday-show", "date": "2024-12-22" }, { "title": "FAA cancels some drone shows nationwide after Orlando incident", "publisher": "News4JAX (WJXT)", "url": "https://news4jax.com/news/florida/2024/12/31/faa-cancels-some-drone-shows-nationwide-after-orlando-incident", "date": "2024-12-31" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-12-16-amazon-prime-air-mk30-pendleton-test-crashes", "url": "https://roboincidents.com/incidents/2024-12-16-amazon-prime-air-mk30-pendleton-test-crashes/", "title": "Two Amazon MK30 drones crash minutes apart at Pendleton test range", "summary": "Two Amazon MK30 delivery drones fell from about 200 feet within minutes of each other during testing in Oregon after faulty altitude readings cut power to their motors.", "date": "2024-12-16", "date_precision": "day", "city": "Pendleton", "state": "OR", "country": "US", "category": "drones", "category_name": "Drones", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Amazon Prime Air (Amazon.com Services LLC)", "manufacturer": "Amazon", "system": "Amazon Prime Air MK30 delivery drone", "companies": [ "Amazon" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NTSB", "FAA" ], "official_records": [], "outcomes": [ "Amazon voluntarily paused commercial drone deliveries in College Station, Texas, and Tolleson, Arizona, on January 17, 2025, to update the MK30's software.", "The FAA approved Amazon's software changes on March 12, 2025, and deliveries resumed in late March 2025.", "The NTSB record for the accident attributes the power loss to an incorrect altitude indication that followed a recent software update." ], "key_facts": [ "Two Amazon Prime Air MK30 drones crashed about four minutes apart during test flights at Amazon's Pendleton, Oregon, range on December 16, 2024.", "The drones were flying at 217 feet and 183 feet when their propellers lost power, according to federal findings reported by Bloomberg.", "One of the two drones caught fire on the ground; no one was injured.", "The NTSB record for the accident cites an improper altitude indication after a recent software update, which led to a loss of engine power in flight.", "Amazon paused customer drone deliveries in Texas and Arizona on January 17, 2025, but said the Oregon crashes were not the main reason." ], "tags": [ "amazon-prime-air", "mk30", "test-flight", "lidar", "software" ], "sources": [ { "title": "Why Amazon's MK30 Drones Crashed: Sensor Issues Exposed", "publisher": "DroneXL", "url": "https://dronexl.co/2025/05/16/why-amazon-mk30-drones-crashed-sensor-issues-exposed", "date": "2025-05-16" }, { "title": "Amazon hits pause on drone delivery after crash reports", "publisher": "DroneDJ", "url": "https://dronedj.com/2025/01/21/amazon-drone-delivery-crash-mk30/", "date": "2025-01-21" }, { "title": "AMAZON.COM SERVICES LLC MK30", "publisher": "RecallCheck (copy of NTSB record WPR25LA063)", "url": "https://recallcheck.net/aviation-safety/28373", "date": null }, { "title": "Amazon Resumes Drone Deliveries After Two-Month Pause Due to Sensor Concerns", "publisher": "DroneXL", "url": "https://dronexl.co/2025/04/01/amazon-resumes-drone-deliveries", "date": "2025-04-01" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-05-24-ecovacs-deebot-x2-robot-vacuums-hijacked-us-homes", "url": "https://roboincidents.com/incidents/2024-05-24-ecovacs-deebot-x2-robot-vacuums-hijacked-us-homes/", "title": "Hijacked Ecovacs Deebot X2 robot vacuums shout slurs in US homes", "summary": "Intruders took remote control of Ecovacs Deebot X2 robot vacuums in Minnesota, Los Angeles and El Paso in May 2024, driving them around homes and yelling slurs through the speakers.", "date": "2024-05-24", "date_precision": "day", "city": "", "state": "MN", "country": "US", "category": "consumer-robots", "category_name": "Consumer robots", "severity": "disruption", "severity_name": "Disruption", "fatalities": 0, "injuries": 0, "operator": "Private owners (devices taken over by unauthorized remote users)", "manufacturer": "Ecovacs", "system": "Ecovacs Deebot X2 robot vacuum with camera, speaker and app-based remote control", "companies": [ "Ecovacs" ], "autonomy_mode": "teleoperated", "autonomy_mode_name": "Teleoperated", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Ecovacs told the Australian Broadcasting Corporation that it traced one case to an unauthorized person who had obtained the owner's account credentials, and that it blocked the IP address involved.", "Ecovacs said it had fixed a flaw allowing the camera PIN to be bypassed and would issue a further security update for X2 owners in November 2024." ], "key_facts": [ "On May 24, 2024, an Ecovacs Deebot X2 robot vacuum in a Minnesota home was taken over remotely and a voice shouted racial slurs through its speaker.", "The same day a Deebot X2 in Los Angeles was driven around a home chasing the owner's dog while abusive comments played, and five days later a similar event was reported in El Paso.", "Security researchers had shown in December 2023 that the four-digit PIN protecting the X2's camera and remote control was checked only by the app and could be bypassed.", "Ecovacs said it found no breach of its own systems and attributed one case to reused login credentials, a technique known as credential stuffing.", "No physical injuries were reported." ], "tags": [ "cybersecurity", "robot-vacuum", "remote-access", "privacy", "home" ], "sources": [ { "title": "Hackers take control of robot vacuums in multiple cities, yell racial slurs", "publisher": "ABC News (Australian Broadcasting Corporation)", "url": "https://www.abc.net.au/news/2024-10-11/robot-vacuum-yells-racial-slurs-at-family-after-being-hacked/104445408", "date": "2024-10-11" }, { "title": "Hacked Robot Vacuums Across the U.S. Started Yelling Slurs", "publisher": "Gizmodo", "url": "https://gizmodo.com/hacked-robot-vacuums-across-the-us-started-yelling-slurs-2000511013", "date": "2024-10-11" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-05-21-waymo-phoenix-utility-pole-collision", "url": "https://roboincidents.com/incidents/2024-05-21-waymo-phoenix-utility-pole-collision/", "title": "Waymo robotaxi strikes utility pole in Phoenix alley, prompting recall", "summary": "An empty Waymo robotaxi hit a wooden utility pole in a Phoenix alley during a low-speed pullover on May 21, 2024. Waymo recalled software and maps on 672 vehicles.", "date": "2024-05-21", "date_precision": "day", "city": "Phoenix", "state": "AZ", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Waymo LLC", "manufacturer": "Waymo (automated driving system)", "system": "Waymo robotaxi running the 5th Generation Automated Driving System", "companies": [ "Waymo" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NHTSA" ], "official_records": [], "outcomes": [ "Waymo updated its driving software between May 29 and June 3, 2024, and its maps by June 6, 2024.", "On June 10, 2024, Waymo filed recall 24E-049 covering 672 vehicles." ], "key_facts": [ "On May 21, 2024, a Waymo vehicle in Phoenix collided with a wooden utility pole in an alley while performing a low-speed pullover.", "There were no passengers or other road users involved and no injuries; the Waymo vehicle was damaged.", "Waymo told NHTSA the software could assign a low damage score to a pole-like object and fail to avoid it when the map lacked a hard road edge in front of it.", "Recall 24E-049, filed June 10, 2024, covered 672 Waymo vehicles.", "The fix combined a software update with map changes adding a hard road edge between poles and the drivable surface." ], "tags": [ "robotaxi", "fixed-object", "pullover", "recall", "mapping" ], "sources": [ { "title": "Part 573 Safety Recall Report 24E-049", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/rcl/2024/RCLRPT-24E049-1733.PDF", "date": "2024-06-10" }, { "title": "Waymo recalls more than 600 self-driving vehicles for updates after one strikes Phoenix pole", "publisher": "Associated Press via ABC15 Arizona", "url": "https://www.abc15.com/news/local-news/waymo-recalls-more-than-600-self-driving-vehicles-for-updates-after-one-strikes-phoenix-pole", "date": null } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-02-24-ford-bluecruise-san-antonio-i10-stationary-vehicle-fatality", "url": "https://roboincidents.com/incidents/2024-02-24-ford-bluecruise-san-antonio-i10-stationary-vehicle-fatality/", "title": "Ford Mach-E using BlueCruise hits stopped SUV on I-10 in San Antonio", "summary": "A Ford Mustang Mach-E operating hands-free on BlueCruise struck a Honda CR-V stopped in a travel lane of I-10 in San Antonio on February 24, 2024, killing the Honda's driver.", "date": "2024-02-24", "date_precision": "day", "city": "San Antonio", "state": "TX", "country": "US", "category": "driver-assistance", "category_name": "Driver assistance", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 1, "operator": "Private driver of the Ford Mustang Mach-E", "manufacturer": "Ford Motor Company", "system": "2022 Ford Mustang Mach-E operating in BlueCruise hands-free partial automation mode", "companies": [ "Ford" ], "autonomy_mode": "driver-assistance", "autonomy_mode_name": "Driver assistance (Level 2)", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NTSB" ], "official_records": [], "outcomes": [ "The NTSB considered the crash, together with a second fatal BlueCruise crash in Philadelphia, at a board meeting on March 31, 2026, and issued report HIR-26-02.", "The NTSB recommended that Ford revise its driver monitoring and require automatic emergency braking to be engaged when BlueCruise is in use.", "The NTSB recommended that NHTSA require driver monitoring systems, automation data recording and crash notification for new Level 2 vehicles." ], "key_facts": [ "The crash happened at 9:48 p.m. on February 24, 2024, in the eastbound center lane of Interstate 10 near the Woodlake Parkway exit in San Antonio.", "System data showed the Ford was traveling 74.7 mph in a 70 mph zone with BlueCruise engaged, and no braking or steering by the driver or the system was recorded before impact.", "The driver of the stationary 1999 Honda CR-V died; the Ford's driver had minor injuries.", "The NTSB found the probable cause was the Ford driver's failure to respond to the stopped vehicle due to distraction, likely from the in-vehicle navigation system.", "The NTSB cited as a contributing factor that the Ford's partial automation system, including automatic emergency braking, could not detect and respond to the stationary vehicle." ], "tags": [ "ford", "bluecruise", "hands-free", "highway", "stationary-vehicle", "ntsb" ], "sources": [ { "title": "Fatal Crashes Between Vehicles Operating in Hands-Free Partial Automation Mode and Stationary Vehicles", "publisher": "NTSB", "url": "https://www.ntsb.gov/investigations/Pages/HWY24FH006.aspx", "date": null }, { "title": "NTSB determines cause of 2 fatal BlueCruise-involved crashes, notes system safety limitations", "publisher": "Repairer Driven News", "url": "https://www.repairerdrivennews.com/2026/04/02/ntsb-determines-cause-of-2-fatal-bluecruise-involved-crashes-notes-system-safety-limitations/", "date": "2026-04-02" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2024-02-06-schreiber-foods-carthage-automated-palletizer-fatality", "url": "https://roboincidents.com/incidents/2024-02-06-schreiber-foods-carthage-automated-palletizer-fatality/", "title": "Schreiber Foods worker killed in automated palletizer in Carthage", "summary": "A 48-year-old worker died on February 6, 2024, after becoming trapped in an automated palletizing machine at the Schreiber Foods plant in Carthage, Missouri.", "date": "2024-02-06", "date_precision": "day", "city": "Carthage", "state": "MO", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Schreiber Foods", "manufacturer": "", "system": "Automated palletizing machine at a food plant", "companies": [ "Schreiber Foods" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Carthage Police Department" ], "official_records": [], "outcomes": [ "Carthage police treated the death as an industrial accident and said further police investigation was unlikely.", "Schreiber Foods said it was working with authorities to investigate and brought grief counselors to the plant." ], "key_facts": [ "On February 6, 2024, a 48-year-old worker died at the Schreiber Foods plant on Claxton Avenue in Carthage, Missouri.", "Carthage's police chief said the emergency caller reported that the worker had fallen into an automated palletizing machine and was stuck.", "Emergency dispatch received the call at about 3:44 p.m., and the worker was declared dead at the plant after resuscitation efforts.", "Schreiber Foods said it was working with authorities to investigate the incident." ], "tags": [ "palletizer", "food-processing", "entrapment" ], "sources": [ { "title": "Worker dies after falling into pallet machine at Mo. plant", "publisher": "The Joplin Globe (via EMS1)", "url": "https://www.ems1.com/fatal-incidents/worker-dies-after-falling-into-pallet-machine-at-mo-plant", "date": "2024-02-12" }, { "title": "Worker death at Schreiber Foods in Carthage being investigated", "publisher": "Newstalk KZRG", "url": "https://newstalkkzrg.com/2024/02/07/worker-death-at-schreiber-foods-in-carthage-being-investigated", "date": "2024-02-07" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-12-11-waymo-phoenix-towed-pickup-double-collision", "url": "https://roboincidents.com/incidents/2023-12-11-waymo-phoenix-towed-pickup-double-collision/", "title": "Two Waymo robotaxis hit the same towed pickup truck in Phoenix", "summary": "Two driverless Waymo vehicles struck the same pickup truck, which was being towed backward at an angle, minutes apart in Phoenix on December 11, 2023. Waymo later recalled software.", "date": "2023-12-11", "date_precision": "day", "city": "Phoenix", "state": "AZ", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Waymo LLC", "manufacturer": "Jaguar (vehicle), Waymo (automated driving system)", "system": "Waymo robotaxis running the 5th Generation Automated Driving System", "companies": [ "Waymo" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NHTSA" ], "official_records": [], "outcomes": [ "Waymo updated the software on all affected vehicles between December 20, 2023, and January 12, 2024.", "On February 13, 2024, Waymo filed recall 24E-013 covering 444 vehicles, the company's first recall." ], "key_facts": [ "On December 11, 2023, two Waymo robotaxis in Phoenix hit the same pickup truck, which was being towed backward at an angle, within minutes of each other.", "Neither Waymo vehicle was carrying riders, and no injuries were reported.", "Waymo said its software incorrectly predicted the future motion of the towed vehicle.", "Recall 24E-013 covered 444 Waymo vehicles and was the company's first recall.", "Waymo completed the software fix by January 12, 2024, before the recall was filed." ], "tags": [ "robotaxi", "tow-truck", "prediction-error", "recall", "no-injuries" ], "sources": [ { "title": "Part 573 Safety Recall Report 24E-013", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/rcl/2024/RCLRPT-24E013-4528.PDF", "date": "2024-02-13" }, { "title": "Waymo issues a voluntary recall on its self-driving vehicle software", "publisher": "CNBC", "url": "https://www.cnbc.com/2024/02/13/waymo-issues-a-voluntary-recall-on-its-self-driving-vehicle-software.html", "date": "2024-02-13" }, { "title": "Waymo recalls software after two self-driving cars hit the same truck", "publisher": "CNN via ABC15 Arizona", "url": "https://www.abc15.com/news/national/waymo-recalls-software-after-two-self-driving-cars-hit-the-same-truck", "date": null } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-10-02-cruise-san-francisco-pedestrian-dragging", "url": "https://roboincidents.com/incidents/2023-10-02-cruise-san-francisco-pedestrian-dragging/", "title": "Cruise robotaxi drags pedestrian about 20 feet in San Francisco", "summary": "A driverless Cruise robotaxi ran over a pedestrian thrown into its path by another car in San Francisco on October 2, 2023, then dragged her about 20 feet while pulling over.", "date": "2023-10-02", "date_precision": "day", "city": "San Francisco", "state": "CA", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "serious-injury", "severity_name": "Serious injury", "fatalities": 0, "injuries": 1, "operator": "Cruise LLC", "manufacturer": "Cruise / General Motors", "system": "Driverless Cruise robotaxi; the recalled component was the collision detection subsystem in Cruise's driverless software", "companies": [ "Cruise", "General Motors" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "California DMV", "NHTSA", "US Department of Justice", "California Public Utilities Commission" ], "official_records": [], "outcomes": [ "The California DMV suspended Cruise's deployment and driverless testing permits on October 24, 2023, effective immediately.", "Cruise paused its driverless fleet on October 26, 2023, and on November 7, 2023, filed recall 23E-086 covering 950 automated driving system units.", "On September 30, 2024, NHTSA announced a consent order under which Cruise paid a $1.5 million penalty for incomplete crash reports.", "On November 14, 2024, Cruise entered a three-year deferred prosecution agreement and agreed to pay a $500,000 criminal fine for submitting a false report to NHTSA." ], "key_facts": [ "On October 2, 2023, a human-driven vehicle struck a pedestrian in San Francisco and threw her into the path of a driverless Cruise robotaxi, which ran over her.", "After stopping, the Cruise vehicle tried to pull over and dragged the pedestrian about 20 feet because it did not detect that she was underneath it.", "Cruise's recall report said its software wrongly classified the impact as a lateral collision and commanded a pullover instead of staying stopped.", "The California DMV suspended Cruise's driverless permits on October 24, 2023, citing an unreasonable risk to public safety and misrepresentation of safety information.", "Cruise admitted submitting a false report to NHTSA that omitted the dragging and paid a $500,000 criminal fine and a $1.5 million civil penalty." ], "tags": [ "robotaxi", "pedestrian", "permit-suspension", "recall", "false-report", "doj" ], "sources": [ { "title": "Cruise Admits To Submitting A False Report To Influence A Federal Investigation And Agrees To Pay $500,000", "publisher": "US Department of Justice, US Attorney's Office, Northern District of California", "url": "https://www.justice.gov/usao-ndca/pr/cruise-admits-submitting-false-report-influence-federal-investigation-and-agrees-pay", "date": "2024-11-14" }, { "title": "NHTSA Announces Consent Order with Cruise After Company Failed to Fully Report Crash Involving Pedestrian", "publisher": "NHTSA", "url": "https://www.nhtsa.gov/press-releases/consent-order-cruise-crash-reporting", "date": "2024-09-30" }, { "title": "DMV Statement on Cruise LLC Suspension", "publisher": "California DMV", "url": "https://www.dmv.ca.gov/portal/news-and-media/dmv-statement-on-cruise-llc/", "date": "2023-10-24" }, { "title": "Part 573 Safety Recall Report 23E-086", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/rcl/2023/RCLRPT-23E086-7725.PDF", "date": "2023-11-07" }, { "title": "California DMV immediately suspends Cruise's robotaxi permit", "publisher": "TechCrunch", "url": "https://techcrunch.com/2023/10/24/dmv-immediately-suspends-cruises-robotaxi-permit-in-california/", "date": "2023-10-24" }, { "title": "Cruise fined $500,000 for filing false report about driverless car dragging pedestrian", "publisher": "KTVU FOX 2 / Bay City News", "url": "https://ktvu.com/news/cruise-fined-500000-filing-false-report-about-driverless-car-dragging-pedestrian", "date": "2024-11-14" }, { "title": "Cruise admits to false report in 2023 dragging of San Francisco pedestrian", "publisher": "CBS San Francisco", "url": "https://www.cbsnews.com/sanfrancisco/news/cruise-automation-admits-false-report-sf-pedestrian-dragging/", "date": "2024-11-14" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-09-22-starship-arizona-state-university-parking-attendant", "url": "https://roboincidents.com/incidents/2023-09-22-starship-arizona-state-university-parking-attendant/", "title": "Starship delivery robot reverses into ASU parking attendant in Tempe", "summary": "A Starship delivery robot backed into a 73-year-old parking attendant at Arizona State University and knocked her down, a police report says. She later sued the company.", "date": "2023-09-22", "date_precision": "day", "city": "Tempe", "state": "AZ", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Starship Technologies", "manufacturer": "Starship Technologies", "system": "Starship six-wheeled sidewalk food delivery robot", "companies": [ "Starship Technologies" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Arizona State University Police Department" ], "official_records": [], "outcomes": [ "ASU police documented the collision in a report.", "The injured employee sued Starship Technologies in Maricopa County Superior Court, alleging product liability and negligence.", "Starship has denied liability in court, and a jury trial was scheduled, KJZZ reported in July 2026." ], "key_facts": [ "On September 22, 2023, a Starship delivery robot reversed into a 73-year-old parking attendant near a parking structure on Arizona State University's Tempe campus.", "An ASU police report says the robot knocked the woman onto her back and then reversed toward her a second time while she was on the ground.", "The police report lists a 4-inch cut near her left elbow, back pain and difficulty walking; the Tempe Fire Department treated her at the scene.", "According to the police report, Starship asked for her contact details so it could offer insurance information and promo codes.", "Her lawsuit alleges severe and permanent injuries; Starship says in court filings that it is not at fault." ], "tags": [ "starship", "campus", "pedestrian", "lawsuit", "reversing" ], "sources": [ { "title": "Delivery Robot Knocked Over Pedestrian, Company Offered 'Promo Codes' to Apologize", "publisher": "404 Media", "url": "https://www.404media.co/delivery-robot-knocked-over-pedestrian-company-offered-promo-codes-to-apologize/", "date": "2024-09-19" }, { "title": "Lawsuit claims ASU employee was struck, injured by a food delivery robot", "publisher": "KJZZ", "url": "https://www.kjzz.org/business/2026-07-14/lawsuit-claims-asu-employee-was-struck-injured-by-a-food-delivery-robot", "date": "2026-07-14" }, { "title": "Robot delivery gone wrong: ASU worker says food-toting rover ran her down on campus in new lawsuit", "publisher": "FOX 10 Phoenix", "url": "https://www.fox10phoenix.com/news/delivery-robot-disaster-asu-worker-says-food-delivering-rover-ran-her-down-campus-new-lawsuit", "date": "2026-07-30" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-08-24-aiper-elite-pro-robotic-pool-cleaner-recall-overheating-burn", "url": "https://roboincidents.com/incidents/2023-08-24-aiper-elite-pro-robotic-pool-cleaner-recall-overheating-burn/", "title": "Aiper Elite Pro robotic pool cleaners recalled after 17 overheating reports", "summary": "About 22,000 Aiper Elite Pro cordless robotic pool cleaners were recalled on August 24, 2023 after 17 reports of overheating while charging, including one minor fingertip burn.", "date": "2023-08-24", "date_precision": "day", "city": "", "state": "", "country": "US", "category": "consumer-robots", "category_name": "Consumer robots", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Consumer owners", "manufacturer": "Compurobot Technology Company (China); distributed by Shenzhen Aiper Intelligent Co., Ltd.", "system": "Aiper Elite Pro GS100 cordless robotic pool vacuum cleaner", "companies": [ "Aiper" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "CPSC" ], "official_records": [], "outcomes": [ "On August 24, 2023, the U.S. Consumer Product Safety Commission announced a recall of about 22,000 Aiper Elite Pro GS100 robotic pool cleaners (recall number 23-784).", "Aiper offered owners a free replacement, its Seagull Pro robotic pool cleaner.", "On March 20, 2025, the Seagull Pro was itself recalled (recall number 25-187) after 19 reports of units melting, smoking or catching fire while charging, with five reports of property damage and no injuries." ], "key_facts": [ "About 22,000 Aiper Elite Pro GS100 cordless robotic pool cleaners sold in the United States were recalled on August 24, 2023 for burn and fire hazards.", "The company had received 17 reports of the pool cleaners overheating, including one minor fingertip burn that did not need medical treatment.", "The Consumer Product Safety Commission said the battery could overheat and short circuit if the charging cord was plugged in without its adapter.", "The replacement model offered in the recall, the Aiper Seagull Pro, was recalled in March 2025 after 19 reports of melting, smoking or fire while charging." ], "tags": [ "recall", "pool-robot", "battery", "overheating", "cpsc" ], "sources": [ { "title": "Aiper Elite Pro Cordless Robotic Pool Vacuum Cleaners Recalled Due to Burn and Fire Hazards; Distributed by Shenzhen Aiper Intelligent Co. (Recall Alert)", "publisher": "U.S. Consumer Product Safety Commission", "url": "https://www.cpsc.gov/Recalls/2023/Aiper-Elite-Pro-Cordless-Robotic-Pool-Vacuum-Cleaners-Recalled-Due-to-Burn-and-Fire-Hazards-Distributed-by-Shenzhen-Aiper-Intelligent-Co-Recall-Alert", "date": "2023-08-24" }, { "title": "Aiper Seagull Pro Cordless Robotic Pool Vacuum Cleaners Recalled Due to Burn and Fire Hazards; Distributed by Shenzhen Aiper Intelligent Co.", "publisher": "U.S. Consumer Product Safety Commission", "url": "https://www.cpsc.gov/Recalls/2025/Aiper-Seagull-Pro-Cordless-Robotic-Pool-Vacuum-Cleaners-Recalled-Due-to-Burn-and-Fire-Hazards-Distributed-by-Shenzhen-Aiper-Intelligent-Co", "date": "2025-03-20" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-08-17-cruise-san-francisco-fire-truck-collision", "url": "https://roboincidents.com/incidents/2023-08-17-cruise-san-francisco-fire-truck-collision/", "title": "Cruise robotaxi collides with San Francisco fire truck, injuring rider", "summary": "A driverless Cruise robotaxi carrying a passenger collided with a fire truck responding to an emergency in San Francisco on August 17, 2023. The DMV had Cruise halve its fleet.", "date": "2023-08-17", "date_precision": "day", "city": "San Francisco", "state": "CA", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Cruise LLC", "manufacturer": "Cruise / General Motors", "system": "Driverless Cruise robotaxi operating in commercial ride-hail service", "companies": [ "Cruise", "General Motors" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "California DMV", "San Francisco Police Department" ], "official_records": [], "outcomes": [ "On August 18, 2023, the California DMV asked Cruise to immediately cut its active San Francisco driverless fleet by half, to no more than 50 vehicles by day and 150 at night.", "Cruise agreed to the reduction, which the DMV said would last until its investigation was complete and corrective action was taken." ], "key_facts": [ "The collision happened at about 10:23 p.m. on August 17, 2023, at Turk and Polk streets in San Francisco, according to police.", "The fire truck was responding to an emergency with its lights and siren on.", "The robotaxi's one passenger was taken to a hospital with injuries described as not life-threatening.", "Cruise said buildings at the intersection blocked the view of cross traffic and that the fire truck was in the oncoming lane to pass a red light.", "The California DMV asked Cruise to halve its San Francisco fleet the next day, and Cruise complied." ], "tags": [ "robotaxi", "emergency-vehicle", "passenger-injury", "intersection", "fleet-reduction" ], "sources": [ { "title": "California DMV requests Cruise to halve driverless car fleet after collision with firetruck in San Francisco", "publisher": "Fox Business", "url": "https://www.foxbusiness.com/markets/california-dmv-requests-cruise-halve-driverless-car-fleet-after-collision-with-firetruck-san-francisco", "date": "2023-08-19" }, { "title": "Cruise will comply with DMV request to cut fleet in half following crash with SF fire truck", "publisher": "KTVU FOX 2", "url": "https://ktvu.com/news/cruise-robotaxi-with-passenger-crashes-into-san-francisco-fire-truck", "date": "2023-08-18" }, { "title": "California DMV is investigating a Cruise robotaxi's collision with a fire truck", "publisher": "Engadget", "url": "https://www.engadget.com/california-dmv-is-investigating-a-cruise-robotaxis-collision-with-a-fire-truck-093037885.html", "date": "2023-08-19" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-07-22-tesla-fremont-fanuc-robot-arm-technician-injury-lawsuit", "url": "https://roboincidents.com/incidents/2023-07-22-tesla-fremont-fanuc-robot-arm-technician-injury-lawsuit/", "title": "Lawsuit says FANUC robot arm knocked out Tesla technician in Fremont", "summary": "A former Tesla robotics technician alleges a FANUC robot arm struck him and knocked him unconscious during disassembly at the Fremont factory on July 22, 2023.", "date": "2023-07-22", "date_precision": "day", "city": "Fremont", "state": "CA", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "serious-injury", "severity_name": "Serious injury", "fatalities": 0, "injuries": 1, "operator": "Tesla", "manufacturer": "FANUC", "system": "FANUC industrial robot arm being disassembled for maintenance", "companies": [ "Tesla", "FANUC" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "alleged", "status_name": "Alleged", "agencies": [], "official_records": [], "outcomes": [ "A complaint seeking $51 million from Tesla and FANUC was filed in Alameda County Superior Court and moved to federal court in San Francisco on September 19, 2025.", "Tesla asked the court to dismiss the claims against it, arguing that California's workers' compensation law is the exclusive remedy." ], "key_facts": [ "A lawsuit alleges that on July 22, 2023, a robotics technician at Tesla's Fremont, California factory was struck by a FANUC robot arm and lost consciousness.", "The complaint says the technician was helping an engineer disassemble the robot when the arm released with the force of a counterbalance weight of about 8,000 pounds.", "The suit seeks $51 million from Tesla and FANUC and accuses both companies of negligence.", "Tesla has argued that the claims are barred because workers' compensation is the exclusive remedy under California law.", "The allegations have not been tested in court, and neither company had commented publicly when the lawsuit was reported in 2025." ], "tags": [ "automotive", "lawsuit", "maintenance", "stored-energy", "robot-arm" ], "sources": [ { "title": "Former factory worker sues Tesla after robotic arm knocks him unconscious", "publisher": "Manufacturing Dive", "url": "https://www.manufacturingdive.com/news/former-factory-worker-sues-tesla-fanuc-robotic-arm-unconscious-51-million/761123/", "date": "2025-09-25" }, { "title": "Tesla targeted by $51 million lawsuit; worker alleges he was knocked out by robot", "publisher": "Plant Services", "url": "https://www.plantservices.com/industry-news/news/55321150/tesla-targeted-by-51-million-lawsuit-worker-alleges-he-was-knocked-out-by-robot", "date": "2025-10-03" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-04-22-disneyland-fantasmic-maleficent-dragon-animatronic-fire", "url": "https://roboincidents.com/incidents/2023-04-22-disneyland-fantasmic-maleficent-dragon-animatronic-fire/", "title": "Animatronic dragon catches fire during Disneyland's Fantasmic! show", "summary": "The 45-foot animatronic Maleficent dragon in Disneyland's Fantasmic! show caught fire during a performance on April 22, 2023 and was engulfed in flames. No injuries were reported.", "date": "2023-04-22", "date_precision": "day", "city": "Anaheim", "state": "CA", "country": "US", "category": "other", "category_name": "Other robots", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Disneyland Resort (The Walt Disney Company)", "manufacturer": "", "system": "45-foot fire-breathing animatronic Maleficent dragon used in the Fantasmic! nighttime show", "companies": [ "Disney" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Anaheim Fire & Rescue" ], "official_records": [], "outcomes": [ "Anaheim Fire & Rescue responded and the fire was extinguished; the department said no injuries were reported.", "Disney said the cause of the fire was under investigation." ], "key_facts": [ "On the night of April 22, 2023, the animatronic Maleficent dragon in Disneyland's Fantasmic! show caught fire during a performance in Anaheim, California.", "Witnesses said flames appeared around the dragon's head instead of projecting outward as designed, then spread until the figure was fully engulfed.", "The show was stopped, performers and crew were evacuated from Tom Sawyer Island, and nearby attractions were cleared because of smoke.", "The Anaheim Fire Department said no injuries were reported.", "The dragon stands about 45 feet tall; about 1,000 people were watching the show when the fire began, according to City News Service." ], "tags": [ "theme-park", "animatronic", "fire", "live-show" ], "sources": [ { "title": "Disneyland fire-breathing dragon bursts into flames during live 'Fantasmic!' show", "publisher": "Associated Press (via Fortune)", "url": "https://fortune.com/2023/04/24/disneyland-fire-breathing-dragon-bursts-into-flames-during-live-fantasmic-show/", "date": "2023-04-24" }, { "title": "Fire Damages Maleficent Dragon Feature at Disneyland, But No Injuries Reported", "publisher": "City News Service (via Times of San Diego)", "url": "https://timesofsandiego.com/crime/2023/04/23/fire-damages-maleficent-dragon-feature-at-disneyland-but-no-injuries-reported/", "date": "2023-04-23" }, { "title": "A fire-breathing dragon bursts into flames during a popular Disneyland show", "publisher": "NPR / Associated Press (via Hawaiʻi Public Radio)", "url": "https://www.hawaiipublicradio.org/npr-news/npr-news/2023-04-23/a-fire-breathing-dragon-bursts-into-flames-during-a-popular-disneyland-show", "date": "2023-04-23" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2023-03-agility-robotics-digit-promat-chicago-demo-fall", "url": "https://roboincidents.com/incidents/2023-03-agility-robotics-digit-promat-chicago-demo-fall/", "title": "Agility Robotics' Digit humanoid collapses during ProMat demo in Chicago", "summary": "Agility Robotics' Digit warehouse humanoid collapsed while moving containers in a live demonstration at the ProMat trade show in Chicago in March 2023. Nobody was reported hurt.", "date": "2023-03", "date_precision": "month", "city": "Chicago", "state": "IL", "country": "US", "category": "humanoid-robots", "category_name": "Humanoid robots", "severity": "disruption", "severity_name": "Disruption", "fatalities": 0, "injuries": 0, "operator": "Agility Robotics", "manufacturer": "Agility Robotics", "system": "Digit bipedal humanoid logistics robot", "companies": [ "Agility Robotics" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "On April 6, 2023, Agility Robotics published video of the fall itself and said Digit had a 99% success rate over about 20 hours of live demos at ProMat." ], "key_facts": [ "Agility Robotics' Digit humanoid robot collapsed during a live box-handling demonstration at the ProMat 2023 trade show in Chicago.", "Agility Robotics said Digit took a couple of falls at ProMat while achieving a 99% success rate over about 20 hours of live demos.", "The company published the footage itself on April 6, 2023, and a spokesperson said falls are a normal part of any new technology.", "No injuries to people were reported." ], "tags": [ "trade-show", "fall", "warehouse", "public-demo" ], "sources": [ { "title": "Agility Robotics Showcases Latest Version of Humanoid Robot Digit at ProMat 2023", "publisher": "Robotics 24/7", "url": "https://www.robotics247.com/article/agility_robotics_showcases_latest_version_of_humanoid_robot_digit_at_promat_2023", "date": "2023-03-20" }, { "title": "Agility Robotics' Digit Warehouse Bot Collapses After 20+ Hours of Live Demos, Claims 99% Success Rate", "publisher": "Tech Times", "url": "https://www.techtimes.com/articles/290843/20230426/agility-robotics-digit-warehouse-bot-collapses-20-hours-live-demos.htm", "date": "2023-04-26" }, { "title": "Warehouse Robot Collapses After Working For 20 Hours Straight", "publisher": "Sunny Skyz", "url": "https://www.sunnyskyz.com/blog/3590/Warehouse-Robot-Collapses-After-Working-For-20-Hours-Straight", "date": "2023-05-02" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2022-09-13-serve-robotics-hollywood-high-police-tape", "url": "https://roboincidents.com/incidents/2022-09-13-serve-robotics-hollywood-high-police-tape/", "title": "Serve Robotics delivery robot crosses police tape at Hollywood High School", "summary": "A Serve Robotics delivery robot rolled under police tape and through an LAPD scene outside Hollywood High School during a reported shooting that turned out to be a hoax.", "date": "2022-09-13", "date_precision": "day", "city": "Los Angeles", "state": "CA", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "disruption", "severity_name": "Disruption", "fatalities": 0, "injuries": 0, "operator": "Serve Robotics", "manufacturer": "Serve Robotics", "system": "Serve Robotics sidewalk delivery robot working for Uber Eats", "companies": [ "Serve Robotics" ], "autonomy_mode": "teleoperated", "autonomy_mode_name": "Teleoperated", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Serve Robotics said its procedure is to reroute around barrier tape and that it was taking steps to make sure the procedure is followed." ], "key_facts": [ "A Serve Robotics delivery robot drove under police tape and through a police scene outside Hollywood High School in Los Angeles on September 13, 2022.", "Police were responding to a reported school shooting that was later determined to be a hoax.", "Video shows a bystander lifting the tape so the robot could pass and continue past LAPD officers.", "Serve Robotics said a remote robot supervisor believed the robot was being waved through.", "Serve Robotics said its standard procedure is to reroute rather than cross barrier tape." ], "tags": [ "serve-robotics", "police-scene", "remote-supervisor", "uber-eats" ], "sources": [ { "title": "Food Delivery Robot Casually Drives Under Police Tape, Through Active Crime Scene", "publisher": "VICE", "url": "https://www.vice.com/en/article/food-delivery-robot-casually-drives-under-police-tape-through-active-crime-scene/", "date": "2022-09-16" }, { "title": "Watch: Food delivery robot crashes crime scene", "publisher": "Police1", "url": "https://www.police1.com/bizarre/articles/watch-food-delivery-robot-crashes-crime-scene-JQHYaaP112nhEu1G/", "date": "2022-09-19" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2021-10-28-pony-ai-fremont-driverless-median-collision", "url": "https://roboincidents.com/incidents/2021-10-28-pony-ai-fremont-driverless-median-collision/", "title": "Pony.ai driverless test car hits median and sign in Fremont", "summary": "A Pony.ai test vehicle in autonomous mode struck a center divider and a traffic sign in Fremont on October 28, 2021. California suspended its driverless testing permit.", "date": "2021-10-28", "date_precision": "day", "city": "Fremont", "state": "CA", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Pony.ai", "manufacturer": "Hyundai (vehicle), Pony.ai (automated driving system)", "system": "Pony.ai test vehicle operating in autonomous mode under a California driverless testing permit covering 10 Hyundai Kona electric vehicles", "companies": [ "Pony.ai" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "California DMV", "NHTSA" ], "official_records": [], "outcomes": [ "The California DMV suspended Pony.ai's driverless testing permit on November 19, 2021, effective immediately.", "In March 2022 Pony.ai agreed to recall the automated driving software in three vehicles after NHTSA said it believed the software had a safety defect.", "NHTSA described the action as the first recall of an automated driving system, The Robot Report said." ], "key_facts": [ "On October 28, 2021, a Pony.ai vehicle in autonomous mode hit a road center divider and a traffic sign in Fremont, California, after making a right turn.", "No one was injured and no other vehicles were involved, according to the collision report Pony.ai filed with the California DMV.", "The California DMV suspended Pony.ai's driverless testing permit on November 19, 2021, the first suspension of its kind according to CNBC.", "Pony.ai recalled automated driving software in three vehicles in March 2022 at NHTSA's request.", "The suspension did not affect Pony.ai's permit to test with a safety driver." ], "tags": [ "driverless-testing", "single-vehicle", "permit-suspension", "recall" ], "sources": [ { "title": "California halts Pony.ai's driverless testing permit after accident", "publisher": "CNBC", "url": "https://www.cnbc.com/2021/12/14/california-halts-ponyais-driverless-testing-permit-after-accident.html", "date": "2021-12-13" }, { "title": "Pony.ai agrees to recall 3 of its autonomous vehicles", "publisher": "The Robot Report", "url": "https://www.therobotreport.com/pony-ai-agrees-to-recall-3-of-its-autonomous-vehicles/", "date": "2022-03-08" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2021-09-da-vinci-colon-surgery-boca-raton-patient-death-lawsuit", "url": "https://roboincidents.com/incidents/2021-09-da-vinci-colon-surgery-boca-raton-patient-death-lawsuit/", "title": "Suit alleges da Vinci robot burned patient's intestine in Florida surgery", "summary": "A 2024 federal lawsuit alleged that a da Vinci surgical robot burned a patient's small intestine during colon cancer surgery in Boca Raton in September 2021, leading to her death.", "date": "2021-09", "date_precision": "month", "city": "Boca Raton", "state": "FL", "country": "US", "category": "surgical-robots", "category_name": "Surgical robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Surgical team at Baptist Health Boca Raton Regional Hospital", "manufacturer": "Intuitive Surgical", "system": "da Vinci Xi Surgical System with monopolar curved scissors (electrosurgical instrument)", "companies": [ "Intuitive Surgical" ], "autonomy_mode": "teleoperated", "autonomy_mode_name": "Teleoperated", "status": "alleged", "status_name": "Alleged", "agencies": [], "official_records": [], "outcomes": [ "On February 6, 2024, the patient's husband filed a wrongful-death and product-liability suit against Intuitive Surgical in the U.S. District Court for the Southern District of Florida (case 9:24-cv-80137).", "On July 11, 2024, the court granted Intuitive's motion to dismiss in part, ruling out theories based on reporting to the FDA while allowing the other claims to proceed.", "The plaintiff filed a stipulation of dismissal with prejudice and the court closed the case on July 12, 2024; no terms were made public." ], "key_facts": [ "A lawsuit filed in February 2024 alleged that a da Vinci surgical robot caused a thermal injury to a patient's small intestine during colon cancer surgery at Baptist Health Boca Raton Regional Hospital in September 2021.", "The complaint said the injury perforated the intestine, required further procedures, and led to the patient's death on February 7, 2022.", "The suit alleged that Intuitive Surgical knew of insulation problems that could let electrical current escape from its instruments and burn internal organs.", "A federal judge partly granted Intuitive's motion to dismiss on July 11, 2024, and the case was dismissed with prejudice by stipulation the next day.", "The allegations were never tested at trial, and no court found Intuitive Surgical liable." ], "tags": [ "da-vinci", "lawsuit", "electrosurgery", "wrongful-death", "product-liability" ], "sources": [ { "title": "Sultzer v. Intuitive Surgical, Inc., 9:24-cv-80137 – CourtListener.com", "publisher": "CourtListener (Free Law Project)", "url": "https://www.courtlistener.com/docket/68229748/sultzer-v-intuitive-surgical-inc/", "date": "2024-02-06" }, { "title": "Complaint, Sultzer v. Intuitive Surgical, Inc., No. 9:24-cv-80137 (S.D. Fla.), Document 1", "publisher": "U.S. District Court for the Southern District of Florida (via CourtListener RECAP)", "url": "https://storage.courtlistener.com/recap/gov.uscourts.flsd.661879/gov.uscourts.flsd.661879.1.0.pdf", "date": "2024-02-06" }, { "title": "Order on Motion to Dismiss, Sultzer v. Intuitive Surgical, Inc., No. 9:24-cv-80137 (S.D. Fla.), Document 39", "publisher": "U.S. District Court for the Southern District of Florida (via CourtListener RECAP)", "url": "https://storage.courtlistener.com/recap/gov.uscourts.flsd.661879/gov.uscourts.flsd.661879.39.0.pdf", "date": "2024-07-11" }, { "title": "Robotic device burned a woman's small intestine during surgery, lawsuit alleges", "publisher": "NBC News", "url": "https://www.nbcnews.com/health/health-news/robotic-device-burned-womans-small-intestine-surgery-lawsuit-alleges-rcna137998", "date": "2024-02-08" }, { "title": "Sultzer v. Intuitive Surgical, Inc.", "publisher": "Law360", "url": "https://www.law360.com/cases/65c2e2172ca3fab37c2c058c", "date": "2024-07-12" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2021-06-amazon-prime-air-mk27-pendleton-crash-field-fire", "url": "https://roboincidents.com/incidents/2021-06-amazon-prime-air-mk27-pendleton-crash-field-fire/", "title": "Amazon MK27 test drone crashes and starts field fire near Pendleton", "summary": "An Amazon Prime Air MK27 prototype lost power on a test flight in eastern Oregon, fell about 160 feet and set several acres of wheat stubble on fire. No one was injured.", "date": "2021-06", "date_precision": "month", "city": "Pendleton", "state": "OR", "country": "US", "category": "drones", "category_name": "Drones", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Amazon Prime Air", "manufacturer": "Amazon", "system": "Amazon Prime Air MK27 prototype delivery drone, about 89 pounds", "companies": [ "Amazon" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "FAA" ], "official_records": [], "outcomes": [ "The crash became public in March 2022, when Business Insider reported on an FAA document describing it." ], "key_facts": [ "An Amazon Prime Air MK27 prototype drone crashed during a test flight in eastern Oregon in June 2021 after its motors failed.", "The drone fell about 160 feet, and a lithium battery fire after impact consumed the aircraft, according to an FAA report described by Business Insider.", "The fire spread to several acres of wheat stubble, according to the FAA report.", "No one was injured; Amazon said no employee or community member was at risk.", "The crash was not publicly reported until March 2022, about nine months later." ], "tags": [ "amazon-prime-air", "mk27", "test-flight", "battery-fire", "wildfire" ], "sources": [ { "title": "Amazon delivery drone crash sparked acres-wide fire in Oregon: FAA", "publisher": "DroneDJ", "url": "https://dronedj.com/2022/03/25/amazon-delivery-drone-crash-oregon/", "date": "2022-03-25" }, { "title": "Amazon delivery drone crashed and caused fire says FAA report", "publisher": "DroneXL", "url": "https://dronexl.co/2022/04/06/amazon-delivery-drone-crashed-faa", "date": "2022-04-06" }, { "title": "Why Amazon's MK30 Drones Crashed: Sensor Issues Exposed", "publisher": "DroneXL", "url": "https://dronexl.co/2025/05/16/why-amazon-mk30-drones-crashed-sensor-issues-exposed", "date": "2025-05-16" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2021-tesla-giga-texas-engineer-injured-by-industrial-robot", "url": "https://roboincidents.com/incidents/2021-tesla-giga-texas-engineer-injured-by-industrial-robot/", "title": "Tesla engineer injured by industrial robot at Giga Texas in 2021", "summary": "An engineer at Tesla's Austin factory was injured by an industrial robot in 2021. Witness accounts published in 2023 describe a more serious event than Tesla's injury report.", "date": "2021", "date_precision": "year", "city": "Austin", "state": "TX", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Tesla", "manufacturer": "KUKA (according to Elon Musk)", "system": "Industrial robot arm used to handle freshly cast aluminum vehicle parts", "companies": [ "Tesla" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Tesla recorded the injury in a report filed with Travis County as a laceration, cut or open wound caused by a robot.", "In December 2023 Elon Musk said the injury involved an ordinary Kuka industrial robot arm and criticized media coverage that he said implied Tesla's Optimus humanoid robot was involved." ], "key_facts": [ "A 2021 injury report that Tesla filed with Travis County, Texas, records an engineer suffering a laceration, cut or open wound caused by a robot at its Austin factory.", "The Information reported in late 2023, citing two witnesses, that a robot pinned the engineer and drew blood from his back and arm before a coworker pressed an emergency stop.", "According to that account, the engineer had begun work on three robots without realizing that only two had been shut down.", "Elon Musk responded in December 2023 that the injury was two years old and involved a standard Kuka industrial robot arm, not Tesla's Optimus humanoid robot.", "Tesla did not respond to Fortune's request for comment on the incident." ], "tags": [ "automotive", "emergency-stop", "injury-report", "media-dispute", "robot-arm" ], "sources": [ { "title": "A Tesla factory robot reportedly attacked a worker and left them bleeding. This could become a new reality in the increasingly automated workplace", "publisher": "Fortune", "url": "https://fortune.com/2023/12/27/tesla-factory-robot-worker-attack-injury/", "date": "2023-12-27" }, { "title": "Tesla engineer attacked by robot at company's Giga Texas factory, report says", "publisher": "The Independent (via Yahoo News)", "url": "https://www.yahoo.com/news/tesla-engineer-attacked-robot-company-092408662.html", "date": "2023-12-27" }, { "title": "Elon Musk Is Mad About Reporting On Robots Injuring His Workers, And He Has A Point", "publisher": "Jalopnik", "url": "https://jalopnik.com/elon-musk-is-mad-about-reporting-on-his-robots-injuring-1851128923", "date": "2023-12-28" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2020-02-20-smart-columbus-easymile-linden-leap-sudden-stop", "url": "https://roboincidents.com/incidents/2020-02-20-smart-columbus-easymile-linden-leap-sudden-stop/", "title": "EasyMile shuttle's sudden stop throws passenger from seat in Columbus", "summary": "An EasyMile autonomous shuttle on Columbus's Linden LEAP route braked suddenly at 7.1 mph on February 20, 2020, and a passenger fell from her seat. NHTSA then halted rides.", "date": "2020-02-20", "date_precision": "day", "city": "Columbus", "state": "OH", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Smart Columbus (Linden LEAP pilot; local operator EmpowerBus)", "manufacturer": "EasyMile", "system": "EasyMile low-speed autonomous shuttle operating the Linden LEAP neighborhood route with an on-board operator", "companies": [ "EasyMile" ], "autonomy_mode": "autonomous-with-safety-operator", "autonomy_mode_name": "Autonomous, safety operator present", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NHTSA" ], "official_records": [], "outcomes": [ "NHTSA ordered EasyMile to suspend passenger service for 16 shuttles in 10 US cities in late February 2020.", "In May 2020 NHTSA set conditions for lifting the suspension under a Safety Passenger Enhancement Plan that added seat belts, signage and audio alerts, and operator training.", "Smart Columbus said the stop was caused by a slight deviation in the vehicle's steering that triggered an internal safety mechanism." ], "key_facts": [ "The Linden LEAP shuttle was traveling 7.1 mph when it braked suddenly on February 20, 2020, in the Linden neighborhood of Columbus, Ohio.", "Two passengers and a human operator were on board, and a 44-year-old passenger fell from her seat.", "NHTSA suspended passenger operations for 16 EasyMile shuttles in 10 US cities after the incident.", "Smart Columbus attributed the stop to a slight deviation in the shuttle's steering.", "EasyMile said braking was the safest response but that it unfortunately led to a passenger falling." ], "tags": [ "shuttle", "sudden-stop", "passenger-fall", "nhtsa", "pilot-program" ], "sources": [ { "title": "NHTSA lifts suspension of EasyMile vehicles", "publisher": "Smart Cities Dive", "url": "https://www.smartcitiesdive.com/news/smart-columbus-NHTSA-autonomous-shuttles-linden-leap/573107/", "date": "2020-05-19" }, { "title": "Slight deviation in steering caused February sudden stop incident of Linden LEAP shuttle", "publisher": "Mass Transit", "url": "https://www.masstransitmag.com/alt-mobility/autonomous-vehicles/article/21138801/slight-deviation-in-steering-caused-february-sudden-stop-incident-of-linden-leap-shuttle", "date": "2020-05-19" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2019-10-21-starship-university-of-pittsburgh-wheelchair-curb-cut", "url": "https://roboincidents.com/incidents/2019-10-21-starship-university-of-pittsburgh-wheelchair-curb-cut/", "title": "Pitt pauses Starship robots after wheelchair user reports blocked curb cut", "summary": "A wheelchair user said a Starship delivery robot sat in a curb cut on Forbes Avenue and blocked her way out of traffic. The University of Pittsburgh paused the robots for days.", "date": "2019-10-21", "date_precision": "day", "city": "Pittsburgh", "state": "PA", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "disruption", "severity_name": "Disruption", "fatalities": 0, "injuries": 0, "operator": "Starship Technologies", "manufacturer": "Starship Technologies", "system": "Starship six-wheeled sidewalk delivery robot", "companies": [ "Starship Technologies" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "disputed", "status_name": "Disputed", "agencies": [], "official_records": [], "outcomes": [ "The University of Pittsburgh paused testing of the robots on October 21, 2019, about two hours after the report was posted.", "Starship changed the robots' mapping to leave more room at the intersection, and supervised testing resumed on October 25, 2019." ], "key_facts": [ "On October 21, 2019, a University of Pittsburgh doctoral student who uses a power wheelchair reported that a Starship delivery robot blocked a curb cut on Forbes Avenue as she crossed.", "The University of Pittsburgh paused testing of the robots about two hours after her report was posted online.", "Starship later said footage from the robot showed she was able to reach the sidewalk, a description that differed from her account.", "Starship updated the robots' maps to leave more space at the intersection before testing resumed on October 25, 2019.", "About 25 Starship robots were being tested in the Oakland neighborhood at the time, according to the Tribune-Review." ], "tags": [ "starship", "accessibility", "wheelchair", "campus", "curb-cut" ], "sources": [ { "title": "Access Concerns Take Robots Off Oakland, Pa., Sidewalks", "publisher": "Tribune-Review (via Government Technology)", "url": "https://www.govtech.com/products/Access-Concerns-Take-Robots-Off-Oakland-Pa-Sidewalks.html", "date": "2019-10-25" }, { "title": "Food Delivery Robot Resumes Testing On Pitt Campus", "publisher": "CBS Pittsburgh", "url": "https://www.cbsnews.com/amp/pittsburgh/news/food-delivery-robot-resumes-testing-on-pitt-campus", "date": "2019-10-25" }, { "title": "Starship's Robots Pulled From University of Pittsburgh After Accessibility Incident", "publisher": "The Spoon", "url": "https://thespoon.tech/starships-robots-pulled-from-university-of-pittsburgh-after-accessibility-incident/", "date": "2019-10-24" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2018-12-14-kiwibot-uc-berkeley-battery-fire", "url": "https://roboincidents.com/incidents/2018-12-14-kiwibot-uc-berkeley-battery-fire/", "title": "Kiwibot delivery robot catches fire on UC Berkeley campus", "summary": "A Kiwibot food delivery robot caught fire on the UC Berkeley campus. No one was hurt. Kiwi blamed a defective battery installed by mistake and briefly pulled its fleet.", "date": "2018-12-14", "date_precision": "day", "city": "Berkeley", "state": "CA", "country": "US", "category": "delivery-robots", "category_name": "Delivery robots", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Kiwi (Kiwi Campus)", "manufacturer": "Kiwi (Kiwi Campus)", "system": "Kiwibot sidewalk food delivery robot", "companies": [ "Kiwibot" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Kiwi withdrew all of its robots from service after the fire and completed pending orders by hand.", "Kiwi said it added software to monitor the condition of each robot's battery." ], "key_facts": [ "A Kiwibot food delivery robot caught fire on the University of California, Berkeley campus on Friday, December 14, 2018.", "No injuries were reported and the fire was put out quickly.", "Kiwi attributed the fire to human error, saying a defective battery had been installed in place of a working one and went into thermal runaway.", "Kiwi pulled its whole fleet from the field after the fire and delivered outstanding orders by hand.", "More than 100 Kiwibots were operating in Berkeley at the time, according to MIT Technology Review." ], "tags": [ "kiwibot", "battery-fire", "campus", "thermal-runaway" ], "sources": [ { "title": "A Delivery Robot Burst Into Flames in California", "publisher": "Futurism", "url": "https://futurism.com/delivery-robot-caught-fire-california", "date": "2018-12-17" }, { "title": "A food delivery robot burst into flames—and now people have made a candlelight vigil for it", "publisher": "MIT Technology Review", "url": "https://www.technologyreview.com/the-download/612618/a-food-delivery-robot-burst-into-flames-and-now-people-have-made-a-candlelit/", "date": "2018-12-17" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2018-12-05-amazon-robbinsville-bear-repellent-automated-machine", "url": "https://roboincidents.com/incidents/2018-12-05-amazon-robbinsville-bear-repellent-automated-machine/", "title": "Automated machine punctures bear repellent at Amazon Robbinsville site", "summary": "An automated machine punctured a can of bear repellent at Amazon's Robbinsville, New Jersey fulfillment center on December 5, 2018, sending about two dozen workers to hospitals.", "date": "2018-12-05", "date_precision": "day", "city": "Robbinsville", "state": "NJ", "country": "US", "category": "warehouse-robots", "category_name": "Warehouse robots", "severity": "serious-injury", "severity_name": "Serious injury", "fatalities": 0, "injuries": 54, "operator": "Amazon", "manufacturer": "", "system": "Automated machine inside an Amazon fulfillment center (not further identified by officials)", "companies": [ "Amazon" ], "autonomy_mode": "unknown", "autonomy_mode_name": "Not established", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Robbinsville Township Fire Department" ], "official_records": [], "outcomes": [ "Twenty-four workers were taken to five hospitals on December 5, 2018, and about 30 more were treated at the warehouse.", "Amazon said that evening that all affected employees had been released or were expected to be released from hospital within 24 hours, and that a full investigation was under way." ], "key_facts": [ "On December 5, 2018, a 9-ounce can of bear repellent was punctured by an automated machine at Amazon's fulfillment center in Robbinsville, New Jersey, according to a township spokesman.", "Twenty-four employees were taken to five hospitals and about 30 others were treated at the warehouse for breathing difficulty and burning in the eyes and throat.", "At least one worker was reported in critical condition that afternoon but was expected to be released.", "The fumes were confined to part of the building's third floor, which was cleared for several hours; the rest of the warehouse was not evacuated.", "Amazon said a damaged aerosol can had dispersed strong fumes in a contained area and that a full investigation was under way." ], "tags": [ "amazon", "fulfillment-center", "hazmat", "chemical-exposure", "mass-casualty" ], "sources": [ { "title": "Amazon workers treated after bear repellent releases fumes", "publisher": "Associated Press (via KSL.com)", "url": "https://www.ksl.com/article/46441203", "date": "2018-12-05" }, { "title": "Bear Repellent Hospitalizes 24 NJ Amazon Workers", "publisher": "New York Daily News (via Firehouse)", "url": "https://www.firehouse.com/rescue/hazardous-materials/news/21035506/bear-repellent-hospitalizes-sickens-nj-amazon-warehouse-workers-firefighters-video", "date": "2018-12-05" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2018-03-23-tesla-autopilot-mountain-view-us101-barrier-fatality", "url": "https://roboincidents.com/incidents/2018-03-23-tesla-autopilot-mountain-view-us101-barrier-fatality/", "title": "Tesla Model X on Autopilot hits highway barrier in Mountain View", "summary": "A Tesla Model X using Autopilot steered into a gore area on US-101 in Mountain View on March 23, 2018, and hit a damaged crash attenuator, killing the 38-year-old driver.", "date": "2018-03-23", "date_precision": "day", "city": "Mountain View", "state": "CA", "country": "US", "category": "driver-assistance", "category_name": "Driver assistance", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 1, "operator": "Private owner (driver of the Tesla)", "manufacturer": "Tesla", "system": "2017 Tesla Model X P100D using Traffic-Aware Cruise Control and Autosteer (Tesla Autopilot)", "companies": [ "Tesla" ], "autonomy_mode": "driver-assistance", "autonomy_mode_name": "Driver assistance (Level 2)", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NTSB", "NHTSA" ], "official_records": [], "outcomes": [ "The NTSB issued reports HSR-19-01 and HAR-20-01 with recommendations H-19-013 and H-20-001 through H-20-009 to NHTSA, OSHA, SAE International, Apple and other device makers.", "The NTSB found the crash attenuator was damaged and nonoperational because an earlier crash had not been reported and repaired in a timely manner.", "In a later, separate action, Tesla filed recall 23V-838 on December 12, 2023, covering 2,031,220 vehicles, to add Autosteer driver-engagement controls after NHTSA's Autopilot investigation EA22-002." ], "key_facts": [ "The crash happened at 9:27 a.m. on March 23, 2018, on southbound US-101 at the State Route 85 interchange in Mountain View, California.", "The Tesla Model X struck a damaged, nonoperational crash attenuator at about 71 mph, and its high-voltage battery was breached, starting a fire.", "The NTSB found the probable cause was Tesla's Autopilot steering the SUV into a highway gore area due to system limitations, and the driver's lack of response due to distraction.", "The NTSB said the driver was likely distracted by a cell phone game application and had overrelied on Autopilot.", "The NTSB cited Tesla's ineffective monitoring of driver engagement as a contributing factor." ], "tags": [ "tesla", "autopilot", "highway", "driver-distraction", "fire", "ntsb" ], "sources": [ { "title": "Collision Between a Sport Utility Vehicle Operating With Partial Driving Automation and a Crash Attenuator", "publisher": "NTSB", "url": "https://www.ntsb.gov/investigations/Pages/HWY18FH011.aspx", "date": null }, { "title": "NTSB Findings Put Pressure on Tesla to Change Autopilot", "publisher": "Consumer Reports", "url": "https://www.consumerreports.org/car-safety/ntsb-findings-put-pressure-on-tesla-to-change-autopilot", "date": "2020-02-25" }, { "title": "Part 573 Safety Recall Report 23V-838", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/rcl/2023/RCLRPT-23V838-8276.PDF", "date": "2023-12-12" }, { "title": "ODI Resume: Investigation EA22002 (Autopilot System Driver Controls), closing resume", "publisher": "NHTSA", "url": "https://static.nhtsa.gov/odi/inv/2022/INCLA-EA22002-14498.pdf", "date": "2024-04-25" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2018-03-18-uber-atg-tempe-pedestrian-fatality", "url": "https://roboincidents.com/incidents/2018-03-18-uber-atg-tempe-pedestrian-fatality/", "title": "Uber self-driving test vehicle fatally strikes pedestrian in Tempe", "summary": "An Uber test vehicle operating in autonomous mode with a safety operator struck and killed a 49-year-old pedestrian crossing N. Mill Avenue in Tempe on March 18, 2018.", "date": "2018-03-18", "date_precision": "day", "city": "Tempe", "state": "AZ", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Uber Advanced Technologies Group", "manufacturer": "Volvo (vehicle), Uber (self-driving system)", "system": "Modified 2017 Volvo XC90 with Uber's developmental automated driving system", "companies": [ "Uber" ], "autonomy_mode": "autonomous-with-safety-operator", "autonomy_mode_name": "Autonomous, safety operator present", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NTSB", "Tempe Police Department", "Maricopa County Attorney's Office" ], "official_records": [], "outcomes": [ "Uber suspended its self-driving testing in Arizona, Pittsburgh, San Francisco and Toronto after the crash and later ended its Arizona program, the Associated Press reported in May 2018.", "The NTSB determined the probable cause was the vehicle operator's failure to monitor the driving environment and the automated system, and issued six safety recommendations (report HAR-19-03).", "The vehicle's backup driver, originally charged with negligent homicide, pleaded guilty to endangerment and was sentenced to three years of probation in July 2023." ], "key_facts": [ "The crash occurred at 9:58 p.m. on March 18, 2018, on northbound N. Mill Avenue in Tempe, Arizona, where the pedestrian was crossing outside a crosswalk.", "The NTSB found that Uber's automated driving system detected the pedestrian 5.6 seconds before impact but never accurately classified her or predicted her path.", "Video showed the vehicle operator looking at a personal cell phone for an extended period; she looked back at the road about one second before impact.", "The NTSB cited Uber Advanced Technologies Group's inadequate safety culture, including ineffective oversight of vehicle operators, as a contributing factor.", "The backup driver pleaded guilty to endangerment in July 2023 and received three years of probation." ], "tags": [ "pedestrian", "night", "safety-operator", "test-vehicle", "ntsb" ], "sources": [ { "title": "Collision Between Vehicle Controlled by Developmental Automated Driving System and Pedestrian", "publisher": "NTSB", "url": "https://www.ntsb.gov/investigations/Pages/HWY18MH010.aspx", "date": "2019-11-19" }, { "title": "Feds: Uber self-driving SUV saw pedestrian, didn't brake in fatal crash", "publisher": "Associated Press via KUTV", "url": "https://kutv.com/news/nation-world/feds-uber-self-driving-suv-saw-pedestrian-didnt-brake-in-fatal-crash", "date": "2018-05-24" }, { "title": "Backup driver pleads guilty to endangerment in Tempe self-driving Uber death", "publisher": "KJZZ", "url": "https://kjzz.org/content/1853341/backup-driver-pleads-guilty-endangerment-tempe-self-driving-uber-death", "date": "2023-07-28" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2017-11-08-keolis-navya-las-vegas-shuttle-truck-collision", "url": "https://roboincidents.com/incidents/2017-11-08-keolis-navya-las-vegas-shuttle-truck-collision/", "title": "Truck backs into Navya driverless shuttle on its first day in Las Vegas", "summary": "A delivery truck backing into an alley struck a stopped Navya autonomous shuttle carrying seven passengers in downtown Las Vegas on November 8, 2017. No one was hurt.", "date": "2017-11-08", "date_precision": "day", "city": "Las Vegas", "state": "NV", "country": "US", "category": "autonomous-vehicles", "category_name": "Autonomous vehicles", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Keolis North America", "manufacturer": "Navya", "system": "2017 Navya Arma autonomous shuttle operating on a fixed 0.6-mile downtown loop with an on-board attendant", "companies": [ "Keolis", "Navya" ], "autonomy_mode": "autonomous-with-safety-operator", "autonomy_mode_name": "Autonomous, safety operator present", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NTSB" ], "official_records": [], "outcomes": [ "The NTSB published Highway Accident Brief HAB-19-06 in July 2019, citing the truck driver's actions and the attendant's lack of ready access to a manual controller.", "Keolis adopted a policy letting attendants take the hand-held controller out of storage at the start of a trip and keep it available throughout." ], "key_facts": [ "The collision happened at about 12:07 p.m. on November 8, 2017, on South 6th Street in downtown Las Vegas.", "The Navya Arma shuttle had seven passengers and one attendant aboard, and no one on the shuttle or in the truck was injured.", "According to Navya's incident report cited by the NTSB, the shuttle detected the truck 147.6 feet away and was nearly stopped when the attendant pressed the emergency stop button.", "The truck's right front tire struck the shuttle 11 seconds after the shuttle stopped.", "The NTSB found the truck driver expected the shuttle to stop farther away, and that the attendant was not positioned to take manual control." ], "tags": [ "shuttle", "low-speed", "truck", "attendant", "ntsb" ], "sources": [ { "title": "Low-Speed Collision Between Truck-Tractor and Autonomous Shuttle", "publisher": "NTSB", "url": "https://www.ntsb.gov/investigations/pages/HWY18FH001.aspx", "date": null }, { "title": "NTSB completes Las Vegas autonomous shuttle crash investigation", "publisher": "METRO Magazine", "url": "https://www.metro-magazine.com/news/ntsb-completes-las-vegas-autonomous-shuttle-crash-investigation", "date": "2019-07-11" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2017-07-17-knightscope-k5-washington-harbour-fountain", "url": "https://roboincidents.com/incidents/2017-07-17-knightscope-k5-washington-harbour-fountain/", "title": "Knightscope K5 security robot falls into fountain at Washington Harbour", "summary": "A Knightscope K5 security robot patrolling the Washington Harbour complex in Georgetown rolled down steps into a fountain. No one was hurt and the robot was replaced.", "date": "2017-07-17", "date_precision": "day", "city": "Washington", "state": "DC", "country": "US", "category": "security-robots", "category_name": "Security robots", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "Washington Harbour (MRP Realty)", "manufacturer": "Knightscope", "system": "Knightscope K5 Autonomous Data Machine security robot", "companies": [ "Knightscope" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Knightscope said a replacement robot was on site within 48 hours and that the client received a month's credit.", "Knightscope said on July 28, 2017, that its review found an algorithm had not detected an uneven surface and that it was working on a fix." ], "key_facts": [ "A Knightscope K5 security robot fell down a short flight of steps into a fountain at the Washington Harbour complex in Washington, DC, on July 17, 2017.", "No people were injured when the robot went into the water.", "The robot had been deployed at the site only recently and was still mapping the grounds, according to news reports.", "Knightscope said the robot skidded on a loose brick surface after an algorithm failed to detect the uneven ground, and ruled out sabotage.", "Knightscope said it delivered a replacement robot within 48 hours." ], "tags": [ "knightscope", "k5", "fountain", "navigation-failure" ], "sources": [ { "title": "Robot that dived into Washington, D.C., fountain not victim of 'foul play'", "publisher": "Reuters (via Yahoo News)", "url": "https://www.yahoo.com/news/robot-dived-washington-d-c-fountain-not-victim-172501082.html", "date": "2017-07-28" }, { "title": "Security Robot Plunges Into Fountain", "publisher": "Security Today", "url": "https://securitytoday.com/Articles/2017/07/18/Security-Robot-Plunges-Into-Fountain.aspx", "date": "2017-07-18" }, { "title": "Security robot 'in critical condition' after nearly drowning on the job", "publisher": "CNN Wire (via WTKR)", "url": "https://www.wtkr.com/2017/07/21/security-robot-in-critical-condition-after-nearly-drowning-on-the-job", "date": "2017-07-21" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2016-07-07-knightscope-k5-stanford-shopping-center-toddler", "url": "https://roboincidents.com/incidents/2016-07-07-knightscope-k5-stanford-shopping-center-toddler/", "title": "Knightscope K5 security robot knocks down toddler at Palo Alto mall", "summary": "A 300-pound Knightscope K5 security robot collided with a 16-month-old boy at Stanford Shopping Center, leaving him with a scraped, swollen leg. The mall suspended its robots.", "date": "2016-07-07", "date_precision": "day", "city": "Palo Alto", "state": "CA", "country": "US", "category": "security-robots", "category_name": "Security robots", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Stanford Shopping Center", "manufacturer": "Knightscope", "system": "Knightscope K5 autonomous security robot, about 5 feet tall and 300 pounds", "companies": [ "Knightscope" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Stanford Shopping Center took its security robots out of service while it investigated, as reported on July 14, 2016.", "Knightscope issued a public apology on July 14, 2016, and invited the family to its Mountain View headquarters." ], "key_facts": [ "A Knightscope K5 security robot collided with a 16-month-old boy at Stanford Shopping Center in Palo Alto, California, on July 7, 2016.", "The child had a scrape on his leg and a bruise with minor swelling; no serious injuries were reported.", "Knightscope said the robot veered away and stopped before the child backed into it, while the family said the robot struck him and kept moving.", "The shopping center stopped using its security robots while it investigated the collision.", "The K5 involved stands about 5 feet tall, weighs about 300 pounds and typically patrols at around 1 mph, according to Knightscope." ], "tags": [ "knightscope", "k5", "child", "shopping-mall", "pedestrian" ], "sources": [ { "title": "K5 Security Robot Runs Over Toddler at California Mall [Updated]", "publisher": "The Robot Report", "url": "https://www.therobotreport.com/k5-security-robot-runs-over-toddler-at-california-mall-updated/", "date": "2016-07-13" }, { "title": "Investigation begins on robot security after child is hurt", "publisher": "CNBC", "url": "https://www.cnbc.com/2016/07/14/investigation-begins-on-robot-security-after-child-is-hurt.html", "date": "2016-07-14" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2016-06-18-ajin-usa-cusseta-robotic-cell-fatality", "url": "https://roboincidents.com/incidents/2016-06-18-ajin-usa-cusseta-robotic-cell-fatality/", "title": "Temporary worker crushed in robotic cell at Ajin USA plant in Cusseta", "summary": "A 20-year-old temporary worker at auto parts maker Ajin USA in Cusseta, Alabama, was fatally crushed on June 18, 2016, when a robot restarted as she cleared a sensor fault.", "date": "2016-06-18", "date_precision": "day", "city": "Cusseta", "state": "AL", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Joon LLC, doing business as Ajin USA", "manufacturer": "", "system": "Robotic station on an automotive stamping and assembly line", "companies": [ "Ajin USA" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "OSHA", "Occupational Safety and Health Review Commission" ], "official_records": [], "outcomes": [ "On December 14, 2016, OSHA cited Ajin USA and two staffing agencies for 27 violations and proposed $2,565,621 in penalties, and placed Ajin in its Severe Violator Enforcement Program.", "In September 2020 a federal court ordered Ajin USA to pay a $500,000 fine and $1 million in restitution to the worker's estate after it pleaded guilty to a willful violation of an OSHA standard.", "On February 10, 2023, an administrative law judge upheld most of the contested citations, and OSHA said Ajin USA would pay more than $1.3 million in penalties." ], "key_facts": [ "On June 18, 2016, a 20-year-old temporary worker at Ajin USA in Cusseta, Alabama, was crushed inside a robotic station on an assembly line that made parts for Hyundai and Kia.", "OSHA said the line had stopped and four workers entered the robotic station to clear a sensor fault when the robot restarted abruptly.", "OSHA cited Ajin USA for willful violations including failing to use lockout procedures and letting workers enter a robotic cell without shutting down hazardous energy.", "Ajin USA pleaded guilty to a willful violation of an OSHA standard and in September 2020 was ordered to pay a $500,000 fine and $1 million in restitution.", "After a contest lasting more than six years, an administrative law judge affirmed most citations in February 2023, and OSHA said the company would pay more than $1.3 million in penalties." ], "tags": [ "automotive", "temporary-worker", "lockout", "willful-violation", "criminal-plea", "robotic-cell" ], "sources": [ { "title": "Alabama auto parts supplier to Kia and Hyundai, staffing agencies face $2.5M in fines after robot fatally crushes young bride-to-be", "publisher": "U.S. Department of Labor, OSHA", "url": "https://www.dol.gov/newsroom/releases/osha/osha20161214-0", "date": "2016-12-14" }, { "title": "Administrative law judge affirms citations; Alabama automotive parts supplier to pay $1.3M in penalties after 20-year-old worker's 2016 death", "publisher": "U.S. Department of Labor, OSHA", "url": "https://www.dol.gov/newsroom/releases/osha/osha20230308-0", "date": "2023-03-08" }, { "title": "23 violations issued to Ala. plant after woman crushed to death by robotic machine", "publisher": "Associated Press (via CBS News)", "url": "https://www.cbsnews.com/news/aijin-usa-plant-issued-23-violations-regina-allen-elsea-death-robotic-machine/", "date": "2016-12-14" }, { "title": "FY16 federal and state fatality summaries (fy16_federal-state_summaries.csv)", "publisher": "OSHA", "url": "https://www.osha.gov/sites/default/files/fy16_federal-state_summaries.csv", "date": null } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2016-05-07-tesla-autopilot-williston-truck-collision-fatality", "url": "https://roboincidents.com/incidents/2016-05-07-tesla-autopilot-williston-truck-collision-fatality/", "title": "Tesla Model S on Autopilot hits crossing truck near Williston, Florida", "summary": "A Tesla Model S using Autopilot features struck a semitrailer turning across US-27A near Williston, Florida, on May 7, 2016, killing the car's driver.", "date": "2016-05-07", "date_precision": "day", "city": "Williston", "state": "FL", "country": "US", "category": "driver-assistance", "category_name": "Driver assistance", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Private owner (driver of the Tesla)", "manufacturer": "Tesla", "system": "2015 Tesla Model S 70D using Traffic-Aware Cruise Control and Autosteer (Tesla Autopilot)", "companies": [ "Tesla" ], "autonomy_mode": "driver-assistance", "autonomy_mode_name": "Driver assistance (Level 2)", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NTSB", "NHTSA" ], "official_records": [], "outcomes": [ "NHTSA closed its defect investigation on January 19, 2017, without identifying a safety-related defect or ordering a recall.", "The NTSB completed Highway Accident Report HAR-17-02 in September 2017 and issued safety recommendations H-17-037 through H-17-043.", "Tesla changed Autopilot in September 2016 to add hands-off-wheel warnings and to lock out Autosteer for drivers who repeatedly ignored them, according to Consumer Reports." ], "key_facts": [ "The crash happened at 4:36 p.m. on Saturday, May 7, 2016, on US Highway 27A west of Williston, Florida.", "NTSB vehicle data showed the Tesla driver was using Traffic-Aware Cruise Control and Autosteer, both part of Tesla's Autopilot suite.", "The NTSB found the probable cause was the truck driver's failure to yield combined with the car driver's inattention due to overreliance on vehicle automation.", "The NTSB said the Tesla's operational design contributed by permitting prolonged driver disengagement and use of the automation in ways inconsistent with Tesla's guidance.", "NHTSA closed its own investigation in January 2017 without ordering a recall." ], "tags": [ "tesla", "autopilot", "truck", "driver-inattention", "ntsb" ], "sources": [ { "title": "Collision Between a Car Operating With Automated Vehicle Control Systems and a Tractor-Semitrailer Truck", "publisher": "NTSB", "url": "https://www.ntsb.gov/investigations/Pages/HWY16FH018.aspx", "date": null }, { "title": "Safety Agency Closes Tesla Investigation Without Ordering Recall", "publisher": "Consumer Reports", "url": "https://www.consumerreports.org/national-highway-traffic-safety-administration/safety-agency-closes-tesla-investigation-without-ordering-recall", "date": "2017-01-19" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2015-12-09-washington-bottling-warehouse-laser-guided-vehicle-fatality", "url": "https://roboincidents.com/incidents/2015-12-09-washington-bottling-warehouse-laser-guided-vehicle-fatality/", "title": "Driverless forklift crushes warehouse worker at Washington bottler", "summary": "A 45-year-old dock coordinator at a Washington State water bottling warehouse was crushed on December 9, 2015, when the forks of a laser guided vehicle lowered onto him.", "date": "2015-12-09", "date_precision": "day", "city": "", "state": "WA", "country": "US", "category": "warehouse-robots", "category_name": "Warehouse robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Unnamed bottled water manufacturer (not identified in the report)", "manufacturer": "", "system": "Laser guided vehicle (driverless forklift) moving pallets of bottled water", "companies": [], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Washington State Department of Labor & Industries" ], "official_records": [], "outcomes": [ "The Washington State FACE program published a fatality narrative on May 10, 2018, with recommendations on procedures and training for automated guided industrial vehicles." ], "key_facts": [ "On December 9, 2015, a 45-year-old warehouse dock coordinator in Washington State was fatally crushed by the forks of a driverless laser guided vehicle.", "Investigators believe he was trying to pull a strand of plastic wrap from under the raised forks without first pressing the vehicle's emergency stop.", "Because the vehicle was not in emergency-stop mode, it reset when the obstruction was cleared and lowered its forks onto him, according to the state's FACE program.", "Employees told investigators that loose plastic wrap from pallets frequently triggered the vehicles' obstacle alarms.", "The manufacturer's manual required an emergency stop before removing an obstacle, and warning signs on the vehicle told workers not to stand under raised forks." ], "tags": [ "agv", "driverless-forklift", "emergency-stop", "state-face", "bottling" ], "sources": [ { "title": "Warehouse Worker Crushed by Forks of Laser Guided Vehicle", "publisher": "Washington State FACE Program (via eLCOSH)", "url": "https://www.elcosh.org/document/4342/d001598/Warehouse+Worker+Crushed+by+Forks+of+Laser+Guided+Vehicle.html", "date": "2018-05-10" }, { "title": "Fatality Narrative: Warehouse Worker Crushed by Forks of Laser Guided Vehicle - Washington", "publisher": "Washington State Department of Labor and Industries (CDC Stacks)", "url": "https://stacks.cdc.gov/view/cdc/228756", "date": "2018-05-10" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2015-07-07-ventra-ionia-robotic-weld-cell-maintenance-fatality", "url": "https://roboincidents.com/incidents/2015-07-07-ventra-ionia-robotic-weld-cell-maintenance-fatality/", "title": "Maintenance technician killed by robot at Ventra Ionia auto parts plant", "summary": "A 57-year-old maintenance technician was crushed by a robot in a trailer-hitch assembly line at the Ventra Ionia Main plant in Ionia, Michigan, on July 7, 2015.", "date": "2015-07-07", "date_precision": "day", "city": "Ionia", "state": "MI", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Ventra Ionia Main LLC (a Flex-N-Gate affiliate)", "manufacturer": "Prodomax Automation (assembly line integrator); robot makers named in the lawsuit were later dismissed", "system": "Robotic assembly and welding line for trailer hitch receiver assemblies, divided into guarded zones", "companies": [ "Ventra Ionia" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "MIOSHA" ], "official_records": [], "outcomes": [ "In January 2016 Michigan regulators proposed a $7,000 fine against Ventra Ionia Main, saying a lockout device could have stopped the machine.", "In March 2017 the technician's husband filed a federal wrongful-death lawsuit against six companies involved in building, installing and servicing the line.", "In September 2021 a federal judge allowed a product liability claim over the line's control programming to proceed against integrator Prodomax Automation.", "In November 2021 the estate reached a confidential settlement with Prodomax partway through trial." ], "key_facts": [ "On July 7, 2015, a maintenance technician at Ventra Ionia Main in Ionia, Michigan, was fatally crushed by a robot; OSHA's fatality summary records the cause as a robotic arm.", "Michigan inspectors said a lockout device could have halted the machine when the technician entered the robotic cell, and proposed a $7,000 fine.", "A 2017 wrongful-death lawsuit alleged that a robot from an adjoining section entered the section where the technician was working and that safety systems failed.", "A federal court's 2021 account, as summarized in legal commentary, was that the technician climbed over a wall without using the zone's entry procedure and that the robot operated as programmed.", "The 2021 ruling treated the line's control programming as an integral part of a product for purposes of Michigan's product liability statute." ], "tags": [ "automotive", "maintenance", "product-liability", "software", "lockout", "weld-cell" ], "sources": [ { "title": "FY15 Fatalities and Catastrophes To Date", "publisher": "OSHA", "url": "https://www.osha.gov/sites/default/files/fy15_federal-state_summaries.pdf", "date": "2016-08-03" }, { "title": "Auto Worker Dies After Being Caught In Robotic Machine", "publisher": "CBS Detroit / Associated Press", "url": "https://www.cbsnews.com/detroit/news/worker-dies-after-being-caught-in-robotic-machine/", "date": "2015-07-08" }, { "title": "Michigan Company Fined In Employee's Death By Robot", "publisher": "CBS Detroit / Associated Press", "url": "https://www.cbsnews.com/detroit/news/michigan-company-fined-in-employees-death-by-robot/", "date": "2016-01-30" }, { "title": "Lawsuit: Malfunctioning robot killed Michigan woman at work", "publisher": "Fox News / Newser", "url": "https://www.foxnews.com/tech/lawsuit-malfunctioning-robot-killed-michigan-woman-at-work", "date": "2017-03-15" }, { "title": "Widower can proceed in lawsuit against robot installation firm", "publisher": "Business Insurance", "url": "https://www.businessinsurance.com/widower-can-proceed-in-lawsuit-against-robot-installation-firm-william-holbrook/", "date": "2020-11-09" }, { "title": "Unintended Consequences for Software Liability?", "publisher": "Drug & Device Law", "url": "https://www.druganddevicelawblog.com/2021/11/unintended-consequences-for-software-liability.html", "date": "2021-11-26" }, { "title": "Man Whose Wife Was Killed by Factory Robot Settles Mid-Trial", "publisher": "Bloomberg Law", "url": "https://news.bloomberglaw.com/litigation/man-whose-wife-was-killed-by-factory-robot-settles-mid-trial", "date": "2021-11-09" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2013-06-16-nissan-smyrna-articulating-robot-maintenance-fatality", "url": "https://roboincidents.com/incidents/2013-06-16-nissan-smyrna-articulating-robot-maintenance-fatality/", "title": "Nissan maintenance technician killed by robot at Smyrna assembly plant", "summary": "A 43-year-old maintenance technician at Nissan's Smyrna, Tennessee plant was struck and killed by an articulating robot on June 16, 2013, while replacing its gears.", "date": "2013-06-16", "date_precision": "day", "city": "Smyrna", "state": "TN", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Nissan North America", "manufacturer": "", "system": "Articulating industrial robot undergoing gear replacement at a vehicle assembly plant", "companies": [ "Nissan" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "OSHA's fiscal year 2013 summary of workplace fatalities records the death as a worker struck and killed by an articulating robot while replacing robot gears." ], "key_facts": [ "On June 16, 2013, a maintenance technician was killed at Nissan North America's vehicle assembly plant in Smyrna, Tennessee.", "OSHA's national fatality summary for fiscal year 2013 says the worker was struck and killed by an articulating robot while replacing the robot's gears.", "Local radio station WGNS reported that the accident happened at about 1:30 a.m. and that the technician was 43 and had worked for Nissan for 21 years.", "It was the second death at the Smyrna plant in under two months, following the death of a contractor's employee in the paint facility in April 2013." ], "tags": [ "automotive", "maintenance", "articulating-robot", "osha-fatality-list" ], "sources": [ { "title": "FY13 Fatalities and Catastrophes To Date", "publisher": "OSHA", "url": "https://www.osha.gov/sites/default/files/fy13_federal-state_summaries.pdf", "date": null }, { "title": "Update: Name of Employee who Died in Nissan Accident at Smyrna Plant Released", "publisher": "WGNS Radio", "url": "https://www.wgnsradio.com/amp/article/9655/update-name-of-employee-who-died-in-nissan-accident-at-smyrna-plant-released", "date": "2013-06-16" }, { "title": "Robot-Related Fatalities at Work in the United States, 1992–2017", "publisher": "American Journal of Industrial Medicine (via CDC Stacks)", "url": "https://stacks.cdc.gov/view/cdc/230667", "date": "2023-06-01" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2012-08-bacardi-bottling-jacksonville-palletizer-fatality", "url": "https://roboincidents.com/incidents/2012-08-bacardi-bottling-jacksonville-palletizer-fatality/", "title": "Temporary worker crushed by palletizer at Bacardi Bottling in Jacksonville", "summary": "A temporary worker on his first day at Bacardi Bottling in Jacksonville, Florida, was crushed in August 2012 when a palletizing machine was restarted while he cleaned under it.", "date": "2012-08", "date_precision": "month", "city": "Jacksonville", "state": "FL", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Bacardi Bottling Corp.", "manufacturer": "", "system": "Automated palletizing machine on a bottling line", "companies": [ "Bacardi" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "OSHA" ], "official_records": [], "outcomes": [ "On February 11, 2013, OSHA cited Bacardi Bottling Corp. for 12 alleged safety violations, including two willful violations, and proposed $192,000 in penalties.", "OSHA used the case to stress that host employers must train temporary workers on site-specific hazards before they start work." ], "key_facts": [ "In August 2012 a temporary worker was crushed to death by a palletizer at Bacardi Bottling Corp. in Jacksonville, Florida, on his first day on the job.", "OSHA said the worker was cleaning glass from under the palletizer's hoist when another employee restarted the machine.", "OSHA issued two willful citations for failing to develop and use lockout/tagout procedures and failing to train temporary workers on them.", "OSHA proposed $192,000 in penalties across 12 alleged violations on February 11, 2013.", "Bacardi said after the citations that it had retrained employees on lockout/tagout, updated its safety procedures and reviewed its equipment." ], "tags": [ "palletizer", "temporary-worker", "lockout", "osha-citation", "bottling" ], "sources": [ { "title": "US Labor Departments OSHA cites Jacksonville, Fla.-based Bacardi Bottling following death of temporary worker on 1st day", "publisher": "U.S. Department of Labor, OSHA", "url": "https://www.dol.gov/newsroom/releases/osha/osha20130211", "date": "2013-02-11" }, { "title": "Temporary Worker Killed at Bacardi Bottling, OSHA Says Company Failed to Train", "publisher": "EHS Today", "url": "https://www.ehstoday.com/osha/temporary-worker-killed-bacardi-bottling-osha-says-company-failed-train", "date": "2013-02-11" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2009-07-21-golden-state-foods-industry-bakery-robot-fatality", "url": "https://roboincidents.com/incidents/2009-07-21-golden-state-foods-industry-bakery-robot-fatality/", "title": "Golden State Foods bakery worker killed at robotic box sorter in Industry", "summary": "A 40-year-old worker at a Golden State Foods bakery in City of Industry, California, was killed on July 21, 2009, reportedly crushed between a conveyor and a robot arm.", "date": "2009-07-21", "date_precision": "day", "city": "Industry", "state": "CA", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Golden State Foods", "manufacturer": "", "system": "Robotic box-sorting cell with a robot arm and conveyor at an industrial bakery", "companies": [ "Golden State Foods" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Cal/OSHA", "Los Angeles County Sheriff's Department" ], "official_records": [], "outcomes": [ "On July 22, 2009, Cal/OSHA said it had received a complaint and was investigating the death.", "Los Angeles County sheriff's detectives who responded to the scene treated the death as an accident." ], "key_facts": [ "On July 21, 2009, a 40-year-old employee was found dead in a machine at the Golden State Foods bakery in City of Industry, California.", "Cal/OSHA said the company's own safety report stated the worker was removing a jammed package when she was crushed between a conveyor belt and a robot arm.", "Cal/OSHA said it would carry out an independent investigation because information supplied by employers can be inaccurate or incomplete.", "The bakery, a supplier to McDonald's, had not been cited by Cal/OSHA in the previous five years, according to the agency." ], "tags": [ "food-processing", "jam-clearing", "cal-osha", "robot-arm" ], "sources": [ { "title": "State to investigate how La Puente woman was killed by robot arm in Industry bakery", "publisher": "San Gabriel Valley Tribune (via TMCnet)", "url": "https://www.tmcnet.com/usubmit/2009/07/23/4287578.htm", "date": "2009-07-23" }, { "title": "Woman Found Dead at McDonald's Food Processing Plant", "publisher": "Associated Press (via Fox News)", "url": "https://www.foxnews.com/story/woman-found-dead-at-mcdonalds-food-processing-plant", "date": "2009-07-21" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2008-09-09-da-vinci-prostatectomy-harrison-medical-center-washington", "url": "https://roboincidents.com/incidents/2008-09-09-da-vinci-prostatectomy-harrison-medical-center-washington/", "title": "Patient severely injured in 2008 da Vinci prostatectomy in Washington state", "summary": "A patient suffered a rectal laceration and lasting complications in a da Vinci robotic prostatectomy at Harrison Medical Center on September 9, 2008; the case reached the state high court.", "date": "2008-09-09", "date_precision": "day", "city": "", "state": "WA", "country": "US", "category": "surgical-robots", "category_name": "Surgical robots", "severity": "serious-injury", "severity_name": "Serious injury", "fatalities": 0, "injuries": 1, "operator": "Surgeon at Harrison Medical Center, Washington state", "manufacturer": "Intuitive Surgical", "system": "da Vinci Surgical System", "companies": [ "Intuitive Surgical" ], "autonomy_mode": "teleoperated", "autonomy_mode_name": "Teleoperated", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "Claims against the surgeon and the hospital were settled for undisclosed amounts, according to the Associated Press.", "In 2013 a Kitsap County jury found that Intuitive Surgical was not negligent in its warnings or instructions to the surgeon.", "The Washington Court of Appeals affirmed the verdict in 2015.", "On February 9, 2017, the Washington Supreme Court vacated the verdict 6-3 and ordered a new trial, holding that the manufacturer also owed a duty to warn the hospital that bought the system." ], "key_facts": [ "On September 9, 2008, a patient's rectal wall was lacerated during a da Vinci robotic prostatectomy at Harrison Medical Center in Washington state, and the surgeon converted to open surgery.", "According to the Washington Supreme Court's opinion, it was the surgeon's first da Vinci prostatectomy without a proctor, after two proctored procedures.", "The patient had a body mass index of 39 and three prior lower abdominal surgeries, outside the manufacturer's guidance, the court said.", "A Kitsap County jury found for Intuitive Surgical in 2013; the Washington Supreme Court vacated that verdict on February 9, 2017 and ordered a new trial.", "No court has found that the da Vinci system malfunctioned in this operation; the litigation concerned the adequacy of the manufacturer's warnings." ], "tags": [ "da-vinci", "prostatectomy", "duty-to-warn", "jury-verdict", "training" ], "sources": [ { "title": "Taylor v. Intuitive Surgical, Inc., No. 92210-1 (Wash. Feb. 9, 2017)", "publisher": "Washington Supreme Court (via FindLaw)", "url": "https://caselaw.findlaw.com/court/wa-supreme-court/1777420.html", "date": "2017-02-09" }, { "title": "Justices: Makers have duty to warn hospitals about devices", "publisher": "Associated Press (via The Daily Herald, Everett)", "url": "https://www.heraldnet.com/news/justices-makers-have-duty-to-warn-hospitals-about-devices/", "date": "2017-02-09" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2008-04-25-kyodo-america-lawnbott-robotic-mower-recall-laceration-injury", "url": "https://roboincidents.com/incidents/2008-04-25-kyodo-america-lawnbott-robotic-mower-recall-laceration-injury/", "title": "LawnBott robotic mowers recalled after owner cut by still-spinning blade", "summary": "CPSC and Kyodo America recalled about 530 LawnBott robotic lawn mowers on April 25, 2008 after a consumer who lifted a running mower suffered minor cuts from the moving blade.", "date": "2008-04-25", "date_precision": "day", "city": "", "state": "", "country": "US", "category": "consumer-robots", "category_name": "Consumer robots", "severity": "minor-injury", "severity_name": "Minor injury", "fatalities": 0, "injuries": 1, "operator": "Consumer owner", "manufacturer": "Zucchetti Centro Sistemi S.p.A. (Italy); imported by Kyodo America Industries Co. Ltd.", "system": "LawnBott robotic lawn mowers, models LB2000, LB2100, LB3000 and LB3200", "companies": [ "Kyodo America" ], "autonomy_mode": "driverless", "autonomy_mode_name": "Driverless", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "CPSC" ], "official_records": [], "outcomes": [ "On April 25, 2008, the U.S. Consumer Product Safety Commission and Kyodo America announced a recall of about 530 LawnBott robotic mowers (recall number 08-256).", "Owners were told to stop using the mowers and register for a free repair, which the importer expected to have available by the end of June 2008." ], "key_facts": [ "About 530 LawnBott robotic lawn mowers were recalled in the United States on April 25, 2008 because of a laceration hazard.", "The Consumer Product Safety Commission said the cutting blades kept rotating when the mower was lifted off the ground.", "The importer had received one report of a consumer who lifted a mower and suffered minor lacerations from the moving blade.", "The recall also cited side spacing that could let a person's foot pass the shield and be struck by the blade.", "The mowers were made in Italy by Zucchetti Centro Sistemi and sold by Kyodo America dealers from January 2006 through December 2007 for $1,750 to $2,750." ], "tags": [ "recall", "robotic-mower", "laceration", "cpsc" ], "sources": [ { "title": "CPSC, Kyodo America Recall LawnBott Lawn Mowers Due to Laceration Hazard", "publisher": "U.S. Consumer Product Safety Commission", "url": "https://www.cpsc.gov/Recalls/2008/CPSC-Kyodo-America-Recall-LawnBott-Lawn-Mowers-Due-to-Laceration-Hazard", "date": "2008-04-25" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2005-06-09-da-vinci-robot-error-messages-bryn-mawr-hospital-surgery", "url": "https://roboincidents.com/incidents/2005-06-09-da-vinci-robot-error-messages-bryn-mawr-hospital-surgery/", "title": "da Vinci robot allegedly failed with errors mid-surgery in Pennsylvania", "summary": "A patient alleged that a da Vinci surgical robot displayed error messages and could not be restarted during his June 9, 2005 prostatectomy; courts rejected his claim against the maker.", "date": "2005-06-09", "date_precision": "day", "city": "", "state": "PA", "country": "US", "category": "surgical-robots", "category_name": "Surgical robots", "severity": "disruption", "severity_name": "Disruption", "fatalities": 0, "injuries": 0, "operator": "Surgical team at Bryn Mawr Hospital", "manufacturer": "Intuitive Surgical", "system": "da Vinci surgical robot", "companies": [ "Intuitive Surgical" ], "autonomy_mode": "teleoperated", "autonomy_mode_name": "Teleoperated", "status": "alleged", "status_name": "Alleged", "agencies": [], "official_records": [], "outcomes": [ "On March 11, 2009, the U.S. District Court for the Eastern District of Pennsylvania granted summary judgment to Intuitive Surgical.", "On January 28, 2010, the U.S. Court of Appeals for the Third Circuit affirmed, finding no evidence that the alleged malfunction caused the patient's injuries." ], "key_facts": [ "A patient alleged that a da Vinci surgical robot malfunctioned and displayed error messages during his prostatectomy on June 9, 2005.", "According to the Third Circuit's summary, the surgical team and a manufacturer's representative could not get the robot working, and the surgeon finished the operation with conventional laparoscopic equipment.", "The patient later reported bleeding that required hospitalization, erectile dysfunction and groin pain, and sued Intuitive Surgical.", "A federal district court granted summary judgment to Intuitive in March 2009 and the Third Circuit affirmed on January 28, 2010.", "The appeals court said nothing in the record would let a jury infer that the patient's injuries were caused by the robot's alleged malfunction." ], "tags": [ "da-vinci", "malfunction", "lawsuit", "summary-judgment", "prostatectomy" ], "sources": [ { "title": "Mracek v. Bryn Mawr Hospital; Intuitive Surgical, Inc., No. 09-2042 (3d Cir. Jan. 28, 2010) (not precedential)", "publisher": "U.S. Court of Appeals for the Third Circuit", "url": "https://www2.ca3.uscourts.gov/opinarch/092042np.pdf", "date": "2010-01-28" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2004-hoboken-robotic-parking-garage-cadillac-dropped-six-floors", "url": "https://roboincidents.com/incidents/2004-hoboken-robotic-parking-garage-cadillac-dropped-six-floors/", "title": "Hoboken's robotic parking garage drops unoccupied Cadillac six floors", "summary": "An unoccupied Cadillac DeVille was dropped six floors inside Hoboken's automated Garden Street parking garage in 2004; a Jeep fell four stories in the same garage a year later.", "date": "2004", "date_precision": "year", "city": "Hoboken", "state": "NJ", "country": "US", "category": "other", "category_name": "Other robots", "severity": "property-damage", "severity_name": "Property damage", "fatalities": 0, "injuries": 0, "operator": "City of Hoboken (garage owner); Robotic Parking Systems Inc. (builder and software licensor)", "manufacturer": "Robotic Parking Systems Inc. (Clearwater, Florida)", "system": "Fully automated 314-space parking garage on Garden Street that stores and retrieves cars by machine", "companies": [ "Robotic Parking Systems" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "In 2005 a Jeep was dropped four stories in the same garage, according to the Associated Press.", "In early 2006 a malfunction that went unrepaired for 26 hours trapped cars inside the garage.", "In summer 2006 a dispute between Hoboken and Robotic Parking Systems over control of the garage and its software shut it down for about two weeks before a court settlement." ], "key_facts": [ "In 2004 an unoccupied Cadillac DeVille was dropped six floors inside the automated parking garage on Garden Street in Hoboken, New Jersey, according to the Associated Press.", "A Jeep was dropped four stories in the same garage in 2005.", "The 314-space garage, supplied by Robotic Parking Systems Inc., opened in 2002 and parks cars by machine.", "The company's chief operating officer acknowledged operational problems but said the garage had run at 99.99 percent efficiency.", "The reports reviewed do not mention any injuries from either vehicle drop." ], "tags": [ "automated-parking", "vehicle-drop", "municipal", "software-dispute" ], "sources": [ { "title": "Robotic Garage to Park Cars Automatically in New York City", "publisher": "Associated Press (via Fox News)", "url": "https://www.foxnews.com/story/robotic-garage-to-park-cars-automatically-in-new-york-city.amp", "date": "2007-01-31" }, { "title": "And you don't have to tip", "publisher": "Associated Press (via The Daily Herald, Everett)", "url": "https://www.heraldnet.com/business/and-you-dont-have-to-tip", "date": "2007-02-03" }, { "title": "Robot Garage Hijacks Cars", "publisher": "Government Technology", "url": "https://www.govtech.com/magazines/gt/robot-garage-hijacks-cars.html", "date": "2010-08-11" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "2001-01-19-michigan-plastics-plant-gantry-robot-fatality", "url": "https://roboincidents.com/incidents/2001-01-19-michigan-plastics-plant-gantry-robot-fatality/", "title": "Gantry robot fatally strikes mold setter at Michigan plastics plant", "summary": "A 29-year-old mold setter at a Michigan injection molding company died on January 19, 2001, after a cycling gantry robot struck his head as he leaned over the machine.", "date": "2001-01-19", "date_precision": "day", "city": "", "state": "MI", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Unnamed custom plastic injection molding company (not identified in the report)", "manufacturer": "", "system": "Single-side gantry robot unloading parts from a 1,500-ton horizontal injection molding machine", "companies": [], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "MIOSHA", "Michigan FACE program (MIFACE)" ], "official_records": [], "outcomes": [ "MIOSHA inspected the plant and did not issue any citations to the employer.", "The Michigan FACE program published investigation 01MI002 with recommendations on safeguarding, risk assessment and training." ], "key_facts": [ "On January 19, 2001, a 29-year-old mold setter at a Michigan plastics plant was struck on the head by a gantry robot that was running in automatic mode.", "Michigan's FACE program found that the worker climbed onto a guard and leaned over the machine, apparently looking for tools, which put his head in the robot's path.", "Video cameras that monitored the machine recorded part of the sequence leading to the death.", "Investigators wrote that the robot's travel area had been left unguarded when the robot was added to the machine six to eight months earlier.", "MIOSHA did not issue any citations to the employer over the incident." ], "tags": [ "plastics", "injection-molding", "gantry-robot", "safeguarding", "state-face" ], "sources": [ { "title": "MIFACE Investigation #01MI002: Mold Setter's head struck by a cycling single-side gantry robot", "publisher": "Michigan State University, Michigan FACE Program", "url": "https://oem.msu.edu/images/MiFACE/01MI002v1.pdf", "date": null }, { "title": "Mold Setter's Head Struck By a Cycling Single-side Gantry Robot", "publisher": "CDC Stacks (NIOSH FACE program archive)", "url": "https://stacks.cdc.gov/view/cdc/169200", "date": null } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "1999-06-08-nebraska-meat-packing-plant-robotic-platform-fatality", "url": "https://roboincidents.com/incidents/1999-06-08-nebraska-meat-packing-plant-robotic-platform-fatality/", "title": "Robotic platform kills carousel operator at Nebraska meat packing plant", "summary": "A 23-year-old carousel operator at a Nebraska meat packing plant was killed on June 8, 1999, when he tripped a sensor and a computer-controlled platform descended on him.", "date": "1999-06-08", "date_precision": "day", "city": "", "state": "NE", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Unnamed meat processing and packing company (not identified in the report)", "manufacturer": "Alvey (system brand named in the report)", "system": "Computer-controlled boxed-meat handling system with conveyors, a storage carousel and a robotic inserter/extractor platform", "companies": [], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "Nebraska Department of Labor", "OSHA", "NIOSH" ], "official_records": [], "outcomes": [ "A Nebraska FACE investigator and an OSHA compliance officer visited the site on June 8 and 9, 1999.", "The Nebraska FACE program published investigation report 99NE017 on October 25, 1999, with four recommendations for employers." ], "key_facts": [ "At about 2:30 a.m. on June 8, 1999, a 23-year-old carousel operator at a Nebraska meat packing plant was killed by a computer-controlled robotic platform.", "The Nebraska FACE report says the worker stepped onto a conveyor to watch a maintenance job and his foot broke a light beam that signaled the platform to move.", "The conveyor being repaired had been switched off, but the rest of the system had not been locked out, so the sensors and the platform still had power.", "The worker had been employed at the plant for about two months and had received documented lockout/tagout training.", "Investigators recommended full lockout before maintenance, spot inspections, keeping uninvolved workers away from maintenance and a protective grate around the platform's access areas." ], "tags": [ "meat-packing", "lockout", "light-sensor", "niosh-face", "maintenance" ], "sources": [ { "title": "Machine Operator Crushed by Robotic Platform - Nebraska: Report 99NE017", "publisher": "Nebraska FACE Program / NIOSH (CDC Stacks)", "url": "https://stacks.cdc.gov/view/cdc/166988", "date": "1999-10-25" }, { "title": "Nebraska FACE Investigation 99NE017: Machine Operator Crushed by Robotic Platform", "publisher": "Nebraska Department of Labor (CDC Stacks PDF)", "url": "https://stacks.cdc.gov/view/cdc/166988/cdc_166988_DS1.pdf", "date": "1999-10-25" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "1984-07-21-michigan-die-cast-plant-unimate-robot-fatality", "url": "https://roboincidents.com/incidents/1984-07-21-michigan-die-cast-plant-unimate-robot-fatality/", "title": "Die-cast operator fatally pinned by Unimate robot at Michigan plant", "summary": "A 34-year-old die-cast operator was pinned between an industrial robot and a steel pole at a Michigan plant on July 21, 1984, and died five days later.", "date": "1984-07-21", "date_precision": "day", "city": "", "state": "MI", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Unnamed die-casting company (not identified by NIOSH)", "manufacturer": "", "system": "Unimate hydraulic industrial robot tending an automated die-casting cell", "companies": [], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [ "NIOSH" ], "official_records": [], "outcomes": [ "NIOSH investigated the death under its Fatal Accident Circumstances and Epidemiology (FACE) program and issued report FACE 84-20 in September 1984.", "The employer replaced the safety rail around the robot with a chain-link fence after the incident.", "The CDC published the case in its Morbidity and Mortality Weekly Report in 1985, describing it as the first documented robot-related fatality in the United States." ], "key_facts": [ "On July 21, 1984, a 34-year-old die-cast operator in Michigan was found pinned between the back of an industrial robot and a four-inch steel safety pole.", "The robot stalled against the operator's chest, causing cardiopulmonary arrest; he was admitted to hospital in a coma and died five days later.", "NIOSH stated in 1985 that, based on the information it had, this was the first documented robot-related fatality in the United States.", "The operator had 15 years of die-casting experience and had completed a one-week robotics course about a month before the incident.", "The robot's work area was enclosed on two sides by a safety rail with an electrically interlocked gate, which NIOSH said was less effective against deliberate entry." ], "tags": [ "die-casting", "pinch-point", "niosh-face", "safeguarding" ], "sources": [ { "title": "Occupational Fatality Associated with a Robot -- Michigan", "publisher": "CDC Morbidity and Mortality Weekly Report", "url": "https://www.cdc.gov/mmWR/preview/mmwrhtml/00000505.htm", "date": null }, { "title": "Fatal Accident Summary Report: Die Cast Operator Pinned by Robot: FACE 84-20", "publisher": "NIOSH (CDC Stacks)", "url": "https://stacks.cdc.gov/view/cdc/167482", "date": "1984-09-01" } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" }, { "id": "1979-01-26-ford-flat-rock-casting-plant-storage-robot-fatality", "url": "https://roboincidents.com/incidents/1979-01-26-ford-flat-rock-casting-plant-storage-robot-fatality/", "title": "Ford casting plant worker killed by parts-retrieval robot in Flat Rock", "summary": "A 25-year-old worker at Ford's Flat Rock, Michigan casting plant was struck and killed by a transfer vehicle of an automated parts storage system in January 1979.", "date": "1979-01-26", "date_precision": "day", "city": "Flat Rock", "state": "MI", "country": "US", "category": "industrial-robots", "category_name": "Industrial robots", "severity": "fatal", "severity_name": "Fatal", "fatalities": 1, "injuries": 0, "operator": "Ford Motor Company", "manufacturer": "Unit Handling Systems division of Litton Systems", "system": "Automated high-density parts storage and retrieval system using one-ton transfer vehicles with mechanical arms", "companies": [ "Ford" ], "autonomy_mode": "automated-fixed", "autonomy_mode_name": "Fixed automation", "status": "confirmed", "status_name": "Confirmed", "agencies": [], "official_records": [], "outcomes": [ "In August 1983 a Wayne County jury returned a $10 million verdict against Litton's Unit Handling Systems division, which supplied the storage system.", "Litton later settled with the worker's estate under an agreement in which it did not admit negligence or breach of warranty.", "On November 2, 1987, the Michigan Court of Appeals ruled that Litton could not recover the cost of the judgment from Ford through indemnity." ], "key_facts": [ "The January 1979 death of a worker at Ford's Michigan Casting Center in Flat Rock is listed by Guinness World Records as the first fatal casualty of a robot.", "A Michigan Court of Appeals opinion says the worker entered the third level of a high-density robotic storage area to investigate a malfunction and was struck from behind and crushed by a transfer vehicle.", "A jury found the storage system's supplier, a division of Litton Systems, liable for negligence and breach of implied warranty and awarded $10 million to the worker's estate.", "Litton argued that Ford had not sent the worker to Litton's training and had let him enter the system while its lockout was off; the Michigan Court of Appeals rejected Litton's indemnity claim against Ford in 1987.", "Sources disagree on the date: the appellate opinion gives January 26, 1979, while Guinness World Records and news reports of the verdict give January 25, 1979." ], "tags": [ "first-recorded", "storage-retrieval", "product-liability", "automotive", "lockout" ], "sources": [ { "title": "Williams v. Litton Systems, Inc", "publisher": "Michigan Court of Appeals (via CourtListener)", "url": "https://www.courtlistener.com/opinion/1819638/williams-v-litton-systems/", "date": "1987-11-02" }, { "title": "First human killed by a robot", "publisher": "Guinness World Records", "url": "https://www.guinnessworldrecords.com/world-records/first-human-to-be-killed-by-a-robot", "date": null }, { "title": "Robert Williams (robot fatality)", "publisher": "Wikipedia", "url": "https://en.wikipedia.org/wiki/Robert_Williams_(robot_fatality)", "date": null } ], "record_published": "2026-11-13", "record_updated": "2026-11-13" } ] }