Abstract
We studied the transparency of automated tools used during emergency operations in commercial aviation. Transparency (operationalized as increasing levels of explanation associated with an automated tool recommendation) was manipulated to evaluate how transparent interfaces influence pilot trust of an emergency landing planning aid. We conducted a low-fidelity study in which commercial pilots interacted with simulated recommendations from NASA’s Emergency Landing Planner (ELP) that varied in their associated levels of transparency. Results indicated that trust in the ELP was influenced by the level of transparency within the human–machine interface of the ELP. Design recommendations for automated systems are discussed.
Keywords
Transparency of tools used in emergency operations can increase trust among commercial pilots interacting with an automated tool for emergency operations.
Researchers have recently relied on the construct of transparency to address, in part, the challenge of trust calibration. Broadly, transparency represents a process for establishing shared awareness and shared intent between a human and a machine (see Lyons, 2013). Real-life incidents, such as the Asiana 214 San Francisco crash and the US Airways 1549 Hudson River landing, highlight the importance of transparency of automated systems in calibrating trust (National Transportation Safety Board, 2009, 2013).
Transparency may support more optimal trust calibration by providing humans with insight into the analytical, intentional, and awareness-based parameters of an intelligent system, such as a robot (Lyons, 2013). In fact, prior studies have consistently demonstrated that added transparency supports trust development (Chen, Barnes, & Harper-Sciarini, 2011; Wang, Jamieson, & Hollands, 2009).
In this brief report, we share the results of a low-fidelity study of transparency of automated tools for commercial aviation.
Emergency Landing Technologies
The National Aeronautics and Space Administration (NASA) has developed tools to support emergency procedures in commercial aviation. Automated aids in aircraft can be useful, given that aviation is a highly complex and cognitively demanding task (Wickens, 2007); yet care is required to avoid adding further complexity to an already daunting task domain. One such automated tool is the Emergency Landing Planner (ELP; Meuleau, Plaunt, Smith, & Smith, 2008). The ELP was designed to support rapid analysis of complex situations, including damage to the aircraft, adverse weather, and status of possible landing sites to recommend a safe route and desired approach.
Recommendations from the ELP are important because the automated tool conducts extensive analysis of many elements that would be too challenging for a pilot to consider quickly during an emergency situation. For instance, when an aircraft sustains damage or experiences equipment failure, it might change the flight dynamics of the aircraft, requiring higher airspeed, gentler turns, or climb/descent limitations. Further, weather patterns can be complex, forcing pilots to rapidly choose new flight paths and landing possibilities. However, as with any automated tool, commercial pilots may not rely optimally on the ELP (Meuleau, Neukom, Plaunt, Smith, & Smith, 2011), and its use may be associated with other unintended consequences (see Parasuraman & Riley, 1997). Thus the ELP was a good domain to investigate the effects of added transparency on user trust for commercial airline pilots.
Study Method
The current study used a repeated-measures design to present the ELP interface and output in a series of vignette-based scenarios to examine the role of transparency on trust among commercial pilots (N = 12; despite the small sample size, the repeated-measures design allowed for sufficient statistical power for our analyses). Our consultation with two subject-matter experts and the engineers of the ELP revealed that an important factor that influences pilot trust in the ELP is the pilot’s understanding of the rationale behind the ELP’s recommendations. This fact motivated us to develop the following three transparency conditions (see Figure 1): control (the current baseline for the ELP output), risk-based transparency, and logic-based transparency. The control condition provided the same information that the ELP uses to make its recommendation (e.g., weather; runway characteristics, such as length; and terrain). Because this condition was the extant status of the ELP, it was considered to be an adequate baseline condition.

Examples of a diversion recommendation in the control (top), value (middle), and logic (bottom) conditions.
The second condition, risk-based transparency (referred to as the value condition), offered all the information in the control condition, but in addition, pilots were given a risk statement about the probability of success for that landing maneuver (e.g., “There is a 34% chance that you will be able to successfully complete the approach and landing under current conditions”). Note, however, that in this study, a 34% success rate does not translate into a 66% chance of crashing; it means only that the probability of landing successfully on the first attempt is 34%. This important nuance was explained to the pilots during their training with the ELP and its interface.
Finally, the logic-based transparency condition (referred to as the logic condition) included everything within the control and value conditions, but additionally, a statement was included to provide the logic behind the risk statement (e.g., runway unacceptable – the landing crosswind is too high for a safe landing). The idea was that the pilot would receive increased levels of transparency into the ELP output as he or she progressed from the control through the logic conditions. The order of the conditions was counterbalanced, and order had no impact on trust.
We developed a series of six scenarios with emergencies ranging from weather challenges at the planned airport or on the current trajectory to aircraft maintenance issues. The scenarios are summarized in Figure 2. Each scenario involved a situation in which the pilot had to divert from the current flight path and select a new airport to land the plane. The pilots were not given a time limit but were told to make the best decision as quickly as possible.

