Skip to content

YUKON OCT Spinal System 7601-05032Recalls & reported problems

VB Spine LLC · Polyaxial Screw Ø5.0x32 mm · Class 2 · Implant

All models of YUKON OCT Spinal System (54)

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

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

Summary

The FDA's MAUDE database contains 5 adverse event reports that list this exact device (DI 10888857350038), received between Oct 29, 2021 and Feb 19, 2025 — classified as 2 injuries, 3 malfunctions.

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

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 2 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 0 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 2 reportsMar 2025: 0 reportsApr 2025: 0 reportsMay 2025: 0 reportsJun 2025: 0 reportsJul 2025: 0 reportsAug 2025: 0 reportsSep 2025: 0 reportsOct 2025: 0 reportsNov 2025: 0 reportsDec 2025: 0 reportsJan 2026: 0 reportsFeb 2026: 0 reportsMar 2026: 0 reportsApr 2026: 0 reportsMay 2026: 0 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports2024202520262
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Fracture4
  • Device Dislodged or Dislocated1
  • Migration1

Patient problems

  • No Clinical Signs, Symptoms or Conditions3
  • Neck Pain2

Recent adverse event reports

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

  • MalfunctionFeb 19, 2025Fracture; Fracture

    NO NEW INFORMATION.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 21414366 ↗
  • MalfunctionFeb 19, 2025Fracture; Fracture

    A COMPANY REPRESENTATIVE REPORTED THAT TWO YUKON POLYAXIAL SCREWS FRACTURED POST-OPERATIVELY. THIS WAS IDENTIFIED IN POST-OPERATIVE IMAGING TAKEN APPROXIMATELY 15 MONTHS AFTER IMPLANTATION. THE SCREWS REMAIN IMPLANTED. THIS CAPTURES THE FIRST OF TWO SCREWS.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 21414266 ↗
  • InjuryApr 19, 2024Device Dislodged or Dislocated; Migration; Device Dislodged or Dislocated; Migration

    A COMPANY REPRESENTATIVE REPORTED THAT A PATIENT WAS EXPERIENCING PAIN APPROXIMATELY FOUR MONTHS AFTER IMPLANTATION AND UNDERWENT REVISION SURGERY TO ADDRESS MIGRATION OF A YUKON POLYAXIAL SCREW AT C2 AND DISCOVERED ANOTHER YUKON POLYAXIAL SCREW FRACTURE AT T2 INTRA-OPERATIVELY. THIS REPORT CAPTURES THE FIRST OF TWO YUKON POLYAXIAL SCREWS.

    Patient problems: Neck Pain

    MAUDE report 19143123 ↗
  • InjuryApr 19, 2024Fracture; Fracture

    A COMPANY REPRESENTATIVE REPORTED THAT A PATIENT WAS EXPERIENCING PAIN APPROXIMATELY FOUR MONTHS AFTER IMPLANTATION AND UNDERWENT REVISION SURGERY TO ADDRESS MIGRATION OF A YUKON POLYAXIAL SCREW AT C2 AND DISCOVERED ANOTHER YUKON POLYAXIAL SCREW FRACTURE AT T2 INTRA-OPERATIVELY. THIS REPORT CAPTURES THE SECOND OF TWO YUKON POLYAXIAL SCREWS.

    Patient problems: Neck Pain

    MAUDE report 19143120 ↗
  • MalfunctionOct 29, 2021Fracture; Fracture

    THIS REPORT SUMMARIZES ONE MALFUNCTION EVENT WHERE A YUKON OCT POLYAXIAL SCREW BROKE INTRA-OPERATIVELY. SURGERY WAS SUCCESSFULLY COMPLETED WITH NO DELAY. NO ADVERSE CONSEQUENCES OR MEDICAL INTERVENTION WERE REPORTED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 12721727 ↗

Other APPLIANCE, FIXATION, SPINAL INTERLAMINAL devices

All APPLIANCE, FIXATION, SPINAL INTERLAMINAL devices →

Sources and updates

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