Aviation hazard reporting for small Part 135 operators: building a system that actually works

Most small Part 135 operators have a hazard reporting system on paper. Few have one that is actually used. The gap between the two is where SMS audits find their most common finding — and where the most preventable accidents originate.

A hazard reporting system does not need to be sophisticated. It needs three things: a low-friction way to submit a report, a documented response process, and evidence that the response happened. Everything else is overhead.

What a hazard report covers

A hazard is any condition, event, or circumstance that could lead to an accident if not addressed. In a Part 135 operation, hazards typically fall into a few categories:

• Aircraft condition hazards — a squawk that was deferred but seems to be getting worse; an instrument that reads inconsistently; a door seal that the crew has been working around.
• Operational hazards — a route segment with consistently poor ATIS updates; a destination airport where the approach lighting is frequently NOTAMed out; a passenger loading procedure that puts crew in an awkward position.
• Organizational hazards — scheduling pressure that causes crews to accept flights with less rest than they would prefer; a dispatch process that moves faster than the compliance check allows; a training schedule that is always the first thing to slip when operations get busy.
• Environmental hazards — a ramp at a frequently-used airport with poor lighting; a FBO that has had multiple fuel contamination incidents; a handling agent that consistently produces incorrect weight and balance.

Near-misses and incidents also belong in the system — not just hazards caught before anything happened. The distinction matters: a near-miss that is not reported cannot be investigated, and a pattern that could be caught early instead surfaces after an accident.

The minimum viable reporting system

For a 2–10 aircraft operation, the system can be simple:

• A reporting channel. An email address, a shared inbox, a paper form in the crew room, or a simple web form. The channel does not matter — friction does. If reporting requires logging into a system, finding a form, and waiting for approval, it will not be used. If it requires sending an email to one address, it will.
• An acknowledgment process. Every report receives an acknowledgment within 24 hours. The acknowledgment does not need to contain a resolution — it needs to confirm the report was received and is being reviewed. Silence after a report is the fastest way to kill a reporting culture.
• A corrective action decision. Every report receives a documented disposition: either a corrective action is opened (with an owner and a due date), or the report is closed with a documented reason why no action is required. Both outcomes are acceptable. No outcome is not.
• A closed-loop notification. The person who filed the report is told what happened. If a corrective action was opened, they hear when it is closed. This closes the loop and demonstrates that reporting produces results.

Just culture — the non-negotiable foundation

No reporting system works without a just culture — an organizational commitment that good-faith reports of hazards, near-misses, or errors will not result in punishment for the reporter. This must be explicit in the safety policy and demonstrated in practice.

The test of a just culture is not what the safety policy says. It is what happens the first time a pilot reports that they accepted a flight with less rest than they should have. If that report results in a corrective conversation and a process fix, the culture is functioning. If it results in a disciplinary action, every crew member in the company will know within a week, and no one will report anything again.

Just culture does not mean no accountability for willful violations. It means that honest mistakes and good-faith disclosures are treated as information, not evidence for punishment.

What auditors check

An FSDO SMS audit or an insurance loss-control review of hazard reporting looks for four things:

1. Does the system exist? Is there a documented reporting channel, a defined response process, and a written commitment to just culture in the safety policy?
2. Is it being used? Are there reports in the system? A certificate holder with zero hazard reports in 12 months is not a safe operation — it is an operation with a broken reporting culture.
3. Are reports being responded to? Does each report have a disposition? Are corrective actions opened when warranted? Are they closed?
4. Is the data being used? Are trends identified? Has the system ever caught a hazard that led to a process change? The value of the reporting system is in what the organization learns from it — not in the volume of reports.

A small operator with 12 hazard reports, all responded to, with 9 corrective actions opened and 8 closed, is in a far better position than one with zero reports. The auditor's question is not "did anything go wrong?" It is "are you paying attention?"

Connecting to the corrective action register

Every hazard report that results in a corrective action needs to flow into the corrective action register — the document that tracks open items from identification to closure. The register is the evidence trail that shows the reporting system is not just collecting information but acting on it.

The most common failure mode is a good reporting channel paired with a broken handoff to corrective actions. Reports come in, acknowledgments go out, and then nothing — no corrective action opened, no closure documented. The report lives in an inbox and ages out. When the auditor asks about Hazard Report #14 from eight months ago, there is no answer.

The fix is a simple rule: every report is either closed with a documented disposition or escalated to a corrective action within five business days. No report ages past five days without a status.