When a robot goes wrong,
someone files a record.

Every exposure figure we could verify

Very few operators publish how much they run. Each figure below is shown with the sentence it came from, so you can check it against the filing yourself.

For the surgical systems we do not divide one by the other. The FDA says its device reports are “not intended to be used either to evaluate rates of adverse events, evaluate a change in event rates over time, or to compare adverse event occurrence rates across devices”, because reports go unfiled and the FDA does not know how often each device is used. The FDA on its own data

• Manufacturing37 · 17 fatal
• Consumer / household26
• Not coded in the source23 · 15 fatal
• Medical9
• Accommodation & food2
• Professional services1 · 1 fatal
• Utilities & power1 · 1 fatal
• Retail1
• Transport & warehousing1

fatalother investigations

• Recall2026-08-26China DPRCsamrdprc:20260827_115936aigo-brand H872SPW and H875SPW "H8" drones

  aigo-brand H872SPW and H875SPW "H8" drones — 15 units built between 26 May and 22 Jul 2025 recalled because geofencing, sense-and-avoid and electromagnetic compatibility all fail GB 42590-2023, China's civil UAS safety standard. Filed with the Jiangxi provincial market regulator. The regulator's stated risk is that the aircraft can enter restricted airspace and is more prone to mid-air collision. Free repair, part replacement or return.

  cause not establishedsamrdprc:20260827_115936Read the record ↗
• Death reported2026-06-30FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-33713da Vinci Surgical System

  da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: It was reported that during a da Vinci-assisted sliding hiatal hernia procedure, after sealing and cutting of an unspecified branch of the aorta, bleeding occurred and the patient ultimately expired.The surgeon reported that the Vessel Sealer Curved (VSC) instrument seal and cut cycle worked as expected with no error messages. However, when the jaws of the VSC were opened, the sealed branch started to hemorrhage. The procedure continued robotically for approximately one hour in attempts to fully stop the bleeding which was able to be controlled at multiple points after the initial seal. The estimated blood loss during the robotic portion was approximately 2 liters when a mass transfusion protocol was initiated and the procedure was converted to a thoracotomy but the surgeon was unable to control the bleeding. The aorta was then cross-clamped and the bleeding stopped; however, the patient expired in the operating room. The surgeon reports there were no error messages or robotic-related complications that occurred during the procedure. Specifically, the VSC worked as expected with no error messages or complications with sealing during use.

  cause not established2955842-2026-33713Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗
• Recall2026-06-22Health CanadaRA-82239CyberKnife Treatment Delivery System

  CyberKnife Treatment Delivery System — Type II recall: performance malfunction can occur when the collimator housing is moved over the Xchange table, causing the robot to lock up and halt operation. Affects 4 system units (lots C0417, C0545, C0573, C0351). Facilities told to clear the treatment area, not move the robot via the in-room pendant, and contact Accuray service. No injuries reported.

  cause not establishedRA-82239Read the record ↗
• Death reported2026-06-22FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-32985da Vinci Surgical System

  da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED UNSPECIFIED COLORECTAL PROCEDURE, THE INFERIOR MESENTERIC ARTERY (IMA) WAS SEALED WITH THE VESSEL SEALER CURVED (VSC) INSTRUMENT AND BLEEDING OCCURRED AFTER SEALING AND CUTTING. THE PATIENT LATER EXPIRED ON POSTOPERATIVE DAY 3. THE SURGEON REPORTED THAT WHEN THE JAWS WERE OPENED, BLEEDING WAS IMMEDIATE. THE IMA HAD AN OPEN LUMEN AND SHOWED NO SIGNS OF SEALING. THE VSC CONTINUED TO BE USED TO SEAL THE IMA TWO MORE TIMES ALONG DIFFERENT POINTS DURING THE PROCEDURE; BLEEDING OCCURRED AFTER EACH SEAL. THE VESSEL HAD TO BE RE-SEALED MORE PROXIMALLY TOWARD THE AORTA TO MOBILIZE THE TISSUE TO CREATE AN OSTOMY. THE SEALING TONES WERE REPORTED AS APPROPRIATE AND NO ERROR MESSAGES WERE PRODUCED WHILE SEALING. THE ESTIMATED BLOOD LOSS WAS 300ML. AFTER THE ROBOTIC PORTION WAS COMPLETED AND DURING CLOSURE, THE PATIENT CODED. RESUSCITATION MEASURES WERE SUCCESSFUL, AND THE PATIENT WAS TRANSFERRED TO THE INTENSIVE CARE UNIT. THE PATIENT EXPIRED THREE DAYS LATER AFTER THE FAMILY DECIDED TO WITHDRAW CARE. THE SURGEON RELATED THE VSC INABILITY TO SUCCESSFULLY SEAL MULTIPLE TIMES THROUGHOUT THE PROCEDURE TO CHALLENGING TISSUE INTEGRITY DUE TO EDEMA. THE

  cause not established2955842-2026-32985Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗
