Skip to content

NC Euphora™ NCEUP32520XRecalls & reported problems

Medtronic, Inc. · BALLOON NCEUP32520X NCEUPHORA RX US · Class 2

All models of NC Euphora (40)

Data updated Oct 16, 2026 from official FDA records · Editorial policy

Adverse event reports
1
Deaths reported
0
Injuries reported
1
Recalls naming it
0

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 00643169395787), received between Apr 26, 2019 and Apr 26, 2019 — classified as 1 injury.

The most frequently reported specific device problem is “Burst Container or Vessel” (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

  • Burst Container or Vessel1
  • Detachment of Device or Device Component1

Patient problems

  • Patient Problem/Medical Problem1

Recent adverse event reports

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

  • InjuryApr 26, 2019Burst Container or Vessel; Detachment of Device or Device Component; Burst Container or Vessel; Detachment of Device or Device Component

    DURING A PROCEDURE AN NC EUPHORA RX PTCA BALLOON CATHETER WAS USED TO TREAT THE MID RCA. IT IS REPORTED THAT THE BALLOON RUPTURED WHEN INFLATED TO DILATE THE MID RCA. UPON EXTRACTING THE BALLOON IT WAS NOTED THAT PART OF THE BALLOON REMAINED IN THE RCA. THE BALLOON FRAGMENT WAS EXCLUDED BY REALIGNING THE VESSEL WITH AN OVERLAPPING STENT. THERE IS NO FURTHER PATIENT INJURY REPORTED.

    Patient problems: Patient Problem/Medical Problem

    MAUDE report 8554104 ↗

Other Catheters, transluminal coronary angioplasty, percutaneous devices

All Catheters, transluminal coronary angioplasty, percutaneous devices →

Sources and updates

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