08 - RNP Apch

ICAO PBN Workshop
Tanzania
RNP APCH
RNP APCH overview
RNP APCH introduction

Airborne RNP APCH system performance
LNAV
LNAV/VNAV
LPV
RNP APCH Operational approval process
2
AIRBUS Operations S.A.S. All rights reserved. Confidential and proprietary document.
RNP APCH overview

LNAV
LNAV/VNAV
LPV
3

RNP APCH is the PBN navigation specification dealing with approach
procedure
using GNSS.
Those approaches are generally charted under the name RNAV(GNSS) or
RNAV(GPS)
A RNP APCH approach covers three possible types of approach procedure:

Non-precision approach
Identified on the IAC chart by the minima line
LNAV - MDA/MDH
APV BaroVNAV approach
LNAV/VNAV - DA/DH
APV SBAS approach
LPV - DA/DH
APV stands for Approach with vertical Guidance
4

ICAO Classification
NPA approaches
APV approaches
PA approaches
Non-precision approaches
Approaches with vertical

guidance
Precision approaches
Conventional
procedure
RNP APCH
VOR/DME
NPA GPS
RNP APCH
APV Baro
Conventional
procedure
APV SBAS
ILS
NDB
MLS
Localizer
PAR
LNAV
LNAV/VNAV
GLS
LPV
PBN
APV approaches offer vertical guidance but with a lower performance that the one required for a precision
approach
5
6

Airborne architecture Outlines
Airborne architecture is similar to the one supporting Enroute and
Terminal operations:
Main difference between General aviation aircraft and air transport
Single sensor versus multisensor

Single system versus dual system
Complexity of the installation
Coupling with the autopilot and/or flight director
Level of RNAV functionalities
7

Airborne architecture Outlines
Lateral guidance is computed by the airborne system.
The lateral guidance is displayed on a lateral deviation indication (a CDI, a HSI or
an EFIS). A moving map display could be also used.
Digital cross
track
0.2
R
Vertical guidance is computed by certain RNAV systems: the vertical

guidance is based on GNSS (SBAS or GBAS concept) or on
pressure-altitude (Baro VNAV concept)
The vertical guidance is displayed on a vertical deviation indication (a VDI, a HSI
or an EFIS).
8

Materials for RNP APCH LNAV and LNAV/VNAV
ICAO Doc 9613 PBN Manuel VOL II Part C Chapter 5: RNP APCH
Airworthiness Reference
EASA AMC 20-27
FAA AC 20-130A, AC 20-138A, AC 20-129, (replaced by AC 20-138B and
C)
ETSO/TSO C129a, ETSO/TSO C145 and C146
Operational Reference
EASA AMC 20-27: airworthiness approval and operational criteria for
RNP approach (RNP APCH) operations
DGAC OPS directive F 2012-02
DGAC Technical guidelines for RNP APCH operations known as
RNAV(GNSS)
FAA AC 90-105
9

Materials for RNP APCH LPV
ICAO Doc 9613 PBN Manuel VOL II Part C Chapter 5: RNP APCH
Airworthiness Reference
EASA AMC 20-28 airworthiness approval for LPV operations
FAA AC Airworthiness : 20-130A, AC 20-138A (replaced by AC 20138C)
ETSO/TSO C145 and C146
Operational Reference
EASA AMC 20-28 airworthiness approval and operational criteria for
LPV operations
DGAC : OPS directive F 2012-02
DGAC Guidelines for RNP APCH operations also known as
RNAV(GNSS)
FAA AC OPS :AC 90-107,.
10
RNP APCH overview

LNAV
LNAV/VNAV
LPV
11
RNP APCH LNAV aircraft requirements

non-precision approach - RNAV(GNSS) LNAV
RNAV(GNSS) LNAV approaches are not associated with a vertical track in space.
Lateral guidance is by means of the RNAV/GNSS system and is based on GNSS

positioning
Vertical flight management the same as for non-precision approaches

(VOR/DME, NDB, etc.),
In accordance with EU OPS, non-precision approaches meeting CDFA criteria

must be carried out using the CDFA technique.
For a non-precision RNAV(GNSS) / LNAV minima approach:

The operator must comply with EASA AMC 20-27 (chapter 10 and appendix 4)
12
RNP APCH
Charted RNAV(GNSS) or RNAV(GPS)
Non-precision approach (AMC 20-27)

Lateral guidance: GNSS
Vertical plane management: CDFA
(use of V/S, FPA or (Baro) VNAV for aircraft
so equipped)
13

An airborne system approved for RNP APCH / LNAV
- Airworthiness and operational criteria are defined in a European document AMC
-
20-27 and are consistent with the ICAO PBN manual

