Skip to content

Turbo-Flo HD G35109Recalls & reported problems

Cook Incorporated · Cook Turbo-Flo HD Hemodialysis Catheter Tray Double Lumen Polyurethane · Class 2

Data updated Oct 18, 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 00827002351097), received between May 17, 2018 and Aug 1, 2018 — classified as 1 injury, 1 malfunction.

The most frequently reported specific device problem is “Crack” (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 18, 2026.

Most reported problems

Device problems

  • Crack1
  • Leak/Splash1
  • Unraveled Material1

Patient problems

  • No Code Available1
  • No Known Impact Or Consequence To Patient1

Recent adverse event reports

The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.

  • InjuryAug 1, 2018Crack; Leak/Splash; Crack; Leak/Splash

    NO NEW EVENT DESCRIPTION INFORMATION TO REPORT AT THIS TIME.

    Patient problems: No Code Available

    MAUDE report 7739880 ↗
  • MalfunctionMay 17, 2018Unraveled Material

    IT WAS REPORTED THAT THE PHYSICIAN INSERTED THE TURBO-FLO HD HEMODIALYSIS CATHETER INTO THE RIGHT FEMORAL. THE PROCEDURE SEEMED TO GO WELL, BUT THE GUIDE WIRE COMPLETELY UNRAVELED UPON REMOVAL. THERE WERE NO PIECES LEFT IN THE PATIENT, AND THERE WERE NO REPORTED SERIOUS INJURIES TO THE PATIENT AS A RESULT OF THE PRODUCT PROBLEM.

    Patient problems: No Known Impact Or Consequence To Patient

    MAUDE report 7522800 ↗

Other CATHETER, HEMODIALYSIS, NON-IMPLANTED devices

All CATHETER, HEMODIALYSIS, NON-IMPLANTED devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page