AREA NAVIGATION

(RNAV)
Overview for Awareness
Presented by

ARIF MUMTAZ
PANS-OPS Instructor
PANS-OPS Initial 3, July 2011

SEQUENCE OF PRESENTATION

26 July 2011

Introduction to Area Navigation (RNAV)

RNAV Systems- Basic Functions
Required Navigation Performance (Concept Evolution)
Performance Based Navigation (PBN concept)
ICAO GNSS Concept
PBN Design Perspective

PANS-OPS Initial 3, July 2011

NAVIGATION IN CONTEXT
Determination of position and direction
on or above the surface of the earth

COMMUNICATION

AIR TRAFFIC
MANAGEMENT
SURVEILLANCE

CNS/ATM
26 July 2011

PANS-OPS Initial 3, July 2011

NAVIGATION - THE BEGINNING

I Follow Roads!

And Rivers
And Railroads
And Buildings
And Telephone Lines
And Whatever Else I Can See

26 July 2011

PANS-OPS Initial 3, July 2011

THE EARLY DAYS

1910s

First Bonfires and Beacons

Early 1920s
Lighted airport boundaries
Spot-lit windsocks
Rotating lighted beacons on towers
Lighted Airways
1923 Dayton to Columbus,
Ohio (USA) 72 km

26 July 2011

PANS-OPS Initial 3, July 2011

Late 1920s - 1930s

Radio for Two-Way

Communications

Weather Updates
Request Help With Navigation

Radio for Navigation

Radio Marker Beacons

4-Course Radio Range System

Pilots Listen for Navigation

Signals

26 July 2011

PANS-OPS Initial 3, July 2011

1930s - 1940s

Static-Free VHF Omnidirectional Radio Range

Pilots Navigate by
Instrument

VOR (with improvements)

becomes a primary NAVAID
for decades
Defines Routes
Supports Approach
Procedures

26 July 2011

VOR
Has Done a Great Job
For Decades
PANS-OPS Initial 3, July 2011

1940s - 1950s

1929: First system tested

1946: (Provisional) ICAO selects ILS as
primary landing air for international trunk
airports
Today ILS :
Cat I
Cat II
Cat III

ILS Still doing a Great

Job!
26 July 2011

PANS-OPS Initial 3, July 2011

From 1950s
1961: first regular civil use (pilot tuned)
RNAV DME use is based on automatic tuning

DME is
incorporated into
PBN
DME (on top of VOR)
26 July 2011

PANS-OPS Initial 3, July 2011

Radar

26 July 2011

PANS-OPS Initial 3, July 2011

Conventional Navigation

Ground-based navigation aids (NAVAIDs)

Aircraft Overfly NAVAID or Intersection

Display Accuracy is a Function of Distance

Protected Area Grows (Splayed)

= Limited Design Flexibility

26 July 2011

PANS-OPS Initial 3, July 2011

Radio Ranges
NDB
VOR
ILS
DME(Pilot tuned)

Evolution of RNAV
Long Range Navigation (LORAN)
Omega Radio Navigation System*
Inertial Navigation
VOR/DME and DME/DME
GPS/GLONASS and Augmentations
Galileo (Future)
Multi-sensor
Flight Management System (FMS)

* terminated in 1997
26 July 2011

PANS-OPS Initial 3, July 2011

Area Navigation

Ground or Space Based NAVAIDs

26 July 2011

Aircraft Fly Waypoints

Protected Area Constant (Linear)

= Increased Design Flexibility
PANS-OPS Initial 3, July 2011

AREA NAVIGATION (RNAV)

A METHOD OF NAVIGATION WHICH PERMITS
AIRCRAFT OPERTION ON ANY DESIRED FLIGHT
PATH WITHIN THE COVERAGE OF STATIONREFRENCED NAVIGATION AIDS OR WITHIN THE
LIMITS OF THE CAPABILITY OF SELF-CONTAINED
AIDS, OR A COMIBANATION OF THESE.
KEY
POINTS

STATION-REFRENCED
GROUND
BASED

26 July 2011

SPACE
BASED
PANS-OPS Initial 3, July 2011

14

