Situation awareness information requirements for en route air traffic control.

Endsley, Mica R.; Rodgers, Mark D. · 1994 · PsycEXTRA Dataset

DOI: 10.1037/e406512004-001

archive: archived pipeline: cataloged verified

Get this paper ↗ (DOI — opens at the source; we link to it, we don't host it)

Summary

This study addresses the critical need to define the specific situation awareness (SA) information requirements for en route air traffic control specialists (ATCSs). As air traffic volume increases, controllers must maintain a dynamic mental model of aircraft positions, trajectories, and environmental factors to ensure safety and efficiency. The research was motivated by evidence linking low SA to operational errors, with prior studies indicating that 65% of facilities involved in errors exhibited low SA, and that SA problems contributed to a significant portion of communication and radar-related incidents. The primary objective was to identify the dynamic information elements necessary for controllers to perceive, comprehend, and project the status of their environment, thereby providing a foundation for future system design, training, and evaluation. The methodology employed a goal-directed task analysis based on Endsley’s (1993) framework. The process involved three main components: reviewing the restructured CTA Job Task Taxonomy to identify major tasks and goals; conducting expert elicitation with eight experienced ATCS instructors from the FAA Academy; and analyzing videotaped simulations of ATC scenarios. Experts were interviewed individually to discuss major tasks, decisions, and the SA information needed to achieve specific subgoals. These interviews were supplemented by a review of seven simulated scenarios to validate findings and ensure completeness. The resulting data were synthesized into a goal hierarchy and a detailed task breakdown, which were then reviewed by the experts for accuracy. The analysis focused exclusively on dynamic situational information, excluding static knowledge such as procedures or rules. The results identified specific SA requirements across three hierarchical levels. Level 1 (Perception) involves identifying elements such as aircraft ID, position, altitude, speed, route, weather conditions, and equipment status. Level 2 (Comprehension) requires synthesizing these elements to understand their significance, including assessing current separation, deviations from flight plans, timing, and the impact of weather or requests on workload and safety. Level 3 (Projection) involves predicting future states, such as projected aircraft routes, potential conflicts, changes in weather intensity, and the consequences of potential route changes on separation and flow. Table 2 in the report details these requirements, highlighting that controllers must continuously monitor both primary and secondary elements, as loss of SA on secondary elements can lead to severe errors. The significance of this work lies in its application to the design and evaluation of air traffic control systems. By explicitly defining the SA information requirements, particularly at the higher levels of comprehension and projection, the study provides a basis for designing more efficient interfaces and automated assistance tools that support controller workload and enhance SA. Furthermore, the identified requirements can guide SA measurement efforts in system design evaluation, training technique assessment, and error investigation. The study underscores that while SA is built over time and is highly temporal and spatial, ensuring controllers have access to the necessary dynamic information is crucial for preventing errors and maintaining safe air traffic operations.

Key finding

The study produced a comprehensive, goal-directed taxonomy of dynamic situation awareness information requirements for en route air traffic controllers, categorized into perception, comprehension, and projection levels.

Methodology

mixed_methods

Sample size: 8

Provenance

The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via author_sweep_intake on 2026-05-28.

StageOutcomeToolModelPromptAttemptsCompleted
discover success author_sweep 2 2026-05-28
archive success unpaywall 2 2026-06-04
extract success cached 3 2026-06-10
clean success clean 1 2026-06-04
chunk success chunk 1 2026-06-04
embed success embed Qwen/Qwen3-Embedding-8B 1 2026-06-04
enrich success 1 2026-05-28
promote success 1 2026-06-04
summarize success llm qwen3.6-27b-prismaquant summ-v5 2 2026-06-10
tag success vector_similarity 15 2026-06-11
verify success 2 2026-06-10

Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.

Topics

Ranked by relevance to this paper. Hover a topic for its definition.