1. ABN PROC - ECAM PROCEDURES - ECAM PHILOSOPHY
END PF
PNF
DETECTION
FLY THE A/C
NAVIGATE
COMMUNICATE
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
SITUATION ASSESSMENT
DECISION
SYNTHESIS
A320 – REV05

2. First pilot who notices:
DETECTION PF
PNF
First pilot who notices:
MASTER CAUTION/MASTER WARNING……………RESET
ANNOUNCE………………………...…..”TITLE OF FAILURE”
MASTER
MASTER
WARN
WARN
MASTER
MASTER
CAUT
CAUT
FLY THE AIRCRAFT
NAVIGATE
CONSIDER AUTOMATION USE : A/THR, AP
If failure at takeoff:
NO ACTION until
400ft AGL
, with safe flight path established.

3. PF PNF COMMUNICATE Actions to be confirmed by both pilots :
ECAM ACTIONS PF
PNF
ECAM……..CONFIRM using SD and Overhead panel
ORDER…………………………….…”ECAM ACTIONS”
COMMUNICATE when necessary……………………..
ECAM ACTION…………………….…………PERFORM
REQUEST……………………CLEAR “name of SYS”?
ECAM……………………….……………………..CLEAR
ECAM ACTIONS COMPLETE……………..….CHECK
CONFIRM…………….….….. CLEAR “name of SYS”
LAND ASAP
This is to be repeated for each failure displayed on the ECAM. Example :
As soon as he announced “ECAM ACTIONS”, the PF is in charge of communications, until all the ECAM actions have been completed. PF
COMMUNICATE
Actions to be confirmed by both pilots :

4. PF PNF This is to be repeated for each failure displayed on the ECAM.
SYSTEM DISPLAY ANALYSIS PF
PNF
If a SYSTEM page is displayed on the lower ECAM screen:
SYSTEM PAGE DISPLAYED……….ANALYSE
REQUEST…………...CLEAR “name of SYS”?
SYSTEM DISPLAY…………….………..CLEAR
CONFIRM………… CLEAR “name of SYS”
This is to be repeated for each failure displayed on the ECAM.

5. PF PNF Landing distance and approach speed computation: STATUS
REQUEST….………………………………..STATUS?
STATUS …………………………………...……..READ
LIMITATIONS
DEFERRED PROC
INFOS
INOP SYS
CONFIRM………………..……………READ STATUS
After STATUS page consultation and if required :
VAPP & LANDING DIST…………….……COMPUTE
REQUEST………………………… Remove STATUS ?
STATUS…………………………………………Remove
ANNOUNCE………ECAM ACTIONS COMPLETED
CONFIRM……………………………Remove STATUS
RETURN TO NORMAL TASK SHARING
Landing distance and approach speed computation:
Landing distance
Approach speed computation
QRH
1.00

6. DECISION Taking into account : Limitations Weather
SITUATION ASSESSMENT / DECISION
Taking into account :
Limitations
Weather
Operational & Commercial considerations
DECISION
NOTIFY
ATC
PURSER / PAX
OPS …

7. ECAM DEFERRED PROC (if any)
SYNTHESIS PF
PNF
FLY / NAV
TEAM
WORK
ECAM ACTIONS
(until STATUS page)
COM
Consider:
Normal C/L
OEB
Computer resets
ENGINE FIRE EXAMPLE
CONTINUE ECAM
(STATUS page)
DECISION
APPROACH PREPARATION
Briefing
APPROACH C/L
ECAM DEFERRED PROC (if any)

8. ENGINE FIRE EXAMPLE PF
PNF

9. THE END...

10. Confirmation from both pilots is required, when the action concerns…
…Any guarded switch
…Any Irreversible actions on
…Any actions on Thrust levers
ADIRS
PF action
Given that it may influence flight path, actions on thrust levers have to be done by the PF
MASTER SWITCH
PNF action……PF confirmation
PF action……PNF confirmation
Confirmation task-sharing ?
Confirmation task-sharing ?

