This document discusses instrument approach procedures using area navigation (RNAV) and performance-based navigation (PBN). It defines different types of instrument approach operations based on lateral and vertical navigation guidance. It describes various instrument approach procedure types including non-precision approach (NPA), approach procedure with vertical guidance (APV), and precision approach (PA). It also discusses the components, specifications, and applications of PBN concepts. Finally, it covers topics like navigation infrastructure, path terminators, satellite-based navigation, RNP approaches, temperature effects, altimeter settings, and phraseologies.

1. Implementation of RNP/PBN
Instrument Approach Procedure
Arvind Kumar Singh

2. Instrument Approach Operations
Instrument
approach
operations
2D
lateral Navigation
Guidance
3D
Lateral & Vertical
Navigation
Guidance
8/14/2022 2

3. Type DH Visibility(RVR)
Type A 75 m (250 ft)
Type B (CAT I) 60 m (200 ft) 800 M(550 M)
Type B (CAT II) <60 m (200 ft)
>30 m (100 ft)
not less than 300 m
Type B (CAT IIIA ) Lower than 30 m (100 ft) or
no DH
not less than 175 m
Type B (CAT IIIB ) lower than 15 m (50 ft) or
no DH
not less than 50 m
Type B (CAT IIIC ) no DH NO RVR
8/14/2022 3
Instrument Approach Operations

4. Instrument approach procedure (IAP)
 Non-precision approach (NPA) procedure
 Designed for 2D instrument approach operations Type A.
 E.g. VOR,NDB,LNAV
 Approach procedure with vertical guidance (APV)
 PBN instrument approach procedure designed for 3D instrument
approach operations Type A.
 E.g. LNAV/VNAV, LPV
 Precision approach (PA) procedure
 Based on navigation systems (ILS & SBAS CAT I) designed for 3D
instrument approach operations Type A or B.
8/14/2022 4

5. NAVIGATION
APPLICATION
NAVAID
INFRASTRUCTURE
NAVIGATION
SPECIFICATION
PBN Concept-Component
8/14/2022 5

6. 8/14/2022 6
Navigation Infrastructure
Ground-based Navigation Aids (NAVAIDs)
VOR, DME
Space-based Sensors
• GNSS
• GPS, GLONASS, Galileo, BEIDU (COMPASS)
 Augumentation
 SBAS
 GBAS
(Self contained NAVAIDs)
INS/IRS

7. 8/14/2022 7
Navigation Infrastructure
Navigation Specifications vs. Navigation Infrastructure

8. 8/14/2022 8
Navigation Specification

9. 8/14/2022 9
Navigation Application

10. RNAV Types of Turns
FLY- BY/FLY OVER SEGMENT
 Fly By (The most used)
 FMS on board is able to compute the anticipation of the turn.
10

11. 8/14/2022 11
Path Terminator
Path Terminators
 Transform procedures into coded flight path
 Set of two alphabetic characters that define the flight path along the leg,
and the terminator or end-point of the leg
 Instruct to navigate from a stating point to a specific point with
terminating condition

12. 8/14/2022 12
Path Terminator

13. Path Terminator Behavior

14. Satellite Based: GNSS
Receiver “Mode” is automatically selected for each flight phase:
 Enroute Mode 30NM from ARP or further
 Terminal Mode Within 30NM from ARP
 Approach Mode After 2NM prior to FAF (Final Approach Fix)
14

15. RNP APCH(LNAV IAP)
 Designated RNAV (GNSS) (From 1 Dec 2022, RNP)
 Only GNSS sensor used
 RNP navigation specification
 OPMA REQUIRED
 RNP1 (or RNAV1) for initial, intermediate and missed approach, RNP 0.3 for final
 No specific AUTHORIZATION REQUIRED unlike RNP AR
 Approach Classification Type A (minima ≥ 250)
 Lateral (2D RNP APCH, NPA)
 Identified as LNAV (Minima box), descend to MDA/H
8/14/2022 15

16. 8/14/2022 16
RNP Approach
Applicable navigation specification : RNP APCH
Area of Width (AW)
•½ AW = 1.5 XTT + buffer value (BV)
RNP APCH(LNAV IAP)

17. 8/14/2022 17
RNP APCH(LNAV IAP)

