This Topic is relevant to the whole fleet

The presentation of procedures is, as far as practicable, identical to the presentation on ECAM. The abbreviations used are identical to nomenclature on the cockpit panels. All actions or information displayed on ECAM are printed in capital letters. Other information, not on ECAM, is printed in small letters.

Expanded information is inserted in the procedure and printed in italics. It provides :

	identification of the particular failure
	explanation for actions, where the reason is not self evident
	additional background information

When several procedures are presented under the same title, the starting point of each procedure is marked by a black square. Only one procedure is applicable at a time. For example :

Black squares are also used to indicate parts of procedure, among which only one is applicable at a time. For example :

The ECAM does not display black squares.

	If an action depends on a precondition, a black dot identifies the precondition.  If the precondition appears on ECAM, it appears in large letters. If not, it appears in small letters. For example :
	Titles of the procedures appear in the following ways :

TASK SHARING

The general task sharing shown below applies to all procedures.

The pilot flying remains pilot flying throughout the procedure.

PF, the pilot flying, is responsible for :

	thrust levers,
	control of flight path and airspeed,
	aircraft configuration (request configuration change),
	navigation,
	communications.

PNF, the pilot not flying, is responsible for :

	reading aloud the ECAM and checklists,
	executing required actions or actions requested by the PF, if applicable,
	operating the engine master switch and ENG FIRE pushbutton (monitored by the PF).

MEMORY ITEMS

The following procedures are to be applied without referring to paper : Windshear , windshear ahead , TCAS , EGPWS , loss of braking, beginning of EMER DESCENT, beginning of UNRELIABLE SPEED INDICATION.

USE OF AUTOPILOT

The autopilot may be used in most failure cases, when available :

	in case of engine failure, without any restriction including autoland or CAT II / CAT III ILS.
	in case of other failures, down to 500 ft AGL in all modes, however, the AP has not been certified in all configurations and its performance cannot be guaranteed. If the pilot chooses to use the AP in such circumstances, extra vigilance is required and the AP must be disconnected if the aircraft deviates from the desired or safe flight path.

INITIATION OF PROCEDURES

Procedures are initiated on pilot flying command.

No action is taken (apart from audio warning cancel through MASTER WARN light) until

	the appropriate flight path is established,
	the aircraft is at least 400 feet above runway if a failure occurs during take-off, approach or go around. At height of 400 feet is recommended because it gives a good compromise between time necessary for stabilization and excessive delay for procedure initiation. In some emergency cases, provided the appropriate flight path is established, the pilot flying may initiate actions before this height.

If an emergency causes LAND ASAP to appear in red on ECAM, the pilot flying may initiate actions before this height.

If an abnormal procedure causes LAND ASAP to appear in amber on ECAM, the crew should consider the seriousness of the situation and the selection of a suitable airport.

LANDING DISTANCE

Any increase in landing distance resulting from an emergency or abnormality must be based on the actual landing distance in configuration FULL (Refer to 3.02.80).

ECAM

Warning Inhibition during takeoff

Some warnings (non-inhibited) appear whenever the prompting situation arises ; others (inhibited) do not appear at once if the prompting situation arises during takeoff.

CREW COORDINATION

When carrying out a procedure displayed on ECAM, both pilots must be aware of the present display. Before taking any CLEAR action, the pilots should make a cross check to confirm that there remains no blue message (except in case of no action feedback) that they can eliminate by a direct action.

NO CLEAR ACTION BEFORE CROSS-CONFIRMATION

Example of crew coordination and cross confirmation :

WARNING DISPLAY		PILOT FLYING		PILOT NOT FLYING
HYD B RSVR OVHT		READ FAILURE		READ FAILURE
BLUE ENG 1 PUMP.....OFF		TAKE ATC RADIO CTL
		REQUEST ECAM ACTION (1)		PERFORM ECAM ACTION OR REQUEST EXECUTION BY THE PF
HYD B RSVR OVHT	* F/CTL			REQUEST CLEAR
B SYS LO PR		CHECK ECAM ACTION COMPLETED
		CONFIRM CLEAR
SEAT BELTS	* F/CTL			REVIEW ALL AFFECTED EQUIPMENT SHOWN IN AMBER ON F / CTL PAGE
				REQUEST CLEAR
		CONFIRM CLEAR
STATUS				READ STATUS LINE BY LINE
APPR PROC	INOP SYS
IF BLUE OVHT OUT :	CAT 3
BLUE ENG 1 PUMP .... ON	BLUE HYD
	PART SPLRS
CAT 2 ONLY	ALTN BRK
SLATS SLOW	REV 1
				REQUEST CLEAR
		CONFIRM CLEAR

For standard calls, refer to 3.03.90.

(1)

Although it is the responsibility of the pilot flying to request ECAM actions, this does not preclude the captain from either taking control of the aircraft or ordering ECAM actions he considers to be necessary.