• Serious injury2026-06NHTSAWaymoScottsdale30270-15547SUV · struck on the rear left · stopped

  Crash With

  SUV

  Highest Injury Severity Alleged

  Serious W/ Hospitalization

  SV Pre-Crash Movement

  Stopped

  SV Contact Area

  Rear Left

  SV Precrash Speed (MPH)

  0

  CP Pre-Crash Movement

  Proceeding Straight

  CP Contact Area

  Front

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Street

  Weather

  Clear

  Investigating Agency

  Scottsdale Police Department

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On June [XXX], 2026 at 2:53 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing east in the rightmost of two designated left turn only lanes on [XXX], for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling eastbound at a high rate of speed on [XXX] traversed to the left across two lanes, and into the Waymo AV's lane of travel. The SUV maneuvered to the right as it approached the Waymo AV from behind, and the front left side of the SUV made contact with the rear right side of the stopped Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV was transported from the scene to the hospital by ambulance with serious injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-15547WaymoSource file ↗
• Serious injury2026-05NHTSAWaymoPhoenix30270-15174Pickup Truck · struck on the left · proceeding straight

  Crash With

  Pickup Truck

  Highest Injury Severity Alleged

  Moderate W/ Hospitalization

  SV Pre-Crash Movement

  Proceeding Straight

  SV Contact Area

  Left

  SV Precrash Speed (MPH)

  22

  CP Pre-Crash Movement

  Entering Traffic

  CP Contact Area

  Front Right

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Intersection

  Weather

  Clear

  Investigating Agency

  Phoenix Police Department

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On May [XXX], 2026 at 3:59 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling westbound in the second to the right lane on [XXX] and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV began to cross the intersection, a pickup truck traveling northbound in the designated right turn lane on [XXX]t proceeded to enter the intersection against a red light and began to maneuver to the left. The Waymo AV braked and maneuvered to the right as the pickup truck continued to proceed forward, and the front of the pickup truck made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Two passengers in the Waymo AV were not belted at the time of the collision. Two passengers in the Waymo AV were transported to a hospital by an ambulance with moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-15174WaymoSource file ↗
• Serious injury2026-05NHTSAWaymoLos Angeles30270-15070Pickup Truck · struck on the front right · lane / road departure

  Crash With

  Pickup Truck

  Highest Injury Severity Alleged

  Moderate W/ Hospitalization

  SV Pre-Crash Movement

  Lane / Road Departure

  SV Contact Area

  Front Right

  SV Precrash Speed (MPH)

  20

  CP Pre-Crash Movement

  Stopped

  CP Contact Area

  Rear Left

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Street

  Weather

  Cloudy

  Investigating Agency

  Los Angeles Police Department

  Make

  ZEEKR

  Model

  RT

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On May [XXX], 2026 at 6:44 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pickup truck on [XXX] near {XXX}. The Waymo AV was traveling southbound in the right lane on {XXX] in autonomous mode when it began to slow for a queue of traffic stopped for a red light at the intersection with [XXX]. As the Waymo AV was slowing, the Waymo AV transitioned to manual mode and the test driver maneuvered to the right and accelerated forward. As the test driver maneuvered the Waymo AV to pass to the right of a pickup truck that was stopped facing south in the right lane in the queue of traffic ahead, the front left side of the Waymo AV made contact with the rear right side of the pickup truck, the front of the Waymo AV made contact with the west curb of {XXX], and the front right side of the Waymo AV made contact with a street light pole near the curb. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. The test driver of the Waymo AV was transported to a hospital by an ambulance with moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-15070WaymoSource file ↗
• Recall2026-04-09CPSCWYBOT26372Wybotics Recalls Robotic Pool Vacuums Due to Burn and Fire Hazards

  Wybotics Recalls Robotic Pool Vacuums Due to Burn and Fire Hazards — Hazard: The lithium-ion battery in the recalled pool vacuums can overheat, posing burn and fire hazards to consumers. Reported incidents: The firm has received ten reports of the pool vacuums overheating or catching fire while charging and not charging, resulting in nine incidents of property damage. No injuries have been reported.

  cause attributed by source26372WYBOTRead the record ↗
