ECAM philosophy

ECAM Philosophy 1
 Sequence

Crew coordination

“Engine Fire in Flight” example

The “IF” condition

ECAM Philosophy 2
Crew coordination in abnormal situation

First pilot who notices:

 Announces title of the failure
 Resets Master Caution/Master Warning (if applicable)
 Other pilot confirm

Consider automation use

No action is taken until:

 Appropriate flight path established
 Aircraft at least 400 ft AGL above runway

ECAM Philosophy 3
 Crew coordination
PF: PNF:
Confirm ECAM / SD

 Requests “ECAM Action ”  Performs ECAM actions

(Flies & communicates) (System/system)
Call ECAM actions My Radio”

Both pilots should confirm

irreversible/guarded actions

 Requests clear (system)

 Checks ECAM actions
completed & Confirms clear

ECAM Philosophy 4
 Crew coordination
PF: PNF:
STATUS (OEB or Computer Rests -yes/no)
• Reads STATUS line by line
 Checks limitations

 Considers PROC if applicable

 Checks Landing distance &

speed increments (QRH)

 Checks INOP systems

 Requests “Remove Status”

 Confirms –Remove Status

 “ECAM actions completed”
If time permits, review FCOM procedure
(OEB Reminder)
Return to normal task sharing

ECAM Philosophy 5
 Crew coordination
Captain: First officer:

Situation assessment-DODAR

 Decision

Information
ATC ,NITS, Ops

Standard Briefing + Status Briefing

ECAM Philosophy 6
 The “IF” condition

When reaching such a condition, prior to any

action, first check the affected parameter

Here, check CAB V/S on DOOR/OXY page.

“IF” parameter is in normal range, no action is

required (apart from monitoring)

Note: do not forget to refer to FCOM vol 3 for

expanded information

ECAM Philosophy 7
 “Engine Fire in Flight” example

ECAM Philosophy 8
 “Engine Fire in Flight” example

Consider automation use

Ensure safe flight path and

sufficient height/altitude

ECAM Philosophy 9
“Engine Fire in Flight” example

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

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

“Confirm”

“Confirmed”
ECAM Philosophy 12
“Engine Fire in Flight” example

ECAM Philosophy 13
“Engine Fire in Flight” example

“Confirm”
“Confirmed”

ECAM Philosophy 14
“Engine Fire in Flight” example

ECAM Philosophy 15
 “Engine Fire in Flight” example

ECAM Philosophy 16
“Engine Fire in Flight” example

“Confirm”

“Confirmed”
ECAM Philosophy 17
“Engine Fire in Flight” example

ECAM Philosophy 18
“Engine Fire in Flight” example

ECAM Philosophy 19
“Engine Fire in Flight” example

ECAM Philosophy 20
“Engine Fire in Flight” example

ECAM Philosophy 21
“Engine Fire in Flight” example

“Clear Engine Shutdown?”

“Clear”

ECAM Philosophy 22
“Engine Fire in Flight” example

ECAM Philosophy 23
“Engine Fire in Flight” example

“Clear Air?”
“Clear”
ECAM Philosophy 24
“Engine Fire in Flight” example

“Clear HYD?”
“Clear”
ECAM Philosophy 25
“Engine Fire in Flight” example

“Clear ELEC?”
“Clear”
ECAM Philosophy 26
“Engine Fire in Flight” example

“Clear HYD?”
“Clear”
ECAM Philosophy 27
“Engine Fire in Flight” example

“Clear F/CTL?”
“Clear”
ECAM Philosophy 28
“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”
ECAM Philosophy 29
“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

ECAM Philosophy 30
 Summary
ECAM HANDLING
(a) First Pilot to notice or PNF if AP not engaged; Cancel ‘Master Warning’ or ‘Master
Caution’.
Read Title except during takeoff (PNF announces “engine fire” or “engine failure”
only until confirmation point - minimum 400 AAL)

(b) When appropriate PF announces, “My radios, ECAM actions”.

