Civilian Airports / Safety Management System

Safety Management System

Hazard reporting, risk assessment, and safety assurance in one closed loop.

The problem

A safety management system is only as good as the loop it closes

A hazard report that goes nowhere after it's filed isn't a safety management system. It's a form. §139.401 asks for a closed loop: a hazard gets assessed for risk, tracked against a safety performance indicator, and any change that could introduce a new hazard gets reviewed before it happens, not after.

And the person best positioned to notice a hazard is often a tenant or a ramp worker with no login to the system that's supposed to hear about it, so the loop has to start somewhere the Accountable Executive isn't the only one who can reach.

How it works

The four pillars, one screen for the Accountable Executive

  1. 01

    Four pillars, one view

    Safety Policy status, hazards by risk band, Safety Performance Indicators against target, and open Management of Change items, all on the same screen.

  2. 02

    Anyone can report a hazard, not just staff

    A public, anonymous safety-report link (built for a QR code on a terminal wall, a ramp entrance, or an AEP briefing) feeds straight into the same hazard queue as an internal report.

  3. 03

    Hazards move through assessment, not just a list

    Every hazard gets a risk band (high, medium, low) and stays visibly unassessed until it doesn't, instead of sitting unreviewed off to the side.

  4. 04

    One export for an inspector visit

    Policy, hazards, SPIs, audits, Management of Change, and reports all export as a single SMS Manual PDF, built from current data instead of assembled beforehand.

Safety Management System overview for a demo regional airport
The Safety Management System overview for a demo regional airport, subtitled for the Accountable Executive and citing 14 CFR §139.401: Safety Policy reading Current, Hazards (6) split High 0 / Medium 1 / Low 5 / Unassessed 0, SPIs (6) split Alert 3 / Warning 0 / On target 3, and Management of Change showing 0 open MoCs and 6 reports to triage, plus quick links to Policy, Hazards, SPIs, Reports, Audits, and MoC, an SMS Manual PDF export, and a Public Safety Reporting box naming the anonymous report URL to share on terminal walls, ramp entrances, and AEP briefings.

Built on the regulation

The citation, implemented

  • 14 CFR §139.401

    §139.401 requires a Safety Management System built on a documented policy, hazard identification and risk assessment, safety assurance through measured indicators, and a promotion process for review. The four pillars on this screen are that requirement running as a working system, not a manual kept separately from the data behind it.

The benefit

What it automates

Every hazard has a risk band, not just a status

High, medium, low, or unassessed: nothing sits untriaged without also being visibly untriaged.

Reporting doesn't require a login

The public, anonymous link puts hazard reporting in reach of anyone on the airport, not just the people with an account.

The manual is one click, not a project

Every pillar exports into a single SMS Manual PDF built from current data, ready for an inspector visit without weeks of assembly.

Related

Works alongside

FAQ

Straight answers

Who can submit a safety report?

Anyone. The public, anonymous link works without a login and feeds the same queue an internally filed report would.

What are SPIs?

Safety Performance Indicators, measured and tracked against alert and warning thresholds, so a negative trend shows up before it becomes a hazard.

What does Management of Change track?

Anything that could introduce a new hazard, kept open until it's reviewed and either approved or resolved by the Accountable Executive.

Can I export the whole SMS manual at once?

Yes, one button builds the manual PDF from policy, hazards, SPIs, audits, Management of Change, and reports as they currently stand.