Airbus A320 Family Non-Normal Notes

Airbus A320 Family
Non-Normal Notes
Version 2.4
Airbus A320 Family Non-Normal Notes
Airbus A320 Family Non-Normal Notes: Ver-

sion 2.4
Table of Contents
Change log .............................................................................. ix
1. Change highlighting .................................................... ix
2. Changes since version 2.3 ............................................ ix
3. Changes since version 2.2.1 ........................................... x
4. Changes since version 2.2 ............................................ xii
1. Operating techniques .............................................................. 1
1.1. Rejected Takeoff ...................................................... 1
1.2. Failures during takeoff when above V1 ......................... 2
1.3. EOSID .................................................................... 4
2. Miscellaneous ....................................................................... 7
2.1. Emergency descent (memory item) ................................ 7
2.2. Windshear (memory item) ........................................... 8
2.3. Unreliable airspeed (memory item) .............................. 10
2.4. Incapacitation ......................................................... 12
2.5. Ditching ................................................................ 12
2.6. Forced landing ........................................................ 13
2.7. Evacuation ............................................................. 14
2.8. Overweight landing .................................................. 15
2.9. Engine failure in cruise ............................................ 15
2.10. Single engine circling ............................................. 16
2.11. Bomb on board ..................................................... 17
2.12. Stall recovery (memory item) .................................... 17
2.13. Computer reset ..................................................... 19
2.14. Landing distance calculations ................................... 19
2.15. Abnormal V Alpha Prot .......................................... 20
2.16. Overspeed Recovery .............................................. 20
2.17. Volcanic Ash Encounter .......................................... 21
3. Air conditioning, pressurisation and ventilation .......................... 23
3.1. Cabin overpressure .................................................. 23
3.2. Excess cabin altitude ................................................ 23
3.3. Landing Elevation Fault ............................................ 23
3.4. Pack fault .............................................................. 24
3.5. Pack overheat ......................................................... 24
3.6. Pack off ................................................................ 24
3.7. Pack regulator faults ................................................ 25
iii
3.8. ACSC single lane failure .......................................... 25

3.9. Duct overheat ......................................................... 25
3.10. Hot air fault .......................................................... 25
3.11. Trim air faults ....................................................... 26
3.12. Cabin fan faults ..................................................... 26
3.13. Lavatory and galley fan faults ................................... 26
3.14. Pressure controller faults ......................................... 27
3.15. Low diff pressure .................................................. 28
3.16. Outflow valve closed on ground ................................ 28
3.17. Open safety valve .................................................. 28
3.18. Blower fault .......................................................... 29
3.19. Extract fault .......................................................... 29
3.20. Skin valve fault ...................................................... 29
3.21. Avionics ventilation system fault ............................... 29
4. Electrical ............................................................................ 31
4.1. Emergency configuration .......................................... 31
4.2. Battery only ........................................................... 31
4.3. IDG low oil pressure/ high oil temperature .................... 32
4.4. Generator fault ........................................................ 32
4.5. Battery fault ........................................................... 32
4.6. AC Bus 1 fault ....................................................... 32
4.7. AC Bus 2 fault ....................................................... 33
4.8. AC Ess Bus fault ..................................................... 33
4.9. AC Essential Shed Bus lost ....................................... 33
4.10. DC Bus 1 fault ...................................................... 33
4.11. DC Bus 2 fault ...................................................... 34
4.12. DC Essential Bus fault ............................................ 34
4.13. DC Essential shed .................................................. 35
4.14. Loss of DC Bus 1 and DC Bus 2 .............................. 35
4.15. Generator overload ................................................ 35
4.16. Loss of TRs ......................................................... 36
4.17. Battery bus fault .................................................... 36
4.18. DC Emergency configuration ................................... 36
4.19. Static inverter fault ................................................ 37
4.20. Generator 1 line off ............................................... 38
4.21. Tripped circuit breakers .......................................... 38
5. Flight controls ..................................................................... 39
iv
5.1. Elevator faults ......................................................... 39

5.2. Stabilizer jam ......................................................... 39
5.3. Aileron faults .......................................................... 40
5.4. Spoiler faults .......................................................... 40
5.5. Rudder Jam ............................................................ 40
5.6. Flaps and/or slats fault/locked .................................... 41
5.7. SFCC faults ............................................................ 43
5.8. ELAC fault ............................................................ 43
5.9. SEC fault ............................................................... 44
5.10. FCDC faults ......................................................... 44
5.11. Direct Law ........................................................... 44
5.12. Alternate Law ....................................................... 45
5.13. Wingtip brake fault ................................................ 46
5.14. Flap attach sensor failure ........................................ 46
5.15. Flight control servo faults ........................................ 46
5.16. Speed brake disagree .............................................. 46
5.17. Speed brake fault ................................................... 46
5.18. Stiff sidestick/ rudder pedals .................................... 47
5.19. Sidestick unannunciated transducer faults ................... 47
6. Fire ................................................................................... 49
6.1. Smoke and fumes .................................................... 49
6.2. Smoke/ fumes removal ............................................. 51
6.3. Engine fire ............................................................. 52
6.4. Lithium Battery Fire ................................................ 52
7. Fuel .................................................................................. 55
7.1. Fuel leak ............................................................... 55
7.2. Fuel imbalance ....................................................... 56
7.3. Gravity fuel feeding ................................................. 56
7.4. Wing tank pump(s) low pressure ................................ 57
7.5. Center tank pumps low pressure ................................. 57
7.6. Auto feed fault ........................................................ 58
7.7. Low fuel level ........................................................ 58
7.8. Outer tank transfer valves failed closed ........................ 58
7.9. Outer tank transfer valve open out of sequence .............. 58
7.10. Cross-feed valve fault ............................................. 59
7.11. Low fuel temperature ............................................. 59
7.12. High fuel temperature ............................................. 59
v
8. Landing gear ....................................................................... 61

8.1. Loss of braking (memory item) ................................... 61
8.2. Residual braking procedure ....................................... 61
8.3. Gravity extension .................................................... 61
8.4. Asymmetric braking ................................................ 62
8.5. Landing with abnormal landing gear ............................ 62
8.6. Flight with landing gear extended ............................... 63
8.7. Gear shock absorber fault .......................................... 64
8.8. Gear not uplocked ................................................... 64
8.9. Gear not downlocked ............................................... 64
8.10. Gear doors not closed ............................................. 64
8.11. Uplock fault .......................................................... 65
8.12. LGCIU disagreement ............................................. 65
8.13. LGCIU fault ......................................................... 65
8.14. Gear not down ...................................................... 65
8.15. Park brake on ....................................................... 66
8.16. Nosewheel steering fault ......................................... 66
8.17. Antiskid nosewheel steering off ................................ 66
8.18. Antiskid nosewheel steering fault .............................. 66
8.19. Brake system fault ................................................. 67
8.20. Brakes hot ............................................................ 67
8.21. Auto brake fault .................................................... 67
8.22. Hydraulic selector valve fault ................................... 67
8.23. Failure of normal braking system .............................. 68
8.24. Failure of alternate braking system ............................ 68
8.25. Failure of normal and alternate braking systems ........... 68
8.26. Brake accumulator low pressure ................................ 68
8.27. Released brakes, normal system ................................ 68
8.28. Released brakes, alternate system .............................. 69
8.29. Brake temperature limitations requiring maintenance
action .......................................................................... 69
9. Power plant ........................................................................ 71
9.1. Dual engine failure .................................................. 71
9.2. Single Engine failure ................................................ 72
9.3. Single engine operation ............................................ 73
9.4. Engine relight in flight ............................................. 75
9.5. Engine stall ............................................................ 75
vi
9.6. Engine tailpipe fire .................................................. 76

9.7. High engine vibration ............................................... 77
9.8. Low oil pressure ..................................................... 77
9.9. High oil temperature ................................................ 77
9.10. Oil filter clog ........................................................ 78
9.11. Fuel filter clog ...................................................... 78
9.12. Uncommanded reverser pressurisation ....................... 78
9.13. Reverser unlocked in flight ...................................... 79
9.14. EIU fault .............................................................. 79
9.15. N1/N2/EGT overlimit ............................................. 80
9.16. N1/N2/EGT/FF discrepancy .................................... 80
9.17. Start valve fault ..................................................... 80
9.18. Start faults ............................................................ 80
9.19. Ignition faults ........................................................ 81
9.20. Thrust lever angle sensor faults ................................. 81
9.21. FADEC faults ....................................................... 82
10. Navigation ........................................................................ 85
10.1. EGPWS alerts (memory item) ................................... 85
10.2. TCAS warnings (memory item) ................................. 85
10.3. RNAV downgrades ................................................ 86
10.4. ADR faults ........................................................... 88
10.5. ADR disagree ....................................................... 89
10.6. RA faults ............................................................. 89
10.7. IR faults ............................................................... 89
10.8. IR disagree ........................................................... 90
10.9. IR alignment in ATT mode ...................................... 90
10.10. FM/GPS position disagree ..................................... 90
11. Auto-flight ........................................................................ 91
11.1. FAC faults ............................................................ 91
11.2. Yaw damper faults ................................................. 91
11.3. Rudder trim faults .................................................. 91
11.4. Rudder travel limiter faults ...................................... 92
11.5. FCU faults ............................................................ 92
12. Hydraulics ........................................................................ 93
12.1. Green + yellow systems low pressure ......................... 93
12.2. Blue + yellow systems low pressure ........................... 93
12.3. Green + blue systems low pressure ............................ 94
vii
12.4. Green system low pressure ...................................... 95

12.5. Yellow system low pressure ..................................... 95
12.6. Blue system low pressure ........................................ 96
12.7. Engine driven pump low pressure .............................. 96
12.8. Electric pump low pressure or overheat ...................... 96
12.9. Low reservoir air pressure ....................................... 96
12.10. Reservoir overheat ............................................... 96
12.11. Low reservoir fluid level ....................................... 97
12.12. PTU fault ........................................................... 97
12.13. RAT fault ........................................................... 97
13. Ice and rain protection ........................................................ 99
13.1. Double AOA heat fail ............................................. 99
13.2. Single pitot probe heat or static port heat fault .............. 99
13.3. Multiple pitot heat failures ...................................... 99
13.4. Single AOA or TAT heat fault ................................ 100
13.5. Probe heat computer failure ................................... 100
13.6. Window heat fault ................................................ 100
13.7. Engine anti-ice valve fault ...................................... 100
13.8. Wing anti-ice valve open when commanded closed ...... 100
13.9. Wing anti-ice valve closed when commanded open ...... 100
13.10. Wing anti-ice valves fail to close after ground self-
test ............................................................................ 101
13.11. High pressure detected when wing anti-ice turned on .. 101
14. Indicating/ Recording ........................................................ 103
14.1. Display unit failure ............................................... 103
14.2. Multiple spurious ECAM alerts ............................... 104
14.3. Flight Warning Computer failure ............................ 104
15. Pneumatic ....................................................................... 105
15.1. Dual bleed failure ................................................ 105
16. Communications .............................................................. 107
16.1. Communication failure (ICAO) .............................. 107
16.2. Communication failure (UK airspace) ...................... 108
17. Miscellaneous Tips ........................................................... 109
viii
Change log
Change log
1. Change highlighting
Changes since version 2.2 are highlighted. Change highlighting is only avail-
able in the online version. This may be found at:
https://hursts.org.uk
Changed sections have a green background, added sections have a yellow

background. Removed sections are notified in the change log.
Changes to cross references induced by Airbus re-jigging their manuals are

not highlighted.
2. Changes since version 2.3

• Cross references are updated throughout to account for February 2018
re-jigging of FCOM, FCTM, QRH and EOM-B.
• Added footnote to Section 1.1, “Rejected Takeoff” to explain that the

Feb 2018 changes to RTO procedures do not really change anything.
• Added advice for a fresh takeoff attempt following an RTO to Sec-

tion 1.1, “Rejected Takeoff”.
• Removed “engine failure” and “engine fire” calls from Section 1.2, “Fail-
ures during takeoff when above V1”. These calls have been dropped from
EOM-B. Due to EOM-B ambiguity, added advice to state the first ECAM
procedure title with a footnote explaining that this is an interpretation of
the ambiguous procedures.
• Deleted “Immediate VMC recovery” section; it has been removed from

FCOM and hasn't surfaced anywhere else.
• Improved Section 2.9, “Engine failure in cruise” to explain reasons for

required actions.
• Added requirement for FLAP 3 landing to Section 2.10, “Single engine

circling”.
ix
Change log
• Added Section 3.3, “Landing Elevation Fault”.
• Added advice about direct law go-arounds to Section 5.11, “Direct Law”.
• Added FCTM info regarding spurious AVIONICS SMOKE ECAMs to

Section 6.1, “Smoke and fumes”.
• Improved Section 8.4, “Asymmetric braking”.
• Removed section with reference to “if engines are running” from Sec-
tion 9.1, “Dual engine failure” since this is clearly nonsense. Sorry.
• Added explanation of interaction between ECAM and QRH to Sec-

tion 9.1, “Dual engine failure”.
3. Changes since version 2.2.1

• Added requirement to be above single engine acceleration altitude before
accelerating to Section 1.3, “EOSID”.
• Added description of FMGS “engine out mode” interactions to Sec-

tion 1.3, “EOSID”.
• Updated Section 2.1, “Emergency descent (memory item)” with new Air-

bus procedure.
• Added guidance on how to get out of TOGA LK to Section 2.2.1, “Re-

active”.
• Added note to Section 2.3, “Unreliable airspeed (memory item)” to warn

of flight envelope protections leading to uncontrollable aircraft and pro-
vide method for regaining control.
• Updated Section 2.5, “Ditching” with new “quick” procedure for low al-
titude events.
• Updated Section 2.6, “Forced landing” with new “quick” procedure for

low altitude events.
x
Change log
• Updated Section 2.7, “Evacuation” to indicate that cross confirmation of

master switches and fire buttons is not required following alignment of
Airbus Training Study Guide with FCTM.
• Updated Section 2.8, “Overweight landing” to clarify that autoland up to

69,000kg is only available for A319.
• Added case of TR1 and TR2 both failing to Section 4.16, “Loss of TRs”.
• Expanded Section 4.18, “DC Emergency configuration” and referenced

the expanded version in Section 4.14, “Loss of DC Bus 1 and DC Bus 2”.
• Updated Section 5.6, “Flaps and/or slats fault/locked” to clarify that the

next configuration should be selected as speed passes through VFE next
except in case of turbulence, when configuring at any speed above VLS
is acceptable.
• Added advice for dutch roll encounter to Section 5.11, “Direct Law”.
• Added that autopilot may be available to Section 5.12, “Alternate Law”.
• Added guidance of how to handle “smells” to Section 6.1, “Smoke and

fumes”.
• Improved Section 6.1, “Smoke and fumes”.
• Added footnote to Section 7.1, “Fuel leak” to address the strange logic

around suspected center tank and APU fuel line leaks.
• Added reference to new “quick” ditching and forced landing procedures

to Section 9.1, “Dual engine failure”.
• Added that cross bleed must be closed when using APU for pressurisation
to Section 9.3, “Single engine operation”.
• Removed reference to vibrations “rapidly increasing” to above adviso-

ry level from Section 9.7, “High engine vibration” – thrust should be re-
duced whenever vibrations are above advisory level, provided flight con-
ditions permit.
xi
Change log
• Updated Section 9.18, “Start faults” with new procedure for fuel leak
from the drain mast during engine start.
• Update Section 10.2, “TCAS warnings (memory item)” with the new
“TCAS blue, I have control” call.
• Expanded Section 11.5, “FCU faults” with advice not to set MDA in the
MCDU in the event of dual FCU failure.
• Updated ice accreted min speeds in Section 13.9, “Wing anti-ice valve

closed when commanded open”.
• Updated Section 15.1, “Dual bleed failure” with new QRH and ECAM
procedures.
4. Changes since version 2.2

• Added information to Section 9.14, “EIU fault”.
• Added new AP/FD TCAS mode to Section 10.2, “TCAS warnings (mem-

ory item)”.
xii
Chapter 1. Operating techniques
1.1. Rejected Takeoff
The decision to reject rests solely with CM1. This decision is communicat-
ed with the words “Stop” or “Go”. “Stop” implies that CM1 is taking control
of the aircraft. Below 100kt the RTO is relatively risk free and a decision
to stop should be made for any ECAM and most other problems. Above
100kt the RTO may be hazardous and stopping should only be considered
for loss of engine thrust, any fire warning, any uninhibited ECAM1 or any-
thing which indicates the aircraft will be unsafe or unable to fly.
If a stop is required, CM1 calls “Stop” while simultaneously bringing the

thrust levers to idle, then to max reverse. If the stop was commenced below
72kt the ground spoilers will not automatically deploy and the autobrake
will therefore not engage. Monitor automatic braking, and if there is any
doubt, apply manual braking as required. If normal braking fails, announce
“Loss of braking” and proceed with the loss of braking memory items (see
Section 8.1, “Loss of braking (memory item)”). If the reason for the stop was
an engine fire on the upwind side, consider turning the aircraft to keep the
fire away from the fuselage. If there is any chance of requiring evacuation,
bring the aircraft to a complete halt, stow the reversers, apply the parking
brake, and order “Attention, crew at stations” on the PA. If evacuation will
definitely not be required, once the aircraft’s safety is assured the RTO can
be discontinued and the runway cleared. In this case make a PA of “Cabin
crew, normal operations”.
During this initial phase, CM2 confirms reverse (“Reverse green”), con-
firms deceleration (“Decel”), cancels any audio warnings, informs ATC and
1
A change was introduced in Feb 2018 whereby five amber ECAM cautions requiring a high speed
stop are specifically listed. An exhaustive search of amber ECAM cautions that are not inhibited
between 80kt and lift off revealed only two cautions in addition to this list: ENG 1(2) THR LEVER
DISAGREE if the FADEC automatically selects idle thrust and FWS FWC 1+2 FAULT. The first
of these should theoretically never happen due to FADEC logic. The second generates a message
on the EWD but no master caution, since it is the computers that generate master cautions that have
failed. You could therefore modify this rule to: stop for any ECAM warning or caution except the
caution-like FWS FWC 1+2 FAULT.
1
announces “70 knots” when appropriate. CM2 then locates the emergency
evacuation checklist.
Once the aircraft has stopped, CM1 takes the radios and asks CM2 to carry
out any required ECAM actions. Whilst the ECAM actions are being com-
pleted, CM1 will build up a decision as to whether to evacuate. If an evac-
uation is required see Section 2.7, “Evacuation”. Otherwise order “Cabin
crew, normal operations”.
If the aircraft has come to a complete halt using autobrake MAX, the brakes
can be released by disarming the spoilers.
If, following an RTO, a new takeoff is to be attempted, reset both FDs,

set the FCU, then restart SOPs from the After Start checklist. Carefully
consider brake temperatures; temperature indications continue to climb for
some time after a significant braking event.
[EOMB 3.10, FCTM PRO.AEP.MISC]
1.2. Failures during takeoff when above V1

If an engine has lost thrust, apply rudder conventionally. At Vr rotate to-
wards an initial pitch target of 12½° at a slightly reduced rate, then target
speed V2 to V2+15kt. Bank angle should be limited to 15° when more than
3kt below manoeuvring speed for the current configuration2.
When the ground to flight mode transition is complete3, select TOGA (FLX
may be used but this tends to allow speed to decay unless pitch is reduced),
adjust and trim rudder to maintain β target and request “pull heading”. If
the EOSID follows the track of the cleared SID, NAV may be used, but this
is very rare with easyJet EOSIDs. Engage the autopilot once gear is up and
rudder is trimmed.
2
This is a conservative rule of thumb. If the FMGC has correctly identified an engine out condi-
tion, the FD/AP will automatically limit bank angle according to a less conservative algorithm.
[FCOM SYS.22.20.60.40]
3
Introducing TOGA during the ground to flight mode transition (commences as the pitch increases
through 8°, complete after 5 seconds) results in a pitch up moment at a time where the effect of
stick pitch control is not wholly predictable: the stick will need to be moved forward of neutral to
counteract the introduced pitch moment and then returned to neutral as flight mode blends in. A
slight pause before selecting TOGA results in much more normal and predictable handling.
2
Whilst below 400ft, the only failure related actions should be:
• If applicable, PM should state the title of the first displayed ECAM pro-
cedure, but should delay confirmation.4
• Cancellation of master warning or master caution when both pilots con-

firm they are aware of it.
• Heightened awareness of the possibility of missing essential normal ac-

tions, such as calling rotate or raising the gear due to the distraction of
the failure.
Once above 400ft with safe flight path assured, decide on an initial strategy.
In general, where a loss of thrust has occurred or is anticipated, the strategy
will be to fly the EOSID with a level acceleration segment (see Section 1.3,
“EOSID”). Otherwise, it will be to remain on the normal SID and fly a nor-
mal climb profile. Any deviation from the cleared SID will require ATC to
be informed as a priority, usually as part of a PAN or MAYDAY message.
In rare cases where the cleared SID requires a very early turn it may be
necessary to determine and action a strategy when below 400ft. If this is
the case, it must be thoroughly briefed.
Once the flight path strategy has been agreed and actioned, the failure can
be triaged, diagnosed and contained. If the failure has resulted in an ECAM
warning, PF initiates this phase by asking PNF to “Read ECAM”. Once the
diagnosis is agreed, PF will take the radios and request PNF to carry out
the containment actions. The standard phraseology is “My Radios, ECAM
actions”. PF taking the radios is also a good trigger to consider a Mayday
and an “Attention crew at stations”.
When applying ECAM procedures, PF is responsible for moving the thrust

