Mectalif Posterior 03.27.007Recalls & reported problems
Medacta International SA · Posterior Interbody Fusion Device 11x22x9 L5° · Class 2 · Implant
Data updated Oct 18, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 2
- Deaths reported
- 0
- Injuries reported
- 2
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 07630030831492), received between Oct 20, 2017 and Jun 12, 2020 — classified as 2 injuries.
The most frequently reported specific device problem is “Device Dislodged or Dislocated” (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
- Device Dislodged or Dislocated1
- Loose or Intermittent Connection1
- Migration or Expulsion of Device1
Patient problems
- Joint Disorder1
- Neurological Deficit/Dysfunction1
- No Code Available1
Recent adverse event reports
The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.
InjuryJun 12, 2020Device Dislodged or Dislocated
PRIMARY SURGERY WAS PERFORMED ON (B)(6). PLIF SURGERY WAS PERFORMED AT L5-S1. THE SURGEON DISCOVERED THE BACKOUT OF ONE CAGE. REVISION SURGERY WAS PERFORMED ON MAY 13. THE SURGEON REMOVED THE BOTH CAGES AND REPLACED WITH THE OBLIQUE CAGES. THE PEDICLE SCREW SYSTEM WAS NOT MEDACTA.
Patient problems: No Code Available
MAUDE report 10147519 ↗InjuryOct 20, 2017Loose or Intermittent Connection; Migration or Expulsion of Device
THE PRIMARY SURGERY ON L4-L5 WAS FINISHED SUCCESSFULLY AS USUAL. THE SURGEON USED A MEDACTA SPINAL CAGE WITH NON-MEDACTA PEDICLE SCREWS. AFTER THE SURGERY FOLLOW-UP, THE SURGEON CONFIRMED THE MIGRATION OF ONE CAGE AND THE LOOSENING OF THE SCREW ON ONE SIDE. PATIENT HAD NEUROLOGIC SYMPTOMS. THE REVISION SURGERY WAS COMPLETED SUCCESSFULLY ON (B)(6) 2017. THE SURGEON FELT THAT THE CAGE HAD A ROOT CAUSE, EVEN IF LOOSENING OF ONE SCREW WAS ALSO DETECTED. EVEN THOUGH MECTALIF TIPEEK CAGES HAVE A TITANIUM COATING, THE SURGEON HAS AN IMPRESSION THAT MECTALIF TIPEEK CAGES TEND TO MIGRATE BECAUSE THE SURFACE ROUGHNESS AND THE HEIGHT OF PYRAMIDS WOULD BE LOWER THAN OTHER CAGES ON THE MARKET.
Patient problems: Joint Disorder; Neurological Deficit/Dysfunction
MAUDE report 6965045 ↗
Other Intervertebral Fusion Device With Bone Graft, Lumbar devices
- T-PAL 03.812.003Synthes GmbH · Intervertebral fusion device with bone graft, lumbar152 reports
- T-PAL 03.812.004Synthes GmbH · Intervertebral fusion device with bone graft, lumbar120 reports
- Catalyft PL Expandable Interbody System 6068073Medtronic Sofamor Danek, Inc. · Intervertebral fusion device with bone graft, lumbar1 recall66 reports
- Catalyft PL Expandable Interbody System 6069076Medtronic Sofamor Danek, Inc. · Intervertebral fusion device with bone graft, lumbar1 recall51 reports
- Catalyft PL Expandable Interbody System 6068076Medtronic Sofamor Danek, Inc. · Intervertebral fusion device with bone graft, lumbar1 recall46 reports
- EIT TLIF Inserter TFT30101EIT Emerging Implant Technologies GmbH · Intervertebral Fusion Device With Bone Graft, Lumbar88 reports
- T-PAL 03.812.001Synthes GmbH · Intervertebral fusion device with bone graft, lumbar76 reports
- Catalyft PL Expandable Interbody System 6069096Medtronic Sofamor Danek, Inc. · Intervertebral fusion device with bone graft, lumbar1 recall25 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 18, 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