Flight Crew Workload, Acceptability, and Performance When Using Data Comm in a High-Density Terminal Area Simulation

This document describes a collaborative FAA/NASA experiment using 22 commercial airline pilots to determine the effect of using Data Comm to issue messages during busy, terminal area operations. Four conditions were defined that span current day to future flight deck equipage: Voice communication only, Data Comm only, Data Comm with Moving Map Display, and Data Comm with Moving Map displaying taxi route. Each condition was used in an arrival and a departure scenario at Boston Logan Airport. Of particular interest was the flight crew response to D-TAXI, the use of Data Comm by Air Traffic Control (ATC) to send taxi instructions. Quantitative data was collected on subject reaction time, flight technical error, operational errors, and eye tracking information. Questionnaires collected subjective feedback on workload, situation awareness, and acceptability to the flight crew for using Data Comm in a busy terminal area. Results showed that 95% of the Data Comm messages were responded to by the flight crew within one minute and 97% of the messages within two minutes. However, post experiment debrief comments revealed almost unanimous consensus that two minutes was a reasonable expectation for crew response. Flight crews reported that Expected D-TAXI messages were useful, and employment of these messages acceptable at all altitude bands evaluated during arrival scenarios. Results also indicate that the use of Data Comm for all evaluated message types in the terminal area was acceptable during surface operations, and during arrivals at any altitude above the Final Approach Fix, in terms of response time, workload, situation awareness, and flight technical performance. The flight crew reported the use of Data Comm as implemented in this experiment as unacceptable in two instances: in clearances to cross an active runway, and D-TAXI messages between the Final Approach Fix and 80 knots during landing roll. Critical cockpit tasks and the urgency of out-the window scan made the additional head down time to respond to Data Comm messages undesirable during these events. However, most crews also stated that Data Comm messages without an accompanying audio chime and no expectation of an immediate response could be acceptable even during these events.