levers once confirmed by PNF. PNF is responsible for everything else, but
movement of engine master switches, IR selectors and any guarded switch
must be confirmed with PF.
4
The Feb 2018 update to EOM-B removed the “engine failure” and “engine fire” calls, but leaves
the timing of the reading of the ECAM title ambiguous. The advice given here is one interpretation.
Since these calls were good for situational awareness, replacing them with a bald statement of the
first ECAM procedure title seems sensible.
3
PNF indicates high priorty tasks are completed with the phrase “Engine is
secure.” This call is not official SOP (i.e. it is not mentioned in any manual),
but has evolved to be standard in the sim since it is PF’s trigger to interrupt
ECAM and accelerate. High priority tasks are defined as:
• For engine failure, the master switch of the affected engine has been
turned off.
• For engine fire, one squib has been fired and the fire warning has extin-
guished or both squibs have been fired.
[FCTM PRO.AEP.ENG]
1.3. EOSID
Before the divergence point (the last common point between the SID and
the EOSID), if the aircraft detects a loss of thrust the EOSID will be dis-
played as a temporary flight plan. In this case the temporary flight plan
can be inserted and NAV mode used. Otherwise it will be necessary to pull
heading and manually follow either the yellow line or bring up a pre-pre-
pared secondary flight plan and follow the white line.
If beyond the divergence point, pull heading and make an immediate turn
the shortest way onto the EOSID. Airbus specifically recommends against
this in DSC.22_20.60.40, but easyJet states it as policy in EOMB 4.4.4.
Electing to fly the EOSID implies a level acceleration segment:
• Initially fly a TOGA climb at the higher of V2 or current speed, up to a

limit of V2+15kt. If a FLEX takeoff was carried out, a FLEX climb is
permissible. This climb is continued until all high priority tasks are com-
plete (see Section 1.2, “Failures during takeoff when above V1”) and the
aircraft is above single engine acceleration altitude (usually 1000ft QFE,
but may be higher if so specified by the take-off performance calcula-
tion). If the FMGS has detected the engine out condition, the automatic
mode change from SRS to CLB will be inhibited; if not, intervention with
selected modes will be required to prevent untimely acceleration.
• The next segment is a TOGA level acceleration and clean up, either to
Conf 1 and S speed if an immediate VMC return is desired or to Conf 0
4
and green dot. Again FLEX may be used if a FLEX takeoff was carried
out. Level acceleration is usually achieved by pushing V/S; if the FMGS
has detected the engine out condition, all preselected speeds entered in
the MCDU will have been deleted, so the managed target speed should
automatically move to 250kt. The phrases “Stop ECAM” and “Continue
ECAM” can be used to interrupt ECAM procedures in order to initiate
this segment.
• The final segment is a MCT climb segment to MSA, either at S speed if in

Conf 1 or at green dot speed if in Conf 0. This is usually achieved in open
climb; if the FMGS has detected the engine out condition, the managed
target speed becomes dependent on flight phase, and in this case should
automatically select green dot.
TOGA may be used for a maximum of 10 minutes.
If an EOSID is annotated as “STD”, then acceleration to green dot should

be completed prior to commencing the first turn. If “NON-STD”, the turn
takes priority.
[EOMB 4.4.4, FCOM DSC.22_20.60.40]
5
6
Chapter 2. Miscellaneous
2.1. Emergency descent (memory item)
If an emergency descent is required, the Captain should consider taking
control if not already PF. PF initiates the memory items by announcing
“Emergency Descent.”
Don oxygen masks, set them to the N position1 and establish communica-
tion.
PF then flies the emergency descent. Descent with autopilot and autothrust
engaged is preferred. The configuration is thrust idle, full speed brake and
maximum appropriate speed, taking into account possible structural dam-
age.2 Target altitude is FL100 or MORA if this is higher. If speed is low,
allow speed to increase before deploying full speedbrake to prevent acti-
vation of the angle of attack protection. Landing gear may be used below
25,000ft, but speed must be below VLO when it is extended and remain be-
low VLE. If on an airway, consider turning 90° to the left.
PM’s only memory action is to turn the seatbelt signs on.3 Initially, PM’s
main task is to ensure that PF has promptly and correctly initiated the de-
scent.
Once the memory actions are complete and the aircraft is descending, PF
should call for the Emergency Descent Checklist (“My radios, Emergency
Descent Checklist”). This will lead PF to finesse the speed and altitude
targets and inform ATC of the descent; PM to set continuous ignition on
the engines, set 7700 on the transponder and, if cabin altitude will exceed
14,000ft, deploy the cabin oxygen masks. On easyJet aircraft, the CIDS/
1
There may be insufficient oxygen to cover the entire emergency descent profile if the oxygen
masks are left set to 100%.
2
According to Airbus, structural damage may be suspected if there has been a “loud bang” or there
is a high cabin vertical speed. When limiting descent speed due to suspected structural damage, it
is IAS rather than Mach that is relevant.
3
Prior to a 2017 update from Airbus, PM would complete a fairly lengthy list of memory items at
the start of the Emergency Descent procedure. It was found that PM was more usefully employed
monitoring PF’s actions, and hence most of these memory items were removed to a read and do
checklist to be completed once descent had been initiated.
7
PRAM will automatically play a suitable PA, so it is not necessary for the
flight crew to carry out the EMER DESCENT (PA) action.
Once level, restore the aircraft to a normal configuration. When safe to do

so, advise cabin crew and passengers that it is safe to remove their masks.
To deactivate the mask microphone and switch off the oxygen flow, close
the oxygen mask stowage compartment and press the “PRESS TO RESET”
oxygen control slide.
[EOMB 3.80.2, QRH AEP.MISC, FCOM AEP.MISC, FCTM AEP.MISC]
2.2. Windshear (memory item)

2.2.1. Reactive
The windshear detection system is a function of the Flight Augmentation
Computer (FAC). It only operates during the takeoff and landing phases
with at least CONF 1 selected. In the takeoff phase, warnings are provided
from 3 seconds after lift off until 1300ft RA is achieved. In the landing
phase warnings are provided between 1300ft RA and 50ft RA. A warning is
indicated by a red “WINDSHEAR” flag on the PFD and a “WINDSHEAR,
WINDSHEAR, WINDSHEAR” aural warning.
When on the ground, windshear is only indicated by significant airspeed

variations. It is possible that these fluctuations may cause V1 to occur signif-
icantly later in the takeoff run then it should. It therefore falls to the Captain
to make an assessment of whether sufficient runway remains to reject the
takeoff, or whether getting airborne below Vr would be the better option.
If the takeoff is to be continued in windshear conditions, call “Windshear,
TOGA” and apply TOGA power. Rotate at Vr or with sufficient runway
remaining and follow SRS orders.4 SRS will maintain a minimum rate of
climb, even if airspeed must be sacrificed.
If a warning occurs when airborne, call “Windshear, TOGA”, apply TOGA

power and maintain current configuration. The autopilot can fly the escape
manoeuvre as long as αreq < αprot. If the autopilot is not engaged, follow
4
“Sufficient runway remaining” is actually Boeing advice – Airbus offers no guidance for the case
where there is insufficient runway available to stop nor to rotate at normal speeds.
8
the SRS orders on the FD. If the FD is not available, initially pitch up to
17.5°, then increase as required. Do not change configuration until out of
the windshear.
In severe windshear, it is possible that ALPHA FLOOR protection will

activate. As TOGA will already be selected, this will have no immediate
effect. Once clear of the windshear, however, TOGA LK will be active,
requiring the autothrust to be disconnected to avoid an overspeed. This is
most naturally achieved by pressing the “instinctive disconnect pb” on the
thrust levers then flying manual thrust until the situation has sufficiently
stabilised to re-engage the autothrust.
[FCOM PRO.AEP.SURV]
2.2.2. Predictive
When below 2300ft AGL, the weather radar scans a 5nm radius 60° arc
ahead of the aircraft for returns indicating potential windshear.
Alerts are categorised as advisory, caution or warning, in increasing order

of severity. Severity is determined by range, position and phase of flight.
Alerts are only provided when between 50ft and 1500ft, or on the ground
when below 100kt.
All types of alert produce an indication of windshear position on the ND,

providing the ND range is set to 10nm. A message on the ND instructs the
crew to change range to 10nm if not already set. Cautions also give an amber
“W/S AHEAD” message on both PFDs and an aural “MONITOR RADAR
DISPLAY” warning. Warnings give a red “W/S AHEAD” message on the
PFDs and either a “WINDSHEAR AHEAD, WINDSHEAR AHEAD” or
“GO AROUND, WINDSHEAR AHEAD” aural message.
If a warning alert occurs during the takeoff roll, reject the takeoff. If it oc-
curs during initial climb, call “Windshear, TOGA”, apply TOGA thrust and
follow SRS orders. Configuration may be changed as long as the windshear
is not entered.
If a warning alert occurs during approach, carry out a normal go-around.

If positive verification is made that no hazard exists, providing that the
9
reactive windshear is serviceable the crew may downgrade the warning to

a caution. If a caution alert occurs during approach, consider use of CONF
3 and increasing VAPP to a maximum of VLS+15.
[FCOM PRO.AES.SURV]
2.3. Unreliable airspeed (memory item)

Unreliable airspeed indications may result from radome damage and/or un-
serviceable probes or ports. Altitude indications may also be erroneous if
static probes are affected.
The FMGCs normally reject erroneous ADR data by isolating a single

source that has significant differences to the other two sources. It is possible
that a single remaining good source may be rejected if the other two sources
are erroneous in a sufficiently similar way. In this case, it falls to the pilots
to identify and turn off the erroneous sources to recover good data.
The first problem is recognition of a failure, since the aircraft systems may
be unable to warn of a problem. The primary method of doing this is corre-
lation of aircraft attitude and thrust to displayed performance. Correlation
of radio altimeter and GPIRS derived data (available on GPS MONITOR
page) may also aid identification. The stall warning (available in alternate
or direct law) is based on alpha probes, so will likely be valid. Other clues
may include fluctuations in readings, abnormal behaviour of the automat-
ics, high speed buffet or low aerodynamic noise.
If the aircraft flight path is in doubt, disconnect the automatics and fly the
following short term attitude and thrust settings to initiate a climb:
Condition Thrust Pitch

Below Thrust Reduction Altitude TOGA 15°
Below FL100 Climb 10°
Above FL100 Climb 5°
If configured CONF Full, select CONF 3, otherwise flap/slat configuration

should be maintained. The gear and speedbrake should be retracted. If there
10
is any doubt over the validity of altitude information, the FPV must be dis-
regarded. If altitude information is definitely good, the FPV may be used.
It is important to understand that at this stage, while the pilot has identified
that airspeed is unreliable, the aircraft systems have not. Thus flight enve-
lope protections based on airspeed data from unreliable ADRs may acti-
vate. This may lead to pitch inputs from the flight computers that cannot be
overridden with the sidesticks. In this case, immediately switch off any two
ADRs; this causes the flight computers to revert to Alternate Law with no
protections, and thus allows control of the aircraft to be regained.
Once the flight path is under control and a safe altitude is attained, the air-
craft should be transitioned into level flight. Refer to QRH AEP.NAV.USI
to extract a ballpark thrust setting, a reference attitude and a reference speed
for the current configuration, bearing in mind that an auto-retraction of the
flap may have occurred. Set the ballpark thrust setting and adjust pitch at-
titude to fly level; if barometric altitude data is considered accurate use the
VSI, otherwise fly a constant GPS altitude. The thrust should then be ad-
justed until level flight is achieved with the reference attitude. Note that in
the radome damage case, the required N1 may be as much as 5% greater
than the ballpark figure. Once stable, the speed will be equal to the refer-
ence speed.
If there is insufficient data available to fly level (e.g. GPS data unavailable
and barometric data unreliable), fly the reference attitude with the ballpark
thrust setting. This will give approximately level flight at approximately
reference speed.
With the speed now known, the ADRs can be checked to see if any are giving
accurate data. If at least one ADR is reliable, turn off the faulty ADRs. GPS
and IRS ground speeds may also be used for an approximate cross check.
If all ADRs are considered unreliable, turn off any two of them; one is kept
on to provide stall warning from the alpha probes. More recent aircraft have
backup speed/altitude scales based on AOA probes and GPS altitudes which
are activated when below FL250 by turning off the third ADR. The ALL
ADR OFF procedure in QRH AEP.NAV describes the use of these scales,
but it boils down to fly the green on the speed scale and anticipate slightly
reduced accuracy from the altitude scale. For aircraft without this function-
11
ality, tables are provided in section AEP.NAV.USI of the QRH to enable all
phases of flight to be flown using just pitch and thrust settings. Acceleration
and clean up are carried out in level flight. Flap 1 can be selected as soon
as climb thrust is selected, flap 0 once the appropriate S speed pitch atti-
tude from the table on the first page of the QRH AEP.NAV.USI procedure
is reached. Configuration for approach is also carried out in level flight,
stabilising in each configuration using the technique described above. The
approach is flown in CONF 3 at an attitude that should result in VLS+10
when flying a 3° glide. Landing distance will be increased.
[QRH AEP.NAV, FCOM PRO.AEP.NAV, FCTM PRO.AEP.NAV]
2.4. Incapacitation
Take control, using the stick priority button if necessary. Contact cabin crew
ASAP. They should strap the incapacitated pilot to his seat, move the seat
back, then recline it. If there are two cabin crew available, the body can be
moved. Medical help should be sought from passengers, and the presence
of any type rated company pilots on board ascertained.
[FCTM PRO.AEP.MISC]
2.5. Ditching
If time is short due to loss of thrust at low altitude, a “quick“ ditching proce-
dure is available on the back of the normal checklist. This procedure gives
you a suitable configuration for ditching (CONF 2, Gear up) and a table
for determining a suitable approach speed given your gross weight. It also
instructs that the APU be started, the ditching button be pushed, provides
guidance for the flare (minimise VS, attitude 11°) and provides instructions
for shutting down the engines and APU on touchdown (all masters off).
If time is available, apply the procedures in the QRH. The QRH AEP.MISC

Ditching procedure applies if the engines are running. If the engines are not
running, refer to the appropriate QRH AEP.ENG ENG DUAL FAILURE
procedure, both of which include ditching.
Preparation for ditching involves notifying ATC in order to expedite res-

cue, preparing survival equipment and securing the aircraft for impact. The
12
GPWS should be inhibited to prevent nuisance warnings. The crew oxygen

should be turned off below FL100 to prevent potentially dangerous leaks.5
The engines operative ditching configuration is gear up, config full, 11°
pitch and minimal V/S. If both engines are inoperative, use config 3 (only
slats available) and maintain at least 150kt. In strong winds, land into wind.
In lighter winds, land parallel to swell. The bleeds are all turned off and
ditching button pushed (ensure pressurisation is in auto for this to work) in
order to close all openings below the waterline and reduce water ingress.
At 2000ft, make a PA “Cabin crew, landing positions”. At 500ft, make a
PA “Brace, brace”
At touchdown, turn the engine and APU masters off. After coming to a
stop, notify ATC, push all fire buttons, discharge all agents (engine agent 2
may not be available) and evacuate the aircraft.6
[QRH AEP.MISC, QRH AEP.ENG, FCOM PRO.AEP.ENG]
2.6. Forced landing
If time is short due to loss of thrust at low altitude, a “quick“ forced landing
procedure is available on the back of the normal checklist. This procedure
gives you a suitable configuration for forced landing (CONF 2, Gear down
by gravity, spoilers armed) and a table for determining a suitable approach
speed given your gross weight. It also instructs that the APU be started,
provides guidance for the flare (minimise VS) and provides instructions for
shutting down the engines and APU on touchdown (all masters off).
If time is available, apply the procedures in the QRH. The QRH AEP.MISC

Forced Landing procedure applies if the engines are running. If the en-
gines are not running, refer to the appropriate QRH AEP.ENG ENG DUAL
FAILURE procedure, both of which include forced landing.
Preparation for forced landing involves notifying ATC in order to expedite

rescue, preparing survival equipment and securing the aircraft for impact.
5
The reasoning behind turning off the crew oxygen is an assumption on my part.
6
The “no fuel remaining” procedure does not directly call for the fire buttons to be pushed or the
agents to be discharged, but the evacuation action includes these items.
13
The GPWS should be inhibited to prevent nuisance warnings. The crew

oxygen should be turned off below FL100 to prevent potentially dangerous
leaks.5
The engines operative forced landing configuration is gear down, config

full, spoilers armed. If the engines are inoperative, use config 3 (only slats
available) and maintain at least 150kt. The ram air button is used to ensure
that the aircraft will be completely depressurised at touchdown. At 2000ft,
make a PA “Cabin crew, landing positions”. At 500ft, make a PA “Brace,
brace”
At touchdown, turn the engine and APU masters off. This will leave accu-
mulator braking only. After coming to a stop, set the parking brake, notify
ATC, push all fire buttons, discharge all agents (engine agent 2 may not be
available) and evacuate the aircraft.6
[QRH AEP.MISC, QRH AEP.ENG, FCOM PRO.AEP.ENG]
2.7. Evacuation
Evacuation should be carried out in accordance with the emergency evac-
uation checklist. The easyJet procedure is for CM1 to call for the checklist
and then send a Mayday message to ATC before commencing the checklist.
The first two items confirm the RTO actions of stopping the aircraft, setting
the parking brake and alerting the cabin crew. The next item confirms ATC
has been alerted.
The next four items prepare the aircraft for evacuation. If manual cab-
in pressure has been used, CM2 checks cabin diff is zero, and if neces-
sary manually opens the outflow valve. CM2 then shuts the engines down
with their master switches, and pushes all the fire buttons (including the
APU). Confirmation is not required before carrying out these actions.7 In
response to the next checklist item, “Agents”, CM1 decides if any extin-
guishing agents should be discharged and instructs CM2 to discharge them
as required. Engine agent 2 will not be available. Agents should only be
discharged if there are positive signs of fire.
7
The Airbus Training Study Guide was recently (mid 2017) changed to align with the FCTM.
14
Finally, order the evacuation. This is primarily done with the PA “Evacu-
ate, unfasten your seat belts and get out”, with the evacuation alarm being
triggered as a backup.
[EOMB 3.80.1, FCOM PRO.AER.MISC, FCTM PRO.AER.MISC]
2.8. Overweight landing
A landing can be made at any weight, providing sufficient landing distance
is available. In general, automatic landings are only certified up to MLW,
but the FCOM specifies that, for the A319 only, autoland is available up
to 69000kg in case of emergency. The preferred landing configuration is
CONF FULL, but lower settings may be used if required by QRH/ECAM
procedures. QRH AER.MISC.OL also specifies CONF 3 if the aircraft
weight exceeds the CONF 3 go around limit; this will only ever be a factor
for airfields with elevations above 1000ft. Packs should be turned off to
provide additional go around thrust. If planned landing configuration is less
than FULL, use 1+F for go-around.
It is possible that S speed will be higher than VFE next for CONF 2. In this
case, a speed below VFE next should be selected until CONF 2 is achieved,
then managed speed can be re-engaged.
In the final stages of the approach, reduce speed to achieve VLS at runway
threshold. Land as smoothly as possible, and apply max reverse as soon
as the main gear touches down. Maximum braking can be used after nose-
wheel touchdown. After landing, switch on the brake fans and monitor brake
temperatures carefully. If temperatures exceed 800°C, tyre deflation may
occur.
[QRH AER.MISC, FCOM PRO.AER.MISC, FCTM PRO.AER.MISC]
2.9. Engine failure in cruise

Engine out ceiling is highly dependent on weight; ISA deviation also has a
modest effect. It will generally lie between FL180 and FL350.
The first action will be to select both thrust levers to MCT so as to allow the
autothrust its full engine out range. If the N1 gauges indicate a thrust mar-
15
gin exists, then the aircraft is below engine out ceiling; descent may be ap-
propriate to increase the available thrust margin, but there is no immediate
threat. If, however, the N1 gauges indicate that the autothrust is command-
ing MCT, and the speed is still decaying, then the aircraft is above engine
out ceiling and prompt execution of a drift down procedure is required.
Drift down with autopilot engaged in OP DES is preferred. Engagement

of this vertical mode normally results in the autothrust commanding idle
thrust, which is not what is desired. Thus, having set the thrust lever to MCT,
the autothrust is disconnected. The PROG page provides a REC MAX EO
flight level to use as an altitude target. If the speed decay is modest, it may
be possible to alert ATC before initiating the descent, but in-service events
have shown that speed decay is often very rapid, requiring descent initiation
to be prioritised.
Once drift down has been initiated, a decision needs to be made about speed.
If obstacles are a concern, the lowest drift down rate and highest ceiling
are acheived at green dot. Airbus refers to drifting down at green dot as
“Obstacle strategy”. Flying at green dot reduces the chance of the FADECs
automatically relighting the failed engine as the engine will be windmilling
more slowly. Therefore, if obstacles are not a concern, M.78/300kt is flown,
a speed that will always fall within the stabilized windmill engine relight
envelope; Airbus refers to this as “Standard Strategy”.
If obstacles remain a problem, MCT and green dot speed can be maintained
to give a shallow climbing profile. Once obstacles are no longer a problem,
descend to LRC ceiling (use V/S if <500 fpm descent rate), engage the
autothrust and continue at LRC speed.
[FCTM PRO.AEP.ENG.EFDC]
2.10. Single engine circling

It may not be possible to fly level in the standard circling configuration
of CONF 3 gear down. This can be ascertained by checking the table in
QRH AEP.MISC One Engine Inoperative – Circling Approach. If affected,
plan a FLAP 3 landing and delay gear extension until level flight is no longer
required; a L/G NOT DOWN warning which will occur if circling below
16
750ft (can be silenced with the EMER CANC pb) and a TOO LOW GEAR
should be anticipated if below 500ft RA.
[QRH AEP.MISC]
2.11. Bomb on board
The primary aim is to get the aircraft on the ground and evacuated ASAP.
The secondary aim is to prevent detonation of the device. This is achieved

by preventing further increases in cabin altitude through the use of manual
pressure control and by avoiding sharp manoeuvres and turbulence.
The tertiary aim is to minimise the effect of any explosion. This is achieved
by reducing the diff to 1 psi. The method is to set cabin vertical speed to
zero using manual pressurisation control, then descend to an altitude 2500ft
above cabin altitude. As further descent is required, cabin vertical speed
should be adjusted to maintain the 1 psi diff for as long as possible. Auto-
matic pressure control is then reinstated on approach. Low speeds reduce
the damage from an explosion but increase the risk of a timed explosion
occurring whilst airborne; a compromise needs to be found. The aircraft
should be configured for landing as early as possible to avoid an explosion
damaging landing systems.
In the cabin, procedures are laid down for assessing the risks of moving the
device and for moving the device to the LRBL at door 2R.
[QRH AER.80, FCOM PRO.AER.MISC]
2.12. Stall recovery (memory item)

