Skip to content

Stryker Performance Series 6125119090Recalls & reported problems

Stryker Corporation · Stryker Performance Series Sagittal Blade · Class 1

All models of Stryker Performance Series (26)

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

Adverse event reports
16
Deaths reported
0
Injuries reported
2
Recalls naming it
0

Summary

The FDA's MAUDE database contains 16 adverse event reports that list this exact device (DI 04546540501509), received between Jul 20, 2018 and Jan 23, 2026 — classified as 2 injuries, 14 malfunctions.

The most frequently reported specific device problem is “Fracture” (12 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: 1 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 1 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 1 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 1 reportsFeb 2025: 0 reportsMar 2025: 0 reportsApr 2025: 1 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: 1 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

  • Fracture12
  • Break3
  • Delivered as Unsterile Product1
  • Ejection Problem1

Patient problems

  • No Clinical Signs, Symptoms or Conditions11
  • No Consequences Or Impact To Patient4
  • Device Embedded In Tissue or Plaque2

Recent adverse event reports

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

  • MalfunctionJan 23, 2026Fracture

    NO CHANGE.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24163984 ↗
  • MalfunctionApr 21, 2025Fracture; Ejection Problem; Fracture; Ejection Problem

    THIS REPORT SUMMARIZES 1 MALFUNCTION EVENT IN WHICH THE DEVICE REPORTEDLY FRACTURED AND UNINTENTIONALLY EJECTED. - 1 EVENT HAD PATIENT INVOLVEMENT, NO PATIENT IMPACT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 21876263 ↗
  • InjuryJan 24, 2025Fracture; Fracture

    IT WAS REPORTED THAT POST-OPERATIVELY, IT WAS NOTED THAT THE BLADE BROKE WHERE IT FITS INTO THE HANDPIECE. IT WAS ALSO REPORTED THAT THE EVENT REQUIRED MEDICAL INTERVENTION BY WAY OF A REVISION SURGERY TO SUCCESSFULLY REMOVE THE BLADE FRAGMENT FROM THE PATIENT. IT WAS FURTHER REPORTED THAT THE PROCEDURE WAS COMPLETED SUCCESSFULLY.

    Patient problems: Device Embedded In Tissue or Plaque

    MAUDE report 21232895 ↗
  • MalfunctionOct 22, 2024Delivered as Unsterile Product; Delivered as Unsterile Product

    THIS REPORT SUMMARIZES 2 MALFUNCTION EVENTS IN WHICH THE DEVICE WAS REPORTEDLY RECEIVED IN SUCH A MANNER TO INDICATE THAT ITS STERILITY HAD BEEN COMPROMISED. - 2 EVENTS HAD THE PROBLEM IDENTIFIED BEFORE CLINICAL USE/EXPOSURE; THERE WAS NO PATIENT INVOLVEMENT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 20504588 ↗
  • MalfunctionJul 24, 2024Fracture; Fracture

    THIS REPORT SUMMARIZES 2 MALFUNCTION EVENTS IN WHICH THE DEVICE OR CUTTING ACCESSORY FRACTURED. - 2 EVENTS HAD PATIENT INVOLVEMENT; NO PATIENT IMPACT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 19822900 ↗
  • MalfunctionApr 16, 2024Fracture; Fracture

    THIS REPORT SUMMARIZES 1 MALFUNCTION EVENT IN WHICH THE DEVICE OR CUTTING ACCESSORY FRACTURED. 1 EVENT HAD PATIENT INVOLVEMENT; NO PATIENT IMPACT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 19115903 ↗
  • MalfunctionJul 26, 2023Fracture; Fracture

    THIS REPORT SUMMARIZES 5 MALFUNCTION EVENTS IN WHICH THE DEVICE OR CUTTING ACCESSORY FRACTURED. 5 EVENTS HAD PATIENT INVOLVEMENT; NO PATIENT IMPACT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 17398736 ↗
  • InjuryMay 30, 2023Fracture; Fracture

    IT WAS REPORTED THAT DURING A TOTAL KNEE REPLACEMENT PROCEDURE, THE BLADE BROKE AT THE SHAFT. IT WAS ALSO REPORTED THAT A METAL PIECE OF THE BLADE REMAINED IN THE PATIENT, WHICH WAS DISCOVERED DURING A POST-OPERATIVE SCAN. AS A RESULT, A SECOND SURGERY NEEDED TO BE PERFORMED TO REMOVE THE PIECE OF BLADE. IT WAS FURTHER REPORTED THAT THE REVISION PROCEDURE WAS COMPLETED SUCCESSFULLY.

    Patient problems: Device Embedded In Tissue or Plaque

    MAUDE report 17018553 ↗
  • MalfunctionMay 19, 2023Fracture; Fracture

    IT WAS REPORTED THAT DURING A TKA PROCEDURE, THE BLADE BROKE. IT WAS ALSO REPORTED THAT THERE WERE NO ADVERSE CONSEQUENCES, NO MEDICAL INTERVENTION AND NO DELAYS AS A RESULT OF THIS EVENT. IT WAS FURTHER REPORTED THAT THE PROCEDURE WAS COMPLETED SUCCESSFULLY.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 16962728 ↗
  • MalfunctionApr 24, 2023Fracture; Fracture

    THIS REPORT SUMMARIZES 1 MALFUNCTION EVENT IN WHICH THE DEVICE OR CUTTING ACCESSORY FRACTURED. - 1 EVENT HAD PATIENT INVOLVEMENT; NO PATIENT IMPACT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 16801377 ↗
  • MalfunctionApr 18, 2023Fracture; Fracture

    IT WAS REPORTED THAT DURING A SURGICAL PROCEDURE, THE BLADE BROKE AT THE MOUNT. THE PROCEDURE WAS COMPLETED SUCCESSFULLY WITHOUT A CLINICALLY SIGNIFICANT DELAY; NO ADVERSE CONSEQUENCES OR MEDICAL INTERVENTION WERE REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 16763806 ↗
  • MalfunctionAug 4, 2022Fracture; Fracture

    IT WAS REPORTED THAT DURING A TOTAL KNEE ARTHROPLASTY PROCEDURE, THE BLADE BROKE AT THE BASE. IT WAS ALSO REPORTED THAT THERE WERE NO ADVERSE CONSEQUENCES AND NO DELAYS AS A RESULT OF THIS EVENT. IT WAS FURTHER REPORTED THAT THE PROCEDURE WAS COMPLETED SUCCESSFULLY.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 15162814 ↗
  • MalfunctionJul 28, 2020Fracture; Fracture

    IT WAS REPORTED THAT DURING A SURGICAL PROCEDURE, IT WAS NOTED THAT THE BLADE SOUNDED UNUSUALLY LOUD AND ON INSPECTION, THE SAW BLADE WHERE IT ATTACHES TO THE HANDPIECE WAS BROKEN. IT WAS ALSO REPORTED THERE WERE NO DELAYS AND NO ADVERSE CONSEQUENCES AS A RESULT OF THIS EVENT. IT WAS FURTHER REPORTED THAT THE PROCEDURE WAS COMPLETED SUCCESSFULLY.

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

    MAUDE report 10332416 ↗
  • MalfunctionMar 4, 2019Break; Break

    IT WAS REPORTED THAT DURING A TOTAL KNEE ARTHROPLASTY PROCEDURE THE BLADE BROKE AT THE MOUNT. IT WAS ALSO REPORTED THERE WERE NO DELAYS AND NO ADVERSE CONSEQUENCES AS A RESULT OF THIS EVENT. IT WAS FURTHER REPORTED THAT THE PROCEDURE WAS COMPLETED SUCCESSFULLY.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 8387339 ↗
  • MalfunctionDec 19, 2018Break; Break

    IT WAS REPORTED THAT DURING A TKA (TOTAL KNEE ARTHROPLASTY) PROCEDURE, THE BLADE BROKE AT THE MOUNT. IT WAS ALSO REPORTED THAT THERE WERE NO ADVERSE CONSEQUENCES AND NO DELAYS AS A RESULT OF THIS EVENT. IT WAS FURTHER REPORTED THAT THE PROCEDURE WAS COMPLETED SUCCESSFULLY.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 8181625 ↗
  • MalfunctionJul 20, 2018Break; Break

    IT WAS REPORTED THAT DURING A SURGICAL PROCEDURE, THE BLADE BROKE AT THE MOUNT. NO FURTHER INFORMATION WAS PROVIDED.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 7707112 ↗

Other BLADE, SAW, GENERAL & PLASTIC SURGERY, SURGICAL devices

All BLADE, SAW, GENERAL & PLASTIC SURGERY, SURGICAL devices →

Sources and updates

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