Post on 26-Jan-2021
PFPF PNFPNFECAM PHILOSOPHY
A320 - Version 04b
SITUATION ASSESSMENT / DECISION
DETECTION
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY ( if required )
STATUS
LDG DISTLDG DIST
WEATHERWEATHER
OPERATIONAL ANDCOMMERCIAL
CONSIDERATIONS
OPERATIONAL ANDCOMME RCIAL
CONSIDERATIONS
NOT IFYNOT IFY
DECISIONDECISION
OPS …OPS …
PURSER / PAXPURSER / PAX
ATCATC
STAT US, or
SUMMARY
PFPF PNFPNF
First pilot who notices:
MASTER CAUTION/MASTER WARNING……….RESET
ANNOUNCE………………………...…..”TITLE OF FAILURE”
FLIES THE AIRCRAFT
NAVIGATES
1. DETECTION
If failure at takeoff:
400ft AGLNO ACTION until , with safe flight path established.
CONSIDER AUTOMATION USE : A/THR, AP
PFPF PNFPNF2. ECAM ACTIONS
ORDER…………….………………”ECAM ACTIONS”
ECAM ACTIONS COMPLETE……….CHECK
CONFIRM……….… CLEAR “name of SYS”?
ECAM ………………..………..CONFIRM (using SDand overhead panel)
ECAM ACTIONS……………….PERFORM
REQUEST………CLEAR “name of SYS”?
ECAM………………………………..CLEAR
Both pilots should confirmirreversible/guarded actions
This is to be repeated for each failure displayed on theECAM.
Example :
LAND ASAP
*Task sharing:As soon as he announced “ECAMACTIONS”, the PF is in charge ofcommunications, until all the ECAMactions have been completed.PF
PFPF PNFPNF3. SYSTEM DISPLAYS
CONFIRM………… CLEAR “name of SYS”?
SYSTEM PAGE DISPLAYED……….ANALYSE
REQUEST…………...CLEAR “name of SYS”?
SYSTEM DISPLAY…………………..CLEAR
This is to be repeated until all the displayed system pageshave been reviewed, and the STATUS page is displayed.
If a SYSTEM page is displayed on the lower ECAM screen:
PFPF PNFPNF4. STATUS
CONFIRM………………..…………READ STATUS
CONFIRM……………………………CLEAR STATUS
REQUEST….………………………………..STATUS?
STATUS …………………………………...……..READ
LIMITATIONS……………………...….….CHECKPROC………………...……………..…CONSIDERLANDING DIST&SPEED INCREMENT..CHECKINOP SYS……………………………...….CHECK
REQUEST…………………………CLEAR STATUS ?STATUS…………………………………………CLEARANNOUNCE………ECAM ACTIONS COMPLETED
Landing distance and approach speedcomputation:
•For complex procedures (dual hydraulicfailure or electrical emergencyconfiguration): Use SUMMARY
•For other cases:
Review FCOM procedure:
3
Applying ECAM procedure ensuresflight safety.However, referring to FCOM 3.02, iftime permits, may provide usefuladditional information.
02–
AB
N-
EM
ER
RETURN TO NORMAL TASK SHARING
QRH
1.00
PFPF PNFPNF5. SITUATION ASSESSMENT/DECISION
LDG DISTLDG DIST
WEATHERWEATHER
OPERATIONAL ANDCOMMERCIAL
CONSIDERATIONS
OPERATIONAL ANDCOMMERCIAL
CONSIDERATIONS
NOTIFYNOTIFY
DECISIONDECISION
OPS …OPS …
PURSER / PAXPURSER / PAX
ATCATC
STATUS, or
SUMMARY
PFPF PNFPNF6. SYNTHESIS
FLY / NAV
ECAM ACTIONS(until STATUS page)
Consider:Normal C/L
OEBComputer resets
CONTINUE ECAM(STATUS page)
APPROACH C/L
ECAM APPROACHPROC (if any)
APPROACHPREPARATION
Briefing
DECISION
COM
TEAM
WORK
PFPF PNFPNFIRREVERSIBLE / GUARDED ACTIONSCONFIRMATION
Confirmation from both pilots is required, when the action concerns:
How to proceed for confirmation ?
PNFPNFHand on related control:
REQUEST……………….………..CONFIRM ?
ACTION…………………………….PERFORM
PFPF
ACTION…………………………..….CHECK
ANSWER………………..………..CONFIRM
Master switch orADIRS control
Any guarded switch Thrust lever is a PF actiongiven that it may influence flight path
!
How to proceed for confirmation ?
PNFPNFPFPF
ACTION…………………………..….CHECK
ANSWER………………..………..CONFIRM
Hand on related control:
REQUEST……………….………..CONFIRM ?
ACTION…………………………….PERFORM
PFPF PNFPNF2. ECAM ACTIONS
ORDER…………….………………”ECAM ACTIONS”
ECAM ACTIONS COMPLETE……….CHECK
CONFIRM……………………………….CLEAR
ECAM ………………..………..CONFIRM (using SDand overhead panel)
ECAM ACTIONS……………….PERFORM
REQUEST………CLEAR “name of SYS”?
ECAM………………………………..CLEAR
Both pilots should confirmirreversible/guarded actions
This is to be repeated for each failure displayed on theECAM.
Example :
LAND ASAP
*Task sharing:As soon as he announced “ECAMACTIONS”, the PF is in charge ofcommunications, until all the ECAMactions have been completed.PF
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
LAND ASAP
LAND ASAP
PFPF PNFPNFLANDING DISTANCE COMPUTATION
SYS FAILURE AFAILURE B 3
NORM (1)
1.21.1
10
_
(1) If NORM is indicated for landing configuration, and if CONF3 is used, apply an additional 1.1 coefficient to the landingdistance.
Determine the landingdistance coefficient.
Determine the landingdistance in CONF FULLCONF FULLwithout failure
Apply the coefficientdetermined above to thisdistance.
APPR SPD-LDG DIST CORRECTIONSFOR FAILURES
LANDING DISTANCE WITHOUTAUTOBRAKE – CONF FULL
QRH
2.00
QRH
4.00
PFPF PNFPNFAPPROACH SPEED COMPUTATION
Select CONF FULLRead VREF = VLS CONF FULL
AddVREF to VREF
Add wind correction, if applicable
Enter VAPP manually
If LDG in CONF 3 :
Select CONF 3
MCDU PERF APPRpage
LDG CONFCONF 3
LDG CONF
FULL
VLSVAPP
If the ECAM shows :“APPR SPEED……….VREF+VREF”:
VAPP = VREF + VREF + WIND CORRECTION (if applicable)
Note: This computation must bedone according to the appropriateweight at destination, so, withF-PLN properly updated.
VREF is given:
On the ECAM, and
On the QRH
Wind correction onlyapplies when VREF islower than 20 kts.
PFPF PNFPNF4. STATUS
CONFIRM………………..…………READ STATUS
CONFIRM……………………………CLEAR STATUS
REQUEST….………………………………..STATUS?
STATUS …………………………………...……..READ
LIMITATIONS……………………...….….CHECKPROC………………...……………..…CONSIDERLANDING DIST&SPEED INCREMENT..CHECKINOP SYS……………………………...….CHECK
REQUEST…………………………CLEAR STATUS ?STATUS…………………………………………CLEARANNOUNCE………ECAM ACTIONS COMPLETED
Landing distance and approach speedcomputation:
•For complex procedures (dual hydraulicfailure or electrical emergencyconfiguration): Use SUMMARY
•For other cases:
Review FCOM procedure:
3
Applying ECAM procedure ensuresflight safety.However, referring to FCOM 3.02, iftime permits, may provide usefuladditional information.
02–
AB
N-
EM
ER
RETURN TO NORMAL TASK SHARING
QRH
1.00
The PNF should not start reading the STATUS before confirmation from the PF.
For any priority reason Status analysis can be postponed by PFe.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/LNORMAL TAKEOFF C/L has to be performed
OEBOEB (if applicable) is to be applied at that time (Refer to QRH 6.00),
Computer resetsComputer resets may be considered (Refer to QRH 2.00)QRH
2.00
QRH
6.00