1 / 36

When Things Go Wrong: Flight Crews and Emergencies

Human Systems Integration Division. When Things Go Wrong: Flight Crews and Emergencies. Barbara Burian, Ph.D., FRAeS NASA Ames Research Center. The Emergency and Abnormal Situations study was funded through NASA’s former Aviation Safety and Security Program. NORMAL MENU. RESETS.

alessa
Télécharger la présentation

When Things Go Wrong: Flight Crews and Emergencies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Human Systems Integration Division When Things Go Wrong:Flight Crews and Emergencies Barbara Burian, Ph.D., FRAeS NASA Ames Research Center The Emergency and Abnormal Situations study was funded through NASA’s former Aviation Safety and Security Program.

  2. NORMAL MENU RESETS NON-NORMAL MENU FIRE ENG R Fire is detected in the right engine. RIGHT AUTOTHROTTLE ARM SWITCH . . . . . . . . . . . OFF RIGHT THRUST LEVER . . . . . . . . . . . . . . . . . . . . . . CLOSE RIGHT FUEL CONTROL SWITCH . . . . . . . . . . . . . CUTOFF RIGHT ENGINE FIRE SWITCH . . . . . . . . . . . . . . . . . . PULL If FIRE ENG R message remains displayed:  1    2  • RIGHT ENGINE FIRE SWITCH . . . . . . . . . . . . . ROTATE • Rotate to the stop and hold for 1 second. 3 ITEMOVRD CHKLOVRD CHKLRESET NORMAL NOTES Emergency and Abnormal Checklists Boeing 777 ECL

  3. Human Systems Integration Division Checklists and Procedures Checklist Design Checklist Content

  4. Checklist Design Factors (Paper, Electronic, EFB) Physical Properties and Interface - size, weight, materials, integration w/displays Typography and use of Symbology - font, font size, boldface, intuitive symbology Layout, Format, Organization - visual look, arrangement, “white” space Purpose - fix, troubleshoot, manage situation, guide CRM Objective (of checklist item) - direct action, inform, assess, make decision Length and Workload - physical length, timing length, workload Nomenclature & Abbreviations - terms, labels, abbreviations Language, Grammar, & Wording - English?, verb tense, reading difficulty, clarity, orientation/perspective, directiveness Level of Detail - amount of information provided Engineering Completeness - all necessary steps included Engineering Coherence - order of steps/timing makes “sense” to aircraft Logical Coherence - order of actions makes sense to the pilot and make “sense” operationally Progression & Checklist Navigation - movement within & between checklists/manuals Access - finding correct checklist, prime real estate pgs.

  5. Context Human Systems Integration Division Checklists and Procedures Checklist Design Checklist Content

  6. Human Systems Integration Division Pack Trip • Master Caution Alert sounds • Crew Identifies that Pack has tripped off • Crew completes 4 step procedure • Flight proceeds normally

  7. ValueJet 592 - In-flight Fire Florida Everglades May 11, 1996 14:04:09 Takeoff 14:10:03 [chirping sound] “’bout to lose a bus” 14:10:15 “Got an electrical problem” 14:10:20 “We’re losing everything” 14:10:22 “We need to go back to Miami 14:10:25 “Fire, fire, fire, fire!” (from cabin) 14:10:32 “Uh, 592 needs immediate return to Miami” (to ATC) 14:13:43 CVR stops recording 14:14 ValuJet 592 disappears from radar

  8. Level of time criticality Degree of threat Degree of novelty, ambiguity, complexity Amount of increase in workload Checklists Procedures Manuals Requirements of the Emergency or Abnormal Situation

  9. SOPs Regulations Different phases of flight Weather, terrain, etc. Checklists Procedures Manuals Operational Requirements Requirements of the Emergency or Abnormal Situation

  10. Requirements of the specific malfunction History of false warnings Warning systems and alerts Appropriate level of automation Automated aircraft systems Flight protection envelopes Flight deck ergonomics Checklists Procedures Manuals Aircraft and Systems Operational Requirements Requirements of the Emergency or Abnormal Situation

  11. Checklists Procedures Manuals Manufacturer philosophies Company philosophies and policies Types of checklists available (electronic, paper) Philosophy of checklist use and functionality of electronic checklists Cost-benefit tradeoffs, e.g., diversions Updates and revisions Philosophies and Economic Constraints Aircraft and Systems Operational Requirements Requirements of the Emergency or Abnormal Situation

  12. Human Performance Capabilities Human Systems Integration Division Checklists and Procedures Checklist Design Checklist Content Context

  13. Working, long term, and prospective memory Mental computations Judgment and decision making Visual and auditory processing Attention Dealing with interruptions & distractions Situational awareness Ability to shift mental sets Motor skills Affective responses to stress Checklists Procedures Manuals Philosophies and Economic Constraints Aircraft and Systems Operational Requirements Requirements of the Emergency or Abnormal Situation Human Performance Capabilities and Limitations under High Stress and Workload

  14. Human Systems Integration Division Human Performance under Stress • Well-learned motor skills • remain robust and relatively unaffected by stress Our simulator training really paid off. This was my first engine shutdown in 20 years of flying and it felt like I had done it a thousand times before! (ASRS Report, Accession #466167)

  15. Human Systems Integration Division Human Performance under Stress • Tunneling • narrowing of human attention • restricts scanning of environmental cues • narrow focus on most salient or threatening cues • yields poor differential diagnosis of situation • Working Memory • capacity and length of time information can be held decreases • when exceeded – difficulty performing mental calculations, problem solving, making sense of disparate pieces of information, shifting mental sets (concurrent task management) • Tendency to Rush

  16. Human Systems Integration Division Human Performance under Stress We did find communication difficult and the use of oxygen masks, intercom, trying to talk to ATC was a handful. At night made it that much harder to read/accomplish checklist items. Turning cockpit lights on sooner would have helped. (ASRS Report, Accession #472755)

  17. Checklists and Procedures Checklist Design Checklist Content Context Human Performance Capabilities How Checklists are Used

  18. Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Saudi Arabian Flight 163, August 19, 1980 Crew searched unsuccessfully for several minutes for a cargo fire checklist in the Abnormal section of the QRH. The checklist they were looking for, but never found, was in the Emergency section of the QRH instead.

  19. Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Six Different Checklist Titles for the Same Condition – B737 no flap, no slat

  20. Checklists and Procedures: Context and Human Performance Considerations Example: Pilots routinely make errors in correctly recalling “memory items”

  21. Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Applying multipliers to landing distances 1.7 1.55 1.8 1.35 1.15

  22. Pull cbs Reset cbs Checklists and Procedures: Context and Human Performance Considerations Example: Information missing from checklist – Valujet 558, Jan. 7, 1996 AOM The missing information was included in the AOM expanded checklists but was never transferred to the QRH checklists.

  23. If Pack Fault due to low bleed air supply, then a bleed leak does not exist, and if WING ANTI-ICE is not required: If Pack Fault due to low bleed air supply, and if a bleed leak does not exist, and if WING ANTI-ICE is not required: Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Confusing and complex wording

  24. Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Crew confusion – FedEx 1406, September 5, 1996 FE was confused by step 5 and did not complete steps 6 and 7 Items Pertaining to Adjusting Cabin Altitude or Flight Level

  25. Start Example: Complex Navigation

  26. Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Checklist actions cause another abnormal situation to occur Accomplishing the [immediate action] item for cockpit/cabin smoke on the ground in the XXX aircraft induces the abnormal procedure of equipment overheat due to the step of the turning off left and right recirculation fans, the left recirculation fan being the primary equipment cooling on the ground. (ASRS Report, Accession #473359)

  27. Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Checklist actions not appropriate for situation Hydraulic caution light illuminated while taxiing…I completed the QRH checklist…We rolled to a stop in the grass…A very poorly written QRH emergency checklist. CALLBACK: …The checklist is for use in-flight, not on the ground. (ASRS Report, Accession #437817)

  28. Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Swissair 111, Sept. 2, 1998

  29. Time needed for completion of the two checklists: Approximately 30 minutes If smoke/fumes are not eliminated, land at nearest suitable airport Human Systems Integration Division Checklists and Procedures: Context and Human Performance Considerations Example: Swissair 111, September 2, 1998 - continued Time from first abnormal odor until Swissair 111 crashed in the ocean: 20 minutes, 40 seconds

  30. Human Systems Integration Division Human Performance and Context in Emergency and Abnormal Checklists The Good News: Emergency and Abnormal Checklists and Procedures • can be written to address the multiple contexts in which emergency and abnormal situations occur • can be designed to accommodate many human performance limitations that occur under high stress and high workload

  31. Human Systems Integration Division Addressing Context in Emergency and Abnormal Checklists To Ensure that Context is Addressed: • Make sure checklists are designed for full range of the scenarios for which they will be used (e.g., pressurization: slow leak – to – explosive/rapid decompression) • Make sure checklists are appropriate for all phases of flight and aircraft configurations for which they may be used (e.g., on ground, in-flight, throttles at idle) • Make sure checklists address relevant environmental conditions (e.g., icing) and loss of pertinent equipment that has been MEL’ed. • Conduct a realistictiming assessment of crucial checklists and procedures (length of completion). • Conduct a realistic workload assessment of checklists and procedures, especially when conducted during various phases of flight.

  32. Human Systems Integration Division Addressing Human Performance under Stress in Emergency and Abnormal Checklists To Ensure that Tunneling is Addressed: • Draw crew attention to environmental or situational cues that support diagnosis • Draw crew attention to environmental or situational cues that contraindicate diagnosis • Cues specified must be ones that flight crews are able to assess

  33. Addressing Human Performance under Stress in Emergency and Abnormal Checklists To Ensure that Working Memory Limitations are Addressed: • Provide information or resources (e.g., EFB) to diminish/eliminate memory load and need to perform mental calculations • Place remaining “memory items” on quick reference cards/QRH cover (paper and unannunciated electronic checklists) • Integrate all needed information (tables, normal checklists) with emergency and abnormal checklists – “get in, stay in” • Make sure all checklists are complete and ramification of crucial steps is provided (before the step is to be carried out) • Provide “purpose of item” and “purpose of checklist” statements • Provide information describing aircraft performance limitations • Provide information describing remaining aircraft capabilities • However, don’t go overboard with providing so much information that checklists take forever to go through/read

  34. Human Systems Integration Division Barbara Burian, Ph.D. bburian@mail.arc.nasa.gov Emergency and Abnormal Situations Study http://human-factors.arc.nasa.gov/eas

  35. The Context in Which Emergency and Abnormal Situations Occur Explosive Decompression Aloha 243 JetBlue 292 Air Canada 797 Misaligned Nosegear In-flight Fire

  36. In-flight Smoke, Fire, Fumes Integrated Checklist Courtesy of United Airlines

More Related