The operational core of an SMS: a single intake for safety and hazard reports, a 5×5 likelihood-by-severity risk matrix to triage them consistently, audit findings you can track to closure, and a computed crew fatigue risk score that traces back to its inputs — all in the same workspace as your scheduling and compliance.
Anyone can file a safety or hazard report — a bird strike, ramp FOD, an unstable approach, a fatigue concern. It lands in one queue with its severity, so nothing gets buried in an inbox.
Rate each hazard by likelihood × severity on a consistent five-by-five matrix, so the safety manager triages the highest-risk findings first instead of arguing severity case by case.
Audit findings carry an owner, a due date, and an OPEN → CLOSED status, with an open-findings count on the dashboard so nothing is filed and forgotten.
The crew fatigue risk score is a computed, rule-based number — it blends documented duty load with crew members' self-reported sleep and rest, and every score traces back to the inputs behind it. It is deterministic and explainable: same inputs, same score. It is not an AI prediction and not a black-box model — it surfaces who to look at first, and the safety manager decides what to do about it.
Anyone in the operation can file a safety or hazard report — a bird strike, FOD on the ramp, an unstable approach, a fatigue concern. Each report lands in one intake queue with its severity, so nothing depends on a clipboard in the chief pilot's office or an email that gets buried.
Each hazard is rated on a five-by-five matrix — likelihood across one axis, severity up the other — to produce a consistent risk rating. The matrix gives the safety manager a repeatable way to triage what to act on first, instead of arguing severity case by case.
Yes. Audit findings carry an owner and a due date and move OPEN → IN_PROGRESS → CLOSED, and the dashboard shows an open-findings count so a finding stays visible until it's closed. Per-report corrective-action items with their own owners and status are on the roadmap.
No. The fatigue risk score is a computed, rule-based number — it blends documented duty load with crew members' self-reported sleep and rest, and every score traces back to its inputs. It is deterministic and explainable, not an AI prediction or a black-box model.
It's the operational backbone of an SMS — report intake, risk assessment on a 5×5 matrix, audit-finding tracking, and a fatigue risk view — kept in the same workspace as your scheduling, crew, and compliance. Your safety policy, training, and assurance program still sit around it; this is where the day-to-day safety work lives.