WAYPOINT
A specified geographical location used to define an area
navigation route or the flight path of an aircraft employing
area navigation. Waypoints are identified as either:

Fly-by waypoint. A waypoint which

requires turn anticipation to allow
tangential interception of the next
segment of a route or procedure, or

Flyover waypoint. A waypoint at

which a turn is initiated in order to
join the next segment of a route or
procedure.

26 July 2011

PANS-OPS Initial 3, July 2011

15

WAYPOINT FLYBY/FLYOVER

26 July 2011

PANS-OPS Initial 3, July 2011

16

RNAV VOR/DME

Reference Navaid
VOR/DME

Nominal trajectory
WAY-POINT

26 July 2011

PANS-OPS Initial 3, July 2011

DME/DME POSITIONING
DME2

DME4

DME1

d1

DME3
26 July 2011

PANS-OPS Initial 3, July 2011

RNAV POSITIONING GNSS

Satellites range measurements allow users
to calculate a position:

26 July 2011

PANS-OPS Initial 3, July 2011

19

RNAV POSITIONING METHOD

26 July 2011

The RNAV system

identifies the next waypoint,

selects the most appropriate source of

navigation to determine its position

provides information to the auto-pilot to

fly to the next waypoint.

An RNAV route can be flown manually,

thanks to the flight director

PANS-OPS Initial 3, July 2011

20

RNAV POSITIONING METHOD

Next WP

Start of descent

Planned flight Path

Interception

26 July 2011

PANS-OPS Initial 3, July 2011

21

SEQUENCE OF PRESENTATION

Introduction to Area Navigation (RNAV)

RNAV Systems- Basic Functions
Required Navigation Performance (Concept Evolution)
Performance Based Navigation (PBN concept)
ICAO GNSS Concept
PBN Design Perspective

26 July 2011

PANS-OPS Initial 3, July 2011

22

RNAV SYSTEM
All RNAV systems are not the same.

Basic
26 July 2011

RNAV map
PANS-OPS Initial 3, July 2011

Simple Multi sensor

23

RNAV SYSTEM

Complex Multi-sensor Avionic

26 July 2011

PANS-OPS Initial 3, July 2011

24

RNAV SYSTEM

May also be connected with other systems, such as

auto throttle and autopilot/flight director, allowing more
automated
flight
operation
and
performance
management.

Differences in architecture and equipment, the basic

types of functions contained in the RNAV equipment
are common.

26 July 2011

PANS-OPS Initial 3, July 2011

25

RNAV SYSTEM
RNAV SYSTEM
VOR/DME

DME/DME

GNSS

INS/IRU

A/C POSITION
26 July 2011

PANS-OPS Initial 3, July 2011

26

RNAV SYSTEM BASIC FUNCTIONS

RNAV systems are designed to provide a given level of

accuracy, with repeatable and predictable path definition,
appropriate to the application.
The RNAV System typically integrates information from sensors
such as air data, inertial reference, radio navigation, satellite
navigation, together with inputs from internal data bases and
crew-entered data to perform the following functions:

26 July 2011

Navigation
Flight Plan Management
Guidance and Control
Display and System Control
PANS-OPS Initial 3, July 2011

27

RNAV SYSTEM BASIC FUNCTIONS

26 July 2011

PANS-OPS Initial 3, July 2011

28

RNAV AND RNP SPECIFIC FUNCTIONS

RF (Radius to Fix) Leg

Fixed Radius Transition

FIXED RADIUS PATHS

26 July 2011

PANS-OPS Initial 3, July 2011

29

RNAV AND RNP SPECIFIC FUNCTIONS

FLY-BY TURNS
26 July 2011

PANS-OPS Initial 3, July 2011

30

RNAV AND RNP SPECIFIC FUNCTIONS

OFFSET FLIGHT PATH

26 July 2011

PANS-OPS Initial 3, July 2011

31

SEQUENCE OF PRESENTATION

Introduction to Area Navigation (RNAV)

RNAV Systems- Basic Functions
Required Navigation Performance (Concept Evolution)
Performance Based Navigation (PBN concept)
ICAO GNSS Concept
PBN Design Perspective

