Safety Management Systems and Occurrence Reporting
SMS as a management system
A safety management system is not a manual; it is four interlocking components: safety policy and objectives, safety risk management, safety assurance, and safety promotion. Candidates must recognise the difference between reactive, proactive, and predictive processes. Hazard identification feeds risk assessment, which uses severity and likelihood to produce a tolerable or intolerable rating; safety assurance then monitors through audits, data analysis, and change management. A frequent trap is confusing a hazard (a condition with potential to cause harm) with a risk (the assessed combination of severity and likelihood). Another trap treats occurrence reporting as punitive; the reporting system exists to feed safety data, and the rules distinguish mandatory reportable occurrences from voluntary confidential reporting.
Occurrence reporting mechanics
Know what must be reported, to whom, and how quickly. Serious incidents and accidents go to the investigation authority; the operator also notifies the regulator through its own system. Timelines and the protection of reporters are commonly tested. Just culture is central: honest error is distinguished from gross negligence or deliberate violation, and disciplinary action is not the purpose of reporting.
Worked example
A crew reports a runway incursion that was resolved without collision. The operator classifies it, files within the required time, and enters it into the safety data system. The investigation authority decides whether to investigate; the operator's SMS performs its own analysis, identifies a contributing factor in taxi clearance readback, and issues a mitigation. The crew is not disciplined for the honest error, and the report is protected as safety data.