Quick Reference Handbook (QRH)
Quick Reference Handbook (QRH)
Description
The Quick Reference Handbook (QRH) contains all the procedures applicable for abnormal and emergency conditions in an easy-to-use format. In addition, performance data corrections are also provided for specific conditions.
The QRH is a stand-alone document. On the back cover of the QRH, the Normal Checklists are usually also provided. For aircraft not fitted with an Electronic Centralized Aircraft Monitor (ECAM) system or Engine Instruments and Crew Alerting System (EICAS) - or equivalent system the QRH is the sole reference for the management of any abnormal/emergency condition. For aircraft fitted with an ECAM/EICAS, the QRH is used in coordination with the ECAM/EICAS or as a back-up to it.
Coordinated Use of ECAM/EICAS and QRH
To understand the design objectives of the QRH, it is worth reviewing the main operating characteristics of the ECAM/EICAS. The ECAM/EICAS features three types of procedures :
- Self-contained ECAM/EICAS procedures :
- Such procedures are possible whenever the aircraft systems (even under degraded conditions) are able to :
- sense/detect a failure condition, activate the caution or warning alert light and display the relevant procedure(s),
- assess the status of pre-conditions for conditional action steps,
- acquire all the inputs required to provide a feedback on crew actions,
- confirm the status of any system(s) reconfiguration(s),
- identify inoperative systems and provide associated limitations or restrictions
- Such procedures are possible whenever the aircraft systems (even under degraded conditions) are able to :
- ECAM/EICAS procedures featuring a prompt for the continuation of the procedure in the QRH :
- Prompts are used, at any point in the procedure, when aircraft systems are no longer able to acquire all the conditions and signals required to :
- trigger the subsequent action steps,
- provide a feedback on crew actions and systems reconfiguration(s),
- determine inoperative systems and associated limitations.
- Prompts are used, at any point in the procedure, when aircraft systems are no longer able to acquire all the conditions and signals required to :
- QRH procedures :
- QRH procedures are used whenever the ECAM/EICAS is not able to detect/sense the failure or prevailing condition, e.g. :
- in case of loss of electrical power to all ECAM/EICAS components,
- for system malfunctions that are not monitored by the ECAM/EICAS (e.g., FMC failure, PFD or ND failure),
- for conditions that cannot be sensed by any aircraft sensor (e.g., flight in severe turbulence, volcanic ash encounter, bomb on board, ditching, ... ).
- QRH procedures are used whenever the ECAM/EICAS is not able to detect/sense the failure or prevailing condition, e.g. :
For aircraft not fitted with an ECAM/EICAS system, all procedures are solely QRH procedures.
For aircraft fitted with an ECAM/EICAS system, all three types of procedures may be observed, with some variations, depending on successive generations of ECAM/EICAS systems. This requires a coordinated use of the ECAM/EICAS and QRH.
Conditions permitting (e.g., during cruise), after completing an ECAM/EICAS procedure(s) - as available - and QRH procedures, the flight crew may refer to the expanded abnormal/emergency procedures contained in the AOM/FCOM for possible additional guidance.
QRH Design Features
It must be acknowledged that any abnormal/emergency procedure reflects a carefully developed and tested strategy to cope with the prevailing condition. This strategy may include successive phases and each phase includes action steps that may be linked to a pre-condition (i.e. conditional action steps).
In developing/authoring the QRH, the main challenge is to reflect the dynamic nature of abnormal / emergency procedures, in terms of :
- Overall strategy,
- Successive phases,
- Conditional action steps : ■ If .... :
- The agreement of both pilots on the ■ If .... conditions is required before performing any conditional action step,
- Feedback on crew actions,
- Conditional recovery of affected systems,
- Inoperative systems and associated performance limitations,
- Links with other QRH procedures (using a prompt).
More than in any other document, clear and unambiguous layout ergonomics is paramount in the QRH in order to avoid any :
- Omission of an action (or action group),
- Performance of an undue/irrelevant/inadvertent action.
The main ingredients of such an error-resistant layout ergonomics are :
- The correct identification of preconditions / conditional action steps, using symbols such as or ■ , or ●
- The proper indenting (lateral shift) of actions belonging to the same conditional actions group,
- Adequate spacing between the various phases of the procedure and/or between conditional actions groups.
The error-resistant QRH design should be backed-up/reinforced by adherence to operating golden rules such as the verification of each action result before proceeding to the next action step. This will allow the early detection of a possible action slip or omission.
Conclusion
The design and development of the QRH is critical to the proper response to appropriate situations. In aircraft so equipped, it is intimately linked to the ECAM/EICAS for an optimum and integrated use (with some variations depending on the successive generations of ECAM/EICAS systems).
Each QRH procedure must be seen as a strategy to address a prevailing failure condition and minimize its operational impact in terms of affected systems and/or performance. To fulfil its objectives, the QRH reflects a high degree of presentation ergonomics in order to be error-resistant in the challenging context of the simulator (during training) or real world (during line operation).
Related Articles
What Links Here (133)
- Takeoff Stall
- Aircraft Flight Manual (AFM)
- Checklists - Purpose and Use
- Compressor Stall
- Emergency and Abnormal Checklist
- Emergency or Abnormal Situation
- Engine Indicating and Crew Alerting System (EICAS)
- Nose Wheel Steering
- Operations Manual (OM)
- Sea State
- A332, en-route, North Atlantic Ocean, 2001
- DH8A, vicinity Palmerston North New Zealand, 1995
- B742, en-route, south southeast of Jakarta Indonesia, 1982
- A346, en-route, near Amsterdam Netherlands, 2005
- B733, en-route, northwest of Athens Greece, 2005
- B734, vicinity East Midlands UK, 1989
- B737, manoeuvring, west of Norwich UK 2009
- B738, vicinity Amsterdam Netherlands, 2009
- B763, en-route, North West Thailand, 1991
- DH8D, en-route, South West Norway, 2004
- CRJ1, Southampton UK, 2007
- B738, en-route, southern Austria, 2010
- B744, en-route NNW of Bangkok Thailand, 2008
- PC12 /A318, en-route north east of Toulouse France, 2010
- B763, en-route North Bay Canada, 2009
- B772, en-route Bozeman MT USA, 2008
- DH8D, Bournemouth UK, 2010
- A321, en-route, Northern Sudan, 2010
- B738, Knock Ireland, 2009
- B752, Chicago O’Hare IL USA, 2008
- B752, en-route, Central Mauritania, 2010
- AT43, Lubbock TX USA, 2009
- B772, Singapore, 2010
- B738, vicinity Faro Portugal, 2011
- DH8A, en-route SSE of Madang, Papua New Guinea, 2011
- B738, Alicante Spain, 2013
- DH8D, Aalborg Denmark, 2007
- A320, Paris Orly France, 2013
- A321, en-route, near Pamplona Spain, 2014
- B732, vicinity Islamabad Pakistan, 2012
- E145, vicinity Manchester UK, 2001
- GLF4, Le Castellet France, 2012
- SF34, Stornoway UK, 2015
- MA60, en route, west of Bima Indonesia, 2011
- A320, en route, north of Marseilles France, 2013
- DH8D, Edmonton AB Canada, 2014
- A320, Porto Portugal, 2013
- AT76, en route, west-southwest of Sydney Australia, 2014
- B752, en route, western Ireland, 2013
- B735, vicinity Kazan Russia, 2013
- A332, Karachi Pakistan, 2014
- B739, Yogyakarta Indonesia, 2015
- SW4, vicinity Red Lake ON Canada, 2013
- B738, Rostov-on-Don Russia, 2016
- B788, en-route, north of Darwin NT Australia, 2015
- MD83, vicinity Lagos Nigeria, 2012
- B738, Mildura VIC Australia, 2013
- B737, Mildura VIC Australia, 2013
- E190, en-route, southwest Vermont USA, 2016
- A333, London Heathrow UK, 2016
- B763, Warsaw Poland, 2011
- DH8B, en-route, west northwest of Port Moresby Papua New Guinea, 2017
- B734, Kabul Afghanistan, 2016
- B789, en-route, eastern Belgium, 2017
- B773, Tokyo Haneda Japan, 2016
- B738, Christchurch New Zealand, 2015
- B738, vicinity Chuuk Micronesia, 2018
- B744, en-route, southeast of Hong Kong SAR China, 2017
- A320, vicinity Delhi India, 2017
- AT76, en-route, east of Cork Ireland, 2016
- SU95, Moscow Sheremetyevo Russia, 2019
- AT72, vicinity Budapest Hungary, 2016
- SW4, Thompson MB Canada, 2017
- B734, en-route, eastern England UK, 2018
- E75S, vicinity Atlanta GA USA, 2016
- A320, vicinity Tallinn Estonia, 2018
- A333, en-route, southeast of Alice Springs Australia, 2016
- A320, Perth Australia, 2018
- A333, en-route, south of Moscow Russia, 2010
- CRJ2, en-route, south of Santander Spain, 2009
- B744, en-route, East China Sea, 2011
- RJ85, en-route, north of Tampere Finland 2009
- CL30, en-route, north west of Moscow Russia, 2010
- B773, vicinity Toronto Canada, 2012
- A319, vicinity Wuxi China, 2010
- AS3B, en-route, northern North Sea UK, 2008
- AT72, Helsinki Finland, 2012
- S92, en-route, east of St John’s Newfoundland Canada, 2009
- Engine Failure in Cruise
- Emergency Communications
- Hypoxia
- Aircraft Electrical Systems
- Aircraft Fuel Systems
- Hydraulic Systems
- Fumes Detection
- Engine Failure During Takeoff - Multi-Engine Transport Category Jet Aircraft
- Checklists and Procedures for Non-Alerted Fire/Smoke/Fume Events
- Bleed Air Leaks
- Passenger Cabin Fire
- Absence of Procedure
- Aircraft Batteries
- Autoland
- Ditching: Rotary Wing Aircraft
- Emergency Descent: Guidance for Flight Crews
- Hydraulic Problems: Guidance for Flight Crews
- Landing Gear Problems: Guidance for Flight Crews
- Low Level Wind Shear
- Standard Calls (OGHFA BN)
- Written Communication
- Electronic Centralized Aircraft Monitor (ECAM)
- AT75, vicinity Manchester UK, 2016
- AT76, en-route, near Førde Airport Norway, 2016
- A321, Charlotte NC USA, 2015
- CL60, en-route, southwest of Shahr-e-Kord Iran, 2018
- B739, Kathmandu Nepal, 2018
- IL76, Yerevan Armenia, 2019
- BE20, vicinity Gillam Canada, 2019
- A319, Helsinki Finland, 2018
- B738, en-route, Aegean Sea, 2019
- B738, East Midlands UK, 2020
- B738, vicinity Paris Orly France, 2018
- DH8C, Stephenville NL Canada, 2018
- A320, en-route, northwest Greece, 2017
- B763, Auckland New Zealand, 2019
- CL60, Calgary Canada, 2020
- C441, en-route, east southeast of Broome Australia, 2018
- B733, en-route, north of Narrandera NSW Australia, 2018
- B789, London Heathrow UK, 2020
- B738, Halifax Canada, 2020
- DH8D, en-route, east northeast of Accra Ghana, 2018
- B738, Pristina Kosovo, 2016
- B77W, London Heathrow UK, 2021
- B763, Madrid Barajas Spain, 2020