26 July 2011

PANS-OPS Initial 3, July 2011

32

RNP CONCEPT(BACKGROUND-1980-90)
Special Committee on Future Air Navigation
System (FANS) identified need for performance
based navigation and developed Required
Navigation Performance Capability (RNPC).

RNPC: A parameter describing lateral deviations

from assigned or selected track as well as along
track position fixing accuracy on the basis of an
appropriate level.

26 July 2011

PANS-OPS Initial 3, July 2011

RNP CONCEPT(BACKGROUND-1980-90)
Later RGSCP review the concept as RNP
RNP (Doc9613) : A statement of the navigation
performance accuracy necessary for the operation within a
defined airspace.
Standard RNP values of 20, 12.6, 10, 4 and 1 were
adopted through ICAO Required Navigation Performance
Manual (Doc9613).

26 July 2011

PANS-OPS Initial 3, July 2011

34

RNP CONCEPT(BACKGROUND-1995)
Though there was awareness that RNP operations cannot
be conducted without an RNAV system, there was no
correlation/ interrelation between RNAV and RNP.
RNP (Doc9650) : A statement of navigation performance
accuracy, integrity, continuity and availability necessary for
operation in a defined airspace.

(Report of the Special Communications/Operations Divisional Meeting SP COM/OPS/95)

26 July 2011

PANS-OPS Initial 3, July 2011

35

RNP CONCEPT(PROBLEMS)

Addressed only the en-route phase of flight for oceanic

and remote applications.

No ICAO RNAV/RNP requirements for continental

Enroute and Terminal applications.

This Led to:

26 July 2011

Proliferation of national standards

Wide variety of functional requirements
Variety of required navigation sensors
Differing air crew requirements
Lack of global harmonization
PANS-OPS Initial 3, July 2011

36

Why Action was Required ?

Russia

B-RNAV

2
0
0
3

US
Europe

P-RNAV
US-RNAV
RNP10

Boeing
Australia

RNAV
and
RNP

China
Airbus

RNP 4

Canada

RNP/RNAV

Japan

RNP 0.3

South America
India

Development of global navigation applications without intervention

26 July 2011

PANS-OPS Initial 3, July 2011

RNAV/RNP ? COMPLEX WORLD

PRNAV

RNP 4

IRU

LNAV/VNAV

RNAV TYPE A
GPS

BRNAV

RNAV TYPE B

RNP 0.3
RNP-RNAV

RNP 10

INS

RNP 5

DME-DME

26 July 2011

RNAV 2

VOR/DME

PANS-OPS Initial 3, July 2011

RNAV 1

38

Evolution of RNP

RTCA/EUROCAE: Defined performance and functional

requirements

26 July 2011

RTCA DO 236/EUROCAE ED-75 Minimum Aviation System

Performance Standards: Required Navigation Performance for Area
Navigation (2003)
RNP: A Statement of the navigation performance accuracy
necessary for operation within a defined airspace
RNP RNAV: An area navigation capability that meets all of the
requirements of this document
RNP Type: RNP Types are established according to navigational
performance accuracy in the lateral plane
RNP (x) RNAV: A designator used to indicate the minimum
navigation system requirements needed to operate in an area,
on a route or a procedure

Manufacturers: Delivered RNP based on different versions

of requirements
PANS-OPS Initial 3, July 2011

RNAV/RNP ADJUSTMENT REQUIRED

Earlier concept of RNP included the requirement of
accuracy only. Requirements of functional integrity,
continuity and availability was to be included.
Harmonization of current RNAV and RNP operations.
Development of new navigation specifications to meet
operational demands.
Clear distinction between operations that require
performance monitoring and alerting and operations
that dont require performance monitoring and alerting.

26 July 2011

PANS-OPS Initial 3, July 2011

40

The Problem Addressed at ICAO

Need for focal point in ICAO to address

problems experienced with RNP Concept
GNSSP/4

recommendation 1/1
11th Air Navigation Conference

Individual Air Navigation Commission Panels

not suitable to address the problem
ANC (163/9) approved establishment of
Required Navigation Performance Special
Operations Requirements Study Group
(RNPSORSG) as coordinating group
ICAO

