Sphere-9™ AFR-00001Recalls & reported problems
Medtronic, Inc. · CATHETER AFR-00001 SPHERE 9 1PK US · Class 3
Data updated Oct 16, 2026 from official FDA records · Editorial policy
1 open recall names this device. See the recall details and contact the manufacturer or your healthcare provider.
- Adverse event reports
- 7
- Deaths reported
- 0
- Injuries reported
- 2
- Recalls naming it
- 1
Summary
The FDA's MAUDE database contains 7 adverse event reports that list this exact device (DI 00763000871741), received between Dec 4, 2024 and May 5, 2025 — classified as 2 injuries, 5 malfunctions.
The most frequently reported specific device problem is “Use of Device Problem” (3 reports).
1 FDA recall record name this device's identifier, 1 still open.
Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 16, 2026.
Reports received per month
Recalls naming this device
- Mar 11, 2026Open, Classified
Ventricular fibrillation (VF) occurred during radiofrequency (RF) therapy with the Medtronic Sphere-9 catheter in patients who have a Biotronik Implantable Cardioverter Defibrillator (ICD) or Biotronik Cardiac Resynchronization Therapy-Defibrillator (CRT-D) implanted. The observation is caused by an interaction between the Sphere-9 catheter current flow and a safety feature built into Biotronik ICDs and CRT Ds. Medtronic recommends physicians use increased caution when using the Sphere-9 catheter for RF ablation therapy in patients implanted with a Biotronik ICD/CRT-D system, and to ensure external defibrillation systems are readily available.
Z-1948-2026 · Root cause: Device Design · Recall details · FDA record ↗
Most reported problems
Device problems
- Use of Device Problem3
- Adverse Event Without Identified Device or Use Problem2
Patient problems
- No Clinical Signs, Symptoms or Conditions5
- Cardiac Tamponade1
- Pericardial Effusion1
- Ventricular Fibrillation1
Recent adverse event reports
The 7 most recent of 7 reports, in the reporter's own words as published by the FDA.
MalfunctionMay 5, 2025Use of Device Problem; Use of Device Problem
IT WAS REPORTED THAT DURING AN ATRIAL FIBRILLATION ABLATION PROCEDURE, A CATHETER TEMPERATURE SENSOR FAULT OCCURRED, WITH ONE OF THE TEMPERATURE SENSORS BEING OUT OF RANGE. THIS LED TO A PULSED FIELD DELIVERY ERROR AND AN ERROR MESSAGE BEING DISPLAYED, TEMPORARILY INTERRUPTING THE PROCEDURE. IT WAS NOTED THAT THE TRANSEPTAL APPROACH WAS CHALLENGING DUE TO AN ANEURYSMAL SEPTUM, AND THE CATHETER WAS EXCHANGED THROUGH ANOTHER MANUFACTURER'S SHEATH SEVERAL TIMES. CONNECTIONS WERE CHECKED, AND ULTIMATELY, A NEW CATHETER WAS USED TO SUCCESSFULLY COMPLETE THE PROCEDURE. NO FURTHER ISSUES WERE EXPERIENCED AFTER THE CATHETER WAS REPLACED. THE CASE WAS COMPLETED. NO PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 21959877 ↗InjuryJan 31, 2025Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
IT WAS REPORTED THAT DURING A CARDIAC ABLATION PROCEDURE, VENTRICULAR FIBRILLATION OCCURRED ON THE FIRST AND SECOND RADIOFREQUENCY (RF) LESIONS OF THE CAVOTRICUSPID ISTHMUS (CTI) LINE, NECESSITATING DEFIBRILLATION EACH TIME. THE PROCEDURE WAS SWITCHED TO PULSED FIELD (PF) ABLATION FOR THE REMAINING LESIONS ON THE CTI LINE, WHICH PROCEEDED WITHOUT FURTHER ISSUES. THE CASE WAS COMPLETED. NO FURTHER PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: Ventricular Fibrillation
MAUDE report 21283668 ↗MalfunctionJan 24, 2025Use of Device Problem; Use of Device Problem
IT WAS REPORTED THAT MATERIAL WAS FOUND IN THE ABLATION CATHETER POST-PROCEDURE. THE ISSUE OCCURRED DURING REMOVAL OF THE DEVICE. THERE WERE NO PATIENT SYMPTOMS OR COMPLICATIONS ASSOCIATED WITH THIS EVENT, AND NO MEDICAL OR SURGICAL INTERVENTION WAS NEEDED TO PREVENT A PERMANENT IMPAIRMENT OF A FUNCTION. THE EVENT DID NOT LEAD TO OR EXTEND PATIENT HOSPITALIZATION, AND THERE WAS NO INJURY AS A RESULT OF THE EVENT. NO PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 21230667 ↗MalfunctionJan 6, 2025
CHAR WAS PRESENT ON THE TIP OF THE CATHETER ON REMOVAL FROM BODY. NO PATIENT HARM.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 21078677 ↗MalfunctionJan 3, 2025Use of Device Problem; Use of Device Problem
IT WAS REPORTED THAT DURING A CARDIAC ABLATION PROCEDURE, THE CATHETER WAS REMOVED FROM THE BODY TO CLEAR A BUBBLE ALERT, AND UPON REMOVAL, BLOOD MATTER WAS NOTED ON THE LATTICE TIP OF THE CATHETER. IT WAS NOT POSSIBLE TO REMOVE THE BLOOD MATTER BY FLUSHING THROUGH THE PUMP OR BY MANUALLY CLEANING THE LATTICE. THE CATHETER WAS REPLACED, AND THE CASE WAS COMPLETED. THE ACTIVATED CLOTTING TIME (ACT) WAS ABOVE 350 SECONDS FOR THE DURATION OF THE ENTIRE CASE AND BEFORE THE CATHETER ENTERED THE BODY. NO PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 21072072 ↗MalfunctionJan 3, 2025
ABLATION CATHETER NOT RECOGNIZED WHEN CONNECTED TO AFFERA MAPPING SYSTEM. REPLACED WITH RESOLUTION OF ISSUE.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 21066164 ↗InjuryDec 4, 2024Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
IT WAS REPORTED THAT DURING A PULSED FIELD ABLATION PROCEDURE, A PERICARDIAL EFFUSION WAS OBSERVED ON INTRACARDIAC ECHOCARDIOGRAPHY (ICE) AFTER THE CATHETER WAS WITHDRAWN FROM THE LEFT ATRIUM AND INTO THE RIGHT ATRIUM. A PERICARDIAL TAP WAS PERFORMED TO REMOVE BLOOD FROM THE PERICARDIAL SPACE. A CARDIOTHORACIC SURGEON WAS CONSULTED, AND A MEDIAN STERNOTOMY WAS PERFORMED. IT WAS FURTHER REPORTED THAT UPON DIRECT VISUAL INSPECTION OF THE HEART, THERE WERE NO PERFORATIONS NOTED AND NO ACTIVE BLEEDING. THE PATIENT REGAINED HEMODYNAMIC STABILITY AND REMAINED STABLE. THE PROCEDURE WAS ABORTED WHILE THE PATIENT WAS UNDER GENERAL ANESTHESIA. THE PATIENT'S HOSPITALIZATION WAS EXTENDED FOR AN UNKNOWN DURATION. NO FURTHER PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: Cardiac Tamponade; Pericardial Effusion
MAUDE report 20847740 ↗
Other catheter, percutaneous, cardiac ablation, for treatment of atrial flutter devices
- QDOT MICRO D139505Biosense Webster Inc · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter27 deaths915 reports
- IntellaNav MiFi™ Open-Irrigated M004PMR96200Boston Scientific Corporation · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter4 deaths269 reports
- QDOT MICRO D139504Biosense Webster Inc · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter7 deaths138 reports
- Sphere-9™ Catheter AFR-00001Medtronic, Inc. · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter1 recall5 deaths77 reports
- QDOT MICRO D139401Biosense Webster Inc · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter2 deaths114 reports
- NaviStar ThermoCool NI75TCDHBiosense Webster Inc · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter111 reports
- NaviStar RMT ThermoCool NR7TCSIYBiosense Webster Inc · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter9 deaths103 reports
- IntellaNav MiFi™ Open-Irrigated M004PMR9620K20Boston Scientific Corporation · catheter, percutaneous, cardiac ablation, for treatment of atrial flutter78 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026 · each recall links to the FDA recall notice
- Page last rebuilt: Oct 16, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page