.
1.2 - Optimum Use of Automation,
.
1.5 - Use of Normal Checklists,
.
2.2 - CRM Issues in Approach and Landing Accidents.
Regulatory References
.
ICAO – Human Factors Training Manual (Doc 9683).
.
FAA – AC 60-22 – Aeronautical Decision Making.
Operations Golden Rules
Page 6
AIRBUS INDUSTRIE Getting to Grips with
Flight Operations Support Approach-and-Landing Accidents Reduction
Introduction
Standard phraseology is essential to ensure effective crew communication, particularly in today’s operating environment, which increasingly features:
.
Two-crewmember operation; and,
.
International and worldwide contexts involving crewmembers from different cultures and with different native languages.
Standard calls are intended and designed to enhance the flightcrew situational awareness (i.e., including the status and operation of aircraft systems).
Standard calls may vary among:
.
Aircraft models, based upon flightdeck design and systems interfaces; or,
.
Airlines, to suit their operating philosophy (SOPs).
Statistical Data
Insufficient horizontal or vertical situational awareness or inadequate understanding of prevailing conditions is a causal factor in more than 50 % of approach-and-landing accidents.
Use of Standard Calls
Standard calls should be defined to be alerting, to be :
.
Clearly identified by the PF or PNF; and,
.
Distinguished from other intra-cockpit or ATC communications.
Use of standard calls and acknowledgements reduces the risk of tactical (short -term) decision making errors (e.g., in selecting modes, setting targets or selecting aircraft configurations).
The importance of using standard calls increases with increasing workload or flight phase criticality.
Standard calls should be practical, concise, unambiguous and consistent with the aircraft design and operating philosophy.
Standard calls should be included in the flow sequence of company’ SOPs and should be illustrated in the Flight Patterns published in the company’ AOM or QRH (as applicable).
Command and response calls should be performed in accordance with the defined PF / PNF task sharing (i.e., task sharing for hand flying and for autopilot operation, task sharing for normal operation and for abnormal / emergency condition).
Nevertheless, if a call is omitted by one crewmember, the other crewmember should perform the call, per good crew resource management (CRM) practice.
The other crewmember should accomplish the requested command or verify the requested condition and respond accordingly.
The absence of a standard call at the appropriate time or the absence of acknowledgement may be an indication of a system or indication malfunction, or may indicate a possible incapacitation of the other crewmember.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址:Getting to Grips with Approach-and-Landing Accidents Reducti(44)