ART-2025 • Module 4 • Human Factors & Situational Awareness

Why This Matters

Air traffic control is not just passing clearances. It is active risk management in real time. Situational awareness and human performance are what keep small issues from turning into incidents.

When controllers keep a good mental picture of traffic, workload, weather, system status, and intentions, developing problems are caught early — and when we catch them early, recovery is simple, quiet, and safe.

Good teams also speak clearly about their plan. When I say out loud what I intend to do (“I’ll keep XXX high for now and bring YYY first”), everyone in the room hears it. That does two things:

Shared mental model:
Now my colleague knows why I am doing what I am doing. If I suddenly get busy, they can predict my next move and help me.
Safety net:
If my plan is drifting unsafe, they will challenge — “No, keep YYY high instead, wind shifted.” Speaking the plan invites professional challenge, which prevents accidents.

In summary: Human factors is not “soft stuff.” It is core to safe operations. Situational awareness is not magic; it is a set of habits we can train, observe, and protect.

Professional Attitude in ATC

A professional ATCO mindset is not ego, seniority, or loud voice. It is calm control, honest self-check, and respect for procedures.

Own the safety standard:
I am personally responsible for my clearances and separations. I do not assume “someone else is watching it.”
Be challengeable:
If a colleague says “Confirm level, I still have ABC at FL110” that is support, not insult. We’re both protecting the operation.
Speak early, not late:
If I’m reaching mental saturation, I say it. “Stand by, I need traffic status.” That is professionalism.
Continuous scan:
Treat every second as live, not replay. Don’t coast. Expect change. Assume something is building that needs attention.

Professionalism is not “never tired” or “never stressed.” It is admitting limits early, asking for help before the incident, and handing over accurately so that the next controller starts with a safe picture.

Human Behaviour & Error Traps

Most incidents are not caused by one “bad controller.” They come from predictable patterns that repeat in every ACC / APP / TWR. We can name them, spot them, and interrupt them.

Plan continuation bias: Sticking to the original plan even when conditions changed. Example: “We said we’ll land them both, so we’ll land them both” even though runway occupancy is now too tight.
Complacency / assumption: “He’ll vacate fast, he always does.” Dangerous. We stop actively verifying.
Channel overload: When the frequency never goes quiet long enough to think, you shift from planning mode to survival mode.
Fixation: You lock onto one aircraft (“this is my problem child”) and stop scanning the rest.

These traps are normal human reactions under load. The trick is: catch them early, say them out loud, and let your colleague help.

We do not fix these by shouting “BE ALERT.” We fix them by:

saying the plan aloud,
pausing / freezing traffic for 10–20 seconds to reestablish the picture,
reallocating tasks,
and having a “speak up culture” where challenge is expected.

Communication & Handover RT Discipline

RT Discipline

Communication & Handover

Your voice is a control surface. You can actively deconflict, reassure, slow things down, or (if you’re careless) create chaos.

Be crisp, not fast: “ABC123 maintain FL90, traffic opposite direction FL100, report traffic in sight.” Clear and structured beats speed.
No novels: Long transmissions block frequency when others may need you. Short, logical chunks.
Acknowledge readback quality: If the readback was wrong or incomplete, fix it now.
Close the loop with colleague: If you think they cleared someone for take-off while runway is still occupied, ask out loud: “Confirm XYZ123 cleared for take-off?” You are preventing an incident, not insulting them.

Handover / takeover is part of communication. A poor relief briefing is the fastest way to lose situational awareness in the first 30 seconds of your watch.

Minimum content for a relief briefing:

Status: runway in use, weather, equipment outages, staffing, NOTAMs.
Picture: who is where right now; any abnormal / emergency / special handling traffic.
Intent: “After ABC lands, I will line up XYZ, then descend DEF behind him,” etc.

Both controllers must confirm transfer of control out loud.

Stress — Operational View Stress & Load

Stress & Load

Stress — Operational View

Stress in ATC is not always bad. Mild stress keeps you alert and focused. The problem is overload: when demand feels higher than what you can handle.

