Safety Management Systems and Occurrence Reporting
SMS Framework
Safety management systems (SMS) are required for operators and maintenance organizations under RBAC. The SMS has four components: safety policy and objectives, safety risk management, safety assurance, and safety promotion. Candidates must understand the difference between reactive, proactive, and predictive safety management. Occurrence reporting is a key element: personnel must report accidents, serious incidents, and other occurrences to CENIPA and ANAC as required. The reporting system should be non-punitive to encourage reporting, but gross negligence or willful violations are not protected.
Concepts to Master
Know the definition of an occurrence and the reporting timelines. Understand the role of the safety manager and the safety review board. Be familiar with hazard identification, risk assessment (severity and likelihood), and mitigation. Also know the concept of a just culture and how it balances accountability with learning. Understand the requirements for internal occurrence reporting systems and the protection of safety data.
Traps
A common trap is assuming all reports go to CENIPA; some go to ANAC or the operator's SMS. Another is confusing a hazard with a risk. Also watch for the assumption that a voluntary report is always anonymous; confidentiality is protected but not necessarily anonymity.
Worked Example / Rule of Thumb
Rule: "Report immediately, investigate proportionally, learn systematically." Example: A mechanic notices a fuel leak during maintenance. This is an occurrence that must be reported internally and, if it meets the criteria, to CENIPA. The SMS investigates the root cause, implements corrective actions, and shares lessons learned.