An RNAV system based on GNSS positioning.
Lateral navigation
-
Flight plan construction builds from an embedded navigation data base

Provides display of all necessary flight navigation parameters in order to conduct
a safe approach
Vertical navigation
- No requirement.
- Vertical flight management the same as for non-precision approaches
(VOR/DME, NDB, etc.),

- In accordance with OPS European regulation, non-precision approaches meeting
CDFA criteria must be carried out using the CDFA technique.
14

The airborne RNAV/GNSS system should be:
a stand-alone GPS system compliant with TSO C129a/ETSO C129a
class A1 or TSO C 146A (SBAS receiver)
a multisensor system with GNSS sensor compliant with TSO C
129()/ETSO C129() class B1/B3,C1 or C3 or TSO C 145A.
For multi sensor system, the active positioning sensor must be indicated to
the crew.
The active sensor must be the GPS when conducting the approach.
Approach procedure are designed in accordance with PANS OPS Doc
8168, Volume II,
Part III, Section 3, Chapter 3.
Airborne certification criteria have been developed for straight segment
approach
(e.g. T or Y approach) to accommodate basic stand-alone GNSS receiver.
15

Accuracy
The lateral TSE must be within 1 NM ( 95%) for the initial, intermediate
and missed approach segment
The lateral TSE must be within 0.3 NM (95%) for the Final segment
The Total System Error is the Root Sum Square (RSS) of:
Navigation system error (NSE)

Path definition error (PDE)
Flight technical error (FTE)
Desired path
95%
0.3 NM
FTE
Defined path
0.3 NM
16
PDE
TSE
NSE
Actual position
Estimated
position

Integrity and continuity
Total loss of navigation must be remote at aircraft

level (occurrence less than 10-5/per flight hour)
Erroneous displayed information must be remote at

system level (occurrence less than 10-5/ per
approach)
An On Board Performance monitoring and Alerting

Function is required
17

Functional criteria
Continuous indication of aircraft position
relative to track on a navigation display
situated in pilot primary field of view
Or
Position indication on an approved
moving map display
Lateral deviation display
with +/- 0.3 Nm Full Scale on the
Final segment
Cross track error
18
Functional criteria
Capability for the Direct To function (1)

Display of distance and bearing to the active waypoint (2)
Display of ground speed or time to the active waypoint (3)
Display of the identification of the active (TO) waypoint (4)
Display of the active navigation sensor type for multi-sensor
systems
(2)
(1)
(3)
(4)
19

Functional criteria
Navigation Data Base
- Storage of the complete approach procedure including the missed approach
- Selection of the approach by its name (e.g RNAV(GNSS) RWY 13L)
Capability to execute leg transitions and maintain tracks consistent with the
following path terminators
- Initial Fix (I.F); Track between two Fixes (T.F) and Direct to a Fix (D.F)
Automatic leg sequencing and associated turn anticipation.

- Capability to execute transition database procedures (Fly-over and Fly-by turns)
IAF
Fly By turn
IF
IF
Theoretical
transition area
20
TF
TF
FAF
Rwy
MAPt

Functional criteria
Enhanced navigation displays improve
lateral situational awareness,
navigation monitoring and
approach verification (flight plan validation).
Autopilot and/or Flight Director coupling is

required if TSE (accuracy) in manual flight
cannot be maintained.
Display indicator with course selector automatically slaved to the RNAV computed
path is highly recommended to alleviate crew workload.
21
LNAV & CDFA

European Ops requirement (OPS 1.430)
All non-precision approaches shall be flown using the continuous descent final approaches
(CDFA) technique
FAF
CDFA profile - No flight Level including at MDA
DA = MDA + x ft
MAPT
MOC
MDA
NON CDFA
Profile
22
LNAV & CDFA

Continuous descent path
Indicated
Minimun Descent Altitude

23
Distance altitude Table
LNAV & CDFA
CDFA is a flight technique and does not recommend any

particular on-board means.
It can be carried out using vertical speed (V/S) or flight path angle
(FPA) indications, or the (Baro) VNAV function if available.
the vertical path trajectory is checked using the distance - altitude

table and/or the table giving the flight time and vertical speed
between the FAF and the MAPt.
24
LNAV & CDFA
The notion of MDA disappears because CDFA no longer allows a level flight
segment to the MAPt.
The CDFA technique requires a go-around if the visual references are not acquired
at a DA(H) (decision altitude/height).
MDA is determined from an OCA which does not take into account the height loss at
go around
MDA (Minimum Descent Altitude) cannot be used as a DA (Decision Altitude)
without a specific assessment:
To use the add-on concept: DA= MDA+xxFt

(e.g. xx is based on aircraft performance or
could be a fixed value of 50 Ft )
To assess from an obstacle point of view the