• Serious injury2026-04NHTSAWaymoSan Francisco30270-14618SUV · struck on the left, front left, rear, front · proceeding straight

  Crash With

  SUV

  Highest Injury Severity Alleged

  Moderate W/ Hospitalization

  SV Pre-Crash Movement

  Proceeding Straight

  SV Contact Area

  Left, Front Left, Rear, Front

  SV Precrash Speed (MPH)

  2

  CP Pre-Crash Movement

  Lane / Road Departure

  CP Contact Area

  Left, Rear, Front

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Street

  Weather

  Clear

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On April [XXX], 2026 at 9:24 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] when an SUV traveling northbound on [XXX], without activated headlights, maneuvered to the left and entered the Waymo AV's lane of travel. The Waymo AV began to slow to yield to the SUV as the SUV continued to approach, and the left side of the SUV made contact with the left side of the Waymo AV. As a result of this contact, the Waymo AV was pushed to the right and the front right tire of the Waymo AV made contact with the left side of a passenger car parked facing south on the west curb of 47th Avenue. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the SUV sustained damage. The passengers of the Waymo AV were transported to a hospital by an ambulance, alleging minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-14618WaymoSource file ↗
• Death reported2026-03-23FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-22620da Vinci Surgical System

  da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED MEDIAN ARCUATE LIGAMENT SYNDROME RELEASE (MALS) PROCEDURE, THE PATIENT EXPERIENCED INTRAOPERATIVE BLEEDING FROM THE AORTA AND ULTIMATELY EXPIRED. THE VESSEL SEALER CURVED (VSC) INSTRUMENT WAS BEING USED FOR BLUNT DISSECTION AND CAUTERY WHEN SIGNIFICANT BLEEDING OCCURRED FROM THE AORTA. THE PROCEDURE WAS EMERGENTLY CONVERTED TO AN OPEN APPROACH. WHEN AN ASSISTING VASCULAR SURGEON CROSS CLAMPED THE AORTA DURING REPAIR ATTEMPTS, THE PATIENT¿S PULSE WAS LOST AND CHEST COMPRESSIONS WERE STARTED. WITH NO RETURN OF A PULSE, THE CROSS CLAMPS ON THE AORTA WERE REMOVED AND BLEEDING CONTINUED WITH THE CHEST COMPRESSIONS. THE PATIENT EXPIRED IN THE OPERATING ROOM. THE SURGEON STATED THAT THE CAUSE OF THE AORTIC INJURY WAS UNKNOWN. THE SURGEON REPORTED THAT THROUGHOUT THE PROCEDURE, IT WAS NOTICED THAT THE VSC PRODUCED INCREASED THERMAL SPREAD AND INCREASED BLEEDING AFTER ENERGY ACTIVATION WHEN COMPARED TO THE VESSEL SEALER EXTEND. IT WAS ALSO STATED THAT THE VSC JAW MOVEMENT WOULD OPEN A LITTLE SLOWLY AT FIRST, THEN WOULD SPRING OPEN QUICKLY, WITH INCREASED BLEEDING FROM THE FAST JAW OPENING. NO ADDITIONAL INFORMATION WAS PROVIDED.

  cause not established2955842-2026-22620Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗
