Taking a Closer Look at Flight Crew Handling of Complex Failures: Ten Case Studies

Research output: Chapter in Book/Conference proceedings/Edited volumeConference contributionScientificpeer-review

80 Downloads (Pure)

Abstract

Non-normal events, in particular system failures with serious operational impact are rare in flight operations. These events are not always easy to handle by flight crews. The aim of the performed study is to determine where in this process potential issues may lie. Ten incident reports are studied using a newly developed operational issue analysis framework. The framework is used to determine whether and how the current interfaces communicate the initial functional impact and functional impact delayed in time. Additionally, results from pilot interviews are presented which identified three phases of non-normal event handling: fault detection, fault management and strategic planning. Analysis of the ten cases shows that current alert systems are mainly supporting the first two phases while the strategic planning phase, requiring higher level functional information integrated into the operational context as well as failure impact later in time, is relying almost entirely on pilot knowledge and reasoning.
Original languageEnglish
Title of host publication19th International Symposium on Aviation Psychology (ISAP 2017)
Subtitle of host publicationDayton, Ohio, USA, 8-11 May 2017
EditorsP.S. Tsang, M.A. Vidulich
Pages560–565
Number of pages6
Publication statusPublished - 2017
Event19th International Symposium on Aviation Psychology - Dayton, United States
Duration: 8 May 201711 May 2017
Conference number: 19
https://isap.wright.edu/conferences/2017

Conference

Conference19th International Symposium on Aviation Psychology
Abbreviated titleISAP 2017
Country/TerritoryUnited States
CityDayton
Period8/05/1711/05/17
Internet address

Fingerprint

Dive into the research topics of 'Taking a Closer Look at Flight Crew Handling of Complex Failures: Ten Case Studies'. Together they form a unique fingerprint.

Cite this