area below the MDA zone
(e.g VSS, MAPt location ).
25
RNP APCH overview

LNAV
LNAV/VNAV
LPV
26
RNP APCH LNAV/VNAV aircraft requirements

APV BaroVNAV RNAV(GNSS) LNAV/VNAV
Lateral guidance is by means of the RNAV/GNSS system and is based on GNSS

positioning
Vertical guidance uses the (baro) VNAV function,
Certification criteria are included in EASA AMC 20-27.
27
RNP APCH LNAV/VNAV
APV BaroVNAV (AMC 20-27)

Lateral guidance: GNSS
Vertical guidance:
(Baro)VNAV
28
RNP APCH - LNAV/VNAV

Baro-VNAV systems are already fitted
onboard Air Transport aircraft and business
jet.
Use of Baro-altitude data (aircraft

anemometric data) as the primary
information to elaborate the vertical
guidance.
Static probes
Air Data Computer
The integrated navigation system (eg FMS) computes a vertical

guidance based on baro altitude data and the vertical path to be
flown stored in the navigation data base.
29
Static
probes
RNP APCH - LNAV/VNAV
Symbology
1) Lateral deviation
2) Vertical deviation
30
Generally lateral and

vertical guidance are
linear (e.g. full scale +/200 ft)
But there is now design

with ILS look alike
(angular) presentation
Innovation and commonality - FLS Non Precision Approaches :

Principles
Virtual FLS beam built by the FMS according to database information

corresponding to the NPA selected by the crew
defined by an anchor point, a slope, a course
FLS beam
FLS beam
FAF
Course
Anchor Point
FAF
Anchor Point
Slope
MMR computes lateral and vertical deviations between FLS beam and FMS A/C position
A/C is guided on the FLS beam re-using FG ILS guidance laws
FLS parameters and FLS beam are displayed on ND/PFD for pilot cross check
Innovation and commonality - FLS Non Precision Approaches :

PFD
Guidance modes
Approach capability
FLS info
2 Pseudo G/S scale
(Anchor point id,

slope,
& index
distance to rway
threshold)
1
4
Course pointer
Pseudo LOC scale &

index
RNP APCH - LNAV/VNAV aircraft requirements

Approach designed i.a.w APV Baro VNAV PANS OPS criteria.
APV Baro-VNAV approach procedures are classified as instrument
procedures in support of approach and landing operations with vertical

guidance (APV).
Approach plate clearly indicates this type of operation:

-
LNAV/VNAV minima specified in the minimum box

Use of a DA(H) and not a MDA
VPA indicated in
RDH (Wpt coordinates, height)
Temperature limitation
33

Navigation data base should contain WPTs and RNAV/VNAV
information (RDH and VPA).
The approach (lateral and vertical elements) loaded into the RNAV
system must be validated by the operator
Longitudinal accuracy of the RNAV system must be at least

0.3 NM (95%) to bound the horizontal coupling error (impact of
longitudinal error on the vertical plane).
34
35

APV BAROVNAV deviation must be displayed on a vertical deviation
display (HSI, EHSI, VDI).
This display must be used as primary flight instruments for the approach.
The display must be visible to the pilot and located in the primary field of
view
=> suitable fullscale deflection.
The non-numeric display must allow the fight crew to readily distinguish if
the vertical deviation exceeds 75 feet.
If not => it may imply the use of FD or A/P provided an adequate numeric
display to allow the pilot to readily distinguish if the vertical deviation
exceeds 75 feet
36
Obstacles assessed through OAS

Obstacle Assessment Surface
DA/H Decision
Altitude/ Height
Final Approach Surface
37

The Baro-VNAV is the vertical primary guidance during an
APV Baro VNAV approach
Accuracy and integrity performance must be commensurate with this
operation
The aircraft altimetry system should be compliant either to:

FAA TSO-C106, Air Data Computer or
Air data system, ARINC 706, Mark 5 Air Data System or
Barometric altimeter system compliant with DO-88 (Altimetry) and/or
ED-26 MPS for Airborne Altitude Measurements and Coding Systems)
or
Type certified integrated systems providing an Air Data System
capability comparable to Arinc 706 Air Data System
38

ASE (Altimetry system Error): Altimetry system performance is demonstrated
separately through the static pressure systems certification (e.g. FAR or CS 25.1325
compliance)
ASE performance must be better than 30 feet per 100 KIAS.