• Death reported2026-02-20Press recordsTesla

  A judge has denied Tesla's request to overturn a $243 million jury verdict that held the automaker partially responsible for a fatal crash involving its Autopilot driver assistance system.

  cause not establishedTeslaRead the record ↗
• Recall2026-02-19Health CanadaRA-81626Hugo RAS Bipolar Maryland Forceps and Hugo RAS Bipolar Fenestrated Grasper

  Hugo RAS Bipolar Maryland Forceps and Hugo RAS Bipolar Fenestrated Grasper — Voluntary safety notice: increased likelihood of drive-cable pulley-assembly component failure due to manufacturing variations, which can make instrument jaw control incorrect/uncontrolled and may detach a white plastic pulley component inside the patient's body. The Hugo RAS system automatically detects and halts control of the affected instrument when this occurs. No injuries reported.

  cause not establishedRA-81626Read the record ↗
• Recall2026-02-19Health CanadaRA-81627Monarch Platform (Model MON-000006)

  Monarch Platform (Model MON-000006) — Type II recall: rare software glitch where the app may restart during procedure setup, resetting patient-side state to patient-left if it had been set to patient-right, risking unintended robotic-arm movement toward the wrong anatomical side. No injuries reported; facilities told to contact the manufacturer.

  cause not establishedRA-81627Read the record ↗
• Death reported2026-02-03FDA MAUDEMedtronic plc — Surgical RoboticsMazor X3005075696-2026-00049Mazor X

  Mazor X — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: ADDITIONAL INFORMATION WAS RECEIVED. IT WAS REPORTED THAT THE SURGEON'S TECHNIQUE WAS DRILL, TAP, THEN SCREW. THE SURGEON OPERATED AND STARTED ON THE RIGHT SIDE. T3 AND T4 WERE PLACED WHEN AN INACCURACY WAS NOTICED. IT WAS ALSO NOTED THAT WITH REGISTRATION AND AFTER RE-IMAGING, THEY HAD A YELLOW VALUE BUT THEY WERE UNSURE WHAT LEVEL THIS WAS ON. ADDITIONALLY, IT WAS NOTED THAT THE PATIENT HAD A PRE-EXISTING FRACTURE AT T5.

  cause not established3005075696-2026-00049Medtronic plc — Surgical RoboticsMazor XRead the record ↗
• Serious injury2026-02NHTSAWaymoSan Francisco30270-14003Van · struck on the rear right · parked

  Crash With

  Van

  Highest Injury Severity Alleged

  Moderate W/ Hospitalization

  SV Pre-Crash Movement

  Parked

  SV Contact Area

  Rear Right

  SV Precrash Speed (MPH)

  0

  CP Pre-Crash Movement

  Proceeding Straight

  CP Contact Area

  Front Right

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Street

  Weather

  Clear

  Investigating Agency

  San Francisco Police Department

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On February [XXX], 2026 at 11:06 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was parked at the curb facing north on [XXX] with its hazard lights activated for a passenger drop-off. While the Waymo AV was parked, a passenger in the Waymo AV opened the rear right side door in preparation to exit the vehicle. A van traveling northbound on [XXX] in the right lane accelerated as it approached the Waymo AV from behind, and the front of the van made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the Waymo AV was unbelted at the time of the collision as they were preparing to exit the vehicle. Both passengers of the Waymo AV were transported to a hospital by an ambulance, one of the passengers had minor injuries and one of the passengers had moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-14003WaymoSource file ↗
• Death reported2026-01-29FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-14792da Vinci Surgical System

  da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT AFTER A DA VINCI-ASSISTED SINGLE-PORT UNSPECIFIED ¿HEAD AND NECK¿ SURGICAL PROCEDURE, THE PATIENT DEVELOPED A POSTOPERATIVE HEMORRHAGE AND ULTIMATELY EXPIRED. THE SURGEON INFORMED THE INTUITIVE CLINICAL SALES REPRESENTATIVE THAT THE ROBOTIC PROCEDURE WAS COMPLETED WITHOUT ANY INTRAOPERATIVE COMPLICATIONS; HOWEVER, THE PATIENT DEVELOPED POST-OPERATIVE COMPLICATIONS DUE TO UNSPECIFIED BLEEDING FROM THE NON-SPECIFIC PROCEDURE. NO ADDITIONAL EVENT INFORMATION WAS PROVIDED. THE SURGEON STATED THAT THE ADVERSE EVENT ¿HAD NOTHING TO DO WITH THE DA VINCI SP SYSTEM¿. ATTEMPTS TO OBTAIN ADDITIONAL INFORMATION FROM THE SURGEON WERE MADE; HOWEVER, NO RESPONSE WAS RECEIVED.

  cause not established2955842-2026-14792Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗
• Death reported2026-01-26FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-05349da Vinci Surgical System

  da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED PULMONARY LOBECTOMY PROCEDURE, AN INADVERTENT PERFORATION OF THE PULMONARY ARTERY OCCURRED WHILE USING A THIRD-PARTY LAPAROSCOPIC STAPLER INSTRUMENT, RESULTING IN SIGNIFICANT HEMORRHAGE AND THE PATIENT ULTIMATELY EXPIRED. THE EXACT VOLUME OF BLOOD LOSS IS UNKNOWN. THE SURGEON DOES NOT BELIEVE THAT THE DA VINCI SYSTEM, INSTRUMENTS, OR ACCESSORIES CAUSED OR CONTRIBUTED TO THE EVENT. ADDITIONAL INFORMATION WAS REQUESTED, BUT THE CUSTOMER HAS INDICATED THAT THEY WILL NOT GRANT PERMISSION FOR FURTHER ACCESS TO THE EVENT INFORMATION.

  cause not established2955842-2026-05349Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗
• Recall2025-12-19Health CanadaRA-81382Mazor X System

  Mazor X System — Type II recall for the Mazor X surgical robotic guidance platform (6 affected serial numbers) tied to software v5.2, which resolved 111 anomalies from prior versions; 7 of those are evaluated as having observed or potential harm greater than negligible. No injuries reported; facilities told to contact the manufacturer.

  cause not establishedRA-81382Read the record ↗
• Death reported2025-12-09FDA MAUDEMedtronic plc — Surgical RoboticsMazor X3005075696-2026-00029Mazor X

  Mazor X — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MAITY, APRATIM, ET AL. ¿ANALYSIS OF ROOT CAUSES OF ADVERSE EVENTS WITH MAZOR X AND MAZOR X STEALTH EDITION-GUIDED SPINE SURGERIES: AN FDA MAUDE DATABASE STUDY.¿ EUROPEAN SPINE JOURNAL, 22 DEC. 2025, HTTPS://DOI.ORG/10.1007/S00586-025-09683-2. ABSTRACT PURPOSE: THIS STUDY AIMED TO ANALYZE ADVERSE EVENTS ASSOCIATED WITH MAZOR X SURGICAL GUIDANCE ROBOTS, FOCUSING ON PARAMETERS SUCH AS ROOT CAUSES, VERTEBRAL DISTRIBUTION, SURGICAL DELAY, ROBOT ABANDONMENT, AND MORE. METHODS: 330 ADVERSE EVENTS REPORTED WITHIN THE MANUFACTURER AND USER FACILITY DEVICE EXPERIENCE (MAUDE) DATABASE FOR THE MAZOR X (MX) AND MAZOR X STEALTH EDITION (MXSE) ROBOT GUIDANCE SYSTEMS WERE ANALYZED AND CATEGORIZED BASED ON THE ROOT CAUSES, VERTEBRAL DISTRIBUTION, SURGICAL DELAY, ROBOT ABANDONMENT, AND PATIENT OUTCOMES. RESULTS: BOTH THE MX AND MXSE ADVERSE EVENTS WERE PRIMARILY DUE TO EXTERNAL ROOT CAUSES (35% AND 52%, RESPECTIVELY), WITH USER ERROR BEING THE MOST COMMON. DEVIATIONS WERE MOST LIKELY TO AFFECT THE L3, L4, AND L5 VERTEBRA, AND DEVIATE EITHER MEDIALLY OR LATERALLY. MOTOR DEFICITS WERE THE MOST COMMON ADVERSE PATIENT OUTCOME FOR MX, WHILE SENSORY DEFICITS WERE THE MOST COMMON FOR MXSE. THERE WERE TWO D

  cause not established3005075696-2026-00029Medtronic plc — Surgical RoboticsMazor XRead the record ↗
