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
 DETECTION
PF PNF

First pilot who notices: MASTER

WARN

MASTER CAUTION/MASTER WARNING……………RESET

MASTER
ANNOUNCE………………………...…..”TITLE OF FAILURE” 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.

 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 ACTIONS COMPLETE……………..….CHECK
CONFIRM…………….….….. CLEAR “name of SYS” ECAM……………………….……………………..CLEAR

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 :

 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”?
CONFIRM………… CLEAR “name of SYS”
SYSTEM DISPLAY…………….………..CLEAR

This is to be repeated for each failure displayed on the ECAM.

 STATUS
PF PNF
REQUEST….………………………………..STATUS?

CONFIRM………………..……………READ STATUS
STATUS …………………………………...……..READ
• LIMITATIONS
• DEFERRED PROC
• INFOS
• INOP SYS
After STATUS page consultation and if required :
VAPP & LANDING DIST…………….……COMPUTE

REQUEST………………………… Remove STATUS ?

CONFIRM……………………………Remove STATUS
STATUS…………………………………………Remove

ANNOUNCE………ECAM ACTIONS COMPLETED

RETURN TO NORMAL TASK SHARING

Landing distance and approach speed

computation:

Landing distance
QRH
Approach speed computation
1.00
SITUATION ASSESSMENT / DECISION

Taking into account :

Limitations

Weather

Operational & Commercial

considerations

DECISION NOTIFY
ATC
PURSER / PAX
OPS …
 SYNTHESIS
PF PNF

FLY / NAV

ECAM ACTIONS
COM
(until STATUS page)

Consider:
T Normal C/L
OEB
E Computer resets

A
ENGINE FIRE EXAMPLE
M CONTINUE ECAM
(STATUS page)

DECISION
W
APPROACH
PREPARATION O
Briefing
R
K APPROACH C/L

ECAM DEFERRED
PROC (if any)
 ENGINE FIRE EXAMPLE
PF PNF
THE END...
 Confirmation from both pilots is required,
when the action concerns…

…Any guarded switch …Any Irreversible …Any actions on Thrust levers

actions on
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 ?

 Confirmation from both pilots is required,
when the action concerns…

…Any guarded switch …Any Irreversible …Any actions on Thrust levers

actions on
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 ?
RELATED CONTROL…………CHECK
ANSWER.……………………CONFIRM

ACTION…………………………….PERFORM
 Confirmation from both pilots is required,
when the action concerns…

…Any guarded switch …Any Irreversible …Any actions on Thrust levers

actions on
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 ?
RELATED CONTROL…………..….CHECK
ANSWER………………..………..CONFIRM

ACTION…………………………….PERFORM
 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 ACTIONS COMPLETE……………..….CHECK
CONFIRM…………….….…. .CLEAR “name of SYS” ECAM……………………….……………………..CLEAR

LAND
LAND ASAP
ASAP
Depending
This is toon
bethe failure,
repeated LAND
for each ASAP
failure , or on LAND
displayed ASAP
the ECAM. , may
Example : be

displayed, in the right column of the ECAM procedure.

RED LAND ASAP : Land at the next suitable airport.

As soon as he announced “ECAM ACTIONS”,
the PF is in charge of communications, until
AMBERall the
PF
ECAM
LAND actions :have
ASAP Assess
beenthe seriousness of the situation and consider
completed.

COMMUNICATE
the selection of a suitable airport.

 Actions to be confirmed by both pilots :

 STATUS
PF PNF
REQUEST….………………………………..STATUS?

CONFIRM………………..……………READ STATUS
STATUS …………………………………...……..READ
• LIMITATIONS
• DEFERRED PROC
The PNF should not start reading the STATUS before confirmation from the PF.
• INFOS
• INOP SYS
For any priority reason Status analysis can be postponed by PF
e.g. C/L, ATC communication… After STATUS page consultation and if required :
VAPP & LANDING DIST…………….……COMPUTE
In some cases, some other checks or actions may have to be performed, before reading the STATUS :
REQUEST…………………………CLEAR STATUS ?
 In case of failure at takeoff, the NORMAL
CONFIRM……………………………CLEAR STATUS TAKEOFF C/L has to be performed
QRH

 OEB (if applicable) is to be applied at that time (Refer toSTATUS…………………………………………CLEAR

QRH 6.00), 6.00
QRH
ANNOUNCE………ECAM ACTIONS COMPLETED
 Computer resets may be considered (Refer to QRH 2.00)
2.00
RETURN TO NORMAL TASK SHARING