Aerofoil stall is always and only an angle of attack issue. It is not possible to
directly prove an unstalled condition from attitude and airspeed data. The
flight recorders from the December 2014 Air Asia accident recorded an
angle of attack of 40 degrees (i.e. around 25 degrees greater than critical
angle) with both pitch and roll zero and speeds up to 160kt. Importantly, it
is perfectly possible to be fully stalled in the emergency configurations de-
scribed in Section 2.3, “Unreliable airspeed (memory item)”. Identification
17
of a fully stalled condition is thus largely dependent on identifying a high

and uncontrollable descent rate that does not correlate with normal flight
path expectations for the attitude and thrust applied.
To recover from a fully stalled condition, the angle of attack of the aerofoils
must be reduced to below critical. The generic stall recovery is therefore
simply to pitch the nose down sufficiently to break the stall and level the
wings. In normal operations, the velocity vector of the aircraft is around 3°
below the centreline of the aircraft (i.e. an attitude of around 3° is required
to fly level). In a stalled condition, the velocity vector may be 40° or more
below the centreline of the aircraft. Thus the amount of pitch down required
to recover a fully stalled aircraft can be 30° or more.
The aircraft's thrust vector helps to accelerate the aircraft during the recov-
ery, and increasing speed along the aircraft's centreline acts to reduce the
stalled angle of attack. Thus, while thrust is not a primary means of recov-
ery, it does help. Unfortunately, Airbus have determined that due to the
pitch couple associated with underslung engines, there may be insufficient
longitudinal control authority to pitch the aircraft sufficiently to recover
from a stall if TOGA is selected. It may therefore be necessary to initially
reduce thrust to allow the primary recovery technique to be applied; this is
extremely counterintuitive.
In the two recent Airbus accidents involving stalls, the lack of physical cross
coupling of sidesticks was a major factor. If one pilot elects to hold full
back sidestick, the aircraft cannot be recovered by the other pilot unless the
takeover pushbutton is used. With all the alarms, it is easy to miss “Dual
Input”.
Once there are no longer any indications of the stall, smoothly recover from
the dive, adjust thrust, check speedbrakes retracted and if appropriate (clean
and below 20,000ft) deploy the slats by selecting flaps 1. The load factor
associated with an overly aggressive pull out can induce a secondary stall; on
the flip side, once reattachment of the airflow occurs, drag rapidly dimin-
ishes and exceedance of high speed airframe limitations becomes a threat.
If a stall warner sounds on takeoff it is likely to be spurious since you are

almost certainly in normal law. The procedure in this case is essentially to
18
initially assume unreliable airspeed and fly TOGA, 15°, wings level until it
can be confirmed that the warning is spurious.
A stall warning may occur at high altitude to indicate that the aircraft is
reaching αbuffet. In this case simply reduce the back pressure on the side-
stick and/or reduce bank angle.
[FCOM PRO.AER.MISC]
2.13. Computer reset
Abnormal computer behaviour can often be stopped by interrupting the
power supply of the affected computer. This can be done either with cock-
pit controls or with circuit breakers. The general procedure is to inter-
rupt the power supply, wait 3 seconds (5 seconds if a C/B was used), re-
store the power, then wait another three seconds for the reset to complete.
QRH AER.SYSTEM RESET details the specific procedures for a variety
of systems.
On the ground, almost all computers can be reset. MOC can usually supply
a reset procedure if nothing applicable is available in the QRH. The excep-
tions are the ECU and EIU while the associated engine is running and the
BSCU when the aircraft is not stopped.
In flight, only the computers listed in the QRH should be considered for
reset.
[QRH AER.SYSTEM RESET]
2.14. Landing distance calculations

Many failures result in a longer than normal landing distance. The QRH
inflight performance section has tables for calculating VAPP and Refer-
ence Landing Distances for single failures. These reflect the performance
achievable in a typical operational landing without margin. easyJet requires
a factor of 1.15 to be applied to these distances.
The EFB module provides both factored and unfactored landing distances,
and also can calculate for multiple failures.
19
The safety factor may be disregarded in exceptional circumstances.

[QRH IFP, FCOM PER.LDG, EOMB 4.14.2]
2.15. Abnormal V Alpha Prot

If two or more angle of attack vanes become blocked at the same angle
during climb, alpha floor protection will be activated once a Mach num-
ber is reached where the angle of attack at which the vanes were blocked
becomes indicitive of an incipient stall condition. Since the flight comput-
er's attempts to reduce angle of attack will not be registered by the blocked
vanes, a continuous nose down pitch rate which cannot be stopped with side-
stick inputs will result.
Indications of the incipient condition are available from the Alpha Prot and
Alpha max strips. If the Alpha Max strip (solid red) completely hides the
Alpha Prot strip (black and amber) or the Alpha Prot strip moves rapidly
by more than 30kt during flight manoeuvres with AP on and speed brakes
retracted, blocked angle of attack vanes should be suspected.
The solution is to force the flight computers into Alternate Law where the
protection does not apply. This is most conventiently done by turning off any
two ADRs. Once in Alternate Law, the stall warning strip (red and black)
becomes available. Since this may be receiving data from a blocked angle
of attack vane, erroneous presentation is possible.
[OEBPROC-48]
2.16. Overspeed Recovery
In general the response to an overspeed should be to deploy the speedbrake
and monitor the thrust reduction actioned by the autothrust. Disconnection
of the autopilot will not normally be required. If autothrust is not in use, the
thrust levers will need to be manually retarded.
It is possible that the autopilot will automatically disengage and high speed
protection will activate, resulting in an automatic pitch up. In this case,
smoothly adjust pitch attitude as required.
[FCTM PRO.AER.MISC]
20
2.17. Volcanic Ash Encounter

Volcanic ash clouds are usually extensive, so the quickest exit will be
acheived by a 180° turn.
Air quality may be affected, so crew oxygen masks should be donned with
100% oxygen to exclude fumes. Passenger oxygen may also need to be de-
ployed.
Be prepared to carry out the unreliable speed procedure as airspeed indica-

tions may be compromised.
Disconnect the autothrust to prevent thrust variations. To minimise the im-

pact on the engines, if conditions permit thrust should be reduced. Turn on
all anti-ice and set pack flow to high in order to increase bleed demand and
thus increase stall margin. Wing anti-ice should be turned off before restart
in case of double engine flameout.
If engine EGT limits are exceeded, consider precautionary engine shut-

down with restart once clear of volcanic ash. Engine acceleration may be
very slow during restart. Since compressor and turbine blades may have been
eroded, avoid sudden thrust changes.
Damage to the windshield may necessitate an autoland or landing with a

sliding window open.
[QRH AEP.MISC, FCOM PRO.AEP.MISC, FCTM PRO.AEP.MISC]
21
22
Chapter 3. Air conditioning, pressurisation and ventilation
Chapter 3. Air conditioning, pressurisation

and ventilation
3.1. Cabin overpressure
There is no ECAM in the case of total loss of pressure control leading to
an overpressure, so apply the QRH procedure. The basic procedure is to
reduce air inflow by turning off one of the packs and put the avionics ven-
tilation system in its smoke removal configuration so that it dumps cabin
air overboard. The ΔP is monitored, and the remaining pack is turned off
if it exceeds 9 psi. 10 minutes before landing, both packs are turned off
and remain off, and the avionics ventilation is returned to its normal con-
figuration.
[QRH AEP.CAB PR, FCOM PRO.AEP.CAB PR]
3.2. Excess cabin altitude

An ECAM warning of excess (>9550ft) cabin altitude should be relied up-
on, even if not backed up by other indications.
The initial response should be to protect yourself by getting an oxygen mask

on. Initiate a descent; if above FL160, this should be according to Sec-
tion 2.1, “Emergency descent (memory item)”. Once the descent is estab-
lished and all relevant checklists are complete, check the position of the
outflow valve and, if it is not fully closed, use manual control to close it.
[CAB PR EXCESS CAB ALT, FCOM PRO.AEP.CAB PR]
3.3. Landing Elevation Fault

If the landing field elevation is not available from the FMGS, the landing
elevation must be manually selected. This is done by pulling out and turning
the LDG ELEV knob. The scale on the knob is only a rough indication; use
the LDG ELEV displayed on either the CRUISE page or the CAB PRESS
SD page instead.
[CAB PR LDG ELEV FAULT, FCOM PRO.AEP.CAB PR]
23
3.4. Pack fault
The PACK FAULT ECAM indicates that the pack valve position disagrees
with the selected position or that the pack valve is closed. The affected
pack should be turned off. A possible reason for this failure is loss of both
channels of an Air Conditioning System Controller (ACSC). If this occurs,
the associated hot air trimming will also be lost (cockpit for ACSC 1, cabin
for ACSC 2).
If there are simultaneous faults with both packs, ram air must be used. This
will necessitate depressurisation of the aircraft, so a descent to FL100 (or
MEA if higher) is required. If a PACK button FAULT light subsequently
extinguishes, an attempt should be made to reinstate that pack.
[AIR PACK 1(2)(1+2) FAULT, FCOM PRO.AEP.AIR]
3.5. Pack overheat
The associated pack flow control valve closes automatically in the event of
a pack overheating (outlet temp > 260°C or outlet temp > 230°C four times
in one flight). The remaining pack will automatically go to high flow, and is
capable of supplying all of the air conditioning requirement. This system’s
automatic response is backed up by turning off the pack. The FAULT light
in the PACK button remains illuminated whilst the overheat condition ex-
ists. The pack can be turned back on once it has cooled.
[AIR PACK 1(2) OVHT, FCOM PRO.AEP.AIR]
3.6. Pack off
A warning is generated if a functional pack is selected off in a phase of flight
when it would be expected to be on. This is usually the result of neglecting
to re-instate the packs after a packs off takeoff. Unless there is a reason not
to, turn the affected pack(s) on.
[AIR PACK 1(2) OFF, FCOM PRO.AEP.AIR]
24
3.7. Pack regulator faults

A regulator fault is defined as a failure of one of four devices: the bypass
valve, the ram air inlet, the compressor outlet temperature sensor or the
flow control valve. The ECAM bleed page can be used to determine which
device is at fault.
Regardless of the device at fault, the ramification is the same; the pack will
continue to operate but there may be a degradation in temperature regula-
tion. If temperatures become uncomfortable, consideration should be given
to turning off the affected pack.
[AIR PACK 1(2) REGUL FAULT, FCOM PRO.AEP.AIR]
3.8. ACSC single lane failure

Each ACSC has two fully redundant “lanes”, so loss of a single “lane” results
in loss of redundancy only.
[AIR COND CTL 1(2) A(B) FAULT, FCOM PRO.AEP.AIR]
3.9. Duct overheat
A duct overheat is defined as a duct reaching 88°C or a duct reaching 80°C
four times in one flight. If this occurs, the hot air pressure regulating valve
and trim air valves close automatically and the FAULT light illuminates in
the HOT AIR button. This light will extinguish when the temperature drops
to 70°C.
Once the duct has cooled, an attempt can be made to recover the hot air
system by cycling the HOT AIR button. If recovery is not possible, basic
temperature regulation will continue to be provided by the packs.
[ COND FWD CAB/AFT CAB/CKPT DUCT OVHT, FCOM PRO.AEP.COND]
3.10. Hot air fault

If the hot air pressure regulating valve is not in its commanded position, the
effects will depend on its actual position. If it is closed when commanded
open, the packs will provide basic temperature regulation. More serious is
25
if it has been commanded closed in response to a duct overheat and it fails

to close. Manual control may be effective, but if it is not the only option is
to turn off both packs and proceed as per Section 3.4, “Pack fault”.
[COND HOT AIR FAULT, FCOM PRO.AEP.COND]
3.11. Trim air faults

Either a fault with one of the trim air valves or an overpressure downstream
of the hot air valve. An associated message indicates which condition exists.
Failure of a trim valve leads to loss of optimised temperature regulation for

the corresponding zone; basic temperature regulation is still available.
The TRIM AIR HIGH PR message may be disregarded if triggered when

all the trim air valves are closed. This occurs during the first 30 seconds
after the packs are selected on and in flight if all zone heating demands are
fulfilled.1
[COND TRIM AIR SYS FAULT, FCOM PRO.AEP.COND]
3.12. Cabin fan faults

If both cabin fans fail, their flow should be replaced by increasing the pack
flow to HI.
[COND L + R CAB FAN FAULT, FCOM PRO.AEP.COND]
3.13. Lavatory and galley fan faults

The cabin zone temperature sensors are normally ventilated by air extract-
ed by these fans. Loss of the fans therefore leads to loss of accurate zone
temperature indication.
On older aircraft, temperature control reverts to maintenance of a fixed

cabin zone inlet duct temperature of 15°C.
1
The FCOM is not very informative regarding response to overpressure when this does not apply.
However the MEL operating procedures for dispatch with this condition indicate that turning the
HOT AIR pb-sw off is probably a good idea.
26
On newer aircraft the temperature controls for the cabin revert to control-
ling temperature in the ducts. If ACSC 2 has also failed, the duct tempera-
tures are maintained at the same level as the cockpit duct temperature, and
may therefore be controlled with the cockpit temperature selector.
[COND LAV + GALLEY FAN FAULT, FCOM PRO.AEP.COND]
3.14. Pressure controller faults

Loss of a single cabin pressure controller leads to loss of redundancy only.
If both pressure controllers are lost, use manual control. The outflow valve
reacts slowly in manual mode, and it may be 10 seconds before positive
control of the outflow valve can be verified. It may also react too slowly to
prevent a temporary depressurisation.
Manual pressurisation control is activated by pressing the MODE SEL but-

ton. This allows the MAN V/S CTL toggle switch to directly control the
outflow valve. Moving the toggle to DN closes the outflow valve causing the
cabin altitude to descend, whilst moving the toggle to UP opens the outflow
valve causing the cabin altitude to climb. The target climb and descent rates
are 500fpm and 300fpm, these being displayed on the status page for easy
reference.
A table of FL versus ‘CAB ALT TGT’ is also provided on the status page; no
guidance is given for the interpretation of this table. The final action of the
procedure is to fully open the outflow valve when 2500ft QFE in preparation
for an unpressurised landing, so to avoid large pressurisation changes during
this action, the final cabin altitude target needs to be aerodrome elevation
plus 2500ft . This gives an indication of how ‘CAB ALT TGT’ should be
interpreted: it is the lowest cabin altitude that results in a safe ΔP at a given
FL. A cabin altitude greater then ‘CAB ALT TGT’ is always acceptable2
and, moreover, for the final stages of the approach, it is necessary. The
method is therefore to avoid cabin altitudes below ‘CAB ALT TGT’ for your
actual FL while ensuring that a cabin altitude of aerodrome elevation plus
2500ft will be achieved by the time you need to fully open the outflow valve.
2
A reasonable maximum cabin altitude is 8800ft, which is when the CAB ALTITUDE advisory
triggers.
27
Ensure cabin diff pressure is zero before attempting to open the doors.
[CAB PR SYS 1(2)(1+2) FAULT, FCOM PRO.AEP.CAB PR]
3.15. Low diff pressure

High rates of descent may lead to the aircraft descending through the cab-
in altitude when more than 3000ft above the landing altitude. An ECAM
warning indicates that this situation is projected to occur within the next
1½ minutes. If the rate of descent of the aircraft is not reduced, the pres-
sure controllers will have to resort to high rates of change of cabin altitude,
which may cause passenger discomfort. The aircraft’s vertical speed should
be reduced unless there is a pressing reason not to.
[CAB PR LO DIFF PR, FCOM PRO.AEP.CAB PR]
3.16. Outflow valve closed on ground

If the outflow valve fails to automatically open on the ground, manual con-
trol should be attempted. If that doesn’t work, depressurise the aircraft by
turning off both packs.
[CAB PR OFV NOT OPEN, FCOM PRO.AEP.CAB PR]
3.17. Open safety valve

There are safety valves for both cabin overpressure and negative differential
pressure; the associated ECAM message does not distinguish between the
two.
If diff pressure is above 8psi, it is the overpressure valve that has opened.
Attempt manual pressurisation control and if that fails, reduce aircraft al-
titude.
If diff pressure is below zero, it is the negative differential valve. Reduce

aircraft vertical speed or expect high cabin rates.
[CAB PR SAFETY VALVE OPEN, FCOM PRO.AEP.CAB PR]
28
3.18. Blower fault
Defined as low blowing pressure or duct overheat. Unless there is a DC
ESS Bus fault, the blower fan should be set to OVRD. This puts the avion-
ics ventilation into closed configuration and adds cooling air from the air
conditioning system.
[VENT BLOWER FAULT, FCOM PRO.AEP.VENT]
3.19. Extract fault
Defined as low extract pressure. The extract fan should be put in OVRD.
This puts the avionics ventilation into closed configuration and adds cooling
air from the air conditioning system.
[VENT EXTRACT FAULT, FCOM PRO.AEP.VENT]
3.20. Skin valve fault

Defined as one of three faults: the inlet valve is not fully closed in flight, the
extract valve is fully open in flight or the extract valve did not automatically
close on application of take-off power. The ECAM Cab Press page will
differentiate.
If the fault is with the inlet valve, no action is required since it incorporates
a non-return valve.
If the extract valve is affected, the system should be put into smoke config-
uration; this sends additional close signals to the extract valve. If this fails,
the aircraft must be depressurised.
[VENT SKIN VALVE FAULT, FCOM PRO.AEP.VENT]
3.21. Avionics ventilation system fault

Defined as either a valve not in its commanded position or the Avionics
Equipment Ventilation Controller (AEVC) being either unpowered or fail-
ing its power-up test. The system will automatically default to a safe con-
figuration similar to smoke configuration. No crew action is required.
[VENT AVNCS SYS FAULT, FCOM PRO.AEP.VENT]
29
30
Chapter 4. Electrical
4.1. Emergency configuration
Attempt to restore normal power by recycling the main generators. If that
fails, try again after splitting the systems with the BUS TIE button.
If normal power cannot be restored, ensure that the emergency generator is

on line (deploy the RAT manually if required) and maintain speed >140kt to
avoid RAT stall. Cycling FAC 1 will recover rudder trim. Once 45 seconds
have elapsed and when below FL250, the APU can be started.
So much equipment is lost in the emergency configuration that

QRH AEP.ELEC provides a table of surviving equipment. Notable losses
are all the fuel pumps (so ignition on, avoid negative G, center tank fuel is
unusable), the anti-skid and three fifths of the spoilers. Landing speeds and
distances are increased significantly.
QRH AEP.ELEC also provides a paper summary which should be applied

once ECAM actions are complete.
[ELEC EMER CONFIG, QRH AEP.ELEC, FCOM PRO.AEP.ELEC]
4.2. Battery only
Power is available for approximately 30 minutes.1 QRH AEP.ELEC pro-
vides details of remaining equipment. This is very similar to the emergency
electrical configuration (see Section 4.1, “Emergency configuration”) with
the additional loss of FAC1 and FMGC1. An attempt should be made to
bring the emergency generator on line by ensuring speed is >140kt and de-
ploying the RAT with the EMER ELEC PWR MAN ON button.
[ELEC ESS BUSES ON BAT, QRH AEP.ELEC, FCOM PRO.AEP.ELEC]
1
This information was part of Airbus CBT training. There is no figure available in the FCOM.
31
4.3. IDG low oil pressure/ high oil temperature

The IDG should be disconnected. Assuming the associated engine is run-
ning, press the IDG button until the GEN FAULT light comes on. Do not
press the button for more than 3 seconds.
The APU generator should be used if available.

[ELEC IDG 1(2) OIL LO PR/OVHT, FCOM PRO.AEP.ELEC]
4.4. Generator fault
Try to reset the generator by turning it off, then after a short pause, turning
it on again. If unsuccessful, turn it back off.
If an engine driven generator cannot be recovered, the APU generator

should be used if available.
Single generator operation leads to shedding of the galley. Loss of an engine

driven generator leads to loss of CAT III DUAL capability.
[ELEC(APU) GEN (1)(2) FAULT, FCOM PRO.AEP.ELEC]
4.5. Battery fault
The affected battery contactor opens automatically. APU battery start is
unavailable with a single battery.
[ELEC BAT 1(2) FAULT, FCOM PRO.AEP.ELEC]
4.6. AC Bus 1 fault

Some or all of the equipment on AC bus 1 becomes unavailable, includ-
ing TR1. DC Bus 2 is powered from DC Bus 1 via the battery bus. Power
must be re-routed to the Essential AC bus via AC bus 2. This is automatic
on some aircraft. Manual re-routing is achieved with the AC ESS FEED
button. Once Essential AC is powered, the Essential TR powers the DC
Essential bus.
Notable lost equipment includes the blue hydraulic system and associated
services (including spoiler 3), radio altimeter 1 (and hence Cat III capabil-
32
ity), half the fuel pumps, the nose wheel steering, the avionics blower fan
and p1 windshield heat.
[ELEC AC BUS 1 FAULT, FCOM PRO.AEP.ELEC]
4.7. AC Bus 2 fault

Some or all of the equipment on AC bus 2 becomes unavailable, including
TR2. DC bus 2 is powered from DC bus 1 via the battery bus. The majority
of this equipment has a redundant backup, the loss of the FO’s PFD and
ND and a downgrade to Cat I being the major issue. Landing distances are
unchanged.
[ELEC AC BUS 2 FAULT, FCOM PRO.AEP.ELEC]
4.8. AC Ess Bus fault

It may be possible to recover the bus by transferring its power source to
AC BUS 2 with the AC ESS FEED button. If this is unsuccessful, some or
all of the equipment on the AC ESS bus will be lost. The majority of this
equipment has a redundant backup, with the loss of the Captain’s PFD and
ND and a downgrade to Cat I being the major issues. Landing distances
are unchanged.
[ELEC AC ESS BUS FAULT, FCOM PRO.AEP.ELEC]
4.9. AC Essential Shed Bus lost

Some or all of the equipment on the AC ESS SHED bus is lost. The ma-
jor issue is the loss of the passenger oxygen masks. Landing distances are
unchanged.
[ELEC AC ESS BUS SHED, FCOM PRO.AEP.ELEC]
4.10. DC Bus 1 fault

Some or all of the equipment on DC Bus 1 is lost. Most of the equipment
loss causes loss of redundancy only. Landing distances are unchanged.
[ELEC DC BUS 1 FAULT, FCOM PRO.AEP.ELEC]
33
4.11. DC Bus 2 fault

