Trident X3 Insert 723-00-32BRecalls & reported problems
Howmedica Osteonics Corp. · Trident X3 0 Degree Polyethylene Insert · Class 2 · Implant
All models of Trident X3 Insert (22)
Data updated Oct 16, 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 07613327297058), received between Aug 10, 2021 and Nov 11, 2025 — 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 16, 2026.
Reports received per month
Most reported problems
Device problems
- Adverse Event Without Identified Device or Use Problem1
- Device Dislodged or Dislocated1
- Unstable1
Patient problems
- Joint Dislocation1
- Joint Laxity1
- Wound Dehiscence1
Recent adverse event reports
The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.
InjuryNov 11, 2025Unstable; Device Dislodged or Dislocated; Unstable; Device Dislodged or Dislocated
THE FOLLOWING INFORMATION WAS PROVIDED: THIS PI IS FOR THE REVISION OF A STRYKER CONSTRUCT DUE TO DISLOCATION AND HIP INSTABILITY. AS PER PSS IMPLANT REQUEST CASE (B)(4): COMPLEX ORTHOPAEDIC HISTORY, INCLUDING PERIPROSTHETIC FRACTURE OF DISTAL FEMUR, REQUIRING NAIL-PLATE FIXATION, THEN AN INTERTROCHANTERIC FEMUR FRACTURE, TREATED WITH SLIDING HIP SCREW AND THAT WENT ON TO NONUNION. NOW SHE IS S/P CONVERSION THA WITH A GT NONUNION, AND A 44 TRIDENT CUP, AND A RESTORATION MODULAR STEM. SHE HAS DISLOCATED IN HER FIRST WEEK POSTOPERATIVELY. REVISION SURGERY IS SCHEDULED FOR (B)(6) 2025.
Patient problems: Joint Dislocation; Joint Laxity
MAUDE report 23529225 ↗InjuryAug 10, 2021Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
IT WAS REPORTED THAT THE PATIENT'S RIGHT HIP WAS REVISED DUE TO WOUND DRAINAGE. INITIALLY, THE SURGEON SUSPECTED THERE WAS A SUPERFICIAL ABSCESS. INTRA-OPERATIVELY, IT WAS DISCOVERED THAT THE WOUND WAS NOT FULLY CLOSED DOWN TO THE JOINT. A STRYKER LINER AND COMPETITOR HEAD WERE REVISED. REP CONFIRMED THAT NO FURTHER INFORMATION WILL BE RELEASED BY THE HOSPITAL OR SURGEON.
Patient problems: Wound Dehiscence
MAUDE report 12299336 ↗
Other Prosthesis, hip, semi-constrained, metal/polymer, cemented devices
- NA 1365-51-000Depuy (Ireland) · Prosthesis, hip, semi-constrained, metal/polymer, cemented753 reports
- NA 1365-50-000Depuy (Ireland) · Prosthesis, hip, semi-constrained, metal/polymer, cemented412 reports
- ARTICUL/EZE 1365-21-000Depuy (Ireland) · Prosthesis, hip, semi-constrained, metal/polymer, cemented1 recall280 reports
- ARTICUL/EZE 1365-11-000Depuy (Ireland) · Prosthesis, hip, semi-constrained, metal/polymer, cemented1 death262 reports
- LFIT 6260-9-236Howmedica Osteonics Corp. · Prosthesis, hip, semi-constrained, metal/polymer, cemented256 reports
- PINNACLE GRIPTION 1217-32-052Depuy Orthopaedics, Inc. · Prosthesis, hip, semi-constrained, metal/polymer, cemented2 deaths239 reports
- ELEOS™ 25002111EOnkos Surgical, Inc. · Prosthesis, hip, semi-constrained, metal/polymer, cemented3 deaths230 reports
- Novation 130-36-52Exactech, Inc. · Prosthesis, Hip, Semi-Constrained, Metal/Polymer, Cemented2 recalls124 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