ENDOSKELETON® TCS 5210-1021Recalls & reported problems
Medtronic Sofamor Danek, Inc. · INSERTER · Class 1
All models of ENDOSKELETON TCS (12)
Data updated Oct 18, 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 00191375011873), received between Feb 21, 2018 and May 18, 2026 — classified as 2 malfunctions.
The most frequently reported specific device problem is “Mechanical Problem” (2 reports).
2 other recalls cover devices cleared under the same FDA submission (K142940); they may or may not involve this specific model.
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
Most reported problems
Device problems
- Mechanical Problem2
Patient problems
- No Clinical Signs, Symptoms or Conditions1
- No Known Impact Or Consequence To Patient1
Recent adverse event reports
The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.
MalfunctionMay 18, 2026Mechanical Problem
INFORMATION WAS RECEIVED FROM MULTIPLE SOURCES (MANUFACTURER REPRESENTATIVE, USER FACILITY) REGARDING A DEVICE USED FOR ANTERIOR CER VICAL DISCECTOMY AND FUSION (ACDF). IT WAS REPORTED THAT THE TIP OF THE INSERTER WAS NO LONGER HOLDING THE IMPLANT SECURELY. THERE WAS NO PATIENT INVOLVED.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 25199542 ↗MalfunctionFeb 21, 2018Mechanical Problem; Mechanical Problem
IT WAS REPORTED THAT, DURING AN ACF C5-C6 LEVEL SURGERY, THE SURGEON HAD SOME TROUBLE DISENGAGING AN IMPLANT. THE SURGEON EXPERIENCED CROSS THREADING BETWEEN THE THREADED INSERTER AND THE IMPLANT, MAKING THE DISENGAGEMENT BETWEEN THE TWO DIFFICULT. ONCE THE SURGEON DISENGAGED THE IMPLANT, HE DID NOT LIKE THE FIT OF THE IMPLANT INSIDE THE PATIENT'S DISC SPACE. THE SURGEON REMOVED THAT IMPLANT AND USED ANOTHER IMPLANT INSTEAD WHICH WAS SATISFACTORY. THE SURGERY WAS COMPLETED SUCCESSFULLY. THERE WAS NO REPORTED ADVERSE EFFECT TO THE PATIENT.
Patient problems: No Known Impact Or Consequence To Patient
MAUDE report 7287683 ↗
Recalls under the same FDA submission
These recalls involve devices cleared under K142940. One submission often covers many models, so check the product and lot details in each record.
- Z-2327-2015 · Jul 20, 2015 · TerminatedTitan Spine Endoskeleton Locking Bone Screw Assembly, which is part of the Endoskeleton TCS Interbody Fusion Device, spinal implant. Part Numbers / Product Description: 5302-3514
- Z-1324-2015 · Feb 20, 2015 · TerminatedEndo TCS Driver Straight Hexalobe #6 P/N 5210-1004, Non-Sterile, Manufactured by Titan Spine, LLC. Endo TCS driver is one of the instruments within the surgical tray for use with
Other DRIVER, PROSTHESIS devices
- ATTUNE 2544-01-005Depuy (Ireland) · DRIVER, PROSTHESIS1,383 reports
- EXPEDIUM VERSE 299704230Medos International Sàrl · DRIVER, PROSTHESIS875 reports
- NA 9200-10-029Depuy (Ireland) · DRIVER, PROSTHESIS745 reports
- MOSS 279712600Depuy Spine, LLC · DRIVER, PROSTHESIS706 reports
- NA 2598-07-440Depuy (Ireland) · DRIVER, PROSTHESIS665 reports
- NA 2598-07-570Depuy (Ireland) · DRIVER, PROSTHESIS505 reports
- VIPER 286745550Depuy Spine, LLC · DRIVER, PROSTHESIS263 reports
- SUMMIT 2570-05-100Depuy (Ireland) · DRIVER, PROSTHESIS225 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 18, 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