Some or all of the equipment on DC Bus 2 is lost. The F/O’s static probe
sensor is lost, so ADR3 should be selected on the F/O’s side. FCU2 is lost,
so check that the baro ref on the FCU and PFD agree. Landing distance
increases by up to 35% due to the loss of 3 ground spoilers per side and one
reverser. Autobrake is also unavailable. Due to the loss of SFCC2, the slats
and flaps will be slow and the engines will remain in approach idle. FAC2
is lost, so the characteristic speeds on both PFDs are provided by FAC1. F/
O window heat, wipers and rain repellent are lost.
The other lost systems either have redundant backups or are non-essential.
It should be noted that the only flight computers remaining are ELAC 1,
SEC 1 and FAC 1.
[ELEC DC BUS 2 FAULT, FCOM PRO.AEP.ELEC]
4.12. DC Essential Bus fault

The major headache associated with DC Essential Bus failure is signifi-
cant loss of communications systems. This is exacerbated by a design flaw
which, at time of writing, affects MSNs 2037–2402 and MSNs 2471–3122.
By design, ACP1 and ACP2 are lost, along with VHF1. This allows two-
way communication to be recovered by one pilot using ACP3 (selected via
the AUDIO SWTG rotary selector) with VHF2 or VHF3. Since speaker 1
is also lost, having P2 handle the radios with speaker 2 at high volume is
the only method of both pilots having awareness of ATC communications.
On the MSNs detailed above, however, the audio cards connecting cock-
pit mikes and headsets are all powered from the DC Essential Bus. It may
be possible to receive transmissions with a combination of VHF2/3, ACP3
on FO and speaker 2 on, but transmission is limited to morse code on the
transmit switch2.
FCU1 is lost, so the baro refs should be checked. The GPWS is lost and
should be turned off.
2
I am only inferring this solution from the list of equipment lost; there is no specific documentation
to indicate that it will work.
34
Landing distances are increased due to the loss of reverser 2 and the loss of
the blue hydraulic system (and hence spoiler 3). Wing anti-ice is also lost,
so landing distances will also increase significantly if ice is accreted and
increased approach speeds are required.
Slats and flaps are slow due to the loss of SFCC1. This also leads to the
engines reverting to approach idle.
Landing capability is Cat 2 due to the loss of the auto-thrust. The ECAM
status page incorrectly reports Cat 3 single.
The FCOM lists additional systems beyond those listed on the STATUS
page that are lost with DC Essential Bus failure. Of note among these is loss
of HP fuel shutoff valves. This requires that the engines are shut down with
the Engine Fire pushbutton switches.
[ELEC DC ESS BUS FAULT, FCOM PRO.AEP.ELEC]
4.13. DC Essential shed

The only major issue is the loss of wing anti-ice. Therefore, avoid icing
conditions, and apply landing distance procedure if ice accretes.
[ELEC DC ESS BUS SHED, FCOM PRO.AEP.ELEC]
4.14. Loss of DC Bus 1 and DC Bus 2

Some or all of the systems supplied by DC Bus 1 and DC Bus 2 are lost.
The implications are the same as for Section 4.18, “DC Emergency config-
uration” except that the RAT will not need to be deployed since ESS TR
will be supplied from AC 1 instead of the emergency generator.
[ELEC DC BUS 1+2 FAULT, FCOM PRO.AEP.ELEC]
4.15. Generator overload
Shed some load by switching off the galleys.
[ELEC GEN 1(2) OVERLOAD, ELEC APU GEN OVERLOAD, FCOM-
PRO.AEP.ELEC]
35
4.16. Loss of TRs
No systems are lost as a result of failure of a single TR. If the fault is with
TR1 or TR2, DC ESS will be supplied by the ESS TR via AC ESS; in this
case only Cat 3 single will be available.
If TR1 and TR2 are both lost then DC Bus 1, DC Bus 2 and the DC Battery
Bus will also be lost. DC ESS will remain powered by the ESS TR. The
FCOM is not very forthcoming regarding this failure; there is only a de-
scription in the DSC section and nothing specific in the PRO section. The
situation is, however, very similar to the “ECAM complete” phase of Sec-
tion 4.18, “DC Emergency configuration”; the only difference is that AC 1
rather than the emergency generator is providing the power to the ESS TR,
and hence you don't need to worry about RAT deployment or RAT stall.
[ELEC TR 1(2), ELEC ESS TR FAULT, FCOM PRO.AEP.ELEC]
4.17. Battery bus fault

Some or all of the equipment on the Battery bus is lost. The only major
items lost are APU fire detection and APU battery start.
[ELEC DC BAT BUS FAULT, FCOM PRO.AEP.ELEC]
4.18. DC Emergency configuration

Defined as the loss of DC BUSSES 1 + 2, DC ESS BUS and DC BAT BUS.
Recovery assumes that the DC ESS BUS can be fully restored by deploying
the RAT with the EMER ELEC PWR button.
Equipment powered or controlled through DC BUS 1, DC BUS 2 and the

BAT BUS is lost. Loss of the equipment associated with the BAT BUS is
fairly benign: mainly APU Battery Start is unavailable due to loss of the
APU ECB and APU fire detection is inop. A lot of equipment is lost with
the loss of DC BUS 1+2, but it is worth remembering that all three busses
are also lost in Emergency Electrical Config, so you will have, at minimum,
all the equipment detailed in QRH 24.1. The main items of note are:
• A long runway is required. Minimum VAPP is 140kt to prevent RAT stall.

Antiskid, reversers and 60% of the spoilers are lost. Loss of nosewheel
36
steering adds to the difficulty. Braking is from the ABCU, so only manual
braking is available.3
• Flight computer redundancy is significantly reduced, with only ELAC 1,

SEC 1 and FAC 1 available. This is, however, sufficient to keep Normal
Law, so a CONF FULL landing and, indeed, CAT 3 SINGLE autoland
(using AP1 and FMGS1) are available. The latter may be useful since
wipers and window heat are lost. Only FCU 1 is available.
• Deployment of lift devices is slow due do loss of SFCC 2, but they are
all available. Normal gear operation is available through LGCIU 1.
• Pressurised fuel is available from the #1 wing tank pumps, but center
tank fuel is unusable.
• Redundancy in the pressurisation system is seriously compromised.

Manual pressure control and CPC 2 are lost, so you are reliant on CPC 1
for control. Pack 2, BMC 2 and cross bleed control are all lost, so you are
reliant on ENG 1 Bleed and Pack 1 for supply. Ram Air remains avail-
able, so if required a slow depressurisation through turning off Pack 1
followed by a depressurised landing with Ram Air is achievable.
• Communications are limited to VHF 1, controlled by RMP 1.
• Redundancy in the fire detection and suppression systems is compro-

mised. The engines each retain one detection loop and one fire bottle.
APU fire detection and cargo fire extinguishing are lost.
• Heating for all static ports is lost, so be alert for unreliable airspeed and
altitude.
[ELEC DC EMER CONFIG, FCOM PRO.AEP.ELEC]
4.19. Static inverter fault

Normal operations are not affected.
[ELEC STAT INV FAULT, FCOM PRO.AEP.ELEC]
3
easyJet aircraft automatically modulate to 1000psi, but the sim may not.
37
4.20. Generator 1 line off

Pressing the GEN 1 LINE button on the emergency electrical panel has
much the same effect as pressing the GEN 1 button on the main electrical
panel, with the difference that GEN 1 continues to supply its associated
fuel pumps. It is primarily used for the smoke drill. If it's not meant to be
off, turn it on.
[ELEC EMER GEN 1 LINE OFF, FCOM PRO.AEP.ELEC]
4.21. Tripped circuit breakers

It is generally not recommended to reset circuit breakers in flight. It is,
however, acceptable to attempt a single reset if it is judged necessary for
the safe continuation of the flight.
On the ground, any circuit breakers other than those for the fuel pumps may
be reset as long as the action is coordinated with MOC.
The ECAM warning will be triggered if a green circuit breaker trips.
[C/B TRIPPED, FCOM PRO.AEP.ELEC]
38
Chapter 5. Flight controls
5.1. Elevator faults
If a single elevator fails, the SECs use the remaining elevator to provide
pitch control in alternate law (see Section 5.12, “Alternate Law”). In addi-
tion, speed brake should not be used and the autopilots are unserviceable.
If both elevators fail, the only mechanism for pitch control available is man-
ual pitch trim, so pitch reverts to mechanical back up and roll reverts to di-
rect law. For the approach fly a long final, initiating the descent from at least
5000ft AAL. Do not try to flare using trim and do not remove power until
after touchdown. From 1000ft AAL, try to keep power changes to within
2% N1. In the event of a go-around, power must be applied very slowly if
control is not to be lost.1
[F/CTL L(R)(L+R) ELEV FAULT, FCOM PRO.AEP.F/CTL]
5.2. Stabilizer jam
Manual pitch trim is a mechanical connection to the stabilizer actuator. It
may be possible to use manual pitch trim when the ELACs have detected a
stabilizer jam, although it may be heavier than normal. If it is usable, trim
for neutral elevators.
The flight controls will revert to Alternate Law. If the stabilizer could not
be moved, gear extension should be delayed until CONF 3 and VAPP are
achieved so that the elevators are properly trimmed.
If the jam is caused by the mechanical connection, it is possible that the

ELACs will not detect the problem. The procedure in this case is similar,
but Normal Law will remain.
[F/CTL STABILIZER JAM, QRH AEP.F/CTL, FCOM PRO.AEP.F/CTL]
1
This is Boeing advice – Airbus does not provide guidance for the flare or go-around technique
when elevators are frozen.
39
5.3. Aileron faults
The lateral aircraft handling is not adversely affected even if both ailerons
fail, as the systems compensate by using the spoilers. Fuel consumption will,
however, increase by approximately 6%.
[F/CTL L(R) AIL FAULT, FCOM PRO.AEP.F/CTL]
5.4. Spoiler faults
The effect of a spoiler fault depends on whether the spoiler fails retracted
or extended.
If the spoiler fails in the retracted position, handling should not be adversely
affected. A CONF 3 landing may reduce any buffeting that is encountered.
Speed brake should not be used if spoilers 3 + 4 are affected. The loss of
ground spoilers will significantly increase landing distances.
Airbus have identified a failure scenario that leads to high pressure hy-
draulic fluid reaching the extend chamber of a spoiler actuator via a failed
o-ring. This has the effect of a spoiler failing in the fully extended position.
In this case, the autopilot does not necessarily have sufficient authority to
control the aircraft, and it should be disconnected. Fuel burn will increase
significantly; FMGC fuel predictions do not account for the failure and
should be disregarded. Green dot speed will minimize this increased fuel
burn, but may not be viable if there is excessive buffet – attempt to find a
compromise speed. Landing will be flap 3; VAPP and LDG DIST factors
are available in QRH IFP.
[F/CTL (GND) SPLR (1+2)(3+4) FAULT, FCOM PRO.AEP.F/CTL]
5.5. Rudder Jam
The main indication of jammed rudder is undue and adverse pedal move-
ment during rolling manoeuvres caused by the yaw damper orders being fed
back to the pedals when they are no longer sent to the rudder.
Crosswinds from the side that the rudder is deflected should be avoided,
and a cross wind limit of 15kt applies. Control on the ground will require
40
differential braking until the steering handle can be used (below 70kt), so
landing distances are increased. Do not use autobrake.
[F/CTL RUDDER JAM, QRH_AEP.F/CTL, FCOM PRO.AEP.F/CTL]
5.6. Flaps and/or slats fault/locked

The most pressing concern following a flap or slat problem is to establish
a max operating speed that will avoid overspeeding the device in its locked
position. A table is provided on page AEP.F/CTL “Landing with Slats or
Flaps Jammed” of the QRH for this purpose, but a quick estimation can
be made by establishing what flap lever position would be required to get
the device into its current position and using VFE for the configuration as-
sociated with that flap lever position as VMO. In doing this, it must be re-
membered that slat deployment in CONF 2 and CONF 3 is the same (tip:
think of available slat positions as being 0, 1, Intermediate or Full). This
also affects use of the QRH table; the second dot on the slat indicator on
the E/WD should be considered slat 3 for the purpose of this table, not slat
2 as might be expected. The barber’s pole displayed for VFE on the PFD is
a function of the flap lever position, so it may be worth initially selecting
the flap lever to the matching CONF to have this reference available. For
minimum speeds, the VLS displayed on the PFD is calculated from actual
flap and slat position and can be trusted.
Unless there is an obvious reason not to (e.g. wing tip brake on, alignment
fault or fault due to dual hydraulic failure), the flap lever can be recycled.
If normal operation cannot be restored, there are two major issues that must
be quickly addressed. Firstly, fuel burn will be dramatically higher when
flying with a locked device. With slats extended, fuel burn will increase
by 60%. With flaps extended it will increase by 80%. With slats and flaps
extended, fuel burn will double. These figures are available in QRH OPS.
The second issue is that landing distances are significantly increased, in the
worst case by a factor of 2.2. It may be that the combination of these factors
requires a fairly prompt diversion decision.
The flap and slat systems are largely independent, so the flap lever will
continue to move the slats if the flaps are locked and vice versa. In general,
flap 3 should be selected for landing. There are two exceptions. If flaps are
41
locked at >3, flap full should be used. If both slats and flaps are locked at 0,
flap 1 should be used so that the AP/FD go-around is armed. Configurations
and VREF increments are available on page IFP.LDwSFSF of the QRH. If a
flapless and slatless landing is required, the threshold speed may be below
VLS. This is necessary as the landing speeds in this configuration are very
close to tyre limit speeds.
During configuration, VLS is computed from actual configuration and

VFE next is computed from flap lever position. F and S speeds are essentially
meaningless.
The recommended deployment method is to select speed to 5kt below

VFE next then select the next configuration as the speed reduces through
VFE next. To prevent overspeeds in case of turbulence, it is acceptable to con-
figure at lower speeds as long as speed remains above VLS. If VLS>VFE next,
prioritise VLS: fly VLS, select the next configuration, then track VLS as it
reduces with the extension of the lift device. Use of autothrust with selected
speed is generally recommended for all phases of the approach, but in this
case it will need to be temporarily disconnected until landing configuration
is established.
It is worth noting that failure of the slat channels of both SFCCs appears to
result in the loss of characteristic speed display on both PFDs. This is not
mentioned in the FCOM but occurs in the sim. The upshot of this is that
neither VLS nor VSW are available at all, since they are not displayed and
there is no way to calculate them. This is of particular concern when trying
to configure to flaps 2 since the aircraft must be slowed to VFE(conf 2) when
still clean (remember conf 1 is slats only when configuring from conf 0). It
is highly likely that the stall warner will activate during the transition, and
if not anticipated, the subsequent recovery will overspeed the flaps. The
solution is to brief that speed will be reduced very slowly and if the stall
warning occurs the speed will be maintained whilst allowing the deployment
of the flaps to recover the stall margin.
The autopilot may be used down to 500ft AAL, but since it is not tuned for
the abnormal configuration it must be closely monitored.
For the go-around, initially maintain flap/ slat configuration. A speed 10kt
lower than max operating speed should be flown. If it is the slats that are
42
jammed or if the flaps are jammed at 0, clean configuration can be used to

transit to a diversion airfield.
Other issues include the possible loss of the automatic operation of the cen-
tre tank pumps (which is sequenced to the slats) and possible reversion to
Alternate Law.
[F/CTL FLAPS(SLATS) FAULT(LOCKED), QRH_AEP.F/CTL, FCOM-

PRO.AEP.F/CTL]
5.7. SFCC faults
Each SFCC has fully independent slat and flap channels. A failure of a
channel in a single controller will lead to slow operation of the associated
surfaces. In addition, the flap channel of SFCC1 provides input to the idle
control part of the FADECs and to the EGPWC.
Failure of both flap channels or failure of both slat channels is covered in

Section 5.6, “Flaps and/or slats fault/locked”.
[F/CTL FLAP(SLAT) SYS 1(2) FAULT, FCOM PRO.AEP.F/CTL]
5.8. ELAC fault
In normal operations, ELAC 1 controls the ailerons and ELAC 2 controls
the elevators and stabiliser. Failure of a single ELAC will result in failover to
the remaining computer. Provided no uncommanded manoeuvres occurred,
an attempt can be made to reset the failed ELAC.
Failure of both ELACs leads to loss of ailerons and hence Alternate Law.
One of the SECs will take over control of the elevators and stabiliser. Again,
an attempt can be made to reset the computers.
If the fault is designated a pitch fault, only the pitch function of the associ-
ated ELAC is lost.
[F/CTL ELAC 1(2) FAULT, FCOM PRO.AEP.F/CTL]
43
5.9. SEC fault
Each SEC controls either 1 or 2 spoilers per wing. SEC 1 and 2 also provide
back up for the ELACs (see Section 5.8, “ELAC fault”). Loss of a SEC
leads to loss of its associated spoilers. SEC 1 provides spoiler position to the
FACs. If speedbrakes are deployed with SEC 1 u/s and SEC 3 operative,
spoiler 2 will deploy without a corresponding increase in VLS. Therefore,
do not use speedbrake if SEC 1 is affected (it won’t do much anyway!).
Pairs of SECs also provide the signal for reverse thrust lever angle to the
reversers and spoiler deployment to the autobrake. A dual SEC failure will
therefore lead to a loss of a reverser and loss of autobraking.
If all SECs are lost, all the above holds true. Furthermore the flight controls
revert to Alternate Law due to the complete loss of spoilers. Also, due to
routing of LGCIU data to the ELACs via the SECs, Direct Law will occur
at slat extension rather than gear extension.
An attempt should be made to reset the affected SEC(s).

[F/CTL SEC 1(2)(3) FAULT, FCOM PRO.AEP.F/CTL]
5.10. FCDC faults
The two FCDCs are redundant, so a single failure has no immediate effect.
If both FCDCs fail, the ELACs and SECs can no longer supply data to
the EIS. The major effect of this is that F/CTL ECAM warnings are no
longer generated. The warning lights on the overhead panel continue to give
valid information and should be monitored. The aircraft remains in normal
law with all protections, but protection indications (bank and pitch limits,
Vα‑prot and Vα‑max) are not shown and the stall warning system becomes
active.
[F/CTL FCDC 1(2)(1+2) FAULT, FCOM PRO.AEP.F/CTL]
5.11. Direct Law
In Direct Law, deflection of the control surfaces is a linear function of de-
flection of the side-stick and trimming must be done manually. The controls
44
are very sensitive at high speeds. Use of manual thrust is recommended as

power changes will result in pitch changes. Similarly, use of the speed brake
will result in nose up pitch changes so it should be used with care. Protec-
tions are unavailable, so speed is limited to 320kt/0.77M and care must be
taken in GPWS or windshear manoeuvres. Approach speed is increased by
10kt and landing distances increase by a factor of 1.2.
The major handling difficulty in direct law is the go-around. There is no

compensation for the large pitch moment introduced by selecting TOGA
power on the under-slung engines, the thrust levers are non-linear and the
use of the manual pitch trim wheel will be unfamiliar. Apply power smooth-
ly and progressively and anticipate a requirement for unusual side-stick in-
puts.
Direct Law works with or without yaw dampers. The aircraft is always con-
vergent in dutch roll, so use lateral control, not rudder, if dutch roll is ex-
perienced.
[F/CTL DIRECT LAW, FCOM PRO.AEP.F/CTL]
5.12. Alternate Law
In alternate law, pitch is as in normal law, but roll is as in direct law. Load
factor protection is retained, but other protections are either replaced with
static stability or are lost, depending on the nature of the failure. Stall warn-
ings and overspeed warnings become active.
The main effects are that speed is limited to 320kt and stall warnings must
be respected when carrying out EGPWS manoeuvres.
The autopilot may be available.
Expect Direct Law after landing gear extension (see Section 5.11, “Direct
Law”), and hence increased approach speeds and landing distances due to
a CONF 3 landing (see QRH IFP.LDwFCSF).
[F/CTL ALTN LAW, , FCOM PRO.AEP.F/CTL]
45
5.13. Wingtip brake fault

The wingtip brakes activate in case of asymmetry, mechanism overspeed,
symmetrical runaway or uncommanded movements. This protection is lost.
[F/CTL FLAP(SLAT) TIP BRK FAULT, FCOM PRO.AEP.F/CTL]
5.14. Flap attach sensor failure

The flap attach sensor detects excessive differential movement between the
inner and outer flaps which would indicate failure of a flap attachment. This
protection is lost.
[F/CTL FLAP ATTACH SENSOR, FCOM PRO.AEP.F/CTL]
5.15. Flight control servo faults

All flight controls have redundant servos. In the case of an elevator servo
fault, a restriction to not use speedbrake above VMO/MMO applies.
[F/CTL AIL(ELEV) SERVO FAULT, FCOM PRO.AEP.F/CTL]
5.16. Speed brake disagree

This indicates that the spoiler positions do not correspond with the speed-
brake lever position. This may be as a result of automatic retraction (alpha
floor activation or speed brakes deployed when full flap selected) or as a
result of spoiler malfunction. In both cases retract the speedbrake lever and
in the case of spoiler malfunction consider the speedbrakes unserviceable.
[F/CTL SPD BRK DISAGREE, FCOM PRO.AEP.F/CTL]
5.17. Speed brake fault

This indicates a failure of the speedbrake lever transducers rather than a
problem with the spoilers. Ground spoiler activation may be expected on se-
lection of reverse, so providing reversers are used, landing distances should
not be affected.
[F/CTL SPD BRK (2)(3+4) FAULT, FCOM PRO.AEP.F/CTL]
46
5.18. Stiff sidestick/ rudder pedals

This may affect both sidesticks at the same time, but not the rudder pedals
or it may affect the rudder pedals and one sidestick. Control forces will
remain moderate and the aircraft remains responsive. Confirm autopilot
disengagement and consider transferring control if one of the sidesticks is
unaffected.
[QRH_AEP.F/CTL, FCOM PRO.AEP.F/CTL]
5.19. Sidestick unannunciated transducer faults