26 July 2011

RNP Study Group

PANS-OPS Initial 3, July 2011

AVIATION CHALLENGES

Growing demand for RNAV approaches

(safety, accessibility)
Growing demand for solutions to airspace congestion
Growing fuel efficiency requirements
Growing Environmental requirements
Most can be met with current technology, but standardization,
harmonization and operational requirements have to be put into
place.

JulyJuly
26
26,2011
2011

PANS-OPS Initial 3, July 2011

42

SEQUENCE OF PRESENTATION

Introduction to Area Navigation (RNAV)

RNAV Systems- Basic Functions
Required Navigation Performance (Concept Evolution)
Performance Based Navigation (PBN concept)
ICAO GNSS Concept
PBN Design Perspective

26 July 2011

PANS-OPS Initial 3, July 2011

43

PERFORMANCE BASED NAVIGATION

These adjustment resulted in development

of new concept of Performance Based
Navigation (PBN).

All future RNAV applications to be

developed in accordance with PBN criteria.

The concept of PBN relies on the use of an

Area Navigation System.

26 July 2011

PANS-OPS Initial 3, July 2011

44

PERFORMANCE BASED NAVIGATION

PBN is a method for defining equipage

requirements by specifying
the Performance
Requirements of an aircraft instead of mandatory
carriage of an equipment.

The PBN concept represents a shift from sensorbased to Performance Based Navigation.

JulyJuly
26
26,2011
2011

PANS-OPS Initial 3, July 2011

45

PERFORMANCE BASED NAVIGATION

26 July 2011

PANS-OPS Initial 3, July 2011

46

RNAV & RNP in PBN

RNAV Future applications of Performance
Based Navigation (PBN) without the requirement
of on-board performance monitoring and
alerting.

RNP Future applications of Performance Based

Navigation (PBN) with the requirement of onboard performance monitoring and alerting

26 July 2011

PANS-OPS Initial 3, July 2011

47

RNAV Application
(Notional)

RNAV 1
Track Centerline

RNP Application
(Notional)

RNP 1

1NM 95% of
Flight Time

Track Centerline

1NM 95% of
Flight Time

1NM 95% of
Flight Time
1NM 95% of
Flight Time

ALERT TO PILOT
THE KEY DIFFERENCE
ON BOARD PERFORMANCE MONITORING AND ALERTING

26 July 2011

PANS-OPS Initial 3, July 2011

48

Air Navigation Services

PBN COMPONENTS
3
NAVIGATION
APPLICATION

2
NAVIGATION
SPECIFICATION

26 July 2011

1
NAVAID
INFRASTRUCTURE

PANS-OPS Initial 3, July 2011

PBN COMPONENT - 1
NAVAID
INFRASTRUCTURE

Ground-based Navigation Aids (Navaids)

VOR; DME; (Not NDB)

Space-based Navaids GNSS

GPS; GLONASS; future GALILEO
Self Contained ?

26 July 2011

PANS-OPS Initial 3, July 2011

PBN COMPONENT - 2

Previous RNP
concept

NAVIGATION
SPECIFICATION

RNAV

26 July 2011

PANS-OPS Initial 3, July 2011

RNP

PBN COMPONENT - 2

26 July 2011

PANS-OPS Initial 3, July 2011

INHERITANT INCONSISTENCY
Existing

designation of RNP10 is basically RNAV10 as it does

not require on-board performance monitoring and alerting.

Recognizing

the extent of existing airspace designations and

operational approvals using the designation RNP10, the
designation of the airworthiness and operational approval as
well as airspace/route designation remains RNP 10 in order to
grandfather the present publications and extensive approvals.

New

airspace designations and aircraft approvals will also

continue to use the RNP 10 term while the required PBN
application will be now known as RNAV 10.

26 July 2011

PANS-OPS Initial 3, July 2011

PBN COMPONENT - 3

NAVIGATION
APPLICATION

26 July 2011

PANS-OPS Initial 3, July 2011

AIRSPACE CONCEPT
WHAT DO WE WANT TO ACHIEVE?

26 July 2011

PANS-OPS Initial 3, July 2011

