Your SMS Is Collecting Data. Is Anyone Reading It?

Most small operators I talk to have solved the first half of safety assurance: they have a way to collect data. Voluntary reports come in. Someone files them. And then — nothing. The reports sit in a folder, the audit findings sit in a spreadsheet, and the operation keeps running exactly as before.

This is where SMS implementations quietly stall. Not for lack of data. For lack of anyone turning data into decisions.

Safety assurance — Subpart D of 14 CFR Part 5 — doesn’t ask you to collect reports. It asks you to monitor safety performance. Those are different jobs. Collecting is clerical. Monitoring means looking at what the data is telling you, deciding what it means, and doing something about it.

THE TRAP: COLLECTING WITHOUT ANALYZING

The pattern is remarkably consistent. An operator sets up reporting, runs an internal audit or two, and diligently files everything. Ask what the top three safety trends were last quarter, and you get a shrug. The data exists; the analysis doesn’t.

A hazard register that nobody re-opens is a diary, not a management tool. Audit findings logged without trending are a to-do list with no memory. If no one is asking “is this getting better or worse,” the system is running on hope.

START WITH THREE NUMBERS, NOT THIRTY

You don’t need a dashboard with forty metrics. For a small operation, three well-chosen safety performance indicators will tell you more than thirty poorly chosen ones.

Pick indicators tied to your actual operation — the events that would hurt you most. A Part 135 operator might track unstable approaches, ground-handling damage events, and the rate of voluntary report submissions. Set a target for each that is realistic, not aspirational. Then watch the trend line, not the single data point. One bad month is noise; three months moving the wrong way is a signal.

Review the indicators on a fixed rhythm — monthly is enough for most small operators. The review itself is the product, not the chart.

THE MONTHLY HABIT THAT MATTERS MOST

That rhythm has a name: management review. Once a month, the people with authority to change things sit down with the trends and make decisions.

Three rules make it work. First, every corrective action gets an owner and a deadline — “the safety manager will look into it” is not an assignment. Second, someone verifies the fix actually worked, not just that it was done. Closing a finding because the paperwork is complete, without checking whether the problem stopped recurring, is how the same finding appears in next year’s audit. Third, write down the decisions. Memory is not a safety system.

CLOSE THE LOOP — IT FEEDS EVERYTHING ELSE

Here’s the part operators miss: analysis feeds reporting. When frontline employees see that a report led to a real change — a procedure rewritten, a piece of equipment fixed, a hazard controlled — they keep reporting. When reports disappear into a folder, reporting dries up, and your data stream dies at the source.

Safety assurance is a loop, not a pipeline. Reports in, analysis, decisions, action, feedback to the reporter — and the loop runs again. Break it anywhere and the whole thing degrades into paperwork.

Your SMS is probably already collecting data. The question is whether anyone is reading it — and what happens after they do.