Past that point, attention narrows, memory drops, and you start missing calls or forgetting coordination. That moment is predictable. You can feel it coming if you notice irritation, mental blocking, or fixation on one aircraft while you stop scanning the rest.

Stress rises when the job feels bigger than your available time / mental space.
Chronic stress without recovery leads to fatigue (see Fatigue & Vigilance).
Acute stress plus high workload can cause tunnel vision: you “hear but don’t process.”

Managing stress is not about “be tough.” It is about noticing overload early and using recovery actions before safety erodes.

Workload Sweet-Spot Workload Band

Workload Band

Workload Sweet-Spot

Good ATC work happens inside a “band” of workload. Too low and you get bored / complacent. Too high and you get saturated.

Under-load → vigilance loss. You might stop scanning, drift mentally, or miss something because it feels “quiet.”
Optimal band → best performance. You’re actively engaged, slightly ahead of the traffic, mentally rehearsing next steps, but not rushed.
Overload → survival mode. You stop thinking ahead. You start “just keeping it alive.”

You will move between these states during a single duty. The skill is noticing where you are and adjusting.

Overload Signals Warning Signs

Overload Signals

Overload is when the traffic / coordination demand exceeds what you can safely process in real time. You will feel it before you formally “lose the picture.”

You silently hope nobody transmits for a few seconds.
You start delaying basic admin tasks (“standby for code”, “standby descent”) because you don’t have 5 seconds free.
You can’t clearly state who is next for departure / landing.
You are reacting, not planning.

When you feel overload, you must actively recover. Recovery is not “take a break after traffic calms.” Recovery happens while still working the position.

Three proven recovery moves:

Anchor: Pause ~5–10 seconds. Restate the verified picture (“ABC level 70 north, DEF climbing 60 eastbound, GHI holding…”). This recentres you.
Externalise: Push the traffic picture out of your head and into tools — update strips / tags / timers / notes. Offload memory.
Share load: Tell your colleague exactly what to guard: “Watch DEF’s climb against traffic from the south.” Delegation is load management, not weakness.

Recovery Actions Recovery Actions

Recovery Actions

A controller who openly says “Stand by, I need traffic status” is doing recovery, not “failing.” This protects safety.

Stabilise the picture: Issue “maintain present heading”, “maintain present altitude”, “hold position” etc., to freeze rapid changes. You’re taking a snapshot so you can think.
Rebuild SA verbally: Say out loud who is where and who’s next. That instantly lets your colleague back you up.
Task-share: Hand off specific jobs: “You take coordination with XYZ ACC, I’ll run arrivals.” Sharing load is not weakness.
Plan next 1–2 minutes, not the whole session: You don’t need the entire day solved. You need the next safe sequence solved.

Situational Awareness (3 Levels) SA Levels

SA Levels

Situational Awareness (3 Levels)

Classic SA model:

Level 1 — Perception: Knowing what is actually happening right now. Who is where, at what level, doing what.
Level 2 — Understanding: Knowing what it means. Who is conflicting, who is priority, what the runway occupancy picture is, where the weather cells are.
Level 3 — Projection: Knowing what will happen in 1–2 minutes if nobody acts. “If I let both continue, they’ll both get to the FAF together.”

Level 3 (projection) is the magic. Good controllers live slightly in the future.

SA Traps & Antidotes Plan Continuation Bias

Plan Continuation Bias

SA Traps & Antidotes

Common traps:

Plan continuation bias: “We’ll just continue like this” even though conditions changed and the plan is now unsafe.
Optimism / normalisation: “It’ll be fine, it’s usually fine.”
Fixation: You stare at one aircraft/problem and forget to scan the rest.
Silence under pressure: Nobody wants to “bother” the busy controller, so a conflict isn’t called out.

Antidotes:

Say the new risk out loud early.
Pause and re-plan before you hit the unsafe point, not after.
Ask for help and assign specific tasks.
Encourage challenge. “Tell me if you see anything else.”

