Beruflich Dokumente
Kultur Dokumente
FLIGHT OPERATIONS
SUPPORT
A318/A319/A320/A321
Issued by STL
OEB N: 205/2
File in FCOM Vol 3
FEB 11
SUBJECT:
APPLICABLE TO:
CANCELLED BY:
Operations Engineering Bulletins are issued by Airbus as the need arises to quickly transmit technical and
procedural information. They are distributed to all FCOM holders and to others who need advice of changes to
operational information.
Information in this bulletin is recommended by Airbus but may not be approved by Airworthiness Authorities.
If the procedures contained in this OEB differ from the procedures in the AFM, the AFM remains the reference.
Page 1 of 5
The FMS computes the vertical profile of the final approach backwards
from an anchor point that is the Missed Approach Point (MAP), the Runway
threshold (RWY) or the Final End Point (FEP). The FMS adapts its vertical
profile to take into account for each waypoint, the following Navigation
DataBase data:
- FPAs
- Altitude constraints.
R
R
R
R
R Note 2: The use of FLS is not affected as the computation of the FLS beam
R is not impacted.
R DESCRIPTION OF THE MISBEHAVIOUR
R
R
R
R
R
When the theoretical altitude of the FAF, based on the FPA coded on the
anchor point (called FPA-based altitude in this document), is higher than
or equal to the FAF altitude constraint, the FMS erroneously disregards the
FPA coded on the FAF.
OEB N 205/2
Page 2 of 5
R As a result, the vertical profile before the FAF may erroneously consist in:
R
- A descent segment (not respecting the coded FPA), followed by
R
- A level off at the altitude constraint coded at the FAF.
R Note that this altitude constraint at the FAF should always respect the
R Minimum Obstacle Clearance (MOC) altitude.
See the below illustration (example):
R
Approach chart
Aircraft trajectory
OEB N 205/2
Page 3 of 5
MCDU example
R PROCEDURE:
R The following procedure only applies for flight crew.
R 1) If the operator has established a list of impacted NPAs, updated with
the current Navigation DataBase cycle:
R
When preparing a NPA, the flight crew must check if the procedure is
R
in the list or not:
R
OEB N 205/2
Page 4 of 5
R
R
R
R 2) If the operator has not established a list of impacted NPAs, or if the list
R
is not updated with the current Navigation DataBase cycle:
R
The flight crew must check if the procedure contains (refer to the
R
MCDU example on page 4):
R
- 2 or more FPA between the descent point and the
R
MAP/RWY/FEP and
R
- An AT OR ABOVE altitude constraint coded at the FAF
R
R
R
R Notes:
R
1) On an impacted NPA, NAV mode may still be used for lateral
R
guidance.
R
2) For an impacted RNAV approach, the flight crew must not use the
R
LNAV/VNAV minimum.
In all cases, the flight crew should check the approach procedure through
the MCDU (Refer to Standard Operating Procedures Descent
Preparation). If during the approach, the aircraft does not follow the
published vertical profile, the flight crew should revert into selected vertical
R guidance mode.
CORRECTIVE ACTION:
The future Thales/GE FMS 2 R1A S7 standard will cancel this OEB (MOD
and Airbus SB TBD).
Note: The interchangeability code, given in the Illustrated Part Catalog (IPC),
indicates the conditions for interchangeability of equipment. After installation of
corrective modification(s)/SB(s), if an Operator reinstalls any equipment affected by
this OEB it is the Operator's responsibility to ensure that the recommendations
given in this OEB are applied again for the applicable aircraft.
OEB N 205/2
Page 5 of 5