Skip to content

VivaSight™ 2 DLT Kit 35 Fr - LEFT 412351000Recalls & reported problems

Ambu A/S · VivaSight 2 DLT Kit 35 Fr - LEFT · Class 2

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

1 open recall names this device. See the recall details and contact the manufacturer or your healthcare provider.

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

Summary

The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 05707480145706), received between Aug 28, 2024 and Aug 28, 2024 — classified as 2 malfunctions.

The most frequently reported specific device problem is “Difficult to Insert” (2 reports).

1 FDA recall record name this device's identifier, 1 still open.

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: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 2 reportsSep 2024: 0 reportsOct 2024: 0 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 0 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.

Recalls naming this device

  1. Jun 3, 2022Class IIOpen, Classified

    Firm has received complaints on the device concerning leak/rupture of either the bronchial or tracheal cuff. Leakage during procedure could lead to loss of secure airway and will require re-intubation of patient.

    Z-1420-2022 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

Most reported problems

Device problems

  • Difficult to Insert2
  • Structural Problem2

Patient problems

  • Hemorrhage/Blood Loss/Bleeding2

Recent adverse event reports

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

  • MalfunctionAug 28, 2024Difficult to Insert; Structural Problem; Difficult to Insert; Structural Problem

    ACCORDING TO INFORMATION FROM THE CUSTOMER. IN CONNECTION WITH INTUBATING WITH AMBU VIVASIGHT DOUBLE-LUMEN TUBE WITH CAMERA, DIFFICULT INTUBATION OCCURED. THE TUBE WAS HYPERANGULATED, WHICH MADE IT DIFFICULT TO PASS THE EPIGLOTTIS AND TRACHEA. THERE WAS BLEEDING AROUND THE EPIGLOTTIS, AND UPON EXTUBATION, BLOOD WAS SEEN ON THE CUFF AND THE TIP OF THE TUBE. ACCORDING TO FOLLOW-UP INFORMATION FROM THE CUSTOMER, THE PATIENT WAS FINE THE NEXT DAY AND DID NOT COMPLAIN ABOUT SORE THROAT.

    Patient problems: Hemorrhage/Blood Loss/Bleeding

    MAUDE report 20088095 ↗
  • MalfunctionAug 28, 2024Difficult to Insert; Structural Problem; Difficult to Insert; Structural Problem

    ACCORDING TO INFORMATION FROM THE CUSTOMER. IN CONNECTION WITH INTUBATING WITH AMBU VIVASIGHT DOUBLE-LUMEN TUBE WITH CAMERA, DIFFICULT INTUBATION OCCURED. THE TUBE WAS HYPERANGULATED, WHICH MADE IT DIFFICULT TO PASS THE EPIGLOTTIS AND TRACHEA. THERE WAS BLEEDING AROUND THE EPIGLOTTIS, AND UPON EXTUBATION, BLOOD WAS SEEN ON THE CUFF AND THE TIP OF THE TUBE. ACCORDING TO FOLLOW-UP INFORMATION FROM THE CUSTOMER, THE PATIENT WAS FINE THE NEXT DAY AND DID NOT COMPLAINT ABOUT SORE THROAT.

    Patient problems: Hemorrhage/Blood Loss/Bleeding

    MAUDE report 20085639 ↗

Other TUBE, TRACHEAL/BRONCHIAL, DIFFERENTIAL VENTILATION (W/WO CONNECTOR) devices

All TUBE, TRACHEAL/BRONCHIAL, DIFFERENTIAL VENTILATION (W/WO CONNECTOR) devices →

Sources and updates

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