Skip to content

aScope™ Gastro 483001000USRecalls & reported problems

Ambu A/S · aScope Gastro (US version) · Class 2

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

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

Summary

The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 05707480148172), received between May 27, 2026 and May 27, 2026 — classified as 2 injuries.

The most frequently reported specific device problem is “Leak/Splash” (2 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: 0 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: 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: 2 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

  • Leak/Splash2

Patient problems

  • No Clinical Signs, Symptoms or Conditions2

Recent adverse event reports

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

  • InjuryMay 27, 2026Leak/Splash

    THE AMBU SYSTEM HAS BEEN LEAKING. THE PATIENT ASPIRATED AND THE PHYSICIAN DOESN'T WANT TO USE IT ANYMORE. PATIENT CONDITION WAS NOT AFFECTED, AND IS FINE NO PATIENT HARM AT TIME OF INCIDENT OR RESIDUALLY AFTERWARDS. FOLLOWING ADDITIONAL INFORMATION RECEIVED: WAS THE ENDOSCOPE INSPECTED FOR LEAKS OR WATER DRIPPING PRIOR TO INSERTION? IF SO, WHAT WAS OBSERVED? THERE WAS NOT ANY PREINSPECTION OF LEAKS OR DRIPPING PRIOR TO INSERTION. IT WAS DESCRIBED THAT WATER WAS FLOWING OUT LIKE A POWERFUL STREAM DURING PROCEDURE AND CONTINUED UPON EXTUBATION. AFTER PROCEDURE, NO APPARENT LEAKS WERE OBSERVED. FLUID WAS EXITING THROUGH THE FORWARD WATER JET CHANNEL. WAS ANY INTERVENTION REQUIRED BECAUSE OF THE LEAK (E.G. SUCTION), OR DID THE PATIENT CLEAR THE AIRWAY SPONTANEOUSLY BY COUGHING? NO SERIOUS INTERVENTION REQUIRED. JUST SUCTIONING THE AIRWAY FROM ANESTHESIA. AIRWAY WAS CLEARED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 25303353 ↗
  • InjuryMay 27, 2026Leak/Splash

    THE AMBU SYSTEM HAS BEEN LEAKING. THE PATIENT ASPIRATED AND THE PHYSICIAN DOESN'T WANT TO USE IT ANYMORE. PATIENT CONDITION WAS NOT AFFECTED, AND IS FINE NO PATIENT HARM AT TIME OF INCIDENT OR RESIDUALLY AFTERWARDS. FOLLOWING ADDITIONAL INFORMATION RECEIVED: WAS THE ENDOSCOPE INSPECTED FOR LEAKS OR WATER DRIPPING PRIOR TO INSERTION? IF SO, WHAT WAS OBSERVED? THERE WAS NOT ANY PRE-INSPECTION OF LEAKS OR DRIPPING PRIOR TO INSERTION. IT WAS DESCRIBED THAT WATER WAS FLOWING OUT LIKE A POWERFUL STREAM DURING PROCEDURE AND CONTINUED UPON EXTUBATION. AFTER PROCEDURE, NOT APPARENT LEAKS WERE OBSERVED. FLUID WAS EXITING THROUGH THE FORWARD WATER JET CHANNEL. WAS ANY INTERVENTION REQUIRED BECAUSE OF THE LEAK (E.G. SUCTION), OR DID THE PATIENT CLEAR THE AIRWAY SPONTANEOUSLY BY COUGHING? NO SERIOUS INTERVENTION REQUIRED. JUST SUCTIONING THE AIRWAY FROM ANESTHESIA. AIRWAY WAS CLEARED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 25296331 ↗

Other Gastroscope and accessories, flexible/rigid devices

All Gastroscope and accessories, flexible/rigid devices →

Sources and updates

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