11. Confirmation from both pilots is required, when the action concerns…
…Any guarded switch
…Any Irreversible actions on
…Any actions on Thrust levers
ADIRS
PF action
Given that it may influence flight path, actions on thrust levers have to be done by the PF
MASTER SWITCH
PNF action……PF confirmation
PF action……PNF confirmation
Confirmation task-sharing ?
Confirmation task-sharing ? PF
PNF
Hand on related control:
REQUEST……………….………..CONFIRM ?
ACTION…………………………….PERFORM
RELATED CONTROL…………CHECK
ANSWER.……………………CONFIRM

12. Confirmation from both pilots is required, when the action concerns…
…Any guarded switch
…Any Irreversible actions on
…Any actions on Thrust levers
ADIRS
PF action
Given that it may influence flight path, actions on thrust levers have to be done by the PF
MASTER SWITCH
PNF action……PF confirmation
PF action……PNF confirmation
Confirmation task-sharing ?
Confirmation task-sharing ?
PNF
Hand on related control:
REQUEST……………….………..CONFIRM ?
ACTION…………………………….PERFORM
RELATED CONTROL…………..….CHECK
ANSWER………………..………..CONFIRM

13. PF PNF RED : Land at the next suitable airport.
ECAM ACTIONS PF
PNF
ECAM……..CONFIRM using SD and Overhead panel
ORDER…………………………….…”ECAM ACTIONS”
COMMUNICATE when necessary……………………..
ECAM ACTION…………………….…………PERFORM
REQUEST……………………CLEAR “name of SYS”?
ECAM……………………….……………………..CLEAR
ECAM ACTIONS COMPLETE……………..….CHECK
CONFIRM…………….….…. .CLEAR “name of SYS”
LAND ASAP
LAND ASAP
Depending on the failure, , or , may be displayed, in the right column of the ECAM procedure.
RED : Land at the next suitable airport.
AMBER : Assess the seriousness of the situation and consider the selection of a suitable airport.
LAND ASAP
LAND ASAP
This is to be repeated for each failure displayed on the ECAM. Example :
LAND ASAP
As soon as he announced “ECAM ACTIONS”, the PF is in charge of communications, until all the ECAM actions have been completed. PF
LAND ASAP
COMMUNICATE
Actions to be confirmed by both pilots :

14. PF PNF Landing distance and approach speed computation:
STATUS PF
PNF
REQUEST….………………………………..STATUS?
STATUS …………………………………...……..READ
LIMITATIONS
DEFERRED PROC
INFOS
INOP SYS
CONFIRM………………..……………READ STATUS
CONFIRM………………..……………READ STATUS
The PNF should not start reading the STATUS before confirmation from the PF.
For any priority reason Status analysis can be postponed by PF
e.g. C/L, ATC communication…
In some cases, some other checks or actions may have to be performed, before reading the STATUS:
In case of failure at takeoff, the NORMAL TAKEOFF C/L has to be performed
OEB (if applicable) is to be applied at that time (Refer to QRH 6.00),
Computer resets may be considered (Refer to QRH 2.00)
After STATUS page consultation and if required :
VAPP & LANDING DIST…………….……COMPUTE
REQUEST…………………………CLEAR STATUS ?
STATUS…………………………………………CLEAR
ANNOUNCE………ECAM ACTIONS COMPLETED
QRH
CONFIRM……………………………CLEAR STATUS
6.00
QRH
2.00
RETURN TO NORMAL TASK SHARING
Landing distance and approach speed computation:
For complex procedures (dual hydraulic failure or electrical emergency configuration): Use SUMMARY
For other cases:
Landing distance
Approach speed computation
Review FCOM procedure if time permits :
Applying ECAM procedure ensures flight safety.
However, referring to FCOM, if time permits, may provide useful additional information.
02 – ABN-
EMER
QRH 3
1.00

15. SYS LANDING DISTANCE COMPUTATION
QRH
Determine the landing distance coefficient.
APPR SPD-LDG DIST CORRECTIONS FOR FAILURES
2.00
SYS
FAILURE A NORM (1)
FAILURE A
QRH
LANDING DISTANCE WITHOUT AUTOBRAKE – CONF FULL
4.00
Determine the landing distance in CONF FULL without failure
Apply the coefficient determined above to this distance.
(1) If NORM is indicated for landing configuration, and if CONF 3 is used, apply an additional 1.1 coefficient to the landing distance.

