Two different approach strategies are available to perform RNAV approaches:
1. Lateral guidance, managed by the FM, and vertical guidance selected by the crew: NAV-FPA (or NAV-V/S) modes.
This strategy applies, when LNAV ONLY (Lateral Navigation only) RNAV approach is intended. 2. Lateral and vertical guidance, managed by the FM: FINAL APP mode.
CHH A318/A319/A320/A321 FLEET PRO-NOR-SOP-19 P 3/28
FCOM ← A → 07 OCT 11
This strategy applies, when LNAV/VNAV (Lateral and Vertical Navigation) RNAV approach is intended.
For straight in approaches, the recommended flying reference is FPV, which should be selected during the initial approach.
Before starting a RNAV (GPS) approach, two navigation systems must be operative: 2 FMS and 2 GPS.
RNAV approach can be performed in NAV-FPA (or NAV-V/S) modes provided:
‐ The approach stored in the navigation database has been produced by approved suppliers compliant with ED76/DO200A requirements, or has been validated and is approved by the operator.
‐ Before starting the approach, the crew must check the lateral FM F-PLN against the published approach chart using MCDU and ND.
‐ The final approach is laterally and vertically monitored, using the appropriate data: the distance to the runway or to the MAP versus altitude is the primary means of vertical navigation, the deviation on the PFD may be unreliable.
RNAV approach can be performed in FINAL APP mode provided:
‐ The approach stored in the navigation database has been produced by approved suppliers compliant with ED76/DO200A requirements, and the vertical flight path has been validated by the operator, or, the lateral and vertical flight path has been validated and approved by the operator.
If no minimum OAT is published on the approach chart, the effect of low OAT on obstacle clearance needs to be evaluated.
‐ The final approach (FAF to runway or MAP), as extracted from the navigation database and inserted in the primary F-PLN including altitude constraints, is not revised by the crew.
‐ Before starting the approach, the crew must check the lateral and the vertical FM F-PLN against the published approach chart, using the MCDU and ND.
‐ The approach trajectory is laterally and vertically intercepted, before the FAF, or equivalent waypoint in the FM F-PLN, so that the aircraft is correctly established on the final approach course before starting the descent.
‐ The final approach is laterally and vertically monitored, using the VDEV and appropriate raw data (distance to the runway, altitude, FPV).
Note: For additional information on recommended flight crew procedures, and on navigation database flight path validation: Refer to FCB-FCB23 Use of Managed Guidance in Approach and NAV Database Validation and the FMGS Pilot's guide (Refer to PRO-NOR-SRP-01-70 Initial Approach).
For RNAV approach WITH GPS PRIMARY
Unless an instrument approach procedure, not requiring GPS PRIMARY, is available at destination or destination alternate (and at required takeoff alternate, and en route alternate), the GPS PRIMARY availability must be verified before flight.
AIME is available worldwide, if 24 GPS satellites or more are operative.
If the number of GPS satellites is 23 or less, check AIME availability using the approved version of the Litton ground-based AIME prediction software.
Before starting the approach, check that GPS PRIMARY is available on both MCDUs. If the GPS PRIMARY LOST indication appears on the ND during the approach, discontinue the approach, unless:
‐ GPS is not required and navigation accuracy is confirmed against the radio NAVAID raw data, or
‐ For RNAV approach not requiring GPS, HIGH accuracy appears on the MCDU with the appropriate RNP value.
‐ If GPS PRIMARY is lost on only one FMGC, the approach can be continued, using the AP/FD associated to the other FMGC.
If the FM/GPS POS DISAGREE ECAM caution is triggered during the approach, discontinue the approach.
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side. For RNAV approach WITHOUT GPS PRIMARY
Before starting the approach, check the FM position accuracy with radio NAVAID raw data. Check, in addition, that HIGH accuracy appears on the MCDU with the specified RNP value. If HIGH accuracy is lost on one FMGC, the approach can be continued with the AP/FD associated to the other FMGC.
If HIGH accuracy is lost on both FMGCs, discontinue the approach.
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side. Applicable to: B-6156, B-6157, B-6169, B-6198, B-6199, B-6210, B-6211, B-6212, B-6215, B-6221, B-6222
GUIDANCE FOR RNAV APPROACHES
Two different approach strategies are available to perform RNAV approaches:
1. Lateral guidance, managed by the FM, and vertical guidance selected by the crew: NAV-FPA (or NAV-V/S) modes.
CHH A318/A319/A320/A321 FLEET PRO-NOR-SOP-19 P 5/28
FCOM ← A → 07 OCT 11
This strategy applies, when LNAV ONLY (Lateral Navigation only) RNAV approach is intended. 2. Lateral and vertical guidance, managed by the FM: FINAL APP mode.
This strategy applies, when LNAV/VNAV (Lateral and Vertical Navigation) RNAV approach is intended.
For straight in approaches, the recommended flying reference is FPV, which should be selected during the initial approach.
Before starting a RNAV (GPS) approach, two navigation systems must be operative: 2 FMS and 2 GPS.
RNAV approach can be performed in NAV-FPA (or NAV-V/S) modes provided:
‐ The approach stored in the navigation database has been produced by approved suppliers compliant with ED76/DO200A requirements, or has been validated and is approved by the operator.
‐ Before starting the approach, the crew must check the lateral FM F-PLN against the published approach chart using MCDU and ND.
‐ The final approach is laterally and vertically monitored, using the appropriate data: the distance to the runway or to the MAP versus altitude is the primary means of vertical navigation, the deviation on the PFD may be unreliable.
RNAV approach can be performed in FINAL APP mode provided:
‐ The approach stored in the navigation database has been produced by approved suppliers compliant with ED76/DO200A requirements, and the vertical flight path has been validated by the operator, or, the lateral and vertical flight path has been validated and approved by the operator.
If no minimum OAT is published on the approach chart, the effect of low OAT on obstacle clearance needs to be evaluated.
‐ The final approach (FAF to runway or MAP), as extracted from the navigation database and inserted in the primary F-PLN including altitude constraints, is not revised by the crew.
‐ Before starting the approach, the crew must check the lateral and the vertical FM F-PLN against the published approach chart, using the MCDU and ND.
‐ The approach trajectory is laterally and vertically intercepted, before the FAF, or equivalent waypoint in the FM F-PLN, so that the aircraft is correctly established on the final approach course before starting the descent.
‐ The final approach is laterally and vertically monitored, using the VDEV and appropriate raw data (distance to the runway, altitude, FPV).
Note: For additional information on recommended flight crew procedures, and on navigation database flight path validation: Refer to FCB-FCB23 Use of Managed Guidance in Approach and NAV Database Validation and the FMGS Pilot's guide (Refer to PRO-NOR-SRP-01-70 Initial Approach).
For RNAV approach WITH GPS PRIMARY
Unless an instrument approach procedure, not requiring GPS PRIMARY, is available at destination or destination alternate (and at required takeoff alternate, and en route alternate), the GPS PRIMARY availability must be verified before flight.
AIME is available worldwide, if 24 GPS satellites or more are operative.
If the number of GPS satellites is 23 or less, check AIME availability using the approved version of the Litton ground-based AIME prediction software.
Before starting the approach, check that GPS PRIMARY is available on both MCDUs. If the GPS PRIMARY LOST indication appears on the ND during the approach, discontinue the approach, unless:
‐ GPS is not required and navigation accuracy is confirmed against the radio NAVAID raw data, or
‐ For RNAV approach not requiring GPS, HIGH accuracy appears on the MCDU with the appropriate RNP value.
‐ If GPS PRIMARY is lost on only one FMGC, the approach can be continued, using the AP/FD associated to the other FMGC.
If the FM/GPS POS DISAGREE ECAM caution is triggered during the approach, discontinue the approach.
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side. For RNAV approach WITHOUT GPS PRIMARY
Before starting the approach, check the FM position accuracy with radio NAVAID raw data. Check, in addition, that HIGH accuracy appears on the MCDU with the specified RNP value. If HIGH accuracy is lost on one FMGC, the approach can be continued with the AP/FD associated to the other FMGC.
If HIGH accuracy is lost on both FMGCs, discontinue the approach.
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side. 1Applicable to: B-6181, B-6182, B-6193, B-6245, B-6401, B-6402, B-6403, B-6412, B-6709, B-6710, B-6723, B-6725, B-6726, B-6727,
B-6743, B-6746, B-6747, B-6748, B-6763, B-6765, B-6789, B-6790, B-6795, B-6811, B-6837, D-AVYF, MSN 5006 Two different approach strategies are available to perform RNAV approaches
1. Lateral guidance, managed by the FM, and vertical guidance selected by the crew : NAV-FPA (or NAV-V/S) modes.
CHH A318/A319/A320/A321 FLEET PRO-NOR-SOP-19 P 7/28
FCOM ← A → 07 OCT 11
Note: Not applicable to RNP AR.
2. Lateral and vertical guidance, managed by the FM : FINAL APP mode.
This strategy applies, when LNAV/VNAV (Lateral and Vertical Navigation) RNAV approach is intended.
For straight in approaches, the recommended flying reference is FPV, which should be selected during the initial approach.
Before starting a RNAV (GPS) approach, two navigation systems must be operative : 2 FMS and 2 GPS.
Before using a RNAV approach, the operator must ensure that approved suppliers compliant with ED76/D0200A requirements have produced the navigation database.
Otherwise, the operator must validate and approve the approach.
For RNP AR approaches, as per ACD, the operator must validate and approve the approaches even if the navigation database provider is ED76/D0200A compliant.
To perform a RNAV approach in NAV-FPA (NAV-V/S) mode, the following recommendations apply: ‐ Before starting the approach, the flight crew must check the lateral FMS F-PLN against the
published approach chart using MCDU and ND.
‐ The flight crew must laterally and vertically monitor the approach, using the distance to the runway or to the MAP versus altitude.
To perform a RNAV approach in FINAL APP mode, the following recommendations apply: ‐ If no minimum OAT is published on the approach chart, the operator must evaluate the effect of
low OAT on obstacle clearance.
‐ The flight crew must not revise the final approach (FAF to runway or MAP), which was extracted from the navigation database.
‐ Before starting the approach, the flight crew must check the lateral and the vertical FMS F-PLN against the published approach chart using MCDU and ND.
‐ The aircraft must laterally and vertically intercept the approach trajectory before the FAF, so that the aircraft is correctly established on the final approach course before starting the descent. ‐ The flight crew must monitor laterally and vertically the approach, using the VDEV and the
distance to the runway or to the MAP versus altitude.
Note: For additional information on recommended flight crew procedures, and on navigation database flight path validation, Refer to "Use of managed guidance in approach and Nav database validation" and the Refer to FMGS Pilot's guide.
For RNAV approach WITH GPS PRIMARY
Unless an instrument approach procedure, not requiring GPS PRIMARY, is available at destination or destination alternate (and at required takeoff alternate, and en route alternate), the GPS PRIMARY availability must be verified before flight.
RAIM is available worldwide, if 24 or more GPS satellites are operative. If the number of GPS satellites is 23 or less, check RAIM availability, using the approved version of the Honeywell ground-based prediction software. If the GPS PRIMARY availability cannot be verified before flight, RAIM availability can be checked in flight, using the PREDICTIVE GPS MCDU page Note: For RNP AR, before flight, the flight crew must check that the GPS Primary is predicted
available, for the ETA. This prediction should take into account the terrain environment. Before starting the approach, check that GPS PRIMARY is available on both MCDUs.
If the GPS PRIMARY LOST indication appears on the ND during the approach, discontinue the approach, unless:
‐ GPS is not required and navigation accuracy is confirmed against the radio NAVAID raw data, or
‐ For RNAV approach not requiring GPS, HIGH accuracy appears on the MCDU with the appropriate RNP value.
‐ If GPS PRIMARY is lost on only one FMGC, the approach can be continued, using the AP/FD associated to the other FMGC.
If the FM/GPS POS DISAGREE ECAM caution is triggered during the approach, discontinue the approach.
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side. For RNAV approach WITHOUT GPS PRIMARY (Not applicable for RNP AR)
Before starting the approach, check the FM position accuracy with radio NAVAID raw data. Check, in addition, that HIGH accuracy appears on the MCDU with the specified RNP value. If HIGH accuracy is lost on one FMGC, the approach can be continued with the AP/FD associated to the other FMGC.
If HIGH accuracy is lost on both FMGCs, discontinue the approach.
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side.
CHH A318/A319/A320/A321 FLEET PRO-NOR-SOP-19 P 9/28
FCOM ← A → 07 OCT 11
Applicable to: B-6413, B-6415, B-6416, B-6417
Two different approach strategies are available to perform RNAV approaches
1. Lateral guidance, managed by the FM, and vertical guidance selected by the crew : NAV-FPA (or NAV-V/S) modes.
This strategy applies, when LNAV ONLY (Lateral Navigation only) RNAV approach is intended. Note: Not applicable to RNP AR.
2. Lateral and vertical guidance, managed by the FM : FINAL APP mode.
This strategy applies, when LNAV/VNAV (Lateral and Vertical Navigation) RNAV approach is intended.
For straight in approaches, the recommended flying reference is FPV, which should be selected during the initial approach.
Before starting a RNAV (GPS) approach, two navigation systems must be operative : 2 FMS and 2 GPS.
Before using a RNAV approach, the operator must ensure that approved suppliers compliant with ED76/D0200A requirements have produced the navigation database.
Otherwise, the operator must validate and approve the approach.
For RNP AR approaches, as per ACD, the operator must validate and approve the approaches even if the navigation database provider is ED76/D0200A compliant.
To perform a RNAV approach in NAV-FPA (NAV-V/S) mode, the following recommendations apply: ‐ Before starting the approach, the flight crew must check the lateral FMS F-PLN against the
published approach chart using MCDU and ND.
‐ The flight crew must laterally and vertically monitor the approach, using the distance to the runway or to the MAP versus altitude.
To perform a RNAV approach in FINAL APP mode, the following recommendations apply: ‐ If no minimum OAT is published on the approach chart, the operator must evaluate the effect of
low OAT on obstacle clearance.
‐ The flight crew must not revise the final approach (FAF to runway or MAP), which was extracted from the navigation database.
‐ Before starting the approach, the flight crew must check the lateral and the vertical FMS F-PLN against the published approach chart using MCDU and ND.
‐ The aircraft must laterally and vertically intercept the approach trajectory before the FAF, so that the aircraft is correctly established on the final approach course before starting the descent. ‐ The flight crew must monitor laterally and vertically the approach, using the VDEV and the
Note: For additional information on recommended flight crew procedures, and on navigation database flight path validation, Refer to "Use of managed guidance in approach and Nav database validation" and the Refer to FMGS Pilot's guide.
For RNAV approach WITH GPS PRIMARY
Unless an instrument approach procedure, not requiring GPS PRIMARY, is available at destination or destination alternate (and at required takeoff alternate, and enroute alternate), the GPS PRIMARY availability must be verified before flight.
AIME is available worldwide, if 24 GPS satellites or more are operative. If the number of GPS satellites is 23 or less, check AIME availability using the approved version of the Litton ground-based AIME prediction software.
Note: For RNP AR, before flight, the flight crew must check that the GPS Primary is predicted available, for the ETA. This prediction should take into account the terrain environment. Before starting the approach, check that GPS PRIMARY is available on both MCDUs.
If the GPS PRIMARY LOST indication appears on the ND during the approach, discontinue the approach, unless:
‐ GPS is not required and navigation accuracy is confirmed against the radio NAVAID raw data, or
‐ For RNAV approach not requiring GPS, HIGH accuracy appears on the MCDU with the appropriate RNP value.
‐ If GPS PRIMARY is lost on only one FMGC, the approach can be continued, using the AP/FD associated to the other FMGC.
If the FM/GPS POS DISAGREE ECAM caution is triggered during the approach, discontinue the approach.
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side. For RNAV approach WITHOUT GPS PRIMARY
Before starting the approach, check the FM position accuracy with radio NAVAID raw data. Check, in addition, that HIGH accuracy appears on the MCDU with the specified RNP value. If HIGH accuracy is lost on one FMGC, the approach can be continued with the AP/FD associated to the other FMGC.
CHH A318/A319/A320/A321 FLEET PRO-NOR-SOP-19 P 11/28
FCOM ← A → 07 OCT 11
If the FMS1/FMS2 POS DIFF message is triggered during the approach, discontinue the approach, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side. Applicable to: ALL