Altimetry systems meeting such a requirement will satisfy the ASE requirements for APV
Baro-VNAV operation.
VNAV accuracy : the error of the airborne VNAV equipment, excluding altimetry,
should be less than 150 ft (99,7%) when the aircraft is below 5000 ft and is
descending.
FTE should be less than 200 ft (99,7%) when the aircraft is below 5000 ft and is
descending.
In all cases vertical TSE, excluding ASE, must be less than 224 ft (99,7%) when the
aircraft is below 5000 ft and is descending.
An acceptable means of complying with these accuracy requirements is to have an
RNAV system approved for VNAV approaches in accordance with the criteria of FAA
AC20-129 and an altimetry system approved in accordance with FAR/CS 25.1325 or
equivalent.
AMC 20-27 has more stringent requirements than AC 20-129 regarding

TSE
AC 20-138C has even more stringent requirements than AMC 20-27

regarding TSE
39
RNP APCH overview

LNAV
LNAV/VNAV
LPV
40
RNP APCH - LPV
aircraft requirements
APV SBAS RNAV(GNSS) LPV
Lateral and vertical guidance use the RNAV/GNSS system and are
based on GNSS positioning using the GPS signal and the SBAS (WAAS
in the United States and EGNOS in Europe).
The system certification criteria : EASA AMC 20-28.
41
RNP APCH LPV
Display information : ILS look alike
Angular deviations lateral and vertical
Accuracy
Latral: 1.5 m (95%)

Vertical: 2 m (95%)
Alert Limit for the current LPV

HAL = 40 m
VAL= 50 m
Publication of a FAS datablock (for the database encoder) => Final

Segment
42
RNP APCH LPV aircraft requirements

SBAS is designed to improve the
accuracy, integrity and availability of the
Global Positioning System (GPS)
required by civilian air navigation for
approaches
SBASs are regional systems: WAAS in
US, EGNOS in Europe.
The approach operation associated to
SBAS is named LPV (Localizer
Precision with Vertical guidance).
Provides lateral and vertical guidance

Thousands LPV approaches have been
published in the US
43
SBAS coverage
GAGAN
70
60
50
40
EGNOS in ECAC
area
30
20
-40
44
-30
-20
-10
10
20
30
ECAC : European civil aviation conference
40

SBAS is based on a network of several ground reference stations that covers the
defined service area.
Signals from GPS satellites are received by these ground reference stations. Each
of them, precisely surveyed, receive GPS signals and determine if any errors exist.
Each reference station in the network relays the data to a master station where
correction information is computed.
A correction message is prepared and uplinked to a geosynchronous satellite. The

message is then broadcast from the satellite on the same frequency as GPS to
receivers on board aircraft which are within the broadcast coverage area of the
SBAS.
These communications satellites also act as additional navigation satellites for the
aircraft, thus, providing additional navigation signals for position
determination.
45
RNP APCH LPV
EGNOS channel
APV SBAS (AMC 20-28)

Lateral guidance: GNSS +
SBAS
46

3D position and integrity
computation
Receive signal from

GPS and
geosynchronous
47
satellites
Compute lat and vertical

deviation from 3D position
and approach to be flown
Include the 3D approach

path in a FAS data_block
protected by a CRC
Man Machine Interface:

e.g. approach selection,

Two Types of SBAS receiver:
Standalone system incorporating the receiver, the RNAV computer, the nav data
base and the Man Machine Interface

SBAS sensor incorporating only the receiver part. Sensor must be connected to an
integrated navigation system (ex FMS).
The technical standard for the approval of these systems is the DO 229()
(RTCA).
It specifies functional and operational classes.

It specifies technical requirements
FAA and European regulation for equipment qualification standard based on

DO 229():
E/TSO C146() for stand-alone receiver

E/TSO C145() for SBAS sensor.
Regulation for SBAS aircraft certification:
FAA AC 20-138A/ 138C

EASA AMC 20-28 has been issued end of 2008 to address LPV operations.
48

Standalone System (E/TSO C146a)
Functional classes:
GAMMA (receiver +RNAV +D/B+IHM)
Operational classes:
1: Oceanic, Enroute continental, terminal (arrival and departure), non precision approach
2 : Operational class 1+ LNAV/VNAV
3 : Operational class 2+ LPV
SBAS Sensor (E/TSO C145a)

Functional Class:
BETA (receiver only)
Operational classes
1: Oceanic, Enroute continental, terminal (arrival and departure), non precision approach
2 : Operational class 1+ LNAV/VNAV
3 : Operational class 2+ LPV
For LPV approach it is necessary to have :

A GAMMA class 3 stand-alone system or
A multisensor system integrating a BETA class 3 sensor
49

Integrity
The system shall indicate that the navigation system is no longer adequate
to conduct a LPV approach by means of a warning flag or equivalent
indicator on the vertical and lateral navigation display when the
horizontal protection level (HPL) exceeds the alert limit (HAL) or when
the vertical protection level (VPL) exceeds the alert limit (VAL).
Horizontal Alert Limit (HAL) and Vertical Alert Limit (VAL) are stored in the
navigation database for the approach to be flown (FAS data Block)
50
AICSAM - GNSS Concept and GNSS Based Operations - GXP - Ref. PR1414183 - Issue 1
15/10/2014
Different GNSS Performance Levels

