PPRuNe Forums - View Single Post - Threat and error management question
View Single Post
Old 6th Sep 2012, 13:32
  #8 (permalink)  
xxRED BARONxx
 
Join Date: Feb 2012
Location: Victoria
Posts: 42
Likes: 0
Received 0 Likes on 0 Posts
Threat Definition = "Events or errors made by others, that occur beyond the influence of the flight crew, increase operational complexity, and which must be managed to maintain margins of safety"

Error Definition = "Actions or inactions by the flight crew that LEAD to deviations from organisational or flight crew intentions or expectations"

UAS Definition = "UAS are flight crew induced aircraft position or speed deviations, misapplication of flight controls, or incorrect systems configuration, associated with a reduction in margins of safety"

The pilot taking out of date maps is a procedural error, the actions of the pilot taking out of date maps lead to the deviation from flight crew intention of not flying towards CTA. Also, all errors are threats.

Flying the aircraft towards CTA is a flight crew induced position associated with a reduction in margins of safety (UAS).

Furthermore, Flying the aircraft towards CTA would not be "an action by the flight crew that LEAD to deviations from organisational or flight crew intentions or expectations"... BECAUSE it is already a deviation from flight crew intentions, it was the wrong maps that LEAD to the deviations of flight crew intentions + expectations... Therefore T&G answer B) is NOT an error but a UAS...

Last edited by xxRED BARONxx; 6th Sep 2012 at 13:39.
xxRED BARONxx is offline