Most safety programs don’t stall because employees stop caring about safety. The program is in place, reports are being submitted, meetings are occurring, and corrective actions are being tracked. Then, somewhere along the way, the program starts running on autopilot.
There’s a lot of work involved in building and maintaining an SMS, especially in the aviation industry. Getting the right processes, training, documentation, and reporting systems in place is a big part of that. The problem comes when having those things in place becomes the measure of success.
Over time, safety managers must ask if these processes are still working. Are employees actually using the reporting system? Are you seeing the same issues come up again and again? Are corrective actions fixing the problem or simply closing it? Are the safety metrics you’ve been tracking for years telling you anything useful?
Most safety programs have plenty of data, it’s just a matter of connecting it. Between employee reports, ASAP, audits, investigations, risk assessments, flight data, and corrective actions, there can be more information than anyone realistically has time to dig through.
Maybe one report doesn’t seem particularly concerning. But what if you’re seeing something similar in ASAP? What if it also showed up during an audit, or there’s a trend buried in your operational data?
Sometimes the issue isn’t collecting more safety data; it’s taking a better look at what you already have.
We talk a lot about encouraging employees to report, but there’s another side to that conversation that’s easy to overlook: employees want to know that reporting matters.
If someone takes the time to raise a concern and never hears anything about it again, they’re going to notice. If that happens repeatedly, eventually they may decide there isn’t much point in speaking up.
That doesn’t necessarily mean there are fewer safety concerns. It may just mean you’re hearing about fewer of them.
Sometimes “Here’s what we changed because you spoke up” does more for safety culture than another reminder to submit reports.
The safety team can manage the SMS, analyze data, facilitate ASAP, investigate events, and keep corrective actions moving. But they can’t own safety for everyone else.
The strongest programs are the ones where operational managers are engaged, leadership pays attention to what the data is saying, and employees see the SMS as part of how the organization operates… not something that belongs to the safety department.
That’s often where stalled programs need the most attention.
Instead of asking “Is our SMS working?”, try asking: “Where have we gotten a little too comfortable?”
Look at the issues that keep coming back: the metrics everyone reviews because they’ve always reviewed them, the corrective actions that get closed without really changing the outcome, the parts of the program that haven’t changed in years. Those areas may tell you more about the health of your SMS than another checklist ever could.
At Fuzion Safety, we work with aviation organizations at very different stages of their safety programs. Through WBAT support, ASAP facilitation, SMS services, training, and safety data support, we get a close look at what makes these programs work in the real world.
Moving a program forward isn’t about adding another process. It’s about taking a fresh look at the ones you already have. A safety program doesn’t have to be failing to need attention; sometimes it just gets stuck.