16. Δ Δ Δ APPROACH SPEED COMPUTATION
VAPP = VREF + ΔVREF + WIND CORRECTION (if applicable)
When applicable, ΔVREF is given on the QRH.
In this case: Δ Δ
MCDU PERF APPR
page Δ
Select CONF FULL
Read VREF = VLS CONF FULL
Add ΔVREF to VREF
Add wind correction, if applicable
Enter VAPP manually
LDG CONF
VAPP
VLS
FULL
Wind correction only applies when ΔVREF is lower than 20 kts.
LDG CONF
Note: This computation must be done according to the appropriate weight at destination, so, with F-PLN properly updated.
CONF 3
If LDG in CONF 3 :
Select CONF 3
If the ECAM shows a ΔVLS :

17. APPROACH SPEED COMPUTATION when landing conf is selected
The ECAM shows a ΔVLS, while the QRH shows a ΔVREF .
Shown on PFD,
when landing conf is selected
ΔVLS shown on ECAM
ΔVREF shown on
QRH
Speed increase for handling qualities
VLS OF THE
LANDING CONF
VLS increase due to the actual configuration
VREF =
VLS CONF FULL

18. RETURN TO NORMAL TASK SHARING
STATUS PF
PNF
STATUS page
REQUEST….………………………………..STATUS?
STATUS …………………………………...……..READ
LIMITATIONS
DEFERRED PROC
INFOS
INOP SYS
CONFIRM………………..……………READ STATUS
Limitations
If required :
VAPP & LANDING DIST…………….……COMPUTE
Deferred PROC
REQUEST…………………………CLEAR STATUS ?
STATUS…………………………………………CLEAR
ANNOUNCE………ECAM ACTIONS COMPLETED
INOP systems
CONFIRM……………………………CLEAR STATUS
Limitations
corrections to apply for landing
Infos
RETURN TO NORMAL TASK SHARING
Landing distance and approach speed computation:
For complex procedures (dual hydraulic failure or electrical emergency configuration): Use SUMMARY
For other cases:
Landing distance
Approach speed computation
Review FCOM procedure :
Applying ECAM procedure ensures flight safety.
However, referring to FCOM, if time permits, may provide useful additional information.
02 – ABN-
EMER
QRH 3
1.00

19. “Engine Fire in Flight” example

20. “Engine Fire in Flight” example
FLY
Consider automation use
Ensure safe flight path and sufficient height/altitude

21. “Engine Fire in Flight” example

22. “Engine Fire in Flight” example
“ECAM actions” PF

23. “Engine Fire in Flight” examplePF
“ECAM actions”
“Confirm”
“Confirmed”

24. “Engine Fire in Flight” example

25. “Engine Fire in Flight” example
“Confirm”
“Confirmed”

26. “Engine Fire in Flight” example

27. “Engine Fire in Flight” example

28. “Engine Fire in Flight” example
“Confirm”
“Confirmed”

29. “Engine Fire in Flight” example

30. “Engine Fire in Flight” example

31. “Engine Fire in Flight” example

32. “Engine Fire in Flight” example

33. “Engine Fire in Flight” example
“Clear Engine Shutdown?”
“Clear”

34. “Engine Fire in Flight” example

35. “Engine Fire in Flight” example
“Clear Air?”
“Clear”

36. “Engine Fire in Flight” example
“Clear HYD?”
“Clear”

37. “Engine Fire in Flight” example
“Clear ELEC?”
“Clear”

38. “Engine Fire in Flight” example
“Clear HYD?”
“Clear”

39. “Engine Fire in Flight” example
“Clear F/CTL?”
“Clear”

40. “Engine Fire in Flight” example
Check OEB if any (OEB reminder ) *
Review FUEL imbalance limitations (FCOM)
Review Landing distance QRH ( )
Consider APU start
Review INOP SYS
“Remove STS?”
“Remove”

41. “Engine Fire in Flight” example
“ECAM actions completed”
Situation assessment
Captain’s Decision
Information
Crew, ATC, Ops
Further strategy and/or Briefing
Return to normal task sharing
Review FCOM if time permits