• Death reported2025-11-03FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00031Monarch Platform

  Monarch Platform — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A ROBOTICALLY ASSISTED BRONCHOSCOPY PROCEDURE, AS THE PHYSICIAN WAS TAKING ANTERIOR/POSTERIOR SCOUT SHOTS USING A 3D C-ARM, THE PATIENT BEGAN TO EXHIBIT IRREGULAR HEART RHYTHMS. THE PHYSICIAN DECIDED TO ABORT THE PROCEDURE. THE PATIENT WENT INTO ATRIAL FIBRILLATION AND CODED. CHEST COMPRESSIONS WERE STARTED IMMEDIATELY. THE CODE CONTINUED FOR 30 - 35 MINUTES, AND THE PATIENT PASSED AWAY. NO BIOPSIES OR NEEDLE ASPIRATIONS WERE PERFORMED DURING THE PROCEDURE. NO ISSUES WERE REPORTED INVOLVING THE DEVICES USED DURING THE PROCEDURE.

  cause not established3014447948-2025-00031Auris HealthMonarch PlatformRead the record ↗
• Serious injury2025-11NHTSAWaymoScottsdale30270-13161Non-Motorist: Pedestrian · struck on the rear left · proceeding straight

  Crash With

  Non-Motorist: Pedestrian

  Highest Injury Severity Alleged

  Moderate W/ Hospitalization

  SV Pre-Crash Movement

  Proceeding Straight

  SV Contact Area

  Rear Left

  SV Precrash Speed (MPH)

  4

  CP Pre-Crash Movement

  Other, see Narrative

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Street

  Weather

  Clear

  Investigating Agency

  Scottsdale Police Department

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On November [XXX], 2025 at 12:02 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger of the Waymo AV on [XXX] near [XXX]. The Waymo AV was travelling northbound in the left lane of [XXX]. While the AV was in motion, the two passengers seated in the rear of the Waymo AV removed their seatbelts and opened the right rear passenger side door. The Waymo AV detected the opened door and began to slow in lane. While the Waymo AV was slowing to a stop, the passenger seated in the right rear passenger seat exited the vehicle through the open door, placed their feet on the ground, and the rear right tire of the Waymo AV came to a stop on top of the passenger's right foot. The Waymo AV remained stopped on top of the passenger's foot until emergency services arrived and lifted the right side of the vehicle. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger of the Waymo AV was transported from the scene to a hospital for medical treatment with moderate injuries to the foot. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vulnerable road user was struck by an involved vehicle. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-13161WaymoSource file ↗
• Death reported2025-10-15FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00280ExcelsiusGPS

  ExcelsiusGPS — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT AT THE HOSPITAL THEIR ELDERLY PATIENT WITH A THORACIC FRACTURE. THE PATIENT WAS UNWELL AND EVEN HAD AN ISSUE DURING THE SURGERY. EGPS WAS USED WITH E3D AND ALL SCREWS WERE EXECUTED. UNFORTUNATELY THE NEXT DAY THE PATIENT PASSED AWAY. POST OP IMAGING CONFIRMS SCREWS WERE ACCURATE BUT THERE WERE QUESTIONS ABOUT THE ROBOTIC CASE. NO SCREWS WERE FOUND DEVIATED TO HAVE A CLINICAL DEFICIT.

  cause not established3004142400-2025-00280Globus MedicalExcelsiusGPSRead the record ↗
