NA 1806-0084SRecalls & reported problems
Stryker GmbH · Guide Wire, Ball-Tipped · Class 1
Data updated Oct 16, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 3
- Deaths reported
- 0
- Injuries reported
- 1
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 3 adverse event reports that list this exact device (DI 07613154172573), received between Mar 26, 2019 and Mar 26, 2024 — classified as 1 injury, 2 malfunctions.
The most frequently reported specific device problem is “Break” (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.
Reports received per month
Most reported problems
Device problems
- Break1
- Fracture1
- Manufacturing, Packaging or Shipping Problem1
- Material Deformation1
- Material Twisted/Bent1
Patient problems
- Insufficient Information1
- No Known Impact Or Consequence To Patient1
- Perforation1
Recent adverse event reports
The 3 most recent of 3 reports, in the reporter's own words as published by the FDA.
MalfunctionMar 26, 2024Material Deformation; Material Twisted/Bent; Material Deformation; Material Twisted/Bent
AS REPORTED: "THE NAIL WAS NOT IMPLANTED, [WIRE] TWISTED IN THE ORIGINAL BOX.".
Patient problems: Insufficient Information
MAUDE report 18981712 ↗InjuryJan 17, 2023Break; Fracture; Break; Fracture
IT WAS REPORTED THAT THE STRYKER LONG BALL TIP GUIDEWIRE BROKE OFF ABOUT AN INCH ABOVE THE BALL TIP AND WAS LOOSE IN THE FEMORAL CANAL. IT WAS FURTHER REPORTED THAT "THIS WAS AFTER REAMING WAS DONE, AND THE LONG GAMMA NAIL WAS BEING INSERTED. ONCE THE TIP WAS DISCOVERED THE NAIL WAS REMOVED, AS IT WOULD NOT ADVANCE." APPROXIMATELY AN HOUR WAS SPENT RETRIEVING THIS TIP OF THE GUIDEWIRE. THE PATIENT WAS UNDER SPINAL ANESTHETIC AND NEEDED TO SWITCH TO A GENERAL ANESTHETIC GIVEN THE INCREASED SURGICAL TIME. A LARGER INCISION WAS REQUIRED, ALONG WITH A OSTEOTOMY FOR A "BONE WINDOW" TO LOWER FEMUR TO RETRIEVE THE BROKEN PIECE.
Patient problems: Perforation
MAUDE report 16183573 ↗MalfunctionMar 26, 2019Manufacturing, Packaging or Shipping Problem
THE HOSPITAL REPORTED THE FOLLOWING EVENT : "BEFORE THE USE OF THE TIBIA NAIL GUIDE THE PHARMACIST NOTICED THAT THE INNER PACKAGING WAS DAMAGE. DETERIORATED INNER PACKAGING, THEREFORE NON-STERILE IMPLANT. ACCORDING TO THE PHARMACIST AT THE RECEPTION THE BOX WAS NOT DAMAGE, IT WAS ONLY THE INNER PACKAGING. THE INCRIMINATED DEVICE WAS DISCARDED. THEY USE ANOTHER TIBIA NAIL GUIDE TO PERFORMED THE INTERVENTION. NO SURGICAL DELAY, NO ADVERSE CONSEQUENCES, NO MEDICAL INTERVENTION.
Patient problems: No Known Impact Or Consequence To Patient
MAUDE report 8453843 ↗
Other ORTHOPEDIC MANUAL SURGICAL INSTRUMENT devices
- AML EXCEL 2001-42-000Depuy (Ireland) · ORTHOPEDIC MANUAL SURGICAL INSTRUMENT2,009 reports
- NA 03.010.523Synthes GmbH · ORTHOPEDIC MANUAL SURGICAL INSTRUMENT1,208 reports
- EXPRESSEW 214141Medos International Sàrl · ORTHOPEDIC MANUAL SURGICAL INSTRUMENT1,166 reports
- N/A 9560524Medtronic Sofamor Danek, Inc. · ORTHOPEDIC MANUAL SURGICAL INSTRUMENT866 reports
- INHANCE 6500-11-104Depuy (Ireland) · Orthopedic manual surgical instrument831 reports
- INHANCE 6500-11-102Depuy (Ireland) · Orthopedic manual surgical instrument567 reports
- R3 71364450Smith & Nephew, Inc. · ORTHOPEDIC MANUAL SURGICAL INSTRUMENT520 reports
- N/A 9561524Medtronic Sofamor Danek, Inc. · ORTHOPEDIC MANUAL SURGICAL INSTRUMENT494 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