Emergency scenarios for the Emergency Landing Planner experiment. ORD = Chicago O’Hare; DEN = Denver; PHX = Phoenix; COS = Colorado Springs; SFO = San Francisco; EGE = Eagle County; SEA = Seattle; DFW = Dallas/Fort Worth; NTD = need to divert.
For each scenario, pilots were presented with a list of diversion options. The list order was randomized, and the pilots were required to consider the evaluation of each option the ELP provided. Note that outside of the current experiment, the ELP’s top selection is currently the first one listed, but the pilots in this study had no prior experience with the ELP.
Pilots were initially trained on the ELP through a brief presentation that explained its purpose and design, how to use it, and how it integrates information to make a recommendation. All the pilots were aware that the ELP was a NASA technology. Pilots were then shown a series of six vignettes using all six scenarios described earlier, within three trials. Each trial contained two vignettes with the same transparency condition. Trust was assessed following each trial. Pilot trust was measured through a seven-item scale that gauged reliance intentions on the ELP.
Example items included “I would feel comfortable relying on the recommendations of the ELP in the future”; “When the task was hard, I felt like I could depend on the ELP”; and “I would be comfortable allowing the system to make a diversion decision for me.” The seven items were rated on a Likert scale ranging from 1 (strongly disagree) to 7 (strongly agree). The pilots were also asked to rate how helpful several aspects of the ELP were. These factors included the Automatic Terminal Information Service (i.e., real-time weather information), approach information, the logic and value statements provided in the respective logic and value conditions, airport ratings, the list of diversions, individual diversion or runway information, airport facilities descriptions (e.g., emergency vehicle information), and the diversion path.
Results
The trust scale showed acceptable reliability (alpha > .85). As shown in Figure 3, trust varied by transparency condition, F(2, 22) = 4.92, p < .05. Specifically, trust was highest in the logic condition and lowest in the control condition. Contrasts revealed that trust in the control condition was significantly lower than trust in the logic condition, p < .05. Pilots rated aspects of the transparency-based interface as being helpful during the scenarios.

Trust by transparency condition.
As shown in Figure 4, pilots rated the transparency aspects of the value statement and the logic as very useful. Further, qualitative reports from the pilots indicated a strong preference for the logic condition. The pilots reported that this condition was useful for the following reasons:
“[It] gave me the most useful information at a glance.”
“I realized I missed the reasoning when I didn’t have it.”
“It helped me catch something that I would have otherwise missed.”

Helpful ratings of the Emergency Landing Planner information (1 = extremely helpful, 6 = not at all helpful).
Engineering Transparency into Complex Automation
The study demonstrated that added transparency can facilitate higher trust and utility among operators of complex systems. Establishing optimal reliance strategies is critical to human–machine interactions (Lee & See, 2004; Lyons & Stokes, 2012); thus researchers and designers should continue to seek out and understand relevant factors that influence the trust development process between humans and machines.
Although transparency, as defined by Lyons (2013), is broader than just analytic components, our results suggest that these are often critical for systems that offer recommendations for action. In particular, it suggests that these recommendations should be accompanied by the logic from which they were derived, or the pilots, who must balance the dynamic demands of aviating, navigating, communicating, and managing systems, may ignore them (Wickens, 2007). We believe that the importance of transparency will increase as technology – notably, technology with autonomous capabilities – proliferates throughout industry and government. As such proliferation occurs, it will be crucial for operators to adequately understand the logic behind autonomous systems.
Footnotes
Author(s) Note:
The author(s) of this article are U.S. government employees and created the article within the scope of their employment. As a work of the U.S. federal government, the content of the article is in the public domain.
Funding statement:
This research was funded in part by the Air Force Research Laboratory via NASA Ames Research Center.