LNAV/VNAV Basic GPS (lateral) + barometric (vertical)
APV I SBAS: EGNOS, WAAS, MSAS, GAGAN

APV II SBAS: EGNOS, Galileo
Cat I GLS with GBAS or dual freq SBAS

50 m
20 m
10 m
40 m
556 m
Sketch of relative Alarm Limit Box for the different GNSS Performance levels.
Represents the containment of the uncertainty on aircraft position at 10-7
probability
RNP APCH LPV
For Lateral and Vertical Navigation, the system enables the aircraft to fly relative
to a 3D final approach path which is provided by the on-board navigation
database.
The on-board navigation database element defining the LPV Final Approach
Segment is the FAS data block. This FAS Data Block contains the lateral and
vertical parameters, which define the approach to be flown. Each FAS Data
Block ends with a CRC, which wraps around the approach data
52
RNP APCH LPV FAS data Block
53

The deviation display shall have a suitable full-scale deflection
based on the required track keeping accuracy.
The lateral and vertical Full Scale Deflection are angular and dependant
of the lateral and vertical definitions of the Final Approach Segment Path
contained in the FAS data block.
ILS Look Alike

Concept
Lateral full scale

deflection
Vertical full scale
deflection
54
RNP APCH LPV
LPV
55
RNP APCH overview

LNAV
LNAV/VNAV
LPV
56
Approval process
A/C eligibility
Flight OPS Manual
57
RNP APCH Approval Process

Public Transport
To conduct an RNAV(GNSS) approach, the airline must have been

