Collocation of User Request Evaluation Tool, Traffic Management Advisor, and Controller Pilot Data Link Communications: An initial Human Factors Evaluation
archive: archived pipeline: cataloged verified
Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)
Summary
This paper presents an initial human factors evaluation of collocating three en route Air Traffic Control (ATC) automation systems: the User Request Evaluation Tool (URET), the Traffic Management Advisor (TMA), and Controller Pilot Data Link Communications (CPDLC). The study was motivated by the Federal Aviation Administration’s Free Flight Program, which deployed these systems independently but concurrently. While standalone deployment offered low-risk benefits, simultaneous use raised concerns regarding increased controller workload, decreased situational awareness, and potential interface inconsistencies. The research aimed to identify and address these human factors issues early in the development cycle to ensure safety and operational efficiency. The evaluation was conducted in two phases by a team of Human Factors Specialists and Subject Matter Experts. Phase 1 involved a “paper and pencil” engineering analysis using existing system documentation and design guidelines. Researchers mapped tasks to tools, identified information sources, and applied standard human factors principles to detect interface issues. Phase 2 utilized a modified cognitive walkthrough, where controllers familiar with one system mentally simulated using all three tools together during frequent ATC events. The analysis focused on six categories: Concept of Use, Computer-Human Interface (CHI), Information Flow, Integration/Collocation, Coordination, and Procedural Considerations. The study assessed scenarios involving both radar-side and radar associate (RA)-side controllers in various sector types. The analysis identified four primary human factors issues. First, CHI inconsistencies between URET and CPDLC, particularly regarding data block information and interaction methods, posed a risk for controller error. Second, collocating URET and CPDLC on the RA-side controller’s monitor created potential display clutter, challenging timely access to information within limited space. Third, asymmetric information availability, such as conflict alerts visible only to one controller position, necessitated increased coordination and clear role delegation. Fourth, the tools updated the National Airspace System database simultaneously with potentially conflicting information, requiring verification of data consistency. The authors concluded that additional human factors engineering is required, specifically recommending the integration of CPDLC functionality into the URET aircraft list to reduce clutter and improve efficiency. They also emphasized the need for new operational procedures to manage coordination and resolve conflicting data updates. The study served as a foundation for subsequent human-in-the-loop simulations, highlighting that while cognitive walkthroughs identified subtle integration issues, functional system testing is necessary to validate findings and address workload and situational awareness concerns.
Key finding
Collocating URET, TMA, and CPDLC creates significant human factors challenges, primarily characterized by computer-human interface inconsistencies, display clutter on the Radar Associate side, and the necessity for enhanced coordination between controller positions due to disparate information availability.
Methodology
lab_experiment
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 bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | rosap | — | — | 2 | 2026-05-23 |
| archive | success | — | — | — | 1 | 2026-05-23 |
| extract | success | cached | — | — | 2 | 2026-06-10 |
| clean | success | — | — | — | 1 | 2026-06-01 |
| chunk | success | — | — | — | 1 | 2026-06-01 |
| embed | success | — | — | — | 1 | 2026-06-02 |
| enrich | success | — | — | — | 1 | 2026-05-23 |
| promote | success | — | — | — | 1 | 2026-05-23 |
| summarize | success | llm | qwen3.6-27b-prismaquant | summ-v5 | 3 | 2026-06-10 |
| tag | success | vector_similarity | — | — | 24 | 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.
Information type
What kind of knowledge this paper contributes, grouped by family — independent of topic (what it is about) and method (how it was studied).
- Applied Guidance: design guidelines