On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Leak test failures that prevent cycle start, typically caused by scope connection issues, leaks in the scope, or improper hookup.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Do not attempt to run or troubleshoot the AER with a scope intended for patient use.
- Remove the scope and ensure patient care is transitioned to another properly processed scope.
Expected: No risk of using a potentially contaminated or unverified scope
Verify the Reported Error and Behavior
- Attempt to start a cycle
- Observe when the failure occurs (immediately vs during leak test phase)
- Note any audible alarms or displayed messages
Expected: Leak test consistently fails before disinfection begins
Why it matters: Confirms this is not a one-time or user setup issue
Check Scope Connection Integrity (Most Common Cause)
- Disconnect and reconnect all scope channel connectors
- Ensure correct hookup per scope type
- Confirm all ports are securely seated and not cross-connected
Expected: All connections are tight and correctly matched
Why it matters: Air leaks at connection points will fail the pressure-based leak test
Inspect the Endoscope for External Damage or Known Leaks
- Check insertion tube and distal end for visible damage
- Look for cracks, kinks, or fluid intrusion
- Ask staff if the scope previously failed manual leak testing
Expected: No visible damage or known leak issues
Why it matters: A damaged scope will fail the AER leak test regardless of setup
Verify Correct Leak Test Adapter Use (If Applicable)
- Confirm the correct adapter is being used for the specific scope model
- Inspect adapter O-rings and seals for wear or damage
- Swap with a known-good adapter if available
Expected: Adapter is correct, intact, and properly seated
Why it matters: Faulty adapters commonly introduce leaks into the system
Check for Kinked or Blocked Tubing
- Inspect all AER tubing connected to the scope
- Ensure no kinks, pinches, or disconnections
- Straighten tubing and reattempt cycle
Expected: Tubing is unobstructed and properly routed
Why it matters: Pressure inconsistencies can trigger leak test failure
Perform a Manual Leak Test (If Available Per Facility Practice)
- Use a manual leak tester on the scope
- Observe for bubbles or pressure drop
Expected: Scope holds pressure with no visible leaks
Why it matters: Confirms whether the issue is the scope vs the AER
Retry Cycle with a Different Scope (Isolation Step)
- Connect a known-good scope
- Attempt to start the cycle
Expected: Cycle proceeds normally with alternate scope
Why it matters: Helps isolate whether failure is scope-related or AER-related
If the Problem Persists
If all external causes (connections, adapters, tubing, and scope condition) have been ruled out, the issue is likely internal to the AER (pressure sensing, valves, or leak test system).
Remove the unit from service, label it Out of Service, and send for repair or bench evaluation.
Clinical Use Tip
Never rely on a scope that fails a leak test. Always remove it from service immediately and use a verified, properly functioning scope for patient care.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"AER fails leak test and will not start disinfection cycle."
Cause
What was observed during troubleshooting.
Example:
"Loose scope channel connection causing air leak during pressure test."
Resolution
What action was taken.
Example:
"Reconnected scope properly and verified successful cycle initiation."
Helpful Details to Include (If Known)
- Leak test failure message timing
- Scope type and model used
- Whether alternate scope passed
- Adapter condition and swap results
- Tubing condition (kinks, loose connections)
- Any visible scope damage
- Final device status
Final Thought
Leak test failures are most often caused by setup or scope-related issues, not the AER itself. A structured, external-first approach ensures patient safety, protects equipment, and avoids unnecessary service calls. Proper documentation supports traceability and quality assurance.
That is successful troubleshooting.