Flight Training Manual - A330 PDF

y
c u -tr a c k
.c
A330 & A340
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
Flight Crew Training Manual
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
MODEL NUMBERS
The aircraft models listed in the table below are covered in this Flight Crew
Training Manual.
MODEL
A330-300
A333
A340-300
A343
A340-600
A346
Model numbers are used to distinguish information peculiar to one or more, but
not all of the aircraft. Where information applies to all models, no reference is
made to individual model numbers.
DESCRIPTION
The Flight Crew Training Manual provides information and recommendations on
manoeuvres and techniques. The manual is divided into 10 chapters:
1.
FCTM Presentation.
2.
General Information.
3.
Pre-start, Start And Taxi.
4.
Take-off And Initial Climb.
5.
Climb, Cruise And Descent.
6.
Holding And Approach.
7.
Landing, Go-around & Taxi-in.
8.
Non-normal Operations.
9.
COMMS & NAV.
10.
Training Guide.
lic
1.10.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
FCTM Presentation
General
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Chapter 2 covers procedures and techniques not associated with a particular

manoeuvre or phase of flight. Chapters 3 to 7 are titled by phase of flight and
contain information about aircraft operations in that phase including, where
appropriate, operations in adverse weather conditions. Chapter 8 covers
non-normal situations and manoeuvres associated with all phases of flight.
Chapter 9 covers operational information on use of communications and
navigation equipment and TCAS. Chapter 10 contains further information to
clarify standard call-outs, the Company briefing guide and visualisations of the
flow patterns of the Nps.
h a n g e Vi
e
The FCTM describes how to operate the Airbus with descriptions of operational
techniques. It also includes background information of a more technical nature
for reference. Some of the chapters have a preface, describing the chapter in
detail for ease of reference. There is an alphabetical index at the back of the
manual. The FCTM supplements the FCOM and other Company publications
and must be read in conjunction with those manuals. If areas of conflict are
encountered, the FCOM and other Company publications are the over-riding
authorities.
CX Policy is contained in FCOM 3, where applicable and Operations Manual
Volume 2 Part 2.
The FCTM is intended to provide information in support of procedures detailed in
the Operations Manuals and techniques to help the pilot accomplish these
procedures safely and efficiently. The FCTM is written in a format that is more
general than the Operations Manual. It does not account for aircraft configuration
differences, unless these differences have an impact on the procedure or
technique being discussed.
In the case where a procedure or technique is applicable only to an aircraft with
a specific configuration, colour coding is used referring to the specific model.
SUGGESTIONS AND FEEDBACK

All FCTM holders and users are encouraged to submit questions and
suggestions regarding this manual via GroupWise to CP(A) or through IntraCX >
FOP > All Fleets: Home > Crew Tools > Manuals Feedback.
https://iconnect.cathaypacific.com/flightcrew/0,8385,14771,00.html
to
bu
y
.d o
.c
FCTM Presentation
Introduction
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
1.10.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
2.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
General Information
Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
General Information
General
Preface ..........................................................................................................2.10.1
Manual Structure ...........................................................................................2.10.1
Operational Philosophy .................................................................................2.10.2
Autopilot/Flight Director
General..........................................................................................................2.20.1
AP And A/THR Disconnect............................................................................2.20.1
Flight Mode Annunciator ...............................................................................2.20.2
Reversion And Automatic Speed Protection Modes .....................................2.20.2
Triple Click.....................................................................................................2.20.3
Interface ........................................................................................................2.20.3
FCU Handling................................................................................................2.20.3
Flight Directors ..............................................................................................2.20.3
Non-normal Configurations ...........................................................................2.20.4
ECAM Philosophy And Use

General..........................................................................................................2.30.1
Flight Phase Specific Pages..........................................................................2.30.2
ECAM Handling.............................................................................................2.30.2
Use Of Summaries ........................................................................................2.30.9
CRM And TEM

Crew Resource Management (CRM) ............................................................2.40.1
Threat And Error Management (TEM)...........................................................2.40.1
Operating Policy
Callouts .........................................................................................................2.50.1
Standard FMA Callouts .................................................................................2.50.1
Standard Phraseology...................................................................................2.50.1
h a n g e Vi
e
N
y
Flight Controls
General..........................................................................................................2.60.1
Normal Law ...................................................................................................2.60.1
Alternate Law ..............................................................................................2.60.10
Direct Law ...................................................................................................2.60.11
Backup System ...........................................................................................2.60.11
Abnormal Attitude Law ................................................................................2.60.12
Thrust Control
General..........................................................................................................2.70.1
Manual Thrust Control...................................................................................2.70.1
Autothrust ......................................................................................................2.70.2
Autothrust Operational Aspects.....................................................................2.70.5
Flight Path Vector

General..........................................................................................................2.80.1
Information Presentation ...............................................................................2.80.1
Practical Uses Of The FPV ...........................................................................2.80.2
FPV Considerations ......................................................................................2.80.4
k
lic
.d o
General Information
Table Of Contents
to
bu
m
A330/A340
FCTM
05)
lic
2.00.2
wREV 1 (6 .JUN
c
.d o
c u -tr a c k
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
This chapter provides the following general information on Airbus design
concepts and features:
lic
2.10.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
General
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Manual Structure
Operational Philosophy
ECAM Philosophy and Use
CRM/TEM
Operating Policy
Flight Controls
Thrust Control
Flight Path Vector
MANUAL STRUCTURE
FCOM 1 provides technical system information.
FCOM 2 provides selected performance and loading data for flight preparation.
FCOM 3 contains the Limitations, Non-normal Procedures, Bulletins, Normal
Procedures (NPs), Supplementary Procedures (SPs), Operational Engineering
Bulletins (OEBs) and FCOM Bulletins. The NPs set out the policy and philosophy
for the Airbus operation. The NPs ensure a standard operation based on
common phraseology and techniques whereas SPs cover situations that do not
occur on a regular basis, e.g. manual engine start.
FCOM 4 contains information relating to the design philosophy and operation of
the FMGS.
The QRH contains Non-Normal checklists, OEBs and Non-Normal manoeuvres.
The MEL details which aircraft systems may be unserviceable prior to flight and
must be consulted if a reference is specified in the Aircraft Maintenance Log.
The MEL is a Company document that uses the Airbus Master MEL (MMEL) as
its source. Regulatory requirements dictate that the MEL must be at least as
restrictive as the MMEL.
h a n g e Vi
e
OPERATIONAL PHILOSOPHY
The NPs are set out in a logical sequence and provide the structure around
which crew base their operation in order to provide a common standard. Flow
patterns are designed to allocate actions to each crew member to share the
workload. By following the flow patterns, each crew member ensures that all
actions necessary for any particular phase of flight have been accomplished
prior to the completion of the relevant checklist. Normal checklists are of the
"non-action" type, i.e. all actions should be completed from memory prior to the
checklist being called for. The response to a checklist item confirms that the
correct action has already been carried out.
SPs are accomplished only when required.
Non-Normal checklists are provided to deal with and resolve non-normal
situations on the ground or in flight and are located in FCOM 3. By contrast to
normal checklists, Non-Normal checklists are of the "action" type, i.e. the "read
and do" philosophy applies.
to
bu
y
.d o
.c
General Information
General
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.10.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.20.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
GENERAL
The autopilot is designed to fly the aircraft within the normal flight envelope. It
can be engaged shortly after take-off and is certified to Cat 3B limits. The
autopilot is engaged using the push-buttons (pbs) on the FCU and should be
disconnected using the take-over pb on the sidestick.
The autopilot automatically disengages if the aircraft flies significantly outside the
normal flight envelope limits.
AP AND A/THR DISCONNECT

When the AP is disconnected using the takeover pb on the sidestick, the audio
and visual alerts (cavalry charge, master warning light, ECAM message) are
cancelled by a second push of the sidestick priority pb. Similarly, when the
A/THR is disconnected using the instinctive disconnect pb on the thrust levers,
the audio and visual alerts (single chime, master caution light, ECAM message)
are cancelled by a second push of the instinctive disconnect pb. In both cases,
allow sufficient time between these successive actions to ensure that the alerts
are triggered, thereby ensuring that all crew are clearly alerted to the AP or
A/THR disconnect action.
h a n g e Vi
e
FLIGHT MODE ANNUNCIATOR

The FMA is located at the top of the PFD screens. It is divided into 5 columns
which indicate the operational modes of the AP, A/THR and FD. The columns
are numbered from the left and indicate the following:
Mode changes on the FMA are called by the PF, then cross-checked and
confirmed by the PNF.
As a means of attracting the crew's attention to a change on the FMA, a white
box is displayed for 10 seconds around each new annunciation. In the case of a
mode reversion, e.g. LOC/GS to HDG/V/S, the box is displayed for 15 seconds
and is accompanied by a "triple click" aural warning.
REVERSION AND AUTOMATIC SPEED PROTECTION MODES

A mode reversion is when the AP and/or A/THR modes change automatically to
ensure mode compatibility. The new mode is displayed on the FMA and
depending upon the reversion, is sometimes accompanied by triple click. When
a mode reversion occurs, the FMA should be announced in the normal manner.
If required, take the appropriate action to correct the flight path.
In some circumstances, to prevent an inappropriate speed trend, the AP may
temporarily abandon a vertical speed target to prevent the speed from either
reducing below VLS or from exceeding VMAX. In this case, the FMA modes do
not change, however the V/S indication on the FMA pulses and is boxed amber,
and a triple click is generated.
FCOM 1.22.30 refers.
to
bu
y
.d o
.c
General Information
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.20.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.20.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
TRIPLE CLICK
The triple click is an aural alert designed to draw the pilots attention to the
FMA. The FMA highlights a mode change or reversion with a white box around
the new mode, and the pulsing of its associated FD bar.
The triple click aural alert also occurs in the following less common cases:
Reversion to CLB (OP CLB) mode, if the pilot selects a speed on the FCU
while in SRS.
Inhibition of V/S mode engagement, if the pilot pulls the V/S knob while in
ALT*.
Automatic speed protection at VLS/VMAX if the V/S target is not followed
because the selected target is too high.
INTERFACE
The AP can be handled in two ways; "selected" for short-term guidance and
"managed" for long-term guidance. Short-term guidance applies to actions that
are carried out by the pilot on the FCU, e.g. in response to an ATC instruction.
Long-term guidance applies to instructions that have been programmed into the
FMGS, e.g. the flight plan. Whichever method of management is being used, the
crew must monitor AP performance through FMA indications and aircraft
response.
FCU HANDLING
When making selections on the FCU, locate the appropriate selector and then
make any change with reference to the PFD, ND or FMA as appropriate. This
method ensures that the correct target is set for the AP and/or FD.
When the AP is flying the aircraft, the PF makes the selections on the FCU.
When hand flying the aircraft, the PF requests the PNF to make the required
selections on the FCU.
FLIGHT DIRECTORS
The FDs are normally selected on when the aircraft is being flown by the AP.
The FDs give a visual indication of the AP performance. If it is suspected that the
AP/FD is not giving correct or accurate guidance, disconnect the AP, request the
PNF to select both FDs off and fly the aircraft manually. In this case, the FPV
should be selected.
When flying manually, either follow the FDs or direct the PNF to select them both
off. This ensures that the A/THR, if active, will operate in SPEED mode.
h a n g e Vi
e
NON-NORMAL CONFIGURATIONS
With one engine inoperative, the AP can be used throughout the entire flight
envelope without any restriction, including autoland.
In non-normal configurations, e.g. no flaps or no slats, the AP can be used down
to 500 ft AAL on approach. In such cases, be ready to intervene manually should
AP performance be unsatisfactory.
to
bu
y
.d o
.c
General Information
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.20.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
GENERAL
The ECAM monitors and displays all information concerning aircraft systems as
well as system failures. It is a system which, through text and graphic displays,
enables the crew to accomplish a variety of tasks, from monitoring cabin
temperature to dealing with multiple failures, without the need for paper
checklists.
Most warnings and cautions are inhibited during critical phases of flight (TO
INHIBIT and LDG INHIBIT), because most system failures will not affect the
aircrafts ability to continue a take-off or landing.
One of the major advantages of the ECAM is that it displays specific information
only when required, including flight phase specific pages. The ECAM provides
the following:
lic
2.30.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
System monitoring as follows:
Normal mode, which is flight phase related for system and memo
display.
Failure mode, which automatically displays the appropriate

non-normal procedure along with the associated system synoptic.
Advisory mode, which automatically displays the appropriate system

synoptic associated with a drifting parameter. FCOM 3 and QRH
contain recommended actions in the event of certain advisory
conditions.
Manual mode, which enables the pilot to manually select any system
synoptic via the ECAM control panel.
Memo, which displays the take-off and landing memos at the

appropriate time as well as the status of a number of systems that
are selectable by the crew, e.g. Engine Anti-Ice. Memo should be
included in the pilots routine scan.
ECAM warnings - in the event of a failure, the E/WD displays crew

actions necessary to deal with the failure, replacing the traditional
QRH. When the correct action has been carried out the applicable
line of the ECAM checklist will, on most occasions, be cleared.
However, be aware that not all action lines are cleared by carrying
out the required switch/pb action, e.g. GPWS OFF is non-reactive.
Status - the STATUS page provides an operational summary of the

aircraft systems at any stage of the flight and specifically following a
failure. If STS is displayed on the E/WD, the STATUS page is
automatically displayed on the SD when Flap 1 is selected for the
approach or when QNH is set during descent, whichever occurs first.
h a n g e Vi
e
The ECAM control panel is described in FCOM 1.31.30. The operational use of
the Emergency Cancel (EMER CANC) and Recall (RCL) pbs is as follows:
The EMER CANC pb may be used to cancel any cautions that are
considered nuisance cautions, or are displayed as a result of an
acceptable defect with the aircraft having been dispatched under the MEL.
This is indicated on the STATUS page under the CANCELLED CAUTION
title.
The RCL pb is used to either recover cancelled cautions suppressed by
the EMER CANC pb or to review warnings or cautions which have been
cleared using the CLR pb.
The EMER CANC pb may also be used to inhibit any aural alert
associated with a red warning, but it does affect the warning itself on the
E/WD.
FLIGHT PHASE SPECIFIC PAGES

On the SD, some pages are phase specific, e.g. the WHEEL page is
automatically displayed after engine start. The CRUISE page is not selectable
but is continuously displayed from 1500 ft after take-off to landing gear extension
unless a warning or caution is displayed, or a system page has been manually
selected.
The Take-off and Landing memos are only displayed at the appropriate time.
The final item on either the Before Take-off checklist or the Landing checklist is
to confirm that no blue item is present on the memo, which would indicate that a
particular action had not been carried out. Before responding "no blue", ensure
that the correct memo is displayed by reference to the memo title, i.e. T.O. or
LDG. In certain circumstances, e.g. a base training circuit, the LDG MEMO will
not automatically appear. In this case, the PNF shall read the FINAL ITEMS,
including each item of expanded LDG MEMO, from the checklist when the
aircraft is fully configured for landing.
ECAM HANDLING
General
When carrying out ECAM procedures, both pilots must be aware of the present
display. Before any clear action, both pilots shall crosscheck the ECAM display
to confirm that no blue action lines remain that can be eliminated by direct
action, other than those actions that are not sensed by ECAM, e.g. thrust lever at
idle when the FADEC is not powered.
Advisories
The crew should review the drifting parameter on the corresponding SYSTEM
page. If time permits, the PNF may refer to QRH Part 2, which contains the
recommended actions for the various advisory indications.
to
bu
y
.d o
.c
General Information
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.30.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Cautions And Warnings

When the ECAM displays a warning or caution the first priority is to maintain a
safe flight path. The successful outcome of any ECAM procedure is dependent
on the precise reading and actioning of the procedure, maintenance of correct
task sharing and deliberate monitoring and cross-checking. It is important to
remember the following:
In case of a failure during take-off, approach or go-around, ECAM actions

should be delayed until the aircraft reaches at least 400 ft AAL and is
stabilised on a safe trajectory. However, any aural warning should be
cancelled using the MASTER WARN pb.
The PF is to fly the aircraft, navigate and communicate. The use of the AP
is strongly recommended.
The PNF is to deal with the failure on command of the PF. He is
responsible for reading aloud and executing the ECAM or checklist
actions, which includes manipulation of thrust levers and engine master
switches when directed by ECAM or checklist.
Monitoring & crosschecking remain primary tasks for both PF and PNF.
ECAM actions may be stopped by the PF at any time, if other specific
actions must be performed; e.g. normal checklist, application of an OEB,
computer reset. When the action is completed, the PF shall direct to
Continue ECAM.
At any time, the Captain may take control of the aircraft or order ECAM
ACTIONS if he considers it necessary.
Either pilot may cancel an aural warning associated with an ECAM warning or
caution, but to initiate the procedure, the PNF reads the message on the E/WD,
e.g. "Air, Pack 1 overheat". The PF confirms the failure and states "Confirmed"
and then, depending on circumstances, either "Standby" or "I have control,
ECAM actions". Before applying ECAM procedures, the fault should be
confirmed on the system display.
During ECAM procedures, some selectors must be positively cross-checked by
both pilots before movement or selection to prevent the crew from carrying out
inadvertent or irreversible actions. These are:
Thrust lever
Engine master switch
Fire switch
ADIRS panel controls
All guarded pbs and switches
lic
2.30.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
The PF shall monitor all ECAM/checklist actions. Actions associated with

memory items shall be confirmed by the PF when all memory items are complete
and the aircraft is stabilized on the desired flight path. This can normally be done
by reference to ECAM MEMO. If overhead panel pbs or switch selections are to
be made, identification of the correct panel is aided by reference to the system
name, written in white at the side of each system panel. The PNF uses the
terminology of "System, Procedure/Selector, Action", e.g. "Air, Cross Bleed,
close". By using this method and announcing the intended selection prior to
execution, the PNF keeps the PF aware of the progress of the procedure.
Following a system failure, the associated amber fault light in the system pb on
the overhead panel will be illuminated to aid proper identification. When carrying
out system switch or pb selection, verify on the SD that the required action has
occurred, e.g. closing the Cross Bleed valve changes the indications on the SD.
OEBs are issued by Airbus and contain information that may have implications
for crew actions in the event of system failures. The OEBs are located in the
QRH. Depending on FWC modification status, some aircraft are fitted with an
OEB reminder function and consequently some ECAM procedures have a line
that states "REFER TO QRH PROC" rather than an ECAM checklist. In this
case, the failure should be handled with reference to the applicable OEB
procedure.
When reviewing secondary failures follow the same discipline of request and
confirmation before action on the CLR pb.
When all ECAM checklist actions have been completed, the STATUS page is
automatically displayed and should be reviewed by both pilots. A green overflow
arrow indicates further pages of status messages. To access the remaining
lines, press the STS key on the ECP.
Following certain failures, or after multiple failures, the STATUS page may
contain an excess of information. In order to extract the information essential for
landing the aircraft safely, use the following guide:
CONFIG - flap/slat setting, approach speed increment, landing distance

factor and control law for landing.
GEAR - when to lower the gear and whether normal or gravity lowering.
BRAKES - normal, alternate or alternate without anti-skid.
REVERSE - availability.
When carrying out such ECAM procedures, it is important that both crew
members cross-check the applicable landing configuration, approach speed
increment and landing distance.
Having completed the ECAM procedures and prior to reviewing the STATUS,
ensure that any relevant normal checklists have been actioned. After reviewing
the STATUS, refer to OEBs and consider any applicable computer resets.
to
bu
y
.d o
.c
General Information
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.30.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
ECAM procedures and STATUS, supplemented by a check on the PFD/ND are

sufficient for handling the fault. If time permits, and when ECAM actions have
been completed, refer to FCOM 3 procedure for supplementary information.
However in critical situations, do not prolong the flight for the sole purpose of
consulting FCOM 3.
When reviewing the STATUS prior to descent, aircraft configuration for landing
should be emphasised. During the descent and approach, the PNF should
advise the PF of the next abnormal event at a time that will keep crew workload
to a minimum. This sequence should be repeated until all items have been
reviewed and/or completed. The STATUS page is automatically recalled during
descent when QNH is set on the FCU and when slats are extended.
If an ECAM warning disappears during the completion of a procedure, it can be
assumed that the warning is no longer relevant and the applicable procedure can
be stopped. An example of this would be during an engine fire procedure and the
fire was extinguished successfully with the first fire bottle. The Engine Fire
warning would go out and the procedure can be stopped. Any remaining ECAM
procedures should be handled in the normal manner.
If an ECAM caution disappears during the completion of a procedure, the CLR
lights extinguish on the ECP and the STATUS page will not be displayed
automatically. If the STS reminder prompt is displayed, the STATUS page will
need to be manually selected to check the status items.
Multiple Cautions And Warnings

Most failures are straightforward and should not present any difficulty when
handling the related ECAM procedure. Some failures, however, can produce
multiple ECAM procedures and in these cases the following points should be
considered:
lic
2.30.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Complete all required actions (blue) associated with the first red or amber
title.
Clear the title of the first failure before dealing with next failure. Carry out
the second drill until its red/amber title can be cleared, before starting on
the third etc.
Do not leave red or amber titles on the E/WD when all actions associated
with that failure have been completed. Clear the title when the applicable
actions have been completed.
When all necessary actions have been completed there will be no red or
amber titles displayed on the lower part of the E/WD.
h a n g e Vi
e
ECAM Handling In Single Screen Mode

All screens are identical, providing redundancy either automatically or by
switching. The various options to allow switching of screens in the event of
screen failure are detailed in FCOM 1.31.05. In the case of single ECAM display
the remaining screen displays the E/WD.
There is no automatic display of the SD page associated with a failure or an
advisory and so further analysis of the failure requires the relevant system page
pb to be pressed and held. The SD page will temporarily replace the E/WD. This
also applies when reviewing secondary failures.
The STATUS page is only displayed when the STS pb is pressed and held. The
STATUS page will temporarily replace the E/WD. In order to view more pages of
status messages the STS pb must be released for less than 2 seconds and then
pressed and held again.
If the STS or system page pb is held for longer than 3 minutes, the display
automatically reverts back to the E/WD. Alternatively, the SD and STATUS
pages may be transferred to either pilots ND using the ECAM/ND Transfer
Selector. With dual screen mode reestablished once again, ECAM operation is
normal.
In the case of failure of both ECAM displays, the E/WD may be transferred to
either pilots ND using the ECAM/ND Transfer Selector to establish single screen
mode.
In the case of failure of all DMC ECAM channels, the engine parameters can be
monitored through the engine standby page, which can be displayed on the ND
by selection on the EFIS control panel.
to
bu
y
.d o
.c
General Information
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.30.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
Example Of Crew Coordination And Crosschecking
to
.d o
lic
2.30.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
bu
y
.d o
.c
General Information
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.30.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.30.9
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
USE OF SUMMARIES
General
The summaries consist of QRH procedures. They have been created to help the
crew handle the actions associated with complex failures that involve
considerable interaction between ECAM and several paper procedures.
In any case, the ECAM procedure and STATUS review should be applied first.
The PNF should refer to the corresponding QRH summary only after announcing
ECAM actions complete.
After performing ECAM actions, the PNF should begin the QRH summary by
referring to the CRUISE section, in order to determine the landing distance
factor. Since normal landing distances are also given on this page, compute the
landing distance taking failure(s) into account, in order to decide whether a
diversion is required due to insufficient runway length.
Approach Preparation
As always, approach preparation includes a review of ECAM STATUS. After
reviewing the STATUS page, the PNF should once again refer to the CRUISE
portion of the summary to determine the DVREF correction, and compute the
VAPP using VLS CONF FULL (VREF) on the MCDU updated for the new
destination. A VREF table is also provided in the summary for failure cases
leading to the loss of the MCDU.
The LANDING and GO-AROUND sections of the summary should be used for
the approach briefing.
Approach
The APPR PROC actions, annunciated on ECAM STATUS, should be
performed by reading the APPROACH section of the summary. This section has
been added primarily due to the flap extension procedure, which is not fully
addressed by the ECAM. The recommendations provided in this section are
comprehensive, and it is not necessary to refer to the LANDING WITH
FLAPS/SLATS JAMMED paper procedure
After referring to the APPROACH section of the summary, the crew should
review the ECAM STATUS, and confirm that all APPR PROC actions have been
completed.
h a n g e Vi
e
QRH Summary Sequence
to
bu
y
.d o
.c
General Information
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.30.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.40.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
CRM And TEM
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
CREW RESOURCE MANAGEMENT (CRM)

Crew resource management is the application of team management concepts
and the effective use of all available resources to operate a flight safely. In
addition to the aircrew, it involves all other groups who are involved in the
decisions required to operate a flight. These groups include, but are not limited
to, aircraft dispatchers, flight attendants, maintenance personnel and air traffic
controllers.
Throughout this manual, techniques that help build good CRM habit patterns on
the flight deck are discussed. Situational awareness and communications are
stressed. Situational awareness, or the ability to accurately perceive what is
going on in the flight deck and outside the aircraft, requires on-going questioning,
cross-checking, communication and refinement of perception.
It is important that all flight deck crew identify and communicate any situation
that appears unsafe or out of the ordinary. Experience has proven that the most
effective way to maintain safety of flight and resolve these situations is to
combine the skills and experience of all crew members in the decision making
process to determine the safest course of action.
THREAT AND ERROR MANAGEMENT (TEM)

General
Threat and error management is the process that effective crews follow to
manage the safe and efficient operation of their aircraft. This is the first time that
the industry has been able to define airmanship in a practical and simple manner
and has now become the governing philosophy that helps guide everything we
do in flight operations.
Threats are those contingencies that add additional complexity to the operation
and increase the potential for error. They can be obvious ones such as a
thunderstorm off the end of the runway or can be seemingly insignificant, such
as an ACARS printer failure. All, however, increase the potential for error and all
have to be properly managed. Good threat management requires good
anticipation, sharing the threat with the other crew and the development of a
strategy.
Error management (Resolve Phase) is the tool that the crew use to minimise the
consequence of an error. This involves the use of a combination of non-technical
(CRM) and technical (operational) skills. At its very core is the importance of
monitoring and the ability to challenge once an unsafe situation is detected.
h a n g e Vi
e
Monitoring
Effective monitoring requires sensible workload management to ensure that the
PNF is not overloaded at a critical phase of flight. This may involve delaying
certain tasks to a more appropriate time (Aviate, Navigate, Communicate).
Effective monitoring also involves the sharing of a mental model with the PNF.
This principle is known as communication of intent. In its simplest form,
communications of intent is achieved through the C-TWO departure and arrival
briefing.
Challenge
All crew members have the responsibility to advise the Commander any time
that an unsafe or potentially unsafe condition exists. The following strategy is
recommended:
Supportive statement: express personal concern, using standard calls if

possible.
Question: determine the PF's plan, e.g. "Will you be fully stabilised by
1000 ft?".
Solution: offer an alternative, e.g. "Would you like some extra track
miles?".
Action: "Captain you MUST LISTEN" or, if circumstances require, take
over.
However, we must never become over assertive to the extent that we challenge
routine decisions. The strategy recommended above is for dealing with unsafe
situations only.
to
bu
y
.d o
.c
General Information
CRM And TEM
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.40.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.50.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Operating Policy
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
CALLOUTS
Avoid casual and non-essential conversation during critical phases of flight,
particularly during taxi, take-off, approach and landing. The PF makes callouts
based on FMA changes appropriate to the flight mode. The PNF verifies the
condition from the FMA and acknowledges. If the PF does not make the required
callout, the PNF should make it. There is no competition to see who can be the
first to call these changes; the PNF should allow reasonable time for the PF to
call and not pre-empt him with every change. The PF should alert the PNF prior
to disconnecting the autopilot.
One of the basic fundamentals of CRM is that each crew member must be able
to supplement or act as a back-up for the other crew member. Correct
adherence to standard callouts is an essential element of a well-managed flight
deck. These callouts provide both crew members with the required information
about aircraft systems and confirmation of the other crew member's involvement.
The absence of a standard callout at the appropriate time may indicate a system
malfunction or the possibility of pilot incapacitation.
STANDARD FMA CALLOUTS

FCTM Ch 10 refers.
STANDARD PHRASEOLOGY
FCOM 3 and Vol 2 Pt 2 refer.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
GENERAL
The Airbus flight control surfaces are moved by commands from several flight
control computers in response to pilot input. This system is referred to as
"fly-by-wire" as there is no mechanical connection between the sidestick and the
control surfaces. The relationship between sidestick input and the aircraft
response is called the flight control law. Depending upon the status of the
fly-by-wire system, three sets of control laws are provided, i.e. Normal Law,
Alternate Law and Direct Law. In the unlikely event of a failure causing a
complete loss of the fly-by-wire system, the aircraft can be flown safely through a
backup system while the crew complete actions to recover one of the control
laws.
Each law has a set of protections and/or warnings which are discussed below.
NORMAL LAW
Under most circumstances, the aircraft is operated in Normal Law. Normal law is
designed to accommodate single system failures and has three modes:
lic
2.60.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Ground Mode
Flight Mode
Flare Mode
The transition from one mode to the next is transparent to the pilot.
Ground Mode
On the ground and at low speeds, the sidesticks have full authority over the
controls in pitch and roll. Ground mode is progressively blended out after take-off
as the flight mode becomes active.
When the aircraft is on the ground, the PFD includes a symbol (1) that is the sum
of the sidestick positions given to the flight control computers. It permits the PNF
to check that the PF is making the appropriate control input during the take-off
roll.
Small limit marks (2) indicate the limits of stick travel (16 in pitch, 20 in roll).
Do not use this display for flight control checks because it does not indicate flight
control position.
h a n g e Vi
e
Flight Mode
In pitch, when an input is made on the sidestick, the flight control computers
interpret this input as a g demand/pitch rate. Consequently, elevator deflection
is not directly related to sidestick input. The aircraft responds to a sidestick order
with a pitch rate at low speed and a flight path rate or g at high speed. When no
input is made on the sidestick, the computers maintain a 1g flight path. Pitch
changes due to changes in speed, thrust and/or configuration, which in a
conventional aircraft would require the pilot to re-trim the aircraft, are
compensated for by the computers repositioning the THS. The pitch trim wheel
moves as the control law compensates for these changes. Sometimes, changes
of trim due to changes in thrust may be too large for the system to compensate,
and the aircraft may respond to them in pitch in the conventional sense and then
hold the new attitude at which it has stabilised after the trim change.
Due to its neutral static stability, the aircraft maintains the selected flight path.
Should it deviate however, only small sidestick inputs are required to regain the
desired flight path.
to
bu
y
.d o
.c
General Information
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.60.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.60.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
In roll, when an input is made on the sidestick, the flight control computers
interpret this input as a roll rate demand. Consequently, aileron and/or spoiler
deflection is not directly related to sidestick input. When no input is made on the
sidestick, the computers maintain a zero roll rate. At bank angles less than 33
with no input being made on the sidestick, the computers maintain a zero roll
rate and, consequently, the aircraft will maintain a constant bank angle. Within
this range, there is no need to make a correction in pitch, as this will be
compensated for by the computers. Beyond 33 angle of bank, pitch
compensation is no longer available. On releasing the sidestick to neutral, the
aircraft rolls back to 33 angle of bank.
Due to its neutral static stability, within 33 angle of bank, the aircraft maintains
the selected flight path. Should it deviate however, only small inputs are required
on the sidestick to regain the desired flight path. The control law provides turn
co-ordination, so there is no need to use the rudder.
As the flight mode is always aiming to achieve the selected flight path, avoid the
temptation to over-control. The recommended method to avoid over-controlling is
to make a small sidestick input, hold for a short period and then return the
sidestick to neutral. Even in turbulent conditions, the control law resists the
disturbances well without pilot inputs. The pilot should try to limit his control
inputs to that necessary to correct the flight path trajectory and leave the task of
countering air disturbances to the flight control system. If the pilot senses an
over-control, the sidestick should be released.
In climb, cruise, descent and approach, all these basic rules remain in effect.
h a n g e Vi
e
Flare Mode
To perform the flare and landing, the flight controls need to be responsive and
linear. Therefore on reaching 100 ft on the approach the pitch law is modified to
be a full authority direct law with no auto-trim. A nose down term is introduced
which requires the pilot to maintain a backpressure on the sidestick to achieve a
progressive flare, as in a conventional aircraft. After touchdown, the control law
progressively reverts to ground mode.
Protections
Normal Law provides five different protections:
High Angle of Attack Protection

Load Factor Protection
High Pitch Attitude Protection
High Speed Protection
Bank Angle Protection
The protections are complementary and together work to maintain the aircraft in
the safe flight envelope. If an extreme manoeuvre is required, the pilot can make
full sidestick inputs in normal law at any speed. This normal law protection does
not apply to the rudder as it is not normally used in symmetrical flight.
However, it is important to remember that the normal flight envelope is defined
as VLS to VMO/MMO. Pilots should not deliberately fly at a speed outside of the
normal envelope unless absolutely necessary for operational reasons.
High Angle Of Attack Protection

The high angle of attack (AOA) protection allows the pilot to consistently achieve
the best lift while preventing the aircraft from stalling.
The following description illustrates a sequence of events that would lead to the
activation of the various stages of high AOA protection.
In level flight, if the A/THR is disengaged and thrust set to idle, the aircraft
decelerates until the auto-trim stops. This occurs at a predetermined angle of
attack called Alpha Prot. The speed that equates to Alpha Prot (Va PROT) is
displayed as the top of a black and amber strip on the PFD speed scale. If no
input is made on the sidestick, the aircraft will descend to maintain its current
AOA (Va PROT). To maintain the flight path, the pilot must increase the
backpressure on the sidestick, which also provides a tactile indication that
auto-trim has stopped. At Va PROT, AOA protection becomes active and, if the
sidestick is released to neutral and no thrust applied, the aircraft will gently
descend maintaining Va PROT. When AOA protection is active, the speed
brakes retract automatically, if previously extended, and the bank angle limit is
reduced from 67 to 45.
to
bu
y
.d o
.c
General Information
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.60.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.60.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
If the pilot maintains the backpressure, Alpha Floor (covered below) will activate.
If the pilot disconnects the A/THR while maintaining full back stick, Alpha Max
may be reached. The speed which equates to Alpha Max (Va MAX) is displayed
as the top of the red strip on the PFD speed scale. Alpha Max is close to, but
short of the 1g stall. When flying at Va MAX, the pilot can make gentle turns if
necessary. In turbulence, airspeed may fall temporarily below Va MAX without
significant effect.
h a n g e Vi
e
These features are aerodynamic protections. Additionally, there are three energy
features that enhance these protections:
With the A/THR engaged, the aircraft will not decelerate below VLS
(displayed as top of amber strip) even if the target speed is selected below
VLS.
A low energy aural warning is triggered when the aircraft energy level is
below a given threshold. This energy level is a function of several
parameters including aircraft configuration, speed, horizontal deceleration
rate, flight path angle and altitude. (FCOM 1.27.20 refers) The aural
warning "SPEED, SPEED, SPEED" alerts the pilot of the requirement to
adjust thrust and flight path. It is triggered during deceleration before Alpha
Floor (unless Alpha Floor is triggered by stick deflection). The delay
between the aural warning and Alpha Floor activation is a function of
deceleration rate.
If Alpha Prot is reached and the pilot still maintains aft sidestick, Alpha
Floor protection (set between Alpha Prot and Alpha Max) will be reached.
This protection triggers the application of TOGA thrust and the aircraft will
start to climb at a relatively constant low airspeed. Alpha floor protection is
inhibited in some cases. FCOM 1.22.30 refers.
The aircraft can also enter alpha protection at high altitude, where it protects the
aircraft from the buffet boundary. The PFD shows that alpha protection is active
in the same way as at low speed and low level: the amber and black strip rises to
the actual speed of the aircraft. As at low speed and low level, if the stick is
merely released to neutral the aircraft maintains the alpha for alpha protection.
to
bu
y
.d o
.c
General Information
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.60.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.60.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Load Factor Protection

On most commercial aircraft, the maximum load factor range is 2.5g/-1g clean
and 2g/0g with slats and/or flaps extended. The load factor protection is
designed to maintain the aircraft within these limits while allowing the crew to
consistently achieve the best achievable aircraft performance, if required.
On commercial aircraft, high load factors are most likely to be encountered when
the pilot responds to a GPWS warning. Airline pilots are not accustomed to using
"g" as a flying parameter and experience has shown that, in emergency
situations, the application of "g" is initially hesitant and then aggressive. If a
GPWS alert is generated which requires an immediate pull-up, full back stick
should be applied and maintained. The load factor protection will allow maximum
"g" to be achieved in the shortest time while preventing the aircraft from being
overstressed.
Protected/Non-Protected Aircraft Climb Angle Comparison

If the pilot maintains full aft stick because the danger still exists, the high AOA
protection will eventually take over. This is one instance where load factor
protection is enhanced by the high angle of attack protection.
h a n g e Vi
e
CIFT Escape Manoeuvres on Protected and Non-Protected Aircraft
High Pitch Attitude Protection

Excessive pitch attitudes, caused by upsets or inappropriate manoeuvres, lead
to hazardous situations. Even the most extreme emergency situations do not
require flying at excessive pitch attitude. For this reason, high pitch attitude
protection has been designed to be part of the flight control system. The high
pitch attitude protection limits the pitch attitude to +30/-15. The 30 limit
decreases to 25 at low speed. If the aircraft approaches these limits, the pitch
and roll rates start to decrease 5 before the limit so that it will stop at the limit
without overshooting.
High Speed Protection

Beyond the maximum design speed of the aircraft, VD/MD (which is greater than
VMO/MMO), there are potential aircraft control problems due to high air loads.
Therefore the margin between VD/MD and VMO/MMO must be such that any
possible overshoot of the normal flight envelope does not cause controllability
problems.
In order to protect the aircraft from dangerous phenomena at high speed, a
positive nose up "g" demand up to 1.75g is added to the pilot demand on the
sidestick when exceeding VMO/MMO. Additionally, if the side stick remains
forward, the sidestick nose down pitch authority is smoothly reduced to zero at
approximately VMO + 16/MMO + 0.04. With reference to the diagram below, if a
dive is achieved with stick free, the aircraft will slightly overshoot VMO/MMO and
fly back into the flight envelope. If a dive is achieved with the sidestick fully
forward, the aircraft will significantly overshoot VMO/MMO but without reaching
design speed limits, VD/MD.
to
bu
y
.d o
.c
General Information
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.60.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.60.9
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
When high speed protection is triggered, the autopilot disconnects, the pitch trim
is frozen, the spiral static stability is reduced from 33 to 0 of bank and the limit
bank angle is reduced from 67 to 45. If high speed protection is active with the
aircraft established in a turn, when the sidestick is released the aircraft will roll
wings level. This increased spiral stability reduces the risk of a spiral dive.
h a n g e Vi
e
Bank Angle Protection

On commercial aircraft, 30 bank angle is normally not to be exceeded. A bank
angle of 67 in level flight corresponds to the aircraft limit of 2.5 g. Therefore, 67
has been established as the bank angle limit. Approaching this limit, the roll rate
is progressively reduced to avoid over-banking.
This 67 bank angle limit is reduced to 45 in case of high speed protection.
ALTERNATE LAW
In some cases of double failure, e.g. double hydraulic failure, the integrity and
redundancy of the computers and other required systems are not sufficient to
achieve normal law with its protections. In this case, Alternate Law is triggered.
VLS remains, but prot and max disappear, replaced by a single black and
red strip, the top of which is the stall warning speed VSW. Unlike VLS which is
stable, VSW is g sensitive so as to indicate margin above stall during turns. The
autopilot may be available depending on the cause and type of failure(s). During
landing, alternate law reverts to direct law at 100 ft RA.
If the aircraft is operated outside the normal flight envelope, the pilot must take
appropriate corrective action to avoid losing control and/or to avoid high speed
excursions, since the normal law protection features may not be available.
Handling Characteristics
In pitch, handling remains similar to normal law.
In roll, depending on the failure level, control is either normal (ALTN 1) or direct
(ALTN 2). In roll direct, the aircraft appears to be very sensitive and bank stability
is no longer active.
Protections
In Alternate Law the protections change as follows:
High angle of attack protections are replaced by stall warning at 1.03 VS1g
The load factor protection is maintained
The pitch attitude protection is lost
The high speed protection is replaced by overspeed warning
The bank angle protection is maintained if roll is normal (ALTN 1) but lost
in roll direct (ALTN 2)
to
bu
y
.d o
.c
General Information
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.60.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.60.11
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
DIRECT LAW
In most cases of triple failure, e.g. triple ADR failure, direct law is triggered.
Autopilot and auto-trim are not available.
The handling characteristics are similar to a conventional aircraft. Any tendency
to roll stick free can be corrected by conventional use of the rudder. Rudder trim
can be used in the conventional way, but note that the sideslip index may be
slightly displaced from the centre once the rudder forces have been trimmed out.
Rapid speedbrake application and large thrust changes will result in significant
pitching moments, i.e. nose-up with thrust increase and nose down with thrust
reduction.
In pitch, elevator deflection is proportional to sidestick deflection. It is important
to note that the controls are very powerful. Consequently, use small inputs when
at high speed. As there is no auto-trim, use manual trim making small inputs on
the trim wheel.
In roll, aileron and spoiler deflection is proportional to sidestick deflection. Direct
law works with the yaw damper to provide a minimal turn coordination.
Protections
No protections are available but overspeed and stall aural warnings remain
available.
BACKUP SYSTEM
The purpose of the backup system is to allow control of the aircraft following a
total loss of electrics, flight control computers, elevators, or ailerons and spoilers.
It is designed to allow the crew to safely stabilise the flight path while attempting
to recover a control law or restore a lost system(s). It is not intended that an
approach and landing should be flown in this configuration.
Stabilise the aircraft flight path using the rudder and manual pitch trim while
attempting to recover a flight control law. Thrust considerations regarding
pitching moments are similar to those described above in Direct Law.
Pitch control is achieved through the pitch trim wheel. Make small inputs on the
trim wheel and wait for the aircraft response before making a further correction.
Lateral control is achieved through the rudder. The rudder induces a significant
roll with a slight delay. Make small inputs on the rudder pedals and wait for the
aircraft response before making a further correction. Wings level stabilisation
needs some anticipation.
h a n g e Vi
e
ABNORMAL ATTITUDE LAW

If the aircraft is far outside the normal flight envelope and reaches some
abnormal attitudes, the flight control law is modified to allow the crew to regain
normal attitude efficiently. This is the abnormal attitude law. FCOM 1.27.30
refers.
A346 Tailstrike Protection

The A346, being longer than the A333 and A343, has a higher risk of tailstrike.
Consequently, several new features have been incorporated. These include an
added rotation law plus an additional auto-callout, PFD indication and ECAM
warning.
A pitch rotation law has been added for take-off and is engaged during the
rotation phase. A pitch demand depending on pitch rate and sidestick position is
added to the ground law orders. Within certain parameters this law minimises
tailstrike risk if there is inappropriate sidestick input from the pilot.
Below 14 ft RA an auto-callout "PITCH, PITCH" is triggered in case of excessive
pitch attitude.
For both take-off and landing, a tailstrike Pitch Limit Indicator (PLI) is provided on
the PFD. The PLI indicates the maximum pitch attitude in order to avoid a
tailstrike. FCOM 1.31.40 refers.
to
bu
y
.d o
.c
General Information
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.60.12
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
GENERAL
Console mounted levers are used to control engine thrust. Thrust can be
controlled either manually, or automatically through the A/THR. Each lever sends
electrical signals to the FADEC of the engine it controls. The FADEC responds
to the thrust lever position or autothrust command by setting engine thrust.
The thrust lever quadrant is effectively a thrust-rating panel. The thrust levers
move over the range of the quadrant in a conventional sense. For each lever
there are four detents:
Idle
CL
FLX/MCT
TOGA
The significance of CL and FLX/MCT detents is described in detail later. Moving

a thrust lever to the TOGA detent always selects maximum take-off or go-around
thrust as appropriate. In the same way, moving a thrust lever to the idle detent
always selects idle thrust.
A/THR status can be monitored through the FMA and the engine instrument
display on the E/WD. The E/WD gives readout of:
lic
2.70.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Thrust Control
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
The engine thrust limit mode (CL, MCT, etc)

The applicable engine limits
Thrust lever position
FADEC command
The maximum engine rating
MANUAL THRUST CONTROL

With autothrust off, thrust control between the idle detent and the TOGA detent
is entirely conventional. Thrust lever angle (TLA) determines the thrust
demanded. The thrust setting selected by the pilot and the actual engine limit is
indicated on the E/WD. With the thrust lever at less than the CL detent, the
E/WD displays the CL limit, except before take-off when it displays the take-off
thrust limit programmed through the MCDU. If the thrust lever is set between two
detents then the FADEC selects the rating limit corresponding to the higher
detent. With the thrust lever(s) positioned in a detent, the detent setting controls
the engine(s) to that limiting parameter, e.g. with the thrust levers in the CL
detent, the engines will be at climb thrust.
h a n g e Vi
e
AUTOTHRUST
One of the unique features of the Airbus A/THR system is that the thrust levers
are not back-driven, i.e. they do not move as the thrust changes. This being the
case, other cues must be used to monitor A/THR performance, e.g. the speed
trend vector on the PFD or the transient and commanded N1/EPR indications on
the engine instruments. The A/THR normally remains active from the thrust
reduction altitude after take-off until the flare.
Autothrust Modes
With A/THR active, one of the following modes will be engaged as appropriate:
Speed or Mach mode, where the A/THR modulates thrust to achieve a

target speed or Mach.
Thrust mode, where the A/THR commands a specific thrust setting, e.g.
climb thrust or idle.
Retard mode, where the A/THR commands a reduction to idle thrust
during the flare. This mode only operates automatically during an
autoland. The thrust levers must be retarded manually in the flare following
a manual approach.
Engagement Status
The A/THR system can be in one of the following three states:
Armed
Active
Off
to
bu
y
.d o
.c
General Information
Thrust Control
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.70.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.70.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Thrust Control
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
When armed, the A/THR is ready to control the thrust once the thrust levers are
moved into the active range. Normally the A/THR is armed on the application of
take-off thrust, at which point "A/THR" is displayed in blue in the right hand
column of the FMA. After take-off, A/THR is activated by selecting the thrust
levers to the CL detent.
When active, the A/THR automatically controls the engine thrust. The TLA
determines the maximum thrust that can be commanded by the A/THR. This
maximum thrust available is displayed on the thrust gauge by a TLA blue circle.
"A/THR" is displayed in white in the right hand column of the FMA. The operating
mode of the A/THR is displayed in the left hand column of the FMA.
When the A/THR is off, thrust must be controlled manually. In this case, the
A/THR FMA indications will be blank.
h a n g e Vi
e
Thrust Lever Quadrant

The active range of the A/THR depends on whether or not all engines are
operative.
In the all engines case, A/THR is active between the idle and the CL detents.
With all thrust levers above the CL detent, A/THR becomes armed.
With one engine inoperative, the A/THR is active between the idle and FLX/MCT
detent. Similarly, with the remaining thrust levers above the FLX/MCT detent,
A/THR becomes armed.
to
bu
y
.d o
.c
General Information
Thrust Control
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.70.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
AUTOTHRUST OPERATIONAL ASPECTS

The operational aspects of the A/THR system can be divided as follows:
Take-off
Climb, Cruise, Descent and Approach
Go-around
Warnings and messages
Take-off
To initiate take-off, the Captain advances the thrust levers to either the FLX/MCT
or TOGA detent depending upon performance requirements:
lic
2.70.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Thrust Control
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
For a TOGA thrust T/O, set the thrust levers to the TOGA detent.
For a FLEX thrust T/O, set the thrust levers to the FLX/MCT detent.
For a DERATED thrust T/O, set the thrust levers to the FLX/MCT detent.
TOGA thrust should not normally be selected on a derated T/O. FCTM Ch
4 refers.
The thrust is controlled by the FADEC to the applicable limit and the A/THR is
armed. The thrust setting will be displayed on the FMA, e.g. FLX 50, as well as
on the E/WD.
At the thrust reduction altitude entered in the PERF T/O page, the message
"LVR CLB" flashes on the FMA. Smoothly move the thrust levers to the CL
detent where they will normally remain until the flare. The A/THR is now active.
Climb, Cruise Descent And Approach

During the climb, the A/THR is in thrust mode and commands the thrust setting
displayed on the FMA, e.g. THR CLB.
In the cruise, the A/THR is in speed mode and modulates the thrust to maintain a
speed or Mach target.
During descent and approach, the A/THR can be in either thrust or speed mode.
Use of the A/THR on approach will be covered in greater detail in Chapter 6.
Go-around
To select go-around thrust, advance the thrust levers to the TOGA detent. TOGA
thrust is commanded and the A/THR becomes armed. The message "MAN
TOGA" appears on the FMA and the A/THR indication becomes blue. The
A/THR becomes active again when the thrust levers are returned to the CL
detent, (or the FLX/MCT detent if engine inop).
h a n g e Vi
e
Warnings And Messages

There are a number of warnings, cautions and messages associated with the
operation of the A/THR. The warnings, cautions and messages can be classified
as follows:
Take-off
All Engines Operative
One Engine Inoperative
Disconnection
Protection
Take-off
The three thrust setting options available for take-off are Flexible Thrust (FLX),
Derated Thrust (DRT) and Take-off and Go-around Thrust (TOGA). The
corresponding thrust lever quadrant detents are FLX/MCT for FLX and DRT
take-offs and TOGA for TOGA take-offs. The FLX temperature and DRT level
are entered via the MCDU. The ECAM provides an element of protection against
the use of incorrect thrust settings for take-off by generating the warning "ENG
THR LEVERS NOT SET" if the thrust levers position disagrees with the MCDU
input. The corrective action for this warning is different depending on the
situation. All CX aircraft have the DRT function enabled and the situations that
will generate this warning are:
If no FLX temperature or DRT level has been inserted and the thrust
levers are set to the FLX/MCT detent
If a DRT level has been inserted and the thrust levers are set beyond the
FLX/MCT detent
Thrust levers are set to below FLX/MCT detent.
to
bu
y
.d o
.c
General Information
Thrust Control
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.70.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.70.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Thrust Control
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
All Engines Operative

With the A/THR active, if one of the thrust levers is set below the climb detent,
the message "LVR ASYM" is displayed in amber on the FMA. In this case, each
engine will be limited to its appropriate TLA position. This allows the continued
use of autothrust if one engine has to be RPM limited for an operational reason,
e.g. excessive vibration.
With the A/THR active, if all thrust levers are set below the CL detent, the
warning "AUTO FLT A/THR LIMITED" appears on the E/WD and the message
"LVR CLB" flashes in white on the FMA. This situation is brought to the crew's
attention as a caution, with a single chime repeated every 5 secs until the thrust
levers are returned to the CLB detent or the A/THR is disconnected. There
should be no operational requirement for the pilot to limit A/THR authority on all
engines.
With the A/THR active, if all thrust levers are set above CL detent, the message
"LVR CLB" flashes in white on the FMA beneath the boxed "MAN THR"
message. The engine power will increase to the thrust corresponding to the TLA.
One Engine Inoperative

With the A/THR active, if the thrust lever(s) of the remaining engine(s) are set
below the MCT detent, the caution "AUTO FLT A/THR LIMITED" appears on the
E/WD and the message "LVR MCT" flashes in white on the FMA.
h a n g e Vi
e
DISCONNECTION
Intentional A/THR disconnection is accomplished by:
Depressing the instinctive disconnect pb

Setting all thrust levers to IDLE
The normal method of disconnecting the A/THR is through the instinctive

disconnect pb on the thrust levers. The PF should announce his intention to
disconnect the A/THR and then use the following sequence:
Set the thrust levers to the current thrust setting by adjusting the levers
until the N1 (EPR) TLA blue circle is adjacent to the actual N1/EPR. If this
step is not carried out prior to pressing the instinctive disconnect pb, the
thrust will increase rapidly to the current TLA, e.g. climb thrust.
Disconnect the A/THR using the instinctive disconnect pb.
The "AUTO FLT A/THR OFF" caution will be annunciated on the E/WD on
the first press of the instinctive disconnect pb and will be cleared by a
second press of the pb. The caution will also disappear after a 9 sec
time-out following a single press of the disconnect pb.
Adjust the thrust as required.
Disconnection of the A/THR by setting the thrust levers to idle is the normal
method of disconnection during the flare.
Disconnection due to a failure is uncommon but should it occur, react to the
ECAM warnings in the normal manner. It may be possible to regain A/THR by
selecting the other AP. If the A/THR cannot be restored, manual thrust must be
used. Speed and thrust awareness following a failure is extremely important, as
Alpha Floor protection is no longer available.
Disconnection by the use of the FCU A/THR pb is not recommended due to the
associated cautions. This method should only be used if the instinctive
disconnect pb is inoperative.
If the A/THR disconnects due to a failure, or is disconnected using the A/THR pb
on the FCU, the cautions "AUTO FLT A/THR OFF" and "ENG THRUST
LOCKED" will appear on the ECAM and the message "THR LK" will flash in
amber on the FMA. In this instance, promptly align the TLA blue circle to the
current thrust setting and adjust thrust manually.
The A/THR can be reactivated by pressing the A/THR pb on the FCU and
returning the thrust levers to the applicable detent.
Protection
Even with A/THR selected off, high angle of attack protection (Alpha Floor) is
provided by the A/THR. Alpha Floor is not available in the certain cases. FCOM
1.22.30 refers.
to
bu
y
.d o
.c
General Information
Thrust Control
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.70.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.80.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Path Vector
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
GENERAL
The FPV indicates performance and does not direct or command. It displays
information on the aircraft trajectory relative to the ground. Because of inertia,
there will always be a lag between an attitude change and the resultant change
in flight path. Therefore, use of the bird should be limited to non-dynamic
manoeuvres. However, it is particularly useful in those operations where a
stable, accurate flight path is important, e.g. non-precision approaches or visual
circuits. When using the bird, make an attitude change first, as with other aircraft
types and then check the outcome with reference to the bird.
INFORMATION PRESENTATION
The vertical flight path angle can be read directly from the PFD pitch scale. If the
aircraft is stable and the wings of the bird are on the PFD horizon, then the
aircraft is in level flight.
The track is displayed on the PFD as a green diamond indicator on the compass,
as well as by the lateral displacement of the bird from the fixed aircraft symbol.
On the ND, the track is displayed as a green diamond indicator on the compass
scale. The angular difference between track and heading indicates the drift.
h a n g e Vi
e
PRACTICAL USES OF THE FPV

The FPV displays information on the aircraft trajectory relative to the ground.
Because of inertia, there will always be a lag between an attitude change and
the resultant change in flight path. Therefore, use of the bird should be limited to
non-dynamic manoeuvres. However, it is particularly useful in those operations
where a stable, accurate flight path is important, e.g. non-precision approaches
or visual circuits.
When using the bird, make an attitude change first, as with other aircraft types
and then check the outcome with reference to the bird.
to
bu
y
.d o
.c
General Information
Flight Path Vector
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.80.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
2.80.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General Information
Flight Path Vector
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Non-Precision Approach
The FPV is particularly useful on non-precision approaches as the pilot can
select values for the inbound track and final descent path angle on the FCU.
Once established inbound, only minor corrections should be required to maintain
an accurate approach path. Tracking and descent flight path can be monitored
by reference to the track indicator and the bird. Be aware, however, that the bird
only indicates a trajectory and not guidance to a ground based facility. For
example, when selecting FPA to create a synthetic glide path, the aircraft will be
correctly positioned only if it commences descent at the right point in space.
Therefore, although the bird may indicate that the aircraft is on the correct
trajectory, it does not necessarily mean that the aircraft is on the correct final
approach path, since it may only be paralleling the intended path. When the
aircraft is disturbed from the original trajectory, the pilot must adjust either its
track or its flight path angle or both in order to obtain guidance back to the
original trajectory.
Visual Circuits
The FPV is useful as a cross-reference when flying visual circuits. On the
downwind leg, put the wings of the bird on the horizon to maintain level flight.
The downwind track should be set on the FCU. Place the tail of the bird on the
blue track index on the PFD to maintain the desired track downwind.
On the final inbound approach, the track index should be set to the runway final
approach course. A standard 3 approach path is indicated by the top of the
bird's tail being just below the horizon and the bottom of the bird being just
above the 5 pitch down marker.
h a n g e Vi
e
FPV CONSIDERATIONS
Dynamic Manoeuvres
The pilot must take care when performing a go-around with the FPV selected, as
on some aircraft the HDG-V/S FD is not automatically displayed upon the
selection of TOGA. In this case, it is important to use pitch attitude as the
primary reference for the go-around and avoid any temptation to select the target
attitude using the bird. The pitch attitude targets for a go-around are 15 for all
engines operating and 12.5 for one engine inop. If not automatically displayed,
selection of HDG-V/S should be made without delay during the go-around. The
FPV is not used for take-off.
Reliability
As the FPV is derived from IRS data, it is therefore affected by the errors of the
ADIRS. This may be indicated by a slight track error, typically in the order of up
to +/- 2.
to
bu
y
.d o
.c
General Information
Flight Path Vector
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
2.80.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
3.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
Pre-start, Start And Taxi

Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
Pre-start
Seating Position ............................................................................................3.10.1
Safety Exterior Inspection .............................................................................3.10.2
Exterior Inspection.........................................................................................3.10.2
Cockpit To Ground Communication ..............................................................3.10.2
Pushback.......................................................................................................3.10.3
Backing With Reverse Thrust........................................................................3.10.3
Start
Engine Start...................................................................................................3.20.1
Taxi
Prior To Brake Release .................................................................................3.30.1
Brake Check..................................................................................................3.30.1
Thrust Use.....................................................................................................3.30.1
Flight Control Check......................................................................................3.30.2
Steering .........................................................................................................3.30.3
Steering Technique And Visual Cues............................................................3.30.3
A346 Taxi Camera ........................................................................................3.30.5
Taxi Speed And Braking................................................................................3.30.5
Carbon Brakes ..............................................................................................3.30.5
Brake Temperature .......................................................................................3.30.5
180 Turn On The Runway ...........................................................................3.30.6
Late Change Of Runway And/Or Take-off Data............................................3.30.7
Take-off Briefing Confirmation.......................................................................3.30.7
Adverse Weather...........................................................................................3.30.8
Taxi With Engines Shut Down.......................................................................3.30.8
Line-up Technique.........................................................................................3.30.8
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
3.10.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Pre-start
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
SEATING POSITION
As in all aircraft, achieving the correct seating position is very important. The
correct seating position not only allows the pilot to have the best possible view of
the instruments and outside the cockpit, but also ensures that he can operate all
controls in both normal and non-normal situations. It is critical during Low
Visibility Procedures (LVP) that the pilot's eyes are positioned correctly so that
he maximises the visual segment, thus increasing the possibility of achieving the
required visual reference for landing as early as possible.
To achieve correct eye position, the aircraft is fitted with an indicator located on
the centre windscreen post. It comprises two balls which, when superimposed
one on the other, indicate that the pilot's eyes are in the correct position. Adjust
the seat horizontally, vertically and in recline to ensure correct eye position. The
adjustments to the seat should be made when sitting in a normal posture. A
common error is sitting too low which decreases the cockpit cut-off angle,
reducing the visual segment.
After seat adjustment, the outboard armrest should be adjusted such that the
forearm rests on it comfortably when holding the sidestick. There should be no
gaps between the forearm and the armrest and the wrist should not be bent
when holding the sidestick. This ensures that flight manoeuvres can be
accomplished by movement of the wrist rather than having to lift the forearm
from the rest. Symptoms of incorrect armrest adjustment include over-controlling
and the inability to make small, precise inputs.
The rudder pedals must then be adjusted to ensure that both full rudder pedal
displacement and full braking can be achieved simultaneously on the same side.
The armrest and the rudder pedals have position indicators. These positions
should be noted and set accordingly for each flight.
h a n g e Vi
e
SAFETY EXTERIOR INSPECTION

An assessment should be made of the aircraft external environment before
applying pneumatic or hydraulic power. Items to check include:
Wheel chocks (the Park Brake must be applied if chocks are not in place)
Landing gear door positions
APU inlet and exhaust areas
Connection of external electrics
Connection of external air-conditioning or HP air
This visual assessment is normally made when approaching the aircraft from
ground level. However, where such an assessment is not feasible, co-ordination
with the ground engineer must be established before starting the APU or
activating aircraft pneumatic, electric or hydraulic systems.
Double chocks should be positioned approx 2 inches forward and aft of the nose
wheel. Main wheels must also be chocked if wind or ramp slope conditions
require and/or if single type chocks only are used on the nose wheel. Be aware
that the parking brake efficiency is significantly reduced if ACCU PRESS falls
below 1500 psi (amber sector).
EXTERIOR INSPECTION
The objective of the exterior inspection it to get a global assessment of the
aircraft status. Any missing parts or panels should be checked against the CDL
for possible dispatch and operational consequences. Ensure that the main
aircraft control surfaces are in the correct position relative to cockpit control
selection and that there is n o evidence of fuel, oil or hydraulic leaks.
Check the status of essential visible sensors; e.g. AOA, pitot and static probes.
Check the landing gear status; e.g. wheel/tyre condition, safety pins removed,
brake wear, and oleo extension.
Check engine condition; e.g. fan blades, turbine exhaust, engine cowl and pylon
status. Check all access panels are closed.
FCOM 3.03.05 refers
COCKPIT TO GROUND COMMUNICATION

It is essential that good communication is established with the ground personnel
prior to engine start or pushback. It is important that standard terminology is
used to avoid confusion and ensure safety.
To attract the attention of the ground mechanic from the flight deck, use the
"Mech Call" pb. To speak to the mechanic, use either the "INT" key on the ACP
when wearing headsets or the "INT" pb on the ACP and the hand-mike.
Establish communication with the mechanic before commencing any action that
may compromise safety, e.g. powering a hydraulic circuit.
Vol 2 Pt 2 refers.
to
bu
y
.d o
.c
Pre-Start, Start And Taxi

Pre-start
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
3.10.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
3.10.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Pre-start
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PUSHBACK
During this potentially hazardous phase of the operation, the NPs should be
strictly followed to minimise the possibility of injury to ground personnel or
damage to the aircraft/ground equipment. Consequently, ATC clearance should
neither be requested nor copied during pushback.
Once the doors are closed and ATC clearance has been obtained, the START
checklist should be completed and the PF can order the pushback. Prior to
aircraft movement, the PF should ensure that the nosewheel steering is
disconnected by checking the ECAM memo. Engines may be started during
pushback in accordance with local regulations. Ground personnel should be on
the headset throughout the pushback to communicate any possible safety
hazards.
BACKING WITH REVERSE THRUST

Backing, or assisting pushback, with reverse thrust is prohibited.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
3.20.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Start
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
ENGINE START
The thrust levers must be confirmed at idle prior to engine start. If the thrust
levers are not at idle, the thrust will increase above idle after start, creating a
potentially hazardous situation. However, an ECAM caution ENG START FAULT
prompts the PF to set the thrust levers to idle.
The normal method of starting the engines is through the auto-start system,
controlled by the FADECs. Selecting the Engine Start Selector to START
energises the FADECs and the start sequence is initiated by selecting the
Engine Master switch to ON. Pilots should monitor the start sequence, however
the FADEC controls the engine start and takes appropriate action should engine
parameters be exceeded. Should a start malfunction occur, the ECAM should be
handled in the normal manner in order to avoid possibly interrupting a FADEC
controlled sequence, e.g. instinctively selecting the master switch to OFF whilst
the engine is being motored following a hot start. For this reason, the PF should
remove his hand from the master switch during an auto-start on the ground.
The next engine start sequence should be initiated once engine parameters
have stabilised and AVAIL is displayed for the engine on the EW/D.
Once the engine start is complete, check the stabilised parameters. Once the
Engine Start Selector has been selected to the NORM position, the PNF should
select the APU Bleed off without delay to avoid engine exhaust gas ingestion.
Manual Engine Start

The FADECs have limited authority during a MAN start. They ensure passive
monitoring of engine parameters and provide ECAM alerts, but they do not have
the authority to abort a MAN start. The FADECs do provide start valve closure at
50% (A333/A346: N3) (A343: N2).
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PRIOR TO BRAKE RELEASE

The Park Brake shall not be released until:
lic
3.30.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Taxi
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Ground crew "thumbs up" signal has been received indicating all
personnel and equipment are clear.
Following a pushback, the NWS pin has been sighted.
ATC taxi clearance has been received.
The NOSE light is set to TAXI.
Both pilots have visually confirmed and cross-checked, no obstructions in
the taxi path.
BRAKE CHECK
When cleared to taxi select the Park Brake to "OFF". Check the brake triple
indicator to ensure that the brake pressure drops to zero, indicating a successful
changeover to the normal braking system. Once the aircraft starts moving, prove
the efficiency of the normal braking system by gently pressing the brake pedals
and checking that the aircraft slows down. The brake pressure should remain
near zero on the brake triple indicator.
(A346: If the brake pedals are pressed before releasing the park brake, the
alternate braking mode remains active and the brake triple indicator will continue
to display blue system pressure. When the brake pedals are released, normal
braking mode resumes and the brake triple indicator should then read near
zero.)
THRUST USE
To begin taxi, release the brakes and, if required, smoothly increase thrust to the
minimum required for the aircraft to roll forward. If thrust above idle is required to
achieve taxi speed, be aware that engines are slow to accelerate from ground
idle and allow time for aircraft response before increasing thrust further. Engine
noise level in the flight deck is low and not indicative of engine thrust. Excessive
thrust application may result in exhaust blast damage or foreign object ingestion
(FOD). Thrust should normally be used symmetrically.
h a n g e Vi
e
FLIGHT CONTROL CHECK

At a convenient stage, prior to or during taxi, but before arming the autobrake,
the PF announces "Flight Control Check" and applies full longitudinal and lateral
sidestick deflection. On the F/CTL page, the PNF checks and calls full deflection
and correct sense of movement of elevators and ailerons and correct extension
and retraction of spoilers. As each full travel/neutral position is reached, the PNF
announces:
"Full up, full down, neutral".

"Full left, full right, neutral".
The PF then presses the PEDAL DISC pb on the steering handwheel and
applies full left and full right rudder and then returns the rudder to neutral. As
each full deflection/neutral position is reached, the PNF responds:
"Full left, full right, neutral".
Full control input must be held for sufficient time for full travel to be reached and
indicated on F/CTL page.
The PNF then repeats the same procedure for the sidestick only, whilst
monitoring the F/CTL page. On completion, the PNF calls Neutral.
The PF then checks the F/CTL page to confirm the correct position of all flight
controls and that the pitch trim indication is in close agreement with the actual
THS setting. On completion, the PF calls Check.
to
bu
y
.d o
.c

Taxi
c u -tr a c k
A330/A340
FCTM
REV 2 (25 JUL 06)

.d o
lic
lic
3.30.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
3.30.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Taxi
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
STEERING
The nosewheel steering system is "fly-by-wire" with no mechanical connection
between the steering handwheel and the nosewheel. The relationship between
steering handwheel deflection and nosewheel angle is non-linear and the
steering handwheel forces are light and independent of deflection. Anticipation is
required when entering or exiting a turn. Make a smooth input on the steering
handwheel and hold that input for sufficient time to assess the outcome. If
required, any correction should be smooth and progressive, as being over-active
on the steering handwheel will induce uncomfortable oscillations.
On straight taxiways and for shallow turns, use the rudder pedal steering, but be
prepared to use the steering handwheel if required.
When exiting a tight turn allow the aircraft to roll forward for a short distance
before stopping to minimise the stress on the main gears. Asymmetric thrust
may be used in order to initiate a tight turn and to keep the aircraft moving during
the turn, but should not be used to tighten the turn. Avoid stopping the aircraft in
a turn, as excessive thrust will be required to start the aircraft moving again.
Simultaneous use of rudder pedal steering and steering handwheel inputs
should be avoided.
STEERING TECHNIQUE AND VISUAL CUES

On straight taxiways, taxi as close to the centreline as possible while keeping the
nosewheel off the taxiway centreline lights. Taxiing over the centreline lights,
particularly at high speeds, is noisy and uncomfortable for the passengers. If the
pilot displaces the aircraft such that his body is over the centreline, this should
allow sufficient displacement from the taxiway centreline.
There are a number of factors that govern when a turn should be initiated. The
main gear on the inside of a turn always cuts the corner and tracks inside of the
nosewheel track. For this reason, the "over-steer" technique must be used. As
the turn is commenced, steer the nosewheel far enough outside the centreline to
keep the main gear evenly straddling the centreline. Be aware that the nose gear
is 5m behind the flight deck and the main gear (A333/A343: 30m)(A346: 35m)
behind the flight deck.
For turns of 90 or more, speed should be below 10 kt. Smoothly initiate the turn
as the intersecting taxiway centreline (or intended exit point) approaches the
centre of the nearside window or aft edge of the offside windshield.
h a n g e Vi
e
N
k
to
bu
y
.d o
.c

Taxi
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
3.30.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
3.30.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Taxi
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
A346 TAXI CAMERA

The Taxi Aid Camera System (TACS) can be useful in observing areas beneath
the aircraft. The TACS is designed to aid in determining the nose and main gear
position prior to and during taxiing and its use should be limited to these
functions. Direct visual observation out of the cockpit window remains the
primary means of determining when to initiate turns and verifying the aircrafts
position relative to the intended ground track. The oversteer technique is
required before entering a turn. Once stable in the turn, the magenta square on
the upper section of the TACS display tracks close to the taxiway centre line.
The TACS display may be used sparingly to determine the proximity of the gear
to taxiway edges and when the main gear has cleared the turn. Do not fixate on
the TACS display at the expense of aircraft control.
No crew procedure or action, except use while taxiing, is predicated on the use
of TACS. The ECAM remains the primary means of alerting crew to non-normal
situations. TACS use during take-off, approach and landing is prohibited. Certain
state authorities prohibit the display of the TACS view within the cabin.
TAXI SPEED AND BRAKING

On long straight taxiways and with no ATC or other ground traffic constraints,
allow the aircraft to accelerate towards 30 kt and then use one smooth brake
application to decelerate towards 15 kt. Do not "ride" the brakes. The ND ground
speed read out should be used to assess taxi speed.
CARBON BRAKES
Carbon Brake wear is a function of the number of brake applications and brake
temperature. The wear is not a function of the pressure applied or the duration of
the braking. The only way to minimise brake wear is to reduce the number of
applications.
BRAKE TEMPERATURE
The FCOM limits brake temperature to 300C before commencement of take-off.
This limit ensures that any hydraulic fluid which might come into contact with the
brake units would not be ignited after gear retraction. It does not provide
protection against an elevated brake temperature after gear retraction resulting
from a dragging brake. Experience indicates that brake temperatures close to
300C tend to reduce during taxi-out provided correct braking technique is used
and no mechanical abnormality exists.
h a n g e Vi
e
180 TURN ON THE RUNWAY

Do not to attempt a 180 turn on a runway that is less than 56 m wide.
The following procedure is recommended for making a 180 turn:
For the Captain:
Taxi on the right hand side of the runway and turn left to establish a 20
divergence from the runway axis (using the ND or PFD) with a maximum
ground speed of 10 kt.
When physically over the runway edge, smoothly initiate a full deflection
turn to the right.
Asymmetric thrust should be used during the turn. Anticipation is required
to ensure that asymmetric thrust is established before the turn is
commenced, (50% N1 or 1.05 EPR), to maintain a continuous speed of
approximately 5 to 8 kt throughout the manoeuvre.
Differential braking is not recommended due to gear assembly stress.
Moreover, a braked pivot turn is NOT permitted (i.e. braking to fully stop
the wheels on one main gear).
For the First Officer, the procedure is symmetrical (taxi on the left hand side of
the runway).
to
bu
y
.d o
.c

Taxi
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
3.30.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
LATE CHANGE OF RUNWAY AND/OR TAKE-OFF DATA

At airports where the opportunity for a late runway change could be expected,
such as BKK, obtain ACARS RTOW for both runways prior to pushback.
Provided performance is not limiting, input the same flap configuration for the
secondary runway as that generated by the ACARS T/O data printout for the
primary runway. Selection of the same flap configuration will reduce the chance
of an incorrect configuration for takeoff.
Any modification to data shall be inserted and crosschecked following the same
process defined in Normal Procedures. If take-off data has changed, or in the
case of a runway change:
Obtain new ACARS RTOW. Again the Captain shall check the ACARS
RTOW.
Modify the F-PLN to reflect the new ATC clearance for the runway, SID
and transition.
Select appropriate navaids for the SID.
Insert the new PERF TO data; the MCDU may not clear the original PERF
data when the runway is changed. Check PERF CLB data (speed
PRESELECT requirement).
Confirm FLAPS LEVER set to new configuration.
Set revised V2 and Green Dot speed bugs on Standby ASI or ISIS.
Using the EFIS Control Panel, confirm selection of EFIS display for both
ND mode and navaids.
Set first stop altitude on FCU. Preset FCU HDG bug if necessary.
Check transponder code is still correct.
TAKE-OFF BRIEFING CONFIRMATION

This briefing should normally be a brief confirmation of the thorough take-off
briefing made at the parking bay. Any major changes that may have occurred
should be reflected in a comprehensive re-briefing.
lic
3.30.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Taxi
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
ADVERSE WEATHER
The major adverse weather factors affecting taxiing techniques are poor visibility
and contaminated taxiways. In both instances, the taxi speed should be limited
to 10 kt and any action which might divert the full attention of the crew from
taxiing should be delayed until the aircraft is stopped. The Before Take-off
checklist should be performed either before taxi or when reaching the holding
point.
On a contaminated taxiway there are a number of additional factors that should
be taken into account:
At speeds below 10 kt, the anti-skid is de-activated

Engine anti-ice increases ground idle thrust
Avoid large steering handwheel inputs to minimise the risk of skidding
during turns
On slippery taxiways, it might be necessary to use differential braking
and/or thrust to augment the nosewheel steering
On slush or snow covered taxiways, delay flap selection until reaching the
holding point to avoid contamination of the flap/slat actuation mechanism.
When holding on the ground in icing conditions for extended periods of time or if
engine vibration is encountered, thrust should be increased periodically and just
before take-off to shed any ice from the fan blades. Detailed information on this
procedure can be found in FCOM 3.
TAXI WITH ENGINES SHUT DOWN

On A343 and A346 aircraft, taxi out for departure with one or two engines shut
down may be operationally beneficial. FCOM 3.04.90 refers.
LINE-UP TECHNIQUE
It is important, particularly on limiting runways, not to sacrifice an excessive
amount of runway length during the line-up, as a fixed distance is assumed for
performance calculations relating to this manoeuvre.
to
bu
y
.d o
.c

Taxi
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
3.30.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
4.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
Take-off And Initial Climb

Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
Take-off
Thrust Setting ................................................................................................4.10.1
Take-off Roll ..................................................................................................4.10.1
Rotation .........................................................................................................4.10.2
Rotation Performance Differences ................................................................4.10.3
Crosswind Take-off .......................................................................................4.10.3
Tailstrike ........................................................................................................4.10.5
Flex Thrust Take-off ......................................................................................4.10.6
Derated Thrust Take-off ................................................................................4.10.7
Adverse Weather...........................................................................................4.10.9
Initial Climb
Preface ..........................................................................................................4.20.1
Lift-off ............................................................................................................4.20.1
AP Engagement ............................................................................................4.20.1
Vertical Profile ...............................................................................................4.20.1
Lateral Profile ................................................................................................4.20.1
Thrust Reduction Altitude ..............................................................................4.20.2
Acceleration Altitude......................................................................................4.20.2
Take-off At Heavy Weight .............................................................................4.20.4
Tracking The Localiser Of The Opposite Runway.........................................4.20.6
Low Altitude Level-off ....................................................................................4.20.7
Close-in Turn After Take-off ..........................................................................4.20.7
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
THRUST SETTING
Following line up and after brake release, the PF announces "Set Thrust". The
Captain then applies power in two stages:
lic
4.10.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Take-off
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
From idle to (A333: 1.15 EPR), (A343: 50% N1), (A346: 1.05 EPR) in a
rapid and continuous movement by reference to the TLA indicator on the
EPR/N1 gauge. On the A333, there is protection between 1.16 -1.28 EPR
to protect the engine from blade flutter. The FADEC will not allow fan
speed acceleration above 1.16 EPR until the demanded EPR exceeds
1.28 EPR.
When the engine parameters have stabilised, the thrust levers should be
advanced without delay to the FLX/MCT or TOGA detent as appropriate.
Modified Engine Acceleration Schedule for Take-Off (MEASTO) is installed on

the A333 engines. This logic automatically controls engine acceleration by
preventing high N1 at low speed during the take-off roll to avoid fan stall. As a
consequence, take-off thrust takes longer to reach than on other engines
(approximately 10 seconds more) and is achieved around 60 kt IAS.
Once the thrust levers are set, the PF announces the indications on the FMA.
The PNF checks that the thrust is set by 80 kt, by checking that the actual
EPR/N1 of each engine has reached the rating limit displayed on the E/WD, and
calls "Thrust Set". The Captain must keep his hand on the thrust levers until V1.
If the thrust levers are set fully forward to the TOGA detent, TOGA thrust is
applied regardless of any FLEX or DERATE entry in the MCDU PERF TO page.
TAKE-OFF ROLL
On a normal take-off, to counteract the pitch up moment during thrust
application, apply half forward sidestick at the start of the take-off roll until
reaching 80 kt. At this point, gradually reduce the input to be zero by 100 kt.
Use rudder to keep the aircraft straight. Nosewheel steering authority decreases
as the groundspeed increases and the rudder becomes more effective.
Normally, there should be no need to use the tiller once aligned with the runway
centreline, but if it is needed, its use should be avoided above 20 kt.
Normally there should be no requirement to use lateral sidestick. If its use is
required however, avoid using an excessive application, as spoilers will deploy,
decreasing the lift and increasing the tendency of the aircraft to turn into wind.
The ONE HUNDRED KNOTS call by the PNF requires the PF to crosscheck
speed on his PFD and respond CHECK. This response also serves as an
incapacitation check. V1" is an Auto Call Out; if the auto-call fails, the PNF calls
V1". At V1, the Captain removes his hand from the thrust levers. The PNF calls
VR and V2" in sequence as each speed is reached.
h a n g e Vi
e
ROTATION
At VR, promptly and smoothly apply and hold approximately 2/3 aft sidestick to
achieve a rotation rate of approximately 2 to 3/sec, assessed primarily by
outside visual reference. Avoid rapid and large corrections that will result in a
sharp reaction in pitch from the aircraft. The rotation rate may take time to
establish but for a given stick input, once it has developed it remains relatively
constant. If the established pitch rate is not satisfactory, make a smooth
correction on the sidestick, however avoid further aft sidestick inputs near the
point of liftoff. The rotation rate is important as too low a rate would compromise
take-off performance, whereas too high a rate would increase the risk of
tailstrike. It is also important to be well prepared for an engine failure case and
therefore it is appropriate to habitually rotate at a rate that would cater for the
engine failure case, i.e. about 2.5sec. As the rotation progresses and the
runway environment disappears from view, transfer attention to the PFD to
establish the initial pitch attitude. The FD pitch bar is not to be used as an initial
target since it does not provide any pitch rate order, instead rotate initially
towards the following target pitch attitudes:
Aircraft type
Target pitch attitude
A333
15
A343
12.5
A346
15
An indication of the correct rotation rate is achieving the target pitch attitude
approximately 5 seconds after rotation commences (not 5 seconds after sidestick
input). Once airborne, adjust the pitch attitude to follow the SRS command. Flight
mode is progressively blended in about 5 seconds after passing 50 ft RA. This allows
the sidestick to be returned to the neutral position, and the subsequent use of small
control inputs as required to follow the FD commands. Automatic pitch trim normally
begins above 50 ft RA.
to
k
.d o
.c
bu
y
m
c u -tr a c k
lic
to
lic
.d o

Take-off
REV 1 (6 JUN 05)
A330/A340
FCTM
4.10.2
w
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
4.10.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Take-off
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
ROTATION PERFORMANCE DIFFERENCES

With both engines operative the A333 has considerable excess thrust, even at
maximum flex temperatures. It is normal for a correctly flown rotation to result in
a stabilised speed in excess of V2+10 kt. The rotation rate should not be
increased in an effort to contain the speed increase. With both engines
operative, the performance of the aircraft is not compromised by this additional
speed.
At heavy weights, the aircraft has much greater inertia and is therefore slower to
commence rotation. As the aircraft starts to rotate, maintain back-pressure to
achieve a steady rotation to the target pitch attitude. Main wheel lift-off can be
expected at 9 - 10 pitch attitude and there will be a tendency for the aircraft to
stop rotating at this attitude unless the back-pressure is maintained. The slower
initial rotation and shallower climb will result in a later establishment of flight
mode.
Compared to shorter aircraft, the sensory feedback to the pilot during the rotation
on the A346 is different due to the length of the aircraft and its flexibility. For the
same rotation rate, the pilot will sense a delay in the rotation and a higher local
vertical acceleration. Do not allow this sensory feedback to induce large changes
in sidestick inputs which can lead to pitch oscillations. The A346 rotation law has
been adapted to take into account the different characteristics of the aircraft.
For aircraft geometry, FCTM 7.10 refers.
CROSSWIND TAKE-OFF
Maintain the runway centerline using rudder and use aileron to keep the wings
level. In normal crosswind conditions, routine use of into wind aileron is not
necessary. In strong crosswind conditions, some lateral input may be needed to
keep wings level. Care should be taken to avoid using excessive lateral sidestick
input, as this could result in spoiler deployment, increasing the tendency to
weathercock into wind and consequently decreasing lift and increasing drag.
Spoiler deployment starts to become significant with more than half sidestick
deflection.
h a n g e Vi
e
Ground mode lateral law gives a direct relationship between sidestick input and
aileron deflection proportional to airspeed. During rotation the aircraft will react in
the same manner as any conventional swept wing aircraft. With increasing angle
of attack, the aircraft will naturally roll downwind so more aileron input will be
required to maintain wings level. As the aircraft becomes airborne the rudder
should be neutralised. Above approximately 100 ft RA, normal roll law becomes
active and the aircraft will start to roll in response to any lateral sidestick input.
The correct and instinctive response at this stage is to remove any lateral input.
The aim is to maintain wings level throughout the ground-roll, rotation and initial
departure.
to
bu
y
.d o
.c

Take-off
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
4.10.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
To aid directional control in crosswinds greater than 20 kt, or with a tailwind,

apply full forward sidestick at the start of the take-off roll until 80 kt. At this point
gradually reduce the input to be zero by 100 kt.
TAILSTRIKE
An inappropriate take-off technique could result in a tailstrike. Factors that might
cause a tailstrike include:
lic
4.10.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Take-off
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Early rotation
Over-rotation
Excessive rotational pitch rate
Increased aft sidestick input at a late stage in the rotation; i.e. above about
8 pitch attitude, when the aircraft is near the point of lift-off and tail
clearance is at a minimum
Immediately rotating to the SRS pitch bar
Excessive spoiler extension during rotation
Turbulence and windshear
Using the take-off technique described earlier will minimise the risk of tailstrike.
FCOM bulletin refers.
In general, the higher the take-off flap configuration, the greater the tailstrike
margin.
In the event of a tailstrike, identified by ECAM or any other means, flight at high
altitude must be avoided and the aircraft landed as soon as practicable. The
aircraft must not be pressurised.
The A346, being longer than the A333 and A343, has a higher risk of tailstrike.
Consequently, Flap 3 is normally used for take-off.
h a n g e Vi
e
In addition, some new features have been incorporated on the A346:
Pitch Limit Indicator (PLI) on the PFD. This indicates the pitch limits when
the aircraft is on, or close to, the ground.
Modification to the rotation law to account for the characteristics of the
aircraft.
FLEX THRUST TAKE-OFF

The FLEX take-off reduces EGT thus increasing engine life and reliability while
reducing maintenance and operating costs. The FLEX take-off can be used
when the actual take-off weight is lower than the maximum permissible take-off
weight for the actual temperature. As the MTOW decreases with increasing
temperature, it is possible to assume a temperature at which the actual take-off
weight would become limiting. This assumed temperature is called the FLEX
Temperature.
The minimum control speeds associated with the FLEX take-off are related to
VMCG/VMCA at TOGA thrust. Therefore, should the aircraft suffer an engine
failure at V1, there is no limitation on selecting TOGA thrust on the remaining
engine(s).
to
bu
y
.d o
.c

Take-off
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
4.10.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
4.10.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Take-off
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
DERATED THRUST TAKE-OFF

A reduction in take-off thrust leads to lower VMCG/VMCA and hence, a lower
V1. When taking off from short or contaminated runways where ASDA is the
limiting factor, a reduction in the minimum control speeds may generate a
take-off performance benefit and a higher MTOW.
A derated take-off is defined as a take-off at a thrust setting less than TOGA. Six
(A346: 8) derated levels are defined, (A333/A343: D04, D08, D12, D16, D20,
D24) (A346: D28, D32), each corresponding to a specific percentage reduction
from the maximum take-off thrust. Derated procedures should only be used on a
runway where the weight is limited by VMCG. Derating the thrust to a level below
that necessary to meet the performance requirements is not permitted.
During flight preparation, the appropriate derate should be entered in the DRT
TO/FLX TO field in the PERF TO page on the MCDU, e.g. D04. The MCDU logic
requires specific confirmation of this entry. Derated thrust is selected by setting
the thrust levers to the FLX/MCT detent.
h a n g e Vi
e
As opposed to a FLEX take-off, the selection of TOGA following an engine

failure during a derated thrust take-off is prohibited as long as speed remains
below the first flap/slat retraction speed for the take-off configuration. The
selection of TOGA below this speed in these configurations may result in loss of
control due to VMCA considerations.
to
bu
y
.d o
.c

Take-off
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
4.10.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
ADVERSE WEATHER
Adverse weather that can be encountered during the take-off and intial climb
includes:
Cold weather
Contaminated runway
Windshear
Cold Weather
When icing conditions exist at 0C and below, the take-off must be preceded by
an engine static run-up to 50% N1 or greater and stable engine operation
checked before the start of the take-off run. FCOM 3 refers. If the aircraft has
been either de-iced or anti-iced, a pre take-off inspection of the wing upper
surfaces must be carried out just prior to take-off for evidence of ice, snow or
frost accretion. If the anti-icing holdover time has expired, a visual inspection of
the wings for contamination must be performed within the 5 minutes immediately
prior to take-off.
Contaminated Runway
Take-off from an icy runway is not recommended. The minimum friction
co-efficient for take-off is:
lic
4.10.9
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Take-off
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
0.2 FC (ICAO)
0.26 CRFI (Canada)
20 ACBA (USA)
Operations from contaminated runways require a higher level of attention. Slush,

standing water, or deep snow, reduce the aircraft take-off performance due to
increased rolling resistance and the reduction in tyre-to-ground friction. Refer to
FCOM 2 for recommended maximum depth of contaminant.
The use of FLEX thrust for take-off is prohibited. However, DRT thrust may be
used as required to optimise aircraft performance. During operations on
contaminated runways, ensure that engine thrust advances symmetrically. This
will help minimise potential directional control problems.
Before applying thrust, ensure that the nose wheel is straight. Any tendency to
deviate from the runway centreline must be immediately countered with rudder.
Avoid over-controlling on the rudder, as this may induce lateral control
difficulties.
Precipitation drag reduces the initial acceleration. A higher flap setting increases
the RTOW for a particular runway, but reduces the second segment climb
gradient.
h a n g e Vi
e
Windshear
Awareness of the weather conditions which result in windshear will reduce the
risk of an encounter. Studying meteorological reports and listening to tower
reports will assist in the assessment of the weather conditions to be expected
during take-off.
If a windshear encounter is likely, the take-off should be delayed until the
conditions improve, e.g. until a thunderstorm has cleared the airport. If the winds
affecting the airport are not necessarily associated with a temporary short-term
weather phenomenon, then choose the most favourable runway and thrust
setting. i.e. TOGA thrust.
Before take-off, use the weather radar and PWS to ensure the planned flight
path is clear of any problem areas.
On aircraft fitted with PWS, an alert may be generated on the runway before
take-off, in which case the take-off should be delayed. The PWS is described in
detail in FCOM 1.34. Additionally, after liftoff, the FMGEC reactive windshear
warning system may be triggered in the event of a shear being experienced by
the aircraft. The reactive windshear warning system is described in detail in
FCOM 1.22.
On the take-off roll, closely monitor airspeed and airspeed trend. Without PWS,
windshear can be detected by significant and rapid speed variation on the PFD
speed tape. If this occurs below V1, the Captain should reject the take-off only if
he considers that there is sufficient runway remaining to stop the aircraft. If a
rejected take-off is not possible, select TOGA thrust, continue the take-off and
apply the checklist actions from memory.
On receipt of a reactive "WINDSHEAR" warning, select TOGA thrust and apply
the checklist actions from memory.
If windshear is encountered and the take-off is continued, the PF calls
Windshear Go, implying that no configuration change will occur until clear of
the shear. The following points should be stressed:
If encountered above V1 but below VR, a normal rotation should be

initiated no later than 2000 ft before the end of the runway, even if
airspeed is low.
The configuration should not be changed until positively out of the shear
as the operation of the landing gear doors induces additional drag.
Follow the SRS, even if this requires the use of full back stick. As the
speed begins to recover, the piot can reduce back stick while still following
SRS orders until well clear of the shear.
The PNF should call RA, RA trend and V/S and significant related trends.
When clear of the shear, report the encounter to ATC.
to
bu
y
.d o
.c

Take-off
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
4.10.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
4.10.11
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Take-off
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
On receipt of a predictive WINDSHEAR AHEAD warning, apply the checklist

actions from memory. If the warning occurs before 100kt, stop. If the warning
occurs once airborne, select TOGA and follow the SRS. Continue the departure
and clean up as normal unless windshear is encountered or a WINDSHEAR
warning occurs.
Selection of the TERR ON ND pb will inhibit the display of the WINDSHEAR
AHEAD display on that pilots ND.
Strong Crosswind and Gusty Conditions

For take-off in strong, variable crosswinds and/or gusty conditions the use of
TOGA thrust is recommended. The use of a higher thrust setting reduces the
required runway length and minimizes the aircrafts exposure to gusty conditions
during rotation, lift-off and initial climb.
When the reported wind is at, or near to, 90 to the runway, the possibility of
wind shifts, that may result in gusty tailwind components during rotation, or
lift-off, increase. The influence of the airport terminal, aircraft hangars, and
topographical features can have a significant effect on the crosswind and
produce additional turbulence.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
4.20.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Initial Climb
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PREFACE
For the purpose of this manual, initial climb is considered to be from the take-off
through to the completion of flap retraction.
LIFT-OFF
A positive rate of climb should be confirmed on the VSI and RA before ordering
"Gear Up". After confirming increasing RA and positive V/S, the PNF calls
"Positive Rate, Gear Up" and then selects the gear up.
AP ENGAGEMENT
The AP can be engaged 5 seconds after takeoff and above 100 ft RA. Trim the
aircraft and satisfy the FD commands prior to AP engagement. This will prevent
undesirable excursions from the desired flight path.
VERTICAL PROFILE
SRS engages when the thrust levers are set to the FLEX/TOGA detent for
take-off and will remain engaged until the acceleration altitude. SRS orders
provide a speed target of V2+10 (or with one engine inop, the IAS at the time of
failure with a minimum of V2 and a maximum of V2+15), but within pitch and
gradient limits. Consequently, it is possible that the IAS demanded by the FDs
may be higher than V2+10 (or V2 with one engine inop).
LATERAL PROFILE
Under most circumstances, expect to follow the programmed SID. In this case,
NAV is armed on selecting the thrust levers to the applicable detent for take-off
and engages once above 30 ft RA.
ATC may require the aircraft to maintain a specific heading after take-off. In this
case, and prior to commencing the take off roll, turn the FCU HDG selector to
the required heading. This process will disarm NAV. Once airborne and above
30 ft RA, RWY TRK engages. When required, pull the FCU HDG knob to
establish the required heading.
h a n g e Vi
e
THRUST REDUCTION ALTITUDE

At the thrust reduction altitude, "LVR CLB" flashes on the FMA. Follow the FD
pitch command before selecting the thrust levers to the CL detent, at which point
A/THR becomes active. The FD pitch down order depends on the amount of
thrust decrease between TOGA /FLEX and CLB.
Following thrust reduction with all engines operating, the PNF selects Pack 1 on,
pauses 5 to 10 sec, and then selects Pack 2 on. With an engine failure before
thrust reduction altitude, this procedure is delayed until MCT is set and the
aircraft climbing at Green Dot.
ACCELERATION ALTITUDE
At the acceleration altitude, the FD pitch mode changes from SRS to CLB, (or
OP CLB if HDG were pre-selected prior to take off). The speed target becomes
either the preset climb speed, if one had been entered on the PERF CLB page,
or the managed climb speed. At heavy weights, Green Dot speed is normally
higher than the managed speed target. In this case, when Flaps 0 is selected,
the aircraft will accelerate past the managed speed target to Green Dot.
The minimum speed for moving the flap lever to 1 is displayed as F on the PFD
speed tape. The minimum speed for moving the flap lever to 0 is displayed as S
on the PFD speed tape. The PNF positively cross checks that the speed is
above the minimum before moving the flap lever.
Flaps 1 should only be selected when:
No longer in SRS
Above F speed and accelerating
Flaps 0 should only be selected when:
No longer in SRS
Above S speed and accelerating with the next speed target at least Green
Dot
to
bu
y
.d o
.c

Initial Climb
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
4.20.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
4.20.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Initial Climb
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
If the take-off configuration was CONF 2 or 3, then F will be displayed on the

PFD speed tape. Once above F speed and accelerating (it is not necessary that
the target speed be S or faster), the PF requests "Flaps 1". The PNF confirms
that the speed is above F, repeats the call and then selects Flaps 1. The PNF
visually confirms that the E/WD displays "1+F" in blue while the surfaces are in
transit. He then checks that both the "1+F" and the flap position indication turn
green when the surfaces reach their commanded position. Once above S speed
and accelerating to a target speed of green dot or greater, the PF request "Flaps
zero". The PNF confirms that the speed is above S, repeats the call and then
selects Flaps 0. The PNF visually confirms that the E/WD displays "0" in blue
while the surfaces are in transit. He then checks that both the "0" and the
slat/flap position indication disappear when the surfaces are fully retracted.
Manoeuvring in the clean configuration with the speed below Green Dot is not
recommended.
Once the aircraft is in the clean configuration, the PNF disarms the ground
spoilers and turns off the NOSE and RWY TURN OFF lights. Above the
applicable sector MSA, the TERR ON ND pb should be deselected if used during
take-off. When workload permits, call for the After Take-off checklist. Once clear
of any significant weather, call for the seatbelt sign to be cycled, signalling that
the cabin crew can commence the cabin service.
h a n g e Vi
e
Obstacle clearance, noise abatement, or departure procedures may require an

immediate turn after take-off. Provided FD commands are followed accurately,
the flaps and slats may be retracted using the normal procedure as FD orders
provide bank angle limits with respect to speed and configuration. However,
without FD guidance, bank angle must be limited to 15 until S speed with Flaps
1 selected, or Green Dot in the clean configuration.
TAKE-OFF AT HEAVY WEIGHT

At heavy weights, F speed may be close to VMAX CONF 2 and S speed will be
above VMAX CONF 1+F (A333/A343: 215 kt) (A346: 233 kt), which is displayed
on the PFD speed tape as a red and black strip in accordance with flap lever
position. In this case, three protection systems are available:
The Flap Load Relief System (FLRS)

The Automatic Retraction System (ARS)
The Alpha Lock Function
The Flap Load Relief System

While in CONF 2 and when IAS reaches VMAX CONF 2, the FLRS is activated.
The FLRS automatically retracts the flaps to the next further retracted position.
VMAX CONF 2 remains unchanged on PFD speed scale in accordance with the
flap lever position. RELIEF is displayed on the E/WD Flap/Slat indication. If IAS
decreases below VMAX CONF 2, the flaps will re-extend.
The Automatic Retraction System

While in CONF 1+F, as the aircraft accelerates towards VMAX CONF 1+F, the
Automatic Retraction System retracts the flaps to 0 (CONF 1) (A333/A343: 200
kt) (A346: 215 kt). VMAX displayed on the PFD changes from VMAX CONF 1+F
to VMAX CONF 1. As the aircraft accelerates above S speed, the flap lever can
be selected to 0, provided the target speed is Green Dot or greater. F and S
speeds are minimum speeds for flaps and slats retraction and not the speeds at
which the selection must be made. If IAS decreases below (A333/A343: 200 kt)
(A346: 215 kt), the flaps will not re-extend.
to
bu
y
.d o
.c

Initial Climb
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
4.20.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
4.20.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Initial Climb
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
The Alpha Lock Function

The slats alpha/speed lock function will prevent slat retraction at high AOA or low
speed at the moment the flap lever is moved from Flaps 1 to Flaps 0. A LOCK
pulses in green above the E/WD slat indication. This is possible if maneuvering
during a heavy weight take-off. Continue with the scheduled acceleration that will
eventually trigger slats retraction.
The inhibition is removed and the slats retract when both alpha and speed fall
within normal values. This protection feature is no longer available once the flap
lever has been selected to zero.
TRACKING THE LOCALISER OF THE OPPOSITE RUNWAY

If the aircraft is required to track the localiser of the opposite runway, the ILS
must be correctly set on the MCDU RADNAV page to allow monitoring of
localiser deviation in the correct sense.
If the ILS is in the database, the FMGC should automatically tune the correct
frequency and course, which should be the take-off runway course preceded by
a B.
If the ILS is not stored in the database or the FMGC fails to tune the correct
frequency and course, manually insert the ILS frequency (or ident), and the
take-off runway course preceded by a B. For example, if the ILS frequency and
associated course of the opposite runway were 109.9/073, and the take-off
direction was therefore 253, insert frequency 109.9 and course B253. B/C will
be displayed on the ND (ROSE LS) and PFD (LS) in magenta.
If the RWY/ILS MISMATCH message is displayed in the MCDU scratchpad, it
may be disregarded.
Use NAV mode for departure and monitor localiser tracking on the PFD by
pushing the LS pb on the EFIS CTL panel, or on the ND by selecting ROSE LS.
Both the PFD and ND will display localiser deviation in the correct sense. Do not
select the LS pb on ISIS, since the ISIS displays localiser deviation in the
reverse sense.
to
bu
y
.d o
.c

Initial Climb
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
4.20.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
4.20.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Initial Climb
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
LOW ALTITUDE LEVEL-OFF

If the aircraft is required to level-off below the acceleration altitude, ALT*
engages and SRS disengages. The "LVR CLB" message flashes on the FMA
and the target speed goes to the initial climb speed. Thrust levers should be
selected to the CLB detent to engage SPEED mode. In this case expect a faster
than normal acceleration and be prepared to retract the flaps and slats promptly.
CLOSE-IN TURN AFTER TAKE-OFF

Where limited acceleration is required to comply with SID tracking or altitude
requirements, pre-select a suitable speed in the PERF CLB page. The
pre-selected speed should be above F speed to allow initial flap retraction to
CONF 1. Delaying the acceleration by inserting a higher ACCEL ALT in the
MCDU is not recommended.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
h a n g e Vi
e
5.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
Climb, Cruise And Descent

Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
Climb
Preface ..........................................................................................................5.10.1
Climb Thrust ..................................................................................................5.10.1
Lateral Navigation .........................................................................................5.10.2
Vertical Navigation ........................................................................................5.10.2
Speed Considerations ...................................................................................5.10.3
Altitude Considerations .................................................................................5.10.3
Adverse Weather...........................................................................................5.10.4
Cruise
Preface ..........................................................................................................5.20.1
FMS Use .......................................................................................................5.20.1
Cost Index .....................................................................................................5.20.2
Altitude Considerations .................................................................................5.20.4
Fuel ...............................................................................................................5.20.8
Adverse Weather...........................................................................................5.20.9
Polar Operations .........................................................................................5.20.10
Descent Preparation....................................................................................5.20.11
Approach Briefing........................................................................................5.20.12
h a n g e Vi
e
N
y
Descent
TOD Computation .........................................................................................5.30.1
Descent Monitoring .......................................................................................5.30.5
Descent Adjustment ......................................................................................5.30.6
Descent Constraints ......................................................................................5.30.6
Arrival Operating Speeds ..............................................................................5.30.6
Adverse Weather...........................................................................................5.30.6
k
lic
.d o

Table Of Contents
to
bu
m
A330/A340
FCTM
05)
lic
5.00.2
wREV 1 (6 .JUN
c
.d o
c u -tr a c k
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
For the purpose of this manual, the climb phase is considered to be from the end
of the flap retraction to the top of climb. Note however, that the FMGS enters the
climb phase when SRS disengages.
CLIMB THRUST
During the climb with the thrust levers in the CL detent, the A/THR is active in
thrust mode and the FADECs manage the thrust to a maximum value depending
upon ambient conditions.
Engine life is extended by operating the engines at less than maximum climb
rated thrust. Two levels of derated climb thrust can be selected on the PERF
CLB page:
lic
5.10.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Climb
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
D1, which reduces the maximum climb thrust by 5 to 10 %

D2, which reduces the maximum climb thrust by 10 to 15 %
If a derated climb has been entered prior to departure, "THR DCLB 1(2)" will be
displayed on the FMA when the thrust levers are set to the CL detent at the
thrust reduction altitude. The FADEC progressively reduces the derate with
increasing altitude until it is zero at approximately (A343: FL250) (A333/A346:
FL340). Climb performance is reduced when using derated climb thrust but the
ceiling is not affected. The use of D1 is encouraged at all times and the use of
D2 whenever operationally feasible. The level of derate may be modified or
cancelled at any stage via the PERF CLB page.
h a n g e Vi
e
LATERAL NAVIGATION
With the AP/FD in NAV, the aircraft will follow the programmed SID. If a
deviation from the programmed SID is required, e.g. ATC vectors or weather
avoidance, select HDG. If HDG is selected, the climb mode reverts to OP CLB.
When cleared to a specific waypoint, perform a DIR TO to ensure correct
waypoint sequencing, and re-engage CLB mode.
VERTICAL NAVIGATION
The AP/FD climb modes may be either
Managed
Selected
Both climb modes can be flown with either managed or selected speed.
Managed Climb Mode

The managed AP/FD mode in climb is CLB. Its use is recommended as long as
the aircraft is cleared along the F-PLN. Although CLB mode will try to observe
altitude constraints, the next climb altitude is always set on the FCU. CLB mode
will not adjust aircraft speed to achieve altitude constraints.
Selected Climb Mode

The selected AP/FD modes in climb are OP CLB or V/S.
OP CLB is to be used if ATC gives radar vector or clears the aircraft direct to a
given FL without any climb constraints. Any programmed FMGS climb
constraints will be ignored.
The use of low values of V/S, e.g. 1000 fpm or less, may be appropriate for small
altitude changes as it makes the guidance smoother and needs less thrust
variation. In areas of high traffic density, low values of vertical speed will reduce
the possibility of nuisance TCAS warnings. As a guide, a value of +1000 ft/min is
appropriate when in close proximity to other aircraft. The A/THR mode will
automatically revert to SPEED and adjust thrust to maintain the target speed.
Whenever V/S is used, pay particular attention to the speed trend as V/S takes
precedence over speed requirements. If the pilot selects too high a V/S, the
aircraft may be unable achieve both the selected V/S and target speed with Max
Climb thrust. In this case, the AP/FD will guide to the target V/S, and the A/THR
will command up to Max Climb thrust and allow the speed to decelerate. When
VLS is reached the AP will pitch the aircraft down so as to fly at a V/S to
maintain VLS.
to
bu
y
.d o
.c

Climb
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.10.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
SPEED CONSIDERATIONS
Managed
The managed climb speed, computed by the FMGS, provides the most
economical climb profile as it takes into account weight, actual and predicted
winds, ISA deviation and Cost Index (CI). The managed climb speed also takes
into account any speed constraints, e.g. the default speed limit, which is normally
250 kt up to 10000 ft. At heavy weights, Green Dot can be greater than 250 kt. In
this case, the aircraft accelerates to Green Dot even though the magenta speed
target on the PFD indicates 250 kt. When the default speed limit no longer
applies, the magenta speed target becomes ECON climb speed and the aircraft
will accelerate.
Selected
If necessary, the climb speed can be selected on the FCU. This may be required
to comply with climb constraints, ATC clearances or during weather avoidance or
penetration.
The speed to achieve the maximum rate of climb, i.e. to reach a given altitude in
the shortest time, is situated between ECON climb speed and Green Dot. There
is no specific indication of this speed on the PFD. A rule of thumb to achieve
maximum rate climb is to select 285 kt/0.78M.
The speed to achieve the maximum gradient of climb, i.e. to reach a given
altitude in a shortest distance, is Green Dot. The PERF CLB page displays the
time and distance required to achieve the selected altitude by climbing at Green
Dot speed under the "Expedite" heading. Avoid reducing to Green Dot at high
altitude, particularly at heavy weight, as it can take a long time to accelerate to
cruise mach number. There is no operational benefit from selecting a speed
lower than green dot. When IAS is selected, there is no automatic changeover to
Mach.
ALTITUDE CONSIDERATIONS
The PROG page provides:
REC MAX FL
OPT FL
lic
5.10.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Climb
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
REC MAX FL
The recommended maximum flight level is computed as a function of present
gross weight and temperature. It provides a 0.3 g buffet margin, a 300 ft/min rate
of climb at maximum climb thrust and level flight at maximum cruise thrust. It is
limited to FL411. If a FL higher than REC MAX is inserted into the MCDU, it will
be accepted only if it provides a buffet margin greater than 0.2 g. Otherwise, it
will be rejected and the message "CRZ ABOVE MAX FL" will appear on the
MCDU scratchpad. Flight above FL411 is prohibited and MCDU entries above
FL411 will be rejected with the message "ENTRY OUT OF RANGE".
OPT FL
The optimum flight level is computed as a function of present gross weight, CI,
temperature, winds and a minimum estimated cruise time of 15 min. The
optimum flight level will never be greater than the recommended maximum flight
level. Provided there are no operational constraints, fly as close as possible to
the optimum flight level.
Altitude Constraint
The altitude constraints in the F-PLN are observed only when the climb is
managed, i.e. when CLB is displayed on the FMA. Any other vertical mode will
disregard altitude constraints. During all climbs, ensure that the next altitude
restriction is set on the FCU.
ADVERSE WEATHER
Adverse weather which may be encountered during the climb includes:
CB activity
Icing
Turbulence
to
bu
y
.d o
.c

Climb
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.10.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
CB Activity
Areas of known turbulence associated with CBs should be avoided. Good radar
tilt management is essential to accurately evaluate the vertical development of
CBs. Normally the gain should be left in AUTO. However, selective use of
manual gain may help in the assessment of the overall weather situation. Manual
gain is particularly useful when operating in heavy rain if the radar picture has
become saturated. In this instance, reduced gain will help the crew identify the
areas of heaviest water droplet concentration, normally associated with active
CB cells. After using manual gain, it should be re-selected to AUTO to recover
optimum radar sensitivity. A decision to avoid a CB should be made as early as
possible and lateral avoidance should ideally be 20 nm.
Cathay Pacific Weather Radar manual refers.
Icing
Whenever icing conditions are encountered or anticipated, ENG ANTI-ICE
should be selected on. Even though the actual TAT prior to entering cloud might
not require engine anti-ice, crews should be aware that the TAT often decreases
significantly when entering cloud. When the SAT reduces to below -40C, engine
anti-ice should be selected off, unless flying in the vicinity of CBs. Failure to
follow the recommended anti-ice procedures may result in engine stall,
over-temperature or engine damage.
Wing anti-ice should be selected if either severe ice accretion is anticipated or
there is an indication that airframe icing exists.
Turbulence
If turbulence is anticipated or encountered, consider reducing speed towards
turbulence speed for passenger comfort. If severe turbulence is anticipated or
encountered, reduce speed to turbulence speed.
A333
240 kt up to FL 200
then 260 kt / M0.78
A343
260 kt up to FL 200
then 280 kt / M0.78
lic
5.10.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Climb
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
A346
280 kt up to FL 220
then 300 kt / M0.81
Severe Turbulence Speeds

The flight control law is designed to cope with turbulence. If flying manually,
avoid the temptation to over-control on the sidestick in an attempt to overcome
the turbulence.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
5.20.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Cruise
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PREFACE
Once the cruise flight level is reached, ALT CRZ is displayed on the FMA, and
cruise Mach number for best economy based on cost index is targeted by the
A/THR system. On reaching cruise level, the PF shall confirm the commanded
thrust is set correctly and the desired speed/mach target is properly maintained.
If ATC limits CRZ FL to a lower level than that displayed on the PROG page,
insert this lower CRZ FL. Otherwise, there is no transition into CRZ phase:
consequently the managed speed and Mach targets are not modified and A/THR
SOFT mode is not available. FMA will display ALT instead of ALT CRZ in the
second column.
When established in the cruise, conduct an abbreviated flow pattern to ensure
correct switch positions. In addition, relevant SD pages are selected to monitor
system operation and trends. This scan of panels and system pages should be
repeated at least once per hour during the cruise. In addition, ECAM MEMO
should be routinely scanned as it serves as a reminder of system functions or
crew actions that are normally only required for a relatively short period of time.
VLS shown on the PFD ensures 0.3 g buffet margin, and therefore no additional
margin is necessary in cruise.
FMS USE
When reaching cruise FL, ensure that the wind and temperatures are correctly
entered and that the lateral and vertical F-PLN reflect the CFP. This is normally
done by the PNF. Wind entries should be made at waypoints when there is a
difference of either 30 or 30 kts for the wind data and 5C for temperature
deviation. These entries should be made for as many levels as possible to reflect
the actual wind and temperature profile. This will ensure that the FMS fuel and
time predictions are as accurate as possible and provide an accurate OPT FL
computation.
Sensible use of the ETP function will assist the crew in making a decision should
an enroute diversion be required. Suitable airport pairs should be entered on the
ETP page and the FMS will then calculate the ETP. Each time an ETP is
sequenced, insert the next suitable diversion airfield. Additionally, the PROG
page can be used to provide an indication of direct track to any selected en-route
diversion airfield.
The SEC F-PLN is a useful tool and should be used practically. By programming
a potential enroute diversion, workload would be reduced should a failure occur.
This is particularly significant when terrain considerations apply to the intended
diversion route.
h a n g e Vi
e
The DATA > STORED ROUTES function in the MCDU can be used to store up
to five possible diversion routes. These routes can be entered into the SEC
F-PLN using the SEC INIT prompt. This prompt will only be available if the SEC
F-PLN is deleted. FCOM 4.04.30 refers.
COST INDEX
The CI is calculated by the Company, taking into account several parameters.
From an operational point of view, the CI affects speeds and cruise altitude. CI 0
corresponds to minimum fuel consumption whereas CI 999 corresponds to
minimum flight time. From a practical point of view, CI 0 equates to maximum
range. The CI should be considered as a means of long-term speed
management rather than a means of short-term speed control. For example, if a
speed reduction is required for the entire flight to comply with curfew
requirements, then it would be appropriate to reduce the CI. CI for LRC are
approximately A333: 40, A343: 50 and A346: 140.
The SEC F-PLN can be used to check the predictions associated with a new CI.
However, be aware that any modification of the CI in the primary F-PLN will
affect trip cost.
to
bu
y
.d o
.c

Cruise
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.20.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
With "ALT CRZ" annunciated on the FMA, the A/THR engages in "soft" mode,
which means that small deviations around the target Mach (typically 4 kt) are
tolerated before a thrust adjustment occurs. This minimises cruise fuel
consumption.
The cruise speed may be either:
Managed
Selected
Managed
When the cruise altitude is reached, i.e. "ALT CRZ" on the FMA, the A/THR
operates in SPEED/MACH mode. The optimum cruise Mach number is
automatically targeted. Its value depends on:
lic
5.20.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Cruise
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
CI
Cruise flight level
Temperature deviation
Weight
Headwind component.
The optimum Mach number will vary according to the above-mentioned

parameters, e.g. it will increase with an increasing headwind. If there is no
overriding operational constraint, e.g. ATC speed control, the managed Mach
should be maintained as it provides the optimum trip cost.
Should ATC require a specific time over a waypoint, enter a time constraint at
that waypoint via a vertical revision. The managed Mach number will be modified
accordingly, between Green Dot and M0.84, in an attempt to achieve this
constraint. If the constraint can be met within the defined tolerance, a magenta
asterisk will be displayed on the MCDU. If the constraint cannot be met, an
amber asterisk will be displayed. Once the constrained waypoint is sequenced,
the ECON Mach is resumed. FCOM 4 refers.
h a n g e Vi
e
Selected
Should ATC require a specific cruise speed, or turbulence penetration is
required, select the new cruise speed on the FCU. FMS predictions are updated
accordingly until reaching either the next step climb or TOD, at which point the
programmed speeds apply again. The FMS predictions are therefore realistic.
At high altitude, the speed should not be reduced below Green Dot as this may
create a situation where it is impossible to maintain speed and/or altitude as the
increased drag may exceed the available thrust.
ALTITUDE CONSIDERATIONS
The PROG page displays:
REC MAX FL
OPT FL
REC MAX FL
REC MAX reflects aircraft performance and does not take into account the cost
aspect. Unless there are overriding operational considerations, REC MAX should
be considered as the upper cruise limit.
OPT FL
OPT displayed on the PROG page is the cruise altitude for minimum cost when
ECON MACH is flown and should be followed whenever possible. It is important
to note that the OPT FL displayed on the PROG page is meaningful only if the
wind and temperature profile has been accurately entered. Flying at a level other
than the OPT FL adversely affects the trip cost.
For each different Mach number, there will be a different OPT FL. Should an
FMGS failure occur, the crew should refer to the FCOM to determine the OPT
FL. FCOM charts are only provided for two different Mach numbers.
RVSM
At intervals of approximately one hour, cross check the validity of primary
altimeters. A minimum of two must agree within +/- 200 ft. Failure to meet
RVSM requirements should be notified to ATC and recorded in the Aircraft
Maintenance Log. Vol 2 Pt 2 refers.
to
bu
y
.d o
.c

Cruise
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.20.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
LATERAL NAVIGATION
When approaching each waypoint, visually check track and distance to the next
waypoint on the F-PLN page against CFP or enroute chart. It is not necessary to
verbalise this check. Make optimum use of MCDU (FCOM 4 refers).
On aircraft equipped with GPS, a navigation accuracy check is not required as
long as GPS PRIMARY is available.
Without GPS PRIMARY, navigation accuracy should be monitored, particularly
when any of the following occurs:
IRS only navigation

The PROG page displays LOW accuracy
"NAV ACCUR DOWNGRAD" appears
If HIGH ACCURACY is displayed on the PROG page, the FM accuracy meets

the required criteria. Nevertheless, perform a check periodically when navigation
aids are available to allow any FM position error to be quantified against the raw
data on the ND. There are two methods of performing an accuracy check:
lic
5.20.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Cruise
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
On the RAD NAV page, manually tune a VOR/DME to a station that is

within range and select the associated needle on the ND. Check that the
needle (which is raw data) overlies the corresponding blue navaid symbol
(which is FM computed) and that the DME distance is equal to the
distance showing between the aircraft symbol and the navaid symbol on
the ND.
Insert a VOR/DME ident in BRG/DIST TO field on the PROG page and
compare the FM computed BRG/DIST with the raw data on the ND.
When operating on routes with Required Navigation Performance (RNP), ensure

that the ESTIMATED navigation accuracy indicated on the PROG page is better
than the RNP value for the route.
h a n g e Vi
e
VERTICAL NAVIGATION
Step Climb
Since the optimum altitude increases as fuel is consumed during the flight, from
a cost point of view, it is preferable to climb to a higher cruise altitude every few
hours. This technique, referred to as a Step Climb, is typically accomplished by
initially climbing approximately 2000 ft above the optimum altitude and then
cruising at that flight level until approximately 2000 ft below the new optimum
altitude. In RVSM airspace, it is possible to bracket the optimum altitude by 1000
ft.
Step climbs can either be planned at waypoints or be optimum step points
calculated by the FMGS. The FMGS computed step climb provides for minimum
trip cost for the flight. The CFP tends to indicate a step climb as soon as the
predicted aircraft weight would allow. Constraints in the CFP design mean that
climbs can only be designated at waypoints and not at the ideal point. For most
flights, one or more step climbs may be required. It may be advantageous to
request an initial cruise altitude above optimum, if altitude changes are difficult to
obtain on specific routes. This could minimise the possibility of being held at a
low altitude and high fuel consumption condition for a long period of time. The
requested/cleared cruise altitude should be compared to the REC MAX altitude.
Before accepting an altitude above optimum, determine that it will continue to be
acceptable considering the projected flight conditions such as turbulence,
standing waves or temperature change.
to
bu
y
.d o
.c

Cruise
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.20.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
5.20.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Cruise
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
The selected cruise altitude should normally be as close to optimum as possible.

As deviation from optimum cruise altitude increases, economy decreases.
The following diagram shows an approximation of the fuel penalties for flying at
cruise levels other than optimum. Note that these figures only reflect fuel
penalties as opposed to overall trip cost. For example, flying at a higher level
often increases the flight time and consequently the overall trip costs.
h a n g e Vi
e
FUEL
Fuel Monitoring
The flight plan fuel burn from departure to destination is based on certain
assumed conditions. These include gross weight, cruise altitude, planned route,
temperature, cruise wind and cruise speed. Actual fuel consumption should be
compared with the flight plan fuel consumption at least once every hour.
Many factors influence fuel consumption such as actual flight level, cruise speed,
aircraft weight and unexpected meteorological conditions. If fuel consumption
appears higher than expected, then calculate the actual kg/gnm and compare
this with the planned figure on the Fuel Progress Log. The actual kg/gnm is
calculated by dividing the actual fuel burn per hour by the groundspeed.
If planned and actual fuel figures deviate significantly without reason, then
suspect a fuel leak and apply the appropriate procedure.
ECAM FOB, Fuel Prediction (FMGC) and CFP should be used to maintain an
awareness of the current and predicted fuel state. Both the ECAM FOB and the
fuel remaining determined by calculating the difference between BEFORE
START fuel and ECAM FUEL USED, are recorded on the Fuel Log. The lesser
(more conservative) of these figures is used for decision making.
to
bu
y
.d o
.c

Cruise
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.20.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
c u -tr a c k
.c
At least once ever hour, when passing over a waypoint, perform the following
fuel check:
lic
.d o
.c
5.20.9
REV 1 (6
JUN 05)
w
C
c u -tr a c k
A330/A340
FCTM
.d o
Cruise
bu
N
y
bu
C
lic
to
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Enter ECAM FOB in the GAUGE / TOTALISER column, on the CFP

progress log.
To the right of FOB, enter the F.USED from the ECAM CRZ page.
Subtract the F.USED from the BEFORE START fuel to obtain the Fuel
Remaining, and enter to the right of F.USED.
Enter the lesser of FOB and Fuel Remaining in the ACTUAL FUEL
column.
From the ACTUAL FUEL subtract the FR X CONT X MAND and enter the
result in the CONT / MAND / EXTRA column for the waypoint.
Compare this result against the CFP planned contingency fuel in the
adjacent column.
Fuel Temperature
Extended cruise operations increase the potential for fuel temperatures to reach
the freeze point. Fuel freeze refers to the formation of wax crystals suspended in
the fuel, which can accumulate when fuel temperature is below the freeze point.
This can prevent proper fuel feed to the engines.
During normal operations, fuel temperature rarely decreases to the point that it
becomes limiting. Fuel temperature will slowly reduce towards TAT. If fuel
temperature approaches the minimum allowed, attempt to achieve a higher TAT
by descending or diverting to a warmer air mass, or increasing Mach number.
When flying above the tropopause, TAT may only increase if descent is made to
a level below the tropopause. In this case, consider climbing to increase TAT.
Below the tropopause, if a descent is required, the CFP step below altitude
usually results in sufficient increase in TAT. A 4000 ft descent will normally give
a 7C increase in TAT. An increase of 0.01 Mach will increase TAT
approximately 0.7C. Up to one hour may be required for the fuel temperature to
stabilise.
ADVERSE WEATHER
In addition to the adverse weather phenomena encountered in the climb, a
further consideration in the cruise is CAT. CAT can be anticipated by reference
to weather charts and pilot reports. As water droplets are not associated with
CAT, it cannot be detected by the radar. If appropriate, consider avoiding CAT
vertically. Be aware however, that the buffet margin reduces with increasing
altitude.
If severe turbulence is encountered and thrust changes become excessive,
select the A/THR off and set N1 manually with reference to the severe
turbulence table in the QRH.
h a n g e Vi
e
POLAR OPERATIONS
Planning
During the pre-flight planning stage, operations through extremely cold air
masses or at extreme latitudes should be taken into consideration. Certain MEL
items may preclude operations at such latitudes. Some routes may require more
restrictive navigational capability or redundancy such as MNPS, RNP or RVSM
procedures. Consideration should also be given to engine out, decompression
and SAROPS contingencies.
Communications
Above 82N, SATCOM is unavailable. HF frequencies and HF SELCAL must be
arranged prior to the end of SATCOM coverage. Routine company
communications procedures should include "flight following" to enable immediate
assistance during a diversion or other emergency. Abnormal solar winds may
affect HF communications. During periods of high cosmic or sunspot activity it
may be difficult to maintain enroute communications by any method. This will
remain the case until datalink upgrades become available. Experience has
shown that there may be significant periods enroute when no communications
with ATC are possible.
Navigation
In polar regions the magnetic heading reference is completely unusable for
navigation purposes. Magnetic variation is typically extreme and often not
constant at a certain point. It will also change rapidly as aircraft position
changes. TRUE NORTH reference is automatically commanded in the polar
zone. The computer flight plan is conventional. For some high latitude airports,
grid headings are shown on the instrument approach procedures. Note that
unmapped areas in the GPWS terrain database may display MORA as 51.1 on
the ND, regardless of the aircraft altitude.
The primary mode for AP/FD lateral navigation for polar operations is NAV,
which may be used with the heading reference switch in the either position. HDG
mode may be used for deviations from planned route but TRU heading reference
should be selected. If the F-PLN crosses either the North Pole or the South Pole,
a rapid heading and track reversal occurs passing the polar waypoint. If
operating in HDG while near either pole, it is necessary to frequently update the
heading selector to reflect the rapidly changing or reversed heading, otherwise
the AP/FD may command an unwanted turn. For this reason, NAV is the
preferred mode.
to
bu
y
.d o
.c

Cruise
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.20.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
5.20.11
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Cruise
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Due to differences in the FMGS and IRS positions and split IRS operation near
the pole, the AP/FD will disengage if in HDG upon polar waypoint passage. It
may be re-engaged and will function normally several miles after passing the
polar waypoint. Loss of both GPS units results in an increased Estimated
Position Error (EPE) and possible display of the "NAV ACCUR DOWNGRAD"
message, but would not normally prevent polar operations. Loss of one or two
IRs does not significantly affect navigation accuracy. However, operation with
only one IRU would require a diversion to the nearest suitable airport.
True bearing VORs are not stored in the FM database. Such navigation aids
may be built using standard three letter idents via Data > Stored NAVAIDS. They
must be built referenced to MAG and therefore do not show correct relative
bearings on the TRU referenced ND since the bearing is internally corrected by
the FMGS.
The correct raw data radial is presented with either ILS or VOR mode selected
on the ND. However, MAG is in amber indicating non-compatibility with the ND
reference, when it is actually compatible. It is important to be aware of this when
using this VOR information for en-route orientation purposes.
The recommended technique is to tune VORs using the frequency option rather
than the ident on the RAD NAV page. This will present raw data only with correct
relative bearings. NDBs in the Arctic are generally powerful and do provide
reliable relative bearings.
If TRUE is selected for the ILS approach, the ILS may be flown to Cat 1 limits
only.
DESCENT PREPARATION
Obtain the latest destination weather approximately 15 minutes prior to descent
and update the FMGS for the descent and arrival. During FMGS programming
the PF will be head down, so it is important that the PNF does not become
involved in any tasks that preclude close monitoring of the aircraft. The fuel
predictions will be accurate if the F-PLN is correctly entered in terms of arrival,
missed approach and alternate routeing. Once the FMGS has been
programmed, the PNF should cross check the information prior to the approach
briefing. With the descent winds entered and the F-PLN arrival properly
validated, the FMGS can compute an accurate TOD position. Pilots should
crosscheck the FMGS TOD position against their own independently calculated
TOD point, based where possible on a DME distance from a navaid.
Outport stations should be contacted via ACARS preferably or VHF to advise of
significant changes to the arrival information, ATA defect codes, or defects which
could affect the normal taxi in and shutdown procedures, or dispatch on the next
sector, etc. HKG need only be advised if Auto ACARS uplink of information is
inoperative. Volume 2 Part 2 refers.
h a n g e Vi
e
APPROACH BRIEFING
The main objective of the approach briefing is for the PF to inform the PNF of his
intended course of action for the approach. Additionally, potential threats should
be highlighted, along with the strategies to minimise these threats. The briefing
should be practical and relevant to the actual weather conditions expected. It
should be given at a time of low workload if possible, to enable the crew to
concentrate on the content. It is important that any misunderstandings are
resolved at this time. FCTM Ch 10 refers.
to
bu
y
.d o
.c

Cruise
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.20.12
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
5.30.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Descent
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
TOD COMPUTATION
The FMGS calculates the TOD point backwards from a position 1000 ft on the
final approach with speed at VAPP. It takes into account any descent speed and
altitude constraints and assumes managed speed is used. The first segment of
the descent will always be at idle thrust until the first altitude constraint is
reached. The idle segment assumes a small amount of thrust above idle to
provide some flexibility to maintain descent profile in the event that engine
anti-ice is used or if descent winds vary from forecast. Subsequent segments will
be "geometric", i.e. the descent will be flown at a specific angle, taking into
account any subsequent constraints. If the STAR includes a holding pattern it is
not considered for TOD or fuel computation. The TOD is displayed on the ND
track as a symbol: x
h a n g e Vi
e
LATERAL NAVIGATION
With the AP/FD in NAV, the aircraft will follow the programmed STAR. If a
deviation from the programmed STAR is required, e.g. ATC vectors or weather
avoidance, select HDG. If HDG or TRK is selected while in DES mode, reversion
to V/S mode occurs at current vertical speed, accompanied by a triple click aural
warning. When cleared to a specific waypoint, perform a DIR TO to ensure
correct waypoint sequencing, and re-engage DES mode.
VERTICAL NAVIGATION
The AP/FD descent modes may be either
Managed
Selected
Both descent modes can be flown with either managed or selected speed.
Managed Descent Mode

DES mode is available if NAV is engaged. To initiate a managed descent, set
the ATC cleared altitude on the FCU and push the ALT selector at TOD. DES
mode engages and is annunciated on the FMA. If an early descent is required by
ATC, DES mode gives 1000 ft/min rate of descent until the computed profile is
regained.
Be aware that altitude constraints in the flight plan are observed only when the
descent is managed, i.e. when DES is displayed on the FMA. Any other vertical
mode will disregard altitude constraints.
During a managed descent, with DES displayed on the FMA and the F-PLN
accurately reflecting all altitude constraints, it is permissible to select the lowest
ATC cleared altitude on the FCU and monitor that the correct profile is flown.
To avoid overshooting the computed descent path, push the FCU ALT selector a
few miles prior to the calculated TOD. This method will ensure a controlled entry
into the descent and is particularly useful in situations of high cruise Mach
number or strong upper winds.
If the descent is delayed, a "DECELERATE" message appears on the PFD and
MCDU scratchpad. Consider selecting speed towards Green Dot and when
cleared for descent, push for DES and push for managed speed. The speed
reduction prior to descent will enable the aircraft to recover the computed profile
more quickly as it accelerates to the managed descent speed.
to
bu
y
.d o
.c

Descent
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.30.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
5.30.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Descent
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
When DES is engaged and speed is managed, the AP/FD guides the aircraft
along a pre-computed descent path determined by a number of factors such as
altitude constraints, wind and descent speed. However, as the actual conditions
may differ from those planned, the DES mode with managed speed operates
within a speed range around a target speed to enable the aircraft to maintain the
descent path.
If the aircraft gets high on the computed descent path, the speed will increase
towards the upper limit of the speed range. If this increase in speed does not
allow a descent constraint to be achieved, a message "EXTEND
SPEEDBRAKES" is displayed on the PFD and MCDU scratchpad. A path
intercept point n, which assumes half speedbrake extension, will be displayed
on the ND descent track. When regaining the descent profile, retract the
speedbrakes to prevent the A/THR applying thrust against speedbrakes. If the
speedbrakes are not retracted, the "SPD BRK" message on the ECAM memo
becomes amber and "RETRACT SPEEDBRAKES" is displayed on the PFD.
If the aircraft gets low on the computed descent path, the speed will decrease
towards the lower limit of the speed range. When the lower speed limit is
reached, the A/THR reverts to SPEED/MACH mode and applies thrust to
maintain the descent path at this lower speed. A similar path intercept point n
will be displayed on the ND.
The computed descent path remains unchanged if speed is selected. As the
selected speed may differ from the speed used for the pre-computed descent
path and the speed variation around target no longer applies, the aircraft may
deviate from the descent path.
h a n g e Vi
e
Selected Descent Mode

The selected AP/FD modes in descent are OP DES, V/S or less commonly FPA.
During a selected descent with OP DES, V/S or FPA displayed on the FMA,
successive altitude constraints must be set on the FCU. If under radar vectors,
set the next ATC cleared altitude on the FCU.
OP DES is used if ATC gives radar vector or clears the aircraft direct to a given
FL without any descent constraints. All FMGS descent altitude constraints will be
ignored. V/S mode is normally used to recover from a below profile condition.
To initiate a selected descent, set the ATC cleared altitude on the FCU and pull
the ALT selector at TOD. OP DES mode engages and is annunciated on the
FMA. In OP DES, the A/THR commands THR IDLE and the speed is controlled
by the elevators.
Speed may be either managed or selected. In managed speed, the descent
speed is displayed as a magenta target only and there is no longer a speed
target range. The computed descent path is ignored and consequently the speed
will not vary around the target. The AP/FD does not consider any F-PLN descent
altitude constraints and will fly an unrestricted descent down to the FCU selected
altitude.
V/S can be used to adjust the rate of descent. The use of low values of V/S, e.g.
less than 1000 fpm, may be appropriate for small altitude changes as it makes
the guidance smoother and needs less thrust variation. In areas of high traffic
density, low values of vertical speed will reduce the possibility of nuisance TCAS
warnings. As a guide, a value of -1000 ft/min is appropriate when in close
proximity to other aircraft. The A/THR mode will automatically revert to SPEED
and adjust thrust to maintain the target speed. In this configuration, the use of
speedbrakes is not recommended to reduce speed, as it is inconsistent with the
A/THR mode. When in V/S mode, pay particular attention to the speed trend, as
the AP will attempt to maintain the selected V/S irrespective of the effect this has
on the aircraft speed. If the pilot selects a very high V/S, the aircraft may be
unable achieve both the selected V/S and target speed with idle thrust. In this
case, the AP/FD will guide to the target V/S, and the speed will increase. When
VMAX is reached the AP will pitch the aircraft up so as to fly at a V/S to maintain
VMAX.
In OP DES or V/S mode, the level arrow b is displayed on the ND to indicate
the interception point with the altitude set in the FCU.
to
bu
y
.d o
.c

Descent
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.30.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Managed
The managed descent speed computed by the FMGS defaults to ECON speed
and provides the most economical descent profile as it takes into account
weight, actual and predicted winds, ISA deviation and Cost Index (CI). If a speed
is inserted into the PERF DES page for operational or policy reasons, then this
becomes the managed speed for the descent. Once the descent phase is active,
the managed descent speed cannot be modified. The managed descent speed
also takes into account any speed constraints, which may be modified during the
descent phase, e.g. the default speed limit, which is normally 250 kt below
10000 ft.
In turbulent conditions, adjust the speed or Mach target to allow adequate
margin below VMO/MMO. In severe turbulence, select turbulence penetration
speed. If the speed rapidly approaches the upper end of the managed speed
band with the autopilot engaged, a transient increase above VMO is possible.
Monitor the trend vector and, if an exceedance looks likely, either select a lower
speed target on the FCU or select OP DES and a suitable speed below VMO. If
the rate of exceedance is rapid, fly the aircraft manually. The autopilot will
disengage if high speed protection is activated.
Selected
If necessary, the descent speed can be selected on the FCU. This may be
required to comply with descent constraints, ATC clearances or during weather
avoidance or penetration. In selected speed, there is no longer a target speed
range.
DESCENT MONITORING
The PFD displays the magenta Vertical Deviation (VDEV) symbol which, within
+/- 500 ft, indicates the aircraft's vertical displacement from the computed
descent path. This information is only accurate if the aircraft is close to the lateral
flight plan with the waypoints having sequenced correctly. The actual VDEV is
also displayed numerically on the PROG page. VDEV information is available
both in managed and selected descent.
At lower altitudes, when in HDG or TRK, the energy circle on the ND indicates
the required distance to descend, decelerate and land from the present position.
The managed descent profile from high altitude is approximately 2 1/2. As an
estimation of the distance to touchdown is required to enable descent profile
monitoring, it is important to ensure that the F-PLN plan page reflects the
expected approach routeing. Gross errors in the descent profile are normally a
result of either incorrect programming of the MCDU or non-sequencing of F-PLN
waypoints, giving a false distance to touchdown.
FCTM Ch 10 refers.
lic
5.30.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Descent
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
DESCENT ADJUSTMENT
Weather avoidance or ATC vectoring may require descent profile adjustment.
If the aircraft is below the profile, select a lower target speed or adjust the V/S.
After regaining the profile, re-engage managed descent to maintain the FMGS
computed profile.
If the aircraft is above the profile, an increased rate of descent will be required.
Use speedbrake with OP DES, however be alert to the increased VLS at high
altitude. ATC and weather conditions permitting, a higher speed may be
selected.
DESCENT CONSTRAINTS
Descent constraints may be automatically included in the route as part of an
arrival procedure or may be manually entered through the F-PLN page. The
aircraft will attempt to achieve the constraints provided DES mode is engaged. A
DIR TO action in response to an ATC clearance to a STAR waypoint removes
procedural altitude constraints. However, if intermediate waypoints altitude
restrictions are relevant, e.g. for terrain awareness, or there is an ATC
requirement, then perform the "DIR TO" with ABEAMS. Constraints can be
re-entered at these abeam waypoints.
ARRIVAL OPERATING SPEEDS

ADVERSE WEATHER
FCTM 5.10 refers.
to
bu
y
.d o
.c

Descent
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
5.30.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
6.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
Holding And Approach

Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
Holding
Preface ..........................................................................................................6.10.1
ICAO/FAA Maximum Holding Airspeeds.......................................................6.10.1
Holding Speed And Configuration .................................................................6.10.1
Holding Entry Procedures .............................................................................6.10.1
In The Holding Pattern ..................................................................................6.10.2
Adverse Weather...........................................................................................6.10.2
Procedural
Procedure Turns............................................................................................6.20.1
Procedural Approaches.................................................................................6.20.1
Track Establishment......................................................................................6.20.1
Instrument Approaches
Preface ..........................................................................................................6.30.1
Navigation Accuracy......................................................................................6.30.1
Approach Briefing..........................................................................................6.30.1
Approach Category .......................................................................................6.30.1
Landing Minima .............................................................................................6.30.1
The Flying Reference ....................................................................................6.30.1
Delayed Flap Approach (Noise Abatement)..................................................6.30.2
Approach Phase Activation ...........................................................................6.30.2
Approach Speed Considerations...................................................................6.30.2
Deceleration And Configuration Change.......................................................6.30.5
F-PLN Sequencing ........................................................................................6.30.6
Use Of A/THR ...............................................................................................6.30.6
FCU Altitude Setting......................................................................................6.30.6
AP Disconnection ..........................................................................................6.30.6
h a n g e Vi
e
N
y
Adverse Weather...........................................................................................6.30.7
One Engine INOP..........................................................................................6.30.8
ILS Approach
Initial Approach..............................................................................................6.40.1
Interception Of Final Approach Course .........................................................6.40.1
Final Approach ..............................................................................................6.40.1
Glideslope Interception From Above .............................................................6.40.2
Late Runway Change....................................................................................6.40.4
Manual Raw Data ILS ...................................................................................6.40.5
Low Visibility Procedures ..............................................................................6.40.7
Autoland Operations On Runways Not Approved For LWMO,
Or When LVP Are Not In Force ...............................................................6.40.8
Non-precision Approach
Preface ..........................................................................................................6.50.1
Final Approach Strategy................................................................................6.50.2
Navigation Alerts ...........................................................................................6.50.4
F-PLN Crosscheck ........................................................................................6.50.5
Initial Approach..............................................................................................6.50.7
Intermediate Approach ..................................................................................6.50.7
Detailed Approach Sequence........................................................................6.50.8
Minimum Descent Altitude (MDA) ...............................................................6.50.10
Circling Approach
Preface ..........................................................................................................6.60.1
MCDU Preparation ........................................................................................6.60.1
Missed Approach - Circling ..........................................................................6.60.2
k
lic
.d o

Table Of Contents
to
bu
m
A330/A340
FCTM
05)
lic
6.00.2
wREV 1 (6 .JUN
c
.d o
c u -tr a c k
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
6.00.3
k
.d o
O.I. (30
w JUL 04)c
A330/A340
FCTM
lic

Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Visual Approach
Preface ..........................................................................................................6.70.1
Base Turn......................................................................................................6.70.1
Final Approach ..............................................................................................6.70.2
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.10.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Holding
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PREFACE
Whenever holding is anticipated it is preferable to maintain cruise level and
reduce speed to Green Dot, with ATC approval, to minimise the holding
requirement. However, other operational constraints may make this option
inappropriate. A holding pattern can be inserted at any point in the flight plan or
may be included as part of the STAR. In either case, the crew can modify the
holding pattern if required.
ICAO/FAA MAXIMUM HOLDING AIRSPEEDS

Volume 2 Part 2 refers.
HOLDING SPEED AND CONFIGURATION

If a hold is to be flown, provided NAV mode is engaged and the speed is
managed, an automatic speed reduction will occur to achieve a speed close to
Green Dot when approaching the holding pattern. Green Dot corresponds to an
approximation of the best lift to drag ratio and provides the lowest hourly fuel
consumption. If Green Dot is greater than the ICAO or state maximum holding
speed, request a higher speed from ATC. If this is not approved, select Flaps 1
and fly at the required speed. Fuel consumption will be increased when holding
in anything other than clean configuration.
HOLDING ENTRY PROCEDURES

The FMGS computes the applicable hold entry which should be cross-checked.
The hold entry requirements are detailed in PANSOPs. AERAD Guide refers.
h a n g e Vi
e
IN THE HOLDING PATTERN

As the number of holding patterns to be flown cannot be inserted in the FMGS,
the hold distance is not included in the descent path computation. After the
holding fix is sequenced, the FMGS assumes that only the current holding
pattern will be flown and updates predictions accordingly. Once in the holding
pattern the VDEV indicates the vertical deviation between current aircraft altitude
and the altitude at which the aircraft should cross the exit fix to be on the descent
path. In DES mode, the aircraft descends at 1000 ft/min whilst in the holding
pattern until reaching either the cleared altitude or altitude constraint. To exit the
holding pattern, select IMM EXIT. The aircraft will return directly to the holding fix
and continue with the FLT PLN. On leaving the hold, the speed will revert to
managed descent speed. Selected speed may be required to avoid an undesired
acceleration.
In the holding pattern, LAST EXIT UTC/FUEL information is displayed on the
HOLD page. These predictions are based on the fuel policy requirements
specified on the FUEL PRED page with no allowance for extra fuel assuming the
aircraft will divert following a missed approach. This information is computed with
defined assumptions, e.g. diversion routeing, flight level, Mach number and wind.
Deviation from these assumptions may affect the arrival fuel at the diversion
airport.
ADVERSE WEATHER
The most common adverse weather encountered whilst holding is icing. When
holding in icing conditions, maintain clean configuration whenever possible. Use
of engine anti-ice and total anti-ice increases fuel consumption as follows:
FCOM 3.05
Engine anti-ice
Total anti-ice
A333
+ 1.5%
+ 3.5%
A343
+ 4%
+ 5.5%
A346
+ 1%
+ 4%
to
k
.d o
.c
bu
y
m
c u -tr a c k
lic
to
lic
.d o

Holding
REV 1 (6 JUN 05)
A330/A340
FCTM
6.10.2
w
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.20.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Procedural
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PROCEDURE TURNS
Procedure turns must be flown using selected modes. On some approaches the
procedure turn must be completed within specified limits. The turn size is
determined by the ground speed at which the fix is crossed. If the fix is crossed
at an excessively high ground speed, the procedure turn protected airspace may
be exceeded. Initiate the turn at Green Dot and time for 1 min 15 sec from the
start of the turn. Select Flaps 1 when turning inbound. Monitor the track to
ensure the aircraft remains within the protected airspace. The published
procedure turn altitudes are minimum altitudes.
PROCEDURAL APPROACHES
The detailed requirements for procedural approaches are laid down in
PANSOPs. AERAD Guide refers.
TRACK ESTABLISHMENT
Outbound descent may be commenced immediately following station or fix
passage. Conversely, inbound descent may only be commenced when
established within 5 of the published track.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
This section covers general information applicable to all approach types.
Techniques which apply to specific approach types are covered later in the
chapter.
During the approach phase, the aircraft may be operating at or below MSA, often
in adverse weather in a high workload environment. Although ATC may be
providing radar vectors to the initial or final approach fix, maintaining good
situational awareness during the approach is essential.
NAVIGATION ACCURACY
If GPS PRIMARY is not available, a navigation accuracy check is to be carried
out prior to any approach. The navigation accuracy status determines:
lic
6.30.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Which AP/FD modes are to be used.

The non precision approach strategy (guidance modes).
EFIS display.
EGPWS TERR pb selection.
The final approach course may be intercepted in NAV mode if GPS PRIMARY is
available or if the navigation accuracy check is positive. Without GPS PRIMARY,
navigation accuracy should be monitored in accordance with established
procedures.
Navigation Accuracy Check, FCOM 3.04.34 refers.
Navigation Accuracy requirements for the various approach guidance modes,
FCOM 3.03.18 and 3.03.19 refer.
APPROACH BRIEFING
Vol 2 Pt 2 and FCTM Ch 10 refer.
APPROACH CATEGORY
The Airbus is classified as a category "D" aircraft.
LANDING MINIMA
Vol 2 Pt 2 refers.
THE FLYING REFERENCE

Use of HDG/V/S and the FD is recommended for ILS approaches. It is a
requirement to use the FPV and the FPD for non-precision approaches.
h a n g e Vi
e
DELAYED FLAP APPROACH (NOISE ABATEMENT)

Do not compromise the stabilised approach criteria to satisfy noise abatement
procedures. Where airport noise abatement procedures specify the use of
minimum flap for landing, full flap should be used unless operational or
non-normal procedures require a different configuration.
APPROACH PHASE ACTIVATION

Activation of the approach phase initiates a deceleration from managed descent
speed. In NAV or LOC mode, the approach phase activates automatically when
sequencing the deceleration pseudo-waypoint. When in HDG mode or if an early
deceleration is required, the approach phase can be activated via the PERF
page. When the approach phase is activated, the magenta target speed
becomes VAPP but the A/THR will maintain the minimum speed for the actual
configuration.
APPROACH SPEED CONSIDERATIONS

VAPP
VAPP displayed on the PERF APPR page is equivalent to VLS for gross weight
and landing flap configuration, plus an increment based on the inserted tower
wind component. This increment is equivalent to the higher of 5 kt or 1/3 of the
tower headwind component for the landing runway in the F-PLN. VAPP is
computed at the predicted landing weight while in CRZ or DES phase, and using
the current gross weight once the approach phase is activated.
The minimum 5 kt increment must be retained if A/THR is ON or if severe icing
conditions are anticipated. The pilot can insert a lower VAPP on the PERF APPR
page, down to VLS if landing is performed with A/THR OFF, no wind, downburst
or icing. A higher VAPP may be inserted if gusty wind or downburst conditions
are anticipated but the increment to VLS is limited to 15 kt.
Managed speed should be used for final approach as it provides ground speed
mini guidance even when the VAPP has been manually inserted.
Ground Speed Mini and VAPP Target

The purpose of ground speed mini is to keep the aircraft energy level above a
minimum value, whatever the wind variation or gust. This allows for more
efficient thrust management. Thrust varies in the correct sense, but within a
smaller range (15% N1) in gusty conditions.
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.30.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
The minimum energy level is the energy the aircraft will have at landing with the
expected tower wind, represented by the groundspeed at that time which is
called GS mini:
GS mini = VAPP Tower headwind component
In order to achieve this, the aircraft groundspeed must never drop below GS mini
during the approach while the winds are changing. Therefore, the IAS (VAPP
target) must vary in order to cope with the gusts or wind changes to ensure that
the groundspeed is at least equal to GS mini. The FMGS uses the instantaneous
wind component provided by the IRS to compute the VAPP target speed:
VAPP Target = GS mini + instantaneous headwind component
The managed speed target moves on the speed scale as a function of wind
variation, e.g. when VAPP target goes up = headwind gust. The pilot should
ideally check the reasonableness of the target speed by reference to the
groundspeed readout on the top left of the ND.
The VAPP target speed is limited to VFE 5 kt in the case of strong gusts, and
VAPP in case of a tailwind or if the instantaneous headwind component is lower
than the inserted tower wind.
Below 400 ft RA, the VAPP target speed computation is modified as the
instantaneous headwind component is progressively filtered out to avoid high
IAS in the flare. VAPP target computation progressively assumes that the
instantaneous wind equals the inserted tower headwind component so that the
flare is entered at an IAS near VAPP.
lic
6.30.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
Example of GS MINI
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.30.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
DECELERATION AND CONFIGURATION CHANGE

Managed speed is recommended for the final approach. Once the approach
phase has been activated, the A/THR controls the speed to the minimum
required for the current configuration. These speeds are:
Green Dot for Flaps 0

S speed for Flaps 1
F speed for Flaps 2 and 3 (if Flaps 3 is not selected as the LDG CONF)
VAPP for Flaps Full (or for Flaps 3 if selected as the LDG CONF)
To achieve a constant deceleration and minimise thrust variation, select the next
configuration when reaching the target speed + 10 kt, e.g. when the speed
reaches Green Dot + 10 kt, select Flaps 1. The IAS must be lower than VFE
Next. Using this technique, the average deceleration rate will be approximately
10 kt/nm in level flight (20 kt/nm with speedbrake extended).
When below VFE CONF 1, the PF calls for "Flaps 1". The PNF visually confirms
on the PFD that the speed is below VFE CONF 1, calls "Speed checks, Flaps 1"
and then selects the flap lever to Flaps 1. He then monitors the E/WD to confirm
that "1" is displayed in blue during transit and becomes green when the
slats/flaps reach the correct position. This sequence should be repeated for
subsequent flap settings.
If ATC requires a specific speed, select it on the FCU. When the speed control
no longer applies, resume managed speed. If flying the intermediate approach in
selected speed, activate the approach before resuming managed speed,
otherwise the aircraft will accelerate to the previous descent speed.
In certain circumstances, e.g. tailwind or heavy weight, the deceleration rate may
be insufficient. In this case, the landing gear may be lowered before selection of
Flaps 2 and preferably below 220 kt to avoid undue stress to the gear doors.
Speedbrakes may also be used to increase the deceleration rate but be aware of
the following:
lic
6.30.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Increase in VLS
Limited effect at low speeds
Auto-retraction when selecting (A343: CONF 3), (A333: CONF Full). There
is no auto-retraction on A346 and enhanced A333 aircraft. Instead an
ECAM caution SPD BRK STILL OUT alerts the crew to this fact if the
engines are above idle or if the speedbrakes have been extended for more
than 5 seconds when the aircraft is below 800 ft during the approach.
For consistency between types, retract the speedbrakes prior to selection of

Flaps 3.
h a n g e Vi
e
F-PLN SEQUENCING
In NAV mode, the F-PLN will sequence automatically. In HDG/TRK mode, the
F-PLN will only sequence automatically if the aircraft flies close to the
programmed route. Correct F-PLN sequencing is necessary to ensure that the
programmed missed approach route is available in the event of a go-around. If
under radar vectors and automatic waypoint sequencing does not occur, the
F-PLN should be manually sequenced. This can be achieved by either using the
DIR TO RADIAL IN function or by deleting the FROM WPT repeatedly on the
F-PLN page until the next likely WPT to be overflown is displayed as the TO
WPT on the ND. However, when established on an ILS or LOC approach, do not
perform a DIR TO as this will result in LOC reverting to NAV mode. In this case,
the APPR or LOC will have to be re-armed to re-establish on the approach.
USE OF A/THR
A/THR is recommended for all approaches as it provides accurate speed control.
If planning to use manual thrust, A/THR should be disconnected by 1000 ft on
the final approach.
The use of A/THR does not absolve the pilot from his responsibility to monitor its
performance. If A/THR operation is not satisfactory, use manual thrust.
FCU ALTITUDE SETTING

When established on final approach, set the missed approach altitude on the
FCU. This can be done at any time after G/S or FINAL APP mode engages. For
a selected non-precision approach using FPA, the missed approach altitude
must only be set when the aircraft is below the missed approach altitude and no
further level segment is required. This will prevent an unwanted ALT capture on
final approach.
Do not set the MDA or DH on the FCU. Setting the MDA or DH on the FCU
would result in an unwanted ALT* when approaching MDA or DH, resulting in the
approach becoming destabilised at a critical stage.
AP DISCONNECTION
When disconnecting the AP for a manual landing, avoid the temptation to make
unnecessary inputs on the sidestick.
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.30.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
ADVERSE WEATHER
If severe windshear or downburst conditions are expected, consider either
delaying the approach or diverting to another airport. Assess conditions for a
safe landing by interpreting:
The weather radar picture and PWS alerts.

ATIS/actual wind velocity.
Local terrain characteristics.
ATC/pilot reports.
Choose the most favourable runway in conjunction with the most appropriate
approach navaid (e.g. ILS or GPS) and consider using FLAPS 3 for landing.
Should windshear be encountered, FLAPS 3 will allow better aircraft performace
during the escape manoevre. However, with the decrease in drag associated
with flaps 3, speed control during the approach will require close attention to
avoid excessive speed on landing. This may also be exacerbated by using an
increased VAPP. If the approach is continued however, consider the following:
Increasing VAPP displayed on the PERF APP page up to a maximum of

VLS + 15 kt. This is particularly important in downburst conditions.
Managed speed should be used as it provides GS mini function.
Engaging the AP for a more accurately flown approach.
The PWS is described in detail in FCOM 1.34. Additionally, the FMGEC reactive
windshear warning system may be triggered in the event of windshear being
experienced by the aircraft. The reactive windshear warning system is described
in detail in FCOM 1.22.
On receipt of a reactive WINDSHEAR warning, apply the checklist actions from
memory. The PF calls Windshear Go, implying that no configuration change
will occur until clear of the shear. The following points should be stressed:
lic
6.30.7
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
If the AP is engaged, it should remain engaged. It will disengage if and

when prot is reached.
The configuration should not be changed until positively out of the shear
as the operation of the landing gear doors incurs additional drag.
Follow the SRS, even if this requires the use of full back stick. As the
speed begins to recover, the pilot can reduce back stick while still following
SRS orders until well clear of the shear.
The PNF should call IAS, RA, V/S and significant related trends.
When clear of the shear, report the encounter to ATC.
On receipt of a predicitive WINDSHEAR AHEAD warning, apply the checklist

actions from memory. Select TOGA and follow the SRS. The PF calls
Go-Around Flaps ___, reducing the flap setting by one. Continue the go-around
and clean up as normal unless windshear is encountered or a WINDSHEAR
warning occurs.
h a n g e Vi
e
The checklist actions for predictive WINDSHEAR AHEAD warning on approach

allow that in the event a positive verification is made that no hazard exists, the
warning may be considered cautionary. This note to treat the predictive warning
as cautionary is included only as an acknowledgement of the PWS system
limitations. PWS technology relies on Doppler analysis of water particle
movement, and the geographical situation associated with particular wind
conditions may generate false warnings where no hazards exist. It should only
be treated as cautionary on careful analysis and where an early positive
verification can be made that no hazard exists.
Selection of the TERR ON ND pb will inhibit the display of the WINDSHEAR
AHEAD display on that pilots ND.
In gusty wind conditions, the A/THR response time may be insufficient to cope
with an instantaneous loss of airspeed. A more rapid thrust response can be
achieved by moving the thrust levers above the CL detent. The thrust will quickly
increase towards the corresponding TLA. The A/THR remains armed and
becomes active immediately the thrust levers are returned to the CL detent.
Therefore, the thrust levers should be returned to CL detent as soon as there is
a positive speed trend. There are two important points to note however:
Selecting the thrust levers above the CL detent below 100 ft AGL will
disconnect the A/THR. In this case, returning the thrust levers to the CL
detent will set climb thrust.
Selecting the thrust levers to the TOGA detent, even momentarily, will
engage the Go-Around mode.
If A/THR performance is unsatisfactory, it should be disconnected and manual

thrust used.
In the event of ice accretion, approach speed increments should be applied.
ONE ENGINE INOP

FCTM Ch 8 refers.
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.30.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.40.1
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

ILS Approach
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
INITIAL APPROACH
Check that the LS pb has been pressed and that the LOC and GS scales are
displayed on the PFD, and the ILS ident is correctly displayed.
INTERCEPTION OF FINAL APPROACH COURSE

The criteria that must be met prior to pressing the APPR pb is detailed in FCOM
3.03.18
Pressing the APPR pb arms the approach mode. LOC and G/S are displayed in
blue on the FMA. The second AP, if available, should be selected at this stage.
If the initial ATC clearance is to intercept the localiser only, press the LOC pb on
the FCU until cleared for the approach.
Executing some subsequent mode changes through the MCDU (e.g. Direct to
FAF to update the flight plan), will disengage the armed modes of G/S and LOC
blue. Reselection of APPR pb will be necessary.
Monitor aircraft position to anticipate and confirm the correct LOC and G/S beam
is being intercepted to protect against false captures. Observe the FMA for the
correct modes during the ILS capture process.
FINAL APPROACH
Plan to intercept the glideslope from below with at least Flaps 1 selected. When
approaching one dot below the glideslope select Flaps 2. In managed speed, the
aircraft will decelerate to F speed. If the glideslope is intercepted in level flight
below 2000 ft AAL the aircraft may need to be configured beyond CONF 2 prior
to glideslope capture in order to achieve the stabilised approach criteria.
After glideslope capture, set the missed approach altitude on the FCU and check
that it is displayed on the PFD. If the F-PLN has sequenced correctly, either
automatically or manually, a blue go-around procedure will be displayed on the
ND, indicating that NAV mode is available for the go-around. If there is no
go-around procedure displayed, the F-PLN may be incorrectly sequenced and
the go-around will have to be flown using selected modes and raw data.
Select the gear down approaching 2500 ft AAL. Selecting L/G down is the cue
for PNF to arm ground spoilers and set NOSE switch to TAXI, and RWY TURN
OFF switch ON. Once the gear is down, select the remaining stages of flap.
h a n g e Vi
e
GLIDESLOPE INTERCEPTION FROM ABOVE

The following procedure should only be applied when established on the
localiser, with either LOC* or LOC displayed in green on the FMA. The best rate
of descent is achieved with the landing gear extended, Flaps 2 selected and
flying at VFE2 - 5 kt. Speedbrakes may also be used, noting the considerations
detailed in Deceleration and Configuration Changes earlier in this chapter. Apply
the following procedure without delay:
Confirm LOC capture and G/S armed.

Select the FCU altitude above aircraft altitude to avoid unwanted ALT*.
Select V/S -1500 ft/min initially. V/S in excess of 2000 ft/min will result in
the speed increasing towards VFE.
V/S rather than OP DES must be used to ensure that the A/THR is in SPEED
mode rather than IDLE mode. Carefully monitor the rate of descent to avoid
exceeding VFE or triggering a GPWS warning. When approaching the G/S, G/S*
engages. Monitor the capture against raw data. Use normal procedures for the
remainder of the approach.
If at any stage it becomes apparent that the stabilised approach criteria will not
be met, perform a go-around.
to
bu
y
.d o
.c

ILS Approach
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.40.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.40.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

ILS Approach
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LATE RUNWAY CHANGE

If an airport has a number of active landing runways, programme the SEC F-PLN
with the ILS for an alternative runway during the approach preparation, to cover
the possibility of a late runway change. There is no requirement to enter the
complete STAR.
If a runway change occurs and there is time available to achieve the approach
stabilisation criteria, apply the following procedure:
Pull HDG. At this point, LOC and G/S revert to HDG and V/S.
Activate the SEC F-PLN.
Adjust the HDG to intercept second runway LOC.
Adjust V/S as required.
Confirm ILS ident on PFD.
Press APPR pb on FCU.
Monitor ILS capture.
Confirm correct missed approach altitude is set.
Confirm correct TO waypoint on the ND to ensure NAV mode is available
in the event of a missed approach.
to
bu
y
.d o
.c

ILS Approach
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.40.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.40.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

ILS Approach
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
MANUAL RAW DATA ILS

The ILS may be flown using raw data with the FPV as the flying reference. Set
the TRK index to the ILS inbound course. When tracking the LOC, the tail of the
FPV will be coincident with the TRK index. This allows the drift to be taken into
account for accurate LOC tracking. The ILS course pointer and the TRK
diamond are displayed on the PFD compass and can be used to assist in
accurate tracking once established. Rose LS may also be used for raw data
monitoring.
When 1/2 dot below the G/S, initiate the interception of the G/S by smoothly
flying the FPV down to the glide path angle. A 3 flight path angle is indicated on
the PFD by the top of the tail of the FPV almost touching the horizon. It is also
indicated by the bottom of the FPV almost sitting on the -5 pitch scale, but this
reference becomes difficult to use in stronger crosswinds.
h a n g e Vi
e
Flaps full
ILS antenna
at 50 ft at
threshold
Glide
Path
()
G/S
Trans
A
25
No flare
Pitch
angle
(A333/A343:
3.7) (A346:
3)
Touchdown
Point C
B
A333/
A343
A346
A333/
A343
A346
348 m
1142 ft
153 m
502 ft
201 m
661 ft
195 m
640 ft
147 m
481 ft
291 m
955 ft
132 m
433 ft
169 m
555 ft
159 m
522 ft
122 m
400 ft
ILS Final Approach and Landing Geometry
to
k
.d o
.c
CONDITIONS:
bu
y
m
c u -tr a c k
lic
to
lic
.d o

ILS Approach
REV 1 (6 JUN 05)
A330/A340
FCTM
6.40.6
w
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.40.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

ILS Approach
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
LOW VISIBILITY PROCEDURES

Policy
FCOM 3.04.91 and Volume 2 Part 2 refer.
Approach Briefing
Additional briefing items should be considered before commencing CAT2/3
approaches. FCOM 3.04.91 and Volume 2 Part 2 refer.
Additional Factors
Airport capabilities regarding LWMO and autoland are stipulated on the relevant
Port Page. The airport authorities are responsible for establishing and
maintaining the equipment required for CAT 2/3 approach and landing. Prior to
planning a CAT 2/3 approach, ensure that LVP are in force.
Specific wind limitations for CAT 2/3 approaches and autolands apply. FCOM
3.01.22 refers.
Correct eye position is particularly important during low visibility approaches and
landings. When the eye reference position is too low, the visual segment is
further reduced by the cut-off angle of the glareshield.
Due to the reflection from water droplets or snow, do not use landing and/or
nose lights during low visibility approaches. This will ensure the greatest
possibility of achieving the required visual reference at minima.
Alert Height
The alert height is a specified radio height based on the characteristics of the
aircraft and its fail-operational landing system. If a failure of a required redundant
operational system occurs above this height, the approach must be discontinued
unless a reversion to a higher DH is possible. If a failure of a required redundant
operational system occurs below the alert height, the approach may be
continued. In this context, the alert height concept is relevant when CAT 3 DUAL
is displayed on the FMA and the aircraft systems are fail operational. The alert
height is 200 ft RA.
Cat 3 Dual
CAT 3 DUAL is annunciated on the FMA when the aircraft systems are
fail-operational, which means that in the case of a single failure, the AP will
continue to guide the aircraft on the flight path and the autoland system will
operate as a fail-passive system. In the event of a failure below the alert height,
the approach, flare and landing can be completed by the remaining part of the
fail-passive autoland system. In that case, no landing capability degradation is
annunciated on the FMA.
h a n g e Vi
e
Cat 3 Single
CAT 3 SINGLE is annunciated on the FMA when the aircraft systems are
fail-passive, which means that a single failure will lead to AP disconnect without
any significant out of trim condition or deviation from the flight path or attitude.
However, manual flight is then required.
System Faults And Failures

The failures that may affect the aircrafts CAT 2/3 capability are listed in the
QRH. Most of the systems required for the different autoland capabilities are
monitored by the FMGS. If a failure of a monitored system is detected after the
APPR pb is pressed, but above the alert height, a new approach capability will
be displayed on the FMA along with a triple click audio warning. In this case,
the reduced approach category will not be displayed on the Status page. In
addition, reduced approach capabilities displayed on the Status page are
removed and transferred to the FMA when the APPR pb is pushed. The
approach capabilities that can be displayed on the FMA are CAT 1, CAT 2, CAT
3 SINGLE or CAT 3 DUAL. There are also a number of failures which affect the
aircrafts landing capability that are not monitored by the FMGS and are
consequently not reflected on the FMA.
Following any failure that does not incur a landing capability downgrade on
ECAM STATUS or FMA, refer to the "Landing Capability Equipment Required"
table in the QRH to establish the actual landing capability.
Should a failure occur above 1000 ft RA, all ECAM actions, including DH
amendment if required, should be completed before reaching 1000 ft RA. If this
is not possible, initiate a go-around. An alert generated below 1000 ft (and down
to the Alert Height in CAT 3 DUAL) should normally lead to a go-around and a
reassessment of the system capability, unless the required visual reference has
been acquired. Below 1000 ft, there is generally insufficient time to properly
analyse the consequences of the fault, perform the necessary ECAM actions,
check system configuration and any limitations, then carry out a re-briefing. The
decision to continue the approach must be based on sound judgement.
AUTOLAND OPERATIONS ON RUNWAYS NOT APPROVED FOR

LWMO, OR WHEN LVP ARE NOT IN FORCE
Automatic landings may be practised in CAT 1 or better weather conditions for
training purposes. Fluctuations of the LOC and/or G/S might occur due to the
fact that protection of ILS sensitive areas, which applies during LVP, will not
necessarily be in force. It is essential that the PF be prepared to take over
manually at any time during a practice approach and rollout, should the
performance of the AP become unsatisfactory.
to
bu
y
.d o
.c

ILS Approach
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.40.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
Non-precision approaches are defined as:
lic
6.50.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
VOR
NDB
LOC
LOC-BC
RNAV
GPS
An RNAV approach is an instrument approach procedure that relies on aircraft

area navigation equipment (FMS) for navigational guidance. The FMS on Airbus
aircraft is certified RNAV equipment that provides lateral and vertical guidance
referenced from an FMS position. The FMS uses multiple sensors for position
updating including GPS, DME-DME, VOR-DME, LOC-GPS and IRS.
A GPS approach is an RNAV approach requiring GPS position update. Airbus
aircraft using FMS as the primary means of navigational guidance have been
approved to fly GPS approaches provided an RNP of 0.3 or smaller is used.
Non-ILS approaches are flown using FINAL APP or FPA pitch modes and LOC,
FINAL APP or TRACK lateral modes.
h a n g e Vi
e
FINAL APPROACH STRATEGY

General
The type of approach and the navigation accuracy will determine the approach
guidance modes. Where possible, it is preferable to fly a managed approach
(FINAL APP mode). Whether managed or selected guidance is used, use of the
AP is recommended.
Requirements For Using FINAL APP Mode

Low Temperature Altimetry

A managed vertical profile may not be flown if the airport temperature is below
-15C or, if published, the Baro-VNAV authorised temperature on the approach
chart. If the temperature is below the approved limit, the approach may still be
flown using selected vertical guidance (NAV/FPA) and the corrected procedural
altitudes (Volume 2 Part 2 refers). In this case, the approach is flown to an MDA.
VOR, VORDME, NDB And NDBDME Approach

VOR and NDB approaches are flown using one of the following three strategies:
Lateral and vertical guidance selected by the crew using TRK-FPA modes
Lateral guidance managed by the FM and vertical guidance selected by
the crew using NAV-FPA modes
Lateral and vertical guidance managed by the FM in FINAL APP mode
LOC And LOC BACK COURSE Approach

LOC approaches are flown using the LOC signal for lateral navigation and FPA
for vertical guidance.
LOC-B/C approaches are flown using the LOC-B/C signal (LOC signal from the
opposite runway) for lateral navigation and FPA for vertical guidance.
The LOC pb will arm the LOC or LOC B/C AP/FD mode as appropriate. The LS
pb on the EFIS CTL panel will display LOC or LOC B/C deviation on the PFD in
the correct sense. The PFDs VDEV symbol should be disregarded since it may
be incorrect if the Missed Approach Point is located before the runway threshold
If the LOC B/C approach is stored in the FMS database and inserted into the
F-PLN, the ILS frequency and associated back course are automatically tuned
and displayed in the RADNAV page. The CRS digits will be preceded by a B to
indicate back course.
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.50.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.50.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
If the LOC B/C is not stored in the FMS database, enter the ILS frequency and
the intended final approach course preceded by a B in the RADNAV page.
B/C will be displayed in magenta near the localiser deviation scale on both the
PFD and ND. This will provide deviation indications on the PFD and ND in the
correct sense, and proper directional guidance by the FG computers. However,
do not select the LS pb on ISIS, since the ISIS displays B/C localiser deviation in
the reverse sense.
For example:
Back Course Approach RW26

Insert ILS frequency 109.9 and back CRS B255
When the LOC pb is pressed, LOC B/C is annunciated in blue on the FMA to
indicate that the localiser back course is armed.
h a n g e Vi
e
RNAV and GPS Approach

The following two strategies are available for performing RNAV and GPS
approaches:
Lateral and vertical guidance managed by the FM in FINAL APP mode.
This is the recommended strategy. This strategy shall be used for

approach with minima defined as a decision altitude (DA).
Lateral guidance managed by the FM and vertical guidance selected by
the crew using NAV-FPA modes. This strategy may be used for approach
with minima defined as a minimum descent altitude (MDA), and shall be
used for approaches which are conducted when the temperature is below
the approved limit.
NAVIGATION ALERTS
General
A managed approach can be continued following a NAV ACCUR DOWNGRAD if
raw data indicates that the guidance is satisfactory.
RNAV and GPS Approach

Both GPSs must be available and GPS PRIMARY displayed on both MCDUs
prior to commencing the approach. However once the approach has
commenced, note that a single failure, such as NAV GPS 1 FAULT, will not
cause the loss of GPS PRIMARY, since the remaining GPS will update both
FMGS. If GPS PRIMARY LOST is displayed on the ND(s), it will be
accompanied by a triple-click aural alert, even though NAV ACCURACY HIGH
may still be displayed.
Crew procedures following a NAV FM/GPS POSITION DISAGREE caution, or if
GPS PRIMARY LOST is displayed on one or both NDs, depends on whether the
approach is standalone, or in overlay to a radio navaid procedure. FCOM
3.03.19 and QRH refer.
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.50.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.50.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
F-PLN CROSSCHECK
The approach in the navigation database must be validated by scrupulous
comparison between the database profile and the published procedure.
The following graphics show a particular case in which the final descent
approach path is equal to zero and the MAP is beyond the runway threshold.
This approach may not be flown in managed vertical modes. FCOM 3.03.19
refers.
h a n g e Vi
e
N
k
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.50.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.50.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Some charts provide a table of DME versus altitude. On those charts which do
not have this table, an expected FPA for the final approach can be calculated by
dividing the first 2 digits of the height at the FAF by the distance to go, e.g. 2000
ft at 6 nm equates to a 3.3 approach path. When using this method ensure that
the FAF crossing height is used, i.e. the figure in brackets on the chart and not
the FAF crossing altitude.
INITIAL APPROACH
Navigation Accuracy
Confirm GPS PRIMARY.
For RNAV and GPS approaches, 2 FMGS and 2 GPS are required to commence
the approach. The GPS MONITOR page must display NAV for both GPSs. Both
FMGS must be in GPS PRIMARY.
For non-precision approaches referenced to ground based radio aids, if GPS
PRIMARY is not available, check the navigation accuracy to confirm that the
planned approach strategy remains valid. If managed guidance does not
correspond with raw data, the use of selected guidance is mandatory. FCOM
3.03.19 refers.
Flying Reference
The FPV/FPD shall be used for all non-precision approaches.
INTERMEDIATE APPROACH
Approach Phase Activation
Normal approach stability requirements apply to non-precision approaches.
However, as non-precision approaches are rarely flown, consider inserting a
speed constraint of VAPP at the FAF to ensure a timely deceleration.
Final Course Interception

Do not modify the MCDU F-PLN, either laterally or vertically, from the final
approach course fix to the runway threshold or missed approach point.
For RNAV and GPS approach, ensure that the RNP automatically sequences to
the approach value. Typically, this occurs approximately 5 nm prior to the
intermediate approach fix (IF). The RNP approach value is 0.30 nm for a DCDU
equipped aircraft, and 0.37 nm for a non-DCDU equipped aircraft. If the RNP
does not automatically sequence, then the approach may be continued provided
the relevant RNP is manually entered.
h a n g e Vi
e
Ensure that the aircraft is laterally stabilised on the final approach course before
reaching the final approach fix (FAF). It acceptable to go direct to the approach
fixes or use the RADIAL IN function, provided the inbound course is closely
aligned with the final approach course and the resulting change to aircraft course
at the FAF is small.
To commence a managed approach, press the APPR pb. APP NAV is displayed
in green on the FMA with FINAL in blue. The V/DEV scale becomes active and
represents the vertical deviation from the managed descent profile, which may
include a level segment. The V/DEV scale will only be displayed if the LS pb is
not pressed. If the LS pb is pressed, V/DEV will flash in amber on the PFD.
If FINAL APP does not engage at the descent point, select an FPA value to allow
convergence with the final approach path. When VDEV is indicating that the
vertical profile has been reached (VDEV = 0), attempt to re-engage FINAL APP
mode by pressing the APPR pb.
For a selected approach, use TRK mode to establish final course tracking with
reference to raw data. When established on the final course, the selected track
will compensate for drift.
Should ATC give vectors towards the FAF, the use of the "DIR TO RADIAL IN"
function will provide a representation of the extended centreline and cross-track
error on the ND.
DETAILED APPROACH SEQUENCE

Managed Non-precision Approach
Fly the intermediate approach conventionally and configure the aircraft in a
similar manner to an ILS.
Use the following technique:
For RNAV and GPS approach, check both GPS in NAV mode on the GPS
MONITOR page and GPS PRIMARY is displayed on both MCDUs. Check
RNP has sequenced to the approach value (0.30/0.37 nm).
Check that deceleration occurs at the decel pseudo-waypoint, or if not,

activate the approach phase approx 10 nm prior to the FAF.
Select TRK/FPA display, confirming that the FPV and the FPD are
displayed on the PFD.
Ensure LS is not selected.
When cleared for the approach, press the APPR pb to arm APP NAV and
FINAL. If previously in NAV, APP NAV engages immediately.
Do not engage the second AP.
Check that the FMGS computed descent point, represented as a blue
arrow, is displayed on the ND. It may not necessarily coincide with the
chart descent point because the FMGS attempts to compute a continuous
final descent path.
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.50.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
V/DEV appears in approach phase with FINAL armed.

Ensure raw data is correctly displayed.
FINAL APP engages when the aircraft intercepts the vertical flight path.
Set the go-around altitude.
Use managed speed unless there are specific ATC requirements.
Start the chrono at the FAF to check FAF to MAP time.
Monitor the approach using FPV/FPD and VDEV on the PFD, XTK and
F-PLN waypoints on the ND with GPS PRIMARY, and confirmed by
navaids for VOR, NDB and overlay approaches. Cross-check altitudes and
distances with those published on the approach chart.
Selected Non-precision Approach

Fly the intermediate approach conventionally and configure the aircraft in a
similar manner to an ILS. The approach can be flown fully selected or if
navigation accuracy allows, managed laterally and selected vertically.
Partially Selected Approach

For a partially selected approach, i.e. managed laterally and selected vertically,
continue as for a managed non-precision approach with the following additional
consideration:
Fly the final approach in NAV and FPA modes (LOC and FPA for LOC or
LOC B/C approaches).
Fully Selected Approach

For a fully selected approach:
Fly the final approach in TRK/FPA modes.
Both Partially And Fully Selected Approaches

For both partially and fully selected approaches, use the following technique:
lic
6.50.9
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Check that deceleration occurs at the decel pseudo-waypoint, or if not,

activate the approach phase approx 10 nm prior to the FAF.
Select TRK/FPA display, confirming that the FPV and the FPD are
displayed on the PFD.
For LOC and LOC B/C approaches, ensure LS is selected. When cleared
to intercept the localiser or localiser back course, press the LOC pb to arm
the LOC mode.
1 nm prior to the final descent point, pre-select the desired FPA.
Pull the FPA selector 0.2 nm prior to the final descent point to achieve a
smooth interception of the final descent path.
Use managed speed unless there is a specific ATC speed requirement.
Start the chrono at the FAF to check FAF to MAP time.
h a n g e Vi
e
Monitor the approach using FPV/FPD and VDEV on the PFD, XTK and
F-PLN waypoints on the ND with GPS PRIMARY, and confirmed by
navaids for VOR, NDB and overlay approaches. For LOC and LOC B/C
course approaches, monitor lateral displacement using the LOC pointer on
the PFD. Cross-check altitudes and distances with those published on the
approach plate.
When the aircraft is below the missed approach altitude, set the missed
approach altitude on the FCU.
MINIMUM DESCENT ALTITUDE (MDA)

When approaching MDA, expand the scan to include outside visual cues. When
the required visual conditions to continue the approach are met, disconnect the
AP and select the FDs off. If not visual by the MDA or MAP, whichever occurs
first, go-around. Do not fly level at MDA whilst attempting to achieve the required
visual reference.
MDA is the lowest permitted altitude for AP use. If still engaged following a
managed approach, the AP will disconnect at MDA - 50 ft. The modes will revert
to TRK/FPA.
Do not set MDA as a target altitude on the FCU since this would cause a
spurious ALT* when approaching MDA and result in the approach becoming
destabilised at a critical stage.
to
bu
y
.d o
.c

c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.50.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
An instrument approach to one runway, followed by a visual pattern to land on
another runway, is termed a circling approach. Company circling minima may be
more limiting than the circling minima on the approach chart. Vol 2 Pt 2 refers.
MCDU PREPARATION
If a circling approach is likely, set up the MCDU as follows:
Programme the instrument approach into the active F-PLN.

Insert the arrival weather and the circling minima on the PERF APPR
page.
Programme the SEC F-PLN with the landing runway and associated
go-around procedure.
Insert the arrival weather on the SEC PERF APPR page.

Follow normal procedures for the ILS or non-precision approach to establish
inbound on the final segment of the instrument approach. Then use the following
technique:
lic
6.60.1
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Circling Approach
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Fly the inbound instrument approach with Flaps 3 at F speed and gear
down.
When reaching circling minima and with sufficient visual reference for
circling, push the FCU ALT pb.
Select a TRK of 45 (or as required by the published procedure) away
from the inbound approach course towards the circling area.
Select TRK/FPA and when wings level, start the chrono and time for 30
seconds.
Select ROSE NAV and 10 nm on the EFIS display to assist in positioning
the aircraft within the circling area.
Turn onto a downwind track to parallel the landing runway within the
circling area. Early on the downwind leg, activate the SEC F-PLN to
display the landing runway on the ND and provide an accurate GS mini
computation for final approach.
Abeam landing threshold, start chrono and time for 30 seconds.
Disengage AP and select both FDs off prior to the base turn.
Commence the base turn and select Flaps Full leaving the circling altitude.
Complete the Landing Checklist.
h a n g e Vi
e
MISSED APPROACH - CIRCLING

If a missed approach is required at any time while circling, make a climbing turn
towards the landing runway. Consider maintaining the missed approach flap
setting until close-in manoeuvring is completed. Follow ATC instructions or the
applicable missed approach procedure.
to
bu
y
.d o
.c

Circling Approach
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.60.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
Plan to start a visual approach at 1500 ft AAL, 2.5 nm abeam the upwind
threshold. The flight plan selected on the MCDU should include the selection of
the landing runway such that managed speed is available. The downwind leg
may also be part of the flight plan. This may produce a useful indication on the
ND of the aircraft position in the circuit, but visual references must also be used.

Use the following technique:
lic
6.70.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Visual Approach
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Select ROSE NAV and 10 nm on the EFIS display to assist in positioning

the aircraft accurately.
Activate the APPR phase at the start of the downwind leg.
Ensure A/THR is on and managed speed is engaged.
Select TRK/FPA.
Select Flaps 1 abeam the upwind threshold.
Set the go-around altitude on the FCU.
Fly the downwind leg at 1500 ft AAL at S Speed.
Maintain a track parallel to the landing runway approximately 2.5 nm
abeam.
AP and FD may be used on the downwind leg, but must be selected off
prior to the base turn.
Abeam the landing threshold, select Flaps 2, start the chrono and lower
the gear.
Select Flaps 3 prior to the base turn.
Time for 45 sec +/- 1 sec/kt of wind.
Commence the base turn and select Flaps Full when leaving 1500 ft.
Complete the Landing Checklist.
BASE TURN
In calm winds, only 15 of bank will be required. In strong tightening crosswinds,
up to 30 of bank may be required. Speed, bank angle and rate of descent
should be closely monitored by the PNF. If an ILS is being intercepted from a
visual circuit, a G/S warning is possible during the turn.
Commence the final turn onto the runway centreline at approximately 0.8 nm
before the extended centreline (if displayed on the ND). Initial ROD should be
approximately 400 ft/min, increasing to 700 ft/min when established on the
correct descent path. Establish a normal 3 approach as per the stabilised
approach criteria.
h a n g e Vi
e
FINAL APPROACH
Roll out of the turn on the extended runway centreline and maintain VAPP.
Thrust should be stable by 1000 ft. Use the speed trend arrow to anticipate
thrust changes and the FPV to monitor approach path deviations. Use available
G/S and/or PAPIs as well as the visual picture to assist in maintaining a stable
approach.
A continuous visual/instrument scan is required to fly a successful approach. An
effective scan will assist in highlighting small errors, allowing small, early
corrections to be made.
A 3 slope will normally be flown with a ROD of approximately 700 ft/min; a
higher ROD is an indication that the aircraft is about to descend below the ideal
approach path. A small correction of approx 1 of pitch will change the ROD by
approximately 100 ft/min. Azimuth errors will require bank angle changes both to
stop the drift and then to recover to the centreline. Avoid using bank angles
greater than 10 for small corrections.
to
bu
y
.d o
.c

Visual Approach
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
6.70.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
6.70.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Visual Approach
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
h a n g e Vi
e
7.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
Landing, Go-around & Taxi-in

Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
Landing
Visual Aim Point ............................................................................................7.10.1
Visual Approach Slope Indicator (VASI/T-VASI) ...........................................7.10.1
Precision Approach Path Indicator (PAPI) ....................................................7.10.4
Flare ..............................................................................................................7.10.5
Tailstrike Protection And Prevention .............................................................7.10.7
Derotation......................................................................................................7.10.7
Rollout ...........................................................................................................7.10.7
Braking ..........................................................................................................7.10.8
Factors Affecting Landing Distance.............................................................7.10.10
Crosswind Landing......................................................................................7.10.12
Bounced Landing Recovery ........................................................................7.10.13
Ground Clearance .......................................................................................7.10.13
Adverse Weather.........................................................................................7.10.17
Go-around
Preface ..........................................................................................................7.20.1
AP/FD Go-around Mode Activation ...............................................................7.20.1
Leaving The Go-around Phase .....................................................................7.20.2
Rejected Landing ..........................................................................................7.20.3
Taxi-in
Brake Temperature .......................................................................................7.30.1
Park Brake Use .............................................................................................7.30.1
Adverse Weather...........................................................................................7.30.1
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.10.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
VISUAL AIM POINT

When available, PAPI, VASI or ILS glideslope, provide cues to assist in
maintaining the correct path in the latter stages of the approach. The correct
approach path brings the aircraft to 1000 ft beyond the runway threshold. This is
the visual aim point. Assuming a constant speed and attitude, this point should
not move relative to the windscreen. Make small control inputs as required to
maintain the visual aim point fixed in the windscreen until initiation of the flare.
Close to the ground, high sink rates must be avoided even at the expense of
maintaining glideslope or the visual aim point. Priority should be given to correct
attitude and sink rate. If runway length is limiting, a go-around should be
initiated.
VISUAL APPROACH SLOPE INDICATOR (VASI/T-VASI)

The VASI is a system of lights arranged to provide visual descent guidance
information during the approach. Flying the VASI glideslope to touchdown is the
same as selecting a visual aim point on the runway adjacent to the VASI
installation.
h a n g e Vi
e
VASI Landing Geometry

Three-bar VASI
Three-bar VASI installations provide two visual glide paths. The lower glide path
is provided by the near and middle bars and is normally set at 3 while the upper
glide path, provided by the middle and far bars, is normally 1/4 higher (3.25).
This higher glide path should be used in order to provide sufficient threshold
crossing height.
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.10.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Two-bar VASI
On rare occasions, a two bar VASI system may be encountered. These systems
are not compatible with widebody aircraft and their use is not recommended.
T-VASI
When flying an approach using a T-VASI system, an indication of one light high
will provide additional wheel clearance.
h a n g e Vi
e
PRECISION APPROACH PATH INDICATOR (PAPI)

The PAPI is a system of 4 lights which are normally installed on the left side of
the runway. The principle of operation is similar to the VASI but using a single
row of lights.
When the aircraft is on a normal 3 glide path, the pilot sees two white and two
red lights. The PAPI may be safely used with respect to threshold crossing
height. The standard PAPI installation is arranged such that the approach path
intersects runway at 1300 ft. Do not follow PAPI guidance below 200 ft.
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.10.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
FLARE
The techniques below assume a stabilised approach at VAPP and on the
glidepath. Unless an unexpected or sudden event occurs, e.g. windshear, it is
not appropriate to use sudden or abrupt control inputs during landing. Additional
considerations applicable to landings in crosswind and slippery runway
conditions are described later in this chapter.
Autotrim ceases at 100 ft and the pitch law is modified to the flare mode, as
described in FCTM Ch 2. At this point, a backpressure on the sidestick is
required to maintain a constant flight path.
The flare technique is conventional. Commence a gentle, progressive flare just
after the 40 ft auto-callout. The typical pitch increment in the flare is
approximately 2 - 3, associated with about a 5 kt speed decay in the
manoeuvre. Retard the thrust levers to idle and allow the aircraft to touchdown
without a prolonged float. A prolonged float increases both the landing distance
and the risk of tailstrike. In order to assess the rate of descent in the flare and
the aircraft position relative to the ground, look well down the runway.
At 20 ft the "RETARD" auto-callout occurs. This is a reminder rather than an
order. If thrust is required, e.g. due to sinking windshear, do not retard the thrust
levers immediately. The A/THR will then add thrust during the flare to maintain
target speed.
h a n g e Vi
e
Minimum Visual Ground Segment (Flare Phase)

CAT III
H
0 ft
(q = 84)
[TBD]
15 ft
(q = 29)
(q = 42)
CAT II
50 ft
(q = 21)
(q = 30)
120 m (394
ft)
[TBD]
60 m (197 ft)
[TBD]
Visual
Segment
100 ft
(q = 21)
(q = 30)
38 ft
44 ft
77 ft
127 ft
Obscured
B
56 m (185 ft)
[TBD]
44 m (143 ft)
[47 m (155 ft]
73 m (238 ft)
[78 m (255
ft)]
120 m (394
ft)
[128 m (419
ft)]
Note:
1. Where different, A346 values are shown in [ ].
to
k
.d o
.c
bu
y
m
c u -tr a c k
lic
to
lic
.d o

Landing
REV 1 (6 JUN 05)
A330/A340
FCTM
7.10.6
w
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
TAILSTRIKE PROTECTION AND PREVENTION

Tailstrike can occur on landing due to:
lic
7.10.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
VAPP being decreased below the calculated value

A high flare with engine power at idle
A high sink rate just prior to flare
Attempting to touchdown too smoothly (higher pitch attitude)
A prolonged flare and float
Pitching up following a bounce to avoid a second hard touchdown
On A333 and A343 aircraft, the PNF should call PITCH if pitch attitude exceeds
7.5 in the flare.
The A346 tailstrike protection system provides pitch limit indication on the PFD
below 400 ft RA on approach and an aural alert of PITCH, PITCH below 14 ft
RA in case of excessive pitch attitude in the flare. In the event of a tailstrike, an
ECAM TAILSTRIKE caution is generated. FCOM 1.27 refers.
DEROTATION
On landing, the rear main wheels touchdown first. The aft sidestick input applied
for the flare should then be relaxed towards the neutral position. This allows the
aircraft to derotate naturally until front main gear contact. After main gear
touchdown, fly the nose down conventionally, controlling the derotation rate to
ensure a smooth nosewheel touchdown. Lower the nosewheel without delay. Do
not keep the nose high in order to increase aircraft drag during the initial part of
the rollout. This technique is inefficient as it reduces braking efficiency by
delaying full weight-on wheels, increases the risk of a hard nosewheel
touchdown and also increases the risk of tailstrike. If braking is applied with the
nose high, up to full back stick may be required to control the nose down pitching
moment.
After touchdown, with reverse thrust selected on at least one engine and one
main landing gear strut compressed, the ground spoilers partially extend to
further establish ground contact. The ground spoilers fully extend when both
main landing gears are compressed. A small nose down input on the elevators is
introduced by the control law, which compensates the pitch up tendency with
ground spoiler extension.
ROLLOUT
During the rollout, use the rudder pedals to maintain the aircraft on the runway
centreline. At high speed, directional control is achieved with rudder. As the
speed reduces, nosewheel steering becomes active. The steering handwheel is
not to be used until taxi speed is reached.
h a n g e Vi
e
BRAKING
The importance of the timely use of all means of stopping the aircraft cannot be
overemphasised. Execution of the following actions without delay permits
stopping the aircraft with the least landing roll. Three systems are involved in the
aircraft deceleration:
Ground spoilers
Thrust reversers
Wheel brakes
Ground Spoilers
The ground spoilers contribute to aircraft deceleration by increasing
aerodynamic drag and so are more effective at high speed. Ground spoiler
extension also markedly decreases lift. This increases load on the wheels and
therefore improves braking efficiency. Additionally, the ground spoiler extension
signal is used for autobrake activation.
Thrust Reversers
Select reverse thrust immediately after main gear touchdown. Thrust reverser
efficiency is proportional to the square of the speed and is therefore most
efficient at high speeds. Below 70 kt, reverser efficiency decreases rapidly.
Below 60 kt with maximum reverse selected, there is a risk of engine stall.
Smoothly reduce the reverse thrust to idle at 70 kt. However, in case of
emergency, maximum reverse thrust is permitted down to aircraft stop.
Normally full reverse thrust should be used. However, on long, dry runways with
no tailwind component, idle reverse may be used. Stow the reversers when taxi
speed is reached and before leaving the runway.
If airport regulations restrict the use of reverse thrust, select and maintain
reverse idle until taxi speed is reached.
Wheel Brakes
Wheel brakes contribute the most to aircraft deceleration on the ground. Many
factors may affect braking efficiency, e.g. load on the wheels, tyre pressure,
runway pavement characteristics, runway contamination and braking technique.
The only factor over which the pilot has any control is the use of the correct
braking technique.
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.10.9
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Antiskid
The antiskid system adapts pilot applied brake pressure to runway conditions by
sensing an impending skid condition and adjusting the brake pressure to each
individual wheel as required. The antiskid system maintains the skidding factor
(slip ratio) close to the maximum friction force point. This provides the optimum
deceleration with respect to the pilot input. When braking manually, antiskid
performance is optimised by smoothly applying and maintaining the desired
braking command.
Use Of Autobrake
Manual braking often involves a delay between main gear touchdown and brake
application, even when actual conditions dictate the need for a more rapid
initiation of braking. This delay in brake application adversely affects the landing
distance. Brake application may be further delayed by the increased workload
associated with a crosswind, LWMO, or operations on short, wet, or
contaminated runways. The use of autobrake is therefore recommended in
preference to manual braking.
The use of LO (A346: LO, 2, 3) should be preferred on long dry runways
whereas the use of MED (A346: 4, HI) should be preferred on short or
contaminated runways. The use of MAX autobrake on A333/A343 is not
recommended for landing.
On very short runways, the use of manual braking may be envisaged since the
pilot may apply full manual braking without delay after main gear touchdown.
However this should not preclude arming of the autobrake for landing.
As the autobrake system maintains a pre-determined deceleration rate, reverse
thrust reduces the amount of wheel braking required. This results in reduced
brake temperatures.
Brake wear is related to the number of brake applications. The use of autobrake
minimises the number of brake applications and consequently brake wear.
The green DECEL light on the AUTO/BRK panel enables the monitoring of the
deceleration rate. It illuminates when approximately 80% of the selected
deceleration rate is achieved. In some cases it may illuminate without application
of brakes, e.g. if the effect of reverse thrust is sufficient to achieve the
deceleration rate. In other cases, e.g. on contaminated runways, it many not
illuminate because antiskid is unable to achieve the deceleration rate despite
proper operation of the autobrake. (A346: The ACTIV light illuminates to indicate
that the autobrake is functioning but has yet to achieve the desired deceleration.)
h a n g e Vi
e
Autobrake may be disengaged by brake pedal application or by (A333/A343:

deselecting the AUTO/BRK pb) (A346: rotating the selector to DISARM). The
normal method of disarming the autobrake is by applying even pressure on both
brake pedals. Disconnect the autobrake when the desired speed is attained and
in any case above 20 kt to avoid brake shudder at low speed. Failure to
disconnect will result in the aircraft stopping on the runway.
The use of autobrake does not absolve the pilot of the responsibility of achieving
a safe stop within the available runway length.
Manual Braking
Normally delay manual braking until after nosewheel touchdown to vacate the
runway at the appropriate turn-off. To reduce brake wear, the number of brake
applications should be limited.
Manual braking may be applied prior to nosewheel touchdown e.g. on a limiting
runway. Anticipate an increased nose down pitch rate. Apply brakes smoothly
and symmetrically with moderate-to-firm pedal pressure until a safe stop is
assured. Do not ride the brakes but apply manual braking when required and
modulate the pressure without releasing to minimise brake wear.
Deceleration Monitoring
The PNF monitors and calls:
Spoiler deployment (ECAM WHEEL page).

Reverse thrust operation(E/WD).
Autobrake operation (green DECEL light on AUTO/BRK panel).
He should advise the PF of any non-normal indications.
FACTORS AFFECTING LANDING DISTANCE

The field length requirements are contained in the Landing Performance section
of FCOM 2. The landing distance margin is reduced if the correct landing
technique is not used. Factors that affect stopping distance include:
Height and speed over the threshold

Glideslope angle
Landing flare technique
Delay in lowering the nose onto the runway
Improper use of available deceleration devices
Runway conditions (discussed in adverse weather)
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.10.11
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Height of the aircraft over the runway threshold has a significant effect on total
landing distance. For example, on a 3 glide path, passing over the runway
threshold at 100 ft rather than 50 ft could increase the total landing distance by
approximately 300 m/950 ft. This is due to the length of runway used before the
aircraft touches down.
A 5 kt speed increment on VAPP will result in a 5% increase to the distance
extracted from the Landing Distance with Autobrake table in the QRH.
A prolonged period of level flight above the runway prior to touchdown must be
avoided as it uses a significant amount of the runway length available. Land the
aircraft as near to the normal touchdown point as possible. Deceleration on the
runway is approximately three times greater than in the air.
The minimum stopping distance is achieved by applying maximum manual
antiskid braking with maximum reverse thrust selected and ground spoilers fully
deployed.
h a n g e Vi
e
CROSSWIND LANDING
A maximum crosswind for landing is specified in FCOM 3.01.20. The figures are
equally applicable to dry or wet runways. The maximum crosswind values for
automatic landings are autoland system limitations. FCOM 3.01.22 refers.
The recommended technique to fly an approach in a crosswind is to track the
runway centreline with drift applied and wings level. This is called the crabbed
approach.
During the flare, apply rudder to align the aircraft with the runway centreline.
Counteract any tendency to roll downwind by an appropriate sidestick input. It is
possible that a very small amount of into-wind sidestick may be required to
maintain the aircraft on the runway centreline prior to touchdown.
In the case of a very strong crosswind, a full de-crab prior to the flare may lead
to the development of a significant downwind drift. The amount of bank required
to arrest this drift may reach the aircraft lateral geometry limit. In this case, the
combination of a partial de-crab and wing down technique may be required.
The crabbed approach prior to landing has several advantages:
Both main gear struts are compressed simultaneously resulting in full

spoiler extension
If touchdown occurs with drift, the load is more evenly spread across all
main gear
The risk of an engine pod strike is reduced
Rollout
Minimise into wind sidestick input as this would increase the weathercock effect
and create a disproportionate down force on the upwind main gear.
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.12
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
BOUNCED LANDING RECOVERY

A bounced landing may be caused by either one, or a combination, of the
following:
Pitch rate not stopped after touchdown

Backpressure on the sidestick not released after touchdown
Pitch up effect of spoiler extension not controlled
Automatic spoiler deployment inhibited due to thrust levers higher than idle
Should a shallow bounce occur, hold the pitch attitude. Do not attempt to soften
the second touchdown by either increasing pitch or adding thrust.
Should a significant bounce occur, do not attempt to continue the landing but
hold the pitch attitude and go-around. Do not try and avoid a second touchdown
during the go-around by increasing pitch attitude. Should a second touchdown
occur, the go-around must be continued. Delay flap retraction until the normal
go-around procedure is established with a positive climb confirmed. Due to the
possibility of on-ground sensing, with TOGA thrust applied and full flap extended,
a CONFIG warning may occur.
GROUND CLEARANCE
The most common causes for the aircraft structure making ground contact on
landing are:
lic
7.10.13
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Unstable approach
Inappropriate flare and landing technique
Windshear
The landing technique described above minimises the risk of ground contact.
Ground contact occurs if the figures shown in the following charts are exceeded
at touchdown:
h a n g e Vi
e
N
k
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.14
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.10.15
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.16
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
ADVERSE WEATHER
Operations on slippery or contaminated runways have a significant impact on
landing considerations, including:
lic
7.10.17
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Braking action
Directional control
Crosswind limit determination
Braking Action
The presence of fluid contaminant on the runway adversely affects the braking
performance by reducing the friction force between the tyres and the runway
surface. It also creates a fluid layer between the tyres and the runway surface
thus reducing the contact area. The landing distances provided in FCOM 2.03.10
give an indication of the actual landing distances for various levels of
contamination.
The use of LO or MED (A346: LO/2 or 3/4) autobrake is recommended when
landing on an evenly contaminated runway. The DECEL light on the AUTO BRK
panel may not illuminate, as the pre-determined deceleration might not be
achieved. This does not mean that the autobrake is not working.
Make a positive touchdown and select maximum reverse as soon as possible
thereafter.
h a n g e Vi
e
Slippery Or Contaminated Runway Landing Performance

When landing on runways contaminated with ice, snow, slush or standing water,
the reported braking action must be considered. Terms used include GOOD,
FAIR, POOR and NIL. Vol 2 Pt 2 refers.
The braking performance associated with "GOOD" is representative of a wet
runway, while "POOR" is representative of an ice covered runway. Exercise
extreme caution to ensure adequate runway length is available when POOR
braking action is reported.
Contaminated runway landing performance data is presented in FCOM 2.03.10.
Uniform contamination over the entire runway is assumed. This means a uniform
depth for slush/standing water for a contaminated runway or a fixed braking
coefficient for a slippery runway. The data cannot cover all possible
slippery/contaminated runway combinations and does not consider factors such
as rubber deposits or heavily painted surfaces near the end of most runways.
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.18
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
A term commonly used to describe runway conditions is coefficient of friction.

The runway coefficient of friction is normally determined using vehicles towing
measuring equipment. For a variety of reasons, the coefficient measured by the
ground equipment may not necessarily relate to the coefficient that the aircraft
may experience on landing. Coefficient of friction values provide additional
information to be taken into consideration when determining the runway
conditions for landing. Evaluate these readings in conjunction with pilot reports
and the physical description of the runway condition when planning the landing.
Take special care in evaluating all the information available when braking action
is reported as POOR or if slush or standing water is present on the runway.
Unless emergency or operational circumstances dictate otherwise, use the
following minimum friction co-efficient for landing:
lic
7.10.19
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
0.2 FC (ICAO)
0.26 CRFI (Canada)
20 ACBA (USA)
Directional Control
As for a normal landing, use rudder for directional control after touchdown. Use
of the steering handwheel must be avoided above taxi speed as its use may
result in aquaplaning of the nosewheel, leading to reduced cornering force and
consequently, reduced directional control.
A crosswind landing on a contaminated runway requires careful consideration. If
the aircraft touches down with some crab or is allowed to weathercock into wind
after landing, the reverse thrust side force component and the crosswind
component can combine to cause the aircraft to drift to the downwind side of the
runway. Additionally, as the antiskid system will be operating at maximum
braking effectiveness, the main gear tyre cornering forces available to counteract
this drift will be reduced.
To correct back to the centreline, reduce reverse thrust to reverse idle and
release the brakes. This minimises the reverse thrust side force component,
without the requirement to go through a full reverser actuating cycle again and
increases the tyre cornering force available. Rudder and differential braking
should be used to correct back to the runway centreline, if required. When
re-established on the runway centreline, re-apply braking and reverse thrust as
required.
On wet and contaminated runways, directional control is most problematic at low
speed. Differential braking may be used as necessary in conjunction with brake
pedal deflection. If differential braking is used, the pilot should fully release the
brake pedal input on the opposite side to the intended turn direction.
h a n g e Vi
e
Crosswind Limitations
Due to the potential directional control problems associated with landing on
contaminated runways in crosswind conditions, the crosswind limitations are
reduced. FCOM 2.04.10 and the QRH refer.
Autolands
The automatic ROLLOUT mode, has not been demonstrated on snow covered
or icy runways. The ROLLOUT mode relies on a combination of aerodynamic
rudder control and nosewheel steering to maintain the runway centreline using
localizer signals for guidance. On a contaminated runway, nosewheel steering
effectiveness and therefore aircraft directional control capability, is reduced. Use
the more restrictive of the autoland or contaminated runway landing crosswind
limitations to determine the maximum permitted crosswind.
If an autoland is accomplished on a contaminated runway, be prepared to
disengage the AP should ROLLOUT directional control become inadequate.
Landing Technique Summary

The following chart summarises the recommended procedures for landing on
slippery or contaminated runways:
to
bu
y
.d o
.c

Landing
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.10.20
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
PHASE
Approach
Flare
Touchdown
RECOMMENDED
PROCEDURE
to
.d o
lic
7.10.21
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Landing
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
REMARKS
Fly a well-executed
final approach with
the aircraft positioned
on
glidepath,
on
runway centreline and
at
the
speed
recommended
for
existing conditions.
Go-around if approach
stability criteria not met.
Arm
autobrake
system by selecting
LO or MED (A346:
LO/2 or 3/4)
Autobrake
is
recommended provided
contamination is evenly
distributed.
With a crosswind, do
not be misled by the
relative bearing of the
runway due to crab
angle when breaking
out of overcast.
Do not float or allow

drift to build up during
the flare.
Drifting snow can lead

to an illusion of
aircraft drift.
With a crosswind, do
not de-crab prior to
touchdown.
Accomplish a positive
touchdown as near to
the
centreline
as
possible
at
approximately 1,500
500 ft.
The aircraft should be

flown positively onto
the runway even if the
speed is excessive.
If a long touchdown is
likely, go-around.
Use runway lighting and

markings
as
drift
reference
in
drifting
snow.
A touchdown in a crab
establishes main gear
crab effect and actuates
the auto spoilers and the
autobrakes more quickly.
A positive touchdown
improves wheel spin up
on slippery runways.
Deceleration
on
the
runway is about three
times greater than in the
air. Do not allow the
aircraft to float.
.c
h a n g e Vi
e
PHASE
Deceleration
Phase (Expedite
All Items)
Rollout
RECOMMENDED
PROCEDURE
REMARKS
Select
maximum
reverse thrust.
Immediately
nose gear
runway and
forward
pressure.
Check
the
speedbrakes deploy
immediately
after
main gear touchdown.
The autobrake system

begins
symmetrical
braking at ground
spoiler deployment.
Without
autobrake,
use moderate-to-firm,
steady brake pedal
pressure after nose
gear touchdown.
Do not cycle brake

pedals. Both main gear
bogies must be in GND
POS
for
antiskid
operation. Antiskid is
deactivated below 10 kt
ground speed.
Keep the wings level.
Improves
directional
control and traction.
lower the
onto the
hold light
sidestick
Maintain light forward

sidestick pressure.
Use
nosewheel
steering with care.
Maintain
directional
control with rudder for
as long as possible.
to
k
.d o
.c
bu
y
m
c u -tr a c k
lic
to
lic
.d o

Landing
REV 1 (6 JUN 05)
A330/A340
FCTM
7.10.22
w
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
Failure to execute a go-around, when required, is a major cause of approach
and landing accidents. As a go-around is an infrequent occurrence, it is
important to be "go-around minded". The decision to go-around should not be
delayed, as an early go-around is safer than one carried out at the last minute at
low altitude.
AP/FD GO-AROUND MODE ACTIVATION

The go-around phase is activated when the thrust levers are set to TOGA,
provided the flap lever is at Flap 1 or greater. The FDs are displayed
automatically.
The SRS provides guidance to either the speed at go-around engagement or
VAPP, whichever is higher, until the acceleration altitude. The speed is further
limited to maximum of VLS + 25 with all engines operative or VLS + 15 with one
engine inoperative. If the go-around is manually flown, the initial pitch targets are
15 with all engines operative and 12.5 with one engine inoperative. If FPV/FPD
has been used for the approach, it may be necessary to press the HDG V/S-TRK
FPA pushbutton to restore pitch and roll bars.
To initiate the go-around, the PF simultaneously applies TOGA thrust,
announces the go-around, calls for the required flap setting and rotates to the
required pitch attitude. Before moving the flaps, the PNF should check that the
speed is greater than VLS and not reducing. For normal operations, the required
flap setting is one step less than the approach configuration, e.g. Flap 3 following
a Flap Full approach. If the go-around is carried out early in the approach with
Flap 1 selected, do not retract flap until above S speed. PF then checks for
correct FD presentation and once a positive ROC is confirmed requests landing
gear retraction. Before making the requested configuration change, the PNF
checks the required parameters and repeats the PF command. The PNF
confirms that the correct thrust is set and then the PF reads the FMA and
requests the required lateral modes (NAV or HDG). If the AP is engaged the PF
can make the lateral mode selection.
Above the acceleration altitude, the target speed becomes green dot.
lic
7.20.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Go-around
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
GA TRK guides the aircraft on the track memorised at the time of TOGA
selection. The missed approach route becomes the ACTIVE F-PLN provided the
waypoints have been correctly sequenced on the approach. The previously flown
approach is placed back into the F-PLN. If a second approach is required, it
becomes available when the approach phase is re-activated. Pushing for NAV
enables the missed approach F-PLN to be followed. If both APs had been
engaged prior to the selection of TOGA, the go-around will be flown with both
APs remaining engaged. Whenever any other mode engages, AP 2 disengages.
The FMGS makes no predictions in the go-around phase. Consequently CLB
mode is not available and the pilot must observe constraints.
Subsequent procedures, including thrust handling and flap retraction, are in
accordance with the take-off phase. FCTM Ch 4 refers. Thrust reduction and
acceleration will be sequenced at the altitudes programmed in the PERF GA
page.
A late go-around may result in ground contact. If touch down occurs after TOGA
is engaged, the AP will remain engaged and the A/THR remains in TOGA. The
ground spoilers and autobrake are inhibited.
Go-Around From An Intermediate Approach Altitude

To interrupt an approach, or perform a go-around from an intermediate altitude in
the approach where TOGA thrust is not required, set the thrust levers to the
TOGA detent and then retard them as required, normally back to the CL detent.
Provided the flap lever is at Flap 1 or greater, the go-around mode will activate
with the associated AP/FD modes. If the thrust levers are not briefly set to the
TOGA detent, the FMGS will not engage the go-around phase, and flying within
7 nm of the airport will sequence the destination waypoint. In this case, the
active F-PLN will be erased and only PPOS - F-PLN DISCONTINUITY will be
displayed.
If necessary, select the applicable AP/FD and A/THR modes on the FCU to
manage the subsequent flight profile.
LEAVING THE GO-AROUND PHASE

During the missed approach, choose either of the following strategies:
Fly a second approach

Carry out a diversion
The chosen strategy will depend upon the reason for the go-around, e.g. poor
weather. The purpose of leaving the go-around phase is to obtain the proper
target speed and predictions for the chosen strategy.
to
bu
y
.d o
.c

Go-around
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
7.20.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.20.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Go-around
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Second Approach
If a second approach is to be flown, activate the approach phase via the PERF
GO-AROUND page. The target speed moves according to the flaps lever setting,
e.g. Green Dot for Flaps 0.
Ensure correct waypoint sequencing during the second approach in order to
have the missed approach route available, should a further go-around be
required.
Diversion
Once the aircraft path is established and clearance has been obtained, modify
the FMGS as required.
If the ALTN F-PLN is in the active F-PLN perform a lateral revision, preferably at
the TO WPT, to access the ENABLE ALTN prompt. On selecting the ENABLE
ALTN prompt, the lateral mode reverts to HDG if previously in NAV. Fly the
aircraft towards the next waypoint using HDG or perform a DIR TO to engage
NAV.
If the ALTN F-PLN is in the SEC F-PLN, activate the SEC F-PLN and perform a
DIR TO as required. The ACTIVATE SEC F-PLN prompt will only be displayed in
HDG mode.
If the ALTN F-PLN is not stored, make a lateral revision at any waypoint to insert
a NEW DEST. Amend the route and CRZ FL as required.
REJECTED LANDING
A rejected landing is defined as a go-around manoeuvre initiated after
touchdown of the main landing gear.
Once the decision is made to reject the landing, commit to the go-around
manoeuvre and do not be tempted to retard the thrust levers in a late decision to
execute a landing.
Apply TOGA thrust. Ground spoilers will auto-retract and autobrake will disarm
as a consequence. A CONFIG warning will be generated when the aircraft is still
on the runway, with thrust applied and the flaps at FULL. Disregard this warning.
If the AP was engaged, it will disconnect. If on the ground, continue de-rotation.
Rotate only when the PNF has confirmed the thrust is set and the speed is
above VAPP. When clear of the ground, with a positive ROC, select Flaps 3 if
approach was made with Flaps FULL. The landing gear should be retracted
when a positive ROC has been established with no risk of further touchdown.
Thereafter proceed as for a standard go-around.
If reverse thrust has been applied, a full stop landing is mandatory.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
7.30.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o

Taxi-in
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
BRAKE TEMPERATURE
Thermal oxidation is accelerated at high temperature. Therefore, if the brakes
absorb too much heat, carbon oxidation will be increased. This is the reason why
the brakes should not be repeatedly cycled above 500C during normal
operation. Furthermore, after heavy braking, the use of brake cooling fans could
increase oxidation of the brake surface hot spots if the brakes are not thermally
equalised. Thermal equalisation is achieved about 5 minutes after the high
energy absorption event.
PARK BRAKE USE

When parked during normal operations, the Park Brake should be left ON.
Releasing the Park Brake does not have a significant effect on brake cooling.
The very small air gap created between the discs hinders the transfer of heat
energy through the brake unit. Leaving the Park Brake on allows the heat to be
dissipated through the entire mass of the wheel assembly. This is not the case if
brake cooling is used. The Park Brake should be released as this will enable
cooling air to be forced through the gap between the discs and across the brake
surface.
Unless operationally required, park brake use should be avoided if any brake
temperature exceeds 500C. In this case, brake cooling should be applied.
Any decision to release the Park Brake must be done in consultation with the
ground engineer and only after confirmation that the wheel chocks are in place.
ADVERSE WEATHER
The techniques outlined in FCTM Ch 3 concerning operations on contaminated
taxiways are applicable. Additionally, the flaps/slats should not be retracted after
landing to avoid damage that might be caused by crushing any ice present in the
flap/slat tracks. On arrival at the gate a visual inspection should be carried out,
after engine shutdown, to ensure that the flap/slat areas are free of any
contamination prior to retraction.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
h a n g e Vi
e
8.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
Non-normal Operations
Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
General
Preface ..........................................................................................................8.10.1
Use Of Autopilot ............................................................................................8.10.1
Monitoring And Cross-Checking....................................................................8.10.1
Memory Items................................................................................................8.10.1
Landing Distance Procedure .........................................................................8.10.2
Vapp Determination.......................................................................................8.10.2
Landing Distance Calculations ......................................................................8.10.4
Land ASAP....................................................................................................8.10.4
Operating Techniques
Low Speed Engine Failure ............................................................................8.20.1
Rejected Take-off ..........................................................................................8.20.1
Engine Failure After V1 .................................................................................8.20.6
Engine Failure During Initial Climb-Out .........................................................8.20.9
Engine Failure During Cruise ........................................................................8.20.9
One Engine Inoperative Landing.................................................................8.20.11
Circling One Engine Inoperative..................................................................8.20.11
One Engine Inoperative Go-Around ............................................................8.20.12
Two Engines Inoperative Landing (A343/A346)..........................................8.20.12
Recovery From Alpha Protection And Alpha Floor......................................8.20.14
Stall Recovery .............................................................................................8.20.15
Recovery From High Speed Protection.......................................................8.20.15
Electrical
Emergency Electrical Configuration ..............................................................8.30.1
h a n g e Vi
e
Fire Protection
Fire Protection ...............................................................................................8.40.1
Smoke ...........................................................................................................8.40.1
Cargo Smoke ................................................................................................8.40.2
Flight Controls
Non-Normal Flaps/Slats Configuration..........................................................8.50.1
Elevator Redundancy Lost ............................................................................8.50.3
Fuel
Fuel Leak.......................................................................................................8.60.1
Fuel Jettison ..................................................................................................8.60.1
Handling Of Expected Low Fuel Levels At Destination .................................8.60.2
Avoidance Of Non-standard Fuel Distributions On Arrival ............................8.60.2
Avoidance Of Fuel Induced Wing Icing On Arrival ........................................8.60.2
Hydraulic
Double Hydraulic Failures .............................................................................8.70.1
Landing Gear
Landing With Non-normal Gear.....................................................................8.80.1
Navigation
FMGC Failure................................................................................................8.90.1
IRS/ADR Failures ..........................................................................................8.90.1
Dual Radio Altimeter Failure .........................................................................8.90.2
Power Plant
All Engine Flameout ....................................................................................8.100.1
Tail Pipe Fire ...............................................................................................8.100.2
Miscellaneous
Overweight Landing ....................................................................................8.110.1
Emergency Descent ....................................................................................8.110.2
Unreliable Airspeed Indications...................................................................8.110.2
to
bu
y
.d o
.c
Table Of Contents
c u -tr a c k
A330/A340
FCTM
REV 2 (25 JUL 06)

.d o
lic
lic
8.00.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
This chapter highlights techniques to be used in some non-normal operations.
Some of the procedures discussed in this chapter are the result of double or
triple failures. Whilst it is very unlikely that any of these failures will be
encountered, it is useful to have a background understanding of the effect that
they have on the handling and management of the aircraft. In all cases, handle
the ECAM as described in FCTM Ch 2.
USE OF AUTOPILOT
The use of the autopilot is strongly recommended:
In the case of engine failure, without any restriction including autoland or

Cat 2/3 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 AP is used in such circumstances, remain vigilant and
be prepared to disconnect the AP if the aircraft deviates from the desired
or safe flight path.
MONITORING AND CROSS-CHECKING

Monitoring and cross-checking are essential components of effective procedures
and remain primary tasks for all crew members. The PF shall monitor all
ECAM/checklist actions.
MEMORY ITEMS
The following procedures are to be applied from memory:
lic
8.10.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
WINDSHEAR
WINDSHEAR AHEAD
TCAS
EGPWS
LOSS OF BRAKING
EMER DESCENT (inital actions)
UNRELIABLE AIRSPEED INDICATIONS (initial actions)
On completion of the memory items and when the aircraft is stabilised on the
correct flight path, the PNF shall ensure that all the required memory actions
have been carried out by reference to ECAM or checklist, and then complete the
remainder of the procedure.
h a n g e Vi
e
LANDING DISTANCE PROCEDURE

Should a failure occur with a LDG DIST PROC APPLY action displayed on the
ECAM STATUS page, the pilot should enter the LDG CONF/APP SPD/LDG
DIST/CORRECTIONS FOLLOWING FAILURES table in QRH Part 2 to
establish:
The flap lever position for landing

DVREF if required for VAPP determination
The landing distance factor for landing distance calculation
VAPP DETERMINATION
Certain failures affect the approach speed:
Some failures (typically slat or flap) increase the VLS. In this case, the
VLS displayed on the PFD takes into account the actual configuration.
VLS on the PERF APPR page is not modified.
For some other failures, there is a requirement to fly at speed higher than
VLS to improve the handling characteristics of the aircraft. In this case,
ECAM provides a speed increment, called DVLS, which is displayed on the
STATUS page. This speed increment is to be added to the VLS displayed
on the PFD when the landing configuration is reached.
In all cases,
In order to prepare the approach and landing, the pilot needs to know VAPP in
advance. The appropriate VLS is not necessarily available at that time on the
PFD, because the landing configuration has not yet been established. Therefore,
VAPP is determined using VREF, which is the VLS of CONF FULL, and is
available both on MCDU PERF APPR page and in the QRH. DVREF, if required,
is then extracted from the QRH and added.
to
bu
y
.d o
.c
General
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.10.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
8.10.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
General
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Notes:
1.
When computing VAPP, wind correction is normally 1/3 of the tower
headwind component. If DVREF/DVLS < 20 kt, then DVREF/DVLS + wind
correction should not exceed 20 kt. No wind correction should be applied if
DVREF/DVLS 20 kt.
2.
Ensure CONF FULL is selected for the landing configuration when using
VLS on the PERF APPR page to determine VREF. If CONF 3 is required
for landing, it may then be selected on the MCDU.
DREF IN QRH VERSUS DVLS ON PFD
If the QRH requires a DVREF, determine VAPP as described above and insert it
on the PERF APPR page. When fully configured for landing, check the
reasonableness of the pilot computed final approach speed against the VLS on
the PFD.
If the QRH does not require a DVREF, then proceed as for normal operations
using the VAPP on the PERF APPR page as computed by the FMGC.
h a n g e Vi
e
LANDING DISTANCE CALCULATIONS

The actual landing distance is measured from 50 ft above the runway surface
until the aircraft comes to a complete stop. This distance is measured during
flight testing and represents the maximum aircraft performance. It is called
LANDING DISTANCE WITHOUT AUTOBRAKE in the QRH. These distances
are calculated at VLS. The tables provide corrections for VAPP or other speed
increments above VLS.
Should a failure occur in flight, which requires the actual landing distance to be
multiplied by a factor, then apply the factor to the LANDING DISTANCE
WITHOUT AUTOBRAKE CONFIGURATION FULL figure.
Conversely, the AUTOLAND LANDING DISTANCE WITH AUTOBRAKE table
available in the QRH gives a realistic indication of the aircraft performance
during normal operations. Therefore, refer to this table if an enroute diversion is
required and no landing distance factor is to be applied.
LAND ASAP
In a non-normal situation the Captain, being responsible for the operation and
the safety of the flight, must make the decision to continue the flight as planned
or divert. In all cases, the Captain is expected to take the safest course of action.
The ECAM assists the crew in making this decision by indicating LAND ASAP
either in amber or red:
If a non-normal procedure causes a LAND ASAP to appear in amber on

the ECAM, the crew should consider the seriousness of the situation and
the selection of a suitable airport.
If an emergency procedure causes LAND ASAP to appear in red on the
ECAM, the crew should land at the nearest suitable airport.
Following the failure of an engine on a twin-engined aircraft, an emergency

situation exists and the Captain shall land at the nearest suitable airfield. The
relative suitability of airports is at the Captains discretion based on a number of
factors including, but not limited to, weather, navigation aids, runway length and
fire and rescue support facilities. The Captain may determine that, based on the
nature of the situation and an examination of the relevant factors, it is preferable
not to divert to the nearest airport but to continue to a more suitable airport at a
greater distance.
For a fire that cannot be confirmed as extinguished, or persistent smoke, the
safest course of action is to descend and carry out an Emergency Landing with
consideration being given to a possible passenger evacuation.
In the case of a LAND ASAP in red, consider an Overweight Landing rather than
delaying to jettison fuel.
to
bu
y
.d o
.c
General
c u -tr a c k
A330/A340
FCTM
REV 2 (25 JUL 06)

.d o
lic
lic
8.10.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
LOW SPEED ENGINE FAILURE

If an engine failure occurs at low speed, the resultant yaw may be significant,
leading to rapid displacement from the runway centreline. For this reason, it is
essential that the Captain keep his hand on the thrust levers once take-off thrust
has been set. Directional control is achieved by immediately closing the thrust
levers and using maximum rudder and braking, as required. If necessary, use
the steering handwheel to prevent runway departure.
REJECTED TAKE-OFF
Experience has shown that a rejected take-off can be hazardous, even if correct
procedures are followed. Some factors that can detract from a successful
rejected take-off are:
lic
8.20.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Tyre damage
Worn or defective brakes
Error in gross weight determination
Incorrect performance calculations
Incorrect runway line-up technique
Initial brake temperature
Delay in initiating the stopping procedure
Runway friction coefficient lower than expected
Thorough pre-flight preparation and a conscientious exterior inspection can

eliminate the effect of some of these factors.
During taxi-out, review the take-off briefing. During this briefing, confirm that the
computed take-off data reflects the actual take-off wind and runway conditions.
Any changes to the planned conditions require re-calculation of the take-off data.
In this case, do not be pressured into accepting a take-off clearance before
being fully ready. Similarly, do not accept an intersection departure until the
take-off performance has been re-calculated and checked.
The line-up technique is very important. Use the recommended technique to
minimise field length loss and consequently, to maximise the accelerate-stop
distance available. FCTM Ch 3 refers.
A rejected take-off is a potentially hazardous manoeuvre and the time for
decision making is limited. To minimise the risk of inappropriate decisions to
reject a take-off, many ECAM warnings and cautions are inhibited between 80 kt
and 1,500 ft. Therefore, any warnings received during this period must be
considered as significant.
h a n g e Vi
e
To assist in the decision making process, the take-off is divided into low and high
speed regimes, with 100 kt being chosen as the dividing line. The speed of 100
kt is not critical, but was chosen in order to help the Captain make the decision
and to avoid unnecessary stops from high speed. Below 100 kt, the Captain
should seriously consider discontinuing the take-off if any ECAM warning is
activated. Above 100 kt and approaching V1, the Captain should be go-minded
and only reject the take-off in the event of a major failure such as a fire warning
or severe damage, sudden loss of thrust, any indication that the aircraft will not
fly safely, or if an ECAM warning occurs. Examples of ECAM warnings that may
occur are ENG or APU FIRE, ENG FAIL, CONFIG, SIDESTICK FAULT,
REVERSER UNLOCKED, and L+R ELEV FAULT If a tyre fails within 20 kt of
V1, unless debris from the tyre has caused noticeable engine parameter
fluctuations, it is advisable to get airborne, reduce the fuel load and land with a
full runway length available.
V1 is the maximum speed during the take-off roll at which the pilot must take the
first action to stop the aircraft within the accelerate-stop distance. For
certification purposes, an engine failure recognition time of 1 second is allowed
between the engine failure and V1. Additionally a distance margin, equivalent to
2 seconds at a constant speed equal to V1, is added to the accelerate-stop
distance. This increases the safety margin.
V1 is also the minimum speed in the take-off roll, following a failure of the critical
engine at V1, at which the pilot can continue the take-off and achieve the
required height above the take-off surface within the take-off distance. The RTO
Operational Margins diagrams below, give an indication of the consequences of
rejecting the take-off after V1 and/or using improper procedures.
The decision to reject the take-off is the responsibility of the Captain and must be
made prior to V1. If a malfunction occurs before V1, for which the Captain does
not intend to reject the take-off, he announces his intention by calling "GO". If the
Captain decides to reject the take-off, he calls "STOP". This call both confirms
the decision to reject the take-off and also indicates that the Captain now has
control. This is the only time that hand-over of control is not accompanied by the
phrase "I have control".
to
bu
y
.d o
.c
c u -tr a c k
A330/A340
FCTM
REV 2 (25 JUL 06)

.d o
lic
lic
8.20.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
During the rejected take-off, the First Officer monitors and calls "Spoilers, Rev
Green, Decel" as appropriate and "70 kt" during deceleration. It is important to
remember the following:
If the take-off is rejected prior to 72 kt, the spoilers will not deploy and the
autobrake will not be activated.
If the autobrake response does not seem appropriate for the runway
condition, apply and maintain full manual braking.
If the autobrake is unserviceable, the Captain should simultaneously apply
maximum pressure on both pedals as the thrust levers are set to idle. The
aircraft will stop in the minimum distance only if the brake pedals are kept
fully depressed until the aircraft comes to a stop.
If normal braking is inoperative, immediately select the A/SKID & N/W
STRG (A346: A/SKID) switch to OFF and modulate brake pressure as
required below 1000 psi.
Full reverse may be used until complete stop. However if there is sufficient
runway available for the deceleration, reduce reverse thrust preferably
when passing 70 kt.
Do not attempt to clear the runway until it is absolutely clear that an
evacuation is not necessary and that it is safe to do so. If the aircraft
comes to a complete stop using autobrake, release the autobrake prior to
taxi by disarming the spoilers.
The Captain brings the aircraft to a complete stop, sets the parking brake and
advises the cabin crew to "REMAIN SEATED" prior to commencing ECAM
actions. If the take-off has been rejected due to a fire, consider positioning the
aircraft to keep the fire away from the fuselage, taking into account the wind
direction. The First Officer carries out the ECAM actions and the Captain decides
on the next course of action, depending on the circumstances. Give
consideration to:
lic
8.20.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Possible passenger evacuation of the aircraft on the runway

Vacating the runway as soon as possible
Communicating intentions or requests to ATC
If the take-off has been rejected due to an engine fire, ECAM actions should be
completed down to and including discharging the fire agents into the affected
engine. If the fire remains out of control after having discharged the fire agents,
the on ground EMERGENCY EVACUATION paper checklist should be actioned.
On the ground, the right hand dome light automatically illuminates in case of a
rejected take-off whatever the dome switch position allowing the EMERGENCY
EVACUATION checklist to be completed even if normal electrical supply is lost.
If required, the EMERGENCY EVACUATION checklist is on the back page of the
plasticised Normal Checklist. When the aircraft is on battery power alone, the
crew seats can only be operated manually.
h a n g e Vi
e
N
k
to
bu
y
.d o
.c
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.20.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
O
W
N
Case
A
3
3
0
A
3
4
0
to
.d o
k
lic
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
8.20.5
REV 1 (6
JUN 05)
w
w
.d o
A330/A340
FCTM
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Overrun
Speed (kt)
40
30
55
35
Distance
Variation
(ft)
-240
-450
+250
-250
+160
+470
+275
-20
-175
Overrun
Speed (kt)
45
35
50
25
Distance
Variation
(ft)
-470
-600
+400
-320
+230
+480
+190
+100
.c
A successful rejected take-off, at or near V1, is dependent upon the Captain

making a timely decision and using the correct procedures.
h a n g e Vi
e
ENGINE FAILURE AFTER V1

If an engine fails after V1 the take-off must be continued. Stabilise the aircraft at
the correct pitch attitude and airspeed and establish correct tracking prior to the
initiation of the ECAM procedure.
The use of the autopilot is strongly recommended. Following an engine failure,
trim out the rudder forces prior to autopilot engagement. This requires
approximately 20 of rudder trim, which takes approximately 7 sec to apply.
On the ground, use the rudder conventionally to maintain the aircraft on the
runway centreline. At VR, rotate smoothly using a continuous, yet slightly slower
pitch rate than with all engines operating, to an initial pitch attitude of 12.5. The
combination of high FLEX temperatures and low V speeds requires precise
handling during the rotation and lift-off. The 12.5 pitch target will ensure the
aircraft becomes airborne. Avoid following the SRS immediately after take-off as
it will initially be commanding too high an attitude. Once the FD pitch bar comes
down towards the aircraft symbol, follow the SRS order. This may demand a
lower pitch attitude to acquire or maintain V2. When safely airborne with a
positive ROC and RA increasing, retract the landing gear.
Use rudder to prevent yaw. Shortly after lift-off the blue Beta (b) target replaces
the normal sideslip indication on the PFD. Adjust rudder to zero the b target.
When the b target is centred, total drag is minimised even though there is a
small amount of sideslip. The calculation of the b target is a compromise
between drag produced by deflection of control surfaces and airframe drag
produced by a slight sideslip. Centring the b target produces less total drag than
centring a conventional ball, as rudder deflection, aileron deflection, spoiler
deployment and aircraft body angle are all taken into account.
Control heading conventionally with bank, keeping the b target at zero with
rudder. Accelerate if the b target cannot be zeroed with full rudder. Trim the
rudder conventionally.
Once airborne with a positive rate of climb and the radio altitude increasing, the
PF calls for Gear Up.
to
bu
y
.d o
.c
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.20.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Consider the use of TOGA thrust taking into account the following:
lic
8.20.7
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
For a FLEX take-off, selecting the operating engine(s) to TOGA provides

an additional performance margin, but is not a reduced thrust take-off
certification requirement. The application of TOGA very quickly provides a
large thrust increase. However, this comes with a significant increase in
yawing moment and an increased pitch rate. The selection of TOGA
restores thrust margins but it may increase aircraft handling workload
ALT/NAV mode changes may occur if TOGA is selected after the ALT pb
is pressed with flaps/slats retracted. HDG mode will engage and command
the aircraft heading at the time of TOGA selection
For a DRT take-off, asymmetric TOGA thrust must not be selected if the
speed is below F speed in CONF 2 and 3 due to VMCA considerations.
FCTM Ch 4 refers
TOGA thrust is limited to 10 minutes
The PNF closely monitors the aircraft's flight path and cancels any Master
Warning or Caution. At 400 ft RA, the PNF reads the ECAM title displayed on the
top line of the E/WD. Once the PF has stabilised the flight path, he confirms the
failure. If it is necessary to delay the ECAM procedure, he orders "Standby".
Otherwise he announces "I have control, ECAM actions". It is not necessary to
rush into the ECAM actions and 400 ft RA is the minimum height at which
commencement of the actions should be considered.
Normally, only those actions involving movement of the THRUST LEVER and/or
ENG MASTER and those actions required to clear RED warnings are carried out
prior to level acceleration and flap retraction. However, in the event of ENG
FAILURE WITH DAMAGE or ENG FIRE, the ECAM procedure is continued until
the engine is secured. For less critical failures, ECAM actions can be interrupted
when necessary to allow both pilots to monitor normal operational requirements.
At the engine-out acceleration altitude, select ALT to level off and accelerate. If
the aircraft is being flown manually, the rudder input needed to keep the b target
centred reduces as airspeed increases. Retract the flaps as normal. When the
flap lever is at zero, the b target reverts to the normal sideslip indication which
should be centred conventionally using rudder. As the speed trend arrow
reaches Green Dot speed in clean configuration, pull for OP CLB.
Select THR MCT when the LVR MCT message flashes on the FCU, triggered as
the speed index reaches Green Dot and resume the climb using MCT. If the
thrust levers are already in the FLX/MCT detent, move them to CL and then back
to MCT to engage the A/THR. After MCT is set, both packs are selected on by
the PNF (if previously off for take-off).
h a n g e Vi
e
When an engine failure occurs after take-off, noise abatement procedures no

longer apply. The acceleration altitude provides a compromise between obstacle
clearance and engine thrust limiting time. It allows the aircraft to be configured to
Flap 0 and Green Dot speed. This provides the best climb gradient.
Once established on the final take-off flight path, continue the ECAM until the
STATUS is displayed. At this point, carry out the AFTER T/O checklist. Finally,
review the STATUS and consult the OEB for applicability.
to
bu
y
.d o
.c
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.20.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
ENGINE FAILURE DURING INITIAL CLIMB-OUT

Proceed as above. If the failure occurs above V2 however, the SRS will
command an attitude to maintain the speed at which the failure occurred. In any
event the minimum speed is V2.
When an engine failure is detected, the FMGS predictions are based on the
engine-out configuration and any pre-selected speeds entered in the MCDU are
deleted. Consider the use of the EOSID, if one exists in the database.
ENGINE FAILURE DURING CRUISE

There are three strategies available for dealing with an engine failure in the
cruise:
Standard strategy
Obstacle strategy
Fixed speed strategy
Unless a specific procedure has been established before dispatch (considering

ETOPS or mountainous areas), the standard strategy is recommended.
As soon as an engine failure is recognised, the PF should call for the ECAM
actions and simultaneously:
Set MCT on the remaining engine(s).

Disconnect the A/THR.
Select the SPEED according to the strategy.
Select a HDG to keep clear of the airway, preferably heading towards an
alternate, if appropriate. Consider the aircraft position relative to any
relevant critical or equi-time point.
Select the LRC ceiling or driftdown ceiling according to strategy in the FCU
ALT window and pull for OP DES when target speed is reached.
Placing the thrust lever(s) to MCT and carrying out the ECAM actions should not
be rushed, as it is important to complete the procedure correctly. Generally,
there is sufficient time to cross-check all actions. However, at high levels close to
limiting weights, more urgency is required, as speed decays more quickly.
The FCU selections for an engine failure run from left to right:
SPD select.
HDG select.
FCU altitude insert.
ALT selector pull (when target speed is reached).
lic
8.20.9
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
Standard Strategy (Long Range Strategy)

Set .82M/300 kt. The speed of .82M/300 kt is chosen to ensure the aircraft is
within the stabilised windmill engine relight in-flight envelope. The thrust is fixed
at MCT with A/THR disconnected and speed is controlled by the elevator. The
REC MAX EO cruise level displayed on the EO PROG page, equates to LRC
with anti-icing off. The nearest semi-circular or RVSM cruise level at or below
this level should be set on the FCU. Once established in the descent, the PERF
CRZ page shows time to descend and predicted descent distance. These can
also be checked on the relevant performance table in the QRH. If V/S becomes
less than 500 ft/min, select V/S -500 ft/min and A/THR on. This is likely to occur
approaching level off altitude, or at light weight.
Cruise altitude and speed are also available in the QRH in case of double FM
failure.
Fixed Speed Strategy

For ETOPS operations, a fixed speed strategy is adopted for planning purposes
to establish the maximum diversion distance and the diversion fuel requirements
for the single engine ETOPS critical scenario. Two fixed speed strategies are
considered:
VMO (M.82/330/MCT)
310 kt (M.82/310/MCT)
During an ETOPS diversion the Captain may choose to adopt any suitable
strategy and is not required to fly the fixed speed strategy unless operationally
required.
ETOPS is taught as a separate course. Volume 2 Part 2 refers.
Obstacle Strategy
To minimise the rate and angle of descent and enable the aircraft to clear high
terrain or obstacles on the intended flight path, the drift down procedure should
be adopted. The procedure is similar to the standard strategy, except that the
speed target is Green Dot.
The PERF CRZ page displays the drift down ceiling, assuming Green Dot speed.
Conversely, the PROG page displays the EO REC MAX ALT assuming LRC
speed. The drift down ceiling at Green Dot is higher than the EO REC MAX ALT
and the aircraft should be able to stabilise at this altitude. When clear of
obstacles, set the LRC ceiling on the FCU and descend if required. Accelerate to
LRC speed and engage A/THR.
to
bu
y
.d o
.c
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.20.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
8.20.11
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
ONE ENGINE INOPERATIVE LANDING

Autoland is available with one engine inoperative. Maximum use of the AP
should be made to minimise crew workload.
If an autoland is not possible, e.g. due to airport equipment limitations, fly a
manual approach. A manual approach and landing with one engine inoperative
is conventional. Use rudder trim to keep the sideslip indication centred. The
sideslip indication remains yellow as long as N1 on the remaining engine(s) is
below 80%. With flap selected and thrust above 80% N1, the indicator changes
to the engine-out mode blue b target. This visual cue indicates that the aircraft is
approaching its maximum thrust capability. Although the A/THR is available,
some pilots may prefer to use manual thrust as they find it easier to anticipate
rudder inputs as the power changes.
Avoid selecting the gear down in level flight, as high thrust settings will be
required, increasing the handling workload.
To make the landing run easier, it is recommended to reset the rudder trim to
zero in the later stages of the approach. Anticipate the increased rudder force
required as the trim is removed when the rudder trim reset button is pressed.
With rudder trim at zero, the neutral rudder pedal position corresponds to zero
rudder and zero nose wheel deflection.
After touchdown, use any remaining reverser(s).
CIRCLING ONE ENGINE INOPERATIVE

A circling approach with one engine inoperative requires the downwind leg to be
flown in CONF 3, with landing gear extended. In hot and high conditions, the
aircraft may not be able to maintain level flight in CONF 3 with landing gear
down. In this case, landing gear extension should be delayed until leaving the
circling altitude. Until the gear is locked down and depending on the circling
altitude, it is possible to receive the L/G GEAR NOT DOWN ECAM warning
(below 750 ft RA) or a GPWS TOO LOW GEAR (below 500 ft RA). However,
with a minimum circling altitude of 1000 ft AAL it is unlikely that this problem will
be encountered.
h a n g e Vi
e
ONE ENGINE INOPERATIVE GO-AROUND

A one engine inoperative go-around is similar to that flown with all engines
operating. On the application of TOGA, rudder must be applied promptly to
compensate for the asymmetric increase in thrust and to keep the b target
centred. Smoothly increase pitch to follow the SRS. If SRS is not available, the
initial target pitch attitude is 12.5. As a one engine inoperative approach is flown
with Flaps 3, the initial flap retraction is to Flaps 2. With a positive ROC and an
increasing RA, retract the gear. The lateral FD mode is initially GA TRK, which
guides the aircraft on the track at TOGA selection. If there are terrain
considerations on the go-around path or specific tracking requirements, select
NAV without delay. Select ALT at the engine inoperative acceleration altitude
and retract the flap using the same technique as described in the Engine Failure
after V1.
At certain weights and CG positions, it may not be possible to satisfy b target
demands at VLS. Consequently, when obstacle clearance is assured, accelerate
to a speed at which the b target can be satisifed.
TWO ENGINES INOPERATIVE LANDING (A343/A346)

General
Operational requirements following a second engine failure are detailed in
Volume 2 Part 2. Continued flight may be complicated by driftdown, lateral
navigation requirements to ensure terrain clearance, fuel jettison to achieve
desired performance and other factors.
It is recommended that weather at the selected ERA should permit visual flight
on approach from at least 500 ft AGL to the runway. The primary consideration
for approach, landing and go-around is one of control. Go-arounds in particular
require careful planning, briefing and execution to ensure controllability margins
are not compromised.
The nature of the failure also needs to be considered, particularly which
combination of engines and associated hydraulic systems have been lost.
Loss Of One Engine On Each Wing

For the loss of any two engines from opposite wings, VLS on the MCDU and
PFD is limited to VMCL (A343: 125 kt), (A346: 132 kt). The loss of engines 1 and
4 does not have a major effect on control, however without the green hydraulic
system a manual landing gear extension is required and there is no retraction
capability. Consequently a go-around is not possible after L/G extension and the
aircraft is committed to land . Landing must be assured prior to L/G extension.
to
bu
y
.d o
.c
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.20.12
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
8.20.13
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Loss Of Two Engines On The Same Wing

Control of the aircraft is more complicated following the loss of two engines on a
single wing. The critical factor is speed, which must not reduce below VMCL-2
(157 kt) until landing is assured. VLS displayed on the PFD will never be lower
than VMCL-2. Speed reduction below VMCL-2 is permissible once landing is
assured. L/G retraction is available in the event of a go-around, but failure to
maintain VMCL-2 with TOGA thrust applied and an insufficient bank angle, will
result in loss of directional control.
Approach
A Commit Altitude is established for any two engine approach. The equivalent
height should never be below 500 ft AGL. It serves two purposes; to establish a
decision point on approach from which a land or go-around decision can be
made, and because it is well above the Cat 1 minima (200 ft AGL), it provides a
300 ft buffer. In the event of a performance-limited go-around, this buffer can be
used to descend and clean up whilst easily ensuring that speed will be well
above VMCL-2 when the nose is raised to climb away.
The Commit Altitude should be inserted on the MCDU PERF APPR page as the
MDA, but is not a not below altitude in the conventional sense.
Autothrust is disconnected once stabilised on final approach. At the Commit
Altitude with the landing assured, speed may be reduced to normal VAPP. In the
case of two engines inoperative on the same wing, VAPP will be below the VLS
displayed on the PFD (VMCL-2), e.g based on the MCDU VLS in case of loss of
two engines on the same wing. Speed reduction below VMCL-2 is acceptable at
this stage, as VMCL-2 is based on the use of TOGA thrust on the remaining
engines, and adequate margins remain at normal approach speeds and thrust
settings.
Go-Around
If a landing is not assured by the Commit Altitude (or immediately prior to L/G
extension with engines 1 and 4 inoperative), then a go-around should be
initiated. If the approach has been flown accurately, the speed will be at VLS.
TOGA thrust should be selected. At certain weights and CG positions, it may not
be possible to satisfy the target demands at VLS. If two engines are
inoperative on the same wing, this may require leading with the inboard thrust
lever. TOGA should be achieved on the outboard engine as soon as directional
control permits, but without undue delay. When obstacle clearance is assured,
accelerate to a speed at which the target can be satisfied.
h a n g e Vi
e
As TOGA is selected, PF calls Go Around, Flaps 1, Gear Up. These directives

may be actioned simultaneously by the PNF as landing gear retraction from
above the Commit altitude does not require confirmation of a positive rate of
climb. The important thing is to reduce drag as quickly as possible. If necessary,
the descending approach path may be maintained while these actions are
performed, but not below 200 ft AGL. In normal circumstances, this will be in
VMC.
If a go-around is required in IMC, the aircraft may descend below the Commit
Altitude, but should not descend below the minima for the approach aid in use to
ensure obstacle clearance is maintained. If such a go-around is envisaged, the
briefing should cover crew intentions regarding the use of autoflight systems, as
the FD will command a pitch up to SRS as soon as the first thrust lever reaches
the TOGA detent.
RECOVERY FROM ALPHA PROTECTION AND ALPHA FLOOR

General
If alpha protection or alpha floor is triggered inadvertently, recover from these
protection modes as soon as other considerations allow by easing forward on
the sidestick to reduce the angle of attack below the value set for alpha
protection, while simultaneously increasing thrust.
Alpha Protection
Pitch control will resume the normal load factor law if the stick is pushed forward
of neutral, but will re-enter alpha protection if the stick is released with the
indicated airspeed still below Va PROT. Consequently, to exit alpha protection
properly, reduce the angle of attack to a value less than that set for alpha
protection.
The PFD shows the recovery clearly, because the indicated speed will be above
the black and amber strip when out of alpha protection. When no longer in alpha
protection, increase speed above VLS (top of the amber strip) as soon as other
considerations allow.
Alpha Floor
Alpha floor will normally be triggered just after alpha protection is entered, and
TOGA thrust will be applied automatically. To recover to a normal flight
condition, alpha protection should be exited by easing forward on the sidestick,
as described above. The alpha floor thrust condition should be canceled by
using the A/THR disconnect pushbutton on either thrust lever as soon as a safe
speed above VLS is regained.
to
bu
y
.d o
.c
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.20.14
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
STALL RECOVERY
In alternate and direct laws, an aural stall warning STALL, STALL, STALL
sounds at low speeds. Recovery is conventional. Apply the following actions
simultaneously:
lic
8.20.15
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Set TOGA thrust

Reduce pitch attitude to 10 below FL200 or 5 at or above FL200
Roll wings level
Check that the speedbrake is retracted
Below FL200 and in the clean configuration, select Flaps 1. If ground contact is
possible, reduce pitch attitude no more than necessary to allow airspeed to
increase. After the initial recovery, maintain speed close to VSW until it is safe to
accelerate.
When out of the stall condition and no threat of ground contact exists, select the
landing gear up. Recover to normal speeds and select flaps as required.
In case of one engine inoperative use thrust and rudder with care.
The aural stall warning may also sound at high altitude, where it warns that the
aircraft is approaching the angle of attack for the onset of buffet. To recover,
relax the back pressure on the sidestick and if necessary reduce bank angle.
Once the stall warning stops, back pressure may be increased again, if
necessary, to get back on the planned trajectory.
RECOVERY FROM HIGH SPEED PROTECTION

On Descent
In managed descent, if the speed is accelerating towards VMO/MMO due to
descending out of a tailwind, or there is an encounter with windshear, pull for
OPN DES. This action will immediately command thrust idle and the target
speed will be the managed descent speed in the FM, or the speed selected on
the FCU. Speed brake may also be used to assist in controlling the speed.
If the aircraft accelerates above VMO/MMO and triggers the high-speed
protection the autopilot will disengage. If VMO/MMO is exceeded significantly the
associated overspeed aural warning may have overwhelmed the autopilot
disconnect aural warning.
The high-speed protection will provide a nose-up order in addition to any pilot
input during the recovery. It is not usually necessary to use a pull force to
recover. If a quicker recovery is required for operational reasons, pull back
smoothly and progressively, monitoring the g indication on the ECAM. It is
important to consider the effect of increased g on the people who may be
standing in the cabin.
When below the high-speed protection range, check autopilot engagement
status and re-engage it if necessary.
F-
c u -tr a c k
Cruise
In the cruise an encounter with CAT, windshear, or standing waves may cause
the speed to increase rapidly. The recommended technique for recovery is to
initially select a lower speed on the FCU, but not below green dot. This will have
the effect of commanding the autothrust system to reduce the thrust, which may
be sufficient to stop a VMO/MMO exceedance.
If the aircraft accelerates above VMO/MMO and triggers the high-speed
protection the autopilot will disengage and the high-speed protection will provide
a nose-up order. If VMO/MMO is exceeded significantly the associated
overspeed aural warning may have overwhelmed the autopilot disconnect aural
warning.
The pilot should not pitch up to reduce speed, but should attempt to maintain the
cruise altitude by making smooth inputs on the sidestick. The autothrust system
will be reducing the thrust, and it should not be necessary to disconnect the
autothrust. It is preferable to leave the autothrust engaged to reduce workload
once the cause of the overspeed is passed. In extreme cases the speedbrakes
may be used, but they should be used with caution at high altitudes.
When below the high-speed protection range, check autopilot engagement
status and re-engage it if necessary.
to
k
lic
.d o
C
w
.c
.d o
A330/A340
FCTM
REV 2 (25 JUL 06)
bu
y
bu
to
lic
8.20.16
w
O
W
h a n g e Vi
e
O
W
XC
er
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
EMERGENCY ELECTRICAL CONFIGURATION

The Emergency Electrical Configuration is triggered by the loss of all AC
busbars. This results in the automatic engagement of the Emergency Generator,
driven by the Green hydraulic system and powered by either the Engine Driven
Pump (EDP) or the RAT, depending upon the cause of the failure. It is most
unlikely that this configuration will ever be encountered, but be aware that
workload is immediately increased in Emergency Electrical Configuration, The
handling of this failure is referred to as a "complex procedure". A summary for
handling the procedure is included in the QRH, which should be referred to upon
completion of the ECAM procedure.
The electrical distribution network has been designed to enable the crew to fly
the aircraft, navigate and communicate. The list of equipment available in
Emergency Electrical Configuration is detailed in the QRH. The available
systems of particular interest prior to selection of LAND RCVY are:
A333
EMER GEN Powered by EDP
EMER GEN Powered by RAT
FLY
AP1, PFD 1, Pitch trim,

Rudder trim, ALTN LAW,
Upper ECAM, ECP,
ISIS/STBY INST
PFD 1, ALTN LAW, Upper

ECAM, ECP, ISIS/STBY INST
NAV
ND 1, FMGC 1, MCDU 1,
DDRMI (VOR/DME 1 or ADF
1), FCU, WXRDR 1
FCU, STBY NAV (via RMP 1),

DDRMI (VOR 1 or ADF 1)
VHF 1, HF 1, RMP 1, ACP 1 &

2, Loundspeakers 1 & 2
VHF 1, RMP 1, ACP 1 & 2,

Loudspeakers 1 & 2
EMER GEN Powered by EDP
EMER GEN Powered by RAT
FLY
PFD 1, Pitch trim, Rudder trim

(without centre pedestal
position indication), ALTN
LAW, Upper ECAM, ECP,
ISIS/STBY INST
PFD 1, ALTN LAW, Upper

ECAM, ECP, ISIS/STBY INST
NAV
MCDU 1 (B/U NAV), STBY

NAV (via RMP 1), DDRMI
(VOR/DME 1 or ADF 1), FCU
FCU, STBY NAV (via RMP 1),

DDRMI (VOR 1 or ADF 1)
VHF 1, RMP 1, ACP 1 & 2,

Loudspeakers 1 & 2
VHF 1, RMP 1, ACP 1 & 2,

Loudspeakers 1 & 2
COMM
A343/A346
COMM
lic
8.30.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Electrical
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
Only PFD 1 is available. The AP will disengage when the failure occurs but AP 1
can be reengaged on the A333 if the EMER GEN is powered by an EDP. As
there is no AP available in this configuration in the A340, the Captain must take
control and fly the aircraft manually. The A340 aircraft is out of trim in roll due to
right outboard aileron upfloat, caused by no power being available to Prim 3 or
Sec 2, and neither pitch trim or rudder trim is available. The aircraft is in ALTN
law (A333 due loss of slat/flap position; A340 due loss of 2 ADRs).
Consequently, pay close attention to bank angle and heading. A333/A346: is in
N1 degraded mode. Once a safe flight path is established and the aircraft is
under control, carry out the ECAM actions.
It is important to correctly identify the failure, as it is possible to confuse
Emergency Electrical Configuration with an All Engine Flameout. Therefore, it is
very important that the ECAM title is read accurately before starting the ECAM
actions. The procedure is lengthy and complicated and, as only one ECAM
display is available, disciplined use of the ECP is essential. FCTM Ch 2 refers.
Consider starting the APU.
Although the ECAM displays LAND ASAP in red, it is unwise to attempt an
approach at a poorly equipped airfield in marginal weather. Consider the power
source for the Emergency Generator as the emergency generator outputs
approximately twice as much electrical power when powered by the EDP. The
aircraft is better configured when the EDP rather than the RAT, powers the
Emergency Generator. In either case, prolonged flight in this configuration is not
recommended.
TRK/FPA should be selected and FDs turned off. This allows the display of the
blue track index on the Captain's PFD to assist in maintaining track. Navigation
should be achieved using all available means. VOR/DME1 or ADF1 only are
available on the DDRMI. The navigation facilities available depend on the aircraft
type and the cause of the failure. QRH refers.
A MAYDAY should be declared. Radar headings to the nearest suitable airfield
may be available and separation from other traffic can be increased.
To ensure proper fuel feed to the engines in ELEC EMER CONFIG, (A333/A343:
one) (A346: two) fuel pump(s) is/are powered and the cross-feed(s)
automatically open. The Engine Anti-Ice is on.
to
bu
y
.d o
.c
Electrical
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.30.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
8.30.3
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Electrical
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Press the LAND RECOVERY pb prior to commencing the approach. This allows
the recovery of a number of systems required for landing, e.g. ILS 1, SFCC 1,
LGCIU 1 (and A333: BSCU 1, LH WHC 1, LH Landing Light). It also sheds a
number of systems that are no longer required, e.g. the operative fuel pump(s)
(and A333: WX RDR 1, HF 1, ADR 3 hence AP 1).
During the approach, the characteristic speeds may not be displayed on the PFD
and can be extracted from the QRH prior to descent. Only raw data is available
for the approach. The landing gear is extended using the gravity system to
prevent fluctuations in the green hydraulic system whilst the Emergency
Generator is operating, thereby preventing it from possibly disconnecting.
Consequently, as the doors remain open, the NWS is not available. When the
gear is extended, the aircraft reverts to Flare Law (Direct) and "USE MAN PITCH
TRIM" is displayed on PFD 1. Thrust reversers autobrake and antiskid are not
available.
If the RAT powers the Emergency Generator, the available systems are further
reduced and the requirement to land is more urgent. Of particular note is that
there is no pitch trim, no rudder trim, no FMGC 1 and no AP 1. Upon selecting
LAND RECOVERY, only the slat channel of SFCC 1 is recovered, so the flaps
are not available for the landing. At slat extension, the Emergency Generator is
inhibited, and the aircraft is supplied by batteries only.
Restoring Normal Electrical Power After EMER ELEC CONFIG

When ELEC EMER CONFIG occurs, the LAND RECOVERY AC and DC
BUSES are initially shed and will remain shed until the LAND RECOVERY pb is
selected ON. This is true even if normal electrical configuration is restored.
Consequently, after restoring normal electrical power, the LAND RECOVERY pb
will still need to be selected ON for approach.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
FIRE PROTECTION
Fire and/or smoke in the fuselage present the crew with potentially difficult
situations. Not only will they have to deal with the emergency itself, but also the
passengers are likely to panic should they become aware of the situation. It is
essential therefore, that action to control the source of combustion is not
delayed. Consider an immediate diversion.
SMOKE
If smoke or fumes are detected in the flight deck, the crew should immediately
don their oxygen masks with 100% selected.
Smoke in the cabin should be easily identifiable and thus easier to fight. The
source is identified either by a local warning, e.g. lavatory fire, or by direct
observation by the cabin crew. In every case, the aim is to isolate the source of
the smoke and extinguish any fire. When fighting a fire in the cabin, wear a PBE
to avoid smoke inhalation.
It is not so easy to identify the source of smoke from either the air conditioning or
avionics. If the source of the smoke is immediately obvious, isolate the faulty
equipment without delay.
Air conditioning smoke can be transported to other cabin areas and some
difficulty may be encountered in identifying the origin of the smoke. Avionics
smoke requires the crew to isolate the faulty equipment, which can also be quite
difficult to ascertain. There may not be any ECAM warning. If this is the case,
apply the QRH procedure.
The QRH procedure is designed to cover all cases even where the source of the
smoke or fumes is unknown. It should be applied if smoke and/or fumes are
detected with or without AVNCS VENT SMOKE ECAM activation. If the AVNCS
VENT SMOKE ECAM procedure is displayed, suspect avionics smoke.
The single procedure layout is organised in three steps:
lic
8.40.1
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Fire Protection
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Common actions (before the text box). These should be applied

immediately, whatever the origin of the smoke, and before trying to identify
this origin. They are designed to protect the crew, extract the smoke
overboard, prevent smoke recirculation and isolate potential sources.
Smoke removal procedure (text box). At any time during the procedure, if
dense smoke exists, the crew may apply the boxed items for smoke
removal. The SMOKE REMOVAL procedure will eventually direct the crew
back to complete the SMOKE/FUMES/AVNCS SMOKE procedure.
Specific actions to identify and isolate potential smoke sources (below text
box).
h a n g e Vi
e
CARGO SMOKE
The cargo smoke detectors are sensitive to the extinguishing agent. Therefore,
even after successfully extinguishing a cargo fire, the SMOKE FWD (AFT/BULK)
CRG SMOKE warning can be expected to remain. LAND ASAP in red is
displayed on the ECAM. As there is no method of checking whether a cargo fire
has been extinguished, divert to the nearest suitable airport.
On the ground, instruct the ground crew not to open the cargo door until the
passengers have disembarked and fire services are present.
On the ground, smoke warnings may be triggered due to high levels of humidity
or following spraying of a compartment to comply with quarantine regulations. If
a SMOKE warning occurs on the ground with cargo compartment doors open, do
not immediately discharge the extinguishing agent without first ordering the
ground crew to investigate and eliminate the smoke source. If the warning is
confirmed to be false, then once extinguished, it will be necessary to reset VENT
CONT 1 & 2 reset buttons to restore normal cargo ventilation (FCOM 3.02.26
refers).
to
bu
y
.d o
.c
Fire Protection
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.40.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
NON-NORMAL FLAPS/SLATS CONFIGURATION

Non-normal operation of the flaps and/or slats may be due to one of the following
problems:
lic
8.50.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Double SFCC failure

Double hydraulic failure (B+G or Y+G)
Flaps/Slats jammed (operation of the WTB)
Non-normal operation of the flaps and slats has significant operational

consequences since the control laws may change. The attitude on approach
changes, approach speeds and landing distances increase and the go-around
procedure may have to be modified. The most significant failure is a double
SFCC fault, which leads to not only the loss of AP and A/THR but also a
complete loss of speed limit information on the PFD.
Flap/slat problems are normally considered in the context of the landing phase.
However, it is possible to encounter a problem during retraction after take-off. In
this case, use selected speed in order to avoid exceeding VFE. The landing
distance available at the departure airport and the aircraft gross weight will
determine the next course of action.
The most probable time for the detection of a slat failure is on the selection of
Flaps 1 for the approach. With the A/THR operative and the flaps lever at 1, the
managed speed target becomes S speed. If the slats fail to extend, select Green
Dot to avoid deceleration in the clean configuration, as the aircraft automatically
decelerates to S speed even if the slats do not extend. Multiple failures are
highly improbable, however appreciate that the initial ECAM F/CTL SLATS
FAULT/LOCKED gives no indication of potential flap problems. Thus it is
possible to spend time determining the appropriate landing configuration before
the complete extent of the flap/slat problem has been identified. If possible, delay
the approach to complete the ECAM procedure, refer to the LANDING WITH
SLATS OR FLAPS JAMMED paper checklist, determine the VAPP and landing
distance and to update the approach briefing.
During the ECAM procedure, Flaps 2 will be selected, as the Flap Lever Position
table in the QRH directs the use of a minimum of CONF 2. If at this point there is
an additional FLAPS FAULT/LOCKED message, then the full extent of the failure
can be determined and the appropriate checklist actioned. If both flaps and slats
are jammed at zero, the QRH directs the crew to the NO FLAPS NO SLATS
LANDING checklist. Setting the flap lever back to Flaps 1 during this particular
checklist is to enable the use of SRS during a go-around. VFE displayed on the
PFD will be incorrect since it based on flap lever position and not the actual
configuration.
h a n g e Vi
e
In the QRH LANDING WITH SLATS OR FLAPS JAMMED checklist, the line;
"SPEED SEL....................................................VFE NEXT PLACARD SPD - 5 kt"
can be slightly confusing but is designed to allow the extension of the flaps/slats
to the required landing configuration while controlling the speed in a safe
manner. This is particularly relevant at heavy weights. The paper checklist
appears to circumvent normal use of the ECAM procedure associated with the
initial slats locked message. However, its intent is to resolve all SFCC issues,
rather than just the initial slats SFCC issue and thus more quickly identify the
achievable landing configuration. Use the lower of VFE Next or Placard Speed.
(VFE Next on the PFD and placard speeds are identical, except for Flap 2 where
the PFD initially displays VFE NEXT for CONF 1* against a placard speed for
CONF 2). The speed reduction and configuration changes should be carried out
in non-manoeuvring flight.
The following scenario on an A333 assumes a failure with the slats locking
between 0 and 1 and flaps operating normally:
Select Green Dot and use selected speed for the rest of the approach.
Green Dot is used initially since the aircraft is effectively still in the clean
configuration.
With Flap 1 selected, VFE NEXT is 205 kt, Placard Speed would be 196
kt.
Select 191 kt and when below Placard Speed of 196 kt, select Flap 2.
While multiple failures are improbable, this is the point when any flap
SFCC problems will be indicated.
If the flaps extend, VLS reduces and the selected speed can be reduced.
Do not reduce speed below VLS.
Repeat the procedure until landing configuration is reached, using the
applicable VFE NEXT.
At high weights, this procedure may involve reducing speed below the
manoeuvring speed for the current configuration. In a non-normal situation this is
acceptable on a short-term basis, provided the speed remains above VLS.
The landing distance factors and approach speed increments are available in the
QRH. Determine the values of each as follows:
LDG DIST = Actual Landing Distance Without Autobrake, CONF FULL x

factor.
VAPP = VREF + wVREF + Wind correction.
Assuming VLS is displayed on the PFD, the approach speed should be close to
VLS plus wind correction, as VLS is computed using the actual slat/flap position.
The use of AP down to 500 ft AAL and A/THR (if available) is recommended.
The AP is not optimised for non-normal configurations and so its performance
must be closely monitored. The PF should be ready to take over manually if AP
performance becomes unsatisfactory.
to
bu
y
.d o
.c
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 2 (25 JUL 06)

.d o
lic
lic
8.50.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
The QRH NO FLAPS NO SLATS LANDING checklist is a relatively simple

procedure. However, more distance is required for manoeuvring. During the
approach the aircraft pitch attitude is high, increasing the risk of a tailstrike.
Consequently, only make a small pitch adjustment in the flare to reduce the rate
of descent prior to a positive touchdown. Due to the high touchdown speed,
avoid a prolonged float. The use of (A333/A343: MED) (A346: 3/4) autobrake is
strongly recommended.
During the approach briefing, emphasise the configuration, calls to be made and
speeds to be flown in the event of a missed approach. At the acceleration
altitude, use selected speed to control the acceleration to the required speed for
the configuration.
Consider the fuel available and the increased consumption associated with a
diversion when flying with flaps and/or slats jammed. Cruise altitude is limited to
20000 ft when diverting with flaps/slats extended.
ELEVATOR REDUNDANCY LOST

The F/CTL ELEV REDUND LOST procedure, which is triggered in case of dual
failures affecting the flight controls, is designed to prepare the aircraft for a third
related failure which would result in the simultaneous loss of one or both
elevators and some ailerons. The procedure has two entry points depending on
the combination of dual failures:
lic
8.50.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Flight Controls
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Ailerons are preset (if a third related failure would result in the loss of both
elevators)
Ailerons are not preset (if a third related failure would result in the loss of
only one elevator)
In anticipation of a third failure that would result in the loss of both elevators, the
ailerons are preset 12 up, and the resulting pitch up moment compensated for
by the elevators, which are still available, and then trimmed by the THS. This
preset is a compromise between the increased fuel consumption (approximately
16%) and the pitch up moment that would occur following a third failure. The
aileron preset is displayed on ECAM F/CTL page.
If a third failure would result in the loss of only one elevator, there is no aileron
preset since the remaining elevator will compensate for the pitch up moment.
Depending on the combination of failures, the AP may not be available. If the
ailerons are preset, the AP automatically disconnects, as its performance is less
than optimum. However, below 2000 ft or when in CONF 2, the aileron preset is
inhibited to facilitate the landing and permit the use of AP if available.
The F/CTL ELEV REDUND LOST procedure imposes both speed and FL
limitations to ensure structural integrity and to maintain stabiliser authority should
a third failure occur. It requires the application of a LDG DIST PROC and since it
is the result of multiple failures, the QRH table must be carefully interrogated for
the correct LDG CONF, DVREF and LDG DIST factors.
h a n g e Vi
e
The Flight Envelope computer computes CG as a function of the THS position,

and this value is used to monitor the FCMC-computed CG and trigger the AFT
CG warning. In the case of aileron preset, the FE-computed CG value is
erroneous because the THS will be abnormally displaced to counteract the pitch
up moment. Consequently any AFT CG warning should be disregarded. GWCG,
computed by the FCMC and displayed on ECAM, remains reliable.
If a third failure does occur and results in the loss of both elevators, the failed
ailerons reset to their zero hinge moment, equivalent to 14 up. As the ailerons
were previously preset up 12, the transition is smooth with only a slight pitch up
moment that can be controlled with the THS. MAN PITCH TRIM ONLY is
displayed on the top of PFD. If desired, the A/THR may be disconnected to
enable smoother longitudinal control with manual pitch trim. The FL and speed
limitations now no longer apply.
Flight Control Architecture, QRH Part 5 refers.
to
bu
y
.d o
.c
Flight Controls
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.50.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
FUEL LEAK
Significant fuel leaks, although rare, are sometimes difficult to detect.
Maintaining the fuel log and comparing fuel on board to expected flight plan fuel
during regular fuel checks, will alert the crew to any discrepancy. This should
then be investigated without delay. Fuel checks should be carried out when
sequencing appropriately spaced waypoints and at least once every hour. Any
time an unexpected fuel quantity indication, ECAM fuel message or imbalance is
noted, a fuel leak should be considered. Initial indications should be carefully
cross-checked by reference to other means. If possible, conduct a visual
inspection of the wings and engines to check for signs of a leak.
If a leak is suspected, action the non-normal checklist. If the leak is from the
wing or cannot be located, it is IMPERATIVE that the cross-feed valve(s) is (are)
not opened.
Fuel Check Procedure, FCTM Ch 5 refers.
FUEL JETTISON
If there is no critical reason to land immediately it is desirable to jettison fuel and
land as close to maximum landing weight as practicable. On the A340, with an
engine secured after a failure, or with a non-critical failure, such as jammed
flaps, there is no requirement to land as soon as possible.
Do not delay the landing because the aircraft is overweight if there is a critical
reason to land immediately. Some valid reasons include:
lic
8.60.1
REV 2 (25
JUL 06)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Fuel
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
An abnormal situation on take-off that casts doubt on the continued safe

operation of the flight.
Any fire that will not extinguish.
A life that will be endangered unless immediate medical attention is
received.
A time critical in-flight situation that requires an immediate diversion and
landing.
The planning and execution of an overweight landing requires good judgement

and due consideration of the many factors involved. The jettison decision must
balance the urgency of an immediate landing against the demands and risks of
the overweight landing.
At high landing weights the flare must be carefully judged, since the increased
inertia of the aircraft requires more anticipation to achieve a normal touchdown.
Any turbulence on the approach will also contribute to the possibility of a firm
landing. A firm landing when the aircraft is significantly overweight increases the
chance of permanent damage to the aircraft landing gear due to the increased
energy absorbed by the landing gear.
The Overweight Landing checklist in QRH section 2 provides further information
and guidance.
h a n g e Vi
e
HANDLING OF EXPECTED LOW FUEL LEVELS AT

DESTINATION
ADVOIDANCE OF NON-STANDARD FUEL DISTRIBUTIONS ON

ARRIVAL
AVOIDANCE OF FUEL INDUCED WING ICING ON ARRIVAL

to
bu
y
.d o
.c
Fuel
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.60.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
DOUBLE HYDRAULIC FAILURES

Single hydraulic failures have very little effect on the handling of the aircraft but
cause a degradation of the landing capability to Cat 3 Single. However, double
hydraulic failures are significant due to the following:
lic
8.70.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Hydraulic
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Loss of AP
Flight control law degradation (ALTN)
Landing in non-normal configuration
Extensive ECAM procedures with associated workload and task-sharing
considerations
Significant considerations for approach and landing
The electrical pumps supply only limited power and should not be used to
replace the engine driven pumps to supply the flight controls as they cannot
cover any high transient demands. Consequently, aircraft handling could be
degraded due to flight control jerk. As a general rule, do not select the ELEC
HYD PUMP on except temporarily to retract the spoilers if they remain out after a
hydraulic failure.
The RAT is designed to supply the Emergency Generator and flight controls
using the green hydraulic system, and can cover high transient demands.
However, the RAT flow is significantly less than an engine driven pump flow and
is dependent on the aircraft speed. The RAT may still pressurise the green
hydraulic system even in the case of LO LVL. It must not be used in case of
green hydraulic system overheat. At low speed, the RAT stalls. Consequently,
some anticipation is required from the crew to carry out a safe landing.
A double hydraulic failure is an emergency situation, with LAND ASAP displayed
in red. Declare a MAYDAY to ATC and land as soon as possible, however
ECAM actions should be completed prior to the approach.
FD and A/THR are available, however the AP will be lost. Therefore, the PF will
have a high workload in flying the aircraft and handling the communications, with
the flight controls in Alternate Law. Additionally, depending on the exact reason
for the failure, aircraft handling characteristics may be different due to the loss of
some control surfaces. This failure is termed a "complex procedure".
Consequently, after completing ECAM actions, refer to the QRH summary during
the handling of the procedure. It is essential that the roles of PF and PNF are
clearly defined and understood. Efficient task sharing is crucial as procedures
are lengthy and the approach briefing may be extensive.
As there are many tasks to complete, clear priorities must be established. If
sufficient fuel remains, take time to plan carefully and brief fully. While there is no
need to remember the following details, an understanding of the structure of the
hydraulic and flight control systems would be an advantage. The F/CTL SD page
and the OPS DATA section of the QRH provide an overview of the flight controls
affected by the loss of hydraulic systems.
h a n g e Vi
e
The following summarises the condition of the aircraft following the possible
combinations of double hydraulic failure:
With a HYD B + Y failure, the stabiliser and most of the spoilers are lost.
There will be no NWS, as the landing gear will have been extended using
the gravity system (to protect the green system integrity for the flight
controls). Due to the loss of the stabiliser and the partial loss of spoilers,
VLS is increased by 10 kt. However, the elevators still operate normally
and autotrim is still available through the elevator. Normal braking is
available on the ground.
With a HYD G + B failure, the slats, most spoilers, the left elevator, the
inner ailerons, normal and alternate braking, anti-skid and (A333/A343:
NWS) are all lost. Braking is only available using the blue system
accumulator. If this failure occurs before any slat has been selected, a
long runway will be required. After stopping, the parking brake may be
inoperative due to low blue system accumulator pressure.
With a HYD G + Y failure, the flaps, most spoilers, the right elevator, outer
ailerons, normal braking and NWS are lost. Again, if this failure occurs
before any flap has been selected, a long runway will be needed. Braking
is available using the alternate braking system with anti-skid.
The PNF should note the calculated VAPP speed and landing distance. The
table in the QRH gives increments for different slat/flap configurations and it is
essential the correct figures are used.
The approach briefing should concentrate on safety issues, with emphasis on
the following:
When the gear will be selected down, noting that it will be a gravity
extension, regardless of the failure. Gear retraction will not be possible.
Approach configuration and Flap Lever position.
Use of selected speeds on the FCU.
Landing, braking and steering considerations.
Go-around calls, configuration and speeds.
Although the ECAM procedure guides the crew through the steps, the workload
is high. Attention must be given to the selected speeds on the FCU. The landing
is manually flown to Cat 1 limits only.
to
bu
y
.d o
.c
Hydraulic
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.70.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
8.80.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Landing Gear
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
LANDING WITH NON-NORMAL GEAR

This situation might occur following completion of a L/G GEAR NOT
DOWNLOCKED procedure. It is always better to land with any available gear
rather than carry out a landing without any gear. The exception to this is the
A343, when it is prohibited to extend the centre gear with one MLG not fully
extended as it was not designed to support the aircraft weight in the case of
main landing gear abnormal configuration. In all cases, reduce weight as much
as possible to provide the slowest possible touchdown speed. Although foaming
of the runway is not a requirement, take full advantage of any ATC offer to do so.
Inform the passengers and cabin crew of the situation in good time. This allows
the cabin crew to prepare the cabin and perform their emergency landing and
evacuation preparation.
In order to retain as much roll authority as possible, do not arm the ground
spoilers since ground spoiler extension would prevent the spoilers from acting as
roll surfaces. Use manual braking as it enables better pitch and roll control.
Autobrake is not armed, and is inhibited if any main landing gear is not fully
extended. The reference speed used by the antiskid system is not correctly
initialised if one main landing gear is not fully extended. Consequently, switch off
the antiskid system to prevent permanent brake release. Since engine contact
with the ground is likely during the rollout, and in order to prevent ground spoiler
extension, do not use reverse thrust.
In all cases, fly a normal approach and use the control surfaces as required to
maintain wings level and a normal pitch attitude for as long as possible after
touchdown. Try to prevent nacelle contact on first touchdown. Shut down the
engines early enough to ensure that fuel is cut off prior to nacelle touchdown, but
late enough to ensure that hydraulic power remains available for the flight
controls. Under normal load, hydraulic power remains available for
approximately 30 seconds after shutdown of the related engine.
Carry out the passenger evacuation checklist if required.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
8.90.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Navigation
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
FMGC FAILURE
Should a single FMGC failure occur, the AP/FD on the affected side will
disconnect. It is possible to restore the AP/FD using the other FMGC. The
A/THR remains engaged. Furthermore, flight plan information on the ND and
MCDU can be recovered by using the FM switching to establish FMGC SINGLE
MODE operation. Consider a FMGC reset as detailed in the QRH.
Should a double FMGC failure occur, depending on the specific failure, flight
management, flight guidance and flight envelope computers may be lost. The
AP/FD and A/THR will disconnect. It is possible to restore AP/FD and A/THR
provided a flight guidance computer is available.
Without AP/FD and A/THR, deselect the FD pbs. Select TRK/FPA to allow the
FPV and blue track index to be displayed. Move the thrust levers to recover
manual thrust, select NAV B/UP on the MCDU MENU page to establish backup
navigation and use the RMPs to tune the navigation aids. Refer to the QRH for
computer reset considerations. If a reset is successful, procedures are available
to reload both FMGCs. FCOM 4.06.20 refers.
Following a double FMGC failure, consider the RNP requirements.
IRS/ADR FAILURES
Each ADIRS has two parts, ADR and IRS, that may fail independently of each
other. Additionally the IRS part may fail totally or may be available in ATT mode.
Single ADR or IRS failures are simple procedures and only require action on the
switching panel as indicated by the ECAM.
Dual IRS or ADR failures cause the loss of A/P and A/THR. and flight controls
revert to ALTN law. Triple IRS or ADR failure is very unlikely and is not displayed
on the ECAM. Should a triple failure occur, two double failures would be
displayed, i.e. ADR 1 + 2 FAULT and ADR 2 + 3 FAULT. The subsequent ECAM
actions would give conflicting instructions. In this case, apply the QRH procedure
for ADR 1 + 2 + 3 failure. This is one of the few cases where the crew will not
follow the ECAM procedure.
There is no procedure for IRS 1 + 2 + 3 failure but the ECAM status page gives
approach procedure and inoperative systems. The standby instruments are the
only attitude, altitude, speed and heading references available.
h a n g e Vi
e
DUAL RADIO ALTIMETER FAILURE

The radio altimeters (RAs) provide inputs to a number of systems, including the
GPWS and FWC for auto-callouts. They also supply information to the AP and
A/THR modes, plus inputs to switch control laws at various stages. Although the
ECAM procedure for a RA 1 + 2 FAULT is straightforward, the consequences of
the failure on the aircraft operation require consideration.
Instead of using RA information, the flight control system uses inputs from the
LGCIU to determine mode switching. Consequently, mode switching is as
follows:
At take-off, normal law becomes active when the MLG is no longer

compressed and pitch attitude becomes greater than 8
On approach, the flare law becomes active in manual flight when the L/G is
extended. If the AP is engaged when the L/G is extended, flare law becomes
active at AP disconnect. As and when flare law activates, manual pitch trim is
required and USE MAN PITCH TRIM is displayed on the PFD.
After landing, ground law becomes active when the MLG is compressed
and the pitch attitude becomes less than 2.5
It is not possible to capture the ILS using the APPR pb and the approach must
be flown to CAT 1 limits only. However, it is possible to capture the localiser
using the LOC pb. Since the autopilot gains are no longer updated by signals
from the radio altimeter, the AP/FD behaviour may be unreliable near the
ground. Consequently, the final stages of the approach should be flown using
raw data in order to avoid excessive roll rates with LOC still engaged. There are
no auto-callouts on approach and no "RETARD" call in the flare.
The GPWS/EGPWS will be inoperative. Therefore increased terrain awareness
is necessary. Similarly, the "SPEED, SPEED, SPEED" low energy warning is
also inoperative, again requiring increased awareness.
to
bu
y
.d o
.c
Navigation
c u -tr a c k
A330/A340
FCTM
REV 2 (25 JUL 06)

.d o
lic
lic
8.90.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
ALL ENGINE FLAMEOUT

Following an All Engine Flameout, the flight deck indications change significantly
as the generators drop off-line. The RAT is deployed, the EMER ELEC CONFIG
warning is inhibited and the ECAM prioritises the checklists. Control of the
aircraft must be taken immediately by the left seat pilot and a safe flight path
established. Significant aircraft systems available include:
EMER GEN Powered by the RAT
FLY
PFD 1, ALTN LAW, Upper ECAM, ECP, ISIS/STBY INST
NAV
FCU, STBY NAV (via RMP 1), DDRMI (VOR 1 or ADF 1)
COMM
lic
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
8.100.1
REV 1 (6
JUN 05)
w
w
.d o
A330/A340
FCTM
Power Plant
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
VHF 1, RMP 1, ACP 1 & 2, Loudspeakers 1 & 2
The AP, pitch trim and rudder trim are not available. If engine windmilling is
sufficient, additional hydraulic power may be recovered from the EDP supplying
the emergency generator, which improves the electrical configuration.
Depending on the exact situation, assistance may be available from ATC
regarding information such as presence of other aircraft and safe headings. In
this case and when convenient, make contact using VHF 1.
ECAM does not distinguish whether fuel is available or not, and therefore
provides a procedure which covers all cases. Furthermore, the ECAM procedure
refers to the QRH for OPERATING SPEEDS and L/G GRAVITY EXTENSION.
Consequently, apply either the ALL ENG FLAME OUT FUEL REMAINING or
ALL ENG FLAME OUT NO FUEL REMAINING paper procedure in the QRH
which are optimised for each case and include any required ancilliary paper
procedures e.g. L/G GRAVITY EXTENSION. On completion of the QRH
procedure and if time permits, clear the ECAM warning and read the ECAM
STATUS page.
Commence the procedure with attention to the optimum relight speed without
starter assist which is initially (A333/A343: 300 kt/.82M) (A346: 270 kt). If there is
no relight within 30 seconds, the QRH/ECAM orders engine master off for 30
seconds and then on again. This is to permit ventilation of the combustion
chamber. Without starter assist, all engine master switches may be selected on
at the same time.
Start the APU below FL 250. Below FL 200, attempt an engine relight using APU
bleed for starter assist. When using APU bleed for starter assist, only one engine
must be started at a time. The optimum speed for starter assist is green dot,
which is not displayed on the PFD. Consequently, use the optimum speed with
APU bleed available from the checklist until the QRH Part 4 can be consulted to
accurately determine green dot speed.
h a n g e Vi
e
TAIL PIPE FIRE

An engine tail pipe fire typically occurs at engine start and results from excess
fuel in the combustion chamber or an oil leak in the low-pressure turbine race. A
tail pipe fire is an internal fire contained within the engine where no sensitive
areas are affected.
Should a tail pipe fire be reported, apply the checklist procedure, which requires
the engine to be shut down and ventilated.
The FIRE pb must not be pushed as this would de-energise the FADECs and
prevent the motoring sequence. The AGENT pbs must not be pushed as they
provide no benefit with extinguishing an internal fire. The priority must be given
to engine ventilation.
If a tail pipe fire is reported with no bleed air readily available, a ground fire
extinguisher should be used as last resort.
FCOM 3.02 70 refers
to
bu
y
.d o
.c
Power Plant
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.100.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
8.110.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Miscellaneous
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
OVERWEIGHT LANDING
Should an overweight landing be required, a long straight in approach, or a wide
visual pattern, should be flown in order to configure the aircraft for a stabilised
approach. Plan to be at VAPP by the final approach fix.
There are no adverse handling characteristics associated with overweight
landings. Landing distance with CONF 3 or FULL at all gross weights is normally
less than take-off distance. However, verify runway field length requirements
from the landing distance charts in the QRH or FCOM 2. Tyre deflation may
occur if brake temperatures exceed 800C.
Automatic landing has been demonstrated up to the weights specified in FCOM
3.01.32. CONF FULL is the preferred landing configuration provided that the
approach climb gradient criteria can be achieved using CONF 3 for the
go-around. At high weights and temperatures, a CONF 3 approach is required to
satisfy go-around criteria (QRH Maximum Weight For Go-Around in CONF 3
table refers). In all cases, if the landing configuration is different from CONF
FULL, select Flaps 1 (CONF 1+F) at initiation of the go-around. The approach
climb gradient criteria is never limiting in CONF 1+F. To ensure that maximum
thrust is available in the event of a go-around, select the packs off, or use the
APU as the bleed source.
If a go-around is performed using CONF 1+F, VLS CONF 1+F may be higher
than VLS CONF 3 + 5 kt (VAPP). In this case, follow the SRS order, which will
accelerate the aircraft up to the displayed VLS. VLS CONF 1+F equates to 1.23
VS1g whereas the minimum speed for go-around required by regulation is
1.13VS1g. Consequently, this requirement is always satisfied.
A normal approach is flown except that in the final stages of the approach, the
target speed is VLS and the max V/S at touchdown is 360 ft/min. At main gear
touchdown, select max reverse and after nosewheel touchdown, apply brakes if
autobrake is not active.
Use the longest available runway and consider wind and slope effects. Where
possible avoid landing in tailwinds, on runways with negative slope, or on
runways with less than normal braking conditions. Do not carry excess airspeed
on final approach. This is especially important when landing during an engine
inoperative or other non-normal condition.
At high weight, the manoeuvring speed for the current configuration may be
close to, or even above the VFE for the next configuration. In this case, the
procedure is to select the speed to VFE next - 5 kt (but not below VLS) and then
select the next configuration as the speed decreases through VFE next. As the
slats/flaps extend, VLS reduces. Flap load RELIEF may annunciate momentarily
as the speed reduces. Repeat if required, until the landing configuration is
achieved. Once completed, select managed speed. The flare and derotation
technique as described in FCTM Ch 7 applies.
h a n g e Vi
e
Taking into account the runway landing distance available, modulate the use of
brakes to avoid very hot brakes and the risk of tyre deflation. In general for
A333/A343, brake energy and tyre speed considerations are not limiting even in
an overweight condition.
EMERGENCY DESCENT
Initiate the emergency descent only upon positive confirmation that cabin altitude
and rate of climb is excessive and uncontrollable. Carry out this procedure from
memory. The use of AP and A/THR is strongly recommended for an emergency
descent. The FCU selections for an emergency descent progress from right to
left, starting with ALT, HDG and then SPD.
At high flight levels, extend the speed brake slowly while monitoring VLS to avoid
the activation of angle of attack protection This would cause the speedbrakes to
retract and may also result in AP disconnection. If structural damage is
suspected, caution must be used when using speedbrakes to avoid further
airframe stress. When the aircraft is established in the descent, the PF requests
the ECAM actions.
When at idle thrust, at high speed and with speedbrake extended, the rate of
descent is approximately 6000 ft/min. It takes approximately 5 minutes and 40
nm to descend from FL400 down to FL100. The MORA value displayed on the
ND is the highest MORA value within a circle of 40 nm radius around the aircraft.
The passenger oxygen MASK MAN ON pb should be pressed only when it is
clear that cabin altitude will exceed 14000 ft.
UNRELIABLE AIRSPEED INDICATIONS

Unreliable airspeed indications can result from blocked or frozen lines in the
pitot/static system.
Most failure modes of the airspeed/altitude system are detected by the ADIRS
and lead to the loss of the corresponding cockpit indication(s) and the triggering
of associated ECAM procedures. The fault sensing logic relies on a voting
principle whereby if one source diverges from the average value, it is
automatically rejected and the system continues to operate normally with the
remaining two sources. This principle applies to flight controls and flight
guidance systems.
However, there may be some cases where the airspeed or altitude output is
erroneous without being recognised as such by the ADIRS. In these cases, the
cockpit indications appear normal but are actually false and pilots must rely on
their basic flying skills to identify the faulty source and take the required
corrective action. When only one source provides erroneous data, a simple
crosscheck of the parameters generated by the three ADRs allows the faulty
ADR to be identified. This identification becomes more difficult in extreme
situations when two or all three ADR sources provide erroneous information.
to
bu
y
.d o
.c
Miscellaneous
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.110.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Normally, each PRIM receives speed information from each ADIRU and
compares the three values. Pressure altitude information is not used by the
PRIM. Each FE computer receives both speed and pressure information from
each ADIRU and compares the three values.
In a failure situation, various combinations of ADR faults may occur, each
interpreted differently by the PRIM and FE computers:
One ADR output is erroneous and the two remaining ADRs are
correct. The PRIMs and the FEs reject the faulty ADR. On basic
A333/A343 aircraft, there is no ECAM alert, however one PFD will display
some incorrect parameters. On the A346 and enhanced A333 aircraft, if
one ADR output is erroneous, and if this ADR is used to display the speed
information on either PFD, a NAV IAS DISCREPANCY caution is
triggered. In all cases, CAT3 DUAL will be displayed as an INOP SYS on
the STATUS page.
Two ADR outputs are erroneous but different and the remaining ADR
is correct, or if all three ADR outputs are erroneous but different. The
AP and A/THR will disconnect. If the disagreement lasts for more than 10
seconds, the PRIM triggers the NAV ADR DISAGREE ECAM caution.
Flight controls revert to ALTN 2 law. The SPD LIM flag is displayed on
both PFDs, however VLS and VSW are not displayed. This condition is
latched until a PRIM reset is performed on ground without any hydraulic
pressure. However, if the disagreement was transient, the AP and A/THR
can be re-engaged when the NAV ADR DISAGREE message has
disappeared.
One ADR is correct but the other two ADRs provide the same
erroneous output, or if all three ADRs provide consistent and
erroneous data. The PRIMs and FEs will reject the good outlier ADR
and will continue to operate normally using the two consistent but faulty
ADRs.
Any erroneous speed/altitude indication will always be associated with one or

more of the following cues:
lic
8.110.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Miscellaneous
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Fluctuations in airspeed indications

Abnormal correlation of basic flight parameters (IAS, pitch, attitude, thrust,
climb rate); e.g IAS increasing with large nose-up pitch attitude, IAS
decreasing with large nose down pitch attitude, IAS decreasing, with nose
down pitch attitude and aircraft descending
Abnormal AP/FD/A/THR behavior
Stall or overspeed warnings
Reduction in aerodynamic noise, with increasing IAS
Increase in aerodynamic noise, with decreasing IAS
h a n g e Vi
e
The ADRs provide a number of outputs to many systems and a blockage of the
pitot and/or static systems may also lead to the following:
SPD LIM flag on PFD

Alpha floor activation (because AOA outputs from the sensors are
corrected by speed inputs)
Wind shear warning (due to Mach input)
Flap load-relief activation
Flap auto-retraction from 1+F to 1
Alpha lock on slats retraction (due to the speed logic part of the alpha lock
function)
ALTI DISCREPANCY on ECAM
RUD TRV LIM FAULT ON on ECAM
Always apply the ECAM procedure. If the failure is not annunciated on ECAM,
crosscheck all IAS/ALTITUDE sources (ADR 1, 2, & 3, and ISIS/STBY INST).
Early recognition of erroneous airspeed indications requires some familiarity with
the relationship between attitude, thrust setting and airspeed. If it is positively
confirmed that the outlier ADR is at fault and that the other two ADRs are
correct, select the faulty ADR OFF. This action will generate an ECAM
procedure, which should be applied in order to reconfigure the PFD to display
correct information.
However, in very extreme circumstances, two or all three ADRs may provide
identical but erroneous data. If there is any doubt, then do not instinctively reject
the outlier ADR, although the temptation may exist if the other two ADR outputs
are consistent. In most cases, this decision would be correct, but not in the case
where two speed/altitude indications are consistent but wrong. Apply the initial
actions of the UNRELIABLE SPEED INDICATION QRH procedure from memory
as they quickly provide a safe flight condition in all phases of flight and aircraft
configuration. Rely on the primary flight parameters of pitch attitude and thrust
setting.
Because the displayed information may be erroneous, the flying accuracy cannot
be assumed. Incorrect transponder altitude reporting could cause confusion.
Therefore, declare a MAYDAY to advise ATC and other aircraft of the situation.
Reference to the QRH should only be made when a safe flight path has been
established. The QRH provides pitch attitude and thrust settings for each flight
phase and for different weights.
After applying the QRH procedure, and when the aircraft flight path is stabilised,
attempt to identify the faulty ADR(s). Once the faulty ADR(s) has/have been
positively identified, it/they should be switched OFF. This will trigger the
corresponding ECAM procedure, which should be applied.
to
bu
y
.d o
.c
Miscellaneous
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
8.110.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Depending of the cause of the failure, the altitude indication may also be
unreliable. However, there are a number of correct indications available to the
crew:
Unreliable Parameter
Altitude
Speed
Disregard
lic
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
8.110.5
REV 1 (6
JUN 05)
w
w
.d o
A330/A340
FCTM
Miscellaneous
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Use
Altimeter
IAS/TAS
Wind
V/S
FPA
GPS altitude
(on GPS monitor page)
IAS/TAS
Wind
GPS GS
(on GPS monitor page)
RA (low level)
When flying the aircraft with unreliable speed and/or altitude indications, it is
recommended to change only one flying parameter at a time; e.g. speed, altitude
or configuration. Consequently, plan to be at VAPP by the final approach fix.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
h a n g e Vi
e
9.00.1
k
.d o
REV 1 (6
w JUN 05)c
A330/A340
FCTM
lic
COMMS & NAV

Table Of Contents
o
c
to
bu
N
y
bu
to
k
lic
C
c u -tr
.
ack
.d o
XC
er
O
W
F-
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
TABLE OF CONTENTS
COMMS & NAV
General
Preface ..........................................................................................................9.10.1
RMP And ACP

Radio Management Panel (RMP) .................................................................9.20.1
Audio Control Panel (ACP)............................................................................9.20.1
ACARS
AIRINC Communication Addressing And Reporting System (ACARS) ........9.30.1
SATCOM
Satellite Communication (SATCOM).............................................................9.40.1
Air To Ground Communication......................................................................9.40.1
Ground To Air Communication......................................................................9.40.2
Hold Function ................................................................................................9.40.2
Call Termination ............................................................................................9.40.3
ATSU And CPDLC

Air Traffic Service Unit (ATSU)......................................................................9.50.1
Controller/Pilot Datalink Communication (CPDLC) .......................................9.50.6
WGS 84
World Geodetic Survey 1984 (WGS 84) .......................................................9.60.1
Honeywell ID Conventions
Un-named Oceanic Control Area Reporting Points.......................................9.70.1
Un-named Terminal Area Fixes ....................................................................9.70.2
Fixes With One Word Names........................................................................9.70.2
Fixes With Multi-word Names........................................................................9.70.3
h a n g e Vi
e
N
y
TCAS
Traffic Alert And Collision Avoidance System (TCAS) ..................................9.80.1
RNP
RNP...............................................................................................................9.90.1
RNP Capability ..............................................................................................9.90.1
Radial Equivalence........................................................................................9.90.2
k
lic
.d o
COMMS & NAV

Table Of Contents
to
bu
m
A330/A340
FCTM
05)
lic
9.00.2
wREV 1 (6 .JUN
c
.d o
c u -tr a c k
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.10.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

General
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PREFACE
This chapter discusses various communication systems, including SATCOM and
CPDLC, the monitoring of navigation accuracy, RNP criteria, the Honeywell
Naming Convention and TCAS displays. Some techniques related to equipment
handling are described in detail, whereas other information is intended to provide
a background working knowledge of the operation and philosophy of various
systems.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
RADIO MANAGEMENT PANEL (RMP)

The RMP is used to tune all VHF and HF radios as well as allowing manual
tuning of ILS, VOR and ADF frequencies. There is a detailed description of the
RMP and its functions in FCOM 1.23. The onside RMP should normally be used
to tune any one of the VHF or HF desired radios.
If tuning the radio results in the illumination of the SEL lights, the onside VHF
should be reselected. This will extinguish the SEL lights. The SEL light should
not remain illuminated for longer than is necessary to select the new frequency
or to set up the next expected frequency in the standby window.
The SEL light will come on both RMPs if:
VHF1 is selected on RMP2 or 3

VHF2 is selected on RMP1 or 3
VHF3, HF1, HF2 is selected on RMP1 or 2
AUDIO CONTROL PANEL (ACP)

The ACP allows the control of the transmission and reception of all
communication equipment as well as allowing aural identification of navigation
aids. FCOM 1.23.20 refers. On some aircraft, the ACP allows transmission and
reception of SATCOM calls.
The normal settings for ACP 1 and 2 are:
lic
9.20.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

RMP And ACP
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
VHF1/VHF 2/INT reception knobs "up" and set to 12 o' clock position
MKR reception knob "up" and set to 9 o' clock position
INT/RAD switch in the central position. When using headsets, select the
INT/RAD switch to INT
VOICE to "OFF"
Do not use VHF3 for voice communications if ACARS is installed unless VHF1
and VHF2 are inoperative.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.30.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ACARS
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
AIRINC COMMUNICATION ADDRESSING AND REPORTING

SYSTEM (ACARS)
ACARS enables communication between the aircraft and ground stations without
the direct involvement of the crew. The system is used in the delivery of
operational information, e.g. Loadsheets and RTOW data. It also provides a
timely and accurate means of disseminating information on the flight status.
Consequently, the ACARS should be initialised before each sector. FCOM
1.23.40 refers.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.40.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

SATCOM
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
SATELLITE COMMUNICATION (SATCOM)

This section details how to use the different cockpit SATCOM functions for air to
ground or ground to air communication. The examples below illustrate typical
scenarios. However, the menus shown do not necessarily reflect those found in
CX system specification. FCOM 1.23.45 refers.
AIR TO GROUND COMMUNICATION

The crew selects the phone number via the MCDU, then initiates and terminates
the call via the ACP.
Phone Number Selection
PRESS the SAT key on the MCDU main page.

To access the SATCOM MAIN MENU page.
PRESS the DIRECTORY key.

For air to ground communication, the Directory contains a list of pre-recorded
phone numbers.
Pre-recorded (Pre-stored) Phone Number

On the SATCOM DIRECTORY page:
PRESS 1L, 2L, 3L or 4L

The MCDU switches to the CATEGORY NUMBER page, where phone
numbers have been stored according to their priority, (e.g. SATCOM
SAFETY):
PRESS 1R to modify the SATCOM channel.

After having entered the desired SATCOM channel in the scratchpad.
PRESS the key (1L, 2L, 3L, 4L or 5L) facing the required phone number.
The MCDU then switches automatically to the SATCOM MAIN MENU page
where the title (of the selected phone number) is displayed. READY TO
CONNECT is displayed in front of the selected SATCOM channel.
h a n g e Vi
e
Call Initiation
Once all information regarding the phone number is entered in the MCDU, the
crew uses the ACP to initiate the SATCOM call. On the SATCOM MAIN MENU
page:
CHECK 2L or 4L field displays the phone number.
PRESS the SAT 1(2) transmission key.

On the ACP, PRESS the SAT transmission key corresponding to the selected
SATCOM channel. The green lines on the SAT 1(2) transmission key flash.
On the SATCOM MAIN MENU page, the DIALING indication replaces the
READY TO CONNECT indication in front of SAT 1(2). When the call is
established, the green lines on the SAT 1(2) transmission key become steady
on the ACP. On the SATCOM MAIN MENU page, CONNECTED indication
replaces the DIALING indication in front of SAT 1(2).
CHECK the availability of the relevant SATCOM channel.

The SATCOM channel, used to initiate the call, is displayed above the phone
number.
PROCEED as for a VHF or HF call. However, with SATCOM, the transmit button
may be held down throughout the call, with no affect on reception.
GROUND TO AIR COMMUNICATION

In case of an incoming call, the amber lines on the ACPs SAT 1(2) transmission
key flash and the SATCOM ALERT green memo is triggered on the ECAM,
when the priority level is below 4.
PRESS the SAT 1(2) transmission key to establish the communication

On the ACP, the green lines on the SAT 1(2) transmission key become
steady. On the SATCOM MAIN MENU page, the CONNECTED indication
replaces the DIALING indication in front of SAT 1(2).
HOLD FUNCTION
If the crew selects a radio for communication (HF or VHF) when a SATCOM call
is established, the SATCOM audio transmission is temporarily interrupted.
On the ACP:
The green lines on the SAT 1(2) transmission key flash. The green lines on the
selected radio (HF or VHF) transmission key come on. To recover the SATCOM
call reselect the same radio (HF or VHF) or the SAT 1(2) transmission key. This
terminates the radio call.
to
bu
y
.d o
.c
COMMS & NAV

SATCOM
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
9.40.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
CALL TERMINATION
For an air to ground call:
lic
9.40.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

SATCOM
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
PRESS the corresponding SAT 1(2) transmission key on the ACP.

The green lines on the selected SAT 1(2) transmission key go out.
After 3 seconds, the call is terminated.
If the SATCOM call is on HOLD, the crew must cancel the HOLD before
terminating the call.
For a ground to air call:

The ground initiates the call termination.
The green lines of the corresponding SAT1 (2) transmission key go out.
Do not select the PA immediately after a SATCOM call. This may result in the
PA being permanently selected. First select another system on the ACP, e.g.
VHF, and then the PA.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
AIR TRAFFIC SERVICE UNIT (ATSU)

Initialization
Successful datalink communications requires that all information is correctly
entered in accordance with the ICAO flight plan during ATSU initialisation. ATSU
is automatically initialised provided a list of service providers has been scanned
and provided the following parameters have been received and validated by the
ATSU:
Aircraft Registration Number (ARN)

Airline two letter Identification Code (A/L ID for datalink service providers)
Airline three letter Identification Code (A/L ID for ATC)
If one of the above conditions is not fulfilled, the ATSU or datalink is not available
and the following occurs:
lic
9.50.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
The ECAM displays an ATSU FAULT warning, with the ATSU INIT FAULT
line procedure
The MCDU scratchpad displays a message to request crew action
A manual entry of the missing parameter re-initialises the ATSU and clears the
ECAM and MCDU message.
h a n g e Vi
e
Notification
Notification is made through the NOTIFICATION page as follows:
The FMGC provides the ATC FLT number. The notification procedure is used by
the ATC to correlate the aircraft with the ICAO flight number. Consequently, it is
essential to enter exactly the same number, shown on the ICAO flight plan (with
the same number of letters), on the INIT page.
The ATC CENTRE field defaults to the centre that was connected during the
previous flight. It can be changed, if applicable.
Once the ATC centre has been notified, "NOTIFIED" is displayed on the
NOTIFICATION page. The ATC centre will then initiate the CPDLC and/or
Automatic Dependent Surveillance (ADS) connection. Therefore, re-notifications
should be avoided.
For ADS operations, check on the CONNECTION STATUS page that the ADS is
set to ON prior to performing a notification.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.50.5
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Connection
Before connection, the DCDU screen appears as below:
Once notified, the connection is made at the ATC's discretion. When the
connection is established in a CPDLC or CPDLC/ADS environment, the active
centre is displayed on the DCDU and the pilot should verify that the appropriate
centre is connected.
For operations in an ADS only environment (i.e. no CPDLC), "NO ACTIVE ATC"
remains displayed on the DCDU and does not reflect the ADS contract status.
This is due to the fact that the DCDU is the interface that sustains CPDLC
communication, whereas the ADS is an additional feature which is transparent to
the crew.
h a n g e Vi
e
CONTROLLER/PILOT DATALINK COMMUNICATION (CPDLC)

This section gives only a few typical examples of the messages that are
exchanged between the crew and ATC. To avoid ambiguity, the following is
recommended:
Avoid sending multiple clearance requests in the same message

Avoid duplicating messages. Consequently:
Answer incoming messages as soon as possible
Do not re-send your message if ATC does not answer immediately.
If, after a reasonable period of time, you feel it is necessary to

re-send a message, e.g. a clearance request, do not re-send the
same request. Use a negotiation query, such as "WHEN CAN WE..."
Close messages when they have been answered or sent to keep the
screen free for additional messages
Avoid using free text. If it is necessary to use free text because
pre-formatted messages do not allow for a specific message element, use
standard ATC phraseology
Avoid non-standard abbreviations
Position Reports
As for voice communications, a position report is required when passing a
waypoint. This is entirely automatic when the ADS function is active. In other
cases, or if manual reports are required in addition to ADS reports, the pilot must
send position reports by using the DCDU. Position report messages can either
be:
Automatically generated on the DCDU by the FMGS, if the AUTO POS

REPORT function has been set to on
Manually prepared by the pilot on the ATC REPORTS page
For the ADS function, or the automatic generation of position reports on
the DCDU by the FMGS, it is essential to ensure correct waypoint
sequencing. The FMGS offset function should be used, when appropriate.
When the heading mode is used, the crew should monitor the waypoint
sequencing and clear them when necessary.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.50.7
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
FMGS Generated Position Reports
When sequencing a waypoint, the FMGS automatically generates the position

report message on the DCDU:
The pilot may modify it by using the MODIFY function key. Then, he sends it to
the ATC. He may also use the MODIFY function key to update the parameters
displayed on the DCDU before sending the position report.
Carry out the following actions on the DCDU:
SEND..............................................................................................SELECT (1)
The message is displayed in green letter and the OPEN status disappears.
CLOSE ...........................................................................................SELECT (2)

The message is removed from the screen.
h a n g e Vi
e
Pilot Generated Position Reports

This has to be done when the AUTO POS REPORT on the ATC REPORTS
page is set to OFF. The POSITION REPORT message must be prepared on the
MCDU.
Complete the following actions on the ATC REPORTS PAGE:
MANUAL POSITION REPORT ......................................................SELECT (1)

POSITION REPORTS pages 1/3, 2/3 and 3/3 show the data that is
automatically provided by the FMGS. The crew can manually enter some
fields, if desired.
REP DISPL.....................................................................................SELECT (2)

This message is displayed on the DCDU with a blue background. It is now
ready to be sent.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.8
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.50.9
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
As for reports that are automatically generated by the FMGS, the pilot can
modify a message displayed on the DCDU. It is then sent to the ATC by using
the SEND function key and is removed from the screen by using the CLOSE
function key.
h a n g e Vi
e
Crew Request To ATC

In this example, the crew makes a request when a lateral flight plan deviation is
desired due to weather reasons. The use of the "WX DEV UP TO" prompt
ensures that the ATC attributes priority to this request. The following actions
should be carried out:
On the ATC MENU PAGE:
LAT REQ ........................................................................................SELECT (1)

The ATC LAT REQ page is displayed.
Fill the WX DEV UP TO field (2)

REQ DISPL ....................................................................................SELECT (3)
The request is displayed on the DCDU with a blue background. It is ready to
be sent.
On the DCDU:
SEND..............................................................................................SELECT (4)
The message is displayed on a green background.
CLOSE ...........................................................................................SELECT (5)

The message and its status are removed from the screen.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.10
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.50.11
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Clearances From ATC And Pilot Responses

Immediate Clearance
In this example, an ATC message is received in response to the previous
request for weather deviation.
The ATSU triggers visual (ATC MSG light) and aural alerts and displays the
message on the screen in white and blue letters. The message status is OPEN
and in blue.
h a n g e Vi
e
ATC MSG ..............................................................................................PRESS

This will turn off the light and stop aural alert.
On the DCDU:
WILCO............................................................................................SELECT (1)
The message status becomes WILCO, on a blue background. (2)
SEND..............................................................................................SELECT (3)
The message is displayed in green letters, and the WILCO status is on a
green background. (4)
CLOSE ...........................................................................................SELECT (5)

The crew has to insert the offset in the FMGS flight plan.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.12
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Deferred Clearance
In this example, ATC have given a clearance to climb at a specific point. The
ATSU triggers visual (ATC MSG light) and aural alerts and displays the message
on the DCDU screen in white and blue letters. The message status is OPEN and
in blue.
lic
9.50.13
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
ATC MSG ..............................................................................................PRESS

This will turn off the light and stop the aural alert.
On the DCDU:
WILCO .................................................................................................SELECT
The message status becomes WILCO, on a blue background.
On the DCDU, the waypoint to which clearance is deferred (DINTY) and
FL350, turn magenta. This indicates that they will be monitored by the
FMGC.
SEND ...................................................................................................SELECT
The message is displayed in green letters and the WILCO status is on a
green background.
CLOSE.................................................................................................SELECT
h a n g e Vi
e
About 30 seconds before DINTY the appropriate part of the message (related to
the first reached parameter) is automatically recalled by the FMGS.
"REMINDER" information and the absence of ATC centre identification indicates

that this is not a new incoming message but is only an FMGS recall. Flight plan
modification has to be done by the crew.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.14
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Navigation Parameter Request From ATC And Pilot Response

When ATC requests confirmation of a parameter, the ATSU triggers the ATC
MSG light and aural alerts and displays the message on the DCDU screen in
white letters. The message status is OPEN and in blue.
lic
9.50.15
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
ATC MSG ..............................................................................................PRESS

This will turn off the light and stop the aural alert.
Automatic answer from the FMGS:

The "WAIT FM DATA" information indicates that the FMGS is preparing an
answer. Then it displays it on the DCDU.
h a n g e Vi
e
On the DCDU:
SEND..............................................................................................SELECT (1)
The message is displayed in green letters.
CLOSE ...........................................................................................SELECT (2)

The message is removed from the screen.
Flight Plan Modifications

Flight plan modifications, sent by the AOC, can be loaded in the FMGS
secondary F-PLN. The crew can also manually prepare modifications. The crew
has to obtain ATC clearance prior to activation.
When the AOC SEC F- PLN UPLINK message is displayed on the scratchpad
(1):
On the SEC INDEX page:
INSERT* .........................................................................................SELECT (2)

The flight plan sent by the ADC is inserted in the secondary flight plan. The
crew can review it and, if necessary, modify it.
REQ DISPL* ...................................................................................SELECT (3)

The DCDU automatically prepares a message. The crew has to send it to
ATC and close it.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.16
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
When ATC clearance is received:
lic
9.50.17
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
ATC MSG ..............................................................................................PRESS

This will turn off the light and stop aural alert.
On the DCDU:
OTHER ...........................................................................................SELECT (1)
LOAD..............................................................................................SELECT (2)
LOAD must be selected at this point. Any other selection may prevent further
loading of the clearance. The "LOAD OK" information is displayed to confirm
that loading is successful. The clearance can be reviewed on the SEC FPLN pages.
h a n g e Vi
e
If the crew accepts the clearance:
OTHER ................................................................................................SELECT
WILCO .................................................................................................SELECT
This has to be sent and cleared, as for other WILCO answers.
The crew has to activate the secondary F- PLN.
If the crew wishes to modify the clearance:

The clearance should be loaded into SEC F-PLN, and then modified.
On the DCDU, the clearance should be rejected (UNABLE).
Another request (modified F-PLN) should be submitted to ATC.
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.18
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Emergency Messages
The following describes the procedure for a PAN message.
ON the ATC MENU PAGE:
EMERGENCY ................................................................................SELECT (1)

The EMERGENCY Page 1/2 is displayed.
PANPAN.........................................................................................SELECT (2)
The PANPAN prompt becomes blue.
Fill the DIVERTING/VIA field (3).

The VIA field defaults to the present position, if it is not manually entered.
Note:
1.
The emergency can be cancelled by using the CANCEL EMERGENCY
prompt on the EMERGENCY page 2/2 (4).
lic
9.50.19
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
EMERG DISPL ...............................................................................SELECT (5)

The message is displayed on the DCDU. The crew has to send it, then close
it, as is done with any downlink message.
h a n g e Vi
e
N
k
to
bu
y
.d o
.c
COMMS & NAV

ATSU And CPDLC
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.50.20
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.50.21
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

ATSU And CPDLC
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Automatic Transfer To Next ATC Authority

The current ATC centre sends the "NEXT DATA AUTHORITY" information
message. The crew only has to close it.
The current ATC centre sends the "END SERVICE" message. It may indicate
the frequency to be used for voice backup.
The crew has to answer "WILCO", as is done for other uplink messages.
When the message is closed, the new ATC centre is shown as active.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.60.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

WGS 84
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
WORLD GEODETIC SURVEY 1984 (WGS 84)

WGS 84 is the standard used for the accurate position reference used by the
GPS system. There are some differences between WGS 84 and the more
current geodetic survey systems but these differences are less than 2 cm. ICAO
recommends that positions of all navigation references are made with respect to
WGS 84 and, in most countries around the world, this recommendation has been
complied with. There are some states, however, where the conversion to WGS
84 has not been carried out, leading to the possibility of navigation inaccuracies.
Use Of GPS In Non-WGS84 Reference Datum Airspace

In non-WGS 84 airspace, the local datum (position basis) used to survey the
navigation data base position information may result in significant position errors
from a survey done using the WGS 84 datum. To the pilot, this means that the
position of runways, airports, waypoints, or navigation aids, may not be as
accurate as depicted on the map display and may not agree with the GPS
position. Crews should consult official sources, e.g. Jeppesen, to determine the
current status of airspace in which they operate.
A worldwide survey has been conducted which determined that using the FMGS
while receiving GPS position updating during enroute navigation, SIDS and
STARS achieve the required navigation accuracy, despite operating in non-WGS
84 airspace. However, this navigation position accuracy may not be adequate for
approaches. Therefore, the aircraft flight manual requires the crew to inhibit GPS
position updating while flying approaches in non-WGS 84 airspace "unless other
appropriate procedures are used."
Provided operational approval has been received and measures to ensure their
accuracy have been taken, RNAV approaches may be flown with GPS updating
enabled. Options available may include surveys of the published approaches to
determine if significant differences or position errors exist, developing special
RNAV procedures complying with WGS 84 or equivalent, or inhibiting GPS
updating.
For approaches based upon ground-based navigation aids such as ILS, VOR,
LOC or NDB, the GPS updating need not be inhibited, provided that appropriate
raw data is used as the primary navigation reference throughout the approach
and missed approach. Aircraft primary lateral and vertical navigation modes may
be used. Provided the FMGS is not used as the primary means of navigation for
approaches, this method can be used instead of inhibiting GPS updating.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
UN-NAMED OCEANIC CONTROL AREA REPORTING POINTS

Positions in the Northern Hemisphere use the letters "N" and "E", while positions
in the Southern Hemisphere use the letters "S" and "W". Latitude always
precedes longitude.
For longitude, only the last two digits of the three digit value are used.
Placement of the designator in the five character set indicates whether the first
longitude digit is 0 or 1. The letter is the last character if the longitude is less than
100 and is the third character if the longitude is 100 or greater. "N" is used for
north latitude, west longitude; "E" is used for north latitude, east longitude. "S" is
used for south latitude, east longitude. "W" is used for south latitude, west
longitude.
Examples:
N50 W040 becomes 5040N
N75 W170 becomes 75N70
N50 E020 becomes 5020E
N06 E110 becomes 06E10
S52 W075 becomes 5275W
S07 W120 becomes 07W20
S50 E020 becomes 5020S
S06 E110 becomes 06S10
lic
9.70.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
UN-NAMED TERMINAL AREA FIXES

DME ARC Procedures
Unnamed fixes along a DME arc procedure are identified by a five character
designation with the first character being "D".
Characters from two to four indicate the radial on which the fix lies. The last
character indicates the arc radius. The radius is expressed by a letter of the
alphabet where A = 1 mile, B = 2 miles, C = 3 miles and so forth.
Examples:
EPH 252/ 24 = D252X
EPH 145/ 24 = D145X
GEG 006/ 20 = D006T
An unnamed waypoint along a DME arc with a radius greater than 26 miles is
identified by the station identifier and the DME radius.
Examples:
CPR 338/29 = CPR29
GEG 079/30 = GEG30
FIXES WITH ONE WORD NAMES

Waypoints located at fixes with names containing five or fewer characters are
identified by the name.
Examples:
DOT, ACRA, ALPHA
Names with more than five characters are abbreviated using the following rules
sequentially until five characters remain:
Delete double letters

Keep the first letter, first vowel and last letter
Delete other vowels starting from right to left
Keep the last letter and then delete consonants from right to left
to
bu
y
.d o
.c
COMMS & NAV

c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.70.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Examples:
KIMMEL
becomes KIMEL
COTTON
becomes COTON
RABBITT
becomes RABIT
Examples:
ADOLPH
becomes ADLPH
BAILEY
becomes BAILY
BURWELL
becomes BURWL
Examples:
ANDREWS
becomes ANDRS
BRIDGEPORT becomes BRIDT

HORSBA
becomes HORSA
FIXES WITH MULTI-WORD NAMES

Use the first letter of the first word and abbreviate the last word using the above
rules sequentially until a total of five characters remain.
Examples:
CLEAR LAKE
lic
9.70.3
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
becomes CLAKE
ROUGH ROAD becomes RROAD
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
TRAFFIC ALERT AND COLLISION AVOIDANCE SYSTEM (TCAS)

Conflict Resolution
Traffic Advisory (RA)
If an intruder represents a potential collision threat, a visual and aural TRAFFIC
ADVISORY is given. This advisory aids the crew to acquire visually the intruder.
Also it prepares the crew for a possible RESOLUTION ADVISORY. However,
not every RA has to be preceded by a TA.
Resolution Advisory (RA)

If the intruder is considered as a real collision threat, an aural and visual
Resolution Advisory is given. The TCAS determines the optimum vertical
manoeuvre that ensures effective separation with the minimum change of
vertical speed. Depending on each situation, the TCAS will generate:
lic
9.80.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

TCAS
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Preventive advisory. The actual vertical speed may be maintained. A

range of vertical speed to avoid is displayed
Corrective advisory. The actual vertical speed is within the range to be
avoided and a range of recommended vertical speed (fly to) is displayed
Modified corrective advisory which changes RA already displayed, e.g. if
the intruder changes its vertical speed
Avoidance Generalities
Always follow the TCAS orders, even if they lead to crossing the altitude of the
intruders, as they ensure the best global separation. Failure to respond
immediately to TCAS orders may result in loss of separation from the intruder
aircraft. TCAS commands override ATC instructions.
For system description, FCOM 1.34.80 refers. For operational procedures,
FCOM 3.02.34 and the QRH refer.
h a n g e Vi
e
N
k
to
bu
y
.d o
.c
COMMS & NAV

TCAS
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.80.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
9.80.3
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

TCAS
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
bu
y
.d o
.c
COMMS & NAV

TCAS
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
9.80.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
RNP
General
Procedures, FCOM 3.04.34 refers.
The aircraft navigation systems required by regulation to fly within a Required
Navigation Performance (RNP) airspace shall comply with RNAV functionality
criteria and with navigation position accuracy and integrity criteria.
When referring to RNP-X, the value of X is the navigation accuracy expressed in
nautical miles, which has to be met with a probability of 95 %.
A RNP value can be associated with an airspace, route, SID, STAR, RNAV
approach or a RNAV missed approach procedure.
Depending on the RNP value and the airspace environment (availability of
ground-based radio navaids), different navigation equipment may be necessary.
RNP CAPABILITY
In order to achieve a given RNP criteria, the FMS estimated position accuracy
(also called Estimated Position Error) must be better than the associated RNP
value. This is dependent on the FMS navigation-updating mode (GPS,
DME/DME, VORDME, or IRS).
Both the required and the estimated position accuracy are displayed on the
MCDU PROG page, and their relationship determines the HIGH/LOW accuracy
indication (FCOM 1.22.20 refers).
The required accuracy can be either the default value, which is a function of the
phase of flight, or a value manually entered by the crew. In this case, when flying
in a RNP environment, the appropriate RNP value should be inserted in the
REQUIRED ACCUR field of the PROG page.
lic
9.90.1
O.I. (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
COMMS & NAV

RNP
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
When HIGH is displayed, the RNP criteria is achieved

When LOW is displayed, the RNP criteria is not achieved. In this case, use
raw data to crosscheck navigation (FCOM 3.04.34 refers). If raw data is
not available or the navigation check is negative, advise ATC.
When leaving the RNP environment, clear any manually entered RNP value.
h a n g e Vi
e
Without GPS PRIMARY

RNP accuracy criteria are met provided the radio navaid coverage supports it
for:
RNP-1 en route and in the terminal area provided a required accuracy of 1

nm* is manually entered in MCDU.
RNP-0.3 in the approach area provided a required accuracy of 0.3nm* is
manually entered in MCDU.
Note:
1.
*It is acceptable to enter the radial equivalent of the specified cross-track
(XTK) accuracy, which is the RNP value multiplied by 1.22.
With GPS PRIMARY

RNP accuracy criteria are met for:
RNP-1 en route
RNP-0.5 in the terminal area provided AP or FD in NAV mode is used
RNP-0.3 in the approach area provided AP or FD in NAV mode is used
RADIAL EQUIVALENCE
Aircraft fitted with legacy FMS, identified by the absence of the DCDUs on the
forward centre instrument panel, display the radial equivalent of the REQUIRED
(RNP) navigation performance on the PROG page.
For RNP requirements, the navigation position error is defined in terms of the
XTK/ATK error. The legacy FMS computes an estimated accuracy that is a radial
value (circle) around the estimated position and displays this equivalent value on
the PROG page. To obtain the radial equivalent of a XTK/ATK (RNP) value,
multiply the XTK/ATK by 1.22 as follows:
Radial equivalent = XTK/ATK (RNP) x 1.22
For example, if an airspace or procedure specified an RNP of 0.3 nm, legacy

FMS will display the radial equivalent value 0.37 nm on the PROG page (0.3 x
1.22), which equates to the specified RNP.
to
bu
y
.d o
.c
COMMS & NAV

RNP
c u -tr a c k
A330/A340
FCTM
O.I. (6 JUN 05)

.d o
lic
lic
9.90.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
10.00.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Table Of Contents
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
TABLE OF CONTENTS
Training Guide
General
Preface ........................................................................................................10.10.1
MEL
General........................................................................................................10.20.1
ATA 100 Format ..........................................................................................10.20.1
MEL Description ..........................................................................................10.20.1
MEL Operational Use ..................................................................................10.20.2
Briefing Guidelines
Briefing Procedure.......................................................................................10.30.1
C-TWO Acronym .........................................................................................10.30.1
Briefing Aide-memoire.................................................................................10.30.3
Expanded Two Briefing Items ...................................................................10.30.3
Briefing Examples .......................................................................................10.30.6
Sidestick
Sidestick Characteristics .............................................................................10.40.1
Operating Speeds
Characteristic Speeds .................................................................................10.50.1
Protection Speeds .......................................................................................10.50.3
Limit Speeds................................................................................................10.50.4
Other Speeds ..............................................................................................10.50.5
PFD/FMA Call Procedure

PFD/FMA Changes To Be Called ...............................................................10.60.1
Descent Management
Descent Profile Management ......................................................................10.70.1
h a n g e Vi
e
Touch And Go-around

General........................................................................................................10.80.1
Approach .....................................................................................................10.80.1
Landing .......................................................................................................10.80.1
to
bu
y
.d o
.c
Training Guide
Table Of Contents
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
10.00.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PREFACE
Chapter 10 provides additional data for initial training. The aim of the chapter is
to:
lic
10.10.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
General
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Describe use of the MEL

Define the requirements of Departure/Arrival Briefings
Discuss sidestick characteristics and characteristic speeds
Define FMA changes to be called
Assist the trainee to visualise cockpit flow patterns - to be issued later
Provide a basis for the handling of abnormal procedures - to be issued
later
Describe base training procedures
FAQ - to be issued later
This chapter is not a complete reference and should be read in conjunction with
FCTM Ch 2 to 9 and the FCOM.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
GENERAL
The Master Minimum Equipment List (MMEL) is published by the aircraft
manufacturer and is a certified document. It allows an aircraft to be dispatched
with some equipment or some functions inoperative. Some limitations,
operational procedures and/or maintenance procedures may have to be carried
out. The Minimum Equipment List (MEL) is published by CX and approved by
the CAD. It is necessarily at least as restrictive as the MMEL. The MMEL cannot
be used as an MEL.
The dispatch of an aircraft is possible with some secondary airframe part or parts
missing. In such a case, refer to the Configuration Deviation List (CDL) at the
rear of the MEL.
ATA 100 FORMAT

Each item/equipment listed in the MEL is identified using ATA (Air Transport
Association) format. It is the official reference for the classification of the aircraft
systems and/or functions. This is achieved using six digits. For example
21-52-01 refers to:
21: ATA 21: Air conditioning

52: Air cooling system
01: Air conditioning pack
MEL DESCRIPTION
The MEL consists of four parts:
ECAM warnings/ MEL entry

List of items that may be inoperative for dispatch
Associated operational procedures
Configuration Deviation List
lic
10.20.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
MEL
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
h a n g e Vi
e
MEL OPERATIONAL USE

The Commander is responsible for ensuring that the aircraft is in every way fit for
the intended flight. The MEL represents guidance to the Commander as to what
defective items might be reasonably left unrectified, without jeopardizing the
safety of the aircraft, when making his decision whether to operate the intended
flight.
If a failure occurs during the taxy phase before the start of the take-off roll, any
decision to continue the flight shall be subject to pilot judgement and good
airmanship. The Commander may refer to the MEL before making a decision to
continue the flight.
During the Flight Deck Check, press the RCL pb for at least 3 sec to recall any
previous cautions or warnings that have been cleared or cancelled. The Aircraft
Maintenance Logbook (AML) should then be consulted to confirm the indications
are compatible with the MEL.
MEL section 00E is titled ECAM warnings/MEL entry. The purpose of this section
is to help the crew determine the MEL entry point when an ECAM caution or
warning message is displayed. If a failed item is not mentioned in the MEL,
dispatch is not possible.
If the failed item is mentioned, dispatch is possible provided all dispatch
conditions are fulfilled:
Check the rectification time interval has not expired. Consider location
where repair is possible
(*) Means that an INOP placard is required
(O) Means a specific operational procedure or limitation is required. Refer
to MEL Chapter 2
(M) Means a specific maintenance procedure is required
When the MEL indicates a requirement for both maintenance and operational
procedures, maintenance procedures must be performed before applying the
operational procedures.
Some failures have operational consequences for LWMO and ETOPS. The
applicable MEL references are annotated "L" and "E" respectively. Although not
necessarily dispatch items, the effect of such failures must be taken into account
if they will have an operational effect on the intended sector.
to
bu
y
.d o
.c
Training Guide
MEL
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
10.20.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
BRIEFING PROCEDURE
The briefing should take place once the set up and cross-check of the Flight
Management System (FMS) is complete. For departure briefings there is no
requirement to wait for the loadsheet or take-off data to be entered into the FMS
before conducting the briefing. The following actions shall be completed before
the briefing commences:
FCOM procedures with the exception of loadsheet and/or take-off data

entry as mentioned above.
The FMS checked for accuracy against the CFP and the relevant
published procedures.
Navigation Aids set-up. Modifications to existing radio aid selections may
be required following an arrival briefing.
Any PNF questions about the set-up addressed. This can be achieved at
the time or during the briefing.
"Are you ready for the briefing?" is typically the question that commences the
briefing process. A positive answer from the PNF means that all required actions
have been completed and checked and that any anomalies have been raised by
the PNF.
C-TWO ACRONYM
Briefings will consist of 4 modules covered by the acronym "C-TWO":
lic
10.30.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Briefing Guidelines
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Chart
Terrain
Weather
Operational
Each module shall be discussed in every briefing. The "C" module identifies the
procedure to be flown. There is no need to discuss every detail of the published
procedure, as this will have been effectively 'self-briefed' during the data entry
and cross-checking phase. However, experience, recency, or training
requirements should be taken into consideration when deciding how much to
mention in this module.
h a n g e Vi
e
The "TWO" modules will consist of details that the PF considers relevant to the
particular departure/arrival to be flown. The PF should consider the intended
departure or arrival and incorporate relevant briefing points into an appropriate
module. The intent is to incorporate briefing points that generate thought and
awareness about the departure/arrival to be flown. A review of pertinent
procedures will usually be required in unusual circumstances. Examples include:
RTO with a thrust-reverser locked out.

Engine inoperative considerations when arriving with an engine
inoperative.
Missed approach considerations when arriving at an airport where there is
an increased chance of a missed approach being flown.
In the simplest case, at a familiar airfield with experienced crew and in good
weather, the modules can be covered with a "nil significant" statement with the
exception of the Terrain Module. This will always require the "Sector MSA plus
Highest MSA" as a minimum statement.
The PF should decide on what material is included in each of the modules. The
Commander shall ensure that all relevant details are covered. The intention of
the briefing is to generate thought provoking and relevant discussion.
Every Departure and Arrival must be viewed in the context of THREATS and
how best to overcome them. Threats must be identified and covered in the
briefing. An example would be when the Port Page identifies a known problem,
e.g. false LOC captures. In this case, the words "nil significant" are clearly
inadequate.
Prior to commencing the briefing, the PF conducts a cross-check of the flight
instruments. The F-PLN page should be selected before either the departure or
arrival briefing is commenced.
The C-TWO module is then initiated by confirming the planned runway, SID,
departure transition, STAR, arrival transition and type of approach, as applicable.
The briefing can be conducted prior to receipt of the clearance. In this case,
upon receipt of the clearance, the F-PLN page shall be reselected by the PF for
confirmation.
An EFIS check is then initiated. This is designed to capture correct settings of
the ND, navigation aids and FMA. The RADNAV page should not be referenced.
Any short-term navigation aid selections should have been discussed in the
C-TWO briefing under Operational.
to
bu
y
.d o
.c
Training Guide
Briefing Guidelines
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
10.30.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
Departure
to
.d o
c u -tr a c k
.c
Arrival
Chart
Runway
Name of SID / Departure Transition
lic
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
10.30.3
O.I. (30
JUL 04)
w
w
.d o
A330/A340
FCTM
Training Guide
Briefing Guidelines
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
Name of STAR/Transition
Approach Chart ID
Type of Approach/Runway
Final profile altitude check
Minimums
Missed Approach. Initial actions only
i.e. Tracking and Altitude
Navigation Aids for approach and
go-around
Terrain
Relevant Sector MSA and highest MSA
Weather
Relevant weather
Operational
Relevant Operational Considerations
Alternate
Relevant Fuel
BRIEFING AIDE-MEMOIRE
A briefing aide-memoire is available in card form. This details the minimum
briefing items required.
EXPANDED "TWO" BRIEFING ITEMS

Items to be included in the "C-TWO" modules will differ for each flight. Examples
of items that may be included in the modules are listed below. This list is not
exhaustive and the principle of including relevant, useful information should be
employed.
h a n g e Vi
e
Terrain
Consider the following:
Area Chart with emphasis on navigation aids to be used to enhance terrain

awareness
Minimum Vectoring Altitude Chart, if available
Airfield elevation, if significant
Low transition levels
Weather

Typhoons
Thunderstorms
Windshear
Turbulence
Rain/runway contamination
Use of wipers/rain-repellent
Icing
Hot weather
Cold weather
Altimetry
Low Visibility Procedures (LVP)
Wind/crosswind
to
bu
y
.d o
.c
Training Guide
Briefing Guidelines
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
10.30.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
Operational
Port page details

Speed control
Noise abatement requirements
LVP
Use of AP
Use of A/THR
Flight mode selection
Non-normal procedures
Engine inoperative procedures
Configuration
Crew duties
Holding
Runway characteristics
Landing weight
Autobrake/braking
Taxying requirements
Significant elements of the missed approach
Diversion plan and fuel requirements
Extra fuel available
to
.d o
lic
10.30.5
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Briefing Guidelines
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
BRIEFING EXAMPLES
Departure
BKK 21R, CAVOK (Experienced crew, current at BKK)
21R, Bruce 2 departure, Regos transition.

The sector and highest MSA is 2300 ft.
No weather or operational considerations.
Any questions?
BKK 21R, CB's to South, Outboard Reverser Inop, WIP Taxiway C
21R, Bruce 2 departure, Regos transition.

The sector and highest MSA is 2300 ft.
Weather avoidance will be required on departure with possible windshear
(discuss windshear actions). Cabin crew will not be released till clear of
weather.
Operationally - taxiway C is closed so we can expect routing on Bravo.

We have #4 thrust reverser inoperative in the event of a rejected T/O.
Any questions?
to
bu
y
.d o
.c
Training Guide
Briefing Guidelines
c u -tr a c k
A330/A340
FCTM
O.I. (30 JUL 04)

.d o
lic
lic
10.30.6
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
10.30.7
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Briefing Guidelines
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Arrival
HKG, 07L, CAVOK
Elato 1A arrival to ILS 07L, chart 11-1, check altitude of 1300 ft at 4.0
DME, IZSL, minimum 222 ft set (confirmed by PNF), missed approach is
initially runway heading, 5000 ft. Navigation aids initially NLG, TD then
SMT, TD.
The Sector and Highest MSA is 4300 ft.

Weather is not a factor.
No significant operational factors. Macau diversion with 30 minutes
holding.
Any questions?
HKG, 07L, thunderstorms and moderate rain, visibility 2000 m
Elato 1A arrival to ILS 07L, Chart 11-1, check altitude of 1300 ft at 4.0
DME, IZSL. Minimum 222 ft set (confirmed by PNF), required RVR 550
m. Missed approach is initially runway heading, altitude 5000 ft.
Navigation aids initially NLG, TD then SMT, TD.
Sector and Highest MSA 4300 ft, high ground south of the airport andin
close proximity to the arrival and missed approach procedure.
Weather avoidance and possible windshear / turbulence (discuss).

This will be an automatic landing. We may need wipers on finals. In the
event of a missed approach I will select TOGA (discuss all MAP
considerations). After landing I will be using max reverse. Shenzhen is
our alternate. We require 5.5 tonnes. We have 30 minutes of holding fuel.
Any questions?
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
10.40.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Sidestick
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
SIDESTICK CHARACTERISTICS
There is no physical interconnection between the sidesticks. Visual monitoring of
the other pilot's sidestick input is significantly reduced because of the sidestick
position.
With the AP engaged, the sidesticks are locked in the neutral position. This
provides a tactile feedback that the AP is engaged and also prevents
simultaneous inputs from the pilot and AP.
When the PF makes a sidestick input, an electrical order is sent to the flight
control computers. If the PNF makes a simultaneous sidestick input, both signals
are algebraically summed and both PF and PNF green lights flash on the
glareshield. This situation might occur in the case of an instinctive PNF reaction
on the sidestick. If the PNF needs to take control, he must press and hold the
take-over pb in order to avoid simultaneous sidestick inputs and announce, "I
have control".
In the case of a SIDESTICK FAULT ECAM warning due to an electrical failure,
the affected sidestick order sent to the computers is zeroed. This means that the
affected sidestick has been deactivated and there is no further procedure
associated with this warning.
In the case of pilot incapacitation where a sidestick input is being made, or in the
case of a mechanical failure leading to a jammed sidestick, the inputs are again
algebraically summed. There is no associated ECAM caution. In either of these
cases, the intervening pilot must press the take-over pb to gain single sidestick
authority. The pb must be depressed for at least 40 seconds to permanently
deactivate the affected sidestick. However, if a sidestick has been deactivated, it
may be reactivated by depressing its take-over pb.
h a n g e Vi
e
N
k
to
bu
y
.d o
.c
Training Guide
Sidestick
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
10.40.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
lic
10.50.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Operating Speeds
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
CHARACTERISTIC SPEEDS
The characteristics speeds VLS, F, S and Green Dot are displayed on the PFD
speed scale and are computed by the Flight Envelope (FE) computer.
VLS, F, S and Green Dot are also displayed on the PERF TAKE OFF, APPR
and GO-AROUND pages. The speeds displayed on these pages are computed
by the FMGC.
Computations made by the FE and the FMGC are based on the gross weight
information transmitted by the Fuel Control Monitoring Computer (FCMC).
h a n g e Vi
e
VS
VS is the stalling speed and is not displayed. For conventional aircraft, the
reference stall speed, VSmin, is based on a load factor that is less than 1g. This
gives a stall speed that is lower than the stall speed at 1g. All operating speeds
are expressed as functions of this speed, e.g. VREF = 1.3 x VSmin. Because
Airbus aircraft have a low speed protection feature which the crew cannot
override, the airworthiness authorities have reconsidered the definition of stall
speed for these aircraft.
All the operating speeds must be referenced to a speed that can be
demonstrated by flight test. This speed is designated as VS1g. Airworthiness
authorities have agreed that a factor of 0.94 represents the relationship between
VS1g, used as a reference for "fly by wire" Airbus andVSmin for conventional
aircraft types. As a result, the authorities allow Airbus aircraft to use the following
factors:
V2 = 1.2 x 0.94 x VS1g = 1.13 x VS1g

VREF = 1.3 x 0.94 x VS1g = 1.23 x VS1g
These speeds are identical to those that the conventional 94% rule would have
defined for these aircraft. The Airbus aircraft have exactly the same manoeuvre
margin that a conventional aircraft would have at its reference speeds. The
FCOM uses VS for VS1g.
VLS
VLS is the lowest selectable speed. VLS is represented by the top of an amber
strip on the airspeed scale on the PFD. It is equal to 1.13 VS at take-off, 1.18 VS
when the flaps are retracted and 1.23 VS when in the clean configuration. It
remains at 1.23 VS until landing. VLS is corrected for Mach effect to maintain a
0.3g buffet margin. In addition, VLS is increased when the speed brakes are
extended. At take-off, until retraction of one step of flaps, VLS is equal to or
greater than the lower of V2/1.05 and 1.05 VMCA. In all other phases of flight,
VLS is equal to or greater than VMCL. In the case of two engines inoperative on
the same wing, as soon as the slats are extended, VLS on the PFD is VMCL-2.
VLS on the MCDU is not modified.
F Speed
At take-off, F speed is the minimum speed at which the flaps may be retracted.
On approach, F speed is the target speed when the aircraft is in CONF 2 or 3. It
is represented by "F" on the PFD speed scale. It is equal to approximately 1.18
VS of CONF 1+F for take-off and is limited to a minimum of VMCL+5 kt. For
approach in CONF 2, it is increased by (A333: 14%) (A343: 18%) (A346: 22%). It
is limited to a minimum of VMCL+15 kt and to a maximum of VFE CONF 3 - 2
kt. For approach in CONF 3, it is increased by (A333: 4%) (A343: 7%) (A346:
12%). It is limited to a minimum of VMCL+10 kt and to a maximum of VFE CONF
FULL - 2 kt.
to
bu
y
.d o
.c
Training Guide
Operating Speeds
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
10.50.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
S Speed
At take-off, S speed is the minimum speed at which the slats may be retracted.
On approach, S speed is the target speed when the aircraft is in CONF 1. It is
represented by "S" on the PFD speed scale. It is equal to approximately 1.21 VS
of clean configuration and it is limited to VFE CONF 1* - 2 kt for approach.
(Green Dot)
Green Dot corresponds to the engine-out operating speed in clean configuration.
It provides the speed for the best lift/drag ratio and corresponds to the final
take-off speed. It is represented by a green dot on the PFD speed scale. A
formula to derive Green Dot for A333/A343 is shown below:
lic
10.50.3
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Operating Speeds
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
0.6 x weight (tonnes) + (A333: 107 kt) (A343: 115 kt) below 20000 ft
Add 1 kt per 1000 ft above 20000 ft
Subtract 10 kt with one engine out.
(A346: Green dot speed is not modified with one engine inoperative)
PROTECTION SPEEDS
The protection speeds Va PROT, Va MAX, VSW displayed on the PFD speed
scale are computed by the PRIM based on aerodynamic data.
Va PROT
Va PROT is the speed that corresponds to the angle of attack at which the AOA
protection becomes active. In normal law it is represented by the top of a black
and amber strip on the PFD speed scale.
Va FLOOR
Va FLOOR is the speed that corresponds to the angle of attack at which the
A/THR triggers TOGA thrust. This value is not displayed on the PFD, but is
normally situated between Va PROT and Va MAX.
Va MAX
Va MAX is the speed that corresponds to the maximum angle of attack that may
be reached in pitch normal law. In normal law it is represented by the top of the
red strip on the PFD speed scale.
VSW
VSW is the stall warning speed. It is represented by the top of the red and black
strip on the PFD speed scale and is only operative when the flight control law is
degraded to alternate or direct.
h a n g e Vi
e
VMAX
VMAX is the maximum permitted speed, represented by the bottom of the red
and black strip on the PFD speed scale. It is determined by the FE computer,
according to the aircraft configuration and is equal to VMO (or speed
corresponding to MMO), VLE or VFE.
LIMIT SPEEDS
VMCG
VMCG is the minimum speed on the ground during take-off, at which the aircraft
can be controlled by the use of the primary flight controls only, after a sudden
failure of the critical engine, with the other engine(s) remaining at take-off thrust.
VMCA
VMCA is the minimum control speed in flight at which the aircraft can be
controlled with a maximum bank angle of 5, if one engine fails, with the other
engine(s) remaining at take-off thrust (take-off flap setting, gear retracted).
VMCL
VMCL is the minimum control speed in flight at which the aircraft can be
controlled with a maximum bank angle of 5, if one engine fails, with the other
engine(s) remaining at takeoff thrust (approach flap setting).
VMCL-2 (A340)
VMCL-2 is the minimum control speed in flight at which the aircraft can be
controlled with a maximum bank angle of 5, if two engines fail on the same side,
with the other engine(s) at TOGA thrust (approach flap setting).
VFE
VFE is the maximum speed for each flap configuration.
VLE
VLE is the maximum speed with landing gear extended.
VLO
VLO is the maximum speed for landing gear operation.
VMO
VMO is the maximum speed.
to
bu
y
.d o
.c
Training Guide
Operating Speeds
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
10.50.4
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
VFE NEXT
VFE NEXT is the maximum speed for the next flap lever selection (further
extended position).
OTHER SPEEDS
V1
V1 is the highest speed, during take-off, at which there is a choice of either
continuing the take-off or stopping the aircraft. It is represented by "1" on the
PFD speed scale and is inserted manually via the PERF TAKE-OFF page.
VR
VR is the speed at which the pilot rotates in order to reach V2 at a height of 35 ft
above the end of the runway with one engine inoperative. It is inserted manually
via the PERF TAKE-OFF page.
V2
V2 is the take-off safety speed that the aircraft achieves at a height of 35 ft
above the end of the runway with one engine inoperative. V2 is maintained
during the second segment. It is represented by the Target Airspeed symbol on
the PFD speed scale. The minimum value is 1.13 VS for the corresponding
configuration. It is inserted manually via the PERF TAKE-OFF page.
VREF
VREF is the reference speed used for normal final approach and is equal to 1.23
VS of Landing Configuration FULL. It is represented on the PERF APPR page if
landing is planned in CONF FULL (VLS CONF FULL).
VAPP
VAPP is the final approach speed. It is displayed on the PERF APPR page and
calculated by the FMGCs. VAPP = VLS + wind correction. The wind correction is
limited to a minimum of 5 kt and a maximum of 15 kt. VAPP may be modified on
the PERF APP page for operational reasons, e.g. ice accretion
VAPP TARGET
VAPP target is calculated by the FMGC and is represented on the PFD speed
scale by a magenta triangle. It gives effective speed guidance on approach for
varying wind conditions. VAPP is computed as follows:
lic
10.50.5
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Operating Speeds
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
VAPP TARGET = GS mini + actual headwind (measured by ADIRS).

GS mini = VAPP - Tower wind (headwind component along runway axis
calculated by FMGC from tower wind entered on the MCDU).
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
PFD/FMA CHANGES TO BE CALLED

All changes on the FMA are to be called by the PF, except "LAND GREEN"
which is called by the PNF on AUTOLAND approaches. If any change has not
been called, then the PNF shall call the change. There is no competition to see
who can be the first to call these changes. The PNF should allow reasonable
time for the PF to call and not pre-empt him with every change. Any target
changes shall be confirmed on the PFD and ND. The result of any selection on
the FCU shall be confirmed on the FMA. The effect on the flight path shall be
monitored using raw data. Selection of an autopilot shall be confirmed by reading
the AP1(2) annunciation on the FMA.
Examples of standard calls are shown below to demonstrate how FMA changes
should be announced. (B) = Blue, (G) = Green and (W) = White.
Take-off
MAN
FLX 50 (W)
SRS (G)
CLB (W)
RWY (G)
NAV (B)
1 FD 2 (W)
A/THR (B)
Flex 50 SRS Runway
Thrust Reduction Altitude And Acceleration Altitude

THR CLB or
THR
DCLB1(2)
CLB (G)
ALT (B)
NAV (G)
AP1 (W)
1FD2 (W)
A/THR (W)
Initially, above 30 ft, NAV will change to green. "NAV" then

"Thrust Climb, Climb, Auto Thrust", or
"Thrust D Climb 1 (2), Climb, Auto Thrust"
When autopilot has been engaged, "Autopilot 1"
Climb In Heading Mode

THR CLB
OP CLB (G)
ALT (B)
HDG (G)
"Open Climb, Heading"
lic
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
10.60.1
O.I. (30
JUL 04)
w
w
.d o
A330/A340
FCTM
Training Guide
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
AP1 (W)
1FD2 (W)
A/THR (W)
h a n g e Vi
e
Climbing And Intercepting FCU Altitude

SPEED
ALT* (G)
NAV (G)
AP1 (W)
1FD2 (W)
A/THR (W)
"Speed ALT Star"
Maintaining FCU Altitude

SPEED
ALT (G)
NAV (G)
AP1 (W)
1FD2 (W)
A/THR (W)
ALT
At Cruise Level In Prog Page

MACH
ALT CRZ
NAV
AP1 (W)
1FD2 (W)
A/THR (W)
ALT Cruise
Descent
THR IDLE
DES (G)
ALT (B)
NAV
AP1 (W)
1FD2 (W)
A/THR (W)
"Thrust Idle, Descent, ALT Blue 230"

(FL 230 set on FCU and indicated blue on the bottom of the
altitude scale of the PFD)
to
k
.d o
.c
bu
y
m
c u -tr a c k
lic
to
lic
.d o
Training Guide
O.I. (30 JUL 04)
A330/A340
FCTM
10.60.2
w
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
Approach
SPEED
ALT (G)
G/S (B)
HDG (G)
LOC (B)
CAT 3
DUAL
MDA xxx
AP1+2 (W)
1FD2 (W)
A/THR (W)
"Glide Slope, LOC, Blue, CAT 2 Dual, Autopilot 1 and 2"

(Radar heading for ILS and Approach Mode has just been armed)
SPEED
G/S* (G)
LOC (G)
CAT 3
DUAL
MDA xxx
AP1+2 (W)
1FD2 (W)
A/THR (W)
"LOC, Glide Slope Star"
Missed Approach
MAN
TOGA
SRS (G)
CLB (B)
GA TRK (G)
lic
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
10.60.3
O.I. (30
JUL 04)
w
w
.d o
A330/A340
FCTM
Training Guide
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
AP1+2 (W)
1FD2 (W)
A/THR (B)
"TOGA, SRS, Go-around Track"
Clearance Levels
As each clearance level is given, the PF sets it in the FCU ALT window.
"290 Blue"
At GS capture, GA altitude is set on FCU.
"5,000 Blue"
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
DESCENT PROFILE MANAGEMENT

If the F-PLN were to be followed from TOD to touchdown, the descent profile
would be managed by the FMGS. However, ATC requirements or weather
avoidance may take the aircraft off the ideal profile. Consequently, it is important
to be aware of the aircraft's position relative to the ideal descent profile andthe
time available for any corrections to take effect. It is relatively easy for the aircraft
to correct from being 3000 ft above profile at FL 350, whereas being 3000 ft
above profile at 10000 ft will require a prompt, decisive correction.
All descent management revolves around the relationship between altitude and
distance to go (DTG) to touchdown. Consequently the F-PLN page must be
realistic. Ensure that the TO waypoint is in front of the aircraft and that the F-PLN
is representative of the expected route.
Before being able to assess the aircraft's position relative to the ideal descent
profile, it is necessary to have a method of calculating the profile. The following
method, illustrated with examples, provides a simple set of rules to monitor and
manage the descent profile. It assumes that the MCDU is updated to reflect the
expected arrival track.
TOD Cross-check
Multiply the flight level (in thousands of feet) by 4 to calculate the required
distance to go (DTG) to touchdown.
At FL350, the required DTG is approximately (35 x 4) = 140 nm.
There will be factors for weight and wind but if the FMGC computed descent
point is within 20 nm of this figure, then it can be considered acceptable as a
gross error check of the FMGC computation.
Descent Monitoring
From top of descent to 15000 ft, multiply the altitude (in thousands of feet) by 4
to calcluate the required DTG.
At 20000 ft, the required DTG is (20 x 4) = 80 nm
Below 15000 ft multiply the altitude by 3 and add 1 nm/10 kt above 150 kt.
lic
10.70.1
REV 1 (6
JUN 05)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Descent Management
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
At 10000 ft and 300 kt, the required DTG becomes (10 x 3) + 15 = 45 nm

At 5000 ft and 250 kt, the required DTG becomes (5 x 3) + 10 = 25 nm
At 3000 ft and 180 kt, flap 2, the required DTG becomes (3 x 3) + 3 = 12
nm.
At this stage, the aircraft will be approaching the glideslope and, hence, a normal
3 slope
h a n g e Vi
e
Profile Management
If the required DTG is less than that shown on the MCDU (low on profile), use
V/S until actual DTG = required DTG.
If the required DTG is more than that shown on the MCDU (high on profile), use
OP DES and speedbrakes until actual DTG = required DTG.
Summary
The benefit of using this method is its simplicity. It starts with a known quantity
(CRZ FL) and works for any speed.
This method does not directly consider wind. As the profile is being regularly
re-assessed during the descent, it will naturally show the effect of wind. A tail
wind will push the aircraft high and a head wind will drag the aircraft low.
Recover the profile using the techniques described above under Profile
Management.
There are numerous variations on this method and ways to finesse the
calculations. Whatever method you develop is a matter of personal choice.
However, it is essential that you develop and use a descent monitoring and
management technique.
to
bu
y
.d o
.c
Training Guide
Descent Management
c u -tr a c k
A330/A340
FCTM
REV 1 (6 JUN 05)

.d o
lic
lic
10.70.2
w
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
XC
h a n g e Vi
e
O
W
N
to
.d o
c u -tr a c k
.c
GENERAL
The touch and go is primarily employed during approach and landing practice. It
is not intended for landing roll and take-off procedure training.
APPROACH
Carry out a visual circuit as described in FCTM Ch 6. Confirm that the spoilers
and autobrake are not armed.
LANDING
The trainee accomplishes a normal final approach and landing. After touchdown,
the instructor selects Flaps 2, directs the trainee to "stand them up", ensures
speedbrakes are retracted and confirms the trim resets into the green band. The
trainee moves the thrust levers to the vertical position to allow the engines to
stabilise before TOGA is selected.
With the nose wheel on the ground, the pitch trim resets automatically to:
lic
10.80.1
O.I. (30
JUL 04)
w
C
.c
bu
N
y
bu
to
k
lic
C
c u -tr a c k
A330/A340
FCTM
.d o
Training Guide
Touch And Go-around
F-
er
O
W
PD
h a n g e Vi
e
XC
er
PD
F-
A333: 4 UP
A343: 5 UP
A346: 3 UP
This normally occurs 5 seconds after the pitch attitude is less than 2.5 and if the
ground spoilers are retracted.
When the engines are stabilised, the instructor calls "go". The trainee then
selects TOGA and removes his hand from the thrust levers. At or above VAPP
the instructor calls "rotate". The trainee rotates smoothly to approximately 15 of
pitch. The thrust levers must always be moved to TOGA to engage the SRS.
Once airborne, if performance is excessive, the thrust levers may be moved to
the climb detent. The aircraft may be slightly out of trim, but this should have little
effect on the rotation. Once the aircraft is airborne, flight law blends in by 100 ft
RA and the autotrim becomes active.
WARNING:
1.
If reverse thrust is selected, a full stop landing must be carried out.
Reverse side blank
y
o
c u -tr a c k
.c
INTENTIONALLY
BLANK
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
h a n g e Vi
e
bu
to
PNF
Common LR
3.THRUST
REDUCTION/ACCELERATION
ALTITUDE
1.GO AROUND
INITIATION
2.LATERAL
GUIDANCE
5.DIVERSION
4.HOLD
(missed approach)
LR
LR
LR - Version 02
.d o
GO AROUND
N
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
1. GO AROUND
INITIATION
Decision
THRUST LEVERS.TOGA
ANNOUNCE.GO AROUNDS FLAPS
FLAPSRETRACT ONE STEP
FMA
When positive climb
ANNOUNCE.POSITIVE CLIMB
ORDER..GEAR UP
L/G....UP
ANNOUNCE..GEAR UP - FLAPS
GRND SPLR.DISARM
EXTERIOR LIGHTS....SET
LR
TOGA
GO
AROUND
PHASE
Missed approach becomes the ACTIVE F-PLN

and the previously flown approach is strung
back into the F-PLN
LR
LR
LR
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common
LR
2. LATERAL
GUIDANCE
NAV or HDG...SELECT
FMA
The GA TRK mode guides the A/C on the memorized track at the time of TOGA selection
Push HDG Knob:

NAV mode engages
(Guidance for published
missed approach)...
Or
Pull HDG Knob

and set heading as
cleared by ATC...
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
3. THRUST REDUCTION/ACCELERATION
ALTITUDE
When LVR CLB flashing at thrust reduction/acceleration altitude

THRUST LEVERS.CL
FMA
At F speed with positive speed trend :
FLAPS 1
At S speed with positive speed trend :
FLAPS 0
AFTER TAKEOFF / CLIMB C/L down to the line
LR
LR
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common
LR
4. HOLD
CONTINUE ON STANDARD MISSED APPROACH PROCEDURE AND ENTER HOLDING PATTERN
3 types of HOLD can be performed
Observe on ND the pattern entry type :
LATERAL REV at HOLD :

Inbound
Ex: direct entry
FMGS HOLD parameters
HOLD EXIT LIMIT information

(When established in Holding pattern)
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
5. DIVERSION
Divert to another airport :

Lat Rev at TO WPT.ENABLE ALTN
When cleared to a WPT:
IMM EXIT..PRESS
DIR TOPERFORM
FMA
If necessary, at transition altitude :
BARO REF: STD

AFTER TAKEOFF / CLIMB C/L below the line
CLIMB
PHASE
ENABLE
1st CLB SPD
<- ALTN
PROG
PAGE
DEFAULT CRZ FL =
FL220
FL220
if ALTN is at less than 200 NM
FL310
FL310
if ALTN is at more than 200 NM
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
bu
to
PNF
Common LR
1.ACTION MONITORING
CROSS CHECKING
IF :
2.LATERAL
GUIDANCE
3.THRUST
REDUCTION
4.ACCELERATION
5.FLIGHT
CONTINUATION
Approach
Approach is
is not
not properly
properly stabilized
stabilized
Doubt
Doubt about
about situation
situation awareness
awareness
Malfunction
Malfunction
ATC
ATC changes
changes the
the final
final approach
approach clearance
clearance
Adequate
Adequate visual
visual cues
cues not
not obtained
obtained at
at MDA
MDA or
or DH
DH
Any
Any GPWS/TCAS
GPWS/TCAS or
or Windshear
Windshear alert
alert occurs
occurs
THEN engage GO AROUND procedure
LR - Version 02
.d o
GO AROUND
N
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
Preflight
Take Off
Climb
Cruise
Des
FLIGHT PHASES
OPTIMUM SPEED PROFILE
PREFLIGHT
TAKE OFF
V2
(V2 + 10)
CLIMB
ECON CLB SPD / MACH
CRUISE
ECON CRZ MACH
DESCENT
ECON DES MACH / SPD
APPROACH
Vapp
(GS Min)
GO AROUND
Vapp or current SPD whichever is greater.

Green Dot at ACC ALT
DONE
Approach
Go Around or Done
SWITCHING CONDITIONS TO NEXT PHASE

SRS take off mode engaged and
N1> 85% (EPR >= 1.25) or
Ground Speed > 90 kt
At acceleration altitude or by engagement of another
vertical mode
Reaching cruise FL
At descent initiation (if distance to DEST < 200 NM

and no step descent)
- Over flying (DECEL) pseudo waypoint with NAV (or
LOC*/LOC) mode engaged and altitude < 7200 ft AGL
- Manual activation of the approach phase.
1. To Go Around : when thrust levers at TO.GA
detent or
2. To Done: 30 seconds after landing or
3. To Climb: when inserting a new CRZ FL
1. To Approach : Manual activation of the approach
phase or
2. To Climb: Above acceleration altitude by
- Selecting ALTN or
- inserting NEW DEST and CRZ FL
To preflight
when INIT or PERF key depressed
to
bu
y
.d o
.c
lic
to
PF FLIGHT PHASE SWITCHING CONDITIONSPNF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common
LR
4. HOLD
CONTINUE ON STANDARD MISSED APPROACH PROCEDURE AND ENTER HOLDING PATTERN

(Database stored HOLD)
Three types of HOLD can be performed
DATABASE HOLD
AT
Observe on ND
Reversions
(Standard HOLD computed by FMGS)

Check the accordance between FMGS HOLD
COMPUTED HOLD
AT
HOLD AT and
published
parameters
data :entry)
(Manual
REVERT TO
COMPUTED
TO
The speedREVERT
DATABASE
change symbol
WPT
INB CRS

TURN
R
TIME/DIST
. /.
For HOLD exit limit information perform a Lateral

Revision at WPT :
The pattern
entry type
Ex: direct entry
LAST
UTC
EXIT
FUEL
Inbound
.d o
HOLD
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
The ALTN has been prepared
Common LR
CLIMB
PHASE
Lat Rev at TO WPT.ENABLE ALTN
The SEC F-PLN has been prepared to a diversion airfield

SEC F-PLN...ACTIVATE
CLIMB
PHASE
Nothing has been prepared !

SPD 250 kt + OP CLB...SELECT
NEW DEST + CRZ FL.INSERT
F-PLN..FINALIZE
CLIMB
PHASE
to
.d o
PNF
DIVERSION : 3 POSSIBILITIES
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
Preflight
Take Off
Climb
Cruise
Des
FLIGHT PHASES
PREFLIGHT
TAKE OFF
V2
(V2 + 10)
CLIMB
ECON CLB SPD / MACH
CRUISE
ECON CRZ MACH
DESCENT
ECON DES MACH / SPD
APPROACH
Vapp
(GS Min)
GO AROUND
Vapp or current SPD whichever is greater.

DONE
Approach
Go Around or Done

SRS take off mode engaged and
N1> 85% (EPR >= 1.25) or
Ground Speed > 90 kt
At acceleration altitude or by engagement of another
vertical mode
Reaching cruise FL
At descent initiation (if distance to DEST < 200 NM

and no step descent)
- Over flying (DECEL) pseudo waypoint with NAV (or
LOC*/LOC) mode engaged and altitude < 7200 ft AGL
- Manual activation of the approach phase.
1. To Go Around : when thrust levers at TO.GA
detent or
2. To Done: 30 seconds after landing or
3. To Climb: when inserting a new CRZ FL
1. To Approach : Manual activation of the approach
phase or
2. To Climb: Above acceleration altitude by
- Selecting ALTN or
- inserting NEW DEST and CRZ FL
To preflight
when INIT or PERF key depressed
to
bu
y
.d o
.c
lic
to
PF FLIGHT PHASE SWITCHING CONDITIONSPNF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
k
to
bu
BEFORE START PNF
lic
w
A330
ENGINE START
AFTER START
A330 - Version 03
.d o
PF
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330
1.a. BEFORE
START
LOADSHEET...CHECK
TAKEOFF DATA...........ENTER/REVISE
TAKEOFF DATA.........XCHECK
COCKPIT DOOR...CLOSED
SEAT BELTSADJUST
SEAT BELTS.ADJUST
MCDU...PERF TO
MCDU.F-PLN
EXT PWR..OFF
ORDER.BEFORE START C/L down to the line
BEFORE START down to the line..PERFORM

ANNOUNCE..BEFORE START C/L
down to the line COMPLETED
Confirm any takeoff weight limitation.

Ask for external power disconnection
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330
1.b. BEFORE
START
NW STRG DISC MEMO..........CHECK
PUSHBACK/START CLEARANCE.OBTAIN
WINDOWS and DOORS.CHECK CLOSED
WINDOWS.CHECK
THR LEVERS..IDLE
BEACONON
PARKING BRAKE ACCU PRESS.CHECK

PARKING BRAKE.ON
ORDER.BEFORE START C/L below the line
BEFORE START C/L below the linePERFORM

ANNOUNCE..BEFORE START C/L
COMPLETE
GROUND CREW COMMUNICATIONESTABLISH

CAUTION ! DO NOT PERFORM the pushback if NW STRG DISC not
displayed on the ECAM MEMO to avoid damages to the nose landing gear.
The BRAKE ACCU PRESS
must be in the green band
When PARKING BRAKE is ON:

brake pressure is shown
PARK BRK MEMO is displayed
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330
2. AUTOMATIC ENGINE
START SEQUENCE
ENG START SEL..........IGN/START

BLEED PRESSURECHECK
GE
RR
PW
ANNOUNCE....STARTING ENGINE 1
MASTER SW 1.ON
START VALVE OPENS
N2 INCREASES (N3 for RR)
IGNITER
FUEL FLOW
EGT
..CHECK
N1
OIL PRESS
START VALVE CLOSE
50% N2 (GE)
Between 43% and 48% N2 (PW)
50% N3 (RR)
ENG IDLE PARAMETERS..CHECK NORMAL
ANNOUNCE...STARTING ENGINE 2
REPEAT START SEQUENCE FOR ENG 2..
Check BLEED PRESSURE on ECAM page.
Start ENG 2 ONCE AVAIL is displayed

for ENG 1
XX.X
ECAM ENGINE page
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.a. AFTER
START
ENG START SEL.NORM

End of START sequence : Signal for PNF actions
APU BLEED.OFF
1. GND SPLRSARM
2. RUD TRIMRESET
3. FLAPSSET
4. PITCH TRIM..SET
ECAM STATUS.CHECK
ECAM DOOR PAGE....CHECK
ANNOUNCE.CLEAR TO DISCONNECT
5.
ENG ANTI ICEAS RQRD

WING ANTI ICE..AS RQRD
6. APU MASTER SWOFF

Overhead
Panel
ENG START SEL

back to NORM
ENGINE
WHEEL
ECAM
4
1
Pedestal
3
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.b. AFTER
START
NWS TOWING FAULT LT extinguishedCHECK
AFTER START C/L

Observe the ECAM MEMO:
engines started
2
To stabilize engine hot section temperature:
t (min.)
3 min (GE) / 5 min (PW & RR) / 3 min (RR if

engines have been stopped for 1.5 hr or less)
minimum at or near IDLE
t
Engine
started
If icing conditions :
GE :
RR :
PW :
High power
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330
2. AUTOMATIC ENGINE
START SEQUENCE

BLEED PRESSURECHECK
GE
RR
PW
MASTER SW 1.ON
START VALVE OPENS
Set ENG master
N2
INCREASES
Select IGN
(N3 for RR)
Wait 3 sec.
switch to ON
START
IGNITER
FUEL FLOW
EGT
..CHECK
N1
ENG
1
is
started
first
because
it
powers
ENG 1 is started first because it powers the
the blue
blue hydraulic
hydraulic system,
system, which
which pressurizes
pressurizes the
the parking
parking
OIL PRESS
brake.
brake.VALVE CLOSE
START
50% N2 (GE)
DO
NOT
SET
the
DO
NOTN3
SET
the MASTER
MASTER switch
switch ON
ON before
before all
all amber
amber crosses
crosses and
and messages
messages have
have disappeared
disappeared on
on
50%
(RR)
engine
parameters
(upper
engine
parameters
(upper ECAM
ECAM display).
display).
ENG
IDLE
PARAMETERS..CHECK
NORMAL
for ENG 1
ECAM ENGINE page
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330
2. AUTOMATIC ENGINE
START SEQUENCE

BLEED PRESSURECHECK
GE
RR
PW
MASTER SW 1.ON
DO
SET
the
DO NOT
NOT
SET
the MASTER
MASTER switch
switch ON
ON before
before EGT
EGT amber
amber crosses
crosses and
and messages
messages have
have disappeared
disappeared on
on
START
VALVE
OPENS
engine
parameters
(upper
N2
INCREASES
(N3 for
RR) ECAM
engine
parameters
(upper
ECAM display).
display).
IGNITER
FUEL FLOW
EGT
ENG
ENG 11 is
is started
started first
first because
because itit powers
powers the
the blue
blue hydraulic
hydraulic system,
system, which
which pressurizes
pressurizes the
the parking
parking
..CHECK
N1
brake.
brake.
OIL PRESS
START VALVE
CLOSE
Starting
a hot engine
50% N2 (GE)
EEC performs a dry crank to
st start: EGT>100C
(1
reduce engine temperature
nd
50% 2N3 start:
(RR) EGT>150C)
for ENG 1
ECAM ENGINE page
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330
2. AUTOMATIC ENGINE
START SEQUENCE

BLEED PRESSURECHECK
GE
RR
PW
MASTER SW 1.ON
START VALVE OPENS
N2
INCREASES
(N3 for RR)
ENG
ENG 11 is
is started
started first
first because
because itit powers
powers the
the blue
blue hydraulic
hydraulic system,
system, which
which pressurizes
pressurizes the
the parking
parking
IGNITER
brake.
brake.
FUEL FLOW
EGT
..CHECK
all
N1
DO
DO NOT
NOT SET
SET the
the MASTER
MASTER switch
switch ON
ON before
before
all amber
amber crosses
crosses and
and messages
messages have
have disappeared
disappeared on
on
OIL
PRESS
engine
parameters
engine
parameters (upper
(upper ECAM
ECAM display).
display).
START VALVE CLOSE
50% N2 (GE)
50% N3 (RR)
for ENG 1
ECAM ENGINE page
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
k
to
NORMAL ENGINE IDLE PARAMETERS PNF

AT ISA SEA
LEVEL
A330
lic
GE:
N1about 23%
EGT.about 360 C
N2about 63%
FFabout 550 kg/h (1210 lb/h)
PW:
EPRabout 1.010%
N2about 59%
EGTabout 320 C
N1about 23%
RR:
EPRabout 1.015%
N3about 63%
EGTabout 380 C
N1about 22.6%
Upper ECAM
N2about 47%
Lower ECAM
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.a. AFTER
START
ENG START SEL.NORM

End of START sequence : Signal for PNF actions
APU BLEED.OFF
1. GND SPLRSARM
Turn
Turn APU
APU BLEED
BLEED OFF
OFF just
just after
after engine
engine start
start
2. RUD TRIMRESET
to
to avoid
avoid ingesting
ingesting engine
engine exhaust
exhaust gases.
gases.
3. FLAPSSET
4. PITCH TRIM..SET
ECAM STATUS.CHECK
ECAM DOOR PAGE....CHECK
ANNOUNCE.CLEAR TO DISCONNECT
5.
ENG ANTI ICEAS RQRD

WING ANTI ICE..AS RQRD
6. APU MASTER SWOFF

Overhead
Panel
ENG START SEL

back to NORM
ENGINE
WHEEL
ECAM
4
1
Pedestal
3
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330
Set Takeoff CG on the pitch trim wheel
For this purpose, use the actual CG indicated on the

ECAM :
The Takeoff CG value must be within the green band

limits.
to
.d o
PNF
PITCH TRIM SET
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
to
k
A330
Engine anti-ice
OAT or TAT 10 C with visible
moisture in the air, standing
water, slush, ice or snow on
the taxiways or runways
ICING
CONDITIONS
expected
ENG ANTI ICE

must be ON
Wing anti-ice
Prevent ice formation
OR
Ice accumulation on the
wing leading edges
WING ANTI ICE

recommended
OR
Ice accumulation on the
visual ice indicator or on
the windshield wipers
CAUTION ! In icing conditions, minimise flight duration with the slats extended.
.d o
.c
lic
to
PF
WHEN ARE ENG & WING ANTI ICE REQUIRED
?
PNF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.b. AFTER
START

If nosewheel steering has exceeded 93
AFTER START C/L
Illumination of the red

oversteer warning light
NO GO
FAULT
Maintenance action required

engines started
2
t (min.)
FAULT

t
Engine
started
GE :
RR :
PW :
High power
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.b. AFTER
START
AFTER START C/L

NW STRG still disconnected

+
engines started
at least 1 engine running
2
t (min.)

t
Engine
started
GE :
RR :
PW :
High power
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.b. AFTER
START
AFTER START C/L

If icing conditions > 30min

OR
Significant engine vibration
engines started
On ground, perform an ENGINE RUN-UP (60% N1 minimum)

for approximately 30 sec prior to higher thrust in order to
centrifuge any ice from the engines rotating parts
2
ENG ANTI ICE

ON
t (min.)
Continuous ignition
automatically selected

t
Engine
started
GE :
RR :
PW :
High power
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.b. AFTER
START
AFTER START C/L

engines started
If icing conditions
0 &
OAT 1 C
On ground, perform an ENGINE RUN-UP (50% N1

t (min.)
recommended) for 10 sec prior to take off
in order to
2
centrifuge any ice from the engines rotating parts
If holding on the ground, perform it once every hour

t
Engine
started
GE :
RR :
PW :
High power
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
3.b. AFTER
START
AFTER START C/L

On ground, perform PERIODIC ENGINE RUN-UP (50% N1

recommended) to centrifuge any ice from the engines
rotating parts at intervals not greater than 15 min.
If icing conditions
&
engines
OAT
started
3 C
t (min.)RUN-UP (50% N1
Take off should be preceded by a STATIC
2
recommended) with observation of all primary parameters
ENG ANTI ICE

Continuous ignition

ON
automatically selected
t
Engine
started
GE :
RR :
PW :
High power
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
to
bu
PNF
START FAULT
lic
EGT OVERLIMIT
A330 PW - Version 03a
.d o
PFENGINE
N
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
1. ENG 1 START FAULT
Apply before start procedure

Start engine 1
DETECTION
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
DECISION
PF
COMMUNICATES
ST AT US, or
SUMM ARY
WE ATHER
WEATHER
LDG DIS T
LDG DIST
OPERATIONAL
OPERATIONALAND
AND
COMME RCIAL
COMMERCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
ATC
DECISION
DECISIO N
NOT IFY
PURSER
PURSER/ PAX
/ PAX
OPS
OPS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
The FADEC automatically :

Adjust the fuel flow
As adjustment of the fuel flow has

not been successful, the FADEC :
shuts off the fuel
turns off the ignition
Note: The FADEC
performs an auto crank
After 30 sec. of dry crank, the FADEC

automatically performs a new start
Both igniters are powered
If the engine doesnt start, the

ECAM asks the pilot to confirm the
automatic start abort by setting
ENG MASTER 1 to OFF.
to
k
.d o
ACTIONS PERFORMED BY THE FADECPNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Do not interrupt the FADEC protective actions
The FADEC automatically

abort the start sequence
The fault light turns off when the

engine master switch is set to OFF
to
.d o
PNF
ECAM PROCEDURE
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Review FCOM 3.02 procedure (If time permits)
Then, 2 options :
Ask for appropriate maintenance actions
Perform a new start attempt (prefer manual start procedure)
FCOM
3.04.70
Starter engagement is limited in time and in number of successive attempts :

Start cycle
5 min
5 min
5 min
Starter cool down

30 min
No engagement of the starter when the N2 is above 35%
5 min
Starter cool down

30 min
.d o
DECISION
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
k
to
bu
TAXI & BEFORE T/OPNF
lic
w
A330/A340-300
LR - Version 03b
.d o
PF
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
A330/A340-300
1. TAXI
INITIATION
Before Taxiing:
NW STRG DISC..CHECK not displayed on
right ECAM MEMO
TAXI CLEARANCE.....OBTAIN
When Taxi clearance obtained:
NOSE LIGHT....TAXI
ELAPSED TIME .................AS RQRD
PARKING BRAKE..................OFF
THRUST LEVERS..AS RQRD
ANNOUNCE.BRAKE CHECK
BRAKE PEDALPRESS
BRAKE PRESSURE...........CHECK ZERO

ANNOUNCE..PRESSURE ZERO
FLT CTLCHECK
FLT CTL..CHECK
Observe ECAM MEMO :
PARKING BRAKE release

( Slight residual pressure may be
indicated for a short period of time )
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2. TAXI : CLEARANCE
CONFIRMATION
When ATC clearance obtained:
ATC CLEARANCE..CONFIRM
TERR ON NDAS RQRD
1. RADAR / PWS...ON / AUTO
2. ATC..SET
3. AUTOBRAKEMAX
4. T/O CONFIG.....PRESS
5. T/O MEMO....CHECK NO BLUE
TCAS STBY
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330/A340-300
3. TAXI
CHECKS
FCU ALT..CHECK
If ATC requests to maintain runway heading or in
case of a radar vector procedure :
HDG....SET
FLIGHT INSTRUMENTS...CHECK
FLIGHT INSTRUMENTS...CHECK
CABIN REPORTRECEIVE (CM1)

T/O BRIEFINGCONFIRM
BEFORE T/O C/L down to the line
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330/A340-300
4. BEFORE
TAKE OFF
If brake fans running:
BRAKE TEMP BELOW 150C.CHECK

BRAKE FANSOFF
APPROACH PATH CLEAR OF TRAFFIC.CHECK
TAKEOFF/LINE UP CLEARANCEOBTAIN
CABIN CREW.ADVISE
ENGINE START SEL....AS RQRD

TCAS..TA or TA/RA
EXTERIOR LIGHTS..SET
PACKS 1 + 2..AS RQRD
SLIDING TABLE...STOW
SLIDING TABLE.....STOW
BEFORE T/O C/L below the line
minimize bird strike hazard

during take-off
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
THE END...
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PF moves the flight controls
A330/A340-300
PNF announces :
Both
elevators
Rudder check
FULL UP
FULL DOWN
NEUTRAL
ailerons
FULL LEFT
FULL RIGHT
NEUTRAL
FULL LEFT
FULL RIGHT
PF checks that PNF calls are in accordance

with the sidestick orders
NEUTRAL
PNF applies full sidestick deflections and

silently checks full travels and correct sense
to
.d o
PNF
FLIGHT CONTROLS CHECK
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2. TAXI : CLEARANCE
CONFIRMATION

If takeoff data / ATC clearance has changed, (or in case of RWY change)
2. ATC..SET
update takeoff data and FMGS :
3. AUTOBRAKEMAX
4. TO CONFIG...PRESS
TAKEOFF DATA updates
- Gross Weight and CG on FUEL PRED
- F-PLN (runway in use)
- Flaps levers (Take-off position)
- V1,VR,V2 (reinsert)
- FLEX T/O temperature (reinsert)
5. TO MEMO..CHECK NO BLUE
FMGS updates
- F-PLN
- Initial climb and speed 3
limit
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2. TAXI : CLEARANCE
CONFIRMATION
If use of radar is required, consider selecting the

radar display on the PF side, and TERR ON ND
on the PNF side only.
TERR ON NDAS RQRD

2. ATC..SET
3. AUTOBRAKEMAX
TCAS STBY
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2. TAXI : CLEARANCE
CONFIRMATION
TERR ON NDAS RQRD
Switch
Switch the
the Radar
Radar ON
ON and
and the
the PWS
PWS to
to AUTO
AUTO as
as
late
late as
as possible
possible to
to avoid
avoid hazardous
hazardous emissions
emissions to
to
ground
ground staff
staff

2. ATC..SET
3. AUTOBRAKEMAX
TCAS STBY
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330/A340-300
2. TAXI : CLEARANCE
CONFIRMATION
TERR ON NDAS RQRD
Set
Set the
the appropriate
appropriate ATC
ATC configuration
configuration for
for takeoff:
takeoff:
2. ATC..SET
ATC:
ATC: AUTO
AUTO
ALT
ALT RPTG:
RPTG: ON
ON
ATC
ATC code
code set
set
TCAS:
TCAS: TA
TA or
or TA/RA
TA/RA
Traffic
Traffic sel:
sel: ABV
ABV
3. AUTOBRAKEMAX
TCAS STBY
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330/A340-300
2. TAXI : CLEARANCE
CONFIRMATION
TERR ON NDAS RQRD
2. ATC..SET
3. AUTOBRAKEMAX
Autobrake
Autobrake may
may be
be armed
armed with
with PARKING
PARKING BRK
BRK ON.
ON. 5. T/O MEMO....CHECK NO BLUE
AUTO BRK
MAX
TCAS STBY
ECAM WHEEL page
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2. TAXI : CLEARANCE
CONFIRMATION
TERR ON NDAS RQRD
Check
Check that
that ECAM
ECAM upper
upper display
display shows
shows
T.O
T.O CONFIG
CONFIG NORMAL
NORMAL

2. ATC..SET
3. AUTOBRAKEMAX
TCAS STBY
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330/A340-300
This
This disarms
disarms NAV
NAV mode.
mode.
Then
Then RWY
RWY TRK
TRK will
will engage
engage at
at 30
30 ft
ft RA
RA and
and will
will keep
keep the
the aircraft
aircraft on
on the
the current
current TRK.
TRK.
FMA
Usual case :
CLB
If HDG preset :
OP CLB
NAV
to
.d o
PNF
HEADING PRESET
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Address
Address any
any changes
changes in
in the
the clearance
clearance
A330/A340-300
Make
Make as
as extensive
extensive use
use as
as possible
possible of
of the
the displays
displays
T/O
T/O BRIEFING
BRIEFING CONFIRMATION
CONFIRMATION FLOW
FLOW
V1
V2
Sel ALT
FLX
4
3
GW
7
PERF
page
VR
( optional)
CONF
2
F-PLN
page
RWY/SID
to
.d o
PNF
TO BRIEFING CONFIRMATION
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330/A340-300
limitation:
300C
auto ignition temperature of the hydraulic fluid
Without brake fan: Rely on HOT BRAKE ECAM caution (triggered at 300C)
With brake fans running:
The fans blow on the temperature sensor, and modifies the indication
Actual Brake temperature :
300 C
Indication on ECAM : 150 C
The crew cannot rely on the ECAM caution (linked to indicated value).
Brake temperature must be checked
If indicated value is above 150C: delay takeoff
to
.d o
PNF
BRAKE TEMPERATURE LIMITATION
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
A330/A340-300
4. BEFORE
TAKE OFF

BRAKE FANSOFF
CABIN CREW.ADVISE
or TA/RA
Conditions
::
Conditions for
for selecting
selecting IGN/START
IGN/START prior
prior to
to takeoff
takeoffTCAS..TA
RR
PW
GE

CFM

BEFORE T/O C/L below the line
Heavy rain or severe turbulences

expected after takeoff
Runway with standing water
ENG ANTI ICE ON
automatically
(not valid for RR and CFM engines)
Consider
ignition
Consider igniters
igniters wear
wear in
in case
case of
of continuous
continuous
ignition
minimize bird
strike hazard
during take-off
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330/A340-300
4. BEFORE
TAKE OFF

BRAKE FANSOFF
CABIN CREW.ADVISE

TCAS..TA or TA/RA
Known nearby traffic, in visual

contactT/O
BEFORE
C/L below the line
Significant potential for unwanted or inappropriate

resolution advisories
minimize bird strike hazard

during take-off
The FAA recommends

selecting TA mode
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
A330/A340-300
4. BEFORE
TAKE OFF

BRAKE FANSOFF
CABIN CREW.ADVISE

TCAS..TA or TA/RA
Improved performance
(TOGA)
Consider selecting
packs
BEFORE
OFF or APU bleed ON
T/O C/L below the line
Note: Select Packs OFF at least 20s

before applying takeoff thrust.
Reduced EGT (FLEX)
Use of APU bleed is not allowed, if wing anti-ice is to be used.

To avoid the ENG THRUST LOST ECAM warning :
APU
bleed ON
Takeoff power
application
At least 20
sec. bird strike hazard
minimize
during take-off
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
LR - Version 03b
to
k
lic
.d o
AFTER LANDING
PF
PARKING SECURING
PNF THE A/C
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
CommonLANDING
LR
1.a. AFTER
Depending on the taxi position :

ANNOUNCE..LANDING LIGHTS
LAND LIGHTS...OFF
GRND SPLRS.DISARM
STROBE..AUTO
Signal for PNF actions
Observe the ECAM MEMO :
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common
LR
1.b. AFTER
LANDING
1- RADAR.OFF/STBY
2- PREDICTIVE WINDSHEAR....OFF
3- ENG START SEL..NORM
4- FLAPS..RETRACT
5-
TCAS MODE SEL.STBY

ATC..AS RQRD
6- APU.START
7- ANTI ICE...AS RQRD
6
5
2
3
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
CommonLANDING
LR
1.c. AFTER
BRAKE TEMP..CHECK
AFTER LDG C/L
FCOM
Brake temperature Limitations :

3.04
Use of brake fans :
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2.a.
PARKING
PARKING BRK ACCU PRESS..CHECK
ANTI - ICE....OFF
PARKING BRK..ON
APU BLEED..ON
ENG MASTER (all)..OFF
SLIDE DISARMEDCHECK
GROUND CONTACTESTABLISH
ELAPSED TIMESTOP
BEACON .....OFF
FUEL PUMPS..OFF
ATC.STBY
IRS PERFORMANCE..CHECK
SEAT BELTSOFF
STATUS.CHECK
ECAM SD auto - switching
(when last Engine is shut down)
To stabilize engine hot

section temperature :
GE & CFM : 3 min

RR : 1 min
PW : 90 sec
WHEEL
minimum at
or near IDLE
t
Landing
ENG shut
down
DOOR
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
LR
2.b.Common
PARKING
PARKING BRK..AS RQRD
BRAKE FANOFF
Dus.....DIM
Dus....DIM
PARKING C/L
REPORT SEVERE ICING CONDITIONS
If one brake temperature > 300C

(or >150C with brake fans ON)
Release parking brakes

after chocks are in place
If operational conditions
permits (no slippery tarmac).
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common
LRAIRCRAFT
3. SECURING
THE
PARKING BRK...CHECK ON
ADIRS (1+2+3)..OFF
OXY CREW SUPPLY..OFF

EXTERIOR LIGHTS.OFF
MAINT BUS switch...AS RQRD
APU BLEED..OFF
EXT PWR.AS RQRD
APU MASTER SW...OFF
EMER EXIT LIGHT...OFF
NO SMOKING...OFF
BAT 1 + 2 + APU..OFF
SECURING THE AIRCRAFT C/L

To ensure the ADIRS memorize the last data:
at least 10 sec.
t
ADIRS OFF
Electrical supply OFF
To prevent smoke entering the cabin during next

start :
2 min
t
APU AVAIL light
goes out
APU flap closed

Set batteries OFF
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common
LR
1.b. AFTER
LANDING
1- RADAR.OFF/STBY
Icing conditions
Slush or snow on the runway

4- FLAPS..RETRACT
Wait until engine shutdown and

ground confirmation that flaps &
7
slats are cleared
of obstructing ice
5-
TCAS MODE SEL.STBY

ATC..AS RQRD
6- APU.START
6
1
5
2
3
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common
LR
1.b. AFTER
LANDING
1- RADAR.OFF/STBY
4- FLAPS..RETRACT
Depending
Depending on
on local
local regulations,
regulations, ATC
ATC transponder
transponder
may
may be
be operated
operated in
in mode
mode SS
7
5-
TCAS MODE SEL.STBY

ATC..AS RQRD
6- APU.START
6
5
2
3
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
Select brake fans

To avoid brake
oxidation
Short turnaround
time
just before stopping at the gate (short taxi)

OR
5 min after landing (long taxi)
Use of brake fans without

oxidation consideration
Observe the ECAM memo if the brake fans are selected
Select brake fans as soon as a green arc appears (temperature > 100C)
to
.d o
PNF
USE OF BRAKE FANS
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2.a.
PARKING
ANTI - ICE....OFF
PARKING BRK..ON
APU BLEED..ON
SLIDE DISARMEDCHECK
ELAPSED TIMESTOP
BEACON .....OFF
FUEL PUMPS..OFF
Above
Above 500
500 C,
C, parking
parking brake
brake application
application should
should
be
be avoided,
avoided, unless
unless operationally
operationallynecessary.
necessary.
ATC.STBY
SEAT BELTSOFF
STATUS.CHECK

GE & CFM : 3 min

RR : 1 min
PW : 90 sec
WHEEL
minimum at
or near IDLE
t
Landing
ENG shut
down
DOOR
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
A330/A340-300
2.a.
PARKING
ANTI - ICE....OFF
PARKING BRK..ON
APU BLEED..ON
SLIDE DISARMEDCHECK
ELAPSED TIMESTOP
BEACON .....OFF
FUEL PUMPS..OFF
Switch
Switch ON
ON the
the APU
APU BLEED
BLEED as
as later
later as
as possible
possible to
to
avoid
avoid ingestion
ingestion of
of exhaust
exhaust gases
gases from
from the
the engines.
engines.
ATC.STBY
SEAT BELTSOFF
STATUS.CHECK

GE & CFM : 3 min

RR : 1 min
PW : 90 sec
WHEEL
minimum at
or near IDLE
t
Landing
ENG shut
down
DOOR
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330/A340-300
2.a.
PARKING
ANTI - ICE....OFF
PARKING BRK..ON
APU BLEED..ON
SLIDE DISARMEDCHECK
ELAPSED TIMESTOP
BEACON .....OFF
FUEL PUMPS..OFF
If APU not
available
Set EXT PWR ON

before
ENG MASTERS OFF
SEAT BELTSOFF
ATC.STBY
STATUS.CHECK

GE & CFM : 3 min

RR : 1 min
PW : 90 sec
WHEEL
minimum at
or near IDLE
t
Landing
ENG shut
down
DOOR
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
Drift check:
POSITION MONITOR page
Check that the drift is in the acceptable margins defined in Fcom 3.03.25
UNACEEPTABLE CONSIDER THE IRU AS

FAILED
CHECK ON NEXT FLIGHT. IF STILL IN OR

ABOVE THIS AREA AFTER 2nd FLIGHT?
CONSIDER THE IRU AS FAILED
ACEEPTABLE
FOR USE
Residual ground speed check:

Ground Speed > 15 kts
&
Excessive deviation occurred
after 2 consecutive flights
OR
Ground Speed > 21 kts
Consider IR as failed
to
k
.d o
PNF
IRS PERFORMANCE
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
A330/A340-300
2.a.
PARKING
ANTI - ICE....OFF
PARKING BRK..ON
APU BLEED..ON
SLIDE DISARMEDCHECK
ELAPSED TIMESTOP
BEACON .....OFF
FUEL PUMPS..OFF
ATC.STBY
SEAT BELTSOFF
STATUS.CHECK
GEare
& CFM
: 3 min
IfIf maintenance
displayed:
WHEEL
DOOR
maintenance status
status messages
messages
are
displayed:
minimum at
RR : 1 min
or near IDLE
At
transit
To stabilize
At
engine
transit
hot:: disregard.
disregard.
PW : 90 sec
section temperature
:
At
or
At main
main base
base
or airport
airport with
with repairs
repairs available:
available: report
report for
for maintenance
maintenance analysis.
analysis.
t
Landing
ENG shut
down
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common
LRAIRCRAFT
3. SECURING
THE
PARKING BRK...CHECK ON
ADIRS (1+2+3)..OFF
OXY CREW SUPPLY..OFF

EXTERIOR LIGHTS.OFF
MAINT BUS switch...AS RQRD
APU BLEED..OFF
Electrical power required for

crew or servicing personnel
EXT PWR.AS
Consider setting MAINT BUS RQRD
switch
to ON prior setting
APU MASTER
SW...OFF
aircraft power to off.
EMER EXIT LIGHT...OFF
NO SMOKING...OFF
BAT 1 + 2 + APU..OFF
SECURING THE AIRCRAFT C/L

To ensure the ADIRS memorize the last data:
at least 10 sec.
t
ADIRS OFF
Electrical supply OFF
To prevent smoke entering the cabin during next

start :
2 min
t
APU AVAIL light
goes out
APU flap closed

Set batteries OFF
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
!
O
W
y
bu
to
k
lic
.c
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu
AIRBUS DESCENT MONITORING

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
THE MAGICAL AND MYSTERIOUS WORLD OF THE AIRBUS FMGS

Youve probably heard the (really) old joke about Airbus Pilots:
How can you tell an Airbus Pilot?
(S)Hes the one who says Whats it doing now?
How can you tell an experienced Airbus Pilot?
(S)Hes the one who says Its doing that again!
I would like a dollar for every time that Ive thought the first thought (when new on the Airbus) and for every time
that Ive thought the second thought (after being on the Airbus for over a decade). Yes, after over ten years on the
Airbus it still throws up stuff that I have either never seen before or have been unable to work out why it does what
it does. However, I have managed to sort out the wheat from the chaff and have a reasonable idea of what the
FMGS is actually doing now.
For most Airbus drivers the FMGS appears to be a blend of logic(?) and black magic and runs on smoke and
mirrors. Just do a quick Google search on the Internet with Airbus Automation and you will find several accident
reports in amongst all the other stuff. Pilots (just like you) have managed to crash Airbuses because they didnt
know, were not aware of, or misunderstood what the FMGS Autoflight system was doing (or trying to do).
In reality the FMGS is just some computer software and does what its programmers, programmed it for. Most of
the mysteries of the FMGS are because YOU (yes you!) dont know or are confused with the rules that it uses to
calculate predictions, display items and symbols (and their colours) on the PFD, ND and MCDU and how it
interacts with the AP, FD and A/THR. Make no mistake all these separate bits of kit are related and interact
together. Thats why the S part of the FMGS is in there its all part of a SYSTEM.
Whether you like it or not, the Airbus is a glass filled, highly automated aircraft. If you cant hack this fact (or are
unwilling to!) then get yourself a Classic conversion fast!!
While the FMGS is busy working away during all Phases of flight, the Descent Phase (and to a lesser extent the
Approach Phase) is where most people have trouble.
What follows is one persons attempt to unravel most of the common misconceptions, errors and Gotchas related to
monitoring the descent on the Airbus. Everything on the Airbus is inter-related so well be looking at the A/THR,
AP, FD, displays (PFD, ND and MCDU symbology and colours) and the FMGS.
Some people try and make monitoring of the Airbus descent into some Black Art that will take years to master. Not
so. Have a read of this, which is mainly extracts pulled from the FCOM 1 (Auto Flight), FCOM 4 (FMGS), FCTM
and my own personal observations after having made all the mistakes (but I bet there are still some out there
waiting for me!).
Couple this new understanding with bog standard, basic mental descent monitoring (I strongly urge you to read,
understand and practically apply the Descent Profile Management contained in the FCTM its easy and will save
your butt when the FMGS does something you werent expecting) and you will gain years worth of my muddling,
mistake riddled Airbus experience.
Mistakes are inevitable in aviation, especially when one is still learning new things. The trick is
to not make the mistake that will kill you. (Stephen Coonts)
Really start to look at the displays (PFD, FMA, ND and MCDU) and use the information that they provide in a
common sense and practical way. There is no point in looking at the PFD, ND or MCDU unless you know what it is
telling you. You will either be ignorant of what is actually occurring or you will make poor decisions based on the
incorrectly interpreted information you decipher from the displays. With correct knowledge you can anticipate what
the system will do next and if it is not what you want, intervene and make it do exactly what you desire.
After all, that is what piloting is all about and you will enjoy flying so much more!
So sit back, relax(?) and let the games begin!
I dont care how you obtained a copy of these notes, however be aware that these notes are not Cathay Pacific Airways approved documents. While I have done my
best to ensure that there are no errors, I cant guarantee this. Official Company publications and FCOMs take precedence over these notes. Therefore, caveat
emptor, use at your own risk.
If you do find an error, please let me know and Ill correct future versions. Send a Groupwise to Jack Frost crwfga.
Page 1 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.d o
o
c
.
AUTOTHRUST
(A/THR)
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Lets start off with a look at the A/THR. Why the A/THR? Well its relatively simple to describe and you need to
understand how the FMGS Vertical modes interact with the A/THR to understand why it is doing what it is doing.
A/THR Engagement Status
The A/THR engagement status is displayed on the PFD FMA fifth column (the right hand column, on the third line).
There are three possible engagement statuses. The A/THR modes may be either:
Armed ( A/THR displayed in blue in the FMA fifth column),
Active ( A/THR displayed in white in the FMA fifth column), or
Disconnected (FMA fifth column, third line blank and no operation mode displayed in the FMA first column).
A/THR Operation Modes

The A/THR operation modes are displayed on the PFD FMA first column (the left hand column).
There are three general A/THR operation modes:
SPEED/MACH,
THR(ust), and
RETARD (IDLE thrust and used when in the AP/FD FLARE mode not considered in this discussion).
SPEED/MACH Mode
When in SPEED/MACH mode the A/THR will command either a SPEED or MACH that is either the Selected Speed
or the Managed Speed. Either SPEED or MACH will be annunciated in green in the FMA first column.
The system determines automatically when it should change from SPEED to MACH in the climb and vice versa in
the descent. The point at which this occurs is called the crossover altitude (normally around FL 310 when using
Managed Speed, but this does vary depending on whether you are climbing or descending or, using Managed or
Selected Speed).
The crossover altitude may be different when using Managed Speed or Selected Speed as the system can use
different Speeds/Mach when climbing or descending. Use the PERF CLB or PERF DES page to view the
Managed Speed/Mach (and if Selected Speed is used the Speed/Mach used for Selected Speed). For example, in
the climb the Managed Speed may be 305/0.82, but if a Selected Speed of 320 Kts is used it may be 320/0.84.
Page 2 of 29
V1.1
June 2007
.c
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
When
the speed is Selected, the pilot can do the switching manually by pressing the SPEED/MACH pushbutton on
the FCU. When the target speed is Managed, the FMGC commands the switchover automatically as a function of
the ECON MACH value.
c u -tr a c k
THR(ust) Mode
When in THR(ust) mode the A/THR will command an amount of thrust. The FMA first column will display THR
along with the associated type of THRUST mode (e.g. THR CLB, THR DCLB1(2), THR IDLE or THR DES).
This amount of thrust is usually fixed (in the case of THR CLB, THR DCLB1(2) or THR IDLE), but can sometimes
be variable (in the case of THR DES).
Interaction Between AP/FD And A/THR Modes
The AP/FD vertical pitch modes can control a target SPEED/MACH or a vertical trajectory (or path); the A/THR
modes can control a fixed THR or a target SPEED/MACH. AP/FD and A/THR cannot simultaneously control a
target SPEED/MACH.
Consequently the AP/FD pitch modes and A/THR modes are integrated as follows:
If an AP/FD pitch mode controls a vertical trajectory, the A/THR mode controls the target SPEED/MACH.
If an AP/FD pitch mode controls a target Speed or Mach, the A/THR mode controls the THR.
If no AP/FD pitch mode is engaged, the A/THR mode reverts to SPEED/MACH mode.
In other words, the selection of an AP/FD pitch mode determines the associated A/THR mode.
FMA INDICATIONS
Lateral and Vertical Modes of the FMGS can be either:
Armed,
Engaged, or
Disengaged.
The AP/FD Vertical Modes are displayed on the second column of the FMA.
The AP/FD Lateral Modes are displayed on the third column of the FMA.
For both the Vertical and Lateral Modes:
The first line displays the Engaged Mode in green.
The second line displays the Armed Mode(s) in blue or magenta (if a constraint is involved). In some
cases for Vertical Modes two modes may be armed at the same time (e.g. ALT and FINAL).
The third line displays Special Messages or AP/FD Common Modes (e.g. ROLLOUT or FLARE).
What is chiefly needed is skill rather than machinery. (Wilbur Wright, 1902)
FMGS FLIGHT PHASES

The vertical flight plan is divided into Flight Phases. For each Phase, the FMGS computes the optimum Speed or
Mach profile. You need to understand what each Flight Phase means, what Speed profile it uses and the
Switching Conditions that the FMGS uses to change the Flight Phases.
The Flight Phases are:
Preflight - Takeoff - Climb - Cruise - Descent - Approach - Go-Around - Done.
The FMGS Flight Phases are NOT related to the FWC Phases (which are used to inhibit/display ECAM Warnings
and Cautions and Take Off and Landing Memos).
Page 3 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
Each
FMGS Phase except the Preflight and Done Phases has a Performance (PERF) page. The PERF pages
display performance data, speeds related to the various phases, and predictions.
c u -tr a c k
Pressing the PERF key on the MCDU calls up the performance page for the current active Phase. Performance
pages relating to Phases already flown are not available. To determine which Flight Phase the FMGS is currently
in, select the MCDU PERF page. The current Flight Phase title will be GREEN large font (e.g. DES ). Non current
Flight Phases titles will be WHITE large font (e.g. CLB ).
The two most important Flight Phases for the purposes of this discussion are the Descent and the Approach
Phases, but all are included for completeness.
FLIGHT PHASE
PREFLIGHT
SRS takeoff mode engaged and N1 > 85 % (EPR

1.25) or Ground Speed > 90 kt.
TAKEOFF
V2 (V2 + 10, all engines)
At ACCLN ALT or by engagement of another

vertical mode.
CLIMB
ECON CLB SPD/MACH
Reaching cruise FL
CRUISE
DESCENT
APPROACH
GO AROUND
No Step Descent, and distance to destination <

200 NM, or all engine operative and selected
altitude below Max (FL 200, highest DES ALT
CSTR)
ECON CRZ MACH
Overflying the Decel pseudo waypoint with

NAV (or LOC*/LOC) mode engaged and
altitude < 7,200 AGL, or
Manual activation of the approach phase.
To Go Around: When thrust levers at TOGA

detent, or
To Done: 30 seconds after landing, or
To Climb: When inserting a new CRZ FL
To Approach: Manual activation of the APPR

Phase, or
To Climb: Above acceleration altitude by:
ECON DES MACH/SPD
VAPP (GS Min)
VAPP or current SPD, whichever is

greater.
DONE
Selecting ALTN, or
Inserting NEW DEST and CRZ FL
To Preflight when INIT or PERF key depressed.
ND SYMBOLOGY
Familiarity with the symbology on the ND can help you monitor your descent (after all thats why they are
displayed). Know what youre looking at and what the symbols and their colours mean. They can be a great help
to plan ahead so that you can anticipate what will occur next and produce an expeditious and efficient approach
and arrival.
T/D
The top of descent displayed on the FPLN page (T/D) and on the ND
is a position that the FMGS calculates,
assuming that the aircraft will begin its descent in DES mode with Managed speed, and that the system will guide
the aircraft along the FPLN track and the descent profile computed is with all the vertical FPLN data (ALT CSTR,
MANAGED MACH/SPEED, SPD CSTR, SPD LIMIT and inserted winds) to reach VAPP at 1,000 feet AGL.
Note: The ND does not display the top of descent arrow when HDG (or TRACK) mode is engaged.
Page 4 of 29
V1.1
June 2007
!
O
W
y
bu
to
k
lic
.c
Level Off (Climb/Descent)
The level off arrow

(climb),
FCU selected altitude.
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
(descent) gives the point on the flight plan where the aircraft will reach the
Continue (Climb/Descent)
The start of climb
or continue descent
leave the current flight level.
shows the point on the flight plan where the aircraft is predicted to
Intercept Point
The intercept symbol
shows the point on the flight plan where the aircraft will intercept the FMGC computed
vertical descent profile. It is displayed in white if DES mode is not armed and in blue when DES mode is armed.
It can appear if the aircraft is either above or below the FMGC computed descent profile.
If Above The FMGC Profile
If the aircraft is above the descent profile and in Managed Speed, the speed will increase toward the upper limit of
the Managed Speed target range. If the speed reaches the upper limit, the aircraft will maintain the speed but will
deviate above the profile (A/THR at IDLE).
The ND Intercept Point assumes the aircraft will return to the profile using:
Idle thrust,
Half speedbrake extension, and
ECON speed plus a margin (until intercepting the profile).
When this symbol reaches the next ALT CSTR waypoint EXTEND SPD BRK appears on the PFD and MCDU
indicating that speedbrakes must be extended in order to match the next altitude constraint. This is an advisory
message.
Note: When DES mode is engaged, the speedbrake extension will not necessarily increase the descent rate. It
does so only if the aircraft is above the profile. If the aircraft is on or below the profile the AP will maintain the
aircraft on profile (or intercept the profile from below) and the A/THR will add thrust to keep the aircraft within the
speed target range.
If Below The FMGC Profile
The system maintains the target speed (Managed or Selected speed) with the A/THR in SPEED/MACH mode, and
at:
1,000 ft/min rate of descent (if the aircraft is flying an IDLE segment), or
500 ft/min rate of descent (if the aircraft is flying a GEOMETRIC segment),
until it reaches the constraint altitude or intercepts the profile.

Arrow Symbol Colours (T/C, T/D, Level Off, Continue, Intercept Point)
The various arrow symbols are coloured blue
if using a Managed mode or it is armed (CLB or DES), magenta
if a constraint or white
if using a Selected mode (OP CLB, OP DES, V/S or FPA). The T/D arrow is
always white as there is no automatic descent (see initiating descent).
Speed Change
The speed change waypoint
SPD LIM).
represents the point(s) of the flight plan where the speed has to change (e.g.
Page 5 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.c
Decel
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
The decelerate waypoint D represents the point of the flight plan where the aircraft is predicted to decelerate for
approach. It is displayed in magenta when in Managed speed and NAV or APPR mode is engaged. Displayed in
white when in Selected speed mode or HDG/TRK mode. Automatic decelerations occur only when displayed in
magenta.
Energy Circle
The energy circle
is indicated by an arc drawn 20. The radius corresponds to the required
distance to land from present position. The energy circle computed by the FMGC is available in ROSE NAV and
ARC modes only.
Waypoint Altitude Constraints
The constraint waypoint (a circle around the waypoint) is displayed at flight plan waypoints where an altitude
constraint (speed constraints are not displayed on the ND with circles) is defined:
Magenta when the ALT CSTR is predicted to be satisfied.
Amber when the ALT CSTR is predicted to be missed.
White when the ALT CSTR is not taken into account by the guidance and the NAV mode is engaged (e.g.
OP DES).
Not displayed when in any other lateral mode except NAV (e.g. HDG).
DESCENT MODE (DES)

This mode would have to provide the most confusion for pilots when they are trying to monitor the Airbus during
descent. If you can understand what the FMGS is trying to achieve and how this translates into AP/FD and A/THR
commands when in the DES mode then you can rightfully call yourself an Airbus pilotif you cant, then youre a
passenger.
There are two kinds of airplanes those you fly and those that fly you. You must have a
distinct understanding at the very start as to who is the boss. (Ernest K. Gann)
DES mode provides Managed vertical guidance along an FM computed vertical descent profile. The system
computes this flight path backwards from the Decel point up to the top of descent (T/D) at the cruise flight level with
respect to the speed and altitude constraints. The Decel point is where the guidance begins the deceleration to
VAPP, to be reached at 1,000 feet above touch down on the final descent path.
The descent profile takes into account wind data and data from the lateral and vertical flight plans (speed and
altitude constraints and SPD LIM), and it is based upon the Managed descent speed profile. It does not take
holding patterns into consideration.
Initiating descent (DES Mode)
The aircraft will not start its descent automatically when reaching the top of descent (T/D). In order to initiate the
descent, you set the ATC lower clearance altitude on the FCU, then push the ALT selector knob. The aircraft will
then descend immediately.
If the descent is initiated before the FM computed T/D, the aircraft descends at a constant V/S converging
on the descent path from below. The A/THR operational mode will be SPEED/MACH.
If the descent is initiated after the FM computed T/D, the aircraft descends at idle thrust and attempts to
converge on the descent path from above. The A/THR operational mode will be THR IDLE.
If the descent is initiated at the FM computed T/D, the aircraft is descending on the FM calculated vertical
descent profile. The A/THR operational mode will be THR DES.
Page 6 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.c
Descent Profile Segments
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Internally, the computer divides the descent path into various segments, depending on the relative positions of the
constraints. It starts at top of descent (T/D) by setting up an Idle segment that takes the aircraft down to the first
constraint, and follows this with Geometric segments between constraints.
The descent profile has several segments:
Repressurization segment. When necessary, this produces a repressurization rate for the cabin during
descent. It is a function of the destination airport altitude and the selected cabin rate (defaulted to 350
feet/min but this can be modified). Dont worry about this segment. Practically it has little bearing on the
vertical descent.
Idle path segment. The AP/FD controls the speed and A/THR stays at idle thrust. Guidance computes this
profile from T/D or the end of the repressurization segment to the first vertical constraint that cannot be
flown at idle thrust.
Geometric path segment(s). The AP/FD controls the vertical path, and A/THR controls the speed. These
segments take the aircraft from the first constraint that cannot be flown at idle thrust (and any subsequent
constraints) to the Decel Point. Note that there may be more than one Geometric segment and the various
Geometric segments may be at different descent angles to satisfy the various altitude or speed constraints
at the waypoints contained in the Geometric segments.
When DES mode is engaged, NAV mode is engaged (or another way to look at it is, you wont be able to engage
DES mode unless you are in NAV mode), and the system takes into account all altitude and speed constraints.
Profile Monitoring
The key parameter for monitoring the descent is the vertical deviation (VDEV) displayed on the PFD and on the
MCDU PROG page, which indicates whether the aircraft is on, above, or below the FM calculated vertical descent
profile.
Well thats what the books say. Ensure that you mentally compute your own vertical descent profile and compare it
with the FM calculated vertical descent profile. Blindly trust VDEV at your own peril!
Its not a matter of IF youll get caught out, but WHEN youll get caught out (and by how much)!
Page 7 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.c
If the aircraft is on the descent profile
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
The aircraft is considered to be on the vertical profile when it is within 50 feet of it. VDEV is close to zero, and the
system predicts that it will match constraints until the aircraft levels off at the next FCU altitude.
The A/THR adjusts the thrust for the particular segment. The first FMA column may display THR IDLE or
SPEED/MACH (depending on whether the Managed Speed reaches the upper or lower limit of the Managed
Speed target range) but will normally display THR DES.
If the aircraft is above the descent profile
VDEV is down on the PFD and positive on the PROG page.
The A/THR sets THR IDLE and if in Managed Speed the AP increases speed up to the maximum of the Managed
Speed target range by calling for down elevator. If the aircraft reaches the upper limit of the Managed Speed target
range, the aircraft diverges from the FM calculated vertical descent profile and maintains the upper limit speed.
If the aircraft is below the descent profile:
VDEV is up on the PFD and negative on the PROG page. The system maintains the target speed (Managed or
Selected Speed).
The A/THR is in SPEED (MACH) mode with a 1,000 ft/min rate of descent (if the aircraft is flying an Idle segment),
or 500 ft/min (if the aircraft is flying a Geometric segment) until the profile is regained.
Managed Speed
When the speed is Managed, a target speed range displayed on the PFD defines acceptable speed variations
around the nominal Managed descent speed target (normally 20 Kts).
If the aircraft is on the descent profile the AP will maintain the Managed target speed. The AP will vary the
speed within this managed target speed to account for minor variations in Winds, Temps, Eng A/I being
selected on etc. to keep on the previously FM calculated vertical descent profile. The A/THR will be in THR
DES mode (you have to be on profile to get this mode), but will most likely be commanding Idle (check on
the EW/D as the FMA will display THR DES).
If the aircraft is above the descent profile the AP commands down pitch and the speed increases toward
the upper limit of the Managed target speed range as the aircraft attempts to converge on the descent
profile from above. If this does not increase the descent angle enough, the aircraft deviates (goes high)
from the descent profile with the A/THR at THR IDLE.
If the aircraft is below the descent profile, the AP maintains the Managed target speed until it reaches the
vertical profile at reduced V/S (either 1,000 ft/min for an Idle segment or 500 ft/min for a Geometric
segment). The lower margin becomes effective when the aircraft is on the descent profile but has to lose
speed in order to stay on it. The A/THR may go into SPEED/MACH mode.
The ND shows an intercept symbol that indicates the position where the system predicts that the aircraft will be
back on the descent profile. (See MCDU message EXTEND SPD BRK and ND Intercept Point Symbology).
Too Steep Path
A segment between two constraints is called TOO STEEP PATH when the FMGS predicts that it is impossible to fly
it at the pre-planned speed with half speedbrakes extended.
TOO STEEP PATH AHEAD appears on the MCDU scratchpad when the system predicts this situation. TOO
STEEP PATH is also displayed on the FPLN page. The FM does not furnish predictions for the waypoints included
in the TOO STEEP PATH segment.
When the aircraft reaches the beginning of the too steep path segment, the FM recomputes the VDEV using an idle
segment from the end of the too steep path segment. The VDEV makes a jump because it is related to a new
profile.
Page 8 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.d o
o
c
.
VDEV
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
The pilot sees a vertical deviation symbol (VDEV magenta doughnut) along the ALT scale on the PFD and a VDEV
value on the MCDU PROG page, so as to monitor the aircraft vertical position on the calculated FM descent profile.
The aircraft may deviate from the DES path while DES mode is engaged if:
Unexpected wind conditions are encountered, or
Anti-icing is turned on, or
Lateral FPLN is modified.
VDEV on PFD and PROG page, predictions on MCDU FPLN page and symbols on ND allow you to assess your
vertical position versus the computed FM descent profile.
OP DES, V/S OR FPA MODE ENGAGED
In either case, the aircraft is no longer guided on the descent profile and altitude constraints are disregarded. If
NAV mode is engaged the ND displays a white circle on waypoints with an altitude constraint. If NAV mode is
disengaged, the circles are removed.
The PFD still shows VDEV for reference purposes (but depending how much the actual lateral and vertical descent
profile differs from the FM calculated vertical descent profile, the VDEV may give inaccurate or incorrect
information).
The target altitude is always the FCU selected altitude (shown in blue). On the ND, the level-off symbol is blue (no
constraint).
If NAV mode is engaged and the speed target Managed, speed constraints are taken into account.
CONSTRAINTS
General
Altitude or Speed constraints are only taken into consideration by the FMGS in the Climb, Descent, or Approach
Phases, but never in the Cruise Phase. Both types of constraints are ignored if entered while in the Cruise Phase.
No constraint can be associated with Go Around waypoints.
CLB Mode
When CLB mode is engaged (always associated with lateral NAV mode), the system takes into account all
constraints defined by the database or manually entered by the crew.
Nevertheless this mode has the following particularity:
When in CLB mode if the system predicts that it will miss an altitude constraint, it will not modify the target
speed. In this case, the pilot may select an appropriate speed in order to meet the ALT CSTR.
Altitude constraint
Altitude constraints may be attached to specific waypoints in the Climb, Descent, or Approach Phases.
To meet the altitude constraint, the aircraft must fly over the waypoint at an altitude equal, above or below the
altitude constraint as specified by the pilot or the database.
An altitude constraint is considered as missed if the system predicts more than 250 feet of difference between the
constraint value and the predicted aircraft altitude.
Altitude constraints are observed in CLB or DES or APP NAV-FINAL modes.
The database may contain an altitude constraint window (two altitudes between which the aircraft must fly passing
over a given waypoint), but the pilot cannot enter such a constraint manually.
Page 9 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.c
Speed constraint
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Speed constraints may be attached to specific waypoints in the Climb, Descent, or Approach Phases.
To meet the speed constraint, the aircraft must fly over the waypoint with a speed equal or less than the speed
constraint.
A speed constraint is considered as missed if the system predicts an aircraft speed 10 Kts greater than the speed
constraint.
Speed constraints are observed when NAV mode is engaged and the speed target is Managed. Otherwise speed
constraints are disregarded.
MCDU Constraint Symbols
When a time, speed or an altitude constraint is part of the vertical flight plan, it appears on FPLN A page (the actual
numbers in magenta) only at the time of insertion or while predictions are not yet available.
Once available, the actual time, speed and altitude predictions are displayed for all FPLN waypoints: when a speed
or an altitude constraint is in effect at a waypoint, a star symbol appears adjacent to the speed or altitude
prediction. If the star is magenta the constraint is predicted to be matched. If the star is amber, the constraint is
predicted to be missed. If the aircraft is predicted to miss the constraint by more than 10 knot, the MCDU
scratchpad displays SPD ERROR AT WPT ---- .
Note: If an altitude constraint is predicted as missed, the system tells you what will be the error at the specific
waypoint by accessing a VERT Revision at that waypoint.
MCDU Constraint Predictions
The database may define an altitude constraint and speed constraint for each waypoint of the Climb, Descent, and
Approach Phases, or the pilot may insert such constraints manually (except at origin, destination, FROM and
pseudo waypoints).
The constraints (the actual numbers, e.g. 250/130) are displayed in magenta as long as predictions are not
completed.
Once predictions are available, constraints are replaced by computed speed and altitude predictions (in green for
all waypoints except the TO and DEST waypoints which are displayed in white) preceded by stars (see above).
Learning the secret of flight from a bird was a good deal like learning the secret of magic from a
magician. After you know what to look for you see things that you did not notice when you did
not know exactly what to look for. (Orville Wright)
PSEUDO WAYPOINTS
Pseudo waypoints are computed geographical positions corresponding to an event in the vertical flight plan; T/C
(top of climb), T/D (top of descent), SPD LIM (speed limit), DECEL (deceleration for approach) etc. The MCDU
FPLN shows them as waypoints in parentheses.
MCDU MESSAGES
Messages displayed on the MCDU are of two types and displayed in two colours:
Type I: a direct result of a pilot action, or
Type II: information about a situation or a call for pilot action.
Amber (A): important
White (W): less important.
Type II messages are stored in a first-in/first-out message queue (5 messages max.) They are suppressed if
correct data is entered or when they no longer apply.
Page 10 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.d o
o
c
.
The
flight crew can clear all messages by pressing the CLEAR key on the MCDU console.
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Some of the more common MCDU Messages displayed during descent and their meanings are:
TYPE/
COLOUR
MESSAGE
CONDITIONS
CSTR DEL ABOVE CRZ FL
II/W
This appears when a flight plan altitude constraint has been

deleted because the flight crew has inserted a cruise flight
level or step-down altitude that is at or below the flight plan
constraint.
DECELERATE (Also displayed on

PFD)
II/A
The aircraft is still in cruise phase and managed speed after it

reaches the top of descent and it has not begun the descent.
ENTER DEST DATA
II/A
The flight crew has not entered wind, QNH, or temperature for
the destination, and the aircraft is 180 NM out.
EXTEND SPD BRK
II/W
DES mode is engaged, idle is selected and the aircraft must

decelerate in order to recover the path, or to respect an
altitude constraint, a speed limit or a speed constraint.
NAV ACCUR DOWNGRAD (also

displayed on ND)
II/A
NAV accuracy has been downgraded from HIGH to LOW.
NAV ACCUR UPGRAD (*EFIS ND)
II/A
NAV accuracy has been upgraded from LOW to HIGH.
RETRACT
SPD
displayed on PFD)
II/W
Speedbrakes are extended, DES mode is engaged and:
BRK
(also
SET MANAGED SPEED (SET

MANAGED SPD is displayed on
PFD)
II/A (W)
ALT or ALT* engages, or
the aircraft is below the path, or
CONF 3 or full is reached.
The target speed is Selected for the current phase, but there
is no preselected speed for the next flight phase.
When this is so, this message is displayed at transitions from
climb to cruise, and from climb or cruise to descent.
The message is always displayed at the transition to descent
from climb or cruise if Selected Speed is active.
It is not displayed if Managed Speed is active.
SPD ERROR AT WPTXX
II/W
In lateral Managed flight, the system predicts that the aircraft

will miss a speed constraint by more than 10 kt.
When the prediction changes to bring the miss within 5 kt, the
message is cleared.
SPD LIM EXCEEDED
II/A
The aircraft is more than 150 feet below the speed limit
altitude and more than 10 kt over the speed limit.
TOO STEEP PATH AHEAD
II/A
The system displays this message in Cruise Phase if the

aircraft is within 150 NM of its destination or in Descent or
Approach Phase and in NAV mode and the descent profile
contains a segment that is too steep.
THINGS TO WATCH OUT FOR

SPEED/MACH Crossover
When in Managed Speed the FMGC determines automatically when it should change from SPEED to MACH in the
climb and vice versa in the descent. The point at which this occurs is called the crossover altitude. The same thing
also occurs if you use Selected Speed. This automatic change from SPEED to MACH in the climb and vice versa
Page 11 of 29
V1.1
June 2007
.c
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
in .the descent is to prevent overspeeds (in the climb if you remain in SPEED you will eventually reach Mmo and . dino c u - t r a c k .
the descent if you remain in MACH you will eventually reach Vmo).
c u -tr a c k
So far, so good.
The problem occurs if you manually select either SPEED or MACH by using the SPD/MACH Pb on the FCU.
There will now be no automatic change at the crossover altitude.
If you manually select SPEED mode in the climb, the aircraft will climb at that Selected Speed. As you gain altitude
the Mmo will start decreasing (Vmax will start decreasing on the PFD) and as you continue climbing the Selected
Speed will eventually reach Mmo (since at a constant IAS as you climb the Mach No. increases). The reverse
happens during descent if you manually select MACH. As you descend the constant Mach No. results in
increasing IAS and you eventually reach Vmo.
If you decide to use the SPD/MACH Pb to manually select a SPEED or MACH the FCU SPEED/MACH window will
display what SPEED/MACH you have selected.
As a general rule if you are going to manually select a SPEED or MACH by using the FCU SPD/MACH Pb, use
MACH in climbs and SPEED in descents to avoid this problem. The reducing gap between your currently Selected
SPEED or MACH and Vmax on the PFD speed tape should also be a huge hint. If youve got the wrong mode
selected, simply push the SPD/MACH Pb to change into the mode you want and (re)set the Selected SPEED or
MACH in the FCU window or simply use Managed Speed.
Decel Point
If you are given extensive radar vectors (and so are using HDG and probably in Selected Speed due to ATC speed
control), you will never sequence the Decel Point and so you will remain in the Descent Phase. You can get to the
situation in the later stages of the arrival that you push for Managed Speed and the speed target jumps up to 250
Kts (probably because that was the last SPD LIM in the FPLN), the A/THR pours on thrust and you start rapidly
accelerating. Just what you dont need when just about to intercept the LOC.
The solution: manually Activate the Approach Phase at a suitable time, early in the arrival. Keep an eye out for the
Decel Point on the ND (in white if in HDG). If you pass abeam its position it can remind you to activate the
Approach Phase.
Descent Phase > 200 NM From DEST
If the FCU selected altitude is lower than the previous CRZ FL and if the FPLN DTG to DEST is more than 200 NM,
the CRZ FL on the PROG page changes and you remain in the Cruise Phase. In effect the FM thinks you want to
do a Step Descent and recalculates the FM predictions and Managed speed target for that situation.
In that case MACH (or SPEED) target is Managed as follows:
At the start of the descent, the MACH target is the Managed Mach number at the initial cruise flight level.
When the aircraft reaches the new flight level, the Mach target switches either to the MACH number for the
lower CRZ FL, or to the SPEED for the lower CRZ FL if the aircraft reaches the crossover altitude. This
logic prevents the aircraft from exceeding Vmo during descent.
The indications you get in this situation are:
White MCDU Scratchpad message CSTR DEL ABOVE CRZ FL (if a constraint has been entered at a
waypoint prior to the FM calculated T/D point)
CLR the Scratchpad A new white MCDU Scratchpad message: NEW CRUISE ALT FLXXX
FMA Indications: DES (a cruise descent or in other words a Step Descent)
PFD Indications magenta Managed Speed (Cruise Speed) with NO target speed range
No magenta VDEV on PFD
MCDU PERF Page Title CRZ in green (Cruise Phase is active)
MCDU PROG Page Title CRZ in green (Cruise Phase is active) and CRZ ALT FLXXX and no VDEV.
Page 12 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
If the
FCU selected altitude is lower than the previous CRZ FL and the aircraft is within 200 NM of its destination,
the system activates the Descent Phase.
c u -tr a c k
The pilot may reactivate the Cruise Phase by entering a new cruise flight level in the MCDU PROG page.
This is a common problem when arriving from China through SIERA. You quite often get numerous ATC descents
in Chinese airspace and all that happens is that a new cruise altitude is selected. The Managed Speed will remain
as the Cruise Managed Speed (quite often less than your ECON or Managed Descent speed due to the low cruise
altitude). Since you remain in the Cruise Phase (effectively doing a Step Descent) the Altitude and/or Speed
constraints that you have (should have?) inserted at SIERA are ignored, with the result that you get high on the
required vertical profile and if nothing is done will diverge further above profile. If youre not ready for it you can get
really high.
There are two ways to address this problem:
Consider using Selected Speed and OP DES and S/B and manually calculate the vertical descent profile,
or
To force the FM to enter the Descent Phase when greater than 200 nm from DEST and above FL 200,
momentarily set the FCU altitude to below FL 200, push or pull the ALT select knob (Managed or Selected
descent) and then reset the desired altitude on the FCU.
S/B While in DES Mode

You can only use S/B in DES mode if above the FM computed descent profile. If you use it on or below the profile
the A/THR will add thrust to maintain the speed target (Managed or Selected). If you need to expedite your
descent use OP DES, which will command THR IDLE.
S/B At Low Speeds
Below about 220 Kts and certainly less than 200 Kts, the S/B is relatively ineffective. On the Airbus it is really hard
to Slow Down and Go Down. You need to think ahead and mentally monitor your descent profile. If you need
S/B close to the LOC it is probably because you stuffed up your descent profile.
Using S/B will cause VLS ( Prot and Max as well) to increase. When at low speeds, particularly if clean, using
S/B can cause VLS to increase above Green Dot or even your current IAS. If VLS increases to above your current
speed and the A/THR is active it will increase thrust to maintain the new higher VLS. This situation may require
you to restrict the amount of S/B that you use (which results in a lower VLS and a reduced V/S). If you are really
high consider selecting some flap to lower VLS so that more S/B can now be used.
V/S (and S/B)
V/S is a Basic Mode. If you select a V/S then the aircraft will achieve that V/S. The FMGC pitch mode guides the
aircraft to the target V/S (or FPA but it is very rare to use FPA during descents). The corresponding A/THR mode
is SPEED/MACH.
The V/S (FPA) guidance has priority over the speed guidance. If the selected target V/S or FPA is too high
(relative to the current thrust condition and speed), the FMGC will steer the aircraft to the target V/S or FPA, but the
aircraft will also accelerate. When the speed reaches the authorized limit, the V/S or FPA decreases automatically
to maintain the maximum speed limit (an automatic mode Reversion occurs).
If you use S/B when using V/S ensure that the thrust is at IDLE on the EW/D (the A/THR mode will probably be
SPEED/MACH even at IDLE thrust). If it is not the A/THR will add thrust to maintain the Speed with the selected
V/S.
VDEV
The VDEV displayed on the altitude scale of the PFD and on the MCDU PROG page is the vertical deviation from
the FM calculated descent profile. This descent profile is calculated prior to T/D and remains fixed until the FM is
forced to make a recalculation (e.g. by doing a DIR TO, (re)inserting altitude or speed constraints or reinserting the
Cruise Alt on the PROG page).
Page 13 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
If you
alter any of the conditions or constraints that the FM used in calculating the vertical descent profile or the
lateral FPLN, then that calculated descent profile will NOT reflect what the aircraft is actually achieving. This
results in the FM calculated VDEV (and the information displayed on the PFD and PROG page) being incorrect, or
in other words, what the aircraft is actually doing bears little or no relationship to the pre T/D FM calculated descent
profile.
c u -tr a c k
So the bottom line is, the VDEV information is only of any value if the aircraft is flying or is very close to both the
lateral and vertical profile that the FM used to calculate the vertical profile. So dont get sucked in and blindly follow
the VDEV. You still need to mentally compute your own vertical profile to assess whether you are high, low or on
the vertical profile.
Speed (IAS)
Your speed (IAS) is an integral part of the vertical descent profile.
You have to slow up at some stage in the approach and this is usually accomplished by either flying level (and this
is what the FM uses to make its calculations and predictions) or by reducing your V/S (which is what we strive to do
as pilots to maintain a continuous descent profile).
In both cases the vertical profile is affected. So dont forget to include speed in your descent profile planning and
monitoring.
Entering A Managed Speed
As long as the Descent Phase is not active, the PERF DES page may be used to insert either a Speed or a Mach
number or both to replace the FM computed ECON Managed descent speed.
The FMGS then uses your manually inserted Speed/Mach Managed Speed instead of its automatic ECON
Managed speed for computing the descent profile and determining the descent Managed speed profile. Note that
even though you have manually modified the FM computed ECON descent speed, it is still considered by the FM to
be Managed Speed its just different from what the FM automatically computed.
When the system switches to the Descent Phase, it sets the Managed target speed to the entered speed. From
there, you can only modify the speed by using the FCU selector knob only (i.e. Selected Speed). Once in the
Descent Phase, the pilot cannot change the Descent Managed Speed again.
GIGO (Garbage In/Garbage Out)
The part of the FMGS that computes predictions and descent profiles is essentially a computer program. Like all
computer programs if you input incorrect or inaccurate information (Garbage In) you will get incorrect or inaccurate
information as an output (Garbage Out).
The FMGS will only be as good as the information that you insert into it. The more accurate information that you
can provide it, the better will be its predictions and accuracy.
Take the time to accurately and correctly insert such things as the STAR (and Transition), Altitude and Speed
constraints, SPD LIM, Managed Descent Speed, Winds and Temps. Throughout the descent and arrival
continually update the lateral (and to a lesser extent the vertical) FPLN to reflect what ATC is currently giving you
and what you anticipate they will give you in future (think ahead) by using DIR TO or by clearing the FROM
waypoint to get a sensible TO waypoint.
This will give you more accurate predictions, DTG and VDEV.
Blindly Accepting The FM Computed Data/Predictions
Do NOT fall into this trap! You must mentally calculate your own independent vertical profile based on the
ACTUAL aircraft performance (not the data used prior to T/D).
The FM computed data and predictions are only as good as the information input to the FM. The vertically
calculated FM descent profile is computed prior to T/D and once in the Descent Phase is fixed in space.
Page 14 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.d o
c u -tr a c k
As. soon as you go into HDG, Select a Speed, get track shortening or anything, the FM calculated vertical descent
profile will be in error to what you are now actually doing. VDEV will also be in error.
c u -tr a c k
This also applies to not only the arrival but to constraints during the descent. For example ATC requires you to
cross MELON at 280 Kts and FL 130 use your actual V/S, altitude and speed to lose (i.e. time required to achieve
the altitude/speed constraint) and your current G/S and DTG (i.e. ETA at the waypoint) and then decide if you
require S/B (high) or need V/S (low).
This is one of the most common mistakes you will make during descent monitoring.
Ensure you use the FCTM Descent Monitoring formula to cross check the FM vertical profile. You have been
warned!!
Pitch Down (And Possible Overspeed)
If ATC requires you to reduce speed (so you use Selected Speed) to below the speed that the FM used to calculate
the vertical descent profile and you are in DES Mode, the A/THR will set IDLE and you will diverge above the FM
calculated vertical profile. VDEV will also be increasing.
If the ATC imposed speed control is now no longer required you can reset Managed Speed. As you are above the
FM calculated vertical descent profile and at a speed lower than Managed Speed the following will occur
simultaneously:
The AP will pitch the aircraft down to rejoin the FM calculated descent profile from above, and
The A/THR will increase thrust to accelerate to Managed Speed.
The IAS will rapidly increase. You have now set yourself up for a self-induced overspeed. The Airbus is notorious
for doing this as the AP and A/THR may not react fast enough to prevent this.
Any time the pitch attitude is less than 2.5 nose down, watch the IAS very carefully. If it gets to 5 nose down you
will very likely have to manually intervene to prevent an overspeed.
The following are the manual intervention actions to prevent an overspeed in this situation:
Selected Speed (decease the Selected Speed if required to pitch the aircraft up). Also removes the
Managed Speed target range of 20 Kts,
Select OP DES (A/THR sets IDLE). Also removes the Managed Speed target range of 20 Kts), or
Disconnect the AP and manually pitch up (this should be your last resort, but if the IAS increases rapidly
may be your only option).
Use common sense here. Its better to accept a slight overspeed by using a calibrated and moderate pitch
up than to contain the speed by using an aggressive pitch up with increased G loads dont forget about
the people possibly walking around in the cabin. People have been injured by pilots hooking on too much
G to prevent an overspeed.
If you cant afford to do something right, then be darn sure you can afford to do it wrong.
(Charlie Nelson)
Page 15 of 29
V1.1
June 2007
!
O
W
y
bu
to
k
lic
.d o
o
c
.
AIRBUS
DESCENT MONITORING (A VISUAL GUIDE)
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
The FM will calculate a T/D point assuming that the aircraft will begin its descent in DES mode with Managed
speed, and that the system will guide the aircraft along the lateral FPLN track and the descent vertical profile
computed is with all the vertical FPLN data (ALT CSTR, MANAGED MACH/SPEED, SPD CSTR, SPD LIMIT and
inserted winds) to reach VAPP at 1,000 feet AGL.
Once the FM sequences into the Descent Phase the FM vertical descent profile is fixed (or frozen in space) using
all the pre T/D constraints (speeds and altitudes), SPD LIM, Managed Speed (Mach) and Winds. The only way to
change this fixed in space vertical profile is to force the FM to re-calculate a new descent profile. This can be
done by performing a DIR TO, or changing the pre-existing or entering new altitude and/or speed constraints.
You cannot however change the Managed Speed used to calculate the descent profile. Selecting a different speed
or changing the vertical descent mode (e.g. selecting V/S or OP DES) will also not change the FM vertical descent
profile.
Did you get all that? Lets break up the descent into two separate sections:
From the Decel Point to the DEST runway (Approach Phase), and
From T/D to the Decel Point (Descent Phase).
Decel Point To Threshold

Lets take a look at how the FM calculates the vertical descent profile from the Decel Point to the DEST runway
landing threshold.
The FM actually works backwards from the DEST runway landing threshold and makes several assumptions (thats
the way it has been programmed):
The aircraft will pass over the DEST runway landing threshold at + 50, in Config FULL (or Config 3 if that
has been selected on the PERF APP page) provided no abnormally high altitude constraint or TOO STEEP
PATH is input at an earlier waypoint,
The aircraft will descend along the FPLN stored pseudo glidepath (which is part of the FMGC database) for
the approach selected for the DEST runway (this is usually a 3 glideslope for most ILSs and Non
Precision Approaches, but not always),
The aircraft will decelerate to reach VAPP at 1,000 AAL, configuring with flap as the aircraft decelerates in
level flight (1,500 AAL if no higher Altitude Constraints are entered into the FPLN) with Managed Speed to
the various Characteristic Speeds (GD, S, F and VAPP). The aircraft decelerates automatically at the
DECEL pseudo waypoint when Managed Speed is active and NAV mode is engaged (DECEL point
displayed in magenta). In the Approach Phase the A/THR maintains the manoeuvring speed of the current
configuration (GD, S, F or VAPP).
The FMGS will use level segments for deceleration (rather than a continuous decelerating descent), but
any SPD LIM will be a decelerating descent.
Crosses DEST
landing threshold
at +50 in Config
Full (or Config 3)
Level deceleration
at 1,500 AAL (if no
other Alt constraints
input).
Pseudo glidepath
for the selected
approach (usually
3)
1,000 AAL
at VAPP
D
At F
select
Full
At F
select
F3
At S
select
F2
Page 16 of 29
At GD
select
F1
DECEL
point
V1.1
June 2007
.c
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
This
profile assumes the use of Managed Speed in DES mode. After the FM has computed this part of the vertical
descent profile it can display the Decel Point on the ND. The Decel Point is where the Approach Phase will
activate automatically and a deceleration will occur if you are in NAV and Managed Speed.
c u -tr a c k
Practically, this area is where most of the action occurs during an arrival and approach and this is where for the
vast majority of our arrivals we are under ATC speed and altitude control and radar vectors so it is quite rare to be
able to fully utilise all this FM calculated descent information. Most of the time we will have an electronic glideslope
(ILS) to refine our manual descent calculations and raw data (G/S, LOC, DME, VOR).
We will focus more on the previous part of the descent; from T/D to the Decel Point, as this is where the majority of
confusion exists when trying to work out what the Airbus is doing while in the Descent Phase.
To get the full descent and approach picture just join the Approach Phase (diagram above) and Descent Phase
(diagrams below) together at their common point the Decel Point.
T/D To Decel Point (No Constraints At All)
Lets assume for the sake of simplicity that this particular arrival has absolutely no altitude or speed constraints and
no SPD LIM points i.e. a single Managed Speed is used from T/D to the Decel Point. Since there are no altitude or
speed constraints to affect the descent profile this is an IDLE descent segment.
No Alt or Speed
constraints or
SPD LIM.
This is an IDLE
segment.
FM
calculated
T/D
If you were to descend at the FM calculated T/D point in Managed Speed and in DES mode the aircraft would
theoretically follow the FM vertical descent profile.
You would observe the following indications on the PFD, ND and MCDU:
THR DES DES NAV,
The FMA would display
The A/THR will maintain the Managed Speed at IDLE thrust. However the only place IDLE will be
displayed is on the EW/D as the A/THR operational mode will display THR DES as you are on the FM
calculated vertical descent profile, and
VDEV (on the PFD and PROG page) would be zero.
Early Descent
What if you started your descent prior to the FM calculated descent point?
FM
calculated
T/D
Early
descent
VDEV
increasing
VDEV at
maximum
VDEV
decreasing
AP set V/S of 1,000 ft/min

(Idle Segment) or 500 ft/min
(Geometric Segment)
Intercept
Point (ND)
Page 17 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
If you
were to descend in Managed Speed and in DES mode the aircraft would be below the FM vertical descent
profile and would attempt to intercept it from below.
c u -tr a c k
SPEED (MACH) DES NAV,
The A/THR will maintain the Managed Speed,
The AP would set a V/S of 1,000 ft/min in an attempt to re-intercept the FM calculated vertical descent
profile from below (for this particular Idle segment V/S 500 ft/min if a Geometric segment),
VDEV is up on the PFD and negative on the PROG page, and
The Intercept Point is displayed on the ND.
You could of course select V/S 500 ft/min (SPEED V/S NAV) which would have the effect of flattening out the
descent angle and thus intercepting the FM calculated descent profile earlier (and bringing the ND Intercept Point
closer) but why make more work for yourself?
Late Descent
What if you started your descent after the FM calculated descent point?
Late
descent
FM
calculated
T/D
VDEV
increasing
AP sets Max Managed

Speed range, A/THR Idle
VDEV at
maximum
VDEV
decreasing
D
Intercept
Point (ND)
If you were to descend in Managed Speed and in DES mode the aircraft would be above the FM vertical descent
profile and would attempt to intercept it from above.
THR IDLE DES NAV,
The speed will increase toward the upper limit of the Managed Speed target range. If the speed reaches
the upper limit, the aircraft will maintain the speed but will deviate from the profile (A/THR at IDLE).
VDEV is down on the PFD and positive on the PROG page, and
The Intercept Point is displayed on the ND.
The ND Intercept Point assumes the aircraft will return to the profile using:
Idle thrust,
Half speedbrake extension, and
ECON speed plus a margin (until intercepting the profile).
Note: When DES mode is engaged, the speedbrake extension will not necessarily increase the descent rate. It
does so only if the aircraft is above the profile. If the aircraft is on or below the profile the system will add thrust to
keep the aircraft on profile and within the speed target range.
In this late descent situation you could Select a higher speed or use up to full S/B. Both methods steepen the
descent angle, and thus would intercept the FM calculated profile from above earlier (and bringing the ND Intercept
Point closer).
Page 18 of 29
V1.1
June 2007
!
O
W
y
bu
to
k
lic
.c
High Speed Descent
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
What if ATC required you to descend at a speed higher (so you use Selected Speed) than that used by the FM to
calculate the vertical descent profile when in the Descent Phase (remember the FM vertical profile is now fixed in
space)?
A speed higher than used in the FM calculation would result in a steeper descent angle and so you would tend to
go below the FM calculated profile (if you used OP DES).
In DES mode the AP will pitch up slightly to maintain the FM vertical profile (its fixed in space and it wants to follow
the profile when in DES mode) and the A/THR will add a little thrust to maintain the new higher Selected Speed.
The FMA will now display SPEED (MACH) DES NAV,
The A/THR will maintain the new higher Selected Speed,
Low Speed Descent

What if ATC required you to descend at a speed lower (so you use Selected Speed) than that used by the FM to
calculate the vertical descent profile when in the Descent Phase?
A speed lower than used in the FM calculation would result in a shallower descent angle and so you would tend to
go above the FM calculated profile (if you used OP DES).
In DES mode the aircraft will initially pitch up to decelerate to the new lower Selected Speed (and so diverge above
the FM descent profile) and the A/THR will reduce thrust to maintain the Selected Speed, most likely to IDLE.
When the speed has reduced to the lower Selected Speed the aircraft may pitch down slightly in an attempt to
maintain or intercept the FM profile from above (it all depends on how far the speed has been reduced). As the FM
calculated vertical descent profile assumes IDLE thrust and as you are now at a lower speed you will go above the
FM profile in most cases. You will diverge from the FM calculated vertical descent profile further, the longer the
lower speed is used (the aircraft is now flying a shallower descent angle).
The FMA will now display THR IDLE DES NAV,
The A/THR will maintain the Selected Speed,
VDEV (on the PFD and PROG page) most likely will start to increase above profile.
Your only option if you are required to maintain the lower speed is to use S/B to re-intercept the FM profile from
above.
High On Profile
The indications when high on profile are very similar to a late descent. When in Managed Speed in DES mode the
speed will increase above the Managed Speed up to the upper limit of the Managed Speed target range (usually to
a maximum of + 20 Kts) in an attempt to rejoin the FM calculated vertical profile from above.
The FMA will now display THR IDLE DES NAV,
The A/THR will set IDLE thrust, and
The AP increases speed by calling for down elevator. If the aircraft reaches the upper limit of the Managed
speed target range, the aircraft diverges and maintains the upper limit speed, and
VDEV is down on the PFD and positive on the PROG page.
Page 19 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.c
Low On Profile
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
The indications when low on profile are very similar to an early descent. When in Managed Speed in DES mode
the speed will be at Managed Speed in an attempt to rejoin the FM calculated vertical profile from below.
SPEED (MACH) DES NAV,
The A/THR will maintain the Managed Speed,
The AP would select a V/S of 1,000 ft/min in an attempt to re-intercept the FM calculated vertical descent
profile from below (for an Idle segment V/S 500 ft/min if a Geometric segment) until the profile is
regained, and
VDEV is up on the PFD and negative on the PROG page.
T/D To Decel Point SPD LIM Only

Lets use the same arrival, again with no altitude or speed constraints, but this time with a SPD LIM of 250 Kts at
10,000 i.e. Managed Speed is used from T/D to the SPD LIM point and then the SPD LIM Managed Speed
specified (in this case 250 Kts) until the Decel Point.
Once again as there are no altitude or speed constraints to affect the descent profile this is an IDLE descent
segment. The SPD LIM point is NOT a speed constraint. The entire descent uses Managed Speed its just that it
automatically changes to decelerate and reach 250 Kts at 10,000 at the SPD LIM point.
No Alt or Speed
constraints.
This entire segment is
also an IDLE segment.
FM
calculated
T/D
SPD LIM
(250 Kts,
10,000)
D
If you were to descend at the FM calculated T/D point in Managed Speed and in DES mode the aircraft would
theoretically follow the FM vertical descent profile as before.
THR DES DES NAV,
The A/THR will maintain the Managed Speed at IDLE thrust. However the only place IDLE will be
displayed is on the EW/D as the A/THR operational mode will display THR DES, and
In addition because of the SPD LIM there would be:
A magenta ball Speed Change pseudo waypoint displayed on the ND,
SPD LIM would be displayed on the MCDU FPLN page, and
Sequencing the SPD LIM waypoint would result in the Managed Speed reducing automatically to 250 Kts
on the PFD Speed tape (the FMA modes would remain the same, but the aircraft would pitch up slightly
while still descending to decelerate at IDLE thrust to achieve 250 Kts at 10,000).
Page 20 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.c
T/D To Decel Point With An Altitude Constraint
.d o
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Now lets look at an arrival with an altitude constraint that requires more than IDLE thrust to achieve that constraint.
There is no SPD LIM to simplify the explanation.
This segment is an
IDLE segment.
FM
calculated
T/D
An Alt constraint that requires

more than IDLE thrust to achieve
is part of this segment.
This segment is a GEOMETRIC
segment.
MELON
FL 130
While the aircraft is in the IDLE segment it behaves almost exactly the same as we have discussed above for all
the various high/low/on profile and high/low speed cases. The only real difference is that ALT CSTR may be
displayed on the FMA and the ND symbology may be a little different due to the extra altitude constraint.
THR DES DES NAV,
So what happens at the Altitude constraint if we are on profile?

The AP will pitch the aircraft up slightly to maintain the geometric shallower profile and the A/THR will add thrust to
maintain the Managed Speed.
SPEED (MACH) DES NAV
Thats it mystery solved.

T/D To Decel Point With All The Other Variables
The same thing will occur if:
Only a Speed constraint(s), or
A combination of an altitude and a speed constraint is used at the same waypoint(s), or
A combination of an altitude and a speed constraint is used at the same waypoint(s) and a SPD LIM is
included.
All that happens is that the FM will calculate the vertical descent profile to take all these various vertical constraints
and SPD LIM points into consideration by altering the angle of the Geometric segment (or segments if more than
one altitude/speed constraint is used), then adding on the Idle segment to finally work out a T/D point.
All youve got to do then is visualise what happens for the high/low/on profile and high/low speed cases. Try and
visualise what the vertical profile will look like from a side view (as in the diagrams) and where you are in relation to
that profile. That will determine what AP/FD lateral and vertical modes will be engaged or armed and what
operational mode (either SPEED/MACH or THR) that the A/THR will use.
The ND symbology can be a great help here, but only if you know what youre looking at and only if you keep the
lateral and vertical FPLN updated.
Mentally confirm ALL FM generated predictions and ensure you are mentally computing your own vertical descent
profile to compare with the FM generated data. Because its not a matter of IF you get caught out, but of WHEN
you get caught out (and by how much)!!
Great pilots are made not born. A man may possess good eyesight, sensitive hands, and
perfect coordination, but the end result is only fashioned by steady coaching, much practice,
and experience. (Air Vice-Marshal J. E. Johnnie Johnson, RAF)
Page 21 of 29
V1.1
June 2007
.c
!
O
W
y
bu
to
k
lic
.d o
o
c
.
FMA
MODES (AND WHAT THEY PRACTICALLY MEAN TO YOU)
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
The FMA included in the upper part of the PFD is your primary indication of what the FMGS (which also includes
the A/THR, AP and FD) is doing. If you understand what the various messages mean then you are far less likely to
be caught out or sit there wondering what it is doing.
Tip of the Day: Any time you ever wonder What is it doing? or Why is it doing that? is a
strong indication that you had better:
Monitor the aircrafts performance using raw data (i.e. IAS, V/S, HDG, ALT, Attitude) to
ensure it is doing what you want it to do, or
Start thinking about reverting to Basic Modes (HDG, V/S or TRACK, FPA), or
In extreme cases, disengage the AP (and possibly turn off the FDs) and manually fly the
aircraft.
By not knowing or understanding what the system is doing or trying to accomplish, and having to start reverting to
monitoring raw data, Basic Modes or manually flying the aircraft means that your workload starts to exponentially
increase and you also start to strip away the various Protections and automatic safeguards that are built into the
FMGS.
Do you recall reading the following extract from the front of most of our Operations Manuals?
AUTOMATION
It is Cathay Pacific Airways policy to regard Automation as a tool to be used, but not blindly
relied upon.
At all times, flight crew must be aware of what automation is doing, and if not
understood, or not requested, reversion to basic modes of operation must be made
immediately without analysis or delay.
Trainers must ensure that all CPA flight crew are taught with emphasis how to quickly revert to
basic modes when necessary.
In the man-machine interface, man is still in charge.
Remember that you are a pilot and not a passenger. So it is imperative that you have a good basic understanding
of what the FMGS can do.
For this discussion we will once again limit ourselves to the Descent Phase.
AP/FD VERTICAL MODES
There are 15 AP/FD Vertical Modes that can be engaged and displayed (on the second column, first line) and 7
that can be armed (on the second column, second line) of the FMA.
Dont panic just yet! We will ignore all the various ALT and ALT*, SRS and G/S Modes as they are pretty selfexplanatory and most pilots can understand them.
During the descent for the vast majority of the time you will use only:
DES (Managed Mode),
OP DES (Selected Mode,
V/S (Basic Selected Mode), or
FPA (Basic Selected Mode normally only used after the FAF during a Non Precision Approach or a
Visual Approach).
Page 22 of 29
V1.1
June 2007
.c
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
Recall
that there is an interaction between the AP/FD and the A/THR. The selection of an AP/FD vertical mode
determines the associated A/THR mode.
c u -tr a c k
The AP/FD can control either a target SPEED/MACH or a vertical trajectory (path).
The A/THR can control either a target SPEED/MACH or a THR(ust).
The AP/FD and A/THR cannot simultaneously control a target SPEED/MACH.
Lets look at each vertical mode separately.

OP DES
OP DES is a Selected vertical mode.
This is probably the easiest vertical mode to understand as it behaves like the first basic aircraft that you learnt to
fly. You set idle power on the engine and control the speed with the elevators by changing the pitch attitude
(remember Power + Attitude = Performance?)
By setting OP DES you command the AP/FD to fly the target SPEED/MACH (either Selected Speed or Managed
Speed). The Speed is now controlled by using the elevator to change the pitch attitude by the AP/FD. As the
AP/FD is controlling the SPEED/MACH the A/THR cannot so it must control the THR(ust), which it does and sets
THR IDLE.
You will always see THR IDLE OP DES together.
No Altitude constraints will be observed and the aircraft will descend at THR IDLE to the FCU selected
altitude (indicated on the ND by the blue level off arrow). If there are Altitude constraints included in the
FPLN these will be ignored and a White circle will surround the associated waypoints on the ND if in NAV.
Speed constraints will be observed only in Managed Speed and NAV.
SPD LIM will be observed only in Managed Speed.
DES
DES is a Managed vertical mode. It can only be set when in NAV lateral mode. DES mode is the only time that
you will get the Managed Speed target range (normally 20 Kts, limited by Vmo 3 Kts or Mmo 0.006 or if a
descent SPD LIM or a Speed constraint is encountered, the speed is limited to the Constraint Speed + 5 Kts)
displayed on the PFD Speed tape.
This mode causes the most confusion, as most pilots do not understand how all the various systems (AP/FD,
A/THR and FMGS) work together and interact to achieve what has been input into the FMGS via the FCU and
MCDU or how the FM draws the vertical descent path.
Remember GIGO (Garbage In/Garbage Out). The FMGS will only be able to achieve what you input into it. If you
put crap in, you can expect a less than optimal performance. Always endeavour to input the most correct and up to
date information into the MCDU and FPLN to get accurate predictions and vertical profile computations.
There are three basic cases that can occur when in the DES mode:
On Profile
The aircraft is descending on the FM calculated vertical profile and so VDEV will be about zero.
By setting DES when on profile you command the AP/FD to fly the target SPEED/MACH (Managed Speed target
range). The Speed is now controlled by using the elevator to change the pitch attitude by the AP/FD. As the
AP/FD is controlling the SPEED/MACH the A/THR cannot so it must control the THR(ust), which it does and sets
THR DES.
When on profile you will always see THR DES DES NAV .
All Altitude and Speed constraints and SPD LIM will be observed.
If there are Altitude constraints included in the FPLN these will be displayed on the ND with a magenta
circle surrounding the waypoint and a magenta star on the MCDU.
Page 23 of 29
V1.1
June 2007
!
O
W
y
bu
to
k
lic
Speed constraints will have a magenta star next to then on the MCDU predictions.
SPD LIM will occur automatically if in Managed Speed.
.d o
.c
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
Above Profile
The aircraft is descending but is above the FM calculated vertical profile and so VDEV will be positive.
By setting DES when above profile you command the AP/FD to fly the target SPEED/MACH (Managed Speed
target range and it will increase up to the upper limit of the range). The Speed is now controlled by using the
elevator to change the pitch attitude by the AP/FD. As the AP/FD is controlling the SPEED/MACH the A/THR
cannot so it must control the THR(ust), which it does and sets THR IDLE in an attempt to intercept the profile
from above.
When above profile you will always see THR IDLE DES NAV .
All Altitude and Speed constraints and SPD LIM will be observed if possible.
circle if achieved (or amber if not achieved) surrounding the waypoint and a magenta star on the MCDU (or
amber star if not achieved).
Speed constraints will have a magenta star if achieved (or amber if not achieved) next to then on the
MCDU predictions.
A blue Intercept Point will be displayed on the ND.
Below Profile
The aircraft is descending but is below the FM calculated vertical profile and so VDEV will be negative.
By setting DES when below profile you command the AP/FD to fly the trajectory to intercept the profile from below.
The Managed Speed target range will be displayed but it will use the set Managed Speed only, not the lower limit
of the range. The trajectory (or path) is now controlled by using the elevator to change the pitch attitude to set a
V/S of either 1,000 ft/min (Idle segment) or 500 ft/min (Geometric segment). As the AP/FD is controlling the
trajectory the A/THR must be in SPEED/MACH mode in an attempt to intercept the profile from below.
When below profile you will always see SPEED/MACH DES NAV .
All Altitude and Speed constraints and SPD LIM will be observed if possible.
circle if achieved surrounding the waypoint (or amber if not achieved) and a magenta star on the MCDU (or
amber star if not achieved).
Speed constraints will have a magenta star if achieved (or amber if not achieved) next to then on the
MCDU predictions.
A blue Intercept Point will be displayed on the ND.
V/S
V/S is a Basic Selected vertical mode.
By setting V/S you command the AP/FD to fly the selected V/S. The trajectory (or path) is now controlled by using
the elevator to change the pitch attitude to set the selected V/S. As the AP/FD is controlling the trajectory the
A/THR must be in SPEED/MACH mode.
You will always see SPEED/MACH V/S together.
No Altitude constraints will be observed and the aircraft will descend at the selected V/S to the FCU
selected altitude (indicated on the ND by the blue level off arrow).
If there are Altitude constraints included in the FPLN these will be ignored and a White circle will surround
the associated waypoints on the ND only if in NAV.
Page 24 of 29
V1.1
June 2007
.c
O
W
y
bu
to
k
lic
.c
c u -tr a c k
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.d o
c u -tr a c k
Speed constraints will be observed only in Managed Speed and NAV and if the selected V/S allows the
required deceleration. Set the V/S too high and even at IDLE thrust (as V/S is a Basic Mode) the aircraft
may increase speed above the speed target to achieve the selected V/S.
SPD LIM will be observed only in Managed Speed and if the selected V/S allows the required deceleration.
FPA
FPA is also a Basic Selected vertical mode. FPA is normally only used after the FAF during a Non Precision
Approach or a Visual Approach (see NPs).
By setting FPA you command the AP/FD to fly the selected FPA. The trajectory (or path) is now controlled by
using the elevator to change the pitch attitude to set the selected FPA. As the AP/FD is controlling the trajectory
the A/THR must be in SPEED/MACH mode.
You will always see SPEED/MACH FPA together.
No Altitude constraints will be observed and the aircraft will descend at the selected FPA to the FCU
selected altitude (indicated on the ND by the blue level off arrow).
If there are Altitude constraints included in the FPLN these will be ignored and a White circle will surround
the associated waypoints on the ND only if in NAV.
Speed constraints will be observed only in Managed Speed and NAV and if the selected FPA allows the
required deceleration. Set the FPA too high and even at IDLE thrust (as FPA is a Basic Mode) the aircraft
may increase speed above the speed target to achieve the selected FPA.
SPD LIM will be observed only in Managed Speed and if the selected FPA allows the required
deceleration.
AP/FD LATERAL MODES

Know how to find the TO Waypoint (the waypoint that the FMGS is trying to get to) is important so you can keep the
FM Lateral FPLN as closely aligned as possible to your actual or anticipated track to obtain meaningful predictions
from the FMGS. It is displayed in the following places:
ND Upper Right Hand corner in green (the direct distance to the TO waypoint and the ETA at the current
Ground Speed are also displayed here),
ND The TO waypoint is displayed on the FPLN track line as a waypoint in white (all the others are in
green), and
MCDU FPLN The TO waypoint immediately follows the FROM waypoint. The TO waypoint and its
predictions are in white (all the others except the DEST waypoint are in green).
There are 11 AP/FD Lateral Modes that can be engaged (on the third column, first line), and 5 that can be armed
(on the third column, second line) of the FMA.
Dont panic just yet (again Im trying to keep your stress levels down!) Fortunately there are just a few Lateral
modes that we normally use during the Descent Phase.
During the descent for the vast majority of the time you will use only:
NAV (Managed Mode),
HDG (Basic Selected Mode), or
TRACK (Basic Selected Mode normally only used after the FAF during a Non Precision Approach or a
Visual Approach).
NAV
This Lateral Mode is pretty easy.
Page 25 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
The
AP/FD will follow the green FPLN track line on your ND. The FMGS bases all its lateral predictions (distance
and ETA) on following this FPLN track line. The FMGS calculated vertical descent profile (that was computed prior
to T/D and is fixed in space once you get into the Descent Phase) is all based on following this FPLN track line as
well. So if you diverge laterally from the FPLN track line the vertical predictions will be inaccurate or in error.
c u -tr a c k
The FMGS calculated vertical descent profile assumes Managed Speed. If you are in NAV and you require a
different speed than that used by the FMGS then the following will occur:
Less. At a speed less than the Managed Speed the FMGS used to calculate the profile, you will remain in
NAV but probably (depending on the speed difference) diverge vertically above the FMGS calculated
profile when you set the lesser Selected Speed. As you will now be above profile the A/THR will change to
THR IDLE.
More. At a speed more than the Managed Speed the FMGS used to calculate the profile then you will
remain in NAV and remain on the vertical profile when you set the greater Selected Speed. As you remain
on profile the A/THR will change to SPEED/MACH to maintain the higher speed.
HDG
This Lateral Mode complicates things a little.
When you go into HDG Lateral mode the following happens:
If in NAV, the Vertical mode reverts to the current V/S,
The ND waypoint altitude constraint circles are removed,
The FMGS FPLN track on the ND is displayed as a green dashed line and the current aircraft track on the
Selected HDG is displayed as a solid green straight line,
The MCDU FPLN predictions assume that the aircraft will return immediately to the flight plan, intercepting
at a predetermined angle (45 intercept to FPLN track if possible, if greater than 45 is required to intercept
then direct) and will then proceed under Managed guidance, and
FPLN waypoints will only sequence if you pass abeam that waypoint within 7 nm.
Ensure that the TO waypoint displayed on the ND and MCDU FPLN is correct. If it is not, all the MCDU predictions
and DTG and VDEV information is useless. Update the TO waypoint either by performing a DIR TO (with
inbound/outbound radial if required) or by clearing the FROM waypoint until the TO waypoint is the one you desire.
This simple little TO waypoint causes so many pilots to screw up descents because they are now using and relying
on incorrect information. ALWAYS keep your TO waypoint updated to what your current ATC clearance is or what
you anticipate it will be. This will also result in a more accurate DTG on the MCDU PFLN page, which is used
when mentally computing your descent profile (I recommend using the FCTM Descent Monitoring formula).
OK, so youre keeping your TO waypoint updated while in HDG. How can you make an assessment as to whether
the VDEV info the FMGS is providing is valid?
If you are close to the FMGS FPLN track (green dashed line on the ND and X Track error of less than about 5 nm),
then the predictions and VDEV is probably OK to use. Probably what do you mean Probably? The further out
you are (more track miles to fly) the less any error will affect you. The closer in you are (getting close to the LOC
now) the more any error will affect you. For example, a VDEV of + 1,500 (above profile), passing FL 350 on
descent with 125 nm DTG is OK, but the same VDEV passing 5,000 just prior to LOC intercept with 12 nm DTG is
probably not OK.
If you are on the FMGS calculated vertical descent profile and the new HDG will add extra track miles, then you will
be below the new actual vertical profile compared to the old FMGS calculated profile. You may need a reduced
V/S (make the descent angle shallower). Vice versa if the new heading requires less track miles. Now you may
need to increase speed or use S/B (make the descent angle steeper).
Try to visualise a superimposed vertical profile onto the ND displayed FPLN lateral track. This takes a little mental
gymnastics as the ND display is a two dimensional plan view from above and now you have to imagine it as a three
dimensional offset side view. Now visualise whether you are on, above or below the FMGS calculated vertical
Page 26 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
.
.d o
c u -tr a c k
profile
(remember this has been frozen in space) with what the aircraft is actually doing (e.g. you might be using
HDG and V/S).
c u -tr a c k
If youre on profile, do nothing (and manually follow the VDEV if it agrees with your mental calculation).
This maintains the same descent angle.
If youre above profile, increase speed or use S/B. This steepens the descent angle.
If youre below profile, use a reduced V/S or decelerate earlier. This shallows the descent angle.
TRACK
This does almost exactly the same as HDG. The only difference is that youre now Selecting a TRACK instead of a
HDG. All the considerations for HDG apply to TRACK as well.
THE REAL WORLD
Crikey! This is a piece of cake(?). Why does everyone have difficultly with the Airbus automation?
It is a very rare day that ATC clears you to complete a Procedural STAR and Approach. If you ever get one of
these arrivals you can use the FMGS as it was designed to be used i.e. THR DES DES NAV with Managed
Speed and sit back and monitor the FMGS do its automatic thing (and it does a bloody good job if youve set it up
correctly).
What now if ATC gives you radar vectors, descent and speed control (remember that speed is part of the vertical
profile picture) that bears no resemblance to any of the altitude or speed constraints or waypoints that you input
into the FMGS?
Welcome to the real world! This is the situation that occurs during most of our arrivals and approaches.
Both the Lateral and Vertical (Speed and Altitude) assumptions and waypoints that you input into the FMGS are
now incorrect (remember GIGO?). The predictions on the MCDU and Altitude and Speed constraints are next to
useless, as is VDEV. In fact, if you rely on them you can screw your approach up big time (have you been mentally
calculating your own vertical descent profile all the way down?).
This is where you start to earn your money. Anyone can do this job when its easy, but not everyone can do it
when it gets hard.
In the real world youve got to visualise what you are actually doing laterally and vertically (I use raw data in ever
increasing amounts the closer I get to the runway) and compare it with what the FMGS has calculated as its vertical
descent profile (I use FMGS derived data in ever decreasing amounts the closer I get to the runway).
Don't ever let an airplane take you someplace where your brain hasn't arrived at least a couple
of minutes earlier.
I think then in terms of on, above or below profile and take action depending on where in the 3D picture I am (on
dont change anything, above S/B (or may be increase speed), below V/S).
The closer to the runway I get the more I am using raw data (DME, VOR, NDB, LOC, G/S (but watch out for false
LOC and G/S captures if too far from the LOC), 3 times tables (Distance x 300 = Altitude for a 3 glideslope), 5
times tables (Groundspeed x 5 = V/S required for a 3 glideslope) and direct distance to the runway threshold input
into the PROG page) and the less I am even looking at any of the FMGS or VDEV predictions.
For what its worth, during the descent I mentally calculate the following and compare it with the VDEV and FMGS
calculated vertical descent profile:
The required DTG/Altitude using the FCTM Descent Monitoring formula every 5,000 during descent above
10,000,
The required DTG/Altitude using the FCTM Descent Monitoring formula every 1,000 between 10,000 and
5,000, and
The required DTG/Altitude using raw data every 1,000 below 5,000.
Page 27 of 29
V1.1
June 2007
O
W
y
bu
to
k
lic
o
c
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.
do
c u -tr a c k
In . the real world you can get any of the following (and most times it will be various combinations of some or all .of
them):
c u -tr a c k
High, on, or low on the calculated FMGS vertical profile,
Speed can be faster, the same, or slower than that used by the FMGS to calculate the vertical descent
profile,
Left, on, or right of the FMGS FPLN track (which results in track lengthening, the same DTG, or track
shortening).
How you react these changing situations and how well you understand the FMGS will determine what modes you
employ to get the aircraft in the right place, at the right time, at the right speed and the right configuration to
execute a safe, expeditious and efficient approach and landing. Easy isnt it!
Good luck and may the Force be with you.
Page 28 of 29
V1.1
June 2007
!
O
W
y
bu
to
k
lic
C
.d o
h a n g e Vi
e
N
C
lic
to
bu

w
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
.c
.c
Try and
visualise what the FMGS calculated vertical descent profile looks like in three dimensions by superimposing the vertical components upon the two dimensional plan view that you. d owill
c u -tr a c k
have displayed on your ND and by looking at the predictions that are provided on the MCDU FPLN page.
c u -tr a c k
The green line represents what you would normally see on the ND with Arc selected on the EFIS Control Panel (i.e. the FMGS FPLN track line). The light blue triangles represent the altitude
and/or speed constraints, the blue vertical lines are the altitude extensions overlaid on the plan view to construct the red lines (the 3D track of the aircraft).
This red line remains fixed in space when the FMGS enters the Descent Phase. Now you have to try and visualise where the aircraft is in relation to this red line.
You can be high, on, or low on the calculated FMGS vertical profile,
Your speed can be faster, the same, or slower than that used by the FMGS to calculate the vertical descent profile,
You can be left, on, or right of the FMGS FPLN track (which results in more, the same, or less track miles to touchdown), or
You can get track shortening or track lengthening (e.g. DIR from MANGO to LIMES).
Level flight from Decel Point to

achieve VAPP at 1,000 AAL
while configuring at
Characteristic Speeds
Idle segment
VHHH 07L
Geometric segments
from MANGO to Decel
Point
CF07L
Insert /+1700
GUAVA
8000
D157U
180/+2000
D
LIMES
+ 2000
MANGO
250/130
SOKOE
220/+ 3000
Page 29 of 29
T/D
V1.1
June 2007
h a n g e Vi
e
N
.c
NORM AL
sl.
ABNORM AL *
01 COC KP IT PRE PA RATION
M AN
EC AM PHILOS OPHY
02 BE FORE STA RTENGINES TART-A FTE R STA RT
M AN
03 TAX I-BTO
M AN
AU TO
AU TO
M AN
M AN
AU TO
M AN
AU TO
AU TO
AU TO
04 TAK EOF F
05 CL IMB
06 CRUISE
07 DE SC ENT
08 ILS_A PP
09 GSm ini
10 NPA _MA NAGE D
11 NPA _S EL EC TED
12 GO_A ROUND
13 AF TER LA NDING - PA RKING M AN
SE CURING
14 RNAV
AU TO
FROZEN
FROZEN
10
12
14
FROZEN
15
FROZEN
17
FROZEN
18
FROZEN
19
FROZEN
20
21
FROZEN
22
* During Tutorial mode :

If the Auto-Pilot is lost during an
Abnormal Proc, the flight is frozen
y
bu
to
k
sl.
24
DUA L AD R FA ULT
M AN
M AN
DUA L RA
M AN
26
M AN
EIS FA IL SW ITCHING
M AN
ELEV RED UND LOS T
M AN
EMER EL EC
M AN
EMERGE NCY DE SC ENT
M AN
ENG FA ILURE IN CRZ DRIFT DW N DA MAGE M AN
ENG FA ILURE IN CRZ STD NO DA MAG E
M AN
Engi ne start failure
M AN
EO AF TER TO_D ama ge
AU TO
EO AF TER TO_No Da mag e
AU TO
FMGC FA ILURE
M AN
FLA PS _LOCK ED
M AN
Fuel imb alance
M AN
IR DISC REP ANC Y
M AN
SLATS _FAUL T
M AN
Smoke
M AN
Unreliab le spe ed indicati on (pito t / static blocked ) M AN
25
27
DUA L_HYD
28
30
31
33
34
35
36
FROZEN
37
FROZEN
38
39
40
41
42
43
44
45
.d o
c u -tr a c k
lic
to
k
lic
C
.d o
Temporary note :
see highlight
LR - PROCEDURES LIST
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
SLIDE TITLE :
to
k
ENG
FAILURE at
T/O
sl. 1
SIMULATION STATUS :
FROZEN
INSTRUCTOR ACTION
TO UNFREEZE : UNFREEZE
MANUAL TRANSITION :
PARAMETER FOR AUTOMATIC TRANSITION :
A/C & FLIGHT STATUS :
FAILURE TRIGGERED :
200
200 ftft
Flight is
initialised at
Take-off
ENG 2
FAILURE
triggered with
DAMAGE
after AP
engaged
INFORMATION PAGE (POP-UP) :
FM & FL CHECK
2
.d o
.c
lic
to
CODES
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
y
o
c u -tr a c k
.c
NORMAL PHASES
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
h a n g e Vi
e
INIT
GATE
PRESENTATION
slide 1
Ext. and
prelim.
slide 2
y
bu
to
k
lic
FMGS Prep (slide 7)
COCKPIT PREP
slide 3
END
slide 4
FROZEN
FROZEN
UNFREEZE
.d o
C
w
PERF DATA
(slide 9)
NAV DATA
(slide 8)
TAKE OFF BRIEFING

(slide 6)
.c
PRELIMINARY CO CKPIT PREP

(slide 5)
to
bu
LR - COCKPIT PREPARATION
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PRESEN
TATION
slide 1
FROZEN
1.a.
BEFORE
START
1.b
BEFORE
START
slide 2
slide 3
2.AUTOMATIC
ENGINE
START
SEQUENCE
slide 4
ICING (PW) (slide 19)
ICING (RR) (slide 18)
ICING (GE) (slide 17)
ECAM MEMO (slide 16)
NWS TOWING (slide 15)
ANTI ICE (slide 14)
PITCH TRIM (slide 13)
APU BLEED (slide 12)
ENG IDLE PARAMETERS (slide 11)
lic
to
y
bu
3.a AFTER
START
3.b AFTER
START
END
slide 5
slide 6
slide 7
FROZEN
UNFREEZE
5
to
bu
O
W
PD
F-
XC
.d o
O
W
PD
lic
A330 - BEFORE START START AFTER START

w
INIT
GATE
STARTING ENG (PW) (slide 10)
.c
STARTING ENG (RR) (slide 9)
c u -tr a c k
STARTING ENG (GE) (slide 8)
.d o
h a n g e Vi
e
h a n g e Vi
e
c u -tr a c k
er
XC
er
w
C
Fw
.c
h a n g e Vi
e
PRESEN
TATION
Slide 1
FROZEN
1.a
BEFORE
START
1.b
BEFORE
START
Slide 2
Slide 3
2.AUTOMATIC
ENGINE
START
SEQUENCE
Slide 4
y
bu
to
k
lic
3.a AFTER
START
3.b AFTER
START
END
Slide 5
Slide 6
Slide 7
FROZEN
UNFREEZE
.d o
C
w
ICING (slide 16)
ECAM MEMO (slide 15)
NWS TOWING (slide 14)
ANTI ICE (slide 13)
PITCH TRIM (slide 12)
APU BLEED (slide 11)
ENG IDLE PARAMETERS

(slide 10)
INIT
GATE
START SEQUENCE (slide 9)
.c
STARTING ENG (slide 8)
to
bu
A340 - BEFORE START START AFTER START
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
2.CLEARANCE
y
bu
to
k
lic
1. TAXI
INITIATION
CONFIRMATION
3.TAXI
CHECKS
4.BEFORE
TAKE OFF
Slide 1
Slide 2
Slide 3
Slide 4
Slide 5
FROZEN
FROZEN
PACKS 1+2 (slide 18)
TCAS (slide 17)
PRESEN
TATION
UNFREEZE
Repositioning:
A/C at T/O position
&
Brakes
engagement in
order to stop the
aircraft
END
Slide 6
Last update : 14/09/05
.d o
C
w
CONTINUOUS
IGNITION (slide 16)
BRAKE TEMP
LIMITATIOIN (slide 15)
TO BRIEFING
CO NFIRMATION (slide 14)
HEADING PRESET
(slide 13)
TERR ON ND (slide 9)
T/O CONFIG (slide 12)
AUTO BRAKE (slide 11)
ATC (slide 10)
F/CTL CHECK (slide 7)
INIT
GATE
RADAR / PWS (slide 9)
.c
ATC CLEARANCE
(slide 8)
to
bu
LR - TAXI & BEFORE TAKE-OFF
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
T/O
PHASE
Slide 1
FROZEN
INIT
READY
FOR T/O
1.TAKE
OFF
INITIATION
2.TAKE
OFF
RUN
Slide 2
ONE PACK (slide 16)
T/O POS
TRHUST LEVERS (slide 15)
FMA (slide 12)
INIT
3a.ROTATION
3b.PRESELECTED HEADING
Slide 3
Slide 4 (330)
Slide 5 (340)
Slide 6
FROZEN
FROZEN
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
AUTOMATIC
THRUST
SETTING
105 kt
When A/P
engaged
10 kt
Preselected
HDG
HDG or
NAV green
4.THRUST
RED
Slide 7
3000 ft
YES
NO
8
bu
to
k
lic
.d o
1/2
EXT LIGHTS (340 - slide 14)
.c
EXT LIGHTS (330 - slide 13)
to
bu
LR - TAKE OFF
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
APU BLEED
ANTI ICE (slide 18 )
FLIG HT PHASE
SWITCHING (slide 19)
FLAPS (slide 17)
5.ACCEL
6.AFTER
Slide 8
T/O
Slide 9
FROZEN
FROZEN
UNFREEZE
UNFREEZE
At 220 kt
AT
TRANSITION
ALT + 100ft
7.TRANSITION ALT
Slide 10
END
Slide11
FROZEN
UNFREEZE
BARO REF STD

SET + 20 sec
OR
bu
to
k
lic
w
.d o
2/2
.c
to
bu
LR - TAKE OFF
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PRESEN
TATION
Slide 1
1.ATC
clearance
change
Slide 2
FROZEN
2.RADARTi
lt & ENG
anti ice
Slide 3
3.FL 100
Slide 4
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
FCU
ALT
SET
9500
ft
LDGT LT
retracted +
1 min 30
sec
RESUME MANAGED
RESUME MANAGED
VERTICAL F-PLAN (slide 20)
FL 100 (slide 16)
4. ATC REQ:
MAINTAIN
PRESENT HDG
5.a. ATC REQ:

RESUME OWN
NAV
Sl ide 5
Sl ide 6
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
HDG
GREEN
NAV
green
Fl 190
3 sec
3 sec
3 sec
5.b.ATC REQ:
RESUME OWN
NAV
Sl ide 7
3 sec
10
bu
to
k
lic
.d o
1/2
LATERAL F-PLAN (slide 19)
EFIS OPTIONS (slide 15)
ENG ANTI-ICE (slide 14)
FL 60
FMA & FL CHECK (slide 13)
INIT
FL 100 (slide 17)
SELECTED MODE (slide 18)
.c
LAT GUIDANCE
to
bu
LR - CLIMB
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
7.CRZ ALT
clearance
AFT XFR (slide 26)
AUTO CG :
CO MPLETE
FLIGHT
SYNTHESIS
(slide 25)
LO WER
SPEED
(slide
24)
CRZ ALT
UPDATE
(slide 22)
MO NITORING
THE CSTR (slide 21)
6.CONSTRAINT
MONITORING
EXPEDITE
(slide 23)
FLIGHT PHASE
8. Automatic
CG control
9.Cruise
Capture
Slide 8
Slide 9
Slide 10
Slide 11
FROZEN
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
Fl 205
FL
220
FL
259
END
Slide
12
3 sec.
11
bu
to
k
lic
.d o
2/2
.c
SWITCH CDTIO NS (slide 27)
to
bu
LR - CLIMB
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
STEPS (slide 16)
TRAFFIC AND MODE

SELECTOR slide12)
CONTROL OF
CG (slide 10)
SYSTEM DISPLAY
REVIEW (slide 11)
TOC on F-PLN
FL 260
WINDS (slide 15)
INIT
FCU ALT SELECTION

CO NSEQUENCES (slide 14)
TRAFFIC AND MODE

SELECTOR
(Ranges - slide 13)
CRUISE
PHASE
1.CRUISE
INITIATION
2.PERIODIC
CHECKS
3.LEVEL
CHANGE
4.VERTICAL CRUISE
MANAGEMENT
Slide 1
Slide 2
Slide 3
Slide 4
Slide 5
FROZEN
FROZEN
UNFREEZE
Change actual
wind to 360/50 kt
When reaching
new FL
12
bu
to
k
lic
w
.d o
1/2
.c
to
bu
LR - CRUISE
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
NAV ACCURACY
CHECK (slide 17)
5.STEP
CLIMB
6.PERIODIC
CHECKS
Slide 6
Slide 7
7.LATERAL
CRUISE
MANAGEMENT
END
Slide 9
Slide 8
Change actual
wind to 270/60 kt
when reaching
new FL
13
bu
to
k
lic
.d o
2/2
.c
OFFSET (slide 18)
to
bu
LR - CRUISE
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PRESENTATION
FROZEN
1.DESCEN
T PREP
Slide 2
Slide 1
Slide 3
2.DESCENT
INIT
3.DESCENT MONITORING
Slide 4
RAD NAV (slide 14)
WIND(slide 17)
AUTOMATIC CG CONTRO L(slide 15)
V DEV (slide 13)
SWITCHING(slide 16)
FLIGHT PHASE
LATE DES (slide 12)
EARLY DES (slide 11)
AUTOBRAKE (slide 10)
lic
to
y
bu
4.FL 100
Slide 5
END
Slide 6
FROZEN
UNFREEZE
14
to
bu
O
W
PD
F-
XC
.d o
O
W
PD
lic
LR - DESCENT
w
FL 310
APP BREIF (slide 9)
.c
INIT
FMG S PREP (slide 8)
c u -tr a c k
DES PREP (slide 7)
.d o
h a n g e Vi
e
h a n g e Vi
e
c u -tr a c k
er
XC
er
w
C
Fw
.c
h a n g e Vi
e
PRESENTATION
FROZEN
ECAM WHEEL page (slide 19)
VFE NEXT (slide 16)
1a.INITIAL
1b.INITIAL
1c.INITIAL
2.INTERMEDIATE
3.FINAL
4a.FINAL
APP
APP
APP
APP
APP
APP
Sl ide 2
Slide 3
Sl ide 4
Sl ide 5
Sl ide 6
Sl ide 7
FROZEN
FROZEN
FROZEN
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
5500ft
2 nd AP engaged
+
3
FLAPS at 1
+
3
2700ft QNH
FLAPS at FULL
+
3
500 ft RA
15
bu
to
k
lic
.d o
1/2
G /A ALT (slide 15)
MANAGED SPD (slide 13)
STABILIZED APP (slide 12)
FL 60
NAV ACC (slide 11)
INIT
DECEL POINT (slide 14)
.c
FLAPS 1 SEL (slide 18)
to
bu
LR - ILS
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FLT
PARAMETER
(slide 17)
4b.FINAL
APP
5.AUTO
LAND
END
Sl ide 8
Sl ide 9
Sl ide
10
FROZEN
FROZEN
UNFREEZE
UNFREEZE
200ft RA
10KT
16
bu
to
k
lic
w
.d o
2/2
.c
to
bu
LR - ILS
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PRESENTATION
Sl ide 1
FROZEN
y
bu
to
k
lic
G/S mini (slide 6)
3700 ft
IAS TARGET
INIT
1.Actual
Headwind
2.Increase to
50kt
3.Decrease
to 20 kt
END
Sl ide 2
Slide 3
Slide 4
Slide
5
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
Headwind
increases to 50 kt
Headwind
decreases to 20 kt
17
.d o
.c
to
bu
LR - GROUND SPEED MINI
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
NPA
Slide 1
FROZEN
1a.INITIAL
APPROACH
2.INTERMEDIATE
APPROACH
Slide 2
1b.INITIAL
APPROACH
Slide 3
FROZEN
FROZEN
y
bu
to
k
lic
Slide 4
3a.FINAL
APPROACH
Slide 5
3b.FINAL
APPROACH
Slide 6
FROZEN
FROZEN
FROZEN
3c.FINAL
APPROACH
Slide 7
AP disc
FROZEN
UNFREEZE
5500ft
UNFREEZE
240 kt
UNFREEZE
FLAPS
at
FULL +
3sec
UNFREEZE
UNFREEZE
2500ft
MDA
+300 ft
+ 3 sec
(1550 ft)
END
Slide 8
18
.d o
C
w
FLT PARAMETERS
( slide19)
POSITION/ FLIGHT
PATH slide 18)
GO AROUND ALTITUDE
(slide17)
F-PLN SEQUENCING
(slide 15)
ND MODE/ RANGE
(slide 13)
CONDITIONS (slide 12)
APPRO ACH STRATEGIES

(slide 11)
STABILIZED APPROACH
(slide10)
5 NM
before
ROA
NAV ACCURACY (slide 9)
INIT
FLAPS FULL (slide16)
.c
V/DEV (slide 14)
to
bu
LR - NPA MANAGED
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
NPA
Slide
1
FROZEN
1a INITIAL
APPROACH
y
bu
to
k
lic
2 INTERMEDIATE
APPROACH
Slide 2
1b INITIAL
APPROACH
Slide 3
FROZEN
FROZEN
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
2500ft
MDA
+300 ft
UNFREEZE
5500ft
240 kt
Slide 4
FLAPS
at
FULL +
3sec
3a FINAL
APPROACH
Slide 5
+ 3 sec
3b FINAL
APPROACH
Slide 6
3c FINAL
APPROACH
Slide 7
FROZEN
(1550 ft)
END
Side 8
19
.d o
C
w
FLT PARAMETERS
(slide15)
G O ARO UND
ALTITUDE (slide 14)
ND MODE RANGE
(slide 11)
STABILIZED
APPRO ACH (slide 10)
5 NM
before
ROA
NAV ACCURACY (slide 9)
INIT
FLAPS FULL (slide 13)
.c
F-PLN SEQ UENCING

(slide 12)
to
bu
LR - NPA SELECTED
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
GO AROUND
Slide 1
1.GO
AROUND
INITIATION
2.LATERAL
GUIDANCE
Slide 3
Slide 2
FROZEN
3.THRUST
RED/ACCEL
ALTITUDE
y
bu
to
k
5.DIVERSION
Slide 5
Slide 6
FROZEN
END
Slide
7
Slide 4
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
L/G up
When
HDG or
NAV
green
When
FLAPS 0
selected
UNFREEZE
230
UNFREEZE
STD
Selected
+ 5 sec
20
.d o
lic
4.HOLD
FROZEN
One
green
FLIG HT PHASE
SWITCHING (slide 12)
3 TYPES O F HOLD
(slide 10)
GO
ARO UND
(slide 8)
2000 ft
FLIG HT PHASE
SWITCHING (slide 9)
INIT
3 POSSIIBLITIES
(slide 11)
.c
DIVERSION :
to
bu
LR - GO AROUND
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PRESENTATION
1.a AFTER
LANDING
1.b AFTER
LANDING
1.c AFTER
LANDING
Slide 2
Slide 3
Slide 4
Slide 1
FROZEN
O
W
y
bu
to
k
lic
2.a
PARKING
2.b
PARKING
3.
SECURING
THE A/C
END
Slide 5
Slide 6
Slide 7
Slide 8
FROZEN
UNFREEZE
21
.d o
C
w
MAINTENANCE BUS
(slide 17)
STATUS (slide 16)
IRS PERFORMANCE
(slide 15)
APU NOT
AVAILABLE (slide 14)
APU BLEED(slide 13)
PARKING BRAKE
(slide 12)
h a n g e Vi
e
PD
RWY 33R
BRAKE FANS (slide

11)
INIT
ATC (slide 10)
O
W
N
C
lic
to
bu
LR - AFTER LANDING PARKING SECURING
.c
XC
er
c u -tr a c k
.d o
F-
FLAPS (slide 9)
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
RNAV
Slide 1
FROZEN
y
bu
to
k
lic
Approach strategy (slide 10)
Before starting (slide 9)
Conditions (slide 8)
Vocabulary (slide 7)
5 NM
before
BENET
Other RNAV (slide 6)
INIT
1.INITIAL
APPROACH
slide 2
2.INTERMEDIATE
APPROACH
FROZEN
FROZEN
slide 3
3.FINAL APPROACH
(LNAV/VNAV) slide 4
AP disc
FROZEN
UNFREEZE
2600 ft
UNFREEZE
FLAPS
at
FULL +
3sec
END
Sl. 8
22
.d o
.c
to
bu
LR - RNAV
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
y
o
c u -tr a c k
.c
ABNORMAL PHASES
23
.d o
.d o
lic
to
bu
y
bu
to
k
lic
C
O
W
h a n g e Vi
e
PD
XC
er
O
W
F-
h a n g e Vi
e
PD
XC
er
F-
c u -tr a c k
.c
h a n g e Vi
e
ECAM
philo
1.Detect
Slide 2
Slide
1
FROZEN
2.ECAM
Procedure
Slide 3
3.SD
4.STATUS
Slide 4
Slide 5
5.SITUATION
ASSESSEMENT/
DECISION
y
bu
to
k
lic
6.Synthesis
END
Slide 7
Slide
8
Slide 6
FROZEN
(1)
UNFREEZE
(1) Gives some time to the instructor

to manually trigger a failure.
24
.d o
C
w
DELTA VLS (slide 14)
APPRO ACH SPEED

COMPUTATION (slide 13)
LANDING DISTANCE
CO MPUTATION (slide 12)
CONFIRM (slide 15)
LAND ASAP (slide 11)
IRREVERSIBLE
ACTIO NS A340 (slide 10)
SAME INIT
AS
CRUISE FL
260
ACTIONS A330 (slide 9)
.c
IRREVERSIBLE
to
bu
LR- ECAM PHILOSOPHY DYNAMIC CHART
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FAILURE
PRESENTATION
1.NAV
ADR 1
FAULT
2.NAV
ADR 1+3
FAULT
slide 1
slide 2
slide 3
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
1st failure
triggered
2nd failure
triggered
NAV ADR 1
FAULT
NAV ADR 1+3

FAULT
3.APPROACH
PREPARATION
y
bu
to
k
lic
END
Slide 5
Slide 4
FROZEN
25
.d o
C
w
APPROACH
SYNTHESIS (slide 10)
ADR ARCHITECTURE
(slide 9)
ECAM PRO C (slide 6)
INIT
CRUISE FL
260
.c
ENG THRUST LOCK

(slide 7)
to
bu
LR - DUAL ADR FAULT
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
RA 1+2
FAILURE
Slide 1
FROZEN
y
bu
to
k
lic
SYNTHESIS
(slide 7)
STATUS ANALYSIS
(slide 8)
ILS
APPROACH
1. NAV RA 2
FAULT
2. NAV RA 1
FAULT
3.APPR
PREP
Slide 2
Slide 3
Slide 4
FROZEN
FROZEN
UNFREEZE
UNFREEZE
RA
RA 22
RA
RA 11
FAILURE
FAILURE TRIGGERED
TRIGGERED
FAILURE
FAILURE TRIGGERED
TRIGGERED
4.AP
DISCONNEC
END
Slide 5
Slide 9
26
.d o
.c
to
bu
LR- NAV : RA 1+2 FAULT
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
DUALHYD
Slide 1
1. HYD G
RSVR LO
LVL
Slide 2
FROZEN
Slide 3
Slide 4
UNFREEZE
UNFREEZE
y
bu
to
k
lic
6. APPR
Slide 5
END
Slide 6
FROZEN
HYD : B ENG 2
PUMP LO PR
Triggered
triggered
27
.d o
C
w
SYNTHESIS
(slide 13)
VAPP FOR
A3456 (slide 9)
VAPP FOR
A340 (slide 8)
3. APPR
PREP
FROZEN
Fluid quantity set at 0
VAPP FOR
A330 (slide 7)
2. HYD G+B SYS

LO PR
FROZEN
HYD : G RSVR LOLVL
SUMMARY
(slide 10)
RAT MAN USE

(slide 11)
INIT CRUISE
FL 240
SUMMARY
(slide 14)
.c
SD ANALSIS
(slide 12)
to
bu
LR- G + B SYS LO PR
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FAILURE
PRESENT
ATION
Slide 1
1.EIS DMC
2 FAULT
2.EIS
DMC 3
FAULT
FAILURE
PRESENT
ATION
Slide 3
Slide 4
Slide 2
FROZEN
FROZEN
NORM restored
3.EIS DMC
1 FAULT
4.EIS DMC
3 FAULT
Slide 5
Slide 6
FROZEN
FROZEN
Switching
canceled
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
Failure
triggered
Failure
triggered
Failure
triggered
Failure
triggered
EIS DMC 2
FAULT
EIS DMC 3
FAULT
EIS DMC 1
FAULT
EIS DMC 3
FAULT
28
bu
to
k
lic
.d o
1/2
FCO M PROC (slide 14)
ECAM PROC (slide 13)
.c
to
bu
LR - EIS FAILURES / SWITCHING
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FAILURE
PRESENT
ATION
5.ND UNIT 1
FAILURE
Slide 8
Slide 7
NORM restored
FROZEN
FAILURE
PRESENT
ATION
6. PFD
UNIT 2
FAILURE
Slide 9
Slide 10
NORM restored
FROZEN
END
Slide 11
Switching
canceled
Switching
canceled
UNFREEZE
UNFREEZE
FAILURE
TRIGGERED
FAILURE
TRIGGERED
ND U2 FAULT
PFD U1 FAULT
29
bu
to
k
lic
w
.d o
2/2
.c
to
bu
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FCO M PROC (slide 15)
FAILURE
PRESENT
ATION
1.EIS EFIS
DMC 2
FAULT
2.EIS EFIS
DMC 3
FAULT
FAILURE
PRESENT
ATION
3.EIS ECAM
DMC 3
FAULT
4.EIS ECAM
DMC 1
FAULT
Slide 1
Slide 2
Slide 3
Slide 4
Slide 5
Slide 6
FROZEN
FROZEN
FROZEN
FROZEN
NORM restored
Switching
canceled
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
Failure
triggered
Failure
triggered
Failure
triggered
Failure
triggered
EIS EFIS DMC

2 FAULT
EIS EFIS DMC

3 FAULT
EIS ECAM
DMC 3 FAULT
EIS ECAM
DMC 1 FAULT
30
bu
to
k
lic
w
.d o
1/2
.c
c u -tr a c k
y
bu
to
k
lic
C
.d o
Temporary note :
see highlight
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
.c
FAILURE
PRESENT
ATION
5.ND UNIT 1
FAILURE
Slide 8
Slide 7
NORM restored
FROZEN
FAILURE
PRESENT
ATION
6. PFD
UNIT 2
FAILURE
Slide 9
Slide 10
NORM restored
FROZEN
END
Slide 11
Switching
canceled
Switching
canceled
UNFREEZE
UNFREEZE
FAILURE
TRIGGERED
FAILURE
TRIGGERED
ND U1 FAULT
PFD U2 FAULT
31
bu
to
k
lic
w
.d o
2/2
c u -tr a c k
y
bu
to
k
lic
C
.d o
Temporary note :
see highlight
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
HYD G + PRIM 2 + SEC

2 LOST (slide 7)
HYD G + PRIM 2 LOST
(slide 6)
NORMAL OPS
(slide 5)
INIT
y
bu
to
k
lic
ELEV
REDUND
LOST
Slide 1
2. F/CTL PRIM 2 FAULT
THE END
Slide 3
Slide 4
Slide 2
FROZEN
FROZEN
UNFREEZE
UNFREEZE
G
G SYS
SYS LO
LO LVL
LVL
PRIM
PRIM 22
FAILURE
FAILURE TRIGGERED
TRIGGERED
FAILURE
FAILURE TRIGGERED
TRIGGERED
FROZEN
32
.d o
FL 360
1. HYD G
RSVR LO
LVL
.c
AILERON
PRESET (slide 8)
to
bu
LR ELEV REDUNDANCY LOST
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PRESENTATION
1. ELEC EMER CONFIG
Slide 1
Slide 2
2. APPROACH
PREPARATION
y
bu
to
k
lic
3. APPROACH
Slide 4
Slide 3
FROZEN
FROZEN
UNFREEZE
ELEC EMER
failure is
triggered:
All AC BUS
FAULT (1-1,1-2)
END
Slide
5
LR - Last update : 13/01/05
33
.d o
C
w
SYNTHESIS
(slide 14)
SUMMARY
(slide 13)
SUMMARY
(slide 12)
STATUS (slide 11)
SYSTEM DISPLAY
(slide10)
ECAM PROC GE
(slide 9)
DESCRIPTION
(slide 6)
Same init
as
CRUISE
FL260
ECAM PROC RR
& PW (slide 8)
.c
ENG THRUST
LO CKED (slide 7)
to
bu
LR A330 - ELEC EMER CONFIG DYNAMIC CHART
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PRESENTATION
1. ELEC EMER CONFIG
Slide 1
Slide 2
2. APPROACH
PREPARATION
y
bu
to
k
lic
3. APPROACH
Slide 4
Slide 3
FROZEN
FROZEN
FROZEN
FROZEN
UNFREEZE
ELEC EMER
failure is
triggered:
All AC BUS
FAULT (1-1,12,2-3,2-4)
END
slide
5
34
.d o
C
w
SYNTHESIS
(slide 14)
SUMMARY
(slide 13)
SUMMARY
(slide 12)
STATUS (slide 11)
SYSTEM DISPLAY
(slide 10)
ECAM PROC A3456

(slide 9)
DESCRIPTION
(slide 6)
Same init
as
CRUISE
FL260
ECAM PROC (slide 8)
.c
ENG THRUST
LOCKED (slide 7)
to
bu
LR A340 - ELEC EMER CONFIG DYNAMIC CHART
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
ATC
(slide 7)
Flight is
initialised in
CRUISE
FL 350
PRESENTATI
ON
1.DETECTION
Slide 1
Slide 2
2.DESCENT &
TARGET
ADJUSTMENTS
Slide 3
FROZEN
FROZEN
FROZEN
UNFREEZE
Cab alt
increases
y
bu
to
k
lic
3.ECAM
ACTIONS
4.REACHING
FL100 or
MORA
Slide 4
Slide 5
UNFREEZE
END
Slide
6
EXCESS ALT
TRIGGERED
35
.d o
C
w
DAMAG E
(slide 9)
.c
NO
DAMAGE
(slide 8)
to
bu
LR - EMERGENCY DESCENT DYNAMIC CHART
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FAILURE
PRESENTATION
2.OBSTACLE
STRATEGY
Slide 2
slide 3
3.ECAM
ACTIONS
DAMAGE
slide 4
4.OBSTACLE
STRATEGY
y
bu
to
k
lic
END
Slide 5
FROZEN
UNFREEZE
Failure
triggered
ENG 1 FAIL
(DAMAGE )
36
.d o
C
w
DAMAG E ? (slide 13)
EO prompt (slide 12)
QRH 340 (slide 11)
1.ENG 1
FAIL
Slide 1
FROZEN
QRH 330 (slide 10)
A/THR (slide 7)
Flight is
initialised in
CRUISE
FL 350
STRATEGY (340) ( slide 9 )
.c
STRATEGY (330) (slide 8 )
to
bu
LR - ENG FAIL IN CRZ DRIFT DOWN DAMAGE
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FAILURE
PRESENTATION
2.STANDARD
STRATEGY
Slide 2
slide 3
3.ENGINE
RELIGHT
slide 4
4.OBSTACLE
STRATEGY
y
bu
to
k
END
Slide 5
Slide 1
FROZEN
FROZEN
UNFREEZE
Failure
triggered
ENG 1 FAIL
(DAMAGE )
ENG RELIGHT
NOT
SUCCESSFUL
then ENG SHUT
DOWN
37
.d o
lic
Q RH (340) (slide 17)
Q RH (330) (slide 16)
PERF CHECK
(slide 14)
DAMAG E ? (slide 13)
FCOM (slide 15)
1.ENG 1
FAIL
EO prompt (slide 12)
QRH 340 (slide 11)
QRH 330 (slide 10)
A/THR (slide 7)
Flight is
initialised in
CRUISE
FL 350
STRATEGY (340) ( slide 9 )
.c
SRTATEGY (330) (slide 8 )
to
bu
LR - ENG FAIL IN CRZ STD NO DAMAGE
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FADEC
ACTIO NS
(slide 4)
Same INIT as
BEFORE
START
PRESENTATION
Slide 1
y
bu
to
k
lic
END
1.
START FAULT
Slide 3
Slide 2
FROZEN
FROZEN
UNFREEZE
Failure reset
when engine
master
switch set to
OFF
START FAULT
(HOT START
eng1) failure is
triggered
38
.d o
C
w
DECISIO N
(slide 6)
.c
ECAM
PROCEDURE
(slide 5)
to
bu
LR - ENGINE START FAULT
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
2.EO ACC
ALT
3. ECAM
ACTIONS
Slide 3
Slide 4
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
PRESENT
1. ENG FAIL
Slide 1
Slide 2
FROZEN
UNFREEZE
y
bu
to
k
lic
APP PREP
Slide 5
FROZEN
END
slide 6
UNFREEZE
ENG 1 FAILURE (A330)

TRIGGERED
200
200ftft
WITH DAMAGE
IfIf AP
AP
NOT
NOTENGAGED
ENGAGED
FROZEN
IfIf AP
AP
ENGAGED
ENGAGED
MCT
MCT+3s
+3s
60s
60s
after AP engaged
1300
1300ftftRA
RA
When
When AP
AP
ENGAGED
ENGAGED
39
.d o
C
w
SYNTHESIS
(slide 10)
STATUS
(slide 7)
THR LEVERS
MCT ((slide 12)
SAME INIT
AS Take-off
DAMAGE
(slide 9)

EO SID, LAND
ASAP
(slide 11)
.c
BETA TARGET
(slide 8)
to
bu
ENG FAIL AFTER T/O - DAMAGE
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PRESENT
1. ENG FAIL
2. EO ACCEL
Slide 1
Slide 2
Slide 3
FROZEN
FROZEN
FROZEN
FROZEN
UNFREEZE
UNFREEZE
UNFREEZE
UNFREEZE
y
bu
to
k
lic
3. ENG
RELIGHT
END
Slide 4
slide 5
ENG 2 FAILURE
(A330)
200
200ftft
IfIf AP
AP
NOT
NOTENGAGED
ENGAGED
ENG 3 FAILURE
(A340)
IfIf AP
AP
ENGAGED
ENGAGED
TRIGGERED
WITHOUT DAMAGE
after AP engaged
FROZEN
1300
1300 ftftRA
RA
ENG
ENG RELIGHTED
RELIGHTED
When
When AP
AP
ENGAGED
ENGAGED
40
.d o
C
w
SYNTHESIS
(slide 8)
THR LEVERS
MCT (slide 10)
SAME INIT
as Take-off
DAMAGE
(slide 7)

EO SID, LAND ASAP

(slide 9)
.c
BETA TARGET
(slide 6)
to
bu
ENG FAIL AFTER T/O - NO DAMAGE
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PRESENTATION
Slide 1
1. AUTO FLT
FM 1 FAULT
Slide 2
FROZEN
FROZEN
UNFREEZE
FM 1 FAILURE
TRIGGERD
WITH AUTO-RESET
WITHOUT AUTORECOVERY
2. AUTO FLT
FM 1+2 FAULT
slide 3
y
bu
to
k
lic
MANUAL RESETS
(slide 8)
3. BACK UP
NAVIGATION
MODE
THE END
Slide 5
Slide 4
FROZEN
UNFREEZE
FMGC 2 RECOVERED
AFTER MANUAL
RESET
FMGC 2 FAILURE
TRIGGERD
WITHOUT AUTORECOVERY AFTER
MORE THAN 3 AUTORESETS
FROZEN
41
.d o
C
w
BACK UP NAV
(slide 10)
MANUAL RESETS
(slide 13)
MANUAL RESETS
(slide 14)
SINGLE MODE
AUTO RESETS
(slide 11)
SING LE MODE
NAVIGATES
(slide 12)
NORMAL MODE
(slide 6)
Flight is
initialised
at FL 240,
same as
init cruise
FLIES THE A/C

(slide 9)
.c
SING LE MODE
ARCHITECT
(slide 7)
to
bu
LR FM FAULT
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
PRESENTA
TION
Slide 1
1.F/CTL FLAPS
LCOKED
Slide 2
APPROACH
SPEED
COMPUTATION
A330 (slide 9)
APPROACH
SPEED
COMPUTATION
A340 (slide 10)
2.
APPROACH
PREPARATION
Slide 3
FROZEN
3.
APPRAOCH
y
bu
to
k
lic
END
Slide 5
Slide 4
FROZEN
UNFREEZE
FLAPS LOCKED
failure is generated
when conf 1+F has
been selected.
Flaps are locked
between conf 2 and
conf 1+F
42
.d o
C
w
APPROACH
SYNTHESIS A3456
(slide 15)
APPROACH SPEED COMPUTATION

A3456 (slide 14)
APPROACH
SYNTHESIS
A330/340 (slide 11)
STATUS A3456
(slide 13)
STATUS
A330340 (slide 8)
STANDBY
STATUS
(slide 7)
Same INIT as
takeoff
SPEED A3456
(slide 12)
.c
SPEED A330/340
(slide 6)
to
bu
LR - FLAPS LOCKED DYNAMIC CHART
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
.c
y
bu
to
k
lic
INIT FL 350
GW
174T(A330)
180T(A340)
FOB
20T(A330)
20T(A340)
Leak 500
KG/MIN on
LH side
FUEL
IMBALANCE
Slide 1
FROZEN
1.ADVISORY
Slide 2 (A330)
Slide 3 (A340)
2.LEAK
SUSPECTED
Slide 4 (A330)
3. LO LVL
Slide 7 (A330)
Slide 9 (A340)
Slide 7
Slide 6 (A340)
FROZEN
FROZEN
UNFREEZE
UNFREEZE
WING TK IMBALANCE (LEAK)

INNER 1 (A340)
FUEL INR 1 LO LVL (A340)
TANK LEAK LEFT INNER
FUEL L WING TK LO LVL
(A330)
failure triggered
END
(A330)
failure triggered
FUEL
ADVISORY
43
.d o
c u -tr a c k
y
bu
to
k
lic
C
.d o
Temporary note :
see highlight
LR - FUEL IMBALANCE / FUEL LEAK
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FAILURE
PRESENTATION
1.NAV IR 1
FAULT
slide 2
slide 1
FROZEN
2.NAV ATT
DISCREPANCY
FAULT
3.APPROACH
PREPARATION
y
bu
to
k
lic
END
Slide 5
Slide 4
slide 3
FROZEN
FROZEN
UNFREEZE
UNFREEZE
1st failure
triggered
2nd failure
triggered
NAV IR 1
FAULT
NAV ATT
DISCREPANCY
FAULT
FROZEN
44
.d o
C
w
APPROACH
SYNTHESIS (slide 11))
ADR ARCHITECTURE
(2/2) (slide 10)
ADR ARCHITECTURE
(1/2) (slide 9)
INIT
CRUISE FL
260
.c
ENG THRUST LOCK

(slide 7)
to
bu
LR IR DISCREPANCY
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
STATUS
(slide 6)
PRESENTA
TION
1.F/CTL SLATS
FAULT
Slide 1
Slide 2
2.
APPROACH
PREPARATION
Slide 3
FROZEN
3.
APPRAOCH
y
bu
to
k
lic
END
Slide 5
Slide 4
FROZEN
UNFREEZE
SLATS FAULT
failure (DUAL
SFCC failure)
is generated
when conf 1
has been
selected
FROZEN
45
.d o
C
w
APPROACH
SYNTHESIS
(slide 9)
Same INIT as
ILS APP
APPROACH
SPEED
CO MPUTATION
A3456 (slide 8)
.c
APPRO ACH
SPEED
COMPUTATION
(slide 7)
to
bu
LR - SLATS FAULT DYNAMIC CHART
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
y
bu
to
k
lic
Init FL 350 at
TUGLI:
-FOB: 20T
- GW: 180 T
PRESENTATION
1.DETEC
-TION
2. PROCEDURE:
FIRST ACTIONS
Slide 1
Slide 2
Slide 3
3. PROCEDURE:
AIR COND
SMOKE
4.PROCEDURE:
CAB EQUIP
SMOKE
Slide 4
Slide 5
5.1.
5.2.
PROCEDURE:
DENSE SMOKE
PROCEDURE:
DENSE SMOKE
Slide 6
Slide 7
FROZEN
UNFREEZE
END
Slide 8
46
.d o
.c
to
bu
LR - SMOKE DYNAMIC CHART
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
DESCRIPTION
Slide 1
FROZEN
1. PITOT PROBE
BLOCKED
Slide 2
GPS
(slide 9)
PITCH/THRUST
SETTING REF (slide 8)
MEMORY ITEMS
A340 (slide 7)
MEMORY ITEMS
A330/3A456 (slide 6)
(slide 5)
-Same init as
T/O
END
Slide 3
FROZEN
UNFREEZE
At 100 ft:
All pitot (1,2,3)
blocked
(FROZEN
PITOT) failure
47
.d o
PITOT PROBES BLOCKED
Flight
initialisation:
lic
to
bu
LR - UNRELIABLE SPEED INDICATION DYNAMIC CHART
OVERSPEED
.c
(slide 4)
c u -tr a c k
PROBES
SCHEMATIC
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
DESCRIPTION
Slide 1
FROZEN
GPS (slide 8)
-Right ADR 1&2 static

probes measure the
cabin pressure
instead of the real
static pressure.
PITCH / THRUST
SETTING REF (slide 7)
-INIT take-off
END
1. OVERSPEED
Slide 2
sl3
FROZEN
UNFREEZE
PERFORM T/O
UNFREEZE
WHEN
OVERSPEED
WARNING
TRIGERRED
+10sec.
48
.d o
STATIC PROBES BLOCKED

Flight initialisation:
lic
to
bu
LR - UNRELIABLE SPEED INDICATION DYNAMIC CHART
MEMORY ITEMS
A340 (slide 6)
.c
MEMORY ITEMS
A330/3A456 (slide 5)
c u -tr a c k
OVERSPEED (slide 4)
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
to
bu
ADR 1+3 FAULTPNF
lic
CommonLR
AIR DATA
REFERENCE
REFERENCE
AIR DATA3
REFERENCE
REFERENCE
AIR DATA2
REFERENCE
ADR 1+3 FAULT
LR - Version 02b
.d o
PF NAV
N
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
1. NAV ADR 1 FAULT
CommonLR
DETECTION
CM2
PF
FLIES THE AIRCRAFT

NAVIGATES
CONSIDER AUTOMATION USE
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
RETURN TO NORMAL TASK SHARING
OBSERVE ECAM MEMO
PF
COMMUNICATES
ADIRS SWTG
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
2. NAV ADR 1+3 FAULT
CommonLR
DETECTION
CM2
PF
FLIES THE AIRCRAFT LOSS OF AP, FD, A/THR

NAVIGATES Short term decision
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
DECISION
ST AT US, or
SUMM ARY
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMMERCIAL
COMME
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
ATC
DECISION
DECISIO N
PURSER
PURSER/ PAX
/ PAX
NOT IFY
OPS
OPS
ADR ARCHITECTURE
FLIGHT IS FROZEN TO PERMIT THE PROCEDURE APPLICATION ON THE M/FTD
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
3. APPROACH PREPARATION
CommonLR
FMGS..PREPARE
APPR BRIEFING ............PERFORM
FMGS PREPARATION :
STANDARD
Done upon PF request
+
MANUAL INSERTION OF VAPP
QRH
2.00
APP BRIEFING :
STANDARD
+
STATUS
APPROACH SYNTHESIS
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
1. NAV ADR 1 FAULT
CommonLR
DETECTION
CM2
PF
FLIES THE AIRCRAFT

NAVIGATES
ADR 1
ADR 1
ADR 3
ADR 2
CONSIDER
AUTOMATION
ADR 3
(BACKUP)
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
Both pilot confirmation

for this action
OBSERVE ECAM MEMO
PF
COMMUNICATES
No Feedback to FWC
ADR 2
.d o
ECAM PROCEDURE
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
CommonLR
DETECTION
CM2
PF

CONSIDER AUTOMATION
Single Chime
(every 5 sec)
ENG THRUST LOCKED
ECAM ACTIONS
Move the thrust levers to

the actual thrust position ECAM
PROCEDURE
SYSTEM DISPLAY
STATUS
DECISION
ST AT US, or
SUMM ARY
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMMERCIAL
COMME
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
ATC
DECISION
DECISIO N
PURSER
PURSER/ PAX
/ PAX
NOT IFY
OPS
OPS
ADR ARCHITECTURE
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
CommonLR
DETECTION
CM2
PF

CONSIDER AUTOMATION
ADR 1
ADR 3
ADR 2
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
! STATUS
Both pilot confirmation
for this action
RETURN
TO NORMAL TASK SHARING
DECISION
No Feedback to FWC
ST AT US, or
SUMM ARY
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMMERCIAL
COMME
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
ATC
DECISION
DECISIO N
PURSER
PURSER/ PAX
/ PAX
NOT IFY
OPS
OPS
ADR ARCHITECTURE
.d o
ECAM PROCEDURE
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
FMGC
bu
y
k
to
PNF
ANY
AP/FD,
A/THR
AVAIL
CommonLR
DETECTION
NO
AP/FD
A/THR
AVAIL
FMGC
CM2
PF
COMPARISON
SELECTION
NO COMPARISON
NO SELECTION

CONSIDER AUTOMATION
IR 2
IR 3
IR 1
IR 1
IR2
IR 3
ECAM ACTIONS
ADR 3
ADR 1
ADR
ADR 1+3
1+3 FAULT
FAULT
ECAM
PROCEDURE
ADR 2
ADR 1
ADR 3
ADR 2
SYSTEM DISPLAY
STATUS
COMPARISON
SELECTION
DECISION
NORMAL
LAW
PRIM
ADR ARCHITECTURE
NO COMPARISON
NO SELECTION
ST AT US, or
SUMM ARY
ALTN
LAW
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMMERCIAL
COMME
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
ATC
DECISION
DECISIO N
PURSER
PURSER/ PAX
/ PAX
NOT IFY
OPS
OPS
PRIM
1
1
2
2
3
.d o
ADR ARCHITECTURE
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
CommonLR
FMGS..PREPARE
Approach flown manually

with raw data : no AP
FD
A/THR
CONF 1

CONF 2
ALTN LAW
FMGS PREPARATION :
STANDARD
CONF 3
APP BRIEFING :
GO AROUND
LANDING GEAR
EXTENSION
STANDARD
+
STATUS
QRH
2.00
APPROACH SYNTHESIS
to
k
.d o
PNF
APPROACH SYNTHESIS
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
bu
PF HYD : G+B SYS LO PRPNF

Common LR
HYD G RSVR LO LVL

HYD B ENG 2 PUMP LO PR
DUAL HYDRAULIC
LAND ASAP
ECAM ACTIONS
DECISION
CONFIGURATION
LANDING GEAR EXTENSION

GO AROUND
FINAL APPR
LANDING & DECELERATION
LR - Version 02b
.d o
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
1. HYD GCommon
RSVR
LO LVL
DETECTION
FLIES THE AIRCRAFT
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
PF
COMMUNICATES
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
2. HYD G Common
+ B SYS
LO PR
DETECTION
FLIES THE AIRCRAFT LOSS OF AP
NAVIGATES LAND ASAPShort term decision
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
USE SUMMARY.....CRUISE part
DECISION
ST AT US, or
SUMM ARY
WE ATHER
WEATHER
LDG DIS T
LDG DIST
OPERATIONAL AND
AND
COMMERCIAL
COMME
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
DECISIO N
DECISION
NOT IFY
PURSER / PAX
OPS
OPS
COMMUNICATES : MAYDAY message
PF
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
3. APPROACH
PREPARATION
ANNOUNCE...I HAVE CONTROL
ANNOUNCE..YOU HAVE CONTROL ?

ECAM STATUS.REVIEW
SUMMARY..USE
FMGSPREPARE
FMGS PREPARATION :
STANDARD
+
QRH

APP BRIEFING :
A 330 :
A 340 :
2.00
A340-600 :
STANDARD
+
STATUS
+
QRH
SUMMARY APP, LDG & G/A sections

1.00
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
4. APPROACH
FLAPS EXTENSION USE SUMMARY
Fly a stabilized approach
APPROACH SYNTHESIS
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
A330
Check that NEW DEST

has been entered
Ensure that VLS & VAPP are based

on the proper weight at destination
VAPP = VREF + VREF
VREF is given:
On the QRH, and
On the summary
VREF = 30 kt
MCDU PERF APPR

page
Select CONF FULL

VAPP
VLS
LDG CONF
FULL
Read VREF = VLS CONF FULL

Add 30 kt (VREF) to VREF
Enter VAPP manually
.d o
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
A340-300
Check that NEW DEST

has been entered

VAPP = VREF + VREF
VREF is given:
On the QRH, and
On the summary
VREF = 35 kt
MCDU PERF APPR

page
Select CONF FULL

VAPP
VLS
LDG CONF
FULL

Enter VAPP manually
.d o
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
A340-600
Check that NEW DEST

has been entered

VAPP = VREF + VREF
VREF is given:
On the QRH, and
On the summary
VREF = 25 kt
MCDU PERF APPR

page
Select CONF FULL

VAPP
VLS
LDG CONF
FULL

Enter VAPP manually
.d o
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
PNF
Common LR
E/WD
PROC
DECISION
2
4
8
AP
STATUS
P
R
EP
IN
C
R
VAPP
AP
6
BRIEFING
.d o
USE OF SUMMARY
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
CONSIDER RAT MAN USE
With the RAT extended, the green SYS is recovered.

This permits slat extension recovery.
With the RAT extended, the fuel consumption increases by approx 0.6 ~ 1 %
to
k
w
.d o
PNF
RAT MAN USE
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
to
PNF
Common
1. HYD Y SYS LO LVL
LRDUAL HYDRAULIC
Roll control is affected by loss of spoilers
DETECTION
SLATS are lost
FLIES THE AIRCRAFT

LOSS
OF AP
FLAPS
will be slow
COMMUNICATES MAYDAY message
CONSIDER AUTOMATION USE : A/THR, AP
SLATS are lost
FLAPS will be slow
G B Y
2. SYSTEMS DISPLAYS analysis
3. STATUS
DECISION
.d o
SYSTEM PAGE ANALYSIS
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
ALTN LAW
CONFIGURATION
LDG WITH SLATS JAMMED
GO AROUND
L/G GRAVITY EXTENSION
GEAR CANNOT BE RETRACTED

(DOORS WILL REMAIN OPEN)

BE AWARE OF :
NO ANTISKID
(BRK PRESSURE MONITORED BY PNF)
PARTIAL LOSS OF GRND SPOILERS
to
k
.d o
PNF
SYNTHESIS
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
PNF
Common LR
E/WD
PROC
DECISION
2
4
8
AP
STATUS
P
R
EP
IN
C
R
VAPP
AP
6
BRIEFING
.d o
USE OF SUMMARY
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
to
bu
NAV : RA 1+2 FAULT PNF
lic
Common LR
NAV RA 2 FAULT
NAV RA 1 FAULT
DUAL RA FAULT
LR - Version 02
.d o
PF
N
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
1. NAVCommon
RA 2
FAULT
DETECTION
FLIES THE AIRCRAFT
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
Below 2500 ft :
Captains side
RADIO ALTIMETER
1
First officers side
RADIO ALTIMETER
2
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
2. NAVCommon
RA 1LRFAULT
DETECTION
FLIES THE AIRCRAFT
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
DECISION
When FLAPS 1 selected :
PF
COMMUNICATES
RADIO ALTIMETER
DATA
ST AT US, or
SUMM ARY
WE ATHER
WEATHER
LDG DIS T
LDG DIST
OPERATIONAL AND
AND
COMMERCIAL
COMME
RCIAL
CONS IDERATIONS
CONSIDERATIONS
ATC
DECISIO N
DECISION
NOT IFY
PURSER / PAX
OPS
OPS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
3. APPROACH
PREPARATION

FMGSPREPARE
FMGS PREPARATION :
STANDARD
APPR BRIEFING :
STANDARD
+
STATUS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
4. AUTOPILOT
DISCONNECTION
At CAT 1 minima:
AP.OFF
In final stage of the APPR, the FD will command excessive roll rates
APPROACH SYNTHESIS
UPON AUTOPILOT DISCONNECTION
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
DUAL RA FAULT
APPROACH PREPARATION :
Plan for ILS approach
CAT I only (Approach mode inhibited)
Configuration FULL
INTERMEDIATE APPROACH :
Localizer intercept ( LOC armed ) or raw data approach
Use Track- FPA
FINAL APPROACH :
L/G DOWN
A/P DISCONNECTION
Flare law is active
USE MAN PITCH TRIM
to
k
.d o
PNF
SYNTHESIS
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
1.b 3.02
NAVprocedure
RA 1 FAULT
Review FCOM
(If time permits)
Common LR
DETECTION
FLIES THE AIRCRAFT
NAVIGATES
FWC
RADIO ALTIMETER
CONSIDER
AUTOMATION USE : A/THR,
AP- R/A, DH / MINIMUM, Retard auto callouts lost
DATA
ECAM
ACTIONS
GPWS
INOP Apply extra caution to terrain clearance
1. ECAM PROCEDURE
FMGC
FCOM
2.
SYSTEMS
DISPLAYS
analysis
LOSS OF APPROACH MODE :
3.02
APP MODE cannot be armed,

No GlideSlope capture (RA info is needed for GS tracking )
PF
COMMUNICATES
When ILS
FLAPS
selected
: in
APP1can
be flown
LOC mode
TRK / FPA
RADIO ALTIMETER
DATA
to
.d o
PNF
STATUS ANALYSIS
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
to
bu
ECAM PHILOSOPHYPNF
lic
Common LR
DETECTION
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY ( if required )
STATUS
SITUATION ASSESSMENT / DECISION
ST AT US, or
SUMM ARY
WE ATHER
WEATHER
LDG DIS T
LDG DIST
OPERATIONAL AND
AND
COMMERCIAL
COMME
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
DECISIO N
DECISION
NOT
NOTIFY
IFY
PURSER
PURSER/ PAX
/ PAX
OPS
OPS
LR - Version 02b
.d o
PF
N
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
1. DETECTION
First pilot who notices:

MASTER CAUTION/MASTER WARNINGRESET
ANNOUNCE.....TITLE OF FAILURE
FLIES THE AIRCRAFT

NAVIGATES
CONSIDER AUTOMATION USE : A/THR, AP
If failure at takeoff:
NO ACTION until
L
LR
400ft AGL , with safe flight path established.
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
LR
2. ECAMCommon
PROCEDURE
ECAM ....CONFIRM (using SD
and overhead panel)
ORDER.ECAM ACTIONS
ECAM ACTIONS.PERFORM
REQUESTCLEAR name of SYS?
ECAM ACTIONS COMPLETE.CHECK
CONFIRM. CLEAR name of SYS?
ECAM..CLEAR
This is to be repeated for each failure displayed on the

ECAM.
Example :
PF
*Task sharing:
As soon as he announced ECAM
ACTIONS, the PF is in charge of
communications, until all the ECAM
Both pilots should confirm

irreversible/guarded actions
A330 A340
LAND ASAP
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
3. SYSTEM DISPLAY
Analysis
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 until all the displayed system pages

have been reviewed, and the STATUS page is displayed.
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
4. Common
STATUS
REQUEST...STATUS?
CONFIRM..READ STATUS
STATUS .....READ
LIMITATIONS.....CHECK
PROC.....CONSIDER
LANDING DIST&SPEED INCREMENT..CHECK
INOP SYS....CHECK
CONFIRMCLEAR STATUS
REQUESTCLEAR STATUS ?
STATUSCLEAR
ANNOUNCEECAM ACTIONS COMPLETED
Landing distance and approach speed

computation:
For other cases:
QRH
3
1.00
02 ABNEMER
For complex procedures (dual hydraulic

failure or electrical emergency
configuration): Use SUMMARY
Review FCOM procedure:

Applying ECAM procedure ensures
flight safety.
However, referring to FCOM 3.02, if
time permits, may provide useful
additional information.
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common LR
5. SITUATION ASSESSMENT/DECISION
STATUS, or
SUMMARY
WEATHER
WEATHER
LDG
LDG DIST
DIST
OPERATIONAL
OPERATIONAL AND
AND
COMMERCIAL
COMMERCIAL
CONSIDERATIONS
CONSIDERATIONS
ATC
ATC
DECISION
DECISION
NOTIFY
NOTIFY
PURSER
PURSER // PAX
PAX
OPS
OPS
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
6. SYNTHESIS
FLY / NAV
COM
ECAM ACTIONS
(until STATUS page)
Consider:
Normal C/L
OEB
Computer resets
T
E
A
M
CONTINUE ECAM
(STATUS page)
W
O
R
K
APPROACH C/L
DECISION
APPROACH
PREPARATION
Briefing
ECAM APPROACH
PROC (if any)
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
Common LR
Confirmation from both pilots is required, when the action concerns:

Any guarded switch
Master switch or
ADIRS control
Thrust lever is a PF action

given that it may influence flight path
!
How to proceed for confirmation ?
PF
PNF
PF
Hand on related control:
REQUEST...CONFIRM ?
REQUEST ...CONFIRM ?
ACTION.PERFORM
ACTION.PERFORM
ACTION...CHECK
ANSWER....CONFIRM
PNF
ACTION...CHECK
ANSWER....CONFIRM
.d o
IRREVERSIBLE / GUARDED ACTIONS

CONFIRMATION
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
Common LR
Confirmation from both pilots is required, when the action concerns:

Any guarded switch
Master switch or
ADIRS control
Thrust lever is a PF action

given that it may influence flight path
!
PF
PNF
PF
REQUEST...CONFIRM ?
REQUEST ...CONFIRM ?
ACTION.PERFORM
ACTION.PERFORM
ACTION...CHECK
ANSWER....CONFIRM
PNF
ACTION...CHECK
ANSWER....CONFIRM
.d o
IRREVERSIBLE / GUARDED ACTIONS

CONFIRMATION
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
LR
2. ECAMCommon
PROCEDURE
ECAM ....CONFIRM (using SD
and overhead panel)
ORDER.ECAM ACTIONS
ECAM ACTIONS.PERFORM
REQUESTCLEAR name of SYS?
ECAM ACTIONS COMPLETE.CHECK
CONFIRM.CLEAR
Depending on the failure,
LAND ASAP
ECAM..CLEAR
, or
LAND ASAP
the right column of the ECAM procedure.

This is to be repeated for each failure displayed on the
ECAM.
Example :
, may be displayed, in
LAND ASAP
LAND
ASAP
: Land at the next suitable airport.
*Task
sharing:
As soon as he announced ECAM
ACTIONS, the PF is in charge of
communications, until all the ECAM
PF
AMBER LAND ASAP
: Assess the seriousness of the situation and consider the
RED
Both pilots should confirm

irreversible/guarded actions
selection of a suitable airport.
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
Common LR
QRH
2.00
APPR SPD-LDG DIST CORRECTIONS

FOR FAILURES
Determine the landing

distance coefficient.
QRH
4.00
SYS
FAILURE A
FAILURE A
NORM (1)
3
1.1
10
1.2
LANDING DISTANCE WITHOUT

AUTOBRAKE CONF FULL
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.
.d o
LANDING DISTANCE COMPUTATION
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
Common LR
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

VAPP
VLS
LDG CONF
FULL

Add VREF to VREF
Wind correction only

applies when VREF is
lower than 20 kts.
Add wind correction, if applicable

Enter VAPP manually
LDG CONF
CONF 3
If LDG in CONF 3 :
Select CONF 3
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 :
.d o
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
PNF
Common LR
The ECAM shows a VLS, while the QRH shows a VREF .
Shown on PFD,
when landing
conf is
selected
Speed increase for

handling qualities
VLS increase due to
the actual
configuration
VLS OF THE
LANDING CONF
VREF =
VLS CONF FULL
VLS
shown
on
ECAM
VREF
shown
on
QRH
.d o
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
4. Common
STATUS
REQUEST...STATUS?
CONFIRM..READ STATUS
STATUS .....READ
LIMITATIONS.....CHECK
PROC.....CONSIDER
LANDING DIST&SPEED INCREMENT..CHECK
INOP SYS....CHECK
STATUS ?
The PNF should not start reading the STATUS beforeREQUESTCLEAR
confirmation from the PF.
CONFIRMCLEAR STATUS
STATUSCLEAR
ANNOUNCEECAM
ACTIONS COMPLETED
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

Landing distance and approach speed
QRH
Review
FCOM
procedure:
computation:
OEB (if applicable) is to be applied at that time (Refer to QRH 6.00),
02 ABNEMER
6.00procedure ensures
Applying
ECAM
QRH
QRH(Refer to QRH 2.00) flight safety.
Computer
resets(dual
may hydraulic
be considered
For
complex
procedures
3
However,
referring to FCOM 3.02, if
failure or electrical emergency
2.00
time permits, may provide useful
1.00
configuration): Use SUMMARY
additional information.
For other cases:
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
E F
bu
to
k
I S
EIS EFIS DMC FAILURES

DMC
E F
I S
22
E
C
A
M
EIS DMC ECAM FAILURES
DMC
EIS DU FAILURE (ND 1)
EIS DU FAILURE (PFD 2)

LR - Version 02a
.d o
.c
lic
to
bu
PF FAILURES - SWITCHING
PNF
EIS
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
1. EIS EFIS DMC 2 FAULT
DETECTION
CM1
PF
FLIES THE AIRCRAFT

NAVIGATES
ECAM ACTIONS
ECAM PROCEDURES
SYSTEM DISPLAY
STATUS
PF
COMMUNICATES
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
DETECTION
CM1
PF
FLIES THE AIRCRAFT

NAVIGATES
ECAM ACTIONS
ECAM PROCEDURES
SYSTEM DISPLAY
STATUS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
E F
I S

DMC
E F
I S
22
E
C
A
M
bu
to
k
Normal operation is
restored.
Ready for next failure.
DMC

LR - Version 02a
.d o
.c
lic
to
bu
PNF
EIS
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
3.EIS ECAM DMC 3 FAULT
DETECTION
CM2
PF
FLIES THE AIRCRAFT

NAVIGATES
ECAM ACTIONS
ECAM PROCEDURES
SYSTEM DISPLAY
STATUS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
DETECTION
CM2
PF
FLIES THE AIRCRAFT

NAVIGATES
FCOM PROCEDUREAPPLY
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
E F
I S

DMC
E F
I S
22
E
C
A
M
bu
to
k
Normal operation is
restored.
DMC

LR - Version 02a
.d o
.c
lic
to
bu
PNF
EIS
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
5.ND UNIT 1 FAILURE
CM1
DISPLAY UNIT FAILURE PROC..APPLY
NO AUTO SWITCHING
QRH
2.00
ND 1 Unit Blank
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PNF
EIS
1
E F
I S

DMC
E F
I S
22
E
C
A
M
Normal operation is
restored.
DMC

LR - Version 02a
h a n g e Vi
e
c u -tr a c k
6.PFD UNIT 2 FAILURE
CM2
DISPLAY UNIT FAILURE PROC..APPLY
QRH
2.00
PFD AUTO SWITCHING

(PFD has priority over ND)
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
DETECTION
CM1
PF
FLIES THE AIRCRAFT

NAVIGATES
CONSIDER AUTOMATION
EFIS ECAM
EFIS ECAM
DMC1
DMC3
EFIS ECAM
DMC2
ECAM ACTIONS
ECAM PROCEDURES
SYSTEM DISPLAY
STATUS
PF
COMMUNICATES
EFIS ECAM
DMC1
EFIS ECAM
DMC3
EFIS ECAM
DMC2
.d o
ECAM PROCEDURE
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
DETECTION
CM1
PF
FLIES THE AIRCRAFT

NAVIGATES
CONSIDER AUTOMATION
ECAM ACTIONS
EFIS ECAM
ECAM PROCEDURES
SYSTEM DISPLAY
STATUS
to
k
.d o
PNF
ECAM PROCEDURE
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
PF
PNF
DETECTION
CM2
PF
FLIES THE AIRCRAFT

NAVIGATES
CONSIDER AUTOMATION
EFIS ECAM
DMC1
ECAM ACTIONS
ECAM PROCEDURES
SYSTEM DISPLAY
STATUS
PF
PNF
DETECTION
CM2
PF
FLIES THE AIRCRAFT

NAVIGATES
CONSIDER AUTOMATION
FCOM PROCEDUREAPPLY
EFIS ECAM
DMC1
h a n g e Vi
e
N
k
to
bu
EMER CONFIGPNF
FL 260
ELEC EMER
ALL AC BUSES
FAULT
LAND ASAP
ECAM ACTIONS
DECISION
CONFIGURATION

FINAL APPR
A330 - Version 02a
.d o
.c
lic
to
bu
PF ELEC
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
1. ELEC EMER CONFIG
DETECTION
CM1 PF
FLIES THE AIRCRAFT LOSS OF AP, A/THR
ECAM ACTIONS
PF
COMMUNICATES
MAYDAY
ECAM PROCEDURE
RR & PW :
GE :
SYSTEM DISPLAY
STATUS
DECISION
ST AT US, or
SUMM ARY
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMME
COMMERCIAL
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
DECISION
DECISIO N
NOT IFY
PURSER / PAX
PURSER / PAX
OPS
OPS
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
ECAM STATUS...REVIEW
SUMMARY...USE
FMGS.PREPARE
APPR BRIEFING ..............PERFORM
FMGS PREPARATION :
STANDARD
+
QRH
2.00
APP BRIEFING :
STANDARD
+
STATUS
+
QRH
ELEC EMER CONFIG summary :

APP, LDG & G/A parts
1.00
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
3. APPROACH
For slats extension :
LAND RECOVERY..ON
FLIES THE AIRCRAFT
LOSS OF AP
ECAM ACTIONS
Approach synthesis
The Land recovery p/b

Removes non necessary loads (AP1, remaining fuel pump, Radar, HF, ADR)
Restores equipment required for landing (SFCC 1, LGCIU 1, BSCU 1, ILS1, speed limits)
to
k
.d o
PNF
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Electrical Emergency configuration = loss of all AC BUSES
It may be caused by :
the loss of one engine and the failure of the opposite generator
OR
the loss of all GEN
OR
the loss of all engines
simultaneous loss of all GEN
suspect a short-circuit
Probability of a successful
APU GEN coupling is low
Note: The EMER GEN is driven by the Green hydraulic system and powered by the Engine Driven
Pump in this case
bu
to
k
.d o
EMER CONFIGPNF
N
m
.c
lic
to
bu
PF ELEC
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
1. ELEC EMER CONFIG
DETECTION
CM1 PF
Single Chime
ENG THRUST
(every 5 sec)
LOCKED
ECAM ACTIONS
Move the thrust levers to

PF thrust position
the actual
COMMUNICATES
MAYDAY
ECAM PROCEDURE
RR & PW :
GE :
SYSTEM DISPLAY
STATUS
DECISION
ST AT US, or
SUMM ARY
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMME
COMMERCIAL
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
DECISION
DECISIO N
NOT IFY
PURSER / PAX
PURSER / PAX
OPS
OPS
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Monitor
FUEL
page
fuel is fed from one side only

(L FUEL PUMP 2 or STBY R PUMP 2)
Thrust control :
EPR (normal situation)

mode
Overhead
panel
N1 rated
mode
A330 RR & PW
.d o
ECAM PROCEDURE
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
1. ELEC EMER CONFIG
DETECTION
CM1 PF
ECAM ACTIONS
PF
COMMUNICATES
MAYDAY
Monitor
FUEL
page
ECAM PROCEDURE
RR & PW :
GE :
SYSTEM DISPLAY
STATUS
Standby status :

fuel is fed from one side only
RETURN
TOPUMP
NORMAL
TASK R
SHARING
(L FUEL
2 or STBY
PUMP 2)
DECISION
ST AT US, or
SUMM ARY
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMME
COMMERCIAL
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
DECISION
DECISIO N
NOT IFY
PURSER / PAX
PURSER / PAX
OPS
OPS
A330 GE
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Optional
Only EWD available :
If needed, analyse SYSTEM page displayed on the upper ECAM screen:

OTHER SYSTEM PAGES
ELEC
ELEC key on ECPPRESS and HOLD

ELEC PAGE DISPLAYED.....ANALYSE
REQUEST..CLEAR ELEC ?
CONFIRM.CLEAR PRESS
PRESS key on ECP......RELEASE
to
.d o
PNF
SYSTEM DISPLAY
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
To display the status :

ANNOUNCESTATUS ?
CONFIRMREAD STATUS
QRH
1.00
STATUS key on ECP.PRESS and HOLD
ELEC EMER CONFIG

SYS REMAINING
Status overflow :
STATUS
PAGE
release the STATUS key on ECP and push it

again within 2 sec to display the next STATUS page
QRH
1.00
Compute the LDG DIST with the SUMMARY,

according to the estimated weight at DEST
Review FCOM 3.02 procedure (If time permits)
Important note regarding

fuel consumption
speed indication reliability
FCOM
3.02.24
.d o
STATUS
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
XX
DECISION
VAPP
IN
PR
E
4
8
A
P
STATUS
AP
6
BRIEFING
.d o
C
R
Z
E/WD
PROC
to
PNF
USE OF SUMMARY
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
XX
DECISION
VAPP
IN
PR
E
4
8
A
P
STATUS
AP
6
BRIEFING
.d o
C
R
Z
E/WD
PROC
to
PNF
USE OF SUMMARY
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Approach flown manually

with raw data : no AP
ALTN LAW FD
A/THR
to
PNF
CONF 1
CONF 2
GO AROUND
FINAL APPR
NO GEAR RETRACTION
NO AUTO CALLOUTS
CONF 3
LANDING GEAR GRAVITY

EXTENSION
DIRECT LAW
MANUAL PITCH TRIM USE

BE AWARE OF :
NO REVERSER
NO NWS
NO AUTO BRK
PARTIAL LOSS OF GRND SPOILERS
.d o
APPROACH SYNTHESIS
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
to
k
Common LR
LR
HYD : G RSVR LO LVL

LR
F/CTL : PRIM 2 FAULT
F/CTL : ELEV REDUND LOST
LR - Version 02
.d o
.c
lic
to
bu
PF
F/CTL : ELEV REDUND LOST
PNF
lic
C
c u -tr a c k
.d o
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR
1. HYD GCommon
RSVR
LO LVL
DETECTION
FLIES THE AIRCRAFT
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
PF
COMMUNICATES
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
2. F/CTL Common
PRIMLR2 FAULT
DETECTION
FLIES THE AIRCRAFT
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
ELEV REDUND LOST :
SYSTEMS DISPLAYS analysis
Ailerons preset :
STATUS
DECISION
ST AT US, or
SUMM ARY
WEATHER
WE ATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMMERCIAL
COMME
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
DECISION
DECISIO N
PURSER / PAX
NOT IFY
OPS
F/CTL ELEV REDUND LOST
PF
COMMUNICATES
When 2 failures occur affecting :

Flight CTRL computers (PRIM, SEC) &/or HYD supply &/or Servocontrol
& when a 3rd failure loss of some ailerons and one or both elevator(s)
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
PNF
Common LR
G
G
YY
G
G
P3
S1
P1
S1
BB
G
G
BB
P2
P1
P2
YY
G
G
S2
P3
If GREEN HYD + PRIM 2 FAILURES
S2
S1
BB
G
G
G
G
YY
P2
P1
P1
P2
S2
S1
S1
S2
S2
.d o
NORMAL CONDITIONS
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
PNF
Common LR
G
G
YY
G
G
P3
S1
P1
S1
ALL AILERONS
& BOTH ELEV
STILL AVAIL
BB
P2
G
G
BB
P1
P2
YY
G
G
S2
P3
If GREEN HYD + PRIM 2 + SEC 2 FAILURES
S2
S1
BB
G
G
G
G
YY
P2
P1
P1
P2
S2
S1
S1
S2
S2
.d o
GREEN HYD + PRIM 2 LOST
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
k
to
PNF
A330-A340-300
S1
P1
S2
S1
G
G
LO
ST
BB
P2
P1
S2
S1
G
G
S2
YY
G
G
S2
P3
YY
P1
P2
S1
S2
IN THIS SITUATION :
AILERONS go to
zero hinge moment ~14
P2
ST
S1
P2
LO
P3
P1
BB
LO
ST
G
G
G
G
LO
ST
YY
BB
LO
ST
G
G
3 AILERONS
& BOTH ELEV
LOST
TO PREVENT IT :
No ELEV AVAIL to counteract
the resulting Pitch-Up moment
When the first 2 failures occur

The ailerons are PRESET UPWARD
close to zero hinge moment ~ 12
.d o
GREEN HYD + PRIM 2 + SEC 2 LOST
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
Common LR
6. SYSTEM
DISPLAYS
ELEV REDUNDANCY LOST
is not always
associated to aileron preset
If a 3rd failure loss of both ELEV :

The ailerons are preset upwards ~12
If a 3rd failure loss of only one ELEV :

The ailerons are not preset upwards
with high fuel consumption & AP disconnect
The altitude is limited to FL 350

The speed is limited to M.80
The altitude is limited to FL 300

The speed is limited to M.75
to
.d o
PNF
AILERON PRESET
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
bu
to
PNF
Common LR
FM SINGLE FAILURE
FMGC 1
MCDU 1
FM DUAL FAILURE
FMGC 2
MCDU 3
STBY
MCDU 2
LR - Version 03a
.d o
FM FAULT
N
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common LR
1. AUTO FLT
FM 1 FAULT
DETECTION
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
Manual Reset
The FM software automatically resets itself.

FMGC1
FMGC2
PF
COMMUNICATES
FCOM
OPP FMGC IN PROCESS
MCDU 1
4.06
MCDU 2
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
2. AUTO FLT
FM 1+2 FAULT
DETECTION
FLIES THE AIRCRAFT Loss of AP, A/THR and FDs
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
Manual Reset
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
Common LR
3. BACK UP NAVIGATION
MODE
Use BACK UP NAV degraded mode when both FMGCs have failed
BACK UP NAV....SELECT on MCDU MENU page
Manual reset of the FMGEC 1 & 2.. PERFORM
3 successive dual resets without result erase all pilot-entered data (F-PLN, GW, CRZ FL, CI)
FCOM
4.06
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
Common LR
FMGC 1
FMGC 2
FADEC
MCDU 1
MCDU 2
THRUST
LEVERS
MCDU 3
STBY
.d o
NORMAL mode
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
to
PNF
Common LR
FMGC1
FMGC 2
FADEC
MCDU 1
MCDU 2
THRUST
LEVERS
MCDU 3
STBY
.d o
SINGLE mode
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
PNF
Common LR
3. BACK UP NAVIGATION
MODE
Use BACK UP NAV degraded mode when both FMGCs have failed
BACK UP NAV....SELECT on MCDU MENU page
Manual reset of the FMGEC 1 & 2.. PERFORM

If this occurs in flight, reset one FMGC at a time.
Read :
QRH
FCOM
2.00
4.06
3 successive dual resets without result erase all pilot-entered data (F-PLN, GW, CRZ FL, CI)
FCOM
4.06
.d o
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
2. AUTO FLT
FM 1+2 FAULT
DETECTION
NAVIGATES
available if Flight Guidance parts are not lost
ECAM ACTIONS
ECAM PROCEDURE
ENG THRUST LOCKED
Single Chime
(every 5 sec)
Move the Thrust
SYSTEMS
DISPLAYS analysis
Levers to the
actual Thrust
STATUS
PositionManual Reset
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
to
PNF
3.b DUALthe
failure
/ BACK
UP
MODE
The MCDU continuously memorizes
active
F-PLN in
itsNAVIGATION
internal memory.
Common LR
The BACK UP NAV MODE recovers the navigation function through the MCDU and ADIRS.
FLY RAW DATA. TUNE necessary navaids using the RMPs

If both FMGCs fail, the back up navigation provides the following functions :
ON MCDU :
Manual reset FMGC .PERFORM

(non recovered)
F-PLN with auto-sequencing

DIR TO
PROG
A/C position using onside IRS or IRS 3
F-PLN display on ND
No AP / FD NAV mode
FMGC1
FMGC2
SELECT on MCDU MENU page this degraded mode when both FMGCs have failed
MCDU 1
BACK UP
NAV
MCDU 3
MCDU 2
BACK UP
NAV
QRH
2.00
.d o
BACK UP NAVIGATION MODE
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
to
PNF
Common LR
Select the same range and mode on both NDs

DO NOT USE the affected MCDU until PLEASE WAIT message disappears
FCOM
FMGEC 2
4.06
.d o
NAVIGATESSINGLE MODE
lic
PF
bu
y
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
2. AUTO FLT
FM 1+2 FAULT
DETECTION
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
MANUAL
Manual Reset
STATUSRESETS
FOR TRAINING PURPOSE : RETARD MANUAL RESETS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common LR
1. AUTO FLT
FM 1 FAULT
DETECTION
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
MANUAL
Manual Reset
STATUSRESETS
The FM software automatically resets itself.
FOR TRAINING PURPOSE : RETARD MANUAL RESETS

FMGC1
FMGC2
PF
COMMUNICATES
FCOM
OPP FMGC IN PROCESS
MCDU 1
4.06
MCDU 2
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
to
bu
FUEL
FUEL IMBALANCE
IMBALANCE PNF
lic
Common LR
Kg
Kg
LR - Version 02c
.d o
PF
N
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common
A330 LR
1. ADVISORY
When fuel imbalance advisory is triggered, or

upon pilot decision :
FUEL
FUEL PAGE DISPLAYED......ANALYSE
ANNOUNCE...
...ECAM ADVISORY CONDITIONS proc ?
CONFIRM...
.. ECAM ADVISORY CONDITIONS proc
ECAM ADVISORY CONDITIONS proc.APPLY
QRH
2.00
E/WD
FOB at departure was 29 T.
FU
FOB
FOB at
departure
FOB
PF
COMMUNICATES
FU1 FU2
CRUISE
page
If
FOB + FU
<
FOB at departure
or, if the sum decreases :
Suspect a fuel leak
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
A330
2. FUEL LEAK
SUSPECTED
When fuel leak is suspected :

QRH
ORDER. FUEL LEAK proc
FUEL LEAK PROC.....APPLY

2.00
DECISION
Cues to confirm
and locate the leak
QRH
2.00
GRAVITY FUEL FEEDING
When leak is
confirmed
AK
LE
ST AT US, or
SUMM ARY
WE ATHER
WEATHER
LDG DIS
DIST
T
OPERATIONAL AND
OPERATIONAL AND
COMME
COMMERCIAL
RCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
DECISION
DECISIO N
NOT IFY
PURSER
PURSER/ PAX
/ PAX
OPS
OPS
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
A330
3. FUEL L WING
TK LO LVL
ECAM ACTIONS
ECAM PROCEDURE
SYSTEM DISPLAY
STATUS
QRH
REMEMBER FUEL LEAK PROC

RECOMMENDATION:
Disregard FUEL X FEED..ON line
2.00
AK
LE
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
N
lic
to
bu
PF
PNF
SLATS
FAULT IN APPROACH
Common LR
CONF 1
selected
F/CTL SLATS FAULT
LR - Version 02d
.d o
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR FAULT
1. F/CTLCommon
SLATS
DETECTION
SPEED.PULL & SELECT
FLIES THE AIRCRAFT
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
PF
SYSTEM DISPLAY
COMMUNICATES
STATUS
DECISION
No characteristic speed available
SPD
LIM
ST AT US, or
SUMM ARY
WE ATHER
WEATHER
LDG DIS T
LDG DIST
OPERATIONAL
OPERATIONALAND
AND
COMME RCIAL
COMMERCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
ATC
DECISION
DECISIO N
NOT IFY
PURSER
PURSER/ PAX
/ PAX
OPS
OPS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common
LR
2. APPROACH
PREPARATION
FMGS...PREPARE
APPR BRIEFING .............PERFORM
FMGS PREPARATION :
STANDARD
+
A 330 / A340
A340- 600
APP BRIEFING :
STANDARD
+
STATUS
+
QRH
2.00
LANDING WITH SLATS OR

FLAPS JAMMED
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
3. APPROACH
For Flaps extension:

LANDING WITH SLATS OR
2.00 FLAPS JAMMED PROC.APPLY
QRH
Before 500 ft:

APOFF
Monitor AP behaviour (not tuned for abnormal

configuration).
Approach synthesis
Fly a stabilized approach
In case of go around
Second approach
maintain configuration
Diversion
clean the A/C
QRH
2.00
Simulation ends at 500 ft
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
LR FAULT
1. F/CTLCommon
SLATS
DETECTION
SPEED.PULL & SELECT
FLIES THE AIRCRAFT
NAVIGATES
ECAM ACTIONS
ECAM PROCEDURE
PF
COMMUNICATES
SYSTEM DISPLAY
STATUS
Flaps are available
DECISION
Compute the landing distance & speed increment

No characteristic speed available
SPD
LIM
ST AT US, or
SUMM ARY
WE ATHER
WEATHER
LDG DIS T
LDG DIST
OPERATIONAL
OPERATIONALAND
AND
COMME RCIAL
COMMERCIAL
CONSIDERATIONS
CONS
IDERATIONS
ATC
ATC
DECISION
DECISIO N
NOT IFY
PURSER
PURSER/ PAX
/ PAX
OPS
OPS
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
A330/A340-300
Check that NEW DEST

has been entered

VAPP = VREF + VREF

VREF is given in the QRH
MCDU PERF APPR

page
VREF = 30 kt (A330)
VREF = 35 kt (A340)
LDG CONF
VAPP
VLS
FULL
Select CONF FULL

Add VREF to VREF
Enter VAPP manually
LDG CONF
CONF 3
VAPP
VLS
FULL
LDG CONF depends on

the failure configuration
to
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
A340-600
Check that NEW DEST

has been entered

VAPP = VREF + VREF

VREF is given in the QRH
MCDU PERF APPR

page
VREF = 25 kt
LDG CONF
VAPP
VLS
FULL
Select CONF FULL

Add VREF to VREF
Enter VAPP manually
LDG CONF
CONF 3
VAPP
VLS
FULL
LDG CONF depends on

the failure configuration
to
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
To reach next configuration:

Decelerate towards VFE NEXT 5kt
(use placards speeds) but
not below VLS
CONF 2
selected
LANDING GEAR
EXTENSION
Set VAPP on
FCU
GO AROUND
FINAL APPR
to
k
.d o
PNF
APPROACH SYNTHESIS
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
c u -tr a c k
bu
to
PNF
Common LR
LR - Version 02b
.d o
SMOKE
lic
PF
N
.c
.d o
lic
to
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
Common LR
1.DETECTION
Moderate smoke in the cockpit:
DETECTION
FLIES THE AIRCRAFT
NAVIGATES
to
k
.d o
PNF
bu
y
m
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common
LR
2. PROCEDURE:
FIRST
ACTIONS
QRH
ORDER. SMOKE/FUMES/AVNCS SMOKE
SMOKE/FUMES/AVNCS SMOKE.....APPLY
1.00
PF
COMMUNICATES
Apply:
APPLY IMMEDIATLY
These actions have to be applied,

regardless of the origin of smoke.
They might be displayed on the
ECAM.
Keep in mind:
IF DENSE SMOKE, at any time of the
procedure:
LAND ASAP
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common LR
3. PROCEDURE:AIR
COND SMOKE
Moderate smoke persists. You suspect AIR COND SMOKE:
QRH
1.00
FCOM
3.02.26
FCOM SMOKE/FUMES/AVNCS SMOKE procedure

contains some guidelines to determine smoke origin.
Keep in mind:
procedure:
Apply:
IF AIR COND SMOKE SUSPECTED:
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
CommonEQUIPMENT
LR
4. PROCEDURE: CABIN
SMOKE
Moderate smoke persists. You suspect now CABIN EQUIPMENT SMOKE:
QRH
1.00
Keep in mind:
procedure:
Apply:
IF CAB EQUIPMENT SMOKE SUSPECTED:
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common
LR
5.PROCEDURE : SMOKE
SOURCE
NOT DETERMINED
Moderate smoke persists. You cannot determine the source
QRH
1.00
Keep in mind
procedure:
Apply:
IF SMOKE SOURCE CANNOT BE

DETERMINED AND STILL PERSISTS
Try to isolate left, then right

normal AC BUS bars
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
N
bu
y
k
to
PNF
Common
LR
6. PROCEDURE:
DENSE
SMOKE
QRH
Smoke is dense, now.
1.00
Apply:
procedure:
SMOKE/TOXIC
FUMES REMOVAL
Apply:
TO SET ELEC EMER CONFIG
QRH
1.00
Then, apply ECAM ELEC EMER

CONFIG procedure.
.d o
.c
lic
to
PF
lic
C
c u -tr a c k
.d o
bu
O
W
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
h a n g e Vi
e
2006 www.a330jam.com
O
W
N
bu
to
k
.d o
.c
QRH 2.08
lic
w
c u -tr a c k
lic
to
bu
A330
w
.d o
FUEL LEAK - DETERMINATION & MANAGEMENT
XC
er
O
W
F-
PD
h a n g e Vi
e
XC
er
PD
F-
c u -tr a c k
.c
Not an official document
LEAK DETERMINATION
A fuel leak may be detected if:

* the sum of FOB and FU is significantly less than FOB at engine start, or is decreasing
* a passenger (or cabin crew member) observes fuel spray from an engine/pylon or wing tip
* the total fuel quantity is decreasing at an abnormal rate
* a fuel imbalance is developing
* fuel quantity in a tank is decreasing too fast (leak from engine/pylon or hole in the tank)
* a tank is overflowing (due to a pipe rupture in the tank)
* the fuel flow is excessive (engine leak)
* fuel is smelt in the cabin
If visibility permits, leak source may be identified by a visual check from the cabin
Seek a visual inspection early, even at night:
Send a supernumerary crew member (S/O)
back to look out the window. Consider an F/A
also. Check both sides of the aircraft from in
front of and behind the wing.
LEAK SUSPECTED
A fuel leak from

LEAK FROM ENGINE/PYLON
the wing in close
CONFIRMED
vicinity to the engine
may be confused with
a fuel leak from the
engine/pylon itself - as observed
Y
from the cabin. Be careful!
LEAK FROM ENGINE/PYLON
VISUALLY OBSERVED
DECISION
DETERMINATION
SEARCH
PILOT ACTIONS
CAUTION: A FUEL IMBALANCE MAY INDICATE A FUEL LEAK

ALWAYS CONSIDER THE POSSIBILITY OF A FUEL LEAK BEFORE BALANCING FUEL
FU/FOB DISCREPANCY
message with a difference of 3.5 tons.
CERTAIN - NO FUEL LEAK
- CONSIDER FUEL IMBALANCE PROC (crossfeeding)

- CONSIDER FUEL MEASUREMENT / FCMC FAULT
LEAK FROM ENGINE/PYLON NOT

CONFIRMED OR LEAK NOT LOCATED
LAND ASAP
FUEL LEAK LOCATION PROCESS - BEGIN
LAND ASAP
Always keep an accurate and frequent

fuel log. It will show up an inappropriate
quantity decrease. Dont rely on the fuel
system to self-manage as it may in fact
mask a fuel leak with automatic transfer
balancing - trim tank to inner tanks
(eg. Azores Glider). Frequent viewing of
the ECAM fuel page is also an SOP
* ISOLATE FUEL TANKS

- FUEL XFEED - MAINTAIN CLOSED
- CENTRE FUEL PUMPS (AS INSTALLED) OFF
- T-TANK FEED ISOLATE
* MONITOR INNER TANK QUANTITIES
* FOB CHECK >> COMPARE FOB+FU WITH FOB AT DEPARTURE.
IF DIFF IS SIGNIFICANT OR THE FOB+FU DECREASES,
SUSPECT A FUEL LEAK
- SHUTDOWN ENGINE
- FUEL CROSSFEED TO LIVE ENGINE AS REQUIRED
If the leak is not from the engines or cannot be located, it is

imperative that the crossfeed valves are not open.
Y
ENGINE LEAK MAY STILL BE SUSPECTED
ONE INNER TANK DEPLETES

FASTER THAN THE OTHER BY
500 KGS IN LESS THAN 30 MINS
- SHUTDOWN ENGINE
- MONITOR FUEL LEAK
(ESP INNER TANKS)
BOTH INNER TANKS DEPLETE AT SAME RATE
A LEAK FROM THE CENTRE TANK

(AS INSTALLED), TRIM TANK OR
APU/TRIM FEEDING LINE MAY BE SUSPECTED
LEAK CONTINUES AFTER

ENGINE SHUTDOWN
old checklist items from FCOM 3 (unsure why removed?)

- GRAVITY FEEDING (to be considered)
In almost all cases, switching the pumps off (at gravity feed cruise level)
will prevent any further loss of fuel. All pumps must be switched off even if the leak is only from one wing, as there are some failures
on one side that will result in fuel loss from the other side.
- ENGINE START SEL - IGN
- ALL TK PUMPS - OFF
- AVOID NEGATIVE G FACTOR
A LEAK FROM THE CENTRE TANK (AS INSTALLED)

OR TRIM TANK MAY BE SUSPECTED
- L&R CTR PUMPS ON

(as installed)
FUEL SMELL IN THE CABIN
- ENGINE RESTART - CONSIDER

- FUEL LOSS REDUCTIO PROC - CONSIDER
FUEL LOSS REDUCTION PROC CONSIDER
Even if there is only 1,100 kg of fuel left in the collector cell after an
inner tank leak - an engine can be restarted and run at idle for quite
some time.
DO NOT APPLY THE FUEL IMBALANCE PROC. APPROACH AND LANDING CAN BE DONE,
EVEN WITH ONE FULL WING/ONE EMPTY WING.
Y
APU/TRIM TANK FUEL FEED LINE LEAK
ANY FUEL LEAK:

DO NOT USE REVERSE FOR LANDING
FUEL LOSS REDUCTION PROCEDURE
- APU (IF ON) - OFF

- T-TANK FEED - ISOL
Apply this procedure only if suggested by the FUEL LEAK procedure, and if the flight crew needs to minimise fuel loss.
It covers two types of leaks.
1) A leak from the wing > manual trim tank transfer. Symmetrically transfer fuel to both inner tanks and avoids automatic fuel transfer to only the least full inner
tank (as happened in the Azores glider dual flameout case).
2) A leak from the trim tank > manual trim tank transfer to both inner tanks (saves trim tank fuel before it is lost through the leak)
Beware of the WING TK LO LVL ECAM
checklist. If a fuel leak has cause the
Checklist for both cases: If centre tank (as installed) trim tank not empty:
When trim tank empty:
wing tank level to deplete to such a
* L & R CTR PUMPS - ON (as installed)
* T TANK FEED AUTO
quantity that this message occurs, the
* CTR TK XFR - MAN (as installed)
* T TANK MODE - ISOL
checklist says open the X-FEED and
* T TANK FEED - AUTO
When centre tank (as installed) empty:
transfer fuel - not what to do if there is
* T TANK MODE - FWD
* CTR TK XFR - AUTO (as installed)
a leak.

Flight Training Manual - A330 PDF

Uploaded by

Copyright:

Available Formats

Flight Training Manual - A330 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Flight Training Manual - A330 PDF

Uploaded by

Copyright:

Available Formats

What are the different models of aircraft covered in the manual?

What are the different models of aircraft covered in the manual?

How is the manual organized and structured?

How is the manual organized and structured?

y

A330 & A340

Flight Crew Training Manual

Pre-start, Start And Taxi.

Take-off And Initial Climb.

Climb, Cruise And Descent.

Holding And Approach.

Landing, Go-around & Taxi-in.

COMMS & NAV.

Chapter 2 covers procedures and techniques not associated with a particular

SUGGESTIONS AND FEEDBACK

O.I. (30 JUL 04)

ECAM Philosophy And Use

CRM And TEM

Flight Path Vector

REV 1 (6 JUN 05)

AP AND A/THR DISCONNECT

FLIGHT MODE ANNUNCIATOR

REVERSION AND AUTOMATIC SPEED PROTECTION MODES

REV 1 (6 JUN 05)

because the selected target is too high.

REV 1 (6 JUN 05)

System monitoring as follows:

Failure mode, which automatically displays the appropriate

Advisory mode, which automatically displays the appropriate system

Memo, which displays the take-off and landing memos at the

ECAM warnings - in the event of a failure, the E/WD displays crew

Status - the STATUS page provides an operational summary of the

FLIGHT PHASE SPECIFIC PAGES

REV 1 (6 JUN 05)

Cautions And Warnings

In case of a failure during take-off, approach or go-around, ECAM actions

The PF shall monitor all ECAM/checklist actions. Actions associated with

CONFIG - flap/slat setting, approach speed increment, landing distance

REV 1 (6 JUN 05)

ECAM procedures and STATUS, supplemented by a check on the PFD/ND are

Multiple Cautions And Warnings

ECAM Handling In Single Screen Mode

REV 1 (6 JUN 05)

Example Of Crew Coordination And Crosschecking

REV 1 (6 JUN 05)

QRH Summary Sequence

REV 1 (6 JUN 05)

CREW RESOURCE MANAGEMENT (CRM)

THREAT AND ERROR MANAGEMENT (TEM)

Supportive statement: express personal concern, using standard calls if

REV 1 (6 JUN 05)

STANDARD FMA CALLOUTS

Reverse side blank

REV 1 (6 JUN 05)

High Angle of Attack Protection

High Angle Of Attack Protection

REV 1 (6 JUN 05)

REV 1 (6 JUN 05)

Load Factor Protection