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-08-18FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-37779da 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-37779Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-18FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-37340da 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-37340Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗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 ↗Not graded by the source2025-08-14FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00024Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE FOLLOWING ARTICLE HAS BEEN REVIEWED: MCNIERNEY D, CHEN J, ZEIN JG, VASZAR L, SWANSON K, AZADEH N, SAKATA KK. COMPARING MONARCH VERSUS ION ROBOTIC-ASSISTED BRONCHOSCOPY PLATFORMS: A PROPENSITY SCORE-MATCHED ANALYSIS. J BRONCHOLOGY INTERV PULMONOL. 2025 JUL 15;32(4):E01019. DOI: 10.1097/LBR.0000000000001019. PMID: 40662912, AND CITED FOUR (4) INSTANCES OF PNEUMOTHORAX WITH CHEST TUBE PLACEMENT. THIS REPORT IS BEING SUBMITTED FOR THESE EVENTS.
cause not established3014447948-2025-00024Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-08-14FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00026Monarch Platform
Monarch Platform — 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 MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED SYSTEM FAULT MESSAGES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00026Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-08-14FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-41245da 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 LOW ANTERIOR RESECTION SURGICAL PROCEDURE, THE CUSTOMER EXPERIENCED UNSTABLE ENERGY OUTPUT WITH A HARMONIC ACE INSTRUMENT. AS A RESULT, THE CUSTOMER ELECTED TO CONVERT THE CASE TO TRADITIONAL LAPAROSCOPIC SURGERY AND AN ADDITIONAL INCISION WAS PLACED.
cause not established2955842-2025-41245Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-14FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-38436da 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-38436Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-14FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-39899da 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 LIVER PARTIAL RESECTION PROCEDURE, THE CUSTOMER RECEIVED A "REDUCE TIP PRESSURE" MESSAGE WHILE USING A HARMONIC ACE INSTRUMENT. THE INSTRUMENT THEN SUDDENLY BROKE AND A FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME SURGICAL PROCEDURE WHICH WAS COMPLETED USING A BACKUP HARMONIC ACE INSTRUMENT.
cause not established2955842-2025-39899Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-12FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-35102da 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 clinical study article reported a retrospective single-center study of consecutive children under 12 months of age who underwent robotic surgery between 2010 and 2020. All procedures were performed using the da Vinci Si surgical system.Postoperative complications were reported in 6 patients, 2 of whom required reoperation. These complications included partial dehiscence of an anorectal anastomosis due to surgical wound infection requiring redo surgery, ileus, accidental gastrostomy outlet requiring endoscopic placement, pleural effusion, bradycardia, and atelectasis.The authors concluded that robotic surgery in newborns and infants can be considered feasible and safe when performed by well-trained surgeons. They also suggested that a wide range of procedures, including complex surgeries in small children, can be carried out safely with a very low complication rate. It was recommended that, further multicenter studies are needed to validate these findings.Intuitive Surgical Inc. (ISI) has made multiple attempts to obtain additional information; however, as of the date of this report, no new information has been obtained.
cause not established2955842-2026-35102Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-11FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-37201da 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 (MSC) TIP COVER ACCESSORY, INSTALLED ON AN MCS INSTRUMENT, FELL OFF INSIDE THE PATIENT. IT IS UNKNOWN IF THE MCS TIP COVER ACCESSORY WAS RETRIEVED. THE PROCEDURE WAS COMPLETED ROBOTICALLY.
cause not established2955842-2025-37201Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-10FDA MAUDEMedtronic plc — Surgical Robotics3005075696-2025-00347Mazor X
Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IACCARINO, F., DUGONI, D. E., PAVESI, G., LANDI, A., GALLIENI, M., GIORDANO, M., IACCARINO, C. (2025). ROBOTIC SPINE SURGERY COMPARED WITH FLUOROSCOPIC-ASSISTED SURGERY: ADVANTAGES, DISADVANTAGES, FUTURE PERSPECTIVES. JOURNAL OF ROBOTIC SURGERY, 19(1). HTT PS://DOI.ORG/10.1007/S11701-025-02654-1 SUMMARY: BACKGROUND: ROBOTIC SPINE SURGERY (RSS) COULD POTENTIALLY OVERCOME SOME LIMITATIONS OF FLUOROSCOPIC-ASSISTED SURGERY (FAS). THE AIM OF THIS STUDY WAS TO ANALYZE RSS ADVANTAGES COMPARED TO FAS AND THE IMPACT OF A DEDICATED NURSING TEAM ON SURGICAL WORKFLOW EFFICIENCY. MATERIALS AND METHODS: WE RETROSPECTIVELY ANALYZED 260 ADULT PATIENTS WITH THORACOLUMBAR DEGENERATIVE/TRAUMATIC INSTABILITY. ONE-HUN DRED-THIRTY UNDERWENT POSTERIOR FUSION WITH MEDTRONIC MAZOR X, WHILE 130 WERE TREATED WITH FAS. PARAMETERS INCLUDED OPERATIVE DURATION, OR ENTRY-TO-START TIME, SCREW IMPLANTATION TIME, ACCURACY (GERTZBEIN-ROBBINS CLASSIFICATION), RADIATION EXPOSURE, COMPLICATIONS, AND OSWESTRY DISABILITY INDEX (ODI). WE ALSO ASSESSED OR ENTRY-START SURGERY/IMPLANT TIMES, NUMBER OF SCREWS IMPLANTED, AND DURATION OF THE INTERVENTION BEFORE AND AFTER THE INTRODUCTION OF A DEDICATED NURSING TEAM FOR RSS. RESU
cause not established3005075696-2025-00347Medtronic plc — Surgical RoboticsRead the record ↗Not graded by the source2025-08-09FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-39898da 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 LIVER PARTIAL RESECTION PROCEDURE, THE HARMONIC ACE INSTRUMENT SUDDENLY BROKE AND A FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME SURGICAL PROCEDURE WHICH WAS COMPLETED ROBOTICALLY.
cause not established2955842-2025-39898Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-08FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-41796da 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 BLADE OF THE HARMONIC ACE INSTRUMENT BROKE, AND A FRAGMENT FELL INSIDE THE PATIENT WHILE THE SURGEON WAS GRASPING TISSUE. THE SURGEON SUSPECTED IT MAY HAVE BEEN A QUALITY ISSUE. THE FRAGMENT WAS SUCCESSFULLY RETRIEVED BY THE ASSISTANT USING ANOTHER INSTRUMENT, AND VISUAL CONFIRMATION ENSURED THAT NO FRAGMENTS REMAINED INSIDE THE PATIENT. THE PROCEDURE WAS COMPLETED ROBOTICALLY USING A BACKUP HARMONIC ACE INSTRUMENT, AND THERE WERE NO POST-SURGICAL COMPLICATIONS REPORTED. NO ADDITIONAL SURGICAL PROCEDURE WAS REQUIRED, AND NO POST-OPERATIVE TESTING WAS PERFORMED.
cause not established2955842-2025-41796Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-08FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-35374da 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 was performed that presented a retrospective review of experiences with robotic-assisted segmentectomy procedures for early-stage non-small-cell lung cancer. The article noted 1 patient who experienced severe pulmonary embolism (grade IV) and one patient experienced sputum retention requiring bronchoscopy (grade IIIa). No device malfunctions were reported, and the authors did not report any events caused by any Intuitive Surgical, Inc. (ISI) device. The corresponding author was contacted but no response has been received.
cause not established2955842-2026-35374Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-07FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-36017da 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 CUSTOMER CONTACTED AN INTUITIVE SURGICAL, INC. (ISI) TECHNICAL SUPPORT ENGINEER (TSE) FOR ASSISTANCE DUE TO ONGOING ISSUES WITH STERILE ADAPTERS. NO TROUBLESHOOTING WAS PERFORMED AS THE SURGEON INSTRUCTED THE OR STAFF TO END THE CALL WITH THE TSE. AT THE TIME THE EVENT OCCURRED, ANESTHESIA WAS ALREADY ADMINISTERED TO THE PATIENT AND PORTS WERE PLACED. IT IS UNCLEAR IF THE CASE WAS ABORTED OR CONVERTED TO OPEN SURGERY.
cause not established2955842-2025-36017Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-07FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-36018da 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 PROSTATECTOMY PROCEDURE, A PIECE OF RUBBER WAS FOUND IN THE SURGICAL FIELD AND REMOVED. THE EVENT OCCURRED AFTER THE CAMERA WAS DOCKED AND INSTRUMENTS WERE INSERTED. UPON EXAMINATION, IT WAS CONFIRMED THAT THE RUBBER INSIDE THE UNIVERSAL SEAL WAS TORN. THE FRAGMENT WAS RETRIEVED DURING THE SAME PROCEDURE AND WAS CONFIRMED TO BE COMPLETELY REMOVED THROUGH VISUAL INSPECTION. NO ADDITIONAL SURGICAL PROCEDURES WERE REQUIRED, NOR WERE ANY POST-OPERATIVE TESTS SUCH AS X-RAYS OR ULTRASOUNDS CONDUCTED TO CHECK FOR REMAINING FRAGMENTS. THE PROCEDURE WAS COMPLETED ROBOTICALLY WITHOUT THE NEED FOR A BACKUP UNIVERSAL SEAL. MOREOVER, THE PATIENT HAS NOT HAD TO RETURN TO THE HOSPITAL DUE TO POST-SURGICAL COMPLICATIONS.
cause not established2955842-2025-36018Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-07FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-36007da 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 TIP OF THE HARMONIC ACE BROKE. A FRAGMENT FELL INSIDE THE PATIENT AND WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE INSTRUMENT WAS INSPECTED PRIOR TO USE. THE NURSE DIDN'T REMEMBER EXACTLY WHAT SURGICAL TASK WAS PERFORMED AT THAT TIME OF THE DEVICE FRAGMENT FALLING INSIDE OF THE PATIENT, BUT THE ISSUE DID NOT OCCUR WHILE INSERTING OR REMOVING THE INSTRUMENT. IT IS UNKNOWN WHAT THE SURGEON BELIEVED WAS THE CAUSE OF THE INSTRUMENT BREAKAGE. THE INSTRUMENT WAS IN USE FOR ABOUT AN HOUR, AND THE SURGEON DID NOT NOTICE ANY ISSUES WITH THE FUNCTIONALITY OF THE INSTRUMENT DURING THE SURGICAL PROCEDURE. THE INSTRUMENT DID NOT COLLIDE WITH ANY OTHER INSTRUMENT OR OTHER HARD MATERIAL DURING THE SURGICAL PROCEDURE. THE FRAGMENT DID NOT FALL INSIDE OF THE PATIENT DURING AN INSTRUMENT TIP/ ACCESSORY COLLISION. THE INSTRUMENT WAS NOT REMOVED DURING THE SURGICAL PROCEDURE PRIOR TO THE BREAKAGE. UPON FINAL REMOVAL OF THE INSTRUMENT, THE WRIST OF THE INSTRUMENT WAS STRAIGHTENED. THE
cause not established2955842-2025-36007Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-07FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-36575da 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 BENIGN HYSTERECTOMY SURGICAL PROCEDURE, THE WHITE PIECES OF THE INSIDE OF THE JAW OF SYNCHROSEAL WERE FALLING OFF INTO THE PATIENT DURING THE CASE. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE INSTRUMENT WAS INSPECTED PRIOR TO USE. THE SURGICAL TASK BEING PERFORMED AT THE TIME THE DEVICE FRAGMENT FELL INSIDE THE PATIENT WAS DISSECTION. IT IS UNKNOWN WHAT THE SURGEON BELIEVED WAS THE CAUSE OF THE INSTRUMENT BREAK OR THE FRAGMENT FALLING INSIDE THE PATIENT. IT IS UNKNOWN HOW LONG THE INSTRUMENT HAD BEEN USED PRIOR TO THE ISSUE. THE SURGEON NOTICED THAT PIECES WERE FALLING OFF INTO THE PATIENT DURING THE PROCEDURE. IT IS UNKNOWN IF THE INSTRUMENT COLLIDED WITH ANY OTHER INSTRUMENTS OR OTHER HARD MATERIAL DURING THE SURGICAL PROCEDURE. THE INSTRUMENT WAS REMOVED DURING THE SURGICAL PROCEDURE PRIOR TO THE BREAKAGE, WITH THE WRIST STRAIGHTENED. THE SURGICAL STAFF DID NOT FEEL ANY RESISTANCE UPON REMOVAL OF THE INSTRUMENT THROUGH THE CANNULA. UPON FINAL REMOVAL OF THE INSTRUMENT, THE WRIST WAS STRAIGHTENED. THE STAFF DIDN'T FEEL ANY RE
cause not established2955842-2025-36575Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-07FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-36570da 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-36570Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-07FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-37610da 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-37610Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-07FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-41795da 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 BLADE OF THE HARMONIC ACE INSTRUMENT BROKE, AND A FRAGMENT FELL INSIDE THE PATIENT WHILE THE SURGEON WAS GRASPING TISSUE. THE SURGEON SUSPECTED THERE MAY HAVE BEEN A QUALITY ISSUE. THE FRAGMENT WAS SUCCESSFULLY RETRIEVED BY THE ASSISTANT USING ANOTHER INSTRUMENT, AND VISUAL CONFIRMATION ENSURED THAT NO FRAGMENTS REMAINED INSIDE THE PATIENT. THE PROCEDURE WAS COMPLETED ROBOTICALLY USING A BACKUP HARMONIC ACE INSTRUMENT, AND THERE WERE NO POST-SURGICAL COMPLICATIONS REPORTED. NO ADDITIONAL SURGICAL PROCEDURE WAS REQUIRED, AND NO POST-OPERATIVE TESTS WERE PERFORMED.
cause not established2955842-2025-41795Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-06FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-35958da 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 AT THE END OF A DA VINCI-ASSISTED PYELOPLASTY PROCEDURE AND AFTER ALL THE INSTRUMENTS WERE TAKEN OUT, A SEAL FROM A ACCESS PORT KIT SNAPPED AND A FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED WITH A GRASPER AND WAS PULLED OUT THROUGH THE EXISTING PORT INCISION. THE PATIENT DID NOT HAVE ANY COMPLICATIONS DUE TO THIS SITUATION AND IS DOING WELL IN POSTOPERATIVELY.
cause not established2955842-2025-35958Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-06FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-41794da 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-41794Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-06FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00025Monarch Platform
Monarch Platform — 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 MONARCH BRONCHOSCOPY PROCEDURE, THE PHYSICIAN ENCOUNTERED NAVIGATION ISSUES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00025Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-08-06FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-34124da 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.
cause not established2955842-2026-34124Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-05FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-32703da 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 AN UNSPECIFIED DA VINCI-ASSISTED SURGICAL PROCEDURE, A MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY, INSTALLED ON AN MCS INSTRUMENT, FELL OFF INSIDE THE PATIENT. THE MCS TIP COVER ACCESSORY WAS RETRIEVED AND REPLACED DURING THE SAME PROCEDURE WHICH WAS COMPLETED ROBOTICALLY. THE CUSTOMER WAS UNABLE TO PROVIDED ANY ADDITIONAL INFORMATION REGARDING THE REPORTED EVENT SUCH AS THE EVENT DATE. NO PRODUCT WILL BE RETURNED.
cause not established2955842-2025-32703Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-41495da 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-41495Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-41498da 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-41498Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-35844da 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 PARTIAL NEPHRECTOMY SURGICAL PROCEDURE, USER REPORTED THAT THERE WERE CHALLENGES WITH THE USE OF THE CUSTOM REMOTE CENTER (CRC) FEATURE, WHICH CREATED UNNECESSARY STRESS FOR THE STAFF AND POSED INTRAOPERATIVE CHALLENGES WHILE OPERATING NEAR THE PARENCHYMAL WALL. PARENCHYMA WALL. THERE WAS NO INJURY OR BLEEDING DUE TO THIS AT ALL. THE USER NOTED THAT THERE WERE NO ISSUES WITH THE SYSTEM ITSELF, BUT THE DIFFICULTIES WITH THE CRC LED TO IT BEING DISABLED. HOWEVER, BY THAT POINT, THE SURGEON HAD ALREADY DECIDED TO CONVERT THE CASE TO OPEN. THE USER EXPRESSED A DESIRE FOR THE CRC FEATURE TO BE MORE USER-FRIENDLY TO PREVENT SUCH COMPLICATIONS IN THE FUTURE. THE REPORTER CONFIRMED THAT THE PROCEDURE WAS CONVERTED TO OPEN DUE TO FRUSTRATION WITH THE CUSTOM REMOTE CENTER (CRC) ISSUE.
cause not established2955842-2025-35844Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-35512da 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 RADICAL SALVAGE PROSTATECTOMY PROCEDURE, MONOPOLAR ENERGY CEASED TO FUNCTION, ACCOMPANIED BY AN ERROR. EACH ATTEMPT BY THE CUSTOMER TO APPLY MONOPOLAR ENERGY RESULTED WITH THE ERROR. THE NURSE MENTIONED THAT BIPOLAR ENERGY REMAINED UNAFFECTED. AS A WORKAROUND, AN INTUITIVE SURGICAL, INC. (ISI) TECHNICAL SUPPORT ENGINEER (TSE) SUGGESTED CONNECTING A FORCE TRIAD GENERATOR WITH AN EXTERNAL PEDAL TO GENERATE MONOPOLAR ENERGY. THE NURSE CONFIRMED THE PRESENCE OF THE BACKUP GENERATOR BUT NOTED THAT THE SURGEON DECIDED TO ABORT THE PROCEDURE. AT THE TIME THE CASE WAS ABORTED, ANESTHESIA HAD ALREADY BEEN ADMINISTERED TO THE PATIENT AND PORTS HAD BEEN PLACED.
cause not established2955842-2025-35512Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-40399da 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-40399Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-08-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-35513da 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 AFTER PORT PLACEMENT THE TEAM HAD PREPARED A PATIENT FOR A RADICAL EXTRAPERITONEAL PROSTATECTOMY. THE SURGEON, AFTER MAKING THE INITIAL INCISION, INSERTED THE SINGLE PORT (SP) ACCESS PORT INTO THE PATIENT. HOWEVER, WHEN ATTEMPTING TO DOCK THE SP SYSTEM, AN ERROR MESSAGE APPEARED INDICATING THAT THE "CANNULA WAS INVALID." FOLLOWING THE TECHNICAL SUPPORT ENGINEER'S (TSE) RECOMMENDATION, THE TEAM OPENED A SECOND SMALL ACCESS PORT KIT, BUT IT RESULTED IN THE SAME ERROR MESSAGE. A HARD SYSTEM RESTART DID NOT RESOLVE THE ISSUE, SO THE TEAM UNDOCKED THE SP, RE-DRAPED THE SYSTEM, AND ATTEMPTED TO REDOCK, BUT THE ERROR PERSISTED. WITH ADVICE FROM THE TSE, AN ENGINEER VISIT WAS SCHEDULED, CONTINGENT ON RECEIVING SPARE PARTS FROM THE NETHERLANDS. THE PROCEDURE WAS CONVERTED TO A MULTI-PORT DA VINCI XI SYSTEM TO COMPLETE THE PROCEDURE. THE CUSTOMER HAD TO CLOSE THE INITIAL SINGLE ACCESS PORT INCISION THAT WAS MADE ON THE PATIENT AND PUT 4 ADDITIONAL 8MM CANNULAS IN FOR THE XI CASE, WHICH MEANT A DIFFERENT APPROACH WAS USED FOR THE CASE AND NOT THE PLANNED EXTRAPERITONEAL APPROACH. THE TRANSITION TO THE XI SYSTEM AND THE TROUBLESHOOTING EFFORTS CAUSED A DELAY OF APPROXIMATELY 45
cause not established2955842-2025-35513Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Property damage only2025-08NHTSAWaymoPhoenix30270-11500struck on the front · 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
- SV Precrash Speed (MPH)
- 13
- 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 August [XXX], 2025 at 12:42 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a section of removed pavement on [XXX] near [XXX]. The Waymo AV was traveling southbound through a construction zone on [XXX] in the rightmost lane delineated by a line of temporary orange pylons when it approached a parked construction truck in its lane of travel with a mounted arrow board displaying a flashing left arrow. The Waymo AV changed lanes to continue traveling southbound on [XXX] to the left of the line of pylons. As the Waymo AV continued to follow the path delineated by the pylons, it encountered a section of the pavement that had been removed creating a drop in the lane surface, and the front left wheel proceeded over the section of removed pavement.. 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-11500WaymoSource file ↗Minor injury2025-08NHTSAWaymoSan Francisco30270-11496Motorcycle · struck on the right · stopped
- Crash With
- Motorcycle
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- SFPD
- 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 August [XXX], 2025 at 1:50 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was traveling southbound in the left lane on [XXX] when it slowed to a stop for a queue of traffic for a red light at the intersection with [XXX]. A motorcycle traveling southbound in the left lane on [XXX] began passing the Waymo AV on the right side, maneuvering between the Waymo AV and a passenger car stopped in the right lane. As the motorcycle passed between the Waymo AV and the stationary passenger car, a passenger in the passenger car opened the rear left side door and the motorcycle made contact with the open rear left side door of the passenger car. As the motorcycle fell to the left, the motorcycle made contact with the right 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 and the passenger car sustained damage. The motorcyclist alleged a minor injury. Waymo is reporting this crash under Request No. 2. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11496WaymoSource file ↗Property damage only2025-08NHTSAWaymoPhoenix30270-11545Passenger Car · struck on the front 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
- Front Right
- SV Precrash Speed (MPH)
- 15
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Left
- 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 August [XXX], 2025 at 5:11 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at the frontage road following the off-ramp exit of Interstate [XXX]. The Waymo AV was traveling westbound on [XXX] and proceeding into the intersection with the frontage road off-ramp of Interstate [XXX] on a green light. As the Waymo AV began to enter the intersection, a passenger car traveling southbound on the frontage road off-ramp of Interstate [XXX] proceeded through the intersection without stopping at the red light. The Waymo AV applied hard braking and the front of the Waymo AV made contact with the left side of the passenger car. 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. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11545WaymoSource file ↗Property damage only2025-08NHTSAWaymoPhoenix30270-11502Passenger Car · struck on the rear right · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- 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
- 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 August [XXX], 2025 at 1:47 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car in the West Parking Lot off of [XXX] at the [XXX]. The Waymo AV was parked facing south in a parking stall in the West Parking Lot off of [XXX]. While the Waymo AV remained parked, a passenger car that was parked in a separate row of parking stalls behind the Waymo AV proceeded forward to exit the parking stall and the front of the passenger car made contact with the rear left 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. 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-11502WaymoSource file ↗Property damage only2025-08NHTSAWaymoInglewood30270-11548struck on the right · passing
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Passing
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 2
- 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 August [XXX], 2025 at 12:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving vegetation in an alley behind [XXX]. The Waymo AV was traveling westbound in an alley behind [XXX] and proceeding to pass to the right of a passenger car that was parked facing east. As the Waymo AV was maneuvering around the passenger car, the right of the Waymo AV made contact with vegetation growing on the north wall of the alley and extending into 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. 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-11548WaymoSource file ↗Property damage only2025-08NHTSAWaymoLos Angeles30270-11508Pickup Truck · struck on the rear · parked
- Crash With
- Pickup Truck
- 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
- 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 August [XXX], 2025 at 11:21 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 stopped in-lane facing west on [XXX] for a passenger pick-up with hazard lights activated. A pickup truck hauling a flatbed trailer was traveling northbound on [XXX] and made a right turn onto eastbound [XXX]. As the pickup truck completed the turn and proceeded to pass the Waymo AV, the left side of the pickup truck made contact with the rear left 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-11508WaymoSource file ↗Property damage only2025-08NHTSAWaymoSan Francisco30270-11516Heavy Truck · struck on the left · proceeding straight
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 13
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 August 16, 2025 at 7:47 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] and [XXX]. The Waymo AV was traveling westbound on [XXX] when it came to a stop in the intersection with [XXX] to yield to a heavy truck that was traveling northwestbound on [XXX] and attempting to make a sharp left turn onto southbound [XXX]. The heavy truck reversed momentarily in the Waymo AV's lane of travel and proceeded forward before it stopped facing south for pedestrians that were crossing [XXX]. The Waymo AV proceeded to maneuver around the stationary heavy truck, passing to the rear of the truck. While the Waymo AV was passing behind the heavy truck, the heavy truck began reversing and the rear of the heavy 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. 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-11516WaymoSource file ↗Property damage only2025-08NHTSAWaymoSan Francisco30270-11765Passenger 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
- 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 August [XXX], 2025 at 11:03 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, a passenger car approached the Waymo AV from behind and the front of the passenger car 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. Waymo became aware of damage to the Waymo AV exceeding $1,000 on September 17, 2025. 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-11765WaymoSource file ↗Property damage only2025-08NHTSAWaymoSan Francisco30270-11590SUV · 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
- 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 August [XXX], 2025 at 12:18 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 it came to a stop to park in-lane for a passenger drop-off with its hazard lights activated. An SUV that was traveling behind the Waymo AV came to a stop behind the parked Waymo AV. While the Waymo AV remained stationary, the SUV proceeded to maneuver around the left side of the Waymo AV by crossing the double yellow center line and entering the opposing lane of travel. As the SUV passed the stationary Waymo AV the right side of the SUV made contact with the rear left side 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. 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-11590WaymoSource file ↗Minor injury2025-08NHTSAWaymoSan Francisco30270-11433Heavy Truck · struck on the rear · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Left
- 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 August [XXX], 2025 at 2:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on a narrow portion of [XXX] with vehicles parked at the curb in both directions when it approached a heavy truck that was traveling northbound on [XXX]. The Waymo AV reversed to yield to the heavy truck and came to a stop at the curb at the intersection with [XXX]. The heavy truck proceeded forward past the Waymo AV and began a left turn onto westbound [XXX] and the left side of the heavy truck made contact with the rear left 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 alleged a minor injury and was transported to a hospital 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-11433WaymoSource file ↗Property damage only2025-08NHTSAWaymoLos Angeles30270-11543SUV · 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
- Proceeding Straight
- CP Contact Area
- Front Left, 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 August [XXX], 2025 at 6:37 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Venice, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was parked partially in-lane at the curb facing southeast on [XXX] at [XXX] for a passenger pickup with its hazard lights activated. While the Waymo AV remained parked, an SUV traveling southeastbound on [XXX] passed the Waymo AV on the left and the front right side of the SUV made contact with the rear left 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-11543WaymoSource file ↗Property damage only2025-08NHTSAWaymoSan Francisco30270-11523Van · struck on the rear · stopped
- Crash With
- Van
- 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
- Proceeding Straight
- CP Contact Area
- Left
- 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 August [XXX], 2025 at 5:55 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 traveling northbound on a narrow portion of [XXX] when it slowed to a stop to yield to a van that was traveling southbound on [XXX]. As the van proceeded straight to pass the Waymo AV, the left side of the van made contact with the rear left side 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. 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-11523WaymoSource file ↗Property damage only2025-08NHTSAWaymoLos Angeles30270-11561struck on the left · 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
- Left
- SV Precrash Speed (MPH)
- 18
- 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 August [XXX], 2025 at 12:59 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a shopping cart on [XXX] near [XXX]. The Waymo AV was traveling northwestbound on [XXX] when a pedestrian standing in the roadway on the south side of [XXX] pushed a shopping cart towards the Waymo AV's lane of travel. The shopping cart 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. 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-11561WaymoSource file ↗Property damage only2025-08NHTSAWaymoPalo Alto30270-11588SUV · struck on the rear · stopped
- Crash With
- SUV
- 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
- Proceeding Straight
- CP Contact Area
- Front Left
- 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 August [XXX], 2025 at 10:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] when it came to a stop for the stop sign at the intersection with [XXX]. An SUV that was traveling behind the Waymo AV approached the Waymo AV from behind and the front right side of the SUV made contact with the rear left side 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. 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-11588WaymoSource file ↗Property damage only2025-08NHTSAWaymoSan Francisco30270-11501Pickup Truck · struck on the right · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Left
- 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 August [XXX], 2025 at 9:03 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 eastbound on [XXX] when a city bus that was traveling westbound on [XXX] approached in the oncoming direction. As the Waymo AV continued eastbound with the city bus on its left and a pickup truck that was parked facing east at the curb on the Waymo AV's right, the driver of the pickup truck opened the front left door and the right side of the Waymo AV made contact with the open front left door of the pickup truck. 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. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11501WaymoSource file ↗Property damage only2025-08NHTSAWaymoPhoenix30270-11546struck 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)
- 29
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Rain
- 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 August [XXX], 2025 at 8:14 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling westbound in the right lane on [XXX] when the front of the Waymo AV made contact with a fallen utility line hanging in the travel lane. 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-11546WaymoSource file ↗Property damage only2025-08NHTSAWaymoLos Angeles30270-11495Bus · struck on the rear · parked
- Crash With
- Bus
- 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 August [XXX], 2025 at 12:04 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a city bus 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. A bus was traveling southbound on [XXX] in the left adjacent lane. As the bus approached the parked Waymo AV, a Waymo AV passenger opened the rear left door and the right side of the bus made contact with the open left rear door 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. A passenger in the Waymo AV was not belted at the time of the collision as they were preparing to exit the Waymo AV. 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-11495WaymoSource file ↗Property damage only2025-08NHTSAWaymoCulver City30270-11547Heavy Truck · struck on the rear · stopped
- Crash With
- Heavy 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
- Proceeding Straight
- CP Contact Area
- 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 August [XXX], 2025 at 9:21 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped facing northwest on [XXX], yielding to a garbage truck traveling southeast in a narrow roadway with parked vehicles on both sides of the street. As the garbage truck passed the stopped Waymo AV, the left side of the garbage truck made contact with the rear left 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. 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-11547WaymoSource file ↗