approved by its supervisory authority. The AOC (Air Operator's Certificate)
must refer to the approved operational capability per type of aircraft.
General aviation
Pilots holding licenses issued by DGAC
Before conducting an RNAV(GNSS) approach, the aircraft must have been

certified for this type of approach and the pilot must have undergone training
approved by the DGAC in accordance with Technical guidelines for RNP
APCH operations known as RNAV(GNSS).
Other pilots
To conduct an RNAV(GNSS) approach, the aircraft and its crew must fulfill
the directive of the authority issuing the pilots license.
58
RNP APCH - A/C eligibility

Eligibility of the A/C is determined through the analyses of the AFM
RNP APCH LNAV
In the AMC 20-27 : chapter 8.3 Existing Installations
An existing statement in the AFM that indicates the aircraft is
approved:
To perform RNP 0.3 GNSS approaches or,
For instrument approaches including a specification of RNP GNSS
capability that meets RNP 0.3
=> is considered acceptable for lateral performance.
59
RNP APCH LNAV/VNAV A/C eligibility

RNP APCH LNAV / VNAV
No such statement in the AMC 20-27.

No harmonization between EASA and FAA
Performance requirements for the vertical TSE more stringent than those in AC 20129 and PBN manual.
DGAC considers the following chapter from AMC 20-27 :
Vertical deviation has to be clearly shown either on PFD or ND (monitoring on

MCDU or CDU of numeric vertical deviation not accepted)
60
RNP APCH LNAV/VNAV A/C eligibility

Example of Management of lateral and
vertical
deviations
Lateral
PNF announces cross track when 0.2Nm
of deviations
PNF announces go around when 0.3Nm of

deviations
Vertical
PNF announces VDEV when 1/2 dot of
deviation (50 )
PNF announces go around when 3/4 dot of

deviation (75)
Use of the FD is mandatory

Use of AP is recommended
61
RNP APCH LNAV /VNAV A/C eligibility
1 : Mode selected
4 : NPS deviation Pointer

Indicates the navigation path
relative to airplane position
62
2 and 5 : Deviation scale

Lateral and Vertical Scales
Outer white lines represent RNP. Center white line represents
position
Bars represent ANP
Area between bars indicates margin available to remain within RNP
RNP APCH LPV A/C eligibility
For LPV : AFM must mentions compliance to AMC

20-28
63
RNP APCH - Application CONTENT OF FLIGHT MANUAL
AFM specifying the RNP capability of the aircraft to determine

Aircraft eligibility for RNP APCH
OPS Manual shall contain
A description of the operation of the RNAV/GNSS navigation system

used.
pre-flight planning procedures.
normal procedures in flight.
contingency procedures.
Database integrity monitoring policy.
Flight crew training requirements.
All operators must also amend the check-lists, QRH and Minimum
Equipment Lists (MEL) (or the document used for this purpose in
general aviation) in order to incorporate the use of RNAV/GNSS
equipment for this type of approach.
64
Operational approval - Pre-flight planning
The flight plan has to be filled in in accordance with the capability.
The navigation database has to be current
Selection of aerodromes
INA Initial and intermediate approach can be RNAV1
Check appropriate approval

RNAV(GNSS) and alternate aerodrome
If no alternate destination aerodrome: the destination aerodrome must be

accessible by means of a conventional approach (non RNAV(GNSS)).
If at least one alternate aerodrome is require : The alternate aerodromes

must be accessible by means of a conventional approach (non
RNAV(GNSS))
An RNAV(GNSS) approach cannot be used to select an alternate

aerodrome at take-off.
For APV SBAS (LPV), the previous requirements apply, unless the
airspace authority concerned does not so require. These requirements
apply in French airspace.
65
Check the MEL
GNSS coverage and availability of the RAIM function (or

equivalent)
Check GNSS NOTAMs
66
GPS NOTAMs: concerning the operating status of the GPS

constellation.
RAIM NOTAMs: supplied for each aerodrome for which an
RNAV (GNSS) approach is published, leading to LNAV or
LN AV/VNAV minima.
SBAS NOTAMs: concerning the unavailability of the LPV
procedure with regard to the performance of the SBAS
system. These NOTAMs are supplied for each aerodrome
for which an RNAV (GNSS) approach leading to LPV
minima is published. (EGNOS NOTAM in Europe)
For an LNAV or LNAV/VNAV approach

Check RAIM availability at the estimated time of arrival (ETA) +/-15
minutes,
RAIM prediction NOTAMs or

the on-board equipment prediction tool
insert satellite unavailability info into the predictive programme
if (ETA) differs by more than 15 minutes => Check again RAIM before
starting the approach,

For some avionics architectures, RAIM prediction may only be required in
certain cases (depending on the availability of the constellation) report to the
AFM.
67
For an LPV approach

Check the SBAS NOTAMs (in Europe EGNOS NOTAMs) for availability of the approach.
No RAIM prediction is required,
integrity is managed directly by the SBAS geostationary satellites.
68
RNP APCH - Normal procedures
Prior to commencing the approach procedure

Before the IAF, the pilot shall check that the correct procedure,
including missed approach, has been loaded.
Check flight path displayed on the navigation screen (ND, MFD,..)
against the approach chart
The sequence of the various waypoints
The final angle of descent in the case of APV BaroVNAV, LPV

approaches, or if the (Baro) VNAV function is used.
The reasonableness of the tracks and distances of the segments, length

and route.
69
RNP APCH Normal Procedure

Monitoring of the FTE
The Lateral deviation must be limited to half the RNP
0.15Nm on the final approach segment,
0.5Nm on the intermediate segments.
The vertical deviation should be limited to 75 ft in the case of APV Baro

VNAV
Brief overshoots are tolerated, in particular during and just after turns.
70
RNP APCH abnormal procedures
Develop simple procedures in accordance with the RNAV system, alarms and
displays
to cover the cases for which the procedure must be discontinued
Loss of the function checking the position
integrity or position error alarm (e.g.: GPS
Primary loss, Unable RNP, RAIM loss/not
available, RAIM position error/alert, etc.)
Suspected database error.
Discrepancy between the two RNAV/GNSS
devices for an installation certified with two
systems.
Excessive FTE (excessive deviation on the
lateral deviation indicator)
excessive deviation observed on the vertical
deviation indicator
71
RNP APCH Contingency procedure
If the missed approach path is a RNAV procedure and

if the loss of RNAV guidance during the approach does not allow to follow
the
missed approach procedure provided for the considered runway.
=> a contingency procedure should be defined
This contingency procedure will consist in following a dead reckoning
path, allowing to reach a sufficient altitude and taking into account:
obstacles
aircraft performance
airspace restrictions
72
Example of a contingency procedure
Courtesy translated:
Approach RNAV (GNSS) Rwy 28
Missed approach following the loss of
RNAV/GNSS function
Extraction procedure :
- climb to 4000 ft, turn to heading 276.
- Contact ATC for instruction
73
RNP APCH - Navigation Database

CAT.IDE.A.355 (Electronic navigation data management) applies
Navigation data base integrity
Shall comply with ED 76/DO 200A methodology standard or an equivalent
approved procedure => LOA type 2 and type 1
Quality Monitoring
The operator should continue to monitor both the process and the products in
accordance with the quality system required by the applicable operational
regulations.
Data Distribution
The operator should implement procedures that ensure timely distribution and
insertion of current and unaltered electronic navigation data to all aircraft that
require it.
Feed back and reporting errors found
significant errors (i.e. those that would affect the flight path of the aircraft) should
be reported to the database supplier and the competent authority
Affected procedures should be prohibited by a company instruction or NOTAM.
74
RNP APCH reportable events

Any significant incidents experienced during RNP APCH procedures have
to be reported
a) Significant navigation errors attributed to incorrect data or a data base
coding error.
b) Unexpected deviations in lateral/vertical flight path not caused by pilot
input.
c) Significant misleading information without a failure warning.
d) Total loss or multiple navigation equipment failure.
e) Loss of integrity (e.g. RAIM) function whereas integrity was predicted to
be available during the preflight planning.
75
RNP APCH special procedures
RNP APCH procedures with particularities (e.g. deviations from the

international procedure design standards) => Define criteria
Analyse the particularities and any special requirements published in the

