RunWay™ H74938969060Recalls & reported problems
Boston Scientific Corporation · Guide Catheter · Class 2
All models of RunWay (18)
Data updated Oct 16, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 4
- Deaths reported
- 0
- Injuries reported
- 0
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 4 adverse event reports that list this exact device (DI 08714729477679), received between Oct 26, 2020 and Jun 20, 2023 — classified as 4 malfunctions.
The most frequently reported specific device problem is “Break” (4 reports).
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
- Break4
Patient problems
- No Clinical Signs, Symptoms or Conditions4
- No Patient Involvement1
Recent adverse event reports
The 4 most recent of 4 reports, in the reporter's own words as published by the FDA.
MalfunctionJun 20, 2023Break; Break
IT WAS REPORTED THAT DEVICE DETACHMENT OCCURRED. A 6F RUNWAY GUIDE CATHETER WAS UNPACKED; HOWEVER, DEVICE WAS NOTED TO BE DAMAGED WITH BREAKAGES. THE PROCEDURE WAS COMPLETED WITH ANOTHER OF THE SAME DEVICE. NO PATIENT COMPLICATIONS WERE REPORTED, AND PATIENT'S STATUS WAS STABLE.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 17162331 ↗MalfunctionJun 13, 2023Break; Break
IT WAS REPORTED THAT DEVICE DETACHMENT OCCURRED. TWO 6F RUNWAY GUIDE CATHETERS WERE UNPACKED; HOWEVER, DEVICES WERE NOTED TO BE DAMAGED WITH BREAKAGES. THE PROCEDURE WAS COMPLETED WITH ANOTHER OF THE SAME DEVICE. NO PATIENT COMPLICATIONS WERE REPORTED, AND PATIENT'S STATUS WAS STABLE.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 17119336 ↗MalfunctionJun 13, 2023Break; Break
IT WAS REPORTED THAT DEVICE DETACHMENT OCCURRED. TWO 6F RUNWAY GUIDE CATHETERS WERE UNPACKED; HOWEVER, DEVICES WERE NOTED TO BE DAMAGED WITH BREAKAGES. THE PROCEDURE WAS COMPLETED WITH ANOTHER OF THE SAME DEVICE. NO PATIENT COMPLICATIONS WERE REPORTED, AND PATIENT'S STATUS WAS STABLE.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 17119335 ↗MalfunctionOct 26, 2020Break; Break
IT WAS REPORTED THAT CATHETER BROKE DURING UNPACKING. A 6F RUNWAY FL3.5 RUNWAY CATHETER WAS SELECTED FOR A CORONARY ANGIOPLASTY. WHEN TAKING THE CATHETER OUT OF ITS PACKAGING, THE CATHETER BODY WAS BROKEN. NO PATIENT COMPLICATIONS WERE REPORTED.
Patient problems: No Clinical Signs, Symptoms or Conditions; No Patient Involvement
MAUDE report 10734208 ↗
Other CATHETER, PERCUTANEOUS devices
- WATCHMAN FXD Curve™ Access System M635TU80020Boston Scientific Corporation · Catheter, percutaneous1 recall47 deaths654 reports
- NA C315HIS02Medtronic, Inc. · Catheter, percutaneous1 recall369 reports
- WATCHMAN TruSteer™ Access System M635TU90050Boston Scientific Corporation · Catheter, percutaneous1 recall28 deaths302 reports
- Guidezilla™ II H7493933515060Boston Scientific Corporation · CATHETER, PERCUTANEOUS1 recall3 deaths278 reports
- Velocity Delivery Microcatheter VEL160STR-APenumbra, Inc. · CATHETER, PERCUTANEOUS297 reports
- Guidezilla™ H7493924215050Boston Scientific Corporation · CATHETER, PERCUTANEOUS294 reports
- WATCHMAN™ TruSeal™ Access System M635TU70020Boston Scientific Corporation · Catheter, percutaneous1 recall11 deaths217 reports
- Lantern Delivery Catheter PXSLIMLAN135T45Penumbra, Inc. · CATHETER, PERCUTANEOUS220 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