Human Factors and Safety Management
This domain tests situational awareness, fatigue, teamwork and safety management as they appear on the position: why an experienced controller misses a conflict, how fatigue is managed, what just culture really means, and how an SMS functions beyond the manual.
Situational awareness
- Three levels: perception of the traffic, comprehension of what it means, and projection of what will happen next.
- Losses come from attentional tunnelling, expectation bias, ambiguous displays and high workload. Symptoms: unexplained traffic, forgotten strip updates, surprise at a call.
- Recovery relies on cross-checks, verbalising the plan and using memory aids such as electronic strips and reminders.
Fatigue
- Driven by circadian rhythm, time awake, sleep debt and workload; the early-morning window and the post-lunch dip are high-risk.
- Managed through Fatigue Risk Management Systems, duty limits, strategic and tactical controls, and controlled rest on position where approved.
- Fatigue is not a personal failing; it is a managed hazard that must be reported.
Teamwork
- Team resource management: briefings, workload sharing, challenge and response, closed-loop communication and assertive escalation when a colleague's action looks unsafe.
- A good challenge names the observation and the risk, not the person.
SMS and just culture
- Annex 19 sets the framework: four components (policy and objectives, risk management, assurance, promotion) delivered through twelve elements.
- Just culture distinguishes unintended error (supported, reported, learned from) from reckless or grossly negligent behaviour (subject to disciplinary action). Blame-free is not the same as consequence-free.
- Reporting systems work only if reporters trust the outcome.
Worked example
Two aircraft with similar callsigns are cleared at once. Reasoning: this is a classic expectancy error, not a knowledge gap. Correct response: stop issuing further clearances, re-verify each aircraft's strip and radar label, use full callsigns, and file a report so the hazard (callsign similarity) is mitigated in the schedule.
Traps
Treating SMS as a documentation exercise; confusing just culture with no accountability; assuming experience prevents error; ignoring fatigue because the roster is legal.