AIP.
It may require an operational evaluation of such procedure in VMC

conditions or in simulator (FFS : Full flight simulator)
to evaluate the controllability of the procedure and
detect any incompatibilities between the coding of the procedure and the
aircraft performance.
Development of an additional pilot training programme to take account of

those particularities
The operator should develop methods and tools to detect that kind of
complex procedures, and gives appropriate directive for the crew.
76
RNP APCH Flight crew qualification and training

Content of the training
Before performing RNAV(GNSS) approaches, the pilots must be familiar
with
the basic principles, limitations and special functions of the RNAV/GNSS
system.
with the operation and particularities of the RNAV/GNSS equipment
installed on the aircraft.
they should be aware of the operational procedures applicable to preflight planning and performance of these approaches.
The minimum training shall comprise a theoretical part and a practical

part.
Each shall be dispensed in accordance with a programme approved by
the authority.
77

The operator shall define the risks and threats linked to the type of procedure
(TEM, Threat and Error Management)
Barometric error
Effect of temperature
Identification and visualisation of the vertical profile
Situation of the aircraft in space (BaroVNAV profile vs ILS look alike profile)
Equipment deterioration
Change in approach type (LNAV, LNAV/VNAV, LPV)
Presentation of information
Navigation Database error
etc.
78

Academic Training
Characteristics , functionalities, limitations of the RNAV/GNSS equipment used,

including alarms and error messages.
Characteristics of RNP APCH approach procedures.
pre-flight planning (selection of aerodromes, NOTAMs, RAIM prediction).
Normal and contingency procedures, (including phraseology).
Manual or automatic holding pattern procedures.
Databases (characteristics, checks and use).
charts, identification of the approach procedure, representation and

characteristics of the various turning points,.
79
RNP APCH Flight Crew Qualification and Training
Crew must be familiar with the

Phraseology
80
Radar guidance limitations
Guidance leading to interception of the final axis less than 2NM

before the FAF should not be accepted.
Manual input of user WPt into the GNSS system by the pilot for
use in the terminal area is not authorised.
"Direct to" clearances to the IF can be accepted provided that the

resulting track change does not exceed 45
"Direct to" clearances to the FAF must not be accepted.

"Direct to" clearances to a waypoint which does not belong to the
procedure must not be accepted.
81

USE OF BARO VNAV ASSOCIATED RISKS,
PRECAUTIONS FOR USE
Importance of specific crew procedures
There are two possible situations for using the (Baro) VNAV
function:
Either to manage the vertical plane of non-precision

approaches (to help with CDFA)
to carry out an APV BaroVNAV (required function)
In both cases, the pilots must take the usual precautions

Altimetry setting
Temperature limitations
82

Altimeter setting.
Flight Crews should take precautions to switch altimeter settings at

appropriate times or locations
request a current altimeter setting if the reported setting may not be recent,
particularly at times when pressure is reported or is expected to be rapidly
decreasing. (for instance before FAF)
Remote altimeter setting is prohibited: A current altimeter setting for the

landing airport is required.
Consolidation of Baro-altitude performance during the approach
Two primary altimeter systems are necessary

Crew requirements for vertical guidance comparisons with regards to primary
altimeter information, altitude crosschecks (e.g. altimetry comparisons of 100
feet), temperature limitations and procedures for altimeter setting.
83

The pilots must know that the vertical flight path in Baro VNAV is influenced by
altimeter setting errors. These errors may not be detected by a cross-check
between the altimeter reading and the values given on the approach chart
(altitude distance verification).
300ft
300 ft
Display error of 10 HPa (e.g.: 996 HPa instead of

1006 HPa) glide slope offset 300 ft upwards: risk of
approach destabilisation on transition to visual
flight
QNH correct
(e.g. 1006 HPa)
Display error of 10 HPa (e.g. 1016 HPa
instead of 1006 HPa) glide slope offset
300 ft downwards: risk of CFIT
84

