Skip to content

LEVEL ONE 25-457-05-91Recalls & reported problems

KLS-Martin L.P. · TWIST DRILL, J NOTCH, 5 MM STOP · Class 1

All models of LEVEL ONE (36)

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

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

Summary

The FDA's MAUDE database contains 3 adverse event reports that list this exact device (DI 00888118041104), received between Jul 1, 2019 and Oct 15, 2020 — classified as 3 injuries.

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

Most reported problems

Device problems

  • Break3

Patient problems

  • Device Embedded In Tissue or Plaque3

Recent adverse event reports

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

  • InjuryOct 15, 2020Break; Break

    IT WAS REPORTED A TWIST DRILL BROKE DURING USE AND A PORTION REMAINS IMPLANTED. THE REPORTED RPMS EXCEEDED THE MAXIMUM VALUE FOUND IN THE IFU. PER IFU 91-600-02-00 FOR THE TWIST DRILL "OPERATE THE TWIST DRILLS WITH NO MORE THAN THE MAXIMUM RECOMMENDED HANDPIECE SPEED SETTING OF 2,500 RPM."

    Patient problems: Device Embedded In Tissue or Plaque

    MAUDE report 10683432 ↗
  • InjuryJul 1, 2019Break; Break

    IT WAS REPORTED THE TWIST DRILL BROKE AND A PORTION REMAINS IMPLANTED.

    Patient problems: Device Embedded In Tissue or Plaque

    MAUDE report 8750345 ↗
  • InjuryJul 1, 2019Break; Break

    IT WAS REPORTED THE TWIST DRILL BROKE AND A PORTION REMAINS IMPLANTED.

    Patient problems: Device Embedded In Tissue or Plaque

    MAUDE report 8750294 ↗

Other BIT, DRILL devices

All BIT, DRILL devices →

Sources and updates

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