Find a safety record
Every incident, injury and recall on file, from the national registries that publish them. Search a maker, a model, a town or a reference number — or narrow by what happened. Each record is the registry's own text, reproduced without rewriting, with the reference that locates it at the source. Registries count different things, so a total is a count of FILINGS and never a measure of how dangerous something is. How the record was collected.
Or jump to a maker
6,008 records on file
362 death reports1987–202614 registries
Narrow it down
What happened
Country
Year
Not graded by the source2025-06-18FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-25983da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF AN ARTICLE THAT EVALUATED THE SAFETY AND PERIOPERATIVE OUTCOMES OF ROBOTIC-ASSISTED SINGLE-PORT VERSUS MULTI-PORT SURGICAL STAGING FOR APPARENT EARLY-STAGE ENDOMETRIAL CANCER WAS PERFORMED. THE RETROSPECTIVE, PROPENSITY-MATCHED STUDY ANALYZED 100 PATIENTS UNDERGOING ROBOTIC-ASSISTED HYSTERECTOMY WITH BILATERAL SALPINGO-OOPHORECTOMY AND NODAL STAGING USING THE DA VINCI SURGICAL SYSTEM BETWEEN JANUARY 2021 AND DECEMBER 2024. A TOTAL OF 3 PATIENTS IN THE SINGLE-PORT GROUP EXPERIENCED POSTOPERATIVE COMPLICATIONS WITHIN 30 DAYS, INCLUDING SURGICAL SITE INFECTION AND ABDOMINAL PAIN REQUIRING READMISSION, AND HEMOPERITONEUM REQUIRING SURGICAL RE-INTERVENTION. NO DEVICE MALFUNCTIONS WERE REPORTED, AND THE AUTHORS DID NOT REPORT ANY EVENTS CAUSED BY ANY INTUITIVE SURGICAL, INC. (ISI) DEVICE. MULTIPLE ATTEMPTS WERE MADE TO CONTACT THE AUTHOR. NO RESPONSE HAS BEEN RECEIVED.
cause not established2955842-2026-25983Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-18FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-30026da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF THE ARTICLE REPORTED THE FOLLOWING ADVERSE EVENT. IN THE DA VINCI SP GROUP REASONS FOR READMISSION WERE: SURGICAL SITE INFECTION AND ABDOMINAL PAIN AND 1 PATIENT REQUIRED A BLOOD TRANSFUSIONS. IN THE DA VINCI XI GROUP REASONS FOR READMISSION WERE URETERAL FISTULA, URINARY TRACT INFECTION, AND ABDOMINAL PAIN. SEVERE COMPLICATIONS (GRADE 3 OR MORE) IN THE DA VINCI SP GROUP INCLUDED HEMOPERITONEUM REQUIRING SURGERY (N 1); WHILE IN THE DA VINCI XI GROUP INCLUDED HEMOPERITONEUM REQUIRING SURGERY (N = 1) AND URETERAL FISTULA (N = 1). ALL SEVERE COMPLICATIONS OCCURRED WITHIN 30 DAYS.
cause not established2955842-2026-30026Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-18FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29553da Vinci Surgical System
da Vinci Surgical System — Injury 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 DISTAL GASTRECTOMY PROCEDURE, A WHITE FRAGMENT FROM THE HARMONIC ACE INSTRUMENT FELL INSIDE THE PATIENT. WHEN THE EVENT OCCURRED, THE SURGEON WAS PERFORMING DISSECTION. THE FRAGMENT WAS NOT RETRIEVED AS IT COULD NOT BE FOUND. AN X-RAY WAS CONDUCTED POST-OPERATIVELY TO CHECK FOR FRAGMENTS. THE SURGERY WAS COMPLETED ROBOTICALLY, UTILIZING A BACKUP HARMONIC ACE INSTRUMENT. AFTERWARDS, IT WAS DISCOVERED THAT THE INSTRUMENT WAS WOBBLING. THE PATIENT HAS NOT RETURNED TO THE HOSPITAL DUE TO ANY POST-SURGICAL COMPLICATIONS RELATED TO RETAINING A FOREIGN OBJECT.
cause not established2955842-2025-29553Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-17FDA MAUDEStryker3005985723-2025-00316Mako Robotic-Arm
Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: VERIFICATION FAILED AND SUBSEQUENT AUTO ARM TEST ALSO FAILED. CABLE AND CAMERA CLEANED. ROBOT RESTARTED SEVERAL TIMES. ROBOT REPOSITIONED AND CAMERA ANGLE CHANGED. THE SURGERY WAS CANCELLED AND THE NEXT SURGERY IN THE OPERATING ROOM TOOK PLACE APPROXIMATELY ONE HOUR AFTER WE STARTED THE FAILED REGISTRATION OF THE ROBOT.
cause not established3005985723-2025-00316StrykerRead the record ↗Not graded by the source2025-06-16FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29554da Vinci Surgical System
da Vinci Surgical System — Injury 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 MYOMECTOMY SURGICAL PROCEDURE, A PORTION OF THE BLACK RUBBER ON THE TROCAR CAPS BROKE OFF AND FELL INSIDE OF THE PATIENT. THE UNIVERSAL SEAL WAS IDENTIFIED WHEN THE SURGICAL TEAM NOTICED A DEVICE FRAGMENT IN THE PELVIS. THE CAUSE OF THE FRAGMENT'S DETACHMENT REMAINS UNKNOWN. THE FRAGMENT WAS RETRIEVED BY THE SURGICAL ASSISTANT USING A LAPAROSCOPIC GRASPER, AND ITS RETRIEVAL WAS CONFIRMED BY MATCHING IT TO THE INNER CAP SEAL. NO ADDITIONAL SURGICAL PROCEDURE WAS NEEDED FOR THE REMOVAL OF THE FRAGMENT, AND NO POST-OPERATIVE TESTS WERE PERFORMED TO CHECK FOR REMAINING FRAGMENTS. THE PROCEDURE WAS COMPLETED ROBOTICALLY WITHOUT THE USE OF A BACKUP INSTRUMENT. THE PATIENT HAS NOT RETURNED TO THE HOSPITAL DUE TO ANY POST-SURGICAL COMPLICATIONS RELATED TO RETAINING A FOREIGN OBJECT.
cause not established2955842-2025-29554Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-16FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29781da Vinci Surgical System
da Vinci Surgical System — Injury 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 BARIATRIC SURGICAL PROCEDURE, THE SURGEON DISCOVERED FRAGMENTS WERE BROKEN OFF FROM THE GASKET OF THE HARMONIC ACE INSTRUMENT. THE DEVICE FRAGMENT FELL INSIDE THE PATIENT WHILE GRASPING, WHICH THE SURGEON BELIEVES WAS CAUSED BY INTRAOPERATIVE CLEANING OR COLLISION. THE FRAGMENT WAS SUCCESSFULLY RETRIEVED BY THE FIRST ASSISTANT UNDER DIRECT VISUALIZATION USING LAPAROSCOPIC INSTRUMENTS, AND ITS RETRIEVAL WAS CONFIRMED BY THE SCRUB NURSE WHO MATCHED THE FRAGMENT TO THE INSTRUMENT'S BREAK POINT. NO ADDITIONAL SURGICAL PROCEDURE WAS REQUIRED TO REMOVE THE FRAGMENT, AND NO POST-OPERATIVE TESTS SUCH AS AN X-RAY OR ULTRASOUND WERE PERFORMED TO CHECK FOR REMAINING FRAGMENTS. THE PROCEDURE WAS COMPLETED ROBOTICALLY. A BACKUP INSTRUMENT, THE HARMONIC SCALPEL, WAS USED TO COMPLETE THE PROCEDURE. THE PATIENT HAS NOT RETURNED TO THE HOSPITAL DUE TO ANY POST-SURGICAL COMPLICATIONS RELATED TO RETAINING A FOREIGN OBJECT. THE INSTRUMENT RECOGNITION ISSUE OCCURRED ON THE SAME HARMONIC ACE INSTRUMENT THAT HAD THE BROKEN FRAGMENT. THE INSTRUMENT IS AVAILABLE FOR RETURN TO ISI FOR EVALUATION; HOWEVER, THE FRAGMENT HAS BEEN DISCARDED AND WILL NOT BE RETURNE
cause not established2955842-2025-29781Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-13FDA MAUDEMedtronic plc — Surgical Robotics3005075696-2025-00302Mazor X
Mazor X — Injury 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 PATIENT HAD SHOWN SOME IMPROVEMENT SINCE THE SURGERY. THE SUSPECTED CAUSE WAS A PATIENT SHIFT DUE TO LEANING WHILE DRILLING, LEADING TO THE SKIVE.
cause not established3005075696-2025-00302Medtronic plc — Surgical RoboticsRead the record ↗Not graded by the source2025-06-12FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29782da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-29782Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-12FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-28492da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-28492Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-12FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-28927da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-28927Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-12FDA MAUDEMedtronic plc — Surgical Robotics3005075696-2025-00297Mazor X
Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MEDTRONIC RECEIVED INFORMATION REGARDING A GUIDANCE SYSTEM BEING USED DURING A SPINAL PROCEDURE, AN L2-L5 FUSION. IT WAS REPORTED THAT THERE WAS AN ALLEGED INACCURACY OF GREATER THAN 10 MILLIMETERS (MM). HARDWARE WAS PLACED IN L2 AND L3, BUT WHEN REACHING L4, THE DILATOR APPEARED TO BE INSIDE THE VERTEBRAL BODY, ALTHOUGH THE SURGEON DID NOT FEEL BONE. AN INTRAOPERATIVE ACCURACY CHECK WAS PERFORMED AND CONFIRMED THE APPEARANCE OF ACCURACY. THE SURGEON DECIDED TO SKIP L4, AND UPON REACHING L5, BLEEDING OCCURRED. AN X-RAY WAS TAKEN, WHICH SHOWED THAT THE HARDWARE IN L2 AND L3 WAS LATERAL AND OUTSIDE OF THE VERTEBRAL BODY. THE HARDWARE IN L2 AND L3 WAS REMOVED, THE C-ARM WAS RECALIBRATED, AND RE-REGISTRATION WAS PERFORMED. THE ROBOT WAS THEN SENT TO L2 ON THE RIGHT, BUT THE DILATOR TRAJECTORY WAS INFERIOR ON AP/LATERAL IMAGING. THE SURGEON COMPLETED THE REMAINDER OF THE CASE FREEHAND. THE PATIENT ALREADY HAD OBLIQUE LATERAL LUMBAR INTERBODY FUSION (OLIF) CAGES PRESENT, AS NOTED IN THE PRE-OPERATIVE COMPUTED TOMOGRAPHY. THERE WAS A THREE-HOUR S URGICAL DELAY, AND THE GUIDANCE SYSTEM AND NAVIGATION WERE ABORTED. THERE WAS NO IMPACT TO PATIENT'S OUTCOME. ADDITIONAL INFORMATION RECEIVED FR
cause not established3005075696-2025-00297Medtronic plc — Surgical RoboticsRead the record ↗Not graded by the source2025-06-10FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-28914da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-28914Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-09FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27422da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-27422Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-09FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-28928da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-28928Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-09FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27477da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-27477Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-09FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-30246da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF THE ARTICLE REPORTED THE FOLLOWING ADVERSE EVENT. URINARY LEAKAGE OCCURRED IN ONE PATIENT IN THE NONRENORRHAPHY GROUP AND TWO PATIENTS IN THE RENORRHAPHY GROUP; HOWEVER, THERE WAS NO STATISTICALLY SIGNIFICANT DIFFERENCE BETWEEN THE GROUPS (P=0.9399). IN THE NONRENORRHAPHY GROUP, ONE PATIENT DEVELOPED A URINOMA REQUIRING READMISSION. URINARY LEAKAGE DID NOT IMPROVE WITH URETERAL STENTING AND DRAINAGE BUT WAS ULTIMATELY RESOLVED AFTER FIBRIN INFUSION.
cause not established2955842-2026-30246Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-08FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27558da Vinci Surgical System
da Vinci Surgical System — Injury 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 TRANSORAL THYROIDECTOMY PROCEDURE, THE WHITE PART OF THE TIP OF THE HARMONIC ACE INSTRUMENT FELL OFF. UPON INSPECTION, IT WAS FOUND THAT THE FRONT TIP WAS SLIGHTLY BROKEN, SO ANOTHER HARMONIC ACE INSTRUMENT WAS USED INSTEAD. THE PROCEDURE WAS COMPLETED ROBOTICALLY. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE TEFLON PAD ON THE HARMONICA ACE INSTRUMENT WAS DAMAGED AND COMPLETELY DETACHED FROM THE INSTRUMENT. THE INSTRUMENT WAS INSPECTED PRIOR TO USE. THE INSTRUMENT DID NOT COLLIDE WITH ANY OTHER INSTRUMENT OR TOOL DURING PROCEDURE. A FRAGMENT FELL INSIDE THE PATIENT AND WAS RETRIEVED DURING THE SAME PROCEDURE. THE PATIENT HAD NO RETURNED TO THE HOSPITAL DUE TO ANY POST-SURGICAL COMPLICATIONS. THE INSTRUMENT IS AVAILABLE FOR RETURN TO ISI FOR EVALUATION; HOWEVER, NO PHOTOS OR VIDEOS ARE AVAILABLE FOR REVIEW.
cause not established2955842-2025-27558Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-05FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-34465da Vinci Surgical System
da Vinci Surgical System — Injury 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 SURGICAL PROCEDURE, THE HARMONIC ACE INSTRUMENT BROKE AND FRAGMENTS FELL INSIDE THE PATIENT'S BODY. THERE WERE NO INSTRUMENT COLLISIONS DURING THE CASE. THE FRAGMENTS WERE RETRIEVED DURING THE SAME SURGICAL PROCEDURE WHICH WAS COMPLETED ROBOTICALLY USING A BACKUP HARMONIC ACE INSTRUMENT.
cause not established2955842-2025-34465Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-05FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30184da Vinci Surgical System
da Vinci Surgical System — Injury 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 DISTAL PANCREATECTOMY PROCEDURE, THE TIP OF A HARMONIC ACE INSTRUMENT BROKE AND A PLASTIC FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME PROCEDURE WHICH WAS COMPLETED ROBOTICALLY USING A BACKUP INSTRUMENT.
cause not established2955842-2025-30184Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-05FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-34469da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-34469Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-05FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-34881da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF A LITERATURE ARTICLE "BENCH SURGERY WITH ROBOT-ASSISTED KIDNEY AUTO-TRANSPLANTATION FOR COMPLEX KIDNEY TUMORS: TECHNIQUE AND OUTCOMES FROM A SINGLE CENTER" WAS PERFORMED. FROM JANUARY 2018 TO MAY 2021, FOUR PATIENTS WITH SOLITARY KIDNEY TUMORS AND EIGHT WITH BILATERAL KIDNEY TUMORS UNDERWENT BENCH SURGERY (BENS) AND ROBOT-ASSISTED KIDNEY AUTO-TRANSPLANTATION (RAKAT). THE ARTICLE NOTED THAT THAT DURING THESE DV SURGERIES, "THREE PATIENTS PRESENTED GRADE IV POSTOPERATIVE COMPLICATIONS, AS FOLLOWS: ONE DEVELOPED SEPTIC SHOCK THAT RESOLVED WITH TREATMENT WITH BROAD-SPECTRUM ANTIBIOTICS AND SUPPORTIVE CARE IN THE INTENSIVE CARE UNIT. WHILE OTHER TWO OTHER DEVELOPED DELAYED GRAFT FUNCTION (DGF) THAT RESOLVED WITH TEMPORARY DIALYSIS." THE AUTHORS CONCLUDED THAT BENS WITH RAKAT IS AN ALTERNATIVE STRATEGY FOR THE TREATMENT OF HIGH-COMPLEXITY RENAL TUMORS THAT ARE UNSUITABLE FOR IN SITU PARTIAL NEPHRECTOMY (PN). LARGER PROSPECTIVE STUDIES WITH LONGER FOLLOW-UP ARE REQUIRED TO FURTHER ASSESS THE FINDINGS. THERE WERE NO SPECIFIC DA VINCI DEVICE MALFUNCTIONS REPORTED, NOR DID THE AUTHOR ALLEGE THAT INTUITIVE SURGICAL, INC. (ISI) PRODUCTS CAUSED OR CONTRIBUTED TO ANY ADVERSE EVENT. I
cause not established2955842-2025-34881Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-05FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-34473da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-34473Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-04FDA MAUDEStryker3005985723-2025-00293Mako Robotic-Arm
Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: AS ORIGINALLY REPORTED BY MPS: "PATIENT STARTED WITH 6 DEGREES OF VARUS. MAKO SAID HIS FINAL LIMB ALIGNMENT WAS 1 DEGREE OF VALGUS BUT THE PATIENT IS NOW IN 5 DEGREES OF VALGUS. SURGEON WANTS TO UNDERSTAND WHY. CASE TYPE / APPLICATION: TKA 2.0" ADDITIONAL INFORMATION: SURGERY ORIGINALLY PERFORMED (B)(6) 2025. ON (B)(6) 2025, MPS WAS MADE AWARE THAT THE PATIENT WAS 'NOW IN 5 DEGREES OF VALGUS' AND THAT THERE WERE PATIENT COMPLAINTS: PATIENT HAS FUNCTIONAL WEAKNESS AND ANKLE/FOOT PAIN.
cause not established3005985723-2025-00293StrykerRead the record ↗Not graded by the source2025-06-03FDA MAUDEStryker3005985723-2025-00288Mako Robotic-Arm
Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: NO NEW INFORMATION.
cause not established3005985723-2025-00288StrykerRead the record ↗Not graded by the source2025-06-03FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00257ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT RELINE MAS REDUCTION SCREWS WERE UTILIZED WITH THE ROBOT FOR THIS CASE. BLACK EXCELSIUS ARRAY WITH AN ADAPTER WAS UTILIZED. TWO EXCELSIUS ARRAYS WERE SET UP WITH MAS REDUCTION DRIVERS AND VERIFICATION OF THESE ARRAYS WAS CHALLENGING. THE CAMERA WAS HAVING A HARD TIME SEEING THESE ARRAYS. SPHERES WERE MANIPULATED MULTIPLE TIMES AND BOTH DRIVER ARRAYS WERE TRIED. ONCE THE CAMERA WAS ABLE TO SEE THE ARRAYS, IT TOOK MULTIPLE VERIFICATION ATTEMPTS AND MANIPULATION.
cause not established3004142400-2025-00257Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-06-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27452da Vinci Surgical System
da Vinci Surgical System — Injury 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 SURGICAL PROCEDURE, THE HARMONIC ACE TIP WAS BROKEN AND THE TEFLON PAD WAS SCRATCHED. THE USER COMPLETED THE PROCEDURE USING A BACKUP HARMONIC ACE WITH NO FURTHER ISSUE REPORTED. NO KNOWN IMPACT OR PATIENT CONSEQUENCE WAS REPORTED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE INSTRUMENT WAS INSPECTED PRIOR TO USE WITH NO DAMAGE OBSERVED. THERE WAS NO INSTRUMENT COLLISION DURING THE PROCEDURE. A FRAGMENT OF THE INSTRUMENT FELL INSIDE OF THE PATIENT AND WAS RETRIEVED DURING THE SAME PROCEDURE.
cause not established2955842-2025-27452Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27447da Vinci Surgical System
da Vinci Surgical System — Injury 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 SURGICAL PROCEDURE, THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY INSTALLED ON AN MCS INSTRUMENT CAME OFF AS THE SURGICAL STAFF WAS REMOVING THE INSTRUMENT. THE STAFF WAS ABLE TO RECOVER THE MCS TIP COVER ACCESSORY DURING THE SAME SURGICAL PROCEDURE WHICH WAS COMPLETED ROBOTICALLY. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE INITIAL REPORTER SAID THAT THE MCS TIP COVER ACCESSORY FELL INSIDE THE PATIENT WHEN THE CUSTOMER WAS TRYING TO REMOVE THE INSTRUMENT. THE TIP COVER WAS IMMEDIATELY RETRIEVED. THE MCS TIP COVER ACCESSORY WAS INSPECTED PRIOR TO USE AND NO DAMAGE OR NOTHING OUT OF ORDINARY WAS NOTED. THE MCS INSTRUMENT DID NOT COLLIDE WITH ANY OTHER INSTRUMENT. THE MCS TIP COVER ACCESSORY WAS PROPERLY INSTALLED. THE INSTRUMENT TIP WAS STRAIGHTENED UPON REMOVAL. THERE WAS NO DAMAGE/HOLES NOTED ON THE MCS TIP COVER ACCESSORY. THE MCS INSTRUMENT WAS FUNCTIONING AS EXPECTED DURING THE SURGICAL PROCEDURE.
cause not established2955842-2025-27447Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27894da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A SYSTEMATIC LITERATURE SEARCH WAS CONDUCTED USING PUBMED/MEDLINE, EMBASE, WEB OF SCIENCE, AND SCOPUS TO IDENTIFY STUDIES PUBLISHED UP TO NOVEMBER 2024. A REVIEW OF THE LITERATURE ARTICLE, ¿RELIABILITY OF THE DA VINCI ROBOTIC SURGICAL SYSTEM: A SYSTEMATIC REVIEW AND POOLED ANALYSIS OF TECHNICAL FAILURES¿ WAS PERFORMED AND 3,308,134 PROCEDURES WERE REVIEWED WITH 1,799 REPORTED EVENTS FROM 25 STUDIES. ALL THE INCLUDED STUDIES WERE RETROSPECTIVE, COVERING PROCEDURES PERFORMED BETWEEN 2000 AND 2021. THE POOLED MALFUNCTION RATE WAS 1.0% (95% CI: 0.9-1.2%). THE POOLED RATE OF DEVICE MALFUNCTIONS WAS 0.1% (95% CI: 0.1%-0.1%); INSTRUMENT MALFUNCTIONS ACCOUNTED FOR 0.4% (95% CI: 0.3-0.5%). THE OVERALL MALFUNCTION-RELATED CONVERSION RATE WAS 0.09% (95%CI: 0.06-0.11%), WITH CONVERSION TO OPEN AND LAPAROSCOPIC SURGERY IN 0.1% AND 0.04% OF THE TOTAL PROCEDURES, RESPECTIVELY. THE POOLED RATE OF MALFUNCTION-RELATED INJURIES WAS 0.01% (95% CI: 0.01-0.02%), WITH NO SIGNIFICANT IMPACT ON PATIENT OUTCOMES. NINETEEN STUDIES REPORTED DATA ON TECHNICAL FAILURES OF THE DA VINCI ROBOTIC SYSTEM, INCLUDING COMPLETE INFORMATION ON THE TOTAL NUMBER OF SURGERIES PERFORMED AND THE CORRESPONDING MALFUNCTIONS OBS
cause not established2955842-2025-27894Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Property damage only2025-06NHTSAWaymoGuadalupe30270-11214Passenger Car · struck on the rear right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 15
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- 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 June [XXX], 2025 at 6:01 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Guadalupe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] and began to slow for a queue of traffic at the intersection at [XXX]. A passenger car traveling southbound on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11214WaymoSource file ↗Property damage only2025-06NHTSAAvrideAustin31101-11278Passenger Car · struck on the front left · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Austin Police Department
- Make
- HYUNDAI
- Model
- Ioniq 5
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.
Our car was stopped at the intersection of [XXX] and [XXX], behind a red Ford Fusion. The Fusion suddenly reversed, struck our front bumper, and then left the scene in a hit-and-run. Damage is minimal: a slightly cracked bumper.
cause not established31101-11278AvrideSource file ↗Property damage only2025-06NHTSAWaymoLos Angeles30270-11295struck on the front right · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 1
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 June [XXX], 2025 at 1:55 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an automatic barrier arm at a parking lot located at [XXX]. The Waymo AV was traveling eastbound to exit a parking lot located at [XXX] and came to a stop for a closed automatic barrier arm. The automatic barrier arm then opened, and the Waymo AV began to proceed through the parking lot exit at low speed. The automatic barrier arm then closed. As the Waymo AV attempted to proceed the front of the Waymo AV made contact with the closed automatic barrier arm. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The automatic barrier arm sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11295WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11225Passenger Car · struck on the right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 21
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- 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 June [XXX], 2025 at 1:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX]. A passenger car exiting a driveway on the north side of [XXX] entered the roadway in front of a van parked at the curb, and the front of the passenger car made contact with the passenger 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11225WaymoSource file ↗Property damage only2025-06NHTSAWaymoAustin30270-11208SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- 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 June [XXX], 2025 at 9:05 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and came to a stop for a red light at the intersection at [XXX]. An SUV approached the Waymo AV from behind, and the front of the SUV 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. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11208WaymoSource file ↗Minor injury2025-06NHTSAWaymoLos Angeles30270-11245SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O 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 June [XXX], 2025 at 6:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northwestbound on [XXX] and was slowing to a stop for the stop sign at the intersection with [XXX]. An SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear 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. One of the two passengers in the Waymo AV reported minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11245WaymoSource file ↗Property damage only2025-06NHTSAWaymoLos Angeles30270-11249Pickup Truck · struck on the rear · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Right
- 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 June [XXX], 2025 at 11:26 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 eastbound in the rightmost lane on [XXX] when it came to a stop to yield to a stationary passenger car with its hazard lights activated in the Waymo AV's lane of travel near the intersection with [XXX]. The Waymo AV had its hazard lights activated, reversed a short distance, and then came to a stop. A pickup truck approached the Waymo AV from behind and came to a stop. The pickup truck then attempted to change lanes and pass to the left of the Waymo AV, and the passenger side of the pickup truck made contact with the rear driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11249WaymoSource file ↗No injury reported2025-06NHTSAWaymoChandler30270-11174struck on the bottom · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 10
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 June [XXX], 2025 at 8:16 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an elevated gate track in a parking lot at [XXX]. The Waymo AV was traveling eastbound in a parking lot at [XXX] through a gate opening when the bottom of the Waymo AV made contact with the elevated gate track. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11174WaymoSource file ↗Minor injury2025-06NHTSAWaymoSan Francisco30270-11205Non-Motorist: Cyclist · struck on the right · parked
- Crash With
- Non-Motorist: Cyclist
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- 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 June [XXX], 2025 at 10:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was stopped facing southeast in the right lane on [XXX] for a red light at the intersection at [XXX] when a Waymo AV passenger opted to end their ride prior to reaching their originally specified drop-off location, prompting the Waymo AV to park in-lane and activate its hazard lights for the passenger drop-off. A cyclist was traveling southeastbound on [XXX] in between vehicles in the right lane and vehicles stopped at the curb. As the cyclist passed the Waymo AV to the right, a Waymo AV passenger opened the front passenger side door and the front passenger side door of the Waymo AV made contact with the cyclist. The passengers in the vehicle were not belted at the time of the collision, as they were preparing to exit the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The cyclist reported minor injuries and was transported from the scene in an ambulance. 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 vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11205WaymoSource file ↗Property damage only2025-06NHTSAWaymoScottsdale30270-11220struck on the front right, bottom · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right, Bottom
- SV Precrash Speed (MPH)
- 23
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- 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 June [XXX], 2025 at 11:35 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving an unattended bicycle in the roadway on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the rightmost lane of [XXX] when the Waymo AV's front and undercarriage made contact with an unattended bicycle that was laying in the middle of the roadway. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. One of the passengers in the Waymo AV was not belted at the time of the collision. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11220WaymoSource file ↗Property damage only2025-06NHTSAWaymoAtlanta30270-11276SUV · struck on the rear · parked
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- 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 June [XXX], 2025 at 11:03 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was parked at the curb facing north on [XXX] when an SUV reversed out of a driveway on the west side of [XXX], and the rear of the SUV made contact with the rear driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11276WaymoSource file ↗Property damage only2025-06NHTSAWaymoPhoenix30270-11216Passenger Car · struck on the rear · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Right
- 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 June [XXX], 2025 at 4:56 PM MST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked at the curb facing south on [XXX] for a passenger drop-off with hazard lights activated. While the Waymo AV remained parked, a passenger car traveling southbound on [XXX] with its front passenger side door open proceeded to pass to the left of the Waymo AV. The front passenger door of the passenger car made contact with the rear driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger seated in the Waymo AV was not belted at the time of the collision, having not put the seatbelt on at the start of the trip. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11216WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11171Van · struck on the rear · parked
- Crash With
- Van
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Right
- 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 June [XXX], 2025 at 7:57 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was parked in-lane facing north on [XXX] with hazards activated for a passenger drop-off. While the Waymo AV remained parked, a van traveling northbound approached the Waymo AV from behind, and attempted to pass to the left of the Waymo AV. A Waymo AV passenger then opened the rear driver side door of the Waymo AV, and the passenger side of the van made contact with the rear driver side door of the stationary Waymo AV. The passengers seated in the Waymo AV were not belted at the time of the collision, as they were preparing to exit 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11171WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11298Heavy Truck · struck on the left · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Left
- 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 June [XXX], 2025 at 11:17 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling westbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions, when it came to a stop to yield to a heavy truck traveling eastbound on [XXX]. As the heavy truck passed by the stopped Waymo AV, the driver side of the heavy truck made contact with the driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11298WaymoSource file ↗Property damage only2025-06NHTSAWaymoLos Angeles30270-11221Pickup Truck · struck on the left · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 8
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- 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 June [XXX], 2025 at 4:41 PM 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 on [XXX] and approached a pick-up truck that was stopped in-lane facing east after making a left turn towards an alley behind [XXX]. As the Waymo AV passed the pick up truck, the pickup truck reversed and the rear of the pickup truck made contact with the driver 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11221WaymoSource file ↗Property damage only2025-06NHTSAWaymoMesa30270-11224SUV · struck on the front left, right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left, Right
- SV Precrash Speed (MPH)
- 6
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Chandler 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], 2025 at 5:34 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving an autonomous vehicle on [XXX] near [XXX]. The Waymo AV was parked facing east for a passenger pick-up on [XXX] adjacent to a parking lot at [XXX]. A passenger entered the Waymo AV and the Waymo AV began to proceed forward momentarily before the passenger opened the front passenger side door and exited the Waymo AV, prompting the Waymo AV to stop. The passenger then re-entered the Waymo AV and the Waymo AV proceeded to pass to the left of a different Waymo AV stopped facing east on [XXX]. While the first Waymo AV was passing the stopped Waymo AV, the passenger in the moving Waymo AV opened the front passenger side door, which then made contact with the driver side mirror of the stopped Waymo AV. The passenger in the moving Waymo AV was not belted at the time of the collision. At the time of the impact, the Level 4 ADS of both Waymo AVs were engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11224WaymoSource file ↗Property damage only2025-06NHTSAWaymoPhoenix30270-11190Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- 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 June [XXX], 2025 at 2:46 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX at [XXX]. The Waymo AV was stopped facing south in the rightmost lane on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, a passenger car traveling southbound in the rightmost lane on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear 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. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because of airbag deployment 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-11190WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11196Pickup Truck · struck on the front left · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 9
- CP Pre-Crash Movement
- Entering Traffic
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- 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], 2025 at 7:19 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX]. As the Waymo AV proceeded past a heavy truck parked on the righthand curb, a pickup truck traveling southeastbound in an alley by [XXX] entered [XXX] in front of the heavy truck and into the Waymo AV's lane of travel. The front driver side of the pickup truck made contact with the front passenger side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11196WaymoSource file ↗Property damage only2025-06NHTSAWaymoScottsdale30270-11167Passenger Car · struck on the front right · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- 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 June [XXX], 2025 at 3:47 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] at Hayden Road. The Waymo AV was parked at the curb facing east on [XXX] when a passenger car that was parked directly in front of the Waymo AV proceeded to reverse, and the rear of the passenger car made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11167WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11244SUV · struck on the front · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 8
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 June [XXX], 2025 at 12:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] and slowing to a stop for a stop sign at the intersection at [XXX]. An SUV that was traveling southbound on [XXX] initiated a left turn at the intersection onto eastbound [XXX]. The SUV continued turning left, crossing the centerline of [XXX] and entering into the Waymo AV's lane of travel. The front of the SUV then made contact with the front driver 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. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because 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-11244WaymoSource file ↗Property damage only2025-06NHTSAWaymoLos Angeles30270-11172SUV · struck on the left · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 22
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Left
- 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 June[XXX], 2025 at 7:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the rightmost lane when an SUV traveling ahead of the Waymo AV southeastbound on [XXX] in the second from the right lane initiated a right turn into a parking garage entrance on the south side of [XXX]. As the Waymo AV was passing the SUV, the SUV crossed the lane line, into the Waymo AV's lane of travel, and the front passenger side of the SUV made contact with the driver side of the Waymo AV. 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11172WaymoSource file ↗Property damage only2025-06NHTSAWaymoLos Angeles30270-11250Van · struck on the rear · parked
- Crash With
- Van
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Right
- 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 June [XXX], 2025 at 10:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a minivan on [XXX] near [XXX]. The Waymo AV was parked at the curb facing west on [XXX] for a passenger pick-up with hazard lights activated. A minivan that was traveling southbound on [XXX] and making a right turn onto westbound [XXX] approached the stationary Waymo AV from behind, momentarily stopped, and proceeded to pass to the left of the Waymo AV. The passenger side of the minivan made contact with the rear driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The minivan sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11250WaymoSource file ↗