To strictly respect temperature limitation
When cold weather temperatures exist, the pilot should check the chart for the
instrument approach procedure to determine the limiting temperature for the
use of Baro-VNAV capability. If the airborne system contains a temperature
compensation capability, manufacturer instructions should be respected.
85
Effect of temperature
at ISA +15c, VPA =
3.2
at ISA, VPA =
3
at ISA - 30c, VPA =
2.6
Example of the effect of temperature on a BaroVNAV vertical profile for an aerodrome situated at
sea level. For a nominal slope (black line) of 3, the actual slope will be 2.6 for ISA -30 (red
line) and therefore closer to any obstacles, and will be 3.2 for ISA+15(blue line) and thus
steeper.
86

Certain charts can publish descent markers (step down fix - SDF)
to clear obstacles by procedure.
Pilot check that when
approaching 3.3 Nm
he is not below 1100ft
(applicable Only for
LNAV)
87

Practical training 1/2
Ground Practical training.
lasts a minimum of two (2) hours,
cover the utilisation of an RNAV/GNSS navigation system
comparable to that installed on the aircraft.

For the purposes of this training, the equipment used may be
presented or installed on a computer, a simulation bench, an FSTD
(flight simulation training device), or an aircraft on the ground.
88

Practical training 2/2
Practical training in-flight or on an FSTD
either on an aircraft of the same type as that used operationally;
or on a simulator, representative of the aircraft used operationally.

In both cases, the RNAV/GNSS equipment used shall be comparable
with that used operationally.
This training shall comprise at least four (4) RNAV(GNSS) approaches.

Two (2) of them with a discontinuation of the approach because of a
simulated failure (loss of RNAV capability or RAIM alarm for example),
followed by a missed approach.
89

Recurrent training - Additional requirements for public air transport pilots
The operator shall ensure that each pilot undergoes a check before conducting this
type of approach. This check can be replaced by satisfactory training on an FSTD
and/or in-flight.
RNAV(GNSS) approaches have to be included in the recurrent training and checking

programmes (required by section OPS 1.965 for CAT), with the same requirements
as those concerning conventional non-precision approaches.
The recurrent training and checking programme shall comprise theoretical refresher
training, experience feedback and a sufficient number of RNAV (GNSS) approaches

to ensure that the pilot's proficiency is currently satisfactory.
90

Attestation
The head of the organisation dispensing the training will certify complete
and satisfactory performance of the training by each pilot. The pilot may
have to present without undue delay, his attestation upon request by an
authorised representative of DGAC.
91

08 - RNP Apch

Uploaded by

Copyright:

Available Formats

08 - RNP Apch

Uploaded by

Document Information

Original Description:

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

08 - RNP Apch

Uploaded by

Copyright:

Available Formats

ICAO PBN Workshop

RNP APCH overview

RNP APCH introduction

RNP APCH overview

RNP APCH introduction

RNP APCH introduction

A RNP APCH approach covers three possible types of approach procedure:

Identified on the IAC chart by the minima line

APV BaroVNAV approach

Identified on the IAC chart by the minima line

APV SBAS approach

Identified on the IAC chart by the minima line

APV stands for Approach with vertical Guidance

RNP APCH introduction

Approaches with vertical

RNP APCH introduction

RNP APCH introduction

Main difference between General aviation aircraft and air transport

Single sensor versus multisensor

RNP APCH introduction

Vertical guidance is computed by certain RNAV systems: the vertical

RNP APCH introduction

RNP APCH introduction

RNP APCH overview

RNP APCH introduction

RNP APCH LNAV aircraft requirements

Lateral guidance is by means of the RNAV/GNSS system and is based on GNSS

Vertical flight management the same as for non-precision approaches

In accordance with EU OPS, non-precision approaches meeting CDFA criteria

For a non-precision RNAV(GNSS) / LNAV minima approach:

Charted RNAV(GNSS) or RNAV(GPS)

Non-precision approach (AMC 20-27)

RNP APCH LNAV aircraft requirements

20-27 and are consistent with the ICAO PBN manual

Flight plan construction builds from an embedded navigation data base

(VOR/DME, NDB, etc.),

RNP APCH LNAV aircraft requirements

RNP APCH LNAV aircraft requirements

Navigation system error (NSE)

RNP APCH LNAV aircraft requirements

Total loss of navigation must be remote at aircraft

Erroneous displayed information must be remote at

An On Board Performance monitoring and Alerting

RNP APCH LNAV aircraft requirements

Cross track error

Capability for the Direct To function (1)

RNP APCH LNAV aircraft requirements

Automatic leg sequencing and associated turn anticipation.

RNP APCH LNAV aircraft requirements

Autopilot and/or Flight Director coupling is

LNAV & CDFA

CDFA profile - No flight Level including at MDA

LNAV & CDFA

Minimun Descent Altitude

Distance altitude Table

LNAV & CDFA

CDFA is a flight technique and does not recommend any

the vertical path trajectory is checked using the distance - altitude