Every operator has a manual. Fewer operators can say, with confidence, that the manual matches what actually happens on the line every day. That gap, between the procedure on paper and the procedure in practice, is where procedural non-compliance lives. And it’s rarely a training problem. It’s a systems problem, and closing it is a company’s job, not an individual’s.
The Myth of the “Bad Apple”
When a deviation surfaces, whether it’s a checklist skipped, a shortcut taken on the ramp, or a step quietly reordered because it’s always been done that way, the easy read is that someone got careless. Write them up, retrain them, move on. But that framing misses the more useful question: why did following the procedure feel harder, slower, or less practical than not following it in that moment?
Procedures don’t get ignored in a vacuum. They get ignored when they’re outdated, when they were written by someone who’s never done the task, when they add steps that don’t reflect the tools in use, or when the operational tempo makes strict compliance feel impossible without falling behind. In most cases, the person deviating isn’t rejecting safety. They’re solving a problem the manual didn’t anticipate.
That distinction matters, because it changes where the company looks for the fix.
Gather Employee Input
The single most effective thing a company can do to limit procedural non-compliance is talk to the people doing the work before writing the procedure that governs it. Line pilots, maintenance techs, dispatchers, and ground crews know where a procedure breaks down in practice long before it shows up in an audit finding. A manual built with their input is a manual people can follow, because it was written for the job as it’s really performed, not the job as someone imagined it from an office.
This is also where usability earns its keep. A procedure buried in dense, cross-referenced text that takes ten minutes to locate isn’t a safety tool. It’s a compliance tool. If following the correct procedure takes longer than finding a workaround, it becomes tempting under real-world pressure to find the workaround. Clear, accessible, field-tested procedures aren’t a nice-to-have. They’re the difference between a document people rely on and one they route around.
Safety Requires Predictability
To ensure the highest level of safety performance, organizations must have reliable, repeatable, predictable systems in place. Any workaround of established procedures removes that predictability. Leadership doesn’t see the difference between work as imagined and work as performed. They assume the procedure is being followed. The reality may be quite different. That practical drift is where danger lives. This is why it’s critical to foster a culture that allows poor procedures to be called out and corrected. Otherwise, you’re finding out a procedure is inadequate at the worst possible time: after an incident.
Build a Way to Hear About It
Even well-designed procedures will run into situations nobody predicted. The question is whether your organization finds out about those gaps before or after something goes wrong. That’s the entire premise behind voluntary reporting programs: give people a way to disclose a deviation, a near miss, or a procedure that doesn’t work as written, without fear that doing so will end their career. Operators who treat every report as a disciplinary event will stop getting reports. Operators who treat reports as data will start closing the gaps that cause non-compliance in the first place.
An SMS built around this principle turns procedural drift from a hidden risk into a visible, manageable one. That’s a full feedback loop, and it only works if leadership protects it.
Audit the Practice, Not Just the Words
Regulatory audits confirm the manual exists and says the right things. They don’t always confirm the manual reflects reality. Your internal audit practices should not just check words on a page; they should check implementation and monitoring as well. Safety data, line check data, regular hangar walks, and training information can be valuable tools to ensure that the work as imagined matches the work as performed. This will help identify faulty process and procedure and will ensure it is caught further upstream than a post-event investigation.
Review Manuals and Checklists Regularly
Everyone has worked somewhere where the manual sits idle until a change is prompted by some outside force. It’s especially easy to do when there’s no in-your-face reason to change it: no recent events, no regulatory pressure, no third-party audit finding. Regular reviews of manuals and checklists in the absence of outside pressure isn’t just a good idea, it’s necessary for the safety health of an organization. Proactivity in identifying procedures that need some mending helps keep things predictable, and predictability drives safety. The frequency that you review is organizationally dependent but should include input from your front-line workers.
The same core moves apply regardless of fleet or company size: write procedures with input from the people who use them, protect safe disclosure, and check performance against practice, not just paperwork.
ACSF’s Member Assistance Program and IAS Lite exist specifically to make that achievable for operators without dedicated safety staff.
Procedural non-compliance isn’t solved by demanding better behavior. It’s solved by building a system where the safe path and the practical path are the same path. That’s a company’s responsibility, and it’s one worth taking seriously.
