Devices › Catheter, percutaneous, cardiac ablation, for treatment of atrial flutter
Device brand name · Catheter percutaneous cardiac ablation for treatment of atrial flutter
Flexability Ablation Catheter Sensor Enabled: medical device reports filed with FDA
210 reports name it, 2017–2026. Manufacturer given most often on reports: St Jude Medical. Product code OAD.
- 210
- device reports naming the brand
- 0% of all MAUDE reports · about 23 a year
- 9
- reports, 12 months to August 2026
- 13 in the 12 months before
- 14.3%
- classified as malfunction
- 48.6% across the product code
- 9%
- classified as death, as reported
- 19 reports · not verified by FDA
FDA's MAUDE database holds 210 reports that name the brand "Flexability Ablation Catheter Sensor Enabled" (catheter percutaneous cardiac ablation for treatment of atrial flutter), received between March 2017 and July 2026; the manufacturer given most often on reports is St Jude Medical. Spellings of one product vary from report to report.
9 reports arrived in the 12 months to August 2026, down 31% from 13 in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are injury (76.7%), malfunction (14.3%) and death (9%); across all catheter, percutaneous, cardiac ablation, for treatment of atrial flutter reports (product code OAD) death is recorded in 3.7% and malfunction in 48.6%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are patient device interaction problem (5.7%), communication or transmission problem (3.8%) and fracture (3.8%). The patient problems coded most often are cardiac perforation, death and arrhythmia. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 5,961 reports carrying product code OAD. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| Patient device interaction problem | 12 | 5.7% | 4% |
| Communication or transmission problemthe device could not communicate or transmit | 8 | 3.8% | 1.5% |
| Fracturea broken bone | 8 | 3.8% | 0.6% |
| Impedance problem | 5 | 2.4% | 0.8% |
| Display or visual feedback problem | 4 | 1.9% | 0.1% |
| Signal artifact/noise | 4 | 1.9% | 1.3% |
| Temperature problem | 4 | 1.9% | 4.4% |
| Difficult to removethe device was hard to remove | 2 | 1% | 0.5% |
| Material deformation | 2 | 1% | 0.3% |
| Detachment of device component | 1 | 0.5% | 3.7% |
| Detachment of device or device componentpart of the device came off | 1 | 0.5% | 0.4% |
| Difficult to insertthe device was hard to insert | 1 | 0.5% | 0% |
| Insufficient device problem information | 1 | 0.5% | 8.1% |
| Material too rigid or stiff | 1 | 0.5% | 0% |
| Overheating of device | 1 | 0.5% | 0.3% |
| Pacing problem | 1 | 0.5% | 0% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| Cardiac perforation | 124 | 59% |
| Deaththe patient died; cause not stated by this term | 12 | 5.7% |
| Arrhythmia | 7 | 3.3% |
| Heart block | 5 | 2.4% |
| Aortic dissection | 4 | 1.9% |
| Thrombosis/thrombus | 4 | 1.9% |
| Complete heart block | 3 | 1.4% |
| Mitral insufficiency | 3 | 1.4% |
| Pericardial effusionfluid around the heart | 3 | 1.4% |
| Stroke/cva | 3 | 1.4% |
| Tissue damage | 3 | 1.4% |
| Vascular dissection | 3 | 1.4% |
| Cardiac arrestthe heart stopped | 2 | 1% |
| Cardiogenic shockshock from the heart failing to pump | 2 | 1% |
| Great vessel perforation | 2 | 1% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Flexability Ablation Catheter Sensor Enabled | Product code OAD | All MAUDE reports |
|---|---|---|---|
| Reports | 210 | 5,961 | 26,136,888 |
| Share of that pool | — | 3.5% | 0% |
| Classified as death, per 1,000 reports | 90 | 37 | 9 |
| Classified as injury | 76.7% | 47.2% | 36.2% |
| Classified as malfunction | 14.3% | 48.6% | 62.3% |
| Filed by the manufacturer | 100% | 95.8% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code OAD
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| IntellaNav MiFi? Open-Irrigated | 466 | 6 | 1.1% |
| IntellaNav MiFi Open-Irrigated Ablation Catheter | 448 | 13 | 1.1% |
| NaviStar ThermoCool | 673 | 20 | 7% |
| Ez Steer Thermocool Nav Bi-Directional Catheter | 302 | 0 | 6.3% |
| Navi-Star Thermo-Cool Electrophysiology Catheter | 259 | 2 | 1.9% |
| Intellatip Mifi Xp Temperature Ablation Catheter | 166 | 0 | 0% |
| Therapy Ablation Catheter | 182 | 7 | 0.5% |
| Navistar Rmt Thermocool Electrophysiology Catheter | 170 | 0 | 7.1% |
| Ampere RF Ablation Generator | 177 | 14 | 1.1% |
| Unk Navistar Thermocool | 220 | 0 | 4.5% |
| Unk Smart Touch Bidirectional | 213 | 0 | 1.4% |
| QDOT Micro | 1,169 | 390 | 3% |
| Thermocool Smarttouch Uni-Directional Navigation Catheter | 663 | 0 | 4.1% |
| Thermocool Smarttouch Bi-Directional Navigation Catheter | 1,224 | 0 | 5% |
| Qdot Micro Catheter | 538 | 37 | 3.5% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about Flexability Ablation Catheter Sensor Enabled reports
How many FDA reports name Flexability Ablation Catheter Sensor Enabled?
210 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 9 in the latest 12 months.
What kinds of events are reported?
injury (76.7%), malfunction (14.3%) and death (9%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
patient device interaction problem (5.7%), communication or transmission problem (3.8%), fracture (3.8%), impedance problem (2.4%) and display or visual feedback problem (1.9%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (100%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Flexability Ablation Catheter Sensor Enabled was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.