Landing distance and approach speed

computation: Review FCOM procedure if time permits :

For complex procedures (dual hydraulic failure or electrical Applying ECAM procedure ensures flight
safety.
emergency configuration): Use SUMMARY 3
QRH However, referring to FCOM, if time permits,
For other cases: may provide useful additional information.
Landing distance 1.00

Approach speed computation

 LANDING DISTANCE COMPUTATION

QRH
APPR SPD-LDG DIST CORRECTIONS
FOR FAILURES
2.00
FAILURE A NORM (1) - 1.1
Determine the landing distance SYS
coefficient. FAILURE A 3 10 1.2

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.
 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 Δ

LDG CONF
 Select CONF FULL
VAPP VLS

FULL  Read VREF = VLS CONF FULL

 Add ΔVREF to VREF
 Add wind correction, if applicable
 Enter VAPP manually
LDG CONF
CONF 3
If LDG in CONF 3 :
 Select CONF 3
Wind correction only
applies when ΔVREF is
lower than 20 kts.
Note: This computation must be done according
to the appropriate weight at destination, so, with
F-PLN properly updated.

If the ECAM shows a ΔVLS :

 APPROACH SPEED COMPUTATION

The ECAM shows a ΔVLS, while the QRH shows a ΔVREF .

Shown on PFD, ΔVREF

when landing
ΔVLS
shown shown
conf is
on on
selected
ECAM QRH

Speed increase for

handling qualities
VLS OF THE
LANDING CONF
VLS increase due to
the actual
configuration VREF =
VLS CONF FULL
 STATUS
PF STATUS page PNF
REQUEST….………………………………..STATUS?

CONFIRM………………..……………READ STATUS
STATUS …………………………………...……..READ
•LIMITATIONS
•DEFERRED PROC
•INFOS
•INOP SYS
Limitations
If required :
VAPP & LANDING DIST…………….……COMPUTE
Deferred PROC
REQUEST…………………………CLEAR STATUS ?
INOP systems
CONFIRM……………………………CLEAR
Limitations STATUS
corrections to apply for landing
STATUS…………………………………………CLEAR

Infos ANNOUNCE………ECAM ACTIONS COMPLETED

RETURN TO NORMAL TASK SHARING

Landing distance and approach speed

computation: Review FCOM procedure :

For complex procedures (dual hydraulic failure or electrical Applying ECAM procedure ensures flight
safety.
emergency configuration): Use SUMMARY 3
QRH However, referring to FCOM, if time permits,
For other cases: may provide useful additional information.
Landing distance 1.00

Approach speed computation

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 19

“Engine Fire in Flight” example

Consider automation use

Ensure safe flight path and

sufficient height/altitude

SOP ABNORMAL – EMERGENCY 20

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 21

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

SOP ABNORMAL – EMERGENCY 22

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

“Confirm”

“Confirmed”
SOP ABNORMAL – EMERGENCY 23
“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 24

“Engine Fire in Flight” example

“Confirm”
“Confirmed”

SOP ABNORMAL – EMERGENCY 25

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 26

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 27

“Engine Fire in Flight” example

“Confirm”

“Confirmed”
SOP ABNORMAL – EMERGENCY 28
“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 29

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 30

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 31

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 32

“Engine Fire in Flight” example

“Clear Engine Shutdown?”

“Clear”

SOP ABNORMAL – EMERGENCY 33

“Engine Fire in Flight” example

SOP ABNORMAL – EMERGENCY 34

“Engine Fire in Flight” example

“Clear Air?”
“Clear”
SOP ABNORMAL – EMERGENCY 35
“Engine Fire in Flight” example

“Clear HYD?”
“Clear”
SOP ABNORMAL – EMERGENCY 36
“Engine Fire in Flight” example

“Clear ELEC?”
“Clear”
SOP ABNORMAL – EMERGENCY 37
“Engine Fire in Flight” example

“Clear HYD?”
“Clear”
SOP ABNORMAL – EMERGENCY 38
“Engine Fire in Flight” example

“Clear F/CTL?”
“Clear”
SOP ABNORMAL – EMERGENCY 39
“Engine Fire in Flight” example

Check OEB if any (OEB reminder * )

Review FUEL imbalance limitations (FCOM) 3.01.28

Review Landing distance QRH (2.27 - 4.03)

Consider APU start

Review INOP SYS

“Remove STS?”
“Remove”
SOP ABNORMAL – EMERGENCY 40
“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

SOP ABNORMAL – EMERGENCY 41