Skip to content

Optetrak Logic 02-012-45-3525Recalls & reported problems

Exactech, Inc. · Class 2 · Implant

All models of Optetrak Logic (408)

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 10885862003980), received between Dec 11, 2024 and Feb 25, 2025 — classified as 2 injuries.

The most frequently reported specific device problem is “Loosening of Implant Not Related to Bone-Ingrowth” (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 18, 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: 1 reportsJan 2025: 0 reportsFeb 2025: 1 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: 0 reportsApr 2026: 0 reportsMay 2026: 0 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports2024202520261
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Loosening of Implant Not Related to Bone-Ingrowth2

Patient problems

  • Osteolysis2
  • Implant Pain1

Recent adverse event reports

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

  • InjuryFeb 25, 2025Loosening of Implant Not Related to Bone-Ingrowth; Loosening of Implant Not Related to Bone-Ingrowth

    AS REPORTED, APPROXIMATELY 7 YEARS AND 1 MONTH POST THE INITIAL LEFT TOTAL KNEE ARTHROPLASTY, THIS CASE WAS SCHEDULED AS JUST A POLY EXCHANGE DUE TO THE RECALL. ONCE THE SURGEON DISSECTED DOWN HE REALIZED THE FEMUR WAS FALLING OFF AND THERE WAS LOTS OF OSTEOLYSIS, SO HE REVISED TO COMPETITOR'S DEVICES. THERE WAS NO REPORTED BREAKAGE OF A DEVICE OR SURGICAL DELAY/PROLONGATION. THE PATIENT WAS LAST KNOWN TO BE IN STABLE CONDITION FOLLOWING THE EVENT.

    Patient problems: Osteolysis

    MAUDE report 21465422 ↗
  • InjuryDec 11, 2024Loosening of Implant Not Related to Bone-Ingrowth; Loosening of Implant Not Related to Bone-Ingrowth

    IT WAS REPORTED THAT APPROXIMATELY 148 MONTHS AFTER A LEFT TOTAL KNEE REPLACEMENT PROCEDURE, THE PATIENT UNDERWENT A REVISION PROCEDURE TO ADDRESS PROSTHESIS WEAR, PROGRESSIVE AND DEBILITATING KNEE PAIN SECONDARY TO ASEPTIC LOOSENING, POLYETHYLENE WAR AND OSTEOLYSIS. REVISION OPERATIVE REPORTS WERE PROVIDED. INTRAOPERATIVELY THE SURGEON OBSERVED ASEPTIC LOOSENING OF THE FEMUR AND TIBIAL TRAY, POLYETHYLENE WEAR OF THE INSERT, SIGNIFICANT SURFACE DAMAGE, DELAMINATION AND PITTING ON THE PATELLA, WHICH WAS FRACTURED AND LOOSE. IT WAS NOTED THE SURGICAL PROCEDURE WAS SIGNIFICANTLY DIFFICULT DUE TO PATIENT'S HEIGHT AND WEIGHT WHICH REQUIRED ADDITIONAL SURGICAL DISSECTION. NO MEDICAL OR SURGICAL INTERVENTION WAS REPORTED. NO ADDITIONAL INFORMATION IS AVAILABLE. IMPACTOR AND THE TIBIAL COMPONENT CAREFULLY REMOVED, WHICH WAS ALSO 02-012-35-3511 - LOGIC TIBIA PS MOD INSRT SZ 3.5 11MM. SERIAL: (B)(6). 510K: K093360 UDI: (B)(4). PRODUCT CODE: JWH. X-RAY: NO. OPERATIVE NOTES: YES.

    Patient problems: Implant Pain; Osteolysis

    MAUDE report 20902659 ↗

Other Prosthesis, Knee, Patellofemorotibial, Semi-Constrained, Cemented, Polymer/Metal/Polymer devices

All Prosthesis, Knee, Patellofemorotibial, Semi-Constrained, Cemented, Polymer/Metal/Polymer devices →

Sources and updates

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