It is possible for a failed sidestick transducer to cause uncommanded control
inputs. If no fault is detected, the result is that the aircraft behaves as if
that input had actually been made. Generally, the autopilot will disconnect
and any attempt to control the aircraft with the failed sidestick will fail.
The aircraft should be recovered with the other sidestick using the takeover
button. Keeping this button pressed for 40 seconds will lock out the failed
sidestick, and the autopilot can then be re-engaged. The autopilot should
not be disconnected in the normal manner as pressing the takeover button
will re-introduce the failed sidestick and the uncommanded input; use the
FCU instead.
47
48
Chapter 6. Fire
Chapter 6. Fire
6.1. Smoke and fumes
The QRH procedure should be applied when smoke is detected and the crew
suspect the avionics, air conditioning or cabin equipment as the source.
The paper procedure includes all the steps of the avionics smoke ECAM
procedure, so if this caution is triggered, the paper procedure should be
applied instead of the ECAM1. The FCTM also adds that the AVIONICS
SMOKE ECAM procedure should be applied only if the flight crew can
confirm it visually or by smell, otherwise it should be considered spurious.
In the case of other smoke related ECAMs, the relevant ECAM procedure
should be applied first and then the use of the paper checklist considered.
While the smoke aspect of these procedures is fairly unambiguous, the

fumes aspect has led to both under- and over-reaction in the simulator.
Training department guidance is that if a “smell” is detected in the cabin
and it is having no physiological effects, no immediate action is required.
If there are physiological effects, the SMOKE/FUMES/AVNCS SMOKE
QRH procedure should be actioned. However, only the first line, LAND
ASAP, is actioned since there is no perceptible smoke and the rest of the
checklist is below the line “if perceptible smoke apply immediately”. Thus
after cross-confirming LAND ASAP, immediately move on to the RE-
MOVAL OF SMOKE/FUMES QRH checklist. It should be noted that con-
firmation of the correctness of this advice is currently being sought from
Airbus, and that in a number of in-service events the source of the smell has
been positively identified as one of the packs.
Rain repellent fluid leaks are not covered. Orange peel smells are toxic, pine
needle smells non-toxic.
1
There is an odd airframe dependency with this; on some airframes the instruction is to run the
paper checklist at latest after completing the immediate actions of the Avionics Smoke ECAM,
whilst on others it is when requested by the Avionics Smoke ECAM. Unfortunately the Avionics
Smoke ECAM itself is not described in the FCOM. A general policy of running the paper procedure
instead of the Avionics Smoke ECAM procedure seems to cover all eventualities.
49
Chapter 6. Fire
The SMOKE/ FUMES/ AVNCS SMOKE checklist attempts to isolate the

source of the smoke. It is possible that it may become impossible to carry
out this checklist due to smoke density. In this case, interrupt the checklist
and carry out the smoke removal drill (see Section 6.2, “Smoke/ fumes re-
moval”). It is also possible that the situation may deteriorate to a level that an
immediate forced landing becomes the preferable option. In general, unless
the source of the smoke is obvious and extinguishable, a diversion should
be initiated immediately. The smoke removal drill is most effective and
adaptable at lower levels, so a descent to 10,000ft or MSA is also a priority.
The first priority is to protect yourself, so get an oxygen mask on. The mask
must be set to 100% oxygen to exclude fumes; at minimum dispatch oxy-
gen levels this will provide as little as 15 minutes of protection. Pushing the
“Emergency pressure selector” knob will provide a few seconds of over-
pressure, which can be used to clear any smoke trapped in the mask as it
was donned.
Likely sources of smoke are the avionics, the cabin fans and the galleys.
Smoke from these sources can be contained with simple and reversible ac-
tions which can be initiated immediately: put the avionics ventilation into
smoke removal mode by selecting both blower and extract fans to OVRD,
turn off the cabin fans and turn off the galleys.
Where the source is immediately obvious, accessible and extinguishable,

isolate the faulty equipment. Otherwise the QRH provides seperate drills
for suspected air conditioning smoke, suspected cabin equipment smoke
or suspected avionics/ electrical smoke. In addition the avionics/ electrical
smoke drill includes undetermined and continuing smoke sources.
Suspect air conditioning smoke if it initially comes out of the ventilation

outlets. Several ECAM warnings are also likely to occur as sensors detect
the smoke in other areas. The displayed ECAM procedures must be applied.
Following an engine or APU failure, smoke may initially enter the air con-
ditioning system but should dissipate quickly once the failure is contained.
The air conditioning drill starts by turning the APU bleed off in case this
is the source. The packs are then turned off one at a time to determine if
the source of the smoke is a pack.
50
Chapter 6. Fire
The cabin equipment smoke drill involves selecting the commercial button
off and searching for faulty cabin equipment.
Suspect avionics smoke if the only triggered ECAM is AVIONICS

SMOKE. If an item of electrical equipment fails immediately prior to the
appearance of the smoke, that equipment should be suspected as the source.
The avionics/ electrical drill (which includes the undetermined source drill)
reduces the amount of electrically powered equipment to a minimum by
adopting a slightly modified emergency electrical configuration.2 The re-
sulting ECAM may 3 contain instructions to reset the generators; these in-
structions should be disregarded, although the rest of the ECAM procedure
must be actioned. The intention is to restore power 3 minutes before land-
ing or at 2000ft aal. Since you will not be able to restore the two IRs that
were depowered, the landing will be in Direct Law and hence CONF 3.4
This is not mentioned in QRH AEP.SMOKE SFAS, and is only mentioned
on the ECAM once gear is extended.
[AVIONICS SMOKE, QRH AEP.SMOKE, FCOM PRO.AEP.SMOKE]
6.2. Smoke/ fumes removal

Smoke removal procedures initially use the pressurisation system to draw
smoke and fumes overboard by increasing the cabin altitude. If there are
no fuel vapours present, the packs are used to drive the smoke overboard.
Otherwise it is driven overboard by residual pressure.
The final target configuration is packs off, outflow valve fully open and ram
air on. As this depressurises the aircraft, it can only be achieved at lower
levels (preferably FL100). If in emergency configuration, turning the APU
master switch on connects the batteries for a maximum of 3 minutes and
allows manual control of the DC powered outflow valve motor. Once at a
2
The EMER ELEC GEN 1 LINE button rather than the GEN 1 button is used to disconnect gen-
erator 1 which disconnects generator 1 from the electrical system but allows it to directly supply
one fuel pump in each wing tank.
3
Which ECAM procedure is displayed is dependent on whether an AVIONICS SMOKE ECAM
has been triggered prior to the adoption of emergency electrical configuration.
4
QRH AEP.ELEC ELEC EMER CONFIG Sys Remaining indicates that by selecting the
ATT HDG selector to CAPT 3 it may be possible to retain IR3 and hence have sufficient equipment
for a Cat 3A landing once power is restored. This has not yet been confirmed by Airbus.
51
Chapter 6. Fire
suitable level and below 200kt, as a last resort PNF’s cockpit window can
be opened.
[QRH AEP.SMOKE, FCOM PRO.AEP.SMOKE]
6.3. Engine fire
The basic sequence is to bring the thrust lever of the affected engine to idle,
turn off its engine master, push its fire button, wait 10 seconds then deploy
its first fire bottle. If the fire is not extinguished after 30 seconds, indicated
by the fire button remaining lit, deploy the second bottle.
This sequence is modified on the ground in that both fire bottles are fired
immediately, and the remaining engine is then also shut down. Note that
shutting down both engines without the APU running will leave only bat-
teries, resulting in loss of all COMS except VHF1 and loss of ECAM ref-
erence for the final actions.
[ENG 1(2) FIRE, FCOM PRO.AEP.ENG]
6.4. Lithium Battery Fire

If there are flames, they should be attacked with a halon extinguisher. This
will necessitate PF donning a crew oxygen mask and PNF donning the
smoke hood.
If there are no flames, or once the flames have been extinguished, the cab-
in crew should remove the device from the cockpit and store it in a lined
container filled with water. If the device cannot be removed, water or non-
alcoholic liquid should be poured on the device, and it should be continu-
ously monitored for re-ignition.
Note that these procedures assume that you are dealing with lithium ion
batteries (i.e. rechargeable batteries found in laptops, tablets, phones etc.)
where the amount of water reactive lithium metal is actually fairly low.
Once the flames have been knocked down, the focus is on cooling to prevent
thermal runaway in adjacent cells. Counter-intuitively, it is vital that ice is
not used as this acts as a thermal insulator and will likely cause adjacent
52
Chapter 6. Fire
cells to explode. For the same reason, smothering with anything that might
thermally insulate the battery pack (e.g. a fire bag) is probably a bad idea.
If smoke becomes the biggest threat, see Section 6.2, “Smoke/ fumes re-
moval”. If the situation becomes unmanageable, consider an immediate
landing.
[QRH AEP.SMOKE, FCOM PRO.AEP.SMOKE, FAA videos (available on

youtube)]
53
Chapter 6. Fire
54
Chapter 7. Fuel
Chapter 7. Fuel
7.1. Fuel leak
Whenever a non-normal fuel event occurs, the possibility that the underly-
ing cause of the event is a fuel leak should be considered. Only when a fuel
leak has been categorically ruled out should the cross-feed valve be opened.
The primary method used to detect fuel leaks is a regular check that actual
fuel remaining corresponds to expected fuel remaining and that fuel used
plus fuel remaining corresponds to fuel at engine start. The latter parameter
is monitored on some aircraft and may trigger an ECAM warning. Other
indications of a leak include fuel imbalance or excessive fuel flow from
an engine. It also possible that a fuel leak may be detected visually or by a
smell of fuel in the cabin.
If a leak can be confirmed to be coming from an engine or pylon, the af-

fected engine must be shut down. In this case, cross-feeding is allowable.
Otherwise, the cross-feed must be kept closed.
If the leak cannot be confirmed to be originating from an engine or pylon,

an attempt should be made to identify the source of the leak by monitoring
the inner tank depletion rates with the crossfeed valve closed and the center
tank pumps off.
If depletion rates are similar, a leak from the center tank or from the APU
feeding line should be suspected. If there is a smell of fuel in the cabin, it
is likely that the APU feeding line is at fault and the APU should be turned
off. Fuel from the center tank should be used once one of the inner tanks
has <3000kg.1
1
The logic here is strange. An unofficial explanation of the requirement for <3000kg in the inner
tank was given to me: some of the fuel lines from the center tank run through the wing tanks, so fuel
from a center tank leak may end up transferring to the wing tanks and with full wing tanks might
be lost overboard by venting the wing tank overflow. As for the APU feeding line leak, I would
expect the left tank to decrease faster than the right in this case; my guess is that the expectation
is that an APU feeding line leak will be detected as a smell in the cabin and the leak will be too
small to become apparent as an imbalance.
55
Chapter 7. Fuel
If, after 30 minutes, one tank has been depleted by 300kg more than the
other, the location of leak is narrowed down to the engine or the wing on
the more depleted side. To confirm which it is, shut down the engine. If the
leak then stops, an engine leak is confirmed and the cross feed can be used.
If not, a leak from the wing is most likely. In this case, an engine restart
should be considered.
In an emergency, a landing may be carried out with maximum fuel imbal-

ance.
Do not use thrust reversers.
[FUEL F USED/FOB DISAGREE, QRH AEP.FUEL, FCOM PRO.AEP.FUEL]
7.2. Fuel imbalance
All fuel balancing must be carried out in accordance with QRH AEP.FU-
EL “Fuel Imbalance”, paying particular attention to the possibility of a fuel
leak. Any action should be delayed until sufficient time has passed for a fuel
leak to become apparent. FCOM PRO.AEP.FUEL adds a note not found
in the QRH that “there is no requirement to correct an imbalance until the
ECAM fuel advisory limit is displayed”, an event that occurs when one inner
tank holds >1500kg more than the other. The limitations for fuel imbalance
in FCOM LIM.FUEL, however, show that the fuel advisory does not neces-
sarily indicate that a limitation is likely to be breached. In particular, when
the outer tanks are balanced and the heavier inner tank contains ≤2250kg,
there are no imbalance limitations. Furthermore, the aircraft handling is not
significantly impaired even at maximum imbalance.
To balance the fuel, open the cross-feed valve and turn the lighter side pumps
and the center tank pumps off.
[QRH AEP.FUEL, FCOM PRO.AEP.FUEL, FCOM LIM.FUEL]
7.3. Gravity fuel feeding

Turn on ignition in case of fuel interruption and avoid negative G. The ceil-
ing at which fuel can be reliably gravity fed depends on whether the fuel has
56
Chapter 7. Fuel
had time to deaerate. If the aircraft has been above FL300 for more than 30
minutes, the fuel may be considered deaerated and the current flight level
maintained. Otherwise, the fuel must be considered aerated and the gravity
feed ceiling is FL300 if the aircraft exceeded FL300 or FL150 if it didn’t.
If gravity feeding is required, descend to the gravity feed ceiling.
It is also possible to gravity cross feed by side slipping the aircraft with a
bank angle of 2° to 3° should this become necessary.
[QRH AEP.FUEL, FCOM PRO.AEP.FUEL]
7.4. Wing tank pump(s) low pressure

Failed pumps should be turned off.
Failure of a single pump in either tank results in reduced redundancy only.
Failure of both pumps in a given tank means that the fuel in that tank is
only available by gravity feeding. Pressurized fuel may be available from
the center tank (use manual mode if necessary) or by cross-feeding. A de-
scent to gravity feed ceiling may be required (see Section 7.3, “Gravity fuel
feeding”).
[FUEL L(R) TK PUMP 1(2)(1+2) LO PR, FCOM PRO.AEP.FUEL]
7.5. Center tank pumps low pressure

Failed pumps should be turned off.
Failure of a single center tank pump results in a loss of redundancy. The

crossfeed should be opened until the center tank fuel has been exhausted so
that the remaining pump can supply both engines.
Failure of both center tank pumps makes the fuel in the center tank unus-
able.
[FUEL CTR TK PUMP(S)(1(2)) LO PR, FCOM PRO.AEP.FUEL]
57
Chapter 7. Fuel
7.6. Auto feed fault

The center tank pumps must be managed manually. They must be switched
off whenever slats are extended, wing tank fuel >5000kg or center tank fuel
is exhausted.
[FUEL AUTO FEED FAULT, FCOM PRO.AEP.FUEL]
7.7. Low fuel level

The ECAM is triggered at approximately 750kg. The warning may be spu-
rious if the ECAM is triggered just before the wing cell transfer valves open.
If center tank fuel remains, it should be used by selecting the center tank
pumps to manual mode. If there is a fuel imbalance and a fuel leak can be
ruled out, crossfeed fuel as required.
If both tanks are low level, about 30 minutes of flying time remain.
If any change to the current clearance will lead to landing with less than
minimum reserve fuel, declare "minimum fuel" to ATC. This is just a heads
up to ATC, not a declaration of an emergency situation. If it is calculated
that less than minimum fuel will remain after landing, declare a MAYDAY.
[FUEL(R)(L+R) WING TK LO LVL, FCOM PRO.AEP.FUEL, EOMA 8.3.8.2]
7.8. Outer tank transfer valves failed closed

If both transfer valves fail to open when a wing tank reaches low level,
the fuel in that outer tank becomes unusable. The fuel balance will remain
within limits since maximum outer tank imbalances are acceptable if the
total fuel in either wing is the same [FCOM LIM.FUEL].
[FUEL L(R) XFR VALVE CLOSED, FCOM PRO.AEP.FUEL]
7.9. Outer tank transfer valve open out of se-

quence
Maximum outer tank imbalances are acceptable if the total fuel in either
wing is the same [FCOM LIM.FUEL], so no action is required.
[FUEL L(R) XFR VALVE OPEN, FCOM PRO.AEP.FUEL]
58
Chapter 7. Fuel
7.10. Cross-feed valve fault

If the valve has failed open, fuel balance can be maintained through selective
use of fuel pumps. If it has failed closed, crossfeeding is unavailable.
[FUEL FEED VALVE FAULT, FCOM PRO.AEP.FUEL]
7.11. Low fuel temperature

ECAM is triggered at approx -43°C. If on the ground, delay takeoff until
temperatures are within limits. If in flight, descending or increasing speed
should be considered.
[FUEL L(R) OUTER(INNER) TK LO TEMP, FCOM PRO.AEP.FUEL]
7.12. High fuel temperature

This ECAM is known to be triggered spuriously by interference from com-
munication equipment. The procedure should only be applied if the mes-
sage has not disappeared within 2 minutes.
The ECAM temperature triggers on the ground are 55°C for the outer cell
and 45°C for the inner cell. In the air they are 60°C for the outer cell and
54°C for the inner cell.
The temperature of fuel returning to the tanks is primarily a function of

IDG cooling requirement. The immediate action, therefore is to turn the
galley off to reduce the IDG load.
On the ground, the engine on the affected side must be shut down if the
outer cell reaches 60°C or the inner cell reaches 54°C. An expeditious taxi
may, therefore, be advantageous.
In the air, if only one side is affected, fuel flow can be increased so that less
hot fuel is returned to the tanks. If the temperature gets too high (>65°C
outer or >57° inner), IDG disconnection will be required. The engine must
be running when the IDG button is pressed, and it must not be held for more
than 3 seconds.[FCOM SYS.24.20]
[FUEL L(R) OUTER(INNER) TK HI TEMP, FCOM PRO.AEP.FUEL]
59
Chapter 7. Fuel
60
Chapter 8. Landing gear
8.1. Loss of braking (memory item)
If it is simply an autobrake failure, just brake manually. Otherwise, apply
max reverse and attempt to use the alternate brake system. To do this, re-
lease the brake pedals and turn off the ASKID & NW STRG switch. If the
alternate system also appears to have failed, short successive applications
of the parking brake may be used. Use of the parking brake in this way risks
tire burst and lateral control difficulties (due brake onset asymmetry) so
delay until low speed if at all possible.
[FCOM PRO.AEP.BRAKES]
8.2. Residual braking procedure

Residual brake pressure must be checked after landing gear extension as
there is no ECAM warning. A brief brake pressure indication is expected
as the alternate system self tests after the gear is down locked, but pressure
should quickly return to zero. If the triple indicator shows residual pressure
after this test, try to zero it by pressing the brake pedals several times. If a
landing must be made with residual pressure in the alternate braking system,
use autobrake MED or immediate manual braking to prioritise the normal
system. Anticipate brake asymmetry at touchdown.
[QRH AEP.BRAKES, FCOM PRO.AEP.BRAKES]
8.3. Gravity extension
Gravity extension is achieved by turning the GRAVITY GEAR EXTN
handcrank clockwise three times until a mechanical stop is reached. Once
the gear is down, the LG lever should be set to down to extinguish the UN-
LK lights and remove the LG CTL message from the WHEEL page.
Availability of landing gear indications depends on the nature of the failure

that resulted in the requirement for gravity extension. LDG GEAR control
panel indications may still be available if LGCIU 1 is otherwise unservice-
able, providing that it is electrically supplied.
61
Gear doors may show amber on the WHEEL page after gravity exten-
sion. There may also be spurious LGCIU 2 FAULT or BRAKES SYS 1(2)
FAULT ECAM warnings.
[QRH AEP.L/G, FCOM PRO.AEP.L/G]
8.4. Asymmetric braking
Defined as all brakes on one gear released (indicated by amber brake re-
lease indicators on both wheels of one main gear on the WHEEL SD page).
When the remaining brakes are applied, the aircraft will tend to swing to-
wards them. This tendency must be countered with rudder, hence the brak-
ing must be progressive and co-ordinated with available rudder authority.
Crosswinds from the side of the available brakes will re-inforce the swing,
so anything greater than 10kt from that side should be avoided.
If a reverser is inoperative on the same side as the inoperative brakes, do

not use the remaining reverser since it would also re-inforce the swing.
Landing distances will increase significantly.
[QRH AEP.BRAKES, FCOM PRO.AEP.BRAKES]
8.5. Landing with abnormal landing gear

A landing should be carried out on a hard surface runway using any avail-
able landing gear. Foaming of the runway is recommended. Manual brak-
ing should be used. Reverse thrust should not be used as it will cause ground
spoiler extension. The GRVTY GEAR EXTN handcrank should be turned
back to normal to allow the landing gear down actuators to be pressurised
and thus reduce the chance of gear collapse.
If the nose gear is not available, move the CG aft by moving passengers
to the rear of the aircraft. Use elevator to keep the nose off the runway,
but lower the nose onto the runway before elevator control is lost. Braking
must be progressive and balanced against available elevator authority. The
engines should be shut down with the ENG MASTER switches prior to nose
impact.
62
If one main gear is not available, consider crossfeeding to remove the fu-
el from the wing with the unserviceable gear. The anti-skid system cannot
operate with a single main gear extended and must be switched off to avoid
permanent brake release. The ground spoilers should not be armed in or-
der to maintain the maximum possible roll authority. The engines should
be shut down at touchdown. After touchdown, use roll control to keep the
unsupported wing from touching down for as long as possible.
If both main gear are unavailable, the engines should be shut down in the
flare. Pitch attitude at touchdown must be >6°.
All doors and slides are available for evacuation in any of the normal gear
up attitudes.
[QRH AEP.L/G, FCOM PRO.AEP.L/G]
8.6. Flight with landing gear extended

Flight into expected icing conditions is not approved. Gear down ditching
has not been demonstrated. FMGC predictions will be erroneous – selected
speed should be used for all phases except approach. CLB and DES modes
should not be used. Altitude alerting will not be available. Any failure that
normally causes a degradation to alternate law will instead cause a degra-
dation to direct law.
The dual engine failure scenario is modified to reflect the gear limiting
speed. Assisted start should be preferred. If the APU is not available, gear
limit speeds should be disregarded to achieve a windmill start. Flight con-
trols will be in direct law; manual pitch trim should be available, even when
not annunciated on the PFD.
Performance in all phases will be affected. In particular, approach climb

limiting weights for go-around (see FCOM PRO.NOR.SUP.L/G) must be
reduced by 14%. Fuel burn will increase (approximate factor is 2.3). Engine
out ceiling and take-off performance are also impacted.
[FCOM PRO.NOR.SUP.L/G]
63
8.7. Gear shock absorber fault

A shock absorber did not extend when airborne or did not compress on
landing. If airborne the gear cannot be retracted. Respect the gear extended
limit speed of 280kt and see Section 8.6, “Flight with landing gear extend-
ed”.
[L/G SHOCK ABSORBER FAULT, FCOM PRO.AEP.L/G]
8.8. Gear not uplocked

Landing gear retraction sequence has not completed within 30 seconds. If
the gear doors have closed, the gear will rest on the doors so avoid excess g
loads. If the doors have not closed, recycle the gear. If this does not work,
select the gear down and see Section 8.6, “Flight with landing gear extend-
ed”.
[L/G GEAR NOT UPLOCKED, FCOM PRO.AEP.L/G]
8.9. Gear not downlocked