Bias is normal. The goal is to spot it and act, not to pretend it doesn’t exist.

Attention Management Toolkit Attention Toolkit

Attention Toolkit

Attention Management Toolkit

Attention is limited. You have to drive it, not let it wander.

Use a scan rhythm. For example: every 20–30 seconds do a full sweep of your sector. Every second sweep include boundary points / hot strips / coordination fixes. That prevents blind spots.

Avoid alarm fatigue. If everything is “urgent”, nothing is urgent. Use meaningful alerts only and acknowledge them deliberately so you know what you’ve already handled.

Batch housekeeping. Paperwork and admin calls can wait until traffic is light. When traffic builds, keep frequency clean for safety-critical calls.

Scan cadence, every ~20–30 sec. Make scanning intentional, not random.
Use meaningful alerts only. Don’t drown yourself in noise.
Batch admin. Admin waits; safety does not.

Decision Loops (OODA / FOR-DEC) OODA / FOR-DEC

OODA / FOR-DEC

Decision Loops (OODA / FOR-DEC)

These are structured decision models that help you avoid fixation.

OODA: Observe → Orient → Decide → Act. Used to constantly update your mental picture and act before you get stuck.
FOR-DEC: Facts → Options → Risks → Decision → Execution → Check. Forces you to speak the risk and the plan clearly.

Saying decisions out loud (“I’ll keep ABC high, I’ll delay DEF 2 minutes”) lets others follow — and challenge — the plan.

Ergonomics & HMI Ergonomics

Ergonomics

Ergonomics & HMI

“HMI” = Human-Machine Interface. It’s how your console, labels, alerts, strips, checklists, timers, coordination lines, etc. talk to you.

Good HMI reduces cognitive load. Clear labels, obvious warning states, predictable colours, no clutter.
Bad HMI forces you to “decode the system,” wasting attention that should be on traffic.
Physical ergonomics matters: seating, posture, screen angle, glare. Pain = distraction.

If your tools work against you (bad display, unreadable tag, sticky strip process), speak up. Fixing ergonomics is a safety action, not “complaint.”

Fatigue & Vigilance Fatigue Risk

Fatigue Risk

Fatigue & Vigilance

Human alertness follows circadian rhythm. Nights, early mornings, extended duty, and back-to-back shifts reduce vigilance.

You have to manage yourself proactively:

Hydrate, micro-break, stretch / move with control.
Watch for microsleep — brief uncontrolled nodding or slow blinking. If that happens, you must speak up, swap or reset. At that point you are unsafe, not “a bit tired.”
Fatigue management is not only tonight. Plan sleep, commute, and recovery across the roster.

Know your circadian lows.
Controlled breaks and hydration.
Microsleep = immediate action.

Time & Peer Pressure Operational Pressure

Operational Pressure

Time & Peer Pressure

External pressure is real:

Airline wants “minimum delay.”
Pilot sounding impatient.
Supervisor asking “Can you take one more departure before arrival XYZ?”

Pressure is not authority. Safety comes first.

You are allowed to say “Unable right now, standby.”
You are allowed to slow the plan: “Hold position,” “Maintain present heading.”
You are allowed to go around.

Saying “No” early is cheaper than cleaning up a loss of separation.

Team Situational Awareness Team SA

Team SA

Team Situational Awareness

SA is not only in your head. It is shared between people.

When I say out loud “After this arrival I’ll depart ABC and then descend DEF,” I am transferring intent — not just facts.

Complacency is the enemy of vigilance.
Treat every session as live, not replay. Scan as if something is waiting to go wrong.
Accountability plus support.
I am responsible for my clearances, and I am also responsible for backing up my colleague.
Invite challenge.
“Let me know if you see anything else” is professional behaviour in high-reliability operations.

Position Relief Briefing Relief Briefing

Relief Briefing

Position Relief Briefing

Handover / takeover must be structured. The relieving controller must start with a safe picture, not guesswork.

