ORBIT GALAXY ENPOWER 641CF0308Recalls & reported problems
Medos International Sàrl · ORBIT GALAXY G2 microcoil Stretch Resistant Complex Fill Coil 3mm x 8cm 190cm Contents: 1 Detachable Coil System Coil Type: Stretch Resistant Complex Fill Coil · Class 2 · Implant
All models of ORBIT GALAXY ENPOWER (16)
Data updated Oct 16, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 2
- Deaths reported
- 0
- Injuries reported
- 0
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 10878528009488), received between Sep 2, 2016 and Feb 24, 2017 — classified as 2 malfunctions.
The most frequently reported specific device problem is “Stretched” (2 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
- Stretched2
Patient problems
- No Consequences Or Impact To Patient2
Recent adverse event reports
The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.
MalfunctionFeb 24, 2017Stretched; Stretched
AS REPORTED BY A HEALTHCARE PROFESSIONAL, A G2 COMPLEX FILL COIL STRETCHED AFTER THE FIRST OPTICAL INSPECTION WHILE PULLING IT BACK INTO THE INTRODUCER SHEATH. THE COIL WAS NOT USED ON THE PATIENT AND HAD BEEN STORED CORRECTLY. WHEN ADVANCING THE DPU WIRE THROUGH THE INTRODUCER SHEATH TO INSPECT THE COIL, IT MOVED SMOOTHLY THROUGH THE SHEATH WITH NO RESISTANCE. WHEN THE COIL WAS EXPOSED, THERE WERE NO KINKS, BURRS, STRETCHING STRIATIONS OR OTHER DAMAGED NOTICED. THERE WERE NO KNOWN FACTORS THAT MAY HAVE CONTRIBUTED TO THE COIL STRETCHING. THE PROCEDURE WAS COMPLETED WITH A SAME/LIKE PRODUCT WITH NO PATIENT INJURY OR SIGNIFICANT DELAY REPORTED. IT WAS REPORTED THAT THE PRODUCT WOULD BE RETURNED FOR ANALYSIS.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 6356116 ↗MalfunctionSep 2, 2016Stretched; Stretched
AS REPORTED BY A HEALTH CARE PROFESSIONAL, DURING THE PROCEDURE A GALAXY2 COIL (641CF0308/P11823) COULD NOT BE ADVANCED INTO A PROWLER SELECT PLUS MICROCATHETER (LOT UNKNOWN) AND POKED THROUGH SLIT IN THE PROTECTIVE SHEATH. IT WAS REPORTED THAT MULTIPLE GALAXY 2 COILS WERE SUCCESSFULLY DEPLOYED, IT IS UNKNOWN IF THEY WERE DEPLOYED PRIOR TO OR AFTER THE EVENT. THERE WERE NO SERIOUS INJURIES TO THE PATIENT OR MEDICAL INTERVENTIONS REQUIRED DUE TO THE REPORTED EVENT. THE EVENT OCCURRED PRIOR TO THE PRODUCT BEING INTRODUCED INTO THE PATIENT. PATIENT DETAILS AND PROCEDURE INFORMATION ARE UNKNOWN. IT WAS REPORTED THAT THE COMPLAINT PRODUCT IS AVAILABLE FOR RETURN.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 5925535 ↗
Other DEVICE, NEUROVASCULAR EMBOLIZATION devices
- POD RBYPODJ60-APenumbra, Inc. · DEVICE, NEUROVASCULAR EMBOLIZATION355 reports
- Penumbra System SCH1Penumbra, Inc. · DEVICE, NEUROVASCULAR EMBOLIZATION295 reports
- RUBY Coil RBY4C0860-APenumbra, Inc. · DEVICE, NEUROVASCULAR EMBOLIZATION276 reports
- Smart Coil 400SMTHXSFT0208Penumbra, Inc. · DEVICE, NEUROVASCULAR EMBOLIZATION165 reports
- Penumbra System RH1-APenumbra, Inc. · DEVICE, NEUROVASCULAR EMBOLIZATION154 reports
- Optima Coil System OPTI0208CSS10Balt USA LLC · Device, Neurovascular Embolization3 recalls3 reports
- POD RBYPOD6-APenumbra, Inc. · DEVICE, NEUROVASCULAR EMBOLIZATION148 reports
- POD RBYPODJ30-APenumbra, Inc. · DEVICE, NEUROVASCULAR EMBOLIZATION132 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