If the landing gear extension sequence has not completed within 30 seconds,
retract the gear, wait until it has fully stowed, and then redeploy it. Recent
studies show that if the gear does not immediately deploy successfully fol-
lowing reselection, it may deploy normally within the next two minutes as
hydraulic pressure continues to act on the gear and doors throughout this
time. If still unsuccessful after two minutes, attempt to deploy the gear by
gravity (see Section 8.3, “Gravity extension”).
[L/G GEAR NOT DOWNLOCKED, FCOM PRO.AEP.L/G]
8.10. Gear doors not closed

A gear door is not uplocked. Recycle the gear. If the doors cannot be closed,
speed is limited to 250kt/M0.6.
[L/G DOORS NOT CLOSED, FCOM PRO.AEP.L/G]
64
8.11. Uplock fault
An uplock is engaged when the corresponding gear is downlocked. As the
uplock will not move to accept the gear the gear must be left down. See
Section 8.6, “Flight with landing gear extended”.
[L/G GEAR UPLOCK FAULT, FCOM PRO.AEP.L/G]
8.12. LGCIU disagreement
The LGCIUs disagree on the position of the gear. In the absence of other
ECAM warnings, the gear position can be assumed to agree with the gear
lever position.
[L/G SYS DISAGREE, FCOM PRO.AEP.L/G]
8.13. LGCIU fault
The FADECs use LGCIU input to determine idle mode. If a LGCIU is
determined to be faulty, the system failsafes to approach idle mode, and
modulated idle and reverse idle (and hence reversers) will not be available.
The GPWS uses LGCIU 1 to determine landing gear position. If this

LGCIU is faulty, the GPWS will need to be inhibited to prevent spurious
warnings.
If both LGCIUs are lost, normal landing gear control and indicating sys-
tems are lost. The gear must be gravity extended (see Section 8.3, “Gravity
extension”).
[L/G LGCIU 1(2) FAULT, FCOM PRO.AEP.L/G]
8.14. Gear not down

Indicates that the landing gear is not downlocked when radio altitude is
below 750ft rad alt and N1 and flap setting indicate that the aircraft is on
approach. If rad alt data is not available, it indicates gear is not down when
flap 3 or flap full is selected. In some cases the warning may be cancelled
with the emergency cancel pushbutton.
[L/G GEAR NOT DOWN, FCOM PRO.AEP.L/G]
65
8.15. Park brake on
The parking brake is set when the thrust levers are set to FLX or TOGA.
Check the position of the brake handle position and for pressure indications
on the brake triple gauge.
[CONFIG PARK BRK ON, FCOM PRO.AEP.CONFIG]
8.16. Nosewheel steering fault

Nosewheel steering is unavailable so differential braking must be used to
steer the aircraft. The nosewheel may not be aligned if the L/G shock ab-
sorber ECAM is also displayed, in which case delay nosewheel touch down
as long as possible. Cat III dual will not be available.
[WHEEL N/W STRG FAULT, FCOM PRO.AEP.WHEEL]
8.17. Antiskid nosewheel steering off

The A/SKID & NW STRG switch is off. The ABCU controls braking
through the alternate braking system. Antiskid is not available so landing
distance will increase significantly. Autobrake and nosewheel steering will
also not be available.
[BRAKES ANTI SKID/NWS OFF, FCOM PRO.AEP.BRAKES]
8.18. Antiskid nosewheel steering fault

Either:
• both BSCU channels have failed or
• the normal brake system has been lost and the yellow hydraulic pressure
is low.
Effects are as for Section 8.17, “Antiskid nosewheel steering off”, although

if yellow hydraulic pressure is low braking will be accumulator only.
[BRAKES A/SKID NWS FAULT, FCOM PRO.AEP.BRAKES]
66
8.19. Brake system fault

A fault has been detected in one channel of the BSCU. Loss of redundancy
only.
[BRAKES SYS 1(2) FAULT, FCOM PRO.AEP.BRAKES]
8.20. Brakes hot
At least one brake temperature is >300°C. Check Section 8.29, “Brake tem-
perature limitations requiring maintenance action” if the temperature is ex-
cessive or the brake temperatures are not reasonably even.
Temperature must be <300°C for takeoff to prevent ignition of any hy-

draulic fluid that leaks onto the brake. Use brake fans as necessary to bring
the temperature down in time for the next takeoff. The brake fans also cool
the temperature sensor, so assume the real brake temperature is twice that
indicated if they have recently been used.
If the warning appears in flight, providing that performance permits, the

landing gear should be extended to allow the brakes to cool.
[BRAKES HOT, FCOM PRO.AEP.BRAKES]
8.21. Auto brake fault

A failure was detected when the autobrake was armed. Brake manually.
[BRAKES AUTO BRK FAULT, FCOM PRO.AEP.BRAKES]
8.22. Hydraulic selector valve fault

This ECAM message may indicate two completely different conditions:
1. The normal brake selector valve has failed in the open position. The
normal servo valves (downstream of the selector valve) will have con-
tinuous full pressure at their inlets, but, as long as anti-skid is opera-
tive, will control brake pressure and anti-skid normally.
2. The steering selector valve has failed in the open position. This means
that the steering will remain pressurised as long as there is pressure in
67
the yellow hydraulic system. This has obvious implications if towing is

attempted, but will also mean that the nosewheel will go to maximum
deflection if the A/SKID & N/W STRG switch is selected off or the
BSCU is reset.
[WHEEL HYD SEL FAULT, FCOM PRO.ABN.32]
8.23. Failure of normal braking system

Normal braking is lost, but alternate braking and anti-skid are available.
Landing distance increases slightly.
[BRAKES NORM BRK FAULT, FCOM PRO.AEP.BRAKES]
8.24. Failure of alternate braking system

Loss of redundancy only.
[BRAKES ALTN BRK FAULT, FCOM PRO.AEP.BRAKES]
8.25. Failure of normal and alternate braking sys-

tems
The only braking remaining is the parking brake. See Section 8.1, “Loss of
braking (memory item)” for method.
[BRAKES NORM + ALTN FAULT, FCOM PRO.AEP.BRAKES]
8.26. Brake accumulator low pressure

Braking is not available unless either the green or yellow hydraulic systems
are pressurised. If the engines are shut down, attempt to recharge the ac-
cumulator using the yellow system electrical pump. When parking the air-
craft, use chocks.
[BRAKES BRK Y ACCU LO PR, FCOM PRO.AEP.BRAKES]
8.27. Released brakes, normal system

If normal braking is active and at least one engine is running, the BSCU
self tests when it receives a “gear downlocked” signal from either of the
68
LGCIUs. The BRAKES RELEASED ECAM is provided if at least one set

of brakes on a main wheel is incorrectly released during this test. The failed
brake is shown by an amber release symbol on the WHEEL page. Loss of a
brake leads to increased landing distances. If both brakes on the same gear
are released, see Section 8.4, “Asymmetric braking”.
[BRAKES RELEASED, FCOM PRO.AEP.BRAKES]
8.28. Released brakes, alternate system

The ABCU self tests the brakes in a similar manner to the BSCU (see Sec-
tion 8.27, “Released brakes, normal system”). If this test is failed, normal
braking can be expected as long as the normal braking system is active.
If the alternate braking system is active, braking will be asymmetric (see
Section 8.4, “Asymmetric braking”).
[BRAKES ALTN L(R) RELEASED, FCOM PRO.AEP.BRAKES]
8.29. Brake temperature limitations requiring

maintenance action
Maintenance is required if:
• One brake temp is >600°C and the other brake on the same gear is 150°C
less
• One brake temp is <60°C and the other brake on the same gear is 150°C
more
• The average temp of one gear is 200°C more than the average temp of
the other
• Any brake temp exceeds 900°C
• A fuse plug has melted
[EOMB 2.3.21]
69
70
Chapter 9. Power plant
9.1. Dual engine failure
If time is short due to the failure occuring at low altitude, “quick” ditch-
ing and forced landing procedures are available on the back of the normal
checklist. These are discussed in Section 2.5, “Ditching” and Section 2.6,
“Forced landing”.
The ENG DUAL FAILURE ECAM may not be triggered under some cir-
cumstances. The QRH procedure, therefore, includes all items provided by
the ECAM; indeed, after a few initial items the ECAM simply refers to the
QRH procedure.
First priority, assuming fuel remains, is to attempt a relight by turning the

ignitors on and setting the thrust levers to idle. The speed should initially
be increased to 300kt to increase windmilling and improve the chance of a
relight. At this speed, the aircraft will cover approximately 2nm for every
1000ft lost. With this in mind, a suitable plan should be constructed to cover
the possibility that relight is not possible.
Whilst awaiting a relight, ensure that the emergency electrical generator is

on line and recycle FAC1 to recover characteristic speed display and rudder
trim. For communications, VHF1 and ATC1 are available in the emergency
electrical config. Due to lack of engine bleeds, a slow depressurisation will
be occurring, so be ready to don oxygen masks.
If there has been no relight after 30 seconds, the combustion chambers

should be ventilated by turning both engine masters off for 30 seconds. An-
other attempt can then be made by turning them back on. This sequence
should be repeated until successful or until APU bleed air becomes avail-
able at FL200.
Once below FL250, the APU can be started. Once below FL200, speed
should be reduced to green dot and assisted starts should be attempted. At
green dot speed, 2½nm will be covered for every 1000ft lost. Attempt to
start one engine at a time in the normal manner.
71
If a landing must be made without power, CONF 3 slats are recommend-

ed (flaps are unavailable). Vapp should be Vref+25kt or 150kt, whichever
is higher. The gear is available with gravity extension. The stabilizer will
be frozen once engine driven hydraulics are lost and elevator trimming will
cease with transition to direct law at gear extension. Therefore, gear exten-
sion should be delayed until CONF 3 and Vapp are reached. If ditching, do
not extend the gear.
If an airfield can be reached, arrange to be inbound on the runway centreline

at 4nm and 2400ft aal with CONF 1, S speed and gear up. To help achieve
this, for a clean aircraft, the following rules of thumb apply:
• A standard one minute leg holding pattern loses 8000ft and an orbit los-
es 4000ft. Thus for every 15 seconds outbound in a holding pattern, ap-
proximately 1000ft is lost.
• Wings level, 400ft is lost per nm.
For the segment inbound from 4nm, macro adjustment of glide path is avail-
able through the timing of gear and slat deployment, then micro adjustment
is available from temporarily increasing speed above Vapp. If necessary, dis-
regard slat limiting speeds. It is better to land fast then long. CONF 3, gear
down will give a glide ratio of approximately 850ft per nm.
If an airfield cannot be reached, refer to Section 2.5, “Ditching” or Sec-

tion 2.6, “Forced landing” as appropriate.
[ENG DUAL FAILURE, QRH AEP.ENG, FCOM PRO.AEP.ENG, FCTM-

PRO.AEP.ENG]
9.2. Single Engine failure

Defined as a rapid decrease in EGT, N2 and FF, followed by a decrease
in N1. The crew must determine whether the engine has been damaged or
whether a simple flame-out has occurred. Indications of damage are loud
noises, significantly increased vibration or buffeting, repeated or uncon-
trollable engine stalls or abnormal post-failure indications (e.g. hydraulic
fluid loss, zero N1 or N2 etc.).
72
Firstly, the ignitors are turned on to protect the remaining engine and to
confirm an immediate relight attempt. The thrust lever of the failed engine
is then moved to idle (PF moves the lever after confirmation from PNF).
If the FADEC hasn’t relit the failed engine within 30 seconds of the fail-
ure, it is shut down with the master switch. If damage is believed to have
occurred, the associated fire button is pushed and, after 10 seconds, agent
1 discharged.
If it is believed that the engine is undamaged, a relight can be considered.

The relight procedure is fairly long and highly unlikely to be successful;
do not delay diversion and landing by attempting a relight. Also note that a
relight attempt will erase FADEC troubleshooting data.
If there is vibration and/or buffeting, attempt to find an airspeed and alti-

tude combination that minimizes the symptoms.
Refer to Section 9.3, “Single engine operation” if unable to relight the en-

gine.
[ENG 1(2) FAIL, FCOM PRO.AEP.ENG]
9.3. Single engine operation

The most pressing issue is that a single engine bleed cannot support wing
anti-ice and two packs. With the crossbleed valve selector in the normal
AUTO position, the crossbleed valve is effectively synchronised to the APU
bleed valve1 and thus will most probably be closed; wing anti-ice, if it is
in use, will be operating asymmetrically. If a fire button has been pushed,
its associated side of the pneumatic system will be locked out and thus the
only option is to turn the wing anti-ice off. PRO.NOR.SUP.AW “Minimum
Speed with Ice Accretion” provides mitigation of icing in the event of in-
operative wing anti-ice. If both sides of the cross bleed system are available,
the cross bleed valve can be manually opened at a cost of 1200ft to the sin-
gle engine gross ceiling. With the cross bleed valve open, wing anti-ice is
available, but one of the packs must be turned off2 whenever it is used.
1
The exception is that the crossbleed won't open if a bleed air duct leak is detected except during
engine start.
2
It will need to be pack 1 in Emergency Electrical config; otherwise it will generally be the pack
on the dead engine side.
73
The remaining engine must be safeguarded. To this end, continuous ignition

should be selected.
A fuel imbalance may develop. Fuel imbalance limitations are detailed in

FCOM LIM.FUEL. If the outer tanks are balanced, once the fuller inner
tank contains less than 2250kg, fuel balance will never be limiting. Since
this first occurs with approximately 5900kg of fuel remaining, fuel balanc-
ing due to balance limitations will generally not be required. Fuel may, how-
ever, still need to be crossfed to prevent fuel starvation of the remaining
engine. Balance this concern against feeding your live engine the same fuel
that was feeding your failed engine when it stopped working.
TCAS should be selected to TA to avoid unflyable climb RAs.
If a reverser is unlocked with associated buffet, speed should be limited to

240kt. See Section 9.13, “Reverser unlocked in flight” for more details of
this scenario.
If the remaining engine is operated at maximum power with the aircraft at

low speed (e.g. responding to windshear) it is possible that directional con-
trol may be lost before the flight computer protections apply. Be cautious
about reducing speed below VLS on one engine.
The main systems lost are the generator, bleed and hydraulic pump associ-
ated with the engine. Other systems may be lost depending on the reason
for the shutdown. The APU can be used to replace the lost generator and,
providing the left side of the pneumatic system is available and isolated (i.e.
cross bleed valve closed), provide pressurisation through pack 1, thus giv-
ing additional margin for the go-around. The BMCs automatically close the
engine bleeds when the APU bleed valve is opened, so it is not necessary to
manually turn them off to achieve this additional go-around margin. Note,
however, that the APU cannot support wing anti-ice.
Approach and landing will be fairly normal. The main provisos are
• Full flap should only be selected once descending on the glidepath; if

a level off is required, the landing should be CONF3 [QRH AEP.ENG
“OEI – Straight in approach”].
74
• Only Cat 3 Single is available due to the loss of the ability to split the
electrical system.[QRH OPS]
• On A319s, the autopilot cannot fly FINAL APP, NAV/VS or NAV/FPA

approaches. All modes are available for manual flight with flight direc-
tors. [FCOM LIM.AFS.GEN]
• If flying manually, consider using manual thrust to better anticipate the

rudder inputs required by thrust changes. Also consider setting rudder
trim to zero at a late stage of the approach.[FCTM PRO.AEP.ENG]
[ENG 1(2) SHUT DOWN, FCOM PRO.AEP.ENG]
9.4. Engine relight in flight

A graph showing the in flight relight envelope is provided in section
AEP.ENG of the QRH. The ceiling is 27000 ft. Automatic start is recom-
mended, but crew action is required in case of abnormal start.
To prepare for the start, ensure the affected engine master switch is turned
off and the affected thrust lever is at idle. Select ignition on the engine mode
selector and open the cross bleed. If it is anticipated starter assist may be
required, ensure wing anti ice is selected off.
To begin the start sequence, select the affected master switch on. The
FADEC will determine whether starter assist is required and will open the
start valve as needed. Both ignitors are energised as soon as the master
switch is turned on, and the HP fuel valve opens at 15% N2. Closure of the
start valve and de-energisation of the ignitors occurs at 50% N2 as normal.
Light off must occur within 30 seconds of fuel flow initiation. If uncertain
about successful relight, move the thrust lever to check for engine response.
The START FAULT ENG STALL ECAM may be disregarded if all other
parameters are normal.
[QRH AEP.ENG, FCOM PRO.AEP.ENG]
9.5. Engine stall
A stall is indicated by abnormal engine noise, flame from the engine exhaust
(and possibly inlet in extreme cases), fluctuating performance parameters,
75
sluggish thrust lever response, high EGT and/ or rapid EGT rise when the
thrust lever is advanced. The ECAM warning will be triggered when N2 is
between 50% and idle (approx 60%). If N2 is above idle, the QRH should
be used.
The ECAM simply instructs the master switch to be turned off, and then
secures the engine using the after engine shut down procedure (see Sec-
tion 9.3, “Single engine operation”). This procedure should also be followed
if a stall occurs on the ground.
In flight, if no ECAM is triggered, the affected thrust lever should be re-

tarded to idle. If the engine parameters remain abnormal, shut the engine
down with the master switch. If the parameters are normal, turn on all the
anti-icing to increase bleed demand and slowly advance the thrust lever. If
the stall recurs, the engine can be operated at low thrust settings, otherwise
it can be operated normally.
[ENG 1(2) STALL, QRH AEP.ENG, FCOM PRO.AEP.ENG]
9.6. Engine tailpipe fire

An internal engine fire may be encountered during engine start or shutdown.
It will either be seen by ground crew or may be indicated by EGT failing to
decrease after the master switch is selected off.
Start by getting the engine to a known state by ensuring the man start button
is selected off and the affected engine master is selected off.
The concept is to blow the fire out by dry cranking the engine. It is there-
fore essential that the fire button is not pressed, as this will remove exter-
nal power from the FADEC and prevent dry cranking. Firstly, a source of
bleed air must be available to power the starter. Possibilities, in order of
preference, are the APU, the opposite engine or a ground air cart. If using
the opposite engine, the source engine bleed must be on, the target engine
bleed should be off, the cross bleed should be opened and thrust increased
to provide 30 psi of pressure. If using ground air, both engine bleeds should
be off and the cross bleed opened. Once high pressure air is available, select
the engine mode selector to crank and select the man start button to on.
76
Once the fire is extinguished, select the man start button off and the engine
mode selector to normal.
As a last resort, external fire suppression agents may be used. They are,
however, highly corrosive and the engine will be a write off.
9.7. High engine vibration

The ECAM VIB advisory (N1≥6 units, N2≥4.3 units) is simply an indica-
tion that engine parameters should be monitored more closely. High VIB
indications alone do not require the engine to be shut down.
High engine vibration combined with burning smells may be due to contact
of compressor blade tips with associated abradable seals.
If in icing conditions, high engine vibration may be due to fan blade or

spinner icing. The QRH provides a drill to shed this ice, after which normal
operations can be resumed.
If icing is not suspected and if flight conditions permit, reduce thrust so that
vibrations are below the advisory level. Shut down the engine after landing
for taxiing if vibrations above the advisory level have been experienced.
9.8. Low oil pressure

The sources for the gauge on the ECAM ENG page and the ECAM warning
are different. If there is a discrepancy between the two, a faulty transducer
is the most likely cause and the engine can continue to be operated normally.
If both sources agree, the engine should be shut down by retarding its thrust
lever and selecting its master switch off and the after shutdown procedure
applied (see Section 9.3, “Single engine operation”).
[ENG 1(2) OIL LO PR, FCOM PRO.AEP.ENG]
9.9. High oil temperature

It may be possible to reduce oil temperature by increasing engine fuel flow.
77
If oil temperature exceeds 155°C or exceeds 140°C for 15 minutes, the

engine must be shut down.
[ENG 1(2) OIL HI TEMP, FCOM PRO.AEP.ENG]
9.10. Oil filter clog

If a warning occurs during a cold engine start with oil temperature <40°C,
the warning may be considered spurious. The oil filter features a bypass
mechanism, so there is no immediate problem.
[ENG 1(2) OIL FILTER CLOG, FCOM PRO.AEP.ENG]
9.11. Fuel filter clog

No immediate crew action required. I assume there is some sort of bypass
mechanism, but this isn’t apparent from the FCOM.
[ENG 1(2) FUEL FILTER CLOG, FCOM PRO.AEP.ENG]
9.12. Uncommanded reverser pressurisation

There are two valves that prevent pressure reaching the thrust reverser ac-
tuators at an inopportune moment, plus a third that commands direction of
movement. The most upstream of these, controlled by the SECs, prevents
any hydraulic pressure reaching the Hydraulic Control Unit (HCU) when
the thrust levers are not in the reverse quadrant. If this protection is lost,
the correct operation of the HCU should keep the doors properly stowed.
An HCU malfunction, however, could result in an in-flight reverser deploy-
ment. If flight conditions permit, idle thrust should be selected on the af-
fected engine.
It is unclear from the FCOM whether the ECAM indicates pressure has
reached the directional solenoid valve and hence that the reverser door jacks
are pressurised, albeit in the closed direction, although the existence of the
REV ISOL FAULT ECAM indicates that this is probably the case.
[ENG 1(2) REV PRESSURIZED, FCOM PRO.AEP.ENG]
78
9.13. Reverser unlocked in flight

If one or more reverser doors are detected as not stowed in flight, the as-
sociated FADEC will automatically command idle on the affected engine.
This should be backed up by setting the thrust lever to idle.
A warning without associated buffet is likely to be spurious. In this case