• Serious injury2025-10NHTSAWaymoAtlanta30270-11841Passenger Car · struck on the rear right · stopped

  Crash With

  Passenger Car

  Highest Injury Severity Alleged

  Moderate W/ Hospitalization

  SV Pre-Crash Movement

  Stopped

  SV Contact Area

  Rear Right

  SV Precrash Speed (MPH)

  0

  CP Pre-Crash Movement

  Proceeding Straight

  CP Contact Area

  Front Right

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Intersection

  Weather

  Clear

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On October [XXX], 2025 at 9:55 AM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and came to a stop at the stop sign at the intersection with [XXX]. A passenger car traveling directly behind the Waymo AV proceeded without stopping, and the front driver side of the passenger car then made contact with the rear side of the stationary Waymo AV. First responders arrived at the scene and assisted the rider out of the Waymo AV. An ambulance was called to the scene and Waymo later learned that the rider was transported to the hospital. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV was not belted at the time of the collision they were in the process of locating the belt fastener for the seat they were occupying. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-11841WaymoSource file ↗
• Death reported2025-09NHTSAWaymoTempe30270-11713Motorcycle · struck on the rear · making right turn

  Crash With

  Motorcycle

  Highest Injury Severity Alleged

  Fatality

  SV Pre-Crash Movement

  Making Right Turn

  SV Contact Area

  Rear

  SV Precrash Speed (MPH)

  8

  CP Pre-Crash Movement

  Proceeding Straight

  CP Contact Area

  Front Left, Front Right

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Street

  Weather

  Clear

  Investigating Agency

  Tempe Police Department

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On September [XXX], 2025 at 1:21 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was traveling north in the rightmost lane on [XXX] and began slowing with its right turn signal activated in preparation for a right turn into a parking lot at [XXX], yielding to a pedestrian crossing the driveway entrance to the parking lot on the right-hand sidewalk. While the Waymo AV was slowing with its right turn signal activated, a motorcycle in the rightmost lane approached the Waymo AV from behind and the front of the motorcycle made contact with the rear left corner of the Waymo AV. The impact with the Waymo AV resulted in the motorcyclist falling from the motorcycle and into the roadway to the left of the Waymo AV. Immediately afterwards, a passenger car in the second-from-the-rightmost lane passed the Waymo AV on the left and struck the motorcyclist in the roadway. The passenger car did not stop and left the scene. The motorcyclist was transported from the scene to a hospital, where they were declared deceased. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and the Waymo AV was not carrying passengers. Following contact with the motorcycle, the Waymo AV came to a complete stop and remained stopped until the vehicle was towed away several hours later. The Waymo AV and the motorcycle sustained damage. The extent of the damage to the passenger car that left the scene is unknown at this time. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because of a fatality. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-11713WaymoSource file ↗
• Recall2025-08-15China DPRCsamrdprc:20250818_114037Shou-brand folding aerial-photography drone, models SG107MAX (20 units) and SG107MAX2 (5 units)

  Shou-brand folding aerial-photography drone, models SG107MAX (20 units) and SG107MAX2 (5 units) — 25 units built between 2 May and 2 Jul 2024 recalled because the aircraft has no geofencing function at all and can therefore enter restricted airspace. Refunded rather than repaired. Filed with the Shantou municipal market regulator.

  cause not establishedsamrdprc:20250818_114037Read the record ↗
• Death reported2025-08-01Press recordsTesla

  Last August, a jury awarded a $243 million verdict against Tesla over its culpability in a 2019 fatal crash in Florida that killed Naibel Benavides and critically injured Dillon Angulo. The jury assigned the driver two-thirds of the blame, and attributed one-third to Tesla.

  cause not establishedTeslaRead the record ↗
• Serious injury2025-07NHTSAWaymoSanta Clara30270-11403SUV · struck on the right · making left turn

  Crash With

  SUV

  Highest Injury Severity Alleged

  Moderate W/ Hospitalization

  SV Pre-Crash Movement

  Making Left Turn

  SV Contact Area

  Right

  SV Precrash Speed (MPH)

  25

  CP Pre-Crash Movement

  Changing Lanes

  CP Contact Area

  Front Right

  Within ODD?

  Yes

  Automation System Engaged?

  ADS

  Roadway Type

  Street

  Weather

  Clear

  Investigating Agency

  Santa Clara Police Department

  Make

  JAGUAR

  Model

  I-PACE

  SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

  On July [XXX], 2025 at 1:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Clara, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped on [XXX], preparing to turn right onto northeastbound [XXX] while yielding to oncoming traffic. Once oncoming traffic had cleared, the Waymo AV began to turn right into the rightmost lane on northeastbound [XXX]. As the Waymo AV was completing the right turn, the test driver transitioned the Waymo AV to manual mode. The test driver changed lanes without a signal activated, crossing through the center travel lane and into the dedicated left turn lane where the test driver began to make an unprotected left across southwestbound [XXX]. During this unprotected left turn, an SUV was traveling in the leftmost southwestbound lane. The SUV began to maneuver towards the rightmost lane while the test driver was completing the left turn, and the front of the SUV made contact with the passenger side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, a vehicle involved was towed away, and airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available.

  cause not established30270-11403WaymoSource file ↗
