Skip to content

Tritanium PL 48956136Recalls & reported problems

Stryker Corporation · Posterior Lumbar Cage · Class 2 · Implant

All models of Tritanium PL (45)

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

Adverse event reports
1
Deaths reported
0
Injuries reported
0
Recalls naming it
0

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 07613327295207), received between Aug 4, 2020 and Aug 4, 2020 — classified as 1 malfunction.

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

Most reported problems

Device problems

  • Fracture1

Patient problems

  • No Clinical Signs, Symptoms or Conditions1
  • No Consequences Or Impact To Patient1

Recent adverse event reports

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

  • MalfunctionAug 4, 2020Fracture; Fracture

    IT WAS REPORTED THAT A TRITANIUM PL CAGE FRACTURED INTRA-OPERATIVELY WHERE THE CAGE ATTACHES TO THE INSERTER DURING PLACEMENT AT L5/S1. THIS OCCURRED AFTER THE PHYSICIAN ROTATED THE CAGE IN THE DISC SPACE- A CONTRAINDICATED MANEUVER THEY WERE ADVISED AGAINST. THE FRACTURED CAGE WAS LEFT IN PLACE AND ANOTHER CAGE WAS PLACED ON THE RIGHT SIDE OF THE DISC SPACE. THERE WERE NO ADVERSE CONSEQUENCES TO THE PATIENT. THE PROCEDURE WAS COMPLETED SUCCESSFULLY WITH A 5-7 MINUTE SURGICAL DELAY.

    Patient problems: No Clinical Signs, Symptoms or Conditions; No Consequences Or Impact To Patient

    MAUDE report 10364224 ↗

Other Intervertebral fusion device with bone graft, lumbar devices

All Intervertebral fusion device with bone graft, lumbar devices →

Sources and updates

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