LCS COMPLETE POROCOAT 1294-03-070Recalls & reported problems
Depuy Orthopaedics, Inc. · LCS COMPLETE PRIMARY FEMORAL POROCOAT LRG+ RIGHT · Class 3 · Implant
All models of LCS COMPLETE POROCOAT (9)
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 10603295021728), received between Nov 3, 2017 and Jun 14, 2021 — classified as 2 injuries.
The most frequently reported specific device problem is “Malposition of 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 18, 2026.
Most reported problems
Device problems
- Adverse Event Without Identified Device or Use Problem1
- Malposition of Device1
Patient problems
- Appropriate Clinical Signs, Symptoms and Conditions Term/Code Not Available1
- Limited Mobility Of The Implanted Joint1
Recent adverse event reports
The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.
InjuryJun 14, 2021Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
A. PLEASE VERIFY IF THERE WAS A CONFIRMED INFECTION? 1) THERE WAS NO MICROBIAL CONFIRMATION IN EITHER THE ONE WEEK OR TWO WEEK CULTURES, HOWEVER DR (B)(6) STATED TO ME THAT HIS CONCLUSION WAS INFECTION DUE TO OSTEOLYSIS OF THE SURROUNDING TISSUE. B. STATED IN THE EVENT, "REASON FOR REVISION: TIBIAL LOOSENING." PLEASE CONFIRM WHAT INTERFACE WAS LOOSE. 2) THE BONE-CEMENT INTERFACE WAS LOOSE. C. WAS LOOSENING DUE TO INFECTION? 3) UNKNOWN, BUT THE LOOSENING WAS PRESUMED TO BE DUE TO INFECTION.
Patient problems: Appropriate Clinical Signs, Symptoms and Conditions Term/Code Not Available
MAUDE report 11994841 ↗InjuryNov 3, 2017Malposition of Device; Malposition of Device
DER STATES THAT THERE WAS MALALIGNMENT OF LCS FEMORAL COMPONENT LEADING TO LIMITED ROM IN THE KNEE. IT WAS REPORTED THAT THE SURGEON EXPLANTED FEMUR AND POLY AND REVISING WITH SIGMA FEMUR.
Patient problems: Limited Mobility Of The Implanted Joint
MAUDE report 6998672 ↗
Other Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing devices
- ATTUNE 1506-10-005Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing442 reports
- ATTUNE 1506-10-004Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing442 reports
- ATTUNE 1518-20-038Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing3 deaths393 reports
- LCS SIGMA 1294-33-130Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing1 recall310 reports
- ATTUNE 1518-20-035Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing342 reports
- P.F.C. SIGMA 96-0102Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing1 death319 reports
- ATTUNE 1518-20-041Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing308 reports
- ATTUNE 1506-10-007Depuy (Ireland) · Prosthesis, knee, patellofemorotibial, semi-constrained, metal/polymer, mobile bearing284 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