1 / 16

A320 Strasbourg 1992 Accident Analysis

A320 Strasbourg 1992 Accident Analysis. Sophie ADENOT Carl NEHME. Accident Synopsis. January 20, 1992 Airbus A320 Air Inter F-GGED Lyon -> Strasbourg The flight crew was prepared for an landing runway 23. Why?. Selected mode for automatic pilot

cecil
Download Presentation

A320 Strasbourg 1992 Accident Analysis

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. A320 Strasbourg 1992 Accident Analysis Sophie ADENOT Carl NEHME

  2. Accident Synopsis • January 20, 1992 • Airbus A320 Air Inter F-GGED • Lyon -> Strasbourg • The flight crew was prepared for an landing runway 23

  3. Why? • Selected mode for automatic pilot • Major cause: selection of the descent rate of3300ft/min instead of descent rate of 800 ft/min (enabling a approach plan of 3.3deg)… transcripts indicates that the crew is more worried about headingthan altitude & speed

  4. 3 Main Hypotheses • The captain forgets to change the mode Vertical Speed (VS) in the Flight Control unit (FCU), and then dials 3.3 • The captain wants to stay in VS mode, but dials 3.3 automatically, as he had determined in his approach briefing • The captain changes the VS mode, but because of a problem in the FCU, this change is not taken into account

  5. FCU • VS mode: 3,3 = 3300 feet per minute • FPA mode: 3,3 = 3.3 degrees • Bi-modal dials decide which mode

  6. Accident Analysis • No mechanical failure • No sense of panic • No significant malpractice • Automation surprise • Entry to autopilot was central to events leading to disaster

  7. Task Procedural Structure Failure 1: Failure to perceive Parameter entry mode Select Parameter Entry Mode Instruction Incomplete Enter Parameter Enter Parameter Instruction Complete Select Autopilot Mode Select Autopilot Mode 4 second delay 4 second delay Execution Execution Failure 2: Failure to perceive Unsafe System State (Rapid Descent)

  8. Modal Errors • Modal errors (failure 1) involve failure to perceive current system mode • Modal errors falls under category of perceptual slips • Solutions involve prevention of such slips

  9. Failure 2 explanation • Mode error however does not explain failure 2 • Could have noticed rapid descent from • Instrument panel • Raw physical sensation of rapid descent • De Keyser [KJ] describes this as fixation error (confirmation bias) • Confirmation bias: a tendency to confirm an existing world view in the face of contradictory evidence

  10. Knowledge-Based Errors • More fundamental element exists that links the two failures • Better explanation of surprise than mode error alone • Modal errors better associated with knowledge-based errors than perceptual slips.

  11. New Model Knowledge Gap Modal Error Selectivity Confirmation bias

  12. Appendix A

  13. Experiment • Houriziand Johnson (Univ. of Bath) conducted an experiment • Looked at examples of coordination between pilot an co-pilot which has benefited from decades of research

  14. Pilot/Autopilot Task Model Recipient TRIGGERS instruction Instructor GIVES instruction Does NOT match Given Instruction Recipien REPEATS instruction Instructor CONFIRMS instruction Matches Given Instruction Recipient CONSIDERS Instruction does NOT meet recipient’s internal rules Instruction meets recipient’s internal rules Recipient GIVES Feedback Recipient GIVES Acceptance

  15. Comparison of the two task models shows: • No full repetition of the desired instruction is provided • No confirmation is required from the pilot (instruction automatically executed after 4 second delay) • No internal rule check is performed by the recipient (autopilot) • Feedback given back is both distributed and passive

  16. References • [HJ] Hourizi, R & Johnson, P Human Computer Interaction Laboratory, Computing Science Group, University of Bath • [KJ] De Keyser, V, Javaux, D, 1996. Human factors in aeronautics, design, specification & verification of interactive systems 1996 • French accident analysis: http://www.bea-fr.org/docspa/1992/f-ed920120/htm/f-ed920120.html

More Related