18. LNAV/VNAV, Baro VNAV
 GNSS (lateral guidance) + Barometric altimeter (vertical guidance)
 Cannot be used with remote altimeter setting
 Lateral and Vertical (3D RNP APCH, APV)
 DA/H, not MDA/H
 No FAF and MAPt
 The LNAV-only FAF and MAPt are used to define the areas but are not part
of the VNAV procedure.
 Vertical Path Angle defined from FAP to THR above 50ft
 Considers cold temperature correction during designing procedures
 Publishes a minimum promulgated temperature
 Must not be used below the promulgated minimum temp
8/14/2022 18

19. LNAV/VNAV (Baro VNAV)
Effect by Temperature
While trying to fly the published altitude on Intermediate Segment,
actual flight altitude is lower in cold days than in warm days since air
mass is compressed.
Procedure is designed considering:
 Obstacle is assessed assuming cold days.
 Lowest vertical path shall not be less than 2.5 deg even in cold days.
 Minimum temperature for which Baro-VNAV is authorized is
published.
8/14/2022 19

20. FINAL APPROACH SURFACE: FAS
20

21. 21
Temperature effect on final approach
profile

22. Temperature effect on final approach
profile
8/14/2022 22

23. Altimeter Setting Error
8/14/2022 23

24. 8/14/2022 24
Altimeter Setting Error

25. Protection Area LNAV,LNAV/VNAV
8/14/2022 25

26. LPV Procedure
Localizer Performance with Vertical guidance (LPV)
 Take advantage of the refined accuracy of Wide Area Augmentation
System (WAAS)(GAGAN)
 No effect of temperature
 Lateral and vertical guidance to provide an approach very similar to
a Category I Instrument Landing System (ILS).
 Like an ILS, an LPV has vertical guidance and is flown to a Decision
Altitude (DA).
 Identified as LNAV/VNAV or LPV (minima box), Descend to DA/H
8/14/2022 26

27. 8/14/2022 27
Protection Area LPV

28. GBAS azimuth reference point (GARP)
Flight path alignment point (FPAP)
8/14/2022 28

29. FAS Data Block
 Only for LPV approach
 FAS Data Block stands for Final Approach Segment Data Block and
contains the lateral and vertical parameters, which define the final
approach to be flown.
 LPV final approach segment will be promulgated using the FAS Data
Block process.
 This specific on board navigation database element defines the LPV
FAS and is called “FAS Data Block”.
 Each FAS Data Block ends with a Cyclic Redundancy Check (CRC),
which wraps around the approach data.
8/14/2022 29

30. Phraseologies
 Pilot/controller phraseology in case of vectoring followed by an RNP
final approach
 Pilot: ABC124, requesting RNP Approach Runway 19L
 ATC: ABC124 , Fly/turn L/R/ heading XXX, radar vectoring RNP [final]
Approach Runway 28.
 ATC: ABC124 , track direct LATEP, descend XXXX ft QNH 1015, cleared
RNP Approach Runway 28.
 To establish aircraft position:
 ABC124 , report established on final approach track
 ABC124, report 2 miles from final approach fix
 ABC124 , report passing final approach fix
8/14/2022 30

31. GNSS status information
 When aware of problems with the GNSS system, controllers will notify
the pilot specifying, where known, applicability in terms of type of
operation, location, geographical boundaries and times:
 ABC124, GNSS reported unreliable
 ABC124 , GNSS may not be available due to interference in the vicinity of
CCB until further notice
 When aware of problems with the GNSS system, the Pilot will notify-
 ABC124 , Unable RNP, Loss of RAIM, Request ILS Approach
 ABC124 , RAIM alert, going around
8/14/2022 31
Phraseologies

32.  Confirmation of PBN Approval
 Confirm (Navigation Specification) Approved
 To ascertain PBN approval status of an aircraft
 C: ABC124 Confirm RNAV1 (RNP1, RNP APCH, RNP AR, RNP2, etc.) approved
 P: Affirm RNAV1 (RNP1, RNP APCH, RNP AR, RNP2, etc.)
 P:Negative (Navigation Specification) [(ask alternative method of navigation)]
 C: RSO 123 Confirm RNAV1 (RNP1, RNP APCH, RNP AR, RNP2, etc.) approved
 P: Negative RNAV1 (RNP1, RNP APCH, RNP AR, RNP2, etc.). Request radar vector
(or name of conventional procedure)
8/14/2022 32
Phraseologies

33. 8/14/2022 33