Air Navigation Services

AIRSPACE CONCEPT DEVELOPMENT

It requires the combined efforts of

Air Navigation Service Providers (Air Traffic)

Regulators (Flight Standards/Airworthiness etc)

PANS-OPS specialists (Procedure Designers)

System Users (operators)

26 July 2011

PANS-OPS Initial 3, July 2011

STAKE HOLDERS

to:

AIRSPACE CONCEPT DEVELOPMENT

1. To Identify Strategic Objectives
Safety ?

Capacity ?

Efficiency ?

Environment ?

Access ?

2. To prioritize Strategic Objectives

Safety ?

Capacity ?

Efficiency ?

Environment ?

Access ?

3. To address Airspace Enablers

Communication

26 July 2011

Navigation

Surveillance

PANS-OPS Initial 3, July 2011

Air Traffic Management

ADVANTAGES OF PBN

Reduces need to maintain sensor-specific routes and

procedures, and their associated costs.
Avoids need for development of sensor-specific
operations with each new evolution of navigation
systems, which would be cost-prohibitive.
Allows more efficient use of airspace (route
placement, fuel efficiency, noise abatement).
Clarifies the way in which RNAV systems are used.
Facilitates the operational approval process for
operators by providing a limited set of navigation
specifications intended for global use.

26 July 2011

PANS-OPS Initial 3, July 2011

PBN COMPONENT
APAC Navigation Strategy

RNAV 5
Enroute
Continental

RNAV 10
Enroute
Oceanic
26 July 2011

RNAV 1/2
Terminal

RNP 4
Enroute

PANS-OPS Initial 3, July 2011

RNP 1
Terminal

RNP
APCH

APAC Navigation Strategy

transit to PBN operations as follows :

RNP10/RNP4 for Oceanic and Remote Continental routes;
RNAV5/RNAV2 for Continental En-route;
RNAV1, RNAV2 and Basic RNP1 based arrivals and departure;
APV (Baro-VNAV, RNP AR and APV I/II);
Precision approaches at selected runways.
with respective end states as follows:
RNP4 for Oceanic and Remote Continental routes;
RNP1/RNP2 for Continental En-route;
RNP1 and RNP0.3 based arrivals and departure;
APV (Baro-VNAV, RNP AR and APV I/II);
Precision approaches at selected runways.

26 July 2011

PANS-OPS Initial 3, July 2011

SEQUENCE OF PRESENTATION

Introduction to Area Navigation (RNAV)

RNAV Systems- Basic Functions
Required Navigation Performance (Concept Evolution)
Performance Based Navigation (PBN concept)
ICAO GNSS Concept
PBN Design Perspective

26 July 2011

PANS-OPS Initial 3, July 2011

61

GNSS FUNDAMENTALS
Satellites range measurements allow users
to calculate a position:

26 July 2011

PANS-OPS Initial 3, July 2011

62

GNSS FUNDAMENTALS

Two core satellite constellations

GPS (USA) and GLONASS (Russia)
Galileo (EU-FUTURE)
Each satellite sends permanently a navigation
message (Ephemeris) which contains
Identification
Position
Time
Others

26 July 2011

PANS-OPS Initial 3, July 2011

63

2 points given by the

intersection of the three
LOPs

SVk : xk, yk,

zk

SVi : xi, yi, zi

SVj : xj, yj, zj

GPS receiver
location
PANS-OPS Initial 3, July 2011

GNSS FUNDAMENTALS

Satellites range measurements allow users to

calculate a position.
User clock is not precise enough: pseudo ranges,
including clock error, are measured.
Pseudo-range measurements may be affected by
satellites geometry and different type of errors:
Atmospheric propagation
Ephemeris and clock errors
Satellite failures

26 July 2011

PANS-OPS Initial 3, July 2011

65

Dilution of Precision
Number of satellites in view
Geometry

PRECISION

Satellite Outage

26 July 2011

PANS-OPS Initial 3, July 2011

66

Dilution of Precision

Does the position

meet the
requirement to be
used for navigation

26 July 2011

PANS-OPS Initial 3, July 2011

67