• Recall2025-05-07EU Safety GateSR/00867/25Poolrunner Battery Pro Performance

  Poolrunner Battery Pro Performance — Fully automatic battery-operated pool robot for cleaning pools, powered by a rechargeable battery. Product sold online, in particular via steinbach-group.com. Hazard (Burns, Fire): A technical defect in the charging station or the battery could cause a fire and burns to the user. The product does not comply with the Low Voltage Directive. Action: Recall of the product from end users.

  cause not establishedSR/00867/25Read the record ↗
• Death reported2025-04-22FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-45559da Vinci Surgical System

  da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF AN ARTICLE WAS CONDUCTED, WHICH AIMED TO EVALUATE THE INITIAL EXPERIENCE AND FEASIBILITY OF ROBOTIC-ASSISTED PYLORUS-PRESERVING PANCREATICODUODENECTOMY PROCEDURES (PPPD) USING THE DA VINCI SP SYSTEM VERSUS THE DA VINCI XI SYSTEM. THE STUDY WAS A RETROSPECTIVE CASE SERIES ANALYZING 14 PATIENTS UNDERGOING PPPD FROM DECEMBER 2021 AND SEPTEMBER 2023. ONE PATIENT WITH COMMON BILE DUCT CANCER DIED DURING AT AN UNSPECIFIED TIME POST-PROCEDURE DUE TO THE PROGRESSION OF CANCER. THERE WAS NO REPORT OR INDICATION IN THE ARTICLE OF ANY DA VINCI SP SYSTEM MALFUNCTIONS. MULTIPLE ATTEMPTS TO OBTAIN ADDITIONAL INFORMATION FROM THE CORRESPONDING AUTHOR WERE MADE; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.

  cause not established2955842-2025-45559Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗
• Recall2025-03-20CPSCAiper25187

  Aiper Seagull Pro Cordless Robotic Pool Vacuum Cleaners Recalled Due to Burn and Fire Hazards; Distributed by Shenzhen Aiper Intelligent Co. — Hazard: The recalled pool vacuum cleaner has a large current adapter that can overheat, posing burn and fire hazards. Reported incidents: The firm has received 19 reports of the recalled pool vacuums melting, smoking or catching on fire while charging causing five incidents of property damage. No injuries have been reported.

  cause attributed by source25187AiperRead the record ↗

These are the most serious 30. Browse all 6,008 records — filter by registry, severity, country or year.

• United States600 makers5,961 records4 registries
• China399 makers5 records2 registries
• Japan102 makers6 records2 registries
• Germany85 makers1 record1 registry
• South Korea65 makersrecalls read · workplace blocked
• India50 makersread · no robots
• Canada50 makers14 records1 registry
• United Kingdom48 makers5 records1 registry
• France48 makers2 records1 registry
• Switzerland44 makersno registry found
• Italy26 makersin EU Safety Gate · none
• Israel26 makersno registry found

China is the case worth understanding. It is the second-largest maker base on this site, and the easy assumption is that it files nothing. It does. China runs two recall registers we can now read — the market regulator's own column and its recall technical centre's consumer channel — and between them we read 2,426 notices, every one of them. Four are robots. All four are drones. One register is dominated by cars and motorcycles; the other by furniture, toys and appliances. So the gap is not silence — it is two registers built for other things being asked a question about robots. Most of the gaps above are some version of that same mismatch rather than a refusal to disclose.