Status: runway config, weather, outages, NOTAMs.
Picture: who is where, any specials / emergencies.
Intent: what is about to happen next.

Tips:

Speak in plain language, not shorthand.
“Status → Picture → Intent” is the standard order.
The relieving controller must restate; both confirm the exact transfer moment.
Unusual events and unusual handovers should be timestamped.

Substances & Medication Fitness for Duty

Fitness for Duty

Substances & Medication

Alcohol, recreational drugs, or sedating medicines are incompatible with ATC duty. Even legal medication can slow you or make you less coordinated.

If you’re on medication and you’re not sure about its effect, you must declare it and get medical guidance before duty. Hiding it is not “being tough”; it’s creating an operational hazard.

Medication side-effects (drowsiness, delayed reaction).
Residual alcohol / hangover.
Self-medicating stimulants / energy boosters.

Fatigue, stress, and medication mix badly. If in doubt: escalate early, don’t improvise.

Error Management & Learning Learning Culture

Learning Culture

Error Management & Learning

Controllers are human. We will make mistakes. The question is: do we surface them, learn, and fix the system — or do we hide them until one of them burns us?

“Just Culture” means we examine what happened and why, not “who to punish by default.”
We report incidents and near misses early.
We discuss openly what worked in recovery.
We fix systemic contributors (staffing, tools, procedure gaps), not just “tell the controller to concentrate.”

Culture must support speaking up. If people fear punishment for honest reporting, they will hide the warning signs until it is too late.

Case Vignettes Case Vignettes

Case Vignettes

Short, realistic “this really happens” ATC situations:

Vignette 1: Runway occupancy squeeze.
Arrival has not vacated yet. Departing traffic lined up. You feel supervisor pressure: “Can you get him out?” You say: “Negative, wait for runway vacated.” You prevent a runway incursion and a reportable event.
Vignette 2: Loss of SA then recovery.
You momentarily lose track of an inbound. You say, clearly, “Stand by, I need traffic status.” You freeze changes, rebuild aloud, and assign your partner to watch a single conflict.
Vignette 3: Plan continuation bias.
You realise two aircraft will compress on final. Instead of “just try it,” you order a go-around early and restack the sequence. You treat safety as normal, not as “aborting.”

Takeaway: speaking early, freezing change, and clear delegation are practical safety tools. They are not magic.

You are allowed to slow the plan.
You are allowed to say “stand by.”
You are allowed to force a re-plan and reassess now, not later.

High-Load Checklist (Live) READY Indicator

High-Load Checklist (Live)

Use this when the workload starts feeling heavy or your mental picture begins to fade. Work through the steps — once every item is ticked, the frame turns green and shows READY ✅.

High-Load Actions

Re-establish the picture: Quickly review who’s where and what’s happening — mentally rebuild your traffic and coordination overview.

Set immediate priorities: Identify the one or two aircraft or tasks that need attention first; park anything non-essential for the moment.

Request focused support: Ask your colleague or planner for a clear, limited assist — e.g. “Watch DEF’s climb against southbound traffic.”

Record the essentials: Update strips, radar tags, or notes so the current status is visible; this eases the mental load.

Look one to two minutes ahead: Predict which aircraft will interact next or where spacing may tighten.

State the plan clearly: Brief your colleague or team in short, plain language — confirm what you’re doing next and why.

“READY” means you’ve regained control of the picture — not that the workload vanished, but that it’s back under management.

Key Takeaways Must-Remember Points

Must-Remember Points

Key Takeaways

Situational awareness is a habit, not magic. You build and speak your mental picture.
Speak early if you’re losing the picture. Saying “Stand by…” is recovery, not failure.
You’re allowed to slow down the plan to keep it safe.
Good handover = Status → Picture → Intent.
Our strongest safety tools day-to-day are: clear communication, professional challenge, early support from a colleague.

Review Quiz (5 Questions) Self Check

Self Check

Review Quiz (5 Questions)

Click an answer. You’ll immediately see if you’re correct and why.

Loading quiz…