TARGET M0035479300Recalls & reported problems
Stryker Corporation · 360 Soft Detachable Coil · Class 2 · Implant
All models of TARGET (114)
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 04546540676627), received between Oct 2, 2019 and Oct 4, 2023 — classified as 4 malfunctions.
The most frequently reported specific device problem is “Premature Separation” (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.
Reports received per month
Most reported problems
Device problems
- Premature Separation4
Patient problems
- No Clinical Signs, Symptoms or Conditions3
- No Consequences Or Impact To Patient1
Recent adverse event reports
The 4 most recent of 4 reports, in the reporter's own words as published by the FDA.
MalfunctionOct 4, 2023Premature Separation; Premature Separation
THE COIL (SUBJECT DEVICE) WAS RETURNED FOR ANALYSIS AND THE DEVICE INVESTIGATION REVEALED THAT THE COIL (SUBJECT DEVICE) HAD DETACHED PREMATURELY DURING USE. THE PROCEDURE WAS COMPLETED SUCCESSFULLY. NO CLINICAL CONSEQUENCES WERE REPORTED TO THE PATIENT DUE TO THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 17872932 ↗MalfunctionMay 9, 2023Premature Separation; Premature Separation
IT WAS REPORTED THAT DURING A NEUROVASCULAR PROCEDURE, RESISTANCE WAS FELT WHILE ADVANCING THE SUBJECT COIL THROUGH THE CATHETER. WHEN RETRIEVED, IT WAS FOUND THAT THE SUBJECT COIL HAD SEPARATED FROM THE DELIVERY WIRE INSIDE THE MICRO-CATHETER. THE SUBJECT COIL WAS REPLACED, AND THE PROCEDURE WAS COMPLETED SUCCESSFULLY. NO CLINICAL CONSEQUENCES WERE REPORTED TO THE PATIENT DUE TO THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 16900011 ↗MalfunctionJan 31, 2022Premature Separation; Premature Separation
ANALYSIS OF THE RETURNED DEVICE FOUND THAT THE SUBJECT COIL PREMATURELY DETACHED/SEPARATED DURING USE. THERE WERE NO CLINICAL CONSEQUENCES TO THE PATIENT REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 13395415 ↗MalfunctionOct 2, 2019Premature Separation; Premature Separation
IT WAS REPORTED THAT DURING PROCEDURE, WHILE PUSHING THE COIL INTO THE MICROCATHETER, THERE WAS A LOT OF FRICTION FELT. THE USER PULLED BACK THE COIL AND FOUND IT DETACHED IN THE HUB OF THE MICROCATHETER. THERE WERE NO CLINICAL CONSEQUENCES TO THE PATIENT.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9148921 ↗
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