Building an SMS Program People Will Actually Use

← Back to Resources

The Manual on the Shelf Problem

Every operator knows the type. A thick binder sitting on a shelf in the office, full of policies nobody reads, procedures nobody follows, and forms nobody fills out. It checks a box. It doesn't make anyone safer.

That's the risk with SMS compliance. The FAA requires you to have a Safety Management System under 14 CFR Part 5 by May 28, 2027. But the regulation doesn't just ask for a document. It asks for a functioning system with active hazard identification, ongoing risk assessment, safety performance monitoring, internal audits, and a reporting culture that actually produces reports. If your SMS lives on a shelf and only comes out when the CMT visits, you don't have a safety management system. You have a liability.

Start With How You Actually Operate

The biggest mistake operators make is building their SMS around a template instead of around their operation. Templates give you structure, and structure is useful. But when the content doesn't reflect how your company actually runs, two things happen: your people ignore it because it doesn't match their reality, and your inspectors see through it because it reads like a generic document with your name on it.

A good SMS starts with an honest look at your operation. What aircraft do you fly? What routes and environments do you operate in? What are the real hazards your pilots and dispatchers deal with on a regular basis? How does information flow between the people making safety decisions? The answers to those questions should drive every section of your manual, from your hazard identification process to your safety performance indicators.

Make Reporting Easy or It Won't Happen

Safety reporting is the engine of any SMS. Without reports coming in, your hazard identification process has nothing to work with, your risk assessments are based on assumptions instead of data, and your safety assurance program is running blind.

The problem is that most pilots and crew members won't fill out a complicated form unless they absolutely have to. If your reporting process requires logging into a portal, navigating a menu, filling out 15 fields, and clicking through three screens, you're going to get reports only when something goes seriously wrong. The everyday observations, the near misses, the "that didn't feel right" moments? Those will go unreported.

We build our safety reporting systems to be as simple as possible. A one-page form, accessible from a phone, that takes two minutes to fill out. The goal is to remove every possible barrier between a pilot noticing a hazard and that hazard entering your system. Once it's in the system, you can assess it, track it, and do something about it. But it has to get there first.

Single-Pilot SMS: Smaller Operation, Same Requirements

If you're a single-pilot Part 135 operator, you might be wondering how all of this applies to you. The answer is: most of it still does.

Part 5 does provide limited exceptions for operations where one person serves as the sole individual responsible for safe operations. Some of the internal communication and management review requirements are scaled back because, frankly, you can't hold a formal meeting with yourself. But the core components still apply. You still need a safety policy. You still need a process for identifying hazards and assessing risk. You still need safety assurance procedures, training documentation, and a way to track safety performance over time.

The challenge for single-pilot operations isn't the scope of the requirements. It's the bandwidth. You're the pilot, the safety manager, the accountable executive, and probably the person answering the phone. You don't have time to manage a complex software platform on top of everything else.

Your Risk Matrix Should Mean Something

Every SMS includes a risk matrix. Most of them are a 5x5 grid copied from AC 120-92D with generic likelihood and severity definitions. That's a starting point, but it's not enough.

Your risk matrix should use language and scenarios that are specific to your operation. If you fly single-pilot IFR in mountainous terrain, your severity definitions should reflect that environment. If you operate floats in remote areas without reliable weather reporting, your likelihood categories should account for the information gaps your pilots actually deal with. A risk matrix that feels abstract and disconnected from daily operations is a risk matrix that nobody uses.

When we build a risk matrix for a client, we calibrate it to their actual operating environment. The definitions reference real scenarios. The examples come from hazards we identified during the system description process. The result is a tool that pilots and managers can look at and immediately apply to a real decision, not an academic exercise they skip past.

Training That Sticks

Part 5 requires safety promotion, which includes initial and recurrent SMS training. A lot of operators treat this as a checkbox: sit everyone down once a year, run through the slides, collect the signatures.

Training works better when it's tied to real events in your operation. Use your own safety reports as case studies. Walk through an actual risk assessment your team completed. Review a hazard that was identified, assessed, and mitigated using your own SRM process. When people see the system working with real examples from their own operation, they understand it. When they understand it, they use it.

Build It Right the First Time

The operators who invest the time upfront to build an SMS that genuinely fits their operation are the ones who end up with a program that works. Not just during surveillance, but every day. The reports come in. The risk assessments get done. The audits produce findings that lead to real improvements. That's the difference between compliance and safety, and a well-built SMS delivers both.

If you're getting started on your SMS, or if you have one that isn't working the way it should, we can help. Every program we build is customized to the operation, delivered at a one-time cost with no monthly fees, and designed to be something your people will actually use.