Controller Workload
Controller Workload
Article Information
Category:
Content source:
Content control:
Last modified:
15.Nov.2023
Article UID:
Cite This Page
SKYbrary Aviation Safety. (November 15, 2023). Controller Workload.
Retrieved June 4, 2026
from https://skybrary.aero/articles/controller-workload
UID: 22944
Copied!
COPY
Description
The role of the ATCO is to ensure the safe and expeditious flow of air traffic through the airspace for which they have responsibility. A controller must remain alert and effective throughout that part of their assigned shift which involves operational duty, ready to cope with unexpected or unforeseen situations such as the consequences of aircraft emergency declarations or extreme weather conditions.
The workload of a controller must be accurately assessed to permit optimum efficiency. If it is too high for too long, they may be overstretched. If it is too low for too long, this not only constitutes an inefficient application of resources but is likely to increase the chances of a controller becoming distracted from their primary task.
Effects
- An overworked controller may:
- Have difficulty maintaining Situational Awareness;
- Overlook a developing unsafe situation;
- Make errors of judgement;
- Become confused;
- Be unable to cope with a sudden increase in workload.
- A controller experiencing significant periods of underwork during a partcular shift may become bored and distracted from their primary task. Repetition of this over many consecutive shifts may lead to Complacency and invites specific measures for Risk Mitigation
Defences
- Airspace is divided into sectors of responsibility sized according to the capability of a single controller.
- These sectors must be capable of being combined or split, on a tactical basis, where traffic levels are subject to significant variation from the sector design assumptions.
- Controllers are provided with Safety Nets and back-up teams to support their work.
- Shift patterns are designed to ensure that controllers can have sufficient rest and to reflect the different off duty rest issues for night-time and daylight duties.
- Each working duty contains appropriate breaks to allow controllers to rest and, if necessary, to recover after periods of high workload.
- SOPs properly define hand-over procedures so that an on-going controller is fully briefed before taking over a position.
- Ensure that all aspects of on the job training (OJT) are governed by effective SOPs
Contributory Factors
- Staff shortage;
- Equipment malfunction or failure;
- Controller Position Design;
- Poor Team Resource Management (TRM);
- Inadequate Standard Operating Procedures (SOPs).
Solutions
- Ensure that staffing levels are adequate to cope with the expected task in peak periods, plus a margin to allow for sickness, training, etc;
- Split sectors in periods of very high activity; combine sectors in quiet periods;
- Rotate controllers’ duties to provide variety;
- Review and if necessary improve the design of the controller’s position;
- Ensure that adequate rest breaks are scheduled and that rest conditions are satisfactory.
- Review and if necessary improve TRM training provisions.
- Review and if necessary improve SOPs for handover/takeover of duties; ensure that SOPs are followed.
SKYclip
Related Articles
Further Reading
HindSight Articles:
Categories
What Links Here (86)
- Loss of Separation
- Loss of Separation - ATCO-induced Situations
- Situational Awareness
- Runway Incursion
- Level Bust
- Airspace Infringement
- Airspace Infringement and Communication
- ATC Clearance
- Base Effect
- Hindsight 13
- Hindsight 21
- Short Term ATFCM Measures (STAM)
- B744 / A306, vicinity London Heathrow UK, 1996
- Air-Ground Voice Communications
- Blocked Transmissions / Undetected Simultaneous Transmissions (USiT)
- Call Sign Confusion
- Frequency Congestion
- Loss of Communication
- Radio Discipline
- Radio Interference
- Speed and Timeliness of Communication
- Standard Phraseology
- Airspace Infringement and Briefing
- European Airspace Infringement Action Plan
- Level Bust - ATCO-Induced Situations
- ATC Unit Coordination
- Basic Controller Techniques: Speed Control
- Basic Controller Techniques: Vertical Speed
- Blind Spots - Inefficient conflict detection with closest aircraft
- Conflict Detection
- Midair Collision
- Minimum Hours in Position
- State Aircraft and Formation Flights - Separation Minima
- Structured Scan for Mitigating the Blind Spot Effect
- Surveillance
- Aligned Weather Impact Management
- Airspace Infringement and Navigation
- Methods to Show an Occupied Runway
- Taxi-in Runway Incursions
- Similar Call Signs
- Update on Erroneous '0607' squawk
- ATC Task Demand
- ATM Shift Management
- Cross-Checking Process
- Fatigue
- Pilot Workload
- Teamwork in Air Traffic Control
- Vigilance in ATM
- ATCO On-Duty Fitness
- ATC Clearance Error
- ATC Team Coordination
- Team Resource Management (TRM)
- Conflict Detection with Adjacent Sectors
- Automation and ATM
- ATCO Actions during Prolonged Loss of Communication
- CPDLC General Safety Considerations
- Takeoff without ATC Clearance
- Conflicts with Adjacent Sectors – Typical Causes and Contributors
- Operation without a Transponder or with a Dysfunctional Transponder
- Maintenance Workload
- Minimum Safe Altitude Warning (MSAW)
- Aircraft Without Transponder – Mitigations
- ATM Sector Management
- Closest Point of Approach (CPA)
- Loss of Separation at Sector Boundaries
- Loss of Separation During Weather Avoidance
- Airborne Separation Assurance Systems (ASAS)
- ATC Operations in Weather Avoidance Scenarios
- ATC Safety Nets for Remotely Piloted Aircraft
- Conflict Free Routing under Contingency
- Human Factor in Emergencies
- Integration of Very Light Jets in ATM Operations
- Workload Management (SKYclip)
- Progressive Taxi Instructions
- Risk Mitigation
- Safety Nets
- System Wide Events: Guidance for Controllers
- Workload (OGHFA BN)
- Single Person Operations in ATC
- Capacity Management
- Coordination in ATC
- Executive and Planner Controller
- Approval Request Procedure
- Tailwind
- Misidentification
- The Approach Controller