Integrity Monitoring Alarm Limit

ACCURACY
OF
POSITION

POSITION
TO BE USED

INTEGRITY
POSITION
NOT TO BE
USED

IMAL VALUE

Integrity is a measure of the trust which can be placed

in the correctness of the information supplied by the
total system. Integrity includes the ability of the system
to tell the user when the system must not be used for
the intended operation (or phase of flight).
26 July 2011

PANS-OPS Initial 3, July 2011

68

AUGMENTATION

To meet the operational performance requirements for all

phases of flight, both GPS and GLONASS require
varying degrees of augmentation.

Three systems, ABAS, SBAS and GBAS, overcome

inherent limitations in GPS and GLONASS.
Aircraft Based Augmentation System (ABAS)
Satellite Based Augmentation System (SBAS)
Ground Based Augmentation System (GBAS)

26 July 2011

PANS-OPS Initial 3, July 2011

69

Global Navigation Satellite System (GNSS)

The total system including core satellite

constellations and all augmentation
systems is referred as Global Navigation

Satellite System (GNSS).

26 July 2011

PANS-OPS Initial 3, July 2011

70

ICAO GNSS CONCEPT

EGNOS
SATELLITE
BASED
(SBAS)

AUGMENTATION

WAAS
GEOSTATIONARY
MTSAS

GAGAN

GROUND
BASED
(GBAS)

R.A.I.M
ON BOARD
(ABAS)
A.A.I.M

26 July 2011

PANS-OPS Initial 3, July 2011

71

GNSS MODE
Terminal

ROUTE

en route

Terminal

descent

Approach

holding

climbing
approac
h

initial

taking off
landing
taxiing
airport A

airport B

IMAL is coupled with GNSS mode

26 July 2011

PANS-OPS Initial 3, July 2011

SEQUENCE OF PRESENTATION

Introduction to Area Navigation (RNAV)

RNAV Systems- Basic Functions
Required Navigation Performance (Concept Evolution)
Performance Based Navigation (PBN concept)
ICAO GNSS Concept
PBN Design Perspective

26 July 2011

PANS-OPS Initial 3, July 2011

73

RNAV PBN OPERATIONS

EN-ROUTE

TERMINAL

AIRWAYS

SID/STAR

APPROACH

NPA
Approach procedure with vertical guidance (APV).
An instrument procedure which utilizes lateral
and vertical guidance but does not meet the
requirements established for precision approach
and landing operations.

26 July 2011

APV

BaroVNAV

PANS-OPS Initial 3, July 2011

PA

APVI

CAT I

APVII

CAT II

APV - VERTICAL GUIDANCE?

SBAS

APV
Altimeter

Baro-VNAV

26 July 2011

Baro-VNAV system does not accomodate the

effect of altimeter source temperatures on VPA
PANS-OPS Initial 3, July 2011

75

GLS - VERTICAL GUIDANCE?

GBAS

GLS

26 July 2011

PANS-OPS Initial 3, July 2011

76

ICAO APAC PBN Implementation Targets

Short Term (upto 2012)

RNP APCH (with Baro-VNAV) in 50% of instrument runways

by 2012 and priority should be given to airports with

operational benefits.
RNAV 1 SID/STAR for 75% of international airports by 2012

and priority should be given to airports with RNP Approach.

Re-defining existing RNAV/RNP routes into PBN navigation

specification by 2012
Implementation of additional RNAV/RNP routes

26 July 2011

PANS-OPS Initial 3, July 2011

ICAO APAC PBN Implementation Targets

Medium term (2013-2016)

Implementation of additional RNAV/RNP routes

RNP APCH with Baro-VNAV or APV in 100% of instrument

runways by 2016
RNAV 1/RNP 1 SID/STAR for 100% of international airports

by 2016
RNAV 1/RNP 1 SID/STAR for 70% of busy domestic airports

where there are operational benefits

26 July 2011

PANS-OPS Initial 3, July 2011

RNAV PBN IMPLEMENTATION

Where are we ?

26 July 2011

PANS-OPS Initial 3, July 2011

79

Questions ?

26 July 2011

PANS-OPS Initial 3, July 2011