HI-TORQUE FLOPPY 22299MRecalls & reported problems
Abbott Vascular Inc. · HI-TORQUE FLOPPY II EXTRA SUPPORT GuideWire .014 Straight Tip 2.0 cm x 190 cm · Class 2
Data updated Oct 16, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 2
- Deaths reported
- 0
- Injuries reported
- 1
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 08717648079696), received between Oct 17, 2016 and Mar 2, 2021 — classified as 1 injury, 1 malfunction.
The most frequently reported specific device problem is “Break” (1 report).
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.
Most reported problems
Device problems
- Break1
- Detachment Of Device Component1
- Stretched1
Patient problems
- Foreign Body In Patient1
- Insufficient Information1
Recent adverse event reports
The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.
MalfunctionMar 2, 2021Break; Stretched; Break; Stretched
IT WAS REPORTED THAT DURING A COMPLEX HEAVILY CALCIFIED MID-RIGHT CORONARY ARTERY INTERVENTION AFTER THE LESION WAS STENTED, ADDITIONAL LESIONS WERE NOTED DISTAL TO THE STENT. A HI TORQUE FLOPPY II EXTRA SUPPORT GUIDE WIRE (GW) WAS ADVANCED DISTALLY AND A BALLOON CATHETER WAS ADVANCED OVER THE WIRE TO DILATE THE DISTAL LESION. AFTER REMOVAL OF THE GW THROUGH THE BLEEDBACK VALVE, THE GW APPEARED TO HAVE SHEARED/UNRAVELED FROM THE PROXIMAL PART TO THE SOFT TIP OF THE WIRE. ALL DEVICES WERE REMOVED AT THAT TIME. NOTHING WAS LEFT IN THE PATIENT. THERE WAS NO ADVERSE PATIENT EFFECT OR A CLINICALLY SIGNIFICANT DELAY IN THE PROCEDURE. NO ADDITIONAL INFORMATION WAS PROVIDED.
Patient problems: Insufficient Information
MAUDE report 11402576 ↗InjuryOct 17, 2016Detachment Of Device Component
IT WAS REPORTED THAT THE PROCEDURE WAS TO TREAT A MILDLY TORTUOUS OBTUSE MARGINAL (OM) ARTERY. A HT FLOPPY ES GUIDE WIRE WAS USED DURING A PROCEDURE WHERE AN INTERVENTION WAS SUCCESSFULLY PERFORMED. AT THE END OF THE PROCEDURE WHEN THE DEVICES WERE REMOVED FROM THE ANATOMY, IT WAS NOTED THAT THE TIP OF THE GUIDE WIRE HAD SEPARATED AND REMAINED IN THE OM. THERE WAS NO REPORTED RESISTANCE ADVANCING OR REMOVING THE GUIDE WIRE. ATTEMPTS WERE MADE TO REMOVE THE TIP WITH A SNARE DEVICE BUT IT COULD NOT BE REMOVED AND REMAINS IN THE OM. THE PROCEDURE WAS COMPLETED AT THIS TIME WITHOUT ADDITIONAL TREATMENT. THERE WAS A CLINICALLY SIGNIFICANT DELAY IN THE PROCEDURE DUE TO THE ATTEMPTS TO REMOVE THE TIP. NO ADDITIONAL INFORMATION WAS PROVIDED.
Patient problems: Foreign Body In Patient
MAUDE report 6035322 ↗
Other WIRE, GUIDE, CATHETER devices
- HI-TORQUE BALANCE MIDDLEWEIGHT UNIVERSAL II 1009664Abbott Vascular Inc. · WIRE, GUIDE, CATHETER321 reports
- SYNCHRO 14 M00313010Stryker Corporation · WIRE, GUIDE, CATHETER2 recalls220 reports
- PressureWire™ C12059Lightlab Imaging, Inc. · WIRE, GUIDE, CATHETER1 death296 reports
- SYNCHRO 2 M00326410Stryker Corporation · WIRE, GUIDE, CATHETER2 recalls155 reports
- ENROUTE .014" Guidewire 11686-01Silk Road Medical, Inc. · Wire, Guide, Catheter2 deaths228 reports
- ARROW IPN035915Teleflex Incorporated · WIRE, GUIDE, CATHETER217 reports
- OmniWire Pressure guide wire 89185Philips Image Guided Therapy Corporation · Wire, Guide, Catheter1 recall1 death160 reports
- ARROW IPN055780Teleflex Incorporated · Wire, guide, catheter4 recalls0 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
- 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