limit speed to 300kt/M.78, keep the engine running at idle and expect to
make a normal single engine approach and landing.
If there is buffet, shut the engine down and limit speed to 240kt. Full rud-
der trim may be required. The ECAM will provide one of two approach
procedures depending on how many doors are detected as not stowed:
• If all 4 doors are not stowed, it will be a flap 1 landing, with approach
speed VREF+55kt slowing to VREF+40kt below 800ft. Gear should only
be deployed once landing is assured.
• Otherwise, it will be a flap 3 landing at VREF+10kt.
[ENG 1(2) REVERSE UNLOCKED, FCOM PRO.AEP.ENG]
9.14. EIU fault
The Engine Interface Unit (EIU) receives data from the engine start system,
the auto-thrust system, the LGCIUs, the air conditioning controller and the
engine anti ice system and feeds it to its related FADEC. Thus loss of the
EIU leads to loss of auto-thrust, reverser, idle control (defaults to approach
idle) and start for the affected engine. If engine anti ice is used, the ignitors
must be manually selected.
If an engine fails whilst its associated EIU is inoperative, the usual ECAM
messages will not be generated. The failure can still be diagnosed from the
system pages and an appropriate drill can be actioned from the FCOM.
[ENG 1(2) EIU FAULT, FCOM PRO.AEP.ENG]
79
9.15. N1/N2/EGT overlimit
If the overlimit is moderate, the associated thrust lever can be retarded until
the overlimit ceases, and the flight may be continued normally.
If the overlimit is excessive, the engine should generally be shut down. If

there are over-riding factors precluding a shut down, the engine may be run
at minimum required thrust.
[ENG 1(2) N1/N2/EGT OVERLIMIT, FCOM PRO.AEP.ENG]
9.16. N1/N2/EGT/FF discrepancy
The system can detect a discrepancy between actual and displayed values
of N1, N2, EGT and fuel flow. This is indicated by an amber CHECK
beneath the affected parameter. Attempt to recover normal indications by
switching from DMC1 to DMC3. If this fails, values can be inferred from
the opposite engine.
[ENG 1(2) N1(N2)(EGT)(FF) DISCREPANCY, FCOM PRO.AEP.ENG]
9.17. Start valve fault

If a start valve fails open, remove bleed sources supplying the faulty valve.
If on the ground, turn off the MAN START button if used, and shut the
engine down with its master switch.
If the start valve fails closed, it may be that insufficient pressure is reaching
it. Try opening the cross bleed and turning on the APU bleed.
On the ground, a start may still be possible with manual operation of the
start valve.
[ENG 1(2) START VALVE FAULT, FCOM PRO.AEP.ENG]
9.18. Start faults
Start faults include ignition faults (no light off within 18 seconds of ignition
start), engine stalls, EGT overlimit (>725°C) and starter time exceedance
(2 mins max).
80
On the ground, nearly all starts are auto starts. In this case the FADEC will
automatically abort as needed. It will then automatically carry out the re-
quired dry crank phase and make further attempts. Once the FADEC gives
up, an ECAM message will instruct the crew to turn off the relevant engine
master. If the fault was a stall due to low pressure, consider another auto-
matic start using cross bleed air.
If a manual start is attempted, the crew must monitor the relevant para-
meters (the FADECs will provide some passive monitoring) and, if nec-
essary, abort the start by turning the engine master and man start button
off. The crew must then carry out a 30 second dry crank phase manually.
Note that this is not mentioned in the relevant supplementary procedure,
nor are the relevant lines displayed on the ECAM. It is probably worth hav-
ing FCOM PRO.AEP.ENG handy when carrying out manual starts.
Following an aborted start in flight, the engine master should be turned off
for 30 seconds to drain the engine. A further start attempt can then be made.
If the electrical power supply is interrupted during a start (indicated by loss

of ECAM DUs) turn the master switch off, then perform a 30 second dry
crank.
If a fuel leak from the engine drain mast is reported, run the engine at idle for
5 minutes. If the leak disappears within this time the aircraft may dispatch
without maintenance action.
[ENG 1(2) START FAULT, FCOM PRO.AEP.ENG, EOMB 2.3.8.1]
9.19. Ignition faults
Each engine has two ignitors. If both fail on a single engine, avoid heavy
rain, turbulence and, as far as possible, icing conditions.
[ENG 1(2) IGN FAULT, FCOM PRO.AEP.ENG]
9.20. Thrust lever angle sensor faults

Each thrust lever has two thrust lever angle (TLA) sensors.
81
Failure of one sensor only leads to a loss of redundancy; the proviso is that
it must have failed in a way that the system can positively detect.
More difficult is when the sensors are in disagreement. In this case, the
FADEC makes the assumption that one of the sensors is accurate and pro-
vides a default thrust setting based on this assumption:
• On the ground, if neither sensor is in a take-off position, idle power is

commanded. If one sensor is in take-off position and the other is above
idle, take-off thrust is commanded. This leaves the completely conflicted
case of one sensor at take-off and the other at idle or below; the FADEC
selects idle power as the best compromise.
• In flight, once above thrust reduction altitude the FADEC will assume
that the largest TLA, limited to CLB, is correct. The autothrust can then
manage the thrust between idle and this position. For approach (slats ex-
tended), as long as both TLAs indicate less than MCT, thrust is com-
manded to idle.
If both TLA sensors fail, the FADEC again goes for sensible defaults. On
the ground, idle thrust is set. In flight, if the thrust was TO or FLEX at the
time of failure, this setting will be maintained until slat retraction, where-
upon CLB will be selected. If the thrust was between IDLE and MCT, CLB
will be selected immediately. As soon as slats are deployed, IDLE is com-
manded; this remains the case even for go-around. Autothrust will manage
thrust between IDLE and CLB whenever CLB is assumed.
[ENG 1(2) THR LEVER DISAGREE, ENG 1(2) THR LEVER FAULT, EN-
G 1(2) ONE TLA FAULT, FCOM PRO.AEP.ENG]
9.21. FADEC faults
The FADECs have two redundant channels; loss of a single channel does
not generally require crew action. Single channel FADEC faults during start
may be considered spurious on successful application of the reset procedure
detailed in FCOM PRO.AEP.ENG
If both channels of a FADEC are lost, the thrust lever should be set to idle.
Engine indications will be lost. If all other parameters are normal (check
82
all ECAM system pages), the engine can be left running. Otherwise, shut
it down.
If a FADEC overheats, reducing engine power may reduce temperature in

the ECU area sufficiently to prevent shutdown. If on the ground the engine
must be shut down and the FADEC depowered.
[ENG 1(2) FADEC A(B) FAULT, ENG 1(2) FADEC FAULT, EN-

G 1(2) FADEC HI TEMP, FCOM PRO.AEP.ENG]
83
84
Chapter 10. Navigation
10.1. EGPWS alerts (memory item)
EPGWS alerts can be categorised into warnings and cautions. A warning
is any alert with the instruction “Pull up” or “Avoid” attached. All other
alerts are cautions. A warning may be downgraded to a caution if flying in
daylight VMC and positive visual verification is made that no hazard exists,
or if an applicable nuisance warning notice is promulgated in Company
documentation [EOMA 8.3.6].
The response to a “Pull up” type warning is to call “Pull up, TOGA”, discon-
nect the autopilot and simultaneously roll the wings level, apply full back-
stick and set TOGA power. The speedbrake should then be checked re-
tracted. Once the flight path is safe and the warning stops, accelerate and
clean up as required. Note that it is highly likely that the autothrust ALPHA
FLOOR protection will have engaged and thus the autothrust will need to
be disengaged to cancel TOGA LK mode.
An “Avoid” warning indicates that a vertical manoeuvre alone is insufficient

to prevent collision, and lateral avoiding action must also be taken. The
response is essentially the same except that instead of rolling wings level, a
turn must be initiated. The direction of the turn is at the discretion of the
pilot, with the terrain or obstacle that is the source of the warning being
displayed in red and black crosshatch on the ND.
The response to a caution is to correct the flight path or aircraft configu-

ration as necessary. A configuration warning will almost always require a
go around.
[FCOM PRO.AEP.SURV]
10.2. TCAS warnings (memory item)

TCAS warnings may be either traffic advisories ("Traffic, Traffic") or res-
olution advisories (anything else).
From 28th January 2017, new easyJet deliveries are fitted with the new
AP/FD TCAS mode. When this mode is fitted, the autopilot is capable of
85
autonomously flying the TCAS escape manoeuvre. PF simply calls “TCAS

blue, I have control" to establish who will take over if the autopilot does not
respond appropriately, then calls the FMAs and monitors the autopilot as it
flies the manoeuvre. If flying manually with flight directors and autothrust
on, the flight directors will give standard guidance to fly the manoeuvre. If
flying fully manually, the flight directors will pop up and the autothrust will
engage, although it may be necessary to set the thrust levers to the climb
gate.
If AP/FD TCAS mode is not installed or not available, the first response
to either advisory is to call “TCAS, I have control” to unequivocally estab-
lish who will be carrying out any manoeuvres. If it is a resolution advisory,
the autopilot should be disconnected and both flight directors turned off1.
The autothrust remains engaged and reverts to speed mode. A vertical ma-
noeuvre should then be flown to keep the V/S needle out of the red areas
shown on the V/S scale. ATC should then be notified (e.g “Radar, Easy 123
– TCAS RA”). When clear of conflict, return to assigned level and re-en-
gage the automatics (ATC phraseology: “Radar, Easy 123 – clear of con-
flict, returning to FL XXX”).
If a climb resolution advisory occurs on final approach, a go around must

be flown.
[FCOM PRO.AEP.SURV, CAP413 1.7]
10.3. RNAV downgrades
RNAV operations fall into three main categories:
1. RNAV approach (usually RNP 0.3)
2. RNP-1 (aka PRNAV)
3. RNP-5 (aka BRNAV)
The equipment that must be serviceable is listed in EOMB 2.3.18.3.2 for

RNAV approach and FCOM PRO.SPO.51 for RNP SID/STAR.
1
If one FD is left engaged, the autothrust will not revert to speed mode, possibly resulting in speed
decay and engagement of normal law protections.
86
The following messages indicate loss of RNAV capability:
• NAV ACCUR DOWNGRAD (MCDU and ND)2
• FMS1/FMS2 POS DIFF (MCDU)
• NAV FM/GPS POS DISAGREE (ECAM)
• CHECK IRS 1(2)(3)/FM POSITION (MCDU)3
For RNAV approaches, a go-around is mandated for any of these messages

or if GPS PRIMARY LOST is annunciated on both NDs4.
In an RNP-1 (PRNAV) environment, an RNAV downgrade may leave the

aircraft unsure of position and below MSA. The initial response is to notify
ATC with the phrase “Unable RNAV due equipment” and request reclear-
ance. An immediate climb above MSA should be considered if a suitable
alternative navigation method (e.g. radar vectors) is not available.
Some RNP-1 procedures specify additional downgrade criteria such as a re-

quirement for dual RNAV systems or GPS. If GPS is not specifically man-
dated as an additional restriction, an RNP-1 procedure may still be flown
without GPS PRIMARY: set RNP to 1, check NAV ACCURACY is HIGH
and carry out a raw data check prior to commencement (see Section 10.10,
“FM/GPS position disagree”).
Downgrades in an RNP-5 (BRNAV) environment are less critical as the

aircraft will be above MSA. The IRSs provides RNP-5 required accuracy
for two hours from last full alignment regardless of MCDU ENP, and it is
acceptable to carry out a raw data check (see EOMB 2.3.15) to confirm that
2
For RNP-1 and RNP-5 procedures, if NAV ACCUR DOWNGRAD occurs on one side only, the
procedure may be continued using the unaffected FMGC.
3
This is missing from the RNP-1 list in EOMB but is listed in the FCOM. It is not listed as a go
around criteria for RNAV approach, but continuing would seem somewhat brave…
4
If GPS PRIMARY LOST is annunciated on only one ND, the approach may be continued using
the unaffected FMGC. There is also conflict between EOMA and EOMB as to whether GPS PRI-
MARY is required at all for RNAV(VOR/DME) or RNAV(DME/DME) etc. – I've gone with the
most restrictive here.
87
RNP-5 capability is maintained. If loss of RNP-5 capability is confirmed,

inform ATC and continue with conventional navigation.
[FCOM PRO.SPO.51, EOM A.8.3.3.5, EOMB 2.3.18.3]
10.4. ADR faults
A single ADR fault simply requires switching to the hot spare and turning
the affected unit off. Loss of ADR1 will lead to the loss of the extended
functions of the EGPWS. Loss of ADR2 will lead to both baro reference
channels being driven by the same FCU channel , so the baro refs should
be checked.
Loss of two ADRs will lead to Alternate Law with associated speed restric-
tions and landing configuration considerations. Air data switching is used
as necessary, and the affected ADRs are turned off. ATC switching may be
required to restore transponder. If ADR 1 and 3 are lost, the landing gear
safety valve is controlled closed, so the gear must be gravity extended and
cannot subsequently be retracted. This is not mentioned by the ECAM –
the gear will simply fail to extend normally.
If all three ADRs are lost, the result is airframe dependent. Some of the fleet
now have a NAV ADR 1+2+3 FAULT ECAM and an appropriate proce-
dure utilising the Backup Speed Scale, completing with the QRH AEP.NAV
ALL ADR OFF paper procedure. For older airframes the ECAM displayed
will be for Dual ADR failure and must be ignored since it will request
meaningless air data and ATC switching. Instead revert to standby instru-
ments (the standby ASI and Altimeter have direct pressure feeds from the
the standby pitot and static ports) and refer to QRH AEP.NAV ADR 1+2+3
FAULT. Interestingly, when Backup Speed Scale is available, the ECAM
advises that the standby instrument indications may be unreliable…
Triple ADR failure has a few additional ramifications. Of note is loss of

automatic cabin pressure control (see Section 3.14, “Pressure controller
faults” for manual pressure control methodology), Alternate Law and grav-
ity gear extension. Of lesser concern are loss of stall warning, rudder travel
limiter frozen until slat extension and loss of auto flap retraction.
[NAV ADR 1(2)(3)(1+2)(1+3)(2+3) FAULT, QRH AEP.NAV, FCOM-
PRO.AEP.NAV]
88
10.5. ADR disagree
The ECAM message indicates that, following an ADR fault or rejection,
there is a speed or angle of attack disagreement between the two remaining
ADRs. This will cause a degradation to alternate law. If there is a speed
disagreement, see Section 2.3, “Unreliable airspeed (memory item)”. If the
speed does not disagree, an AOA sensor is providing incorrect data and
there is a risk of spurious stall warnings.
[NAV ADR DISAGREE, FCOM PRO.AEP.NAV]
10.6. RA faults
A single RA fault results in degradation of approach capability to Cat II.
Loss of both RAs will lead to direct law at landing gear extension and a loss
of ILS APPR mode capability. Therefore, landing will be CONF 3 with
associated corrections, the approach should be flown in LOC and FPA and
autopilot disconnect should be anticipated at gear extension.
[NAV RA 1(2) FAULT, FCOM PRO.AEP.NAV]
10.7. IR faults
In case of simultaneous loss of the ADR and IR associated with an ADIRU,
apply the ADR FAULT procedure first.
A single IR fault will simply require ATT/HDG switching. This may lead to
loss of the extended functions of the EPGWS and/or loss of TCAS. It may
be possible to recover the IR in ATT mode (see Section 10.9, “IR alignment
in ATT mode”).
A dual IR fault will lead to loss of PFD indications on at least one side so
use ATT/HDG switching to recover. It will also lead to Alternate Law and
associated speed restrictions and landing configuration considerations.
[NAV IR 1(2)(3)(1+2)(1+3)(2+3) FAULT, FCOM PRO.AEP.NAV]
89
10.8. IR disagree
Following rejection or failure of an IR, there is disagreement between the
two remaining IRs. Normal and alternate laws are lost, but alternate law
with reduced protections can be recovered by isolating the faulty IR (use
standby horizon to cross-check) and resetting the ELACs.
[NAV IR DISAGREE, FCOM PRO.AEP.NAV]
10.9. IR alignment in ATT mode

If IR alignment is lost, it may be possible to recover attitude and heading
information by switching the ADIRU selector to ATT and maintaining level
constant speed flight for 30 seconds. The magnetic heading will need to be
entered, the exact method being dependent on the ADIRS CDU fitted.
[IR Alignment IN ATT Mode, QRH AEP.NAV, FCOM PRO.AEP.NAV]
10.10. FM/GPS position disagree

This can be disregarded if on an ILS or LOC approach. On an overlay ap-
proach, revert to raw data. On an RNAV approach, go around unless visual.
In other flight phases, manually tune a VOR and check against either the
needle and DME on the ND or the BRG/DIST TO field on the PROG page.
If the error is greater than 3nm in the cruise or greater than 1nm for ap-
proach, raw data navigation and AP/FD selected lateral and vertical modes
should be used.
[NAV FM/GPS POS DISAGREE, QRH AEP.NAV, FCOM PRO.AEP.NAV]
90
Chapter 11. Auto-flight
11.1. FAC faults
Failure of a single FAC results in loss of redundancy and hence loss of Cat
3 Dual. In particular, a single FAC provides all the characteristic speeds
(VSW, VLS, VFE, VFE-next, VLE, VMO/MMO, Green dot, S speed and F speed).
It may be worth cross-checking against QRH OPS.OD “Operating Speeds“.
If both FACs are lost the rudder travel limit system, rudder trim control,
yaw damper and PFD characteristic speeds are lost and Alternate Law with
mechanical yaw control becomes active. Recovery of full rudder authori-
ty at flap extension should be anticipated, but use rudder with care above
160kt.
[AUTO FLT FAC 1(2)(1+2) FAULT, FCOM PRO.AEP.AUTO FLT]
11.2. Yaw damper faults

A single failure leads to loss of redundancy, and hence loss of Cat 3 Dual.
On some airframes a reset of the affected FAC can be attempted.
With a dual failure a reset of the FACs should be attempted. If the yaw
damper is not recovered, the flight controls revert to alternate law (see Sec-
tion 5.12, “Alternate Law”). Unless the failure occurred below alert height,
only Cat I will be available.
[AUTO FLT YAW DAMPER 1(2)(SYS), FCOM PRO.AEP.AUTO FLT]
11.3. Rudder trim faults

Loss of a rudder trim from a single FAC leads to loss of redundancy and
hence loss of Cat 3 Dual.
If complete loss of rudder trim occurs, an attempt should be made to reset

the FACs. If this is not successful, only Cat I is available.
[AUTO FLT RUDDER TRIM SYS(1(2) FAULT), FCOM PRO.AEP.AUT-
O FLT]
91
11.4. Rudder travel limiter faults

Loss of rudder limit functionality from a single FAC leads to loss of redun-
dancy only.
The effect of complete loss of rudder limiter functionality depends on when

the failure occurred. In general, the rudder should be used with caution
when above 160kt. An attempt should be made to recover the limiter by
resetting the FACs. If unsuccessful, full rudder travel authority may or may
not be recovered at slat extension. If a landing must be made with the rudder
travel limiter frozen in the high speed regime, max crosswind is reduced to
15kt and differential braking may be required on the landing roll (do not
arm autobrake).
[AUTO FLT RUD TRV LIM_1(2)(SYS), FCOM PRO.AEP.AUTO FLT]
11.5. FCU faults
Loss of a single channel will result in the spare channel automatically taking
over. All that is required is a cross check of the baro refs.
Loss of both channels leads to loss of all FCU and EFIS panels. The autopi-
lots, flight directors1 and autothrust are lost and parameters that are normal-
ly controlled by the panels revert to sensible default values. If the weather
radar image remains displayed, disregard it since the scale will be incorrect.
Since it will only be possible to set the QNH on the standby altimeters, the
MDA should not be set in the MCDU; instead the PM should make standard
callouts from the standby altimeter.
[AUTO FLT FCU 1(2)(1+2) FAULT, FCOM PRO.AEP.AUTO FLT]
1
Flight Directors will pop up to provide guidance in the event of a go-around.
92
Chapter 12. Hydraulics
12.1. Green + yellow systems low pressure
It may be possible to recover the yellow system using the yellow electrical
pump. Systems lost because of low air pressure in the reservoir will be re-
coverable at lower altitudes. Systems lost due to reservoir overheats may be
usable for the approach once they have cooled down.
Roll control is available from ailerons and spoiler 3. Pitch control is avail-
able from the elevators, but the THS is frozen. Yaw damping is lost. Slats
are available, but slow. Flaps are frozen. Control law reverts to alternate law
without stability protections. The autopilots are lost.
The gear must be gravity extended, but due to the frozen THS this must
be delayed until VAPP is achieved in CONF 3. Furthermore, transition to
CONF 3 must be achieved in accordance with Section 5.6, “Flaps and/or
slats fault/locked” due to the flaps being frozen. Transition to direct law on
gear deployment adds to the fun, especially as pitch trim is unavailable.
Cat 2 and 3 capability is lost. The landing will be CONF 3, most probably
with only the slats deployed; the flare attitude will be abnormal. There will
only be one spoiler (#3), no reversers, accumulator only braking and no
nose wheel steering. Hence required landing distances almost triple.
The go around, in some ways, is exceptionally straightforward. The gear

cannot be raised and the configuration should be maintained. Therefore all
that needs to be done is selecting a speed of VFE‑10. As long as the flaps
are frozen at zero, the slats can be retracted for a subsequent diversion; fuel
flow will be approximately 2.3 times normal due to the extended gear.
A paper summary is available in section AEP.HYD of the QRH, and this

should be applied once all ECAM actions are completed.
[HYD G + Y SYS LO PR, QRH AEP.HYD, FCOM PRO.AEP.HYD]
12.2. Blue + yellow systems low pressure

It may be possible to recover the yellow system using the yellow electrical
pump or the blue system using the RAT. Systems lost because of low air
93
pressure in the reservoir will be recoverable at lower altitudes. Systems lost

due to reservoir overheats may be usable for the approach once they have
cooled down.
Roll control is provided by ailerons and spoiler 5, pitch control by the THS
and left elevator. Slats and flaps are available at reduced rate. The autopilots
are lost but Normal law is retained. Speedbrake is unavailable.
Cat 2 and 3 capability is lost. Landing distances are increased due to loss
of spoilers 2, 3 and 4 and loss of #2 reverser. Approach configuration is
normal apart from slow flaps and slats and gravity gear extension (protects
green system). Nose wheel steering is lost.
Gear cannot be retracted on go-around. Fuel burn for a subsequent diversion

will be significantly greater (approx factor 2.3); see Section 8.6, “Flight
with landing gear extended” for further details.

[HYD B + Y SYS LO PR, QRH AEP.HYD, FCOM PRO.AEP.HYD]
12.3. Green + blue systems low pressure

If the blue system has been lost due to the loss of its electrical pump, it
may be recovered by deploying the RAT. Systems lost because of low air
pressure in the reservoir will be recoverable at lower altitudes. Systems lost
due to reservoir overheats may be usable for the approach once they have
cooled down.
Roll control is provided by spoilers 2 and 4 only. Use of speedbrake would

therefore lead to loss of roll control. Pitch control is available from the
starboard elevator; the THS remains available. Due to the limited control
surfaces available, the aircraft will be slightly sluggish. The slats are frozen,
but flaps are available. Control law reverts to alternate law without stability
protections. The autopilots are lost. The approach will be flown with the
autothrust off.
Due to the frozen slats, configuration changes must be carried out in accor-
dance with Section 5.6, “Flaps and/or slats fault/locked”. The gear must be
94
gravity extended; to benefit from the improved elevator response available

in direct law, this is done at 200kt. Manual trim will be available.
Cat 2 and 3 capability is lost. The landing will be CONF 3. Two spoilers per
wing are available, reverser 2 is available, alternate braking is available and
nose wheel steering is available. Landing distances approximately double.
Go around is straightforward – the gear cannot be retracted and the flap

configuration should be maintained. Simply select VFE‑10. For diversion,
the flaps can be retracted. With the gear remaining down, fuel burn will
increase by a factor of approximately 2.3.

[HYD G + B SYS LO PR, QRH AEP.HYD, FCOM PRO.AEP.HYD]
12.4. Green system low pressure

The major lost systems are normal landing gear operation (gravity exten-
sion is available but gear retraction is not) and the normal brake system,
including the autobrake (alternate braking is available). Landing distance
will be increased due to loss of two spoilers per wing and reverser 1. Flap
and slat deployment will be slow.
[HYD G SYS LO PR, FCOM PRO.AEP.HYD]
12.5. Yellow system low pressure

It may be possible to recover the yellow system by using the yellow electric
pump.
Two spoilers per wing and reverser 2 are lost, so landing distance will in-
crease slightly. Nose wheel steering is lost. Flap deployment will be slow.
As the alternate braking system is only available through the brake accu-
mulator, ensure there is sufficient pressure when the parking brake is set.
[HYD Y SYS LO PR, FCOM PRO.AEP.HYD]
95
12.6. Blue system low pressure

One spoiler per wing will be lost but this has negligible effect on landing
distance. Slats will be slow to deploy. Deployment of the RAT is not rec-
ommended unless another system is lost. If the system is lost due to low
reservoir level, emergency generation capability is lost.
[HYD B SYS LO PR, FCOM PRO.AEP.HYD]
12.7. Engine driven pump low pressure

Turn off the affected pump. The PTU will pressurise the affected system.
[HYD G(Y) ENG 1(2) PUMP LO PR, FCOM PRO.AEP.HYD]
12.8. Electric pump low pressure or overheat

Turn off the affected pump. In the case of an overheat, the pump may be re-
engaged for the approach providing the relevant FAULT light on the over-
head panel has extinguished.
[HYD Y(B) ELEC PUMP LO PR(OVHT), FCOM PRO.AEP.HYD]
12.9. Low reservoir air pressure

Loss of air pressure to a hydraulic reservoir may lead to pump cavitation
and hence fluctuating pressures. If this occurs, turn off the affected pump,
and if applicable, turn off the PTU. Cavitation reduces with altitude, so it
may be possible to reinstate the system during the descent.
[HYD G(Y)(B) RSVR LO AIR PR, FCOM PRO.AEP.HYD]
12.10. Reservoir overheat
Turn off all affected pumps and if applicable, turn off the PTU. The system
should be reinstated for the approach if it has cooled sufficiently. This is
indicated by the FAULT light going out on the overhead panel.
[HYD G(Y)(B) RSVR OVHT, FCOM PRO.AEP.HYD]
96
12.11. Low reservoir fluid level

Turn off all affected pumps and, if applicable, turn off the PTU. The af-
fected system is not recoverable. In the case of low reservoir level in the
yellow system, it is possible that the fluid from the brake accumulator may
also be lost. This usually occurs within 10 minutes of the initial warning.
Without the brake accumulator, the parking brake is not available, so chock
the aircraft before shutting down engine 1.
[HYD G(Y)(B) RSVR LO LVL, FCOM PRO.AEP.HYD]
12.12. PTU fault
In flight this indicates that either the green or yellow system is low on fluid
and has low system pressure. The PTU must be turned off to prevent over-
heating the supplying system.
[HYD PTU FAULT, FCOM PRO.AEP.HYD]
12.13. RAT fault
Indicates that either the RAT is not fully stowed, pressure is present in the
RAT stowing actuator or that the RAT pump is not available. No action is
required.
[HYD RAT FAULT, FCOM PRO.AEP.HYD]
97
98
Chapter 13. Ice and rain protection

13.1. Double AOA heat fail
If two AOA probes are affected by icing, the computers may erroneously
deselect the remaining good ADR. Switching off one of the affected ADRs
leaves the system in the state described in Section 10.5, “ADR disagree”.
[QRH AEP.A-ICE, FCOM PRO.AEP.A-ICE]
13.2. Single pitot probe heat or static port heat

fault
The ADR associated with the failed probe or port should be considered un-
reliable. ADR1 or ADR2 can be replaced with ADR3 using air data switch-
ing. If using standby instruments with ADR3 unreliable, air data informa-
tion must be monitored closely.
[ANTI ICE CAPT(F/O)(STBY) PITOT(L(R) STAT), FCOM PRO.AEP.A-ICE]
13.3. Multiple pitot heat failures

The issue with loss of anti-ice on more than one pitot probe is that it is
possible that the two unprotected pitot probes will ice up at the same time
and provide erroneous but coherent data. This leads to a situation where the
ADR associated with the remaining protected probe is locked out despite
being the single correct source.
Obviously, the first thing to do is to avoid icing conditions. If there is a

working ADR connected to a protected probe, turn one of the ADRs as-
sociated with an unprotected probe off. This ensures that an “ADR DISA-
GREE” ECAM caution is triggered by significant speed discrepancies and
ensures that the protected ADR will not be automatically deselected.
If pitot heat is lost on all probes, one of the ADRs should, again, be turned
off to ensure the “ADR DISAGREE” ECAM caution is provided. If icing is
expected, turn off a second ADR and be ready to apply unreliable airspeed
procedures (see Section 2.3, “Unreliable airspeed (memory item)”).
[ANTI ICE ALL(CAPT(F/O)+F/O(STBY)) PITOT, FCOM PRO.AEP.A-ICE]
99
13.4. Single AOA or TAT heat fault

No immediate operational effect.
[ANTI ICE CAPT(F/O)(STBY) AOA(TAT), FCOM PRO.AEP.A-ICE]
13.5. Probe heat computer failure

If applicable, deselect the affected ADR.
[ANTI ICE CAPT(F/O)(STBY) PROBES, FCOM PRO.AEP.A-ICE]
13.6. Window heat fault

No immediate operational effect.
[ANTI ICE L(R)(L+R) WINDSHIELD(WINDOW), FCOM PRO.AEP.A-ICE]
13.7. Engine anti-ice valve fault

If a valve fails to open when commanded, avoid icing conditions. If it fails
to close when commanded, a thrust limit penalty applies.
[ANTI ICE ENG 1(2) VALVE OPEN(CLSD), FCOM PRO.AEP.A-ICE]
13.8. Wing anti-ice valve open when commanded

closed
In the air, just allow the failed side to be continually anti-iced and use wing
anti-ice on the working side when required. A thrust limit penalty will apply.
On the ground, isolate and depressurize the pneumatic system on the failed
side.
[WING ANTI ICE L(R) VALVE OPEN, FCOM PRO.AEP.A-ICE]
13.9. Wing anti-ice valve closed when command-

ed open
The wing anti-ice must be turned off to avoid asymmetrically de-icing the
wings. Avoid icing conditions. If ice accretion does occur, landing distances
100
and Vapp adjustments are in QRH IFP and speed must be maintained above
the higher of VLS+10kt or Green Dot.
[WING ANTI ICE SYS FAULT, FCOM PRO.AEP.A-ICE, FCOM-

PRO.NOR.SUP.AW]
13.10. Wing anti-ice valves fail to close after

ground self-test
Simply switch off the wing anti-ice with the push button. If the valves still
do not close, see Section 13.8, “Wing anti-ice valve open when commanded
closed”.
[ANTI ICE OPEN ON GND, FCOM PRO.AEP.A-ICE]
13.11. High pressure detected when wing anti-ice

turned on
A thrust limit penalty is applied automatically.
[WING ANTI ICE L(R) HI PR, FCOM PRO.AEP.A-ICE]
101
102
Chapter 14. Indicating/ Recording
14.1. Display unit failure
Intermittent flashing of DUs may be indicative of a generator issue. If P1
DUs are flashing, try turning off generator 1. If P2 DUs are flashing, try
turning off generator 2. The APU generator can be used if successful.
In the case of a blank DU, a large amber “F”, a distorted display or minimum
brightness, on some airframes a reset may be attempted by selecting the DU
brightness to OFF then back to ON. If the reset is not applicable or the DU
does not recover after 10 seconds, the affected DU can be turned off. In
the case of an INVALID DISPLAY UNIT message, an automatic recovery
attempt is initiated; this can take 40 seconds or more. If automatic recovery
does not succeed, the DU can be turned off.
An INVALID DATA message is indicative of a DMC problem; EIS DMC

switching may recover the DU, as may turning the DU OFF then ON. It is
possible that this message will appear simultaneously on all DUs; this ini-
tiates an automatic recovery attempt, which, again, can take 40 seconds or
more. DUs that are not automatically recovered may be recovered manually
by sequentially turning them off for 40 seconds then back on. If resetting
a DU triggers a recurrence of the original problem, leave that DU off for
the next recovery cycle.
In the event of an unrecoverable failure of a display unit, some automatic

display switching will occur: PFD will auto-transfer to NDUs and E/WD
will auto-transfer to SDU. Each pilot has a PFD/ND XFR button that allows
their PFD to be toggled onto their NDU and their ND to be toggled onto
their PFDU. An ECAM/ND XFR switch on the switching panel allows ei-
ther the SD (when SDU xor E/WDU failed) or E/WD (SDU and E/WDU
failed) to be displayed on an NDU.
The most likely end result of a DU failure is that one ND must be shared
and/or that the SD is not displayed. The ECAM can be operated with just
the E/WD. When a SYS page is needed, press and hold the required SYS
page button. When STATUS is required, press and maintain the STS key.
103
The E/WD will be displayed 2s after the STS key is released. To access
STATUS overflow, release then repress the STS key within 2s.
[QRH AEP.EIS, FCOM PRO.AEP.EIS]
14.2. Multiple spurious ECAM alerts

A faulty DMC can cause multiple spurious ECAM alerts (spurious as con-
firmed by SD pages). The EIS DMC switch should be used to identify the
faulty DMC and replace it with DMC3.
[QRH AEP.FWS, FCOM PRO.AEP.FWS]
14.3. Flight Warning Computer failure

The two identical FWCs generate alert messages, memos, aural alerts, and
synthetic voice messages. Loss of a single FWC leads to downgrade to CAT
3 Single due to loss of redundancy. The major effects of loss of both FWCs
are loss of ECAM (including attention getters, status page and takeoff/land-
ing memos), loss of auto callouts1 (radio height and decision height) and
loss of altitude alerting. In the sim, there is also loss of rudder trim reset,
loss of APU fuel valve status and loss of cabin crew call alert as side-effects.
The procedure is simply to use the SYS pages and overhead panel warning
lights to monitor the systems, and for PM to make the relevant callouts. Al-
ternative method for cabin crew to get flight deck attention may be required.
[FWS FWC 1(2)(1+2) FAULT, FCOM PRO.AEP.FWS]
1
There is some question as to whether windshear and GPWS aural alerts are included under ‘auto
callouts’. The FCOM is unclear on the matter.
104
Chapter 15. Pneumatic
15.1. Dual bleed failure
The historical failure case where supplying two packs from one bleed would
overload it and cause it to fail appears to have been resolved. Furthermore,
recent airframes have four new ECAM procedures associated with dual
bleed failure, the variants based on whether neither, either or both bleeds
have failed due to a wing or pylon leak on its respective side. The ECAMs all
hand off to a new QRH paper procedure if no successful reset is achieved.
Older airframes make do with just the QRH procedure.
Whilst the procedures look complex, the underlying philosophy is fairly

simple:
• A depressurisation will be underway. It should be relatively slow, but

unless a successful reset is achieved immediately, a prompt descent to
FL100/MFA needs to be initiated.
• A bleed lost to a wing or pylon leak is lost for good, whereas a simple
bleed fault or bleed low pressure may be recoverable. The cross bleed
should be shut and the wing anti-ice should be off before an attempt is
made to recover a bleed.
• A leak on the left side precludes the use of the APU bleed for pressuri-
sation, but otherwise the APU bleed can be used to supply pack 1 when
below 22500ft. If pack 1 is unavailable, the APU bleed can supply pack
2 via the cross bleed provided the whole pneumatic system is available.
In line with this philosophy, both the ECAM and QRH procedures start
by shutting the cross bleed and turning off the wing anti-ice. The ECAM
procedures each then attempt an immediate recovery of any recoverable
bleed by cycling the bleed off then on. The QRH attempts an immediate
recovery only in the case that both bleeds are potentially recoverable.
If no bleeds are recovered, the bleeds are all turned off and a descent to
FL100/MFA is initiated. At this point, the ECAM procedures join the QRH
procedure.
105
During the descent the APU is started. If the left hand side of the pneumatic
system is available, at attempt to use the APU bleed for pressurisation is
made at FL200. If this is successful, the descent is stopped at FL200 and a
further attempt is made to reset the engine bleeds; if unsuccessful, the flight
can be continued at FL200 using the APU bleed for pressurisation.
If APU cannot be used for pressurisation descent must be continued. When

level at FL100/MFA, a final attempt is made to restore any available engine
bleeds. If unsuccessful, the flight is completed with ram air.
[AIR 1+2 BLEED FAULT (LEFT(RIGHT) LEAK (AND RIGHT LEAK))

QRH AEP.AIR, FCOM PRO.AEP.AIR]
106
Chapter 16. Communications
16.1. Communication failure (ICAO)
If all attempts to establish contact fail, transmit message twice on designated
channel, proceeded by the phrase “Transmitting Blind.”
Set Mode A Transponder Code to 7600.
If in VMC, continue in VMC to the nearest suitable airfield and land, re-
porting arrival to appropriate ATS by the most expeditious means.
If in IMC or unlikely to be able to maintain VMC:
• If in airspace where a procedural separation service is being applied,

maintain speed and level, or minimum flight altitude if higher, for a peri-
od of 20 minutes following failure to report over a compulsory reporting
point, then adjust level and speed in accordance with flight plan.
• If in airspace where an ATS surveillance system is in use, maintain speed

and level, or minimum flight altitude if higher, for 7 minutes after Code
7600 is set, then adjust level and speed in accordance with flight plan.
• If being radar vectored or having been directed to proceed offset using

RNAV without specified limit, rejoin the flight plan route no later than
the next significant point.
• On reaching the appropriate NAVAID or fix serving the destination aero-

drome, hold if necessary, then at EAT, or if no EAT has been received
and acknowledged, computed flight plan ETA, commence an appropri-
ate instrument approach procedure. If possible land within 30 minutes
of this time.
• Watch for visual signals from the tower:
• Red Pyro: Permission to land cancelled
• Flashing Red Light: Land elsewhere
107
• Continuous Red: Give way to other aircraft, continue circling
• Flashing Green: Return to circuit, await landing clearance
• Continuous Green: Permission to land
16.2. Communication failure (UK airspace)

The UK procedures expand on the ICAO procedures:
• If following a SID fly the published lateral and vertical profiles, includ-
ing any step climb, until the last waypoint of the procedure is reached.
Maintain current speed and last assigned level (or minimum flight alti-
tude if this is higher) until 7 minutes have elapsed since setting 7600.
Then adjust speed and level in accordance with current flight plan. This
procedure also applies to RNP-1 (PRNAV) departures.
• If following a STAR, follow the lateral profile but maintain current speed
and last assigned level (or minimum flight altitude if this is higher) until
7 minutes have elapsed since setting 7600. Subsequently, arrange descent
to be as close as possible to published planning profile. If no profile is
published, arrange to be at the IAF at minimum published level. This
procedure also applies to RNP-1 (PRNAV) arrivals.
• If under radar vectors from Approach Control Radar, comply with in-
structions on radar vectoring chart. If under radar vectors without speci-
fied limit from other ATS unit, continue in accordance with last instruc-
tions until 3 minutes have elapsed since setting 7600, then proceed in most
direct manner to rejoin current flight plan route. If necessary, climb to
minimum flight altitude.
• If performing an SRA, continue visually or by using an alternate ap-

proach aid. If this is not possible, carry out a missed approach and con-
tinue to the holding position of a suitable aerodrome with a notified in-
strument approach and carry out that procedure.
[ICAO Annex 10, ICAO DOC 4444, UKAIP ENR 1.1.3.4]
108
Chapter 17. Miscellaneous Tips
• When configuring, VLS is more critical than VFE, which in turn is more
critical than manoeuvring speeds (S and F speeds). Both VLS and VFE are
trustworthy with jammed flaps/slats.
• When configuring on approach, flaps do not begin to extend until CONF

2 is selected.
• Slat position does not change between CONF 2 and CONF 3.
• The AVIONICS SMOKE ECAM is non-standard. Do not run the proce-

dure from the ECAM, use the QRH procedure instead.
• The Engine Fire on the Ground procedure is non-standard. The FO must

remember to mitigate the effects of loss of electrical power (which in-
cludes loss of ECAM and non-emergency lighting) before shutting down
the second engine.
• Dual hydraulic failure fundamentals:
• You will always need to gravity extend the gear, so you will never be
able to retract it on the go-around.
• If you only have blue, you lose the flaps; if you only have yellow, you
lose the slats. The flaps/slats jammed procedure (including go-around
modifications) is therefore incorporated into both these procedures.
• If you only have blue, the THS is frozen (think

BLUE=COLD=FROZEN THS), so you need to go Direct Law late
(at Conf 3, VAPP) to get neutral trimming of the elevators. If you on-
ly have yellow, you only have one elevator (think YELLOW=COW-
ARDLY=Timid control response); combined with lack of slats this
requires going Direct Law early (at 200kt) to improve pitch response.
• You're going to need a longish runway. Worst case is if you only have
blue, since you have, at best, accumulator braking and you're coming
in fast due to lack of flaps. Yellow is better since you have alternate
109
braking, and its mainly about the lack of slats. If you have green, its
not really all that bad.
110

Airbus A320 Family Non-Normal Notes

Uploaded by

Copyright:

Available Formats

Airbus A320 Family Non-Normal Notes

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Airbus A320 Family Non-Normal Notes

Uploaded by

Copyright:

Available Formats

Airbus A320 Family

Airbus A320 Family Non-Normal Notes: Ver-

3.8. ACSC single lane failure .......................................... 25

5.1. Elevator faults ......................................................... 39

8. Landing gear ....................................................................... 61

9.6. Engine tailpipe fire .................................................. 76

12.4. Green system low pressure ...................................... 95

Changed sections have a green background, added sections have a yellow

Changes to cross references induced by Airbus re-jigging their manuals are

2. Changes since version 2.3

• Added footnote to Section 1.1, “Rejected Takeoff” to explain that the

• Added advice for a fresh takeoff attempt following an RTO to Sec-

• Deleted “Immediate VMC recovery” section; it has been removed from

• Improved Section 2.9, “Engine failure in cruise” to explain reasons for

• Added requirement for FLAP 3 landing to Section 2.10, “Single engine

• Added Section 3.3, “Landing Elevation Fault”.

• Added advice about direct law go-arounds to Section 5.11, “Direct Law”.

• Added FCTM info regarding spurious AVIONICS SMOKE ECAMs to

• Improved Section 8.4, “Asymmetric braking”.

• Added explanation of interaction between ECAM and QRH to Sec-

3. Changes since version 2.2.1

• Added description of FMGS “engine out mode” interactions to Sec-

• Updated Section 2.1, “Emergency descent (memory item)” with new Air-

• Added guidance on how to get out of TOGA LK to Section 2.2.1, “Re-

• Added note to Section 2.3, “Unreliable airspeed (memory item)” to warn

• Updated Section 2.6, “Forced landing” with new “quick” procedure for

• Updated Section 2.7, “Evacuation” to indicate that cross confirmation of

• Updated Section 2.8, “Overweight landing” to clarify that autoland up to

• Expanded Section 4.18, “DC Emergency configuration” and referenced

• Updated Section 5.6, “Flaps and/or slats fault/locked” to clarify that the

• Added advice for dutch roll encounter to Section 5.11, “Direct Law”.

• Added that autopilot may be available to Section 5.12, “Alternate Law”.

• Added guidance of how to handle “smells” to Section 6.1, “Smoke and

• Improved Section 6.1, “Smoke and fumes”.

• Added footnote to Section 7.1, “Fuel leak” to address the strange logic

• Added reference to new “quick” ditching and forced landing procedures

• Removed reference to vibrations “rapidly increasing” to above adviso-

• Updated ice accreted min speeds in Section 13.9, “Wing anti-ice valve

4. Changes since version 2.2

• Added new AP/FD TCAS mode to Section 10.2, “TCAS warnings (mem-

If a stop is required, CM1 calls “Stop” while simultaneously bringing the

If, following an RTO, a new takeoff is to be attempted, reset both FDs,

1.2. Failures during takeoff when above V1

• Cancellation of master warning or master caution when both pilots con-

• Heightened awareness of the possibility of missing essential normal ac-

When applying ECAM procedures, PF is responsible for moving the thrust

Electing to fly the EOSID implies a level acceleration segment:

• Initially fly a TOGA climb at the higher of V2 or current speed, up to a

• The final segment is a MCT climb segment to MSA, either at S speed if in

TOGA may be used for a maximum of 10 minutes.

If an EOSID is annotated as “STD”, then acceleration to green dot should

Once level, restore the aircraft to a normal configuration. When safe to do

2.2. Windshear (memory item)

When on the ground, windshear is only indicated by significant airspeed

If a warning occurs when airborne, call “Windshear, TOGA”, apply TOGA

In severe windshear, it is possible that ALPHA FLOOR protection will

Alerts are categorised as advisory, caution or warning, in increasing order

All types of alert produce an indication of windshear position on the ND,