Safety Management, Occurrence Reporting and Accident Investigation
What this domain tests
This domain links the State safety programme, an operator's safety management system, mandatory occurrence reporting and accident investigation. It tests the difference between safety data used to prevent recurrence and enforcement action, and the need to preserve evidence after an accident.
Core requirements
- An SMS identifies hazards, assesses risk, sets controls and monitors safety performance.
- Occurrence reporting is mandatory for specified accidents and incidents; reports must be timely and factual.
- Just culture encourages reporting without condoning gross negligence or deliberate misconduct.
- Accident investigation follows Annex 13 principles and PNG investigation law; it is separate from CASA PNG enforcement.
- Evidence must be preserved; wreckage, recordings and records must not be disturbed unless necessary for safety.
Worked example
An AME finds a fatigue crack during a routine inspection and reports it through the operator's SMS. The operator grounds the aircraft and notifies CASA PNG as required. The AME records the finding and preserves the removed part. The report is used to assess fleet risk; the AME is not expected to hide the finding to avoid commercial disruption.
Traps that cost marks
Treating the SMS as paperwork rather than a risk-control system; assuming an investigation's purpose is to assign blame; missing a reporting deadline; and disturbing wreckage before the investigating authority authorises it.