N/A 01-3905Recalls & reported problems
Biomet Microfixation, Inc · Class 2
Data updated Oct 16, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 5
- Deaths reported
- 0
- Injuries reported
- 1
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 5 adverse event reports that list this exact device (DI 00841036011222), received between Jul 26, 2019 and Jan 5, 2021 — classified as 1 injury, 4 malfunctions.
The most frequently reported specific device problem is “Detachment of Device or Device Component” (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 16, 2026.
Most reported problems
Device problems
- Detachment of Device or Device Component2
- Fracture2
- Break1
Patient problems
- No Consequences Or Impact To Patient3
- No Information1
- No Known Impact Or Consequence To Patient1
Recent adverse event reports
The 5 most recent of 5 reports, in the reporter's own words as published by the FDA.
MalfunctionJan 5, 2021Fracture; Fracture
IT WAS REPORTED THE CLASP FRACTURED OFF THE PECTUS BAR BENDER DURING SURGERY. THE PROCEDURE WAS COMPLETED WITH ANOTHER PRODUCT. NO ADVERSE EVENTS HAVE BEEN REPORTED AS A RESULT OF THE MALFUNCTION.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 11121468 ↗MalfunctionAug 24, 2020Break; Break
IT WAS REPORTED THAT THE INSTRUMENT DISASSEMBLED DURING A PECTUS BAR REMOVAL PROCEDURE. THE SURGERY WAS COMPLETED SUCCESSFULLY WITHOUT THE USE OF THE INSTRUMENT. NO ADVERSE EVENTS HAVE BEEN REPORTED AS A RESULT OF THE MALFUNCTION.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 10442464 ↗MalfunctionJun 29, 2020Detachment of Device or Device Component; Detachment of Device or Device Component
THIS FOLLOW-UP REPORT IS BEING SUBMITTED TO RELAY ADDITIONAL INFORMATION.
Patient problems: No Known Impact Or Consequence To Patient
MAUDE report 10209004 ↗InjuryJan 16, 2020Detachment of Device or Device Component; Detachment of Device or Device Component
IT WAS REPORTED THAT A PECTUS BAR BENDER WAS UNABLE TO FUNCTION DURING SURGERY. THERE WAS A NINETY MINUTE DELAY WHILE A NEW INSTRUMENT WAS PROCURED. NO ADDITIONAL PATIENT CONSEQUENCES WERE REPORTED.
Patient problems: No Information
MAUDE report 9596226 ↗MalfunctionJul 26, 2019Fracture; Fracture
THIS FOLLOW-UP REPORT IS BEING SUBMITTED TO RELAY ADDITIONAL INFORMATION.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 8832785 ↗
Other Plate, fixation, bone devices
- Lapiplasty System 2 SK14Treace Medical Concepts, Inc. · Plate, Fixation, Bone260 reports
- PRECICE® Plating System LP4.5-PRF4BNuvasive Specialized Orthopedics, Inc. · Plate, Fixation, Bone3 recalls6 reports
- PRECICE® Plating System LP4.5-MLT4BNuvasive Specialized Orthopedics, Inc. · Plate, Fixation, Bone3 recalls5 reports
- PRECICE® Plating System LP4.5-PLF4BNuvasive Specialized Orthopedics, Inc. · Plate, Fixation, Bone3 recalls3 reports
- PRECICE® Plating System LP4.5-MRT4BNuvasive Specialized Orthopedics, Inc. · Plate, Fixation, Bone3 recalls3 reports
- PRECICE® Plating System LP4.5-DRF4BNuvasive Specialized Orthopedics, Inc. · Plate, Fixation, Bone3 recalls1 report
- PRECICE® Plating System LP4.5-PLF40Nuvasive Specialized Orthopedics, Inc. · Plate, Fixation, Bone3 recalls0 reports
- PRECICE® Plating System LP4.5-PRT42Nuvasive Specialized Orthopedics, Inc. · Plate, Fixation, Bone3 recalls0 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