Analysis of routine communication in the air traffic control system
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 study addresses the lack of comprehensive understanding regarding routine air traffic control (ATC) communication, noting that previous research focused primarily on safety incidents and communication breakdowns rather than daily operations. The authors aim to describe the organization of routine controller-pilot discourse, identify the frequency and types of communication problems, and determine factors associated with these issues, such as procedural deviations and traffic density. The research is motivated by the need to improve communication efficiency and operational safety, as well as to inform potential system changes like the transition to data-link communication. The researchers conducted a field study analyzing audio recordings of routine communications from four major Terminal Radar Approach Control (TRACON) facilities: Bay, Los Angeles, Chicago, and Atlanta. Approximately 12 hours of communication were sampled from each site, covering approach and departure sectors under both high and low traffic conditions. The data were transcribed verbatim and coded using a framework derived from discourse theory and cognitive psychology. The coding scheme analyzed discourse organization (turns and transactions), speech acts (e.g., commands, acknowledgments), topics, and communication problems. The study employed a two-phase coding process: a first-pass coding of the entire sample for general dimensions and a second-pass detailed analysis of specific problem transactions. Intercoder reliability was high, with agreement rates ranging from 87% to 97%. Preliminary results from the Bay TRACON sample, which included 1,710 transactions and over 10,000 speech acts, reveal distinct patterns in routine communication. Controllers primarily issued commands and identified addressees, while pilots predominantly acknowledged instructions and identified themselves. Controllers took longer turns than pilots, particularly when communicating with unscheduled aircraft. Problem transactions, which constituted roughly 12.6% of the sample, were significantly longer and more complex than routine ones, involving more turns and speech acts. Specific findings on inaccuracies showed that incorrect readbacks occurred in 2% of acknowledgments, frequently involving headings, frequencies, and altitudes. These errors were strongly correlated with message complexity; the error rate rose from 15% for single-act messages to 64% for messages with three or more acts, suggesting working memory interference. Controllers frequently corrected these errors using stress and repetition. Additionally, topics such as ATIS, traffic, and radio frequencies were discussed more frequently during problem transactions than routine ones. The significance of this work lies in its detailed characterization of the baseline structure of ATC communication, validating the coding scheme against established ATC handbook conventions. By quantifying the costs of communication problems and identifying specific triggers like message length and procedural deviations, the study provides empirical evidence for improving communication practices. The findings suggest that minimizing message complexity and ensuring explicit grounding can enhance efficiency. Furthermore, the detailed understanding of routine discourse offers a foundation for evaluating future technological shifts in the National Airspace System, ensuring that new systems support the collaborative processes essential for safe air travel.
Key finding
Communication problems in air traffic control are associated with longer transaction durations and increased speech acts, with incorrect readbacks occurring more frequently when controllers issue multiple commands due to working memory interference.
Methodology
field_study
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-27.
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | author_sweep | — | — | 2 | 2026-05-27 |
| archive | success | canonical_url | — | — | 4 | 2026-06-06 |
| extract | success | cached | — | — | 3 | 2026-06-10 |
| clean | success | clean | — | — | 1 | 2026-06-07 |
| chunk | success | chunk | — | — | 1 | 2026-06-07 |
| embed | success | embed | Qwen/Qwen3-Embedding-8B | — | 1 | 2026-06-07 |
| enrich | skipped | — | — | — | 4 | 2026-07-02 |
| 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.