A 2012 Human-In-The-Loop air traffic control simulation investigated a gradual paradigm-shift in the allocation of functions between operators and automation. Air traffic controllers staffed five adjacent high-altitude en route sectors, and during the course of a two-week experiment, worked traffic under four different function allocation concepts aligned with increasingly mature NextGen operational environments. These NextGen 'timeframes' ranged from near current-day operations to nearly fully-automated control, in which the ground system's automation was responsible for detecting conflicts, issuing strategic and tactical resolutions, and alerting controllers to exceptional circumstances. This paper continues the investigations reported in previous publications. Analyses of data surrounding the conflict-resolution task serve as the context in which we investigate the interactions between controllers and the automation.
The SA5 SimulationAlthough documented in [3-9], a brief description of the study's conditions follows.
Baseline 'Current-Day' Time-FrameThe Baseline time-frame approximated a nearterm NextGen system, by adding only few differences to current-day, fielded operations. This time-frame assumed that all aircraft had Flight 5D2-2 Management System (FMS) capabilities and enhanced surveillance equipage to broadcast their position and state information.Roles and responsibilities in the Baseline time-frame were identical to those in today's operations, in which controllers were responsible for maintaining safe separation between aircraft, and did so with the available support of a flight-plan-aided conflict probe similar to the User Request Evaluation Tool (URET). Controllers issued all clearances via voice.
Minimum NextGen Time-FrameThe second time-frame, referred to as 'Minimum NextGen', added to the Baseline time-frame a limited Data Comm implementation.The Minimum NextGen time-frame assumed 25% of the aircraft were Data Comm equipped, which enabled two primary changes in handling for those 'equipped' aircraft: the automation would automatically perform the hand-offs and transfers of communication for equipped aircraft, and all equipped aircraft had the clearance to follow their FMS-computed vertical profile, unless otherwise instructed by the controller. Decision-support tool enhancements were two-fold: the conflict probe's information was integrated directly in the data block, shown as minutes-to-go until the predicted Loss of Separation (LOS); and trial-planning functions were available to help the controller craft provisional trajectory changes. The trial-planning functions benefited from instantaneous what-if feedback regarding potential conflicts, also a result of conflict-probe integration. Despite the presence of trial-planning capabilities, controllers still issued all trajectory-related clearances via voice, as Data Comm was only available for transfer of communication messages.