DESCENT PREPARATION
Descent preparation and arrival briefing should be completed before top of descent.
LANDING INFORMATION
WEATHER AND LANDING INFORMATION OBTAIN PM
Check the weather reports and runway conditions at destination and alternate airports. Airfield data, if any, should include the runway to be used for arrival.
When the aircraft operates in low OAT conditions, consider altitude corrections for low temperature.
Note: When icing conditions with OAT below +1 °C (34 °F) are expected at destination or alternate airports, consider to perform engine ice shedding on ground during taxi-in. PRO-NOR-SUP-ADVWXR
NAV CHARTS CLIPBOARD PREPARE BOTH
Prepare the charts for arrival navigation and for the expected approach procedure and verify that both flight crewmembers refer to the same chart reference.
BAROMETRIC REFERENCE
BAROMETRIC REFERENCE PRESET PF-PM
Preset the QNH (QFE) on the ISIS.
ECAM STATUS
ECAM STATUS CHECK PM
Check the ECAM status page before completing the approach checks. Take particular note of any degradation in landing capability, or any other aspect affecting the approach and landing.
- The ECAM STATUS page automatically appears, if not empty, when the BARO setting is selected.
LANDING PERFORMANCE
LANDING CONDITIONS CONFIRM PF-PM
Perform an in-flight landing performance assessment if the landing conditions changed compared with the landing distance computation at dispatch, or with a previous computation (e.g. runway, weather conditions, in-flight failure affecting performance, diversion).FCTM/PR-NP-SOP-160
- If landing conditions changed:
LANDING PERF DATA COMPUTE PF-PM
The PF and the PM independently compute the landing distance performance data, based on the new conditions at arrival.
Note:
1. If the weather conditions are expected to change at the landing airport, or in the event of significant precipitation, the flight crew should consider a second calculation of the in-flight landing distance with the worst possible runway condition.
2. The selection of REV MAX is the standard practice for landing. However, on DRY runways the flight crew may select REV IDLE. On WET runways (runway surface condition GOOD), the flight crew may select REV IDLE, if all the following conditions are satisfied:
- A landing distance assessment has been made with the following parameters:
- MEDIUM TO POOR landing performance level for the in-flight landing distance computation
- No reverser credit.
- The result of this landing distance assessment is within the LDA.
LANDING PERF DATA CROSSCHECK BOTH
The PF and the PM compare their EFB to ensure that the computations are the same. FCTM/PR-NP-SOP-160
FMS
ARRIVAL page COMPLETE/CHECK PF
Insert APPR, STAR, TRANS and APPR VIA if applicable. (Access by lateral revision at destination).
F-PLN A page CHECK PF
- Check that the F-PLN agrees with the planned approach and missed approach
- Check the F-PLN (approach and Missed Approach tracks and distances) vs. the approach charts, using the ND in PLAN mode as necessary
- Check speed constraints. Add new speed constraints if required.
- Check altitude constraints. Add new altitude constraints if required.
Note: The FMS may have deleted the altitude constraints that are at or above the CRZ FL, or at or above any previous lower CRZ FL in the case of step climbs. DSC-22_20-30-20-05
In that case:
- Insert again the affected procedures (STAR, APPR VIA or TRANS)
The FMS keeps the altitude constraints that are below the CRZ FL, and deletes again the altitude constraints that are above current CRZ FL. The FMS may also delete the altitude constraints that are at current CRZ FL, and the altitude constraint windows that have a constraint at or above current CRZ FL.
- Manually enter the altitude constraints that are below current CRZ
FL using the MCDU Vertical Revision pages.
It is not possible to enter an altitude constraint at the CRZ FL.
In the case of an "AT" or "AT OR ABOVE" altitude constraint at the
CRZ FL, the flight crew must select the DES mode only after the aircraft reaches the position of the altitude constraint to prevent an early descent.
- In all cases, do not modify the final approach (FAF to runway or MAP), including altitude constraints
- Identify the position and the altitude of Final Descent Point (FDP) and check the value of the
FPA after this FDP
- If a TOO STEEP PATH message is displayed after the FDP, do not use FINAL APP guidance for approach
- Identify the Missed Approach Point.