Before anything else here’s one simple question. If someone on your team reached for an EEBD right now, in the location where it is mounted, under the conditions that exist at your site, would it work?
Not ‘has it been signed off?’. Would it work?
Emergency escape breathing apparatus inspection programmes exist in most regulated environments. The paperwork usually looks fine. What happens between the paperwork and the device is where things get interesting — and where the gaps that appear in incident reports tend to live.
What an EEBD Is, and Why ‘Inspection’ Isn’t Quite the Right Word
An Emergency Escape Breathing Device or EEBD provides the wearer with breathable air during evacuation from a hazardous atmosphere. That’s it. Not for rescue. Not for extended exposure. Just enough to get out, typically somewhere between ten and twenty minutes, depending on the device and how hard the wearer is breathing at the time.
In maritime environments, SOLAS EEBD requirements on ships define where devices must be located, how long they must last, and how often they must be checked. In fixed industrial facilities, HSE guidance and DSEAR (Dangerous Substances and Explosive Atmospheres Regulations 2002) create equivalent obligations. The requirement to inspect is clear enough. What tends to be far less clear, and far less enforced, is the difference between a genuine inspection and a completed form.
‘Inspection’ implies technical assessment. What some organisations actually run is a documentation cycle. Someone checks a box. The two things are not the same, and in an emergency, that distinction matters enormously.
The Real Problem Is Almost Never the Equipment
Here is something that most maintenance guidance glosses over: EEBD failures are overwhelmingly procedural, not mechanical. Devices degrade because no one noticed the conditions in which they were stored. Hoods crack because they were moved somewhere inappropriate, and nobody followed up. Devices disappear from their recorded positions, get replaced without being logged, or sit in lockers that haven’t been physically opened since the last audit.
The equipment works. The system around it doesn’t.
Inspection intervals get missed when personnel change roles and nobody properly hands over. The person responsible for three locations is also responsible for twelve other things. The annual sign-off happens because the deadline arrived, not because everything was rigorously verified. None of this is obvious negligence. It’s what happens when safety-critical tasks get managed like administrative ones.
The consequence is a device that looks compliant on paper and may or may not function when someone needs it. That’s not a theoretical concern. It’s the finding of incident investigations across every sector that uses EEBDs.
Start With the Register, Not the Device
Every physical inspection should begin with a documentation review and that review should be treated as part of the inspection itself, not a warm-up.
Pull the register. Confirm every device listed is physically present and in its recorded location. Check the service history for gaps, missed dates, or unsigned entries. Look for any reported problems since the last check. If the register is a spreadsheet that hasn’t been updated in months, that tells you something worth knowing before you’ve touched a single device.
In larger sites, a water treatment works with EEBDs spread across multiple access points or an offshore platform with devices across several decks, this documentation pass frequently reveals the first failure. An empty locker nobody flagged. A device last checked by someone who left six months ago with no handover note. An inspection window that passed while two teams each assumed the other was covering it.
These are not paperwork issues. They’re system failures. Finding them before the physical check is the point.
The Physical Check: What to Look For
Device Serviceability Status
Confirm the device is within its stated service life, hasn’t been previously activated, and shows no sign of tampering (the tamper-evident seal and activation mechanism should both be intact). Test the activation components in line with the manufacturer’s service specification. Don’t assume the unit is functional from visual inspection alone. In high-UV or high-humidity environments, components can degrade in ways that give no external indication whatsoever.
It’s worth noting that some manufacturers’ products assist inspection by augmenting the visual check with their own visual indicator. For example, the Semmco LPS units have an indicator that, if blue, indicates the units are operational but, if pink, they should not pass inspection
Hood and Visor
Check the hood for brittleness, cracking, or discolouration. In environments with chemical vapour, (chlorine handling areas, labs with solvent use, offshore decks) hood material degrades faster than standard service intervals assume. The visor matters too. Cloudiness, scratching, or delamination might seem cosmetic until you remember that the person wearing it is navigating somewhere they can’t safely breathe, under time pressure, probably in reduced visibility. Clarity is not a cosmetic issue. Once again, the units from Semmco LPS have a visual indicator to assist the inspector.
Seals and Valves
Look for compression set, cracking, or contamination on every seal. Any EEBD stored in an environment with chemical vapour, even at low concentrations over a long period, may have experienced seal degradation that a casual visual check won’t catch. For devices covered by EEBD SOLAS requirements on ships, valve function needs confirming against the service manual. “Looks fine” is not a test.
Storage and Access
Is the device in the right place? Good. Now: can it actually be released quickly? Is the locker unobstructed? Is the mounting bracket functional, not corroded, not seized, not obstructed by a cable someone left last Tuesday? The emergency donning sequence assumes the device is exactly where it is expected to be, accessible in seconds. Any deviation from that adds time. In a hazardous atmosphere, time is the only resource that matters.
Labelling
Service date, next inspection date, serial number or asset reference. In regulated environments this is a compliance requirement. It’s also the only way to trace patterns when something fails, to determine whether it’s an isolated fault or a signal affecting a batch, a location type, or a specific storage condition. Unlabeled devices should be treated as non-compliant until their status is confirmed.
When You Find a Problem
The device comes out of service immediately. The location gets marked clearly as non-operational. A replacement goes in before the area returns to use. And the failure gets documented properly, not just replaced, but what failed, when it was found, who found it, and whether other devices in the same environment or from the same batch might be affected.
That last part is what separates a maintenance event from a system signal. A single failing device is a maintenance issue. A pattern of similar failures in similar environments is telling you something about your programme, your storage conditions, or your inspection intervals and ignoring that signal is how organisations end up having the same conversation twice.
The quality of the failure record also matters in a different context: an audit or incident investigation. The question won’t be “was the device replaced?” It will be “did you understand why it failed and take steps to prevent recurrence?” The documentation should be able to answer that.
Failure Patterns Worth Knowing
These show up repeatedly in breathing apparatus servicing across high-risk environments and are worth building into any inspection programme as specific watch points:
- Device degradation in unheated or exposed locations: plant rooms, vessel deck positions, storage areas with significant temperature variation where environmental stress accelerates component wear between inspection cycles
- Hood material breakdown in environments with UV, ozone, or chemical vapour exposure. The degradation can be advanced before it’s visible. If the storage environment has any of these characteristics and the inspection interval hasn’t been reviewed against them, it probably should be
- Seal compression set in older devices that have sat in a fixed compressed position for a long time without interim testing. The seal looks intact. It may not perform as intact
- Bracket and housing corrosion in coastal, offshore, or high-humidity environments rarely affects the device itself, but directly affects whether it can be released quickly enough
- Documentation gaps after personnel changes. When the person responsible for a set of devices moves roles and there’s no structured handover, gaps open quietly. The devices don’t fail. The accountability does
Making the Programme Work
The organisations that maintain EEBD equipment most reliably aren’t the ones with the most sophisticated maintenance systems. They’re the ones that treat inspection as a safety-critical task rather than a compliance task and understand that those two things are genuinely different.
In practice, that means named accountability for each device rather than team or role-level accountability. Any anomaly gets investigated, not just corrected. And periodically, someone checks the inspection process itself, not just the equipment, to confirm that what is documented reflects what is happening.
That last step is the one most organisations skip. Separating the documentation of an inspection from the verification that it was conducted properly is the single most effective structural change most programmes could make. The two are usually assumed to be the same thing. They are not.
Signs the Current Programme Needs a Closer Look
If the inspection records are current but your team can’t quickly describe the condition of a specific device in a specific location, the system is functioning as a record-keeping exercise, not a safety control.
If inspection responsibility has changed hands in the past year without a structured handover, there are almost certainly gaps that haven’t surfaced yet. If devices are stored in environments with chemical vapour, UV, or significant temperature variation and the inspection interval was set without reference to those conditions, the schedule may not match the actual degradation rate.
None of this requires a wholesale overhaul. It requires an honest look at whether what’s documented reflects what’s real and the willingness to close the gap if it doesn’t.
View the Semmco LPS EEBD product range
Conclusion
The purpose of EEBD inspection isn’t to produce a compliant record. It’s to ensure that when someone reaches for a device in the seconds after a gas alarm, a fire, or an atmosphere change, that device works exactly as it should.
Every gap in the maintenance system, every missed interval, every undocumented failure, every handover that wasn’t quite complete reduces the probability of that happening. In environments where atmospheres can become dangerous in seconds and escape routes are constrained, the available margin is already tight. A device that fails at the moment it’s needed eliminates whatever margin existed. Inspection isn’t the administrative part of EEBD management. It’s the whole point.
