Skip to content

NA 312.74Recalls & reported problems

Synthes GmbH · 1.6MM TROCAR · Class 1

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

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

Summary

The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 10886982187918), received between Jan 21, 2019 and Nov 22, 2019 — classified as 2 malfunctions.

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

  • Material Deformation2

Patient problems

  • No Patient Involvement2

Recent adverse event reports

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

  • MalfunctionNov 22, 2019Material Deformation; Material Deformation

    IT WAS REPORTED THAT ON (B)(6) 2019, THE ONE (1) TROCAR RECEIVED WAS FOUND BENT. THERE WAS NO PATIENT INVOLVEMENT. THIS COMPLAINT INVOLVES ONE (1) DEVICE. THIS REPORT IS FOR ONE (1) 1.6MM TROCAR. THIS IS REPORT 1 OF 1 FOR (B)(4).

    Patient problems: No Patient Involvement

    MAUDE report 9360442 ↗
  • MalfunctionJan 21, 2019Material Deformation; Material Deformation

    IT WAS REPORTED THAT ON (B)(6) 2018 DURING ROUTINE INCOMING INSPECTION OF LOANER SET AT THE (B)(4) FIELD STOCK LOCATION, IT WAS NOTICED THAT THE 1.6MM TROCAR WAS BENT. THERE WAS NO KNOWN PATIENT OR HOSPITAL INVOLVEMENT. THIS REPORT IS FOR ONE (1) 1.6MM TROCAR. THIS IS REPORT 1 OF 1 FOR (B)(4).

    Patient problems: No Patient Involvement

    MAUDE report 8264692 ↗

Other Guide, surgical, instrument devices

All Guide, surgical, instrument devices →

Sources and updates

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