(c) PNF reads failure title again and commences procedure. The PNF should review the
overhead panel and/or associated SD to analyze and confirm the failure, prior to
taking any action, and should bear in mind that the sensors used for the SD are
different from the sensors that trigger failure
Task sharing according to QRH Section (General).
When all actions of that section (i.e. between underlined titles) have been completed
PNF says, “Clear title?”
PF replies, “Clear title.”
PNF continues with all other sections, repeating these steps until last action
complete

ECAM Philosophy 31
 Summary
ECAM HANDLING
(d) If ‘LAND ASAP’ displayed PNF reads “LAND ASAP red” (or amber) as appropriate
and ensures that PF acknowledges this.
PNF then says, “Secondary failures”
PNF then reads each affected system title in turn and using the system page
paraphrases the affected system. e.g. “Electrics, GEN 1 not available, GEN 2
supplying AC Bus 1 and 2.”
After paraphrasing each system.
PNF offers, “Clear (title e.g. Hydraulics)”
PF replies, “Clear title.”
When the last affected system is cleared the STATUS page appears.
(e) At this stage the crew may pause and complete other tasks as appropriate.
Before proceeding to the status, Computer resets checklists and OEB’s should be
considered.

(f) PNF offers, “STATUS?”

PF replies, “Read STATUS.”
PNF actions drills where possible, reads precisely what is displayed, notes any
items for action later, e.g. VAPP increments, manual gear extension, landing with
Flaps/ Slats jammed ( make hand written note)

ECAM Philosophy 32
 Summary
ECAM HANDLING
(g) PNF reads INOP SYSTEMS. After the last one is read;
PNF offers, “remove STATUS?”
PF replies, “remove STATUS.”
PNF replies, “ECAM actions complete, my radios”.

(h) If a pause is required, PF says, “Stop ECAM.” Then when ready to continue,
“Continue ECAM.

(i) In the case of an engine failure or fire during takeoff at minimum 400ft AAL,
PFcalls, “Read ECAM.” PNF reads ECAM failure title followed by PF.
PF says, “My radios, ECAM actions.”
PF may say, “Stop ECAM” at any point, but it is recommended to secure the engine
in the case of fire or failure with damage before accelerating. To resume ECAM, PF
calls, “Continue ECAM.”

ECAM Philosophy 33
 DODAR - Process
During abnormal and emergency procedures, task sharing will be in accordance with
Airbus FCOM and QRH section (General).
In addition to the QRH and ECAM, Flight Crew should use the DODAR process to
assess both the causes of an abnormal / emergency situation and the required further
action.
The process is intended to give the trained crew some additional thoughts and
guidelines in the event of abnormal situations.
• D - Diagnosis
• O - Options
• D - Decide
• A - Assign tasks and Action
• R - Review decision
In the case of abnormal landing configurations, the CM1 should consider being PF for
landing.
A cabin crew briefing in the Nature of the situation, Intention, Time available, Special
instructions (NITS) format will be required. The cabin crew should be informed of a
normal / precautionary or emergency landing.

ECAM Philosophy 34
 DODAR - Process
D - Diagnosis
Use all resources to identify the symptoms. What exactly is the failure?
Beware of confirmation bias - ie. the tendency to ignore symptoms that do not support
the initial diagnosis. Having identified the failure, what exactly are the consequences -
for example, how will the landing and deceleration be affected?

O - Options
What precisely are the options? Is an immediate diversion necessary or is continuing to
the destination a viable option? Should the SCCM be called to the flight deck
immediately? Has any other crew member identified an alternative option?

D – Decide
As there may not be a perfect solution, the crew must identify the best option.
Are all crew members aware of the decision?

A - Assign tasks and Action

Consider the workload and individual crew member’s experience when assigning tasks.

R - Review decision
Is the original plan still the best option? Are there any new factors to consider? Should
the cabin be prepared for an emergency landing?
ECAM Philosophy 35