Skip to content

ANCHORAGE PLP11342Recalls & reported problems

Stryker GmbH · Plate MTP, right · Class 2 · Implant

All models of ANCHORAGE (52)

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

Adverse event reports
6
Deaths reported
0
Injuries reported
3
Recalls naming it
0

Summary

The FDA's MAUDE database contains 6 adverse event reports that list this exact device (DI 07613252260516), received between Feb 20, 2019 and Mar 3, 2026 — classified as 3 injuries, 3 malfunctions.

The most frequently reported specific device problem is “Device Damaged by Another Device” (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.

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 0 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 0 reportsMar 2025: 0 reportsApr 2025: 0 reportsMay 2025: 0 reportsJun 2025: 0 reportsJul 2025: 0 reportsAug 2025: 0 reportsSep 2025: 0 reportsOct 2025: 0 reportsNov 2025: 0 reportsDec 2025: 0 reportsJan 2026: 0 reportsFeb 2026: 0 reportsMar 2026: 3 reportsApr 2026: 0 reportsMay 2026: 0 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports2024202520263
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Adverse Event Without Identified Device or Use Problem2
  • Device Damaged by Another Device1
  • Fitting Problem1
  • Material Fragmentation1
  • Material Protrusion/Extrusion1
  • Positioning Failure1
  • Structural Problem1

Patient problems

  • No Clinical Signs, Symptoms or Conditions2
  • Insufficient Information1
  • No Known Impact Or Consequence To Patient1
  • Nonunion/Delayed-union Bone Fracture1
  • Pain1

Recent adverse event reports

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

  • InjuryMar 3, 2026Structural Problem

    THE MANUFACTURER RECEIVED RWE REPORT NAMED "SAFETY AND PERFORMANCE OF THE ANCHORAGE AND ANCHORAGE 2 CP IMPLANTS UTILIZING THE PREMIER HEALTHCARE DATABASE" THAT CONTAINS COLLECTED DATA ON THE USAGE AND THE OUTCOMES OF ANCHORAGE AND ANCHORAGE 2 CP. THE REPORT DETAILS ANALYSIS PROVIDED FOR PROCEDURES PERFORMED BETWEEN 1 JAN 2016 ¿ 30 MAR 2025 DURING THE REVIEW OF THE REPORT, IT WAS NOT POSSIBLE TO ESTABLISH A SPECIFIC DEVICE DETAIL, PATIENT INFORMATION, AND CURRENTLY NO ADDITIONAL DEVICE INFORMATION IS AVAILABLE; HOWEVER, PATIENT 138 HAD STRUCTURAL PROBLEM.

    Patient problems: Insufficient Information

    MAUDE report 24497649 ↗
  • InjuryMar 3, 2026Adverse Event Without Identified Device or Use Problem

    THE MANUFACTURER RECEIVED RWE REPORT NAMED "SAFETY AND PERFORMANCE OF THE ANCHORAGE AND ANCHORAGE 2 CP IMPLANTS UTILIZING THE PREMIER HEALTHCARE DATABASE" THAT CONTAINS COLLECTED DATA ON THE USAGE AND THE OUTCOMES OF ANCHORAGE AND ANCHORAGE 2 CP. THE REPORT DETAILS ANALYSIS PROVIDED FOR PROCEDURES PERFORMED BETWEEN 1 JAN 2016 ¿ 30 MAR 2025 DURING THE REVIEW OF THE REPORT, IT WAS NOT POSSIBLE TO ESTABLISH A SPECIFIC DEVICE DETAIL, PATIENT INFORMATION, AND CURRENTLY NO ADDITIONAL DEVICE INFORMATION IS AVAILABLE; HOWEVER, PATIENT 146 HAD GENERALIZED PAIN.

    Patient problems: Pain

    MAUDE report 24495333 ↗
  • InjuryMar 3, 2026Adverse Event Without Identified Device or Use Problem

    THE MANUFACTURER RECEIVED RWE REPORT NAMED "SAFETY AND PERFORMANCE OF THE ANCHORAGE AND ANCHORAGE 2 CP IMPLANTS UTILIZING THE PREMIER HEALTHCARE DATABASE" THAT CONTAINS COLLECTED DATA ON THE USAGE AND THE OUTCOMES OF ANCHORAGE AND ANCHORAGE 2 CP. THE REPORT DETAILS ANALYSIS PROVIDED FOR PROCEDURES PERFORMED BETWEEN 1 JAN 2016 ¿ 30 MAR 2025 DURING THE REVIEW OF THE REPORT, IT WAS NOT POSSIBLE TO ESTABLISH A SPECIFIC DEVICE DETAIL, PATIENT INFORMATION, AND CURRENTLY NO ADDITIONAL DEVICE INFORMATION IS AVAILABLE; HOWEVER, PATIENT 149 HAD NONUNION.

    Patient problems: Nonunion/Delayed-union Bone Fracture

    MAUDE report 24495054 ↗
  • MalfunctionJan 26, 2021Material Fragmentation; Device Damaged by Another Device; Material Fragmentation; Device Damaged by Another Device

    AS REPORTED: "PRIMARY PROCEDURE, RIGHT FIRST MTP. IT WAS REPORTED THAT WHEN THE DRILL GUIDE WAS SEATED INTO A HOLE OF THE PLATE AND AFTER DRILLING WAS DONE, A THREAD-LIKE PIECE OF METAL WAS SEEN IN THE PATIENT. THE PIECE WAS REMOVED BY THE SURGEON. SURGEON REPORTED THAT IT FELT AS THOUGH THE DRILL GUIDE DID NOT SEEM TO BE SEATING AS DEEPLY IN THE HOLE AS IT HAD IN THE PREVIOUS HOLES, AND BELIEVES THAT THE THREAD OF METAL WAS SHAVED OFF OF THE PLATE WHILE DRILLING. PROCEDURE WAS COMPLETED SUCCESSFULLY WITH NO DELAY."

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 11229114 ↗
  • MalfunctionDec 22, 2020Positioning Failure; Positioning Failure

    IT WAS REPORTED THAT, "THE SCREWS COULD NOT BE SCREWED ON THE PLATE DELAY OF INTERVENTION; NO PATIENT CONSEQUENCES."

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 11060307 ↗
  • MalfunctionFeb 20, 2019Fitting Problem; Material Protrusion/Extrusion

    THE FOLLOWING EVENT WAS REPORTED BY CLINIC: DESPITE THE USE OF THE BARREL ON THE PLATE ANCHORAGE MTP RIGHT (REF PLP11342), THE SCREW DIAMETER 3 LOCKING DOES NOT FIT CORRECTLY IN THE HOLE. THREADING PROBLEM WAS OBSERVED AND 1 WIRE CAME OUT OF THE SCREW. THE SCREW PROTRUDES FROM THE PLATE AND A METAL WIRE COMES OUT OF THE SCREW. THE SCREW WAS REMOVED AND ANOTHER SCREW REINSERTED.

    Patient problems: No Known Impact Or Consequence To Patient

    MAUDE report 8356235 ↗

Other PLATE, FIXATION, BONE devices

All PLATE, FIXATION, BONE devices →

Sources and updates

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