You are on page 1of 11

11/2/2017

Performance Based
Navigation

MALKEET SINGH
DGM (ATM-FPD)

2 November 2017 1

A method of navigation enabling


aircraft to fly on any desired flight
path:
◦ within the coverage of referenced NAVAIDS,
or
◦ within the limits of the capability of self-
contained systems, or
◦ a combination of these capabilities

2 November 2017 2

On-board performance monitoring and alerting is concerned with the


performance of the area navigation system.

 "on-board" explicitly means that the performance monitoring and


alerting is affected on board the aircraft and not elsewhere, e.g. using
a ground-based route adherence monitor or ATC surveillance. The
monitoring element of on-board performance monitoring and alerting
relates to flight technical error (FTE) and navigation system error (NSE).
Path definition error (PDE) is constrained through database integrity
and functional requirements on the defined path, and is considered
negligible.

 "monitoring" refers to the monitoring of the aircraft's performance as


regards its ability to determine positioning error and/or to follow the
desired path.

 "alerting" relates to the monitoring: if the aircraft's navigation system


does not perform well enough, this will be alerted to the air crew.

2 November 2017 3

1
11/2/2017

RNAV 2
2 Nautical Miles 95% of time
Track Centerline

2 Nautical Miles 95% of time

RNP 2 ALERT TO PILOT

2 Nautical Miles 95% of time


Track Centerline

2 Nautical Miles 95% of time

2 November 2017 4

On-board monitoring and alerting

In procedurally controlled airspace, separation


minima and route spacing on RNP specifications
are expected to provide a greater benefit than
those based on RNAV specifications.

This is because the on-board performance


monitoring and alerting function could alleviate
the absence of ATS surveillance service by
providing an alternative means of risk mitigation.

2 November 2017 5

Conventional RNAV RNP


Routes Narrow Obstacle
Clearance Areas
Waypoints
Current Ground Seamless
NAVAIDs Vertical
Path

“curved”
paths

Limited
Increased Airspace Optimized
Design
Efficiency Use of Airspace
Flexibility

2 November 2017 6

2
11/2/2017

-WAYPOINTS

-TURN TYPES

-LEG TYPES

2 November 2017 7

 A position defined by lat and long in WGS


coordinates.
 A waypoint may be a named point in space or
associated with existing NAVAIDs,
intersections or fixes.
 A waypoint is most often used to indicate a
change in direction, speed, or altitude along
the desired path.
 There are two types of waypoints: fly-over
and fly-by.

2 November 2017 8

2 November 2017 9

3
11/2/2017

 A change in direction at a fly-by waypoint


requires the navigation system to” anticipate"
the turn in order to intercept and fly the next
leg. The amount of distance of turn
anticipation (DTA), prior to the waypoint
depends primarily on the aircraft speed and
the angle of the turn.
 At a fly-over waypoint, the aircraft will not
turn to intercept the following leg until
passing over or abeam the waypoint. Aircraft
speed and angle of turn will influence the
resulting flight path.
 Fly-over waypoints are shown on charts
within a circle.
2 November 2017 10

FLY BY Turns

Fly-by turns are a key characteristic of an RNAV flight


path.

The RNAV system uses information on aircraft speed,


bank angle, wind and track angle change to calculate
a flight path turn that smoothly transitions from one
path segment to the next.

However, because the parameters affecting the turn


radius can vary from one plane to another, as well as
due to changing conditions in speed and wind, the
turn initiation point and turn area can vary.

2 November 2017 11

How an aircraft will fly an RNAV, STAR or SID


procedure depends upon the type of waypoints
and legs used in the procedure.

There are two types: fly-over and fly-by.

The fly-by waypoint is the most common and is


preferred for use in designing terminal RNAV
procedures.

2 November 2017 12

4
11/2/2017

 The path before, after or between


waypoints.
 Leg types are identified by a two-letter
code.
 First character describes the path (e.g.,
heading, course, track, etc.) and
 The second character specifies the end point
(e.g., the path ends at an altitude, distance,
fix, etc.).
 These coded leg types are used in the
aircraft navigation database, but are not
shown on the procedure chart.
2 November 2017 13

 Two categories of leg types exist


 Bounded leg types both begin and end at a
waypoint
 Unbounded leg types either begin or end at a
unspecified or conditional point (e.g., at an altitude)
rather than a waypoint
 23 possible leg types in the current ARINC
supplement, however only a small subset (5)
of these are required for use in RNAV arrival
and departure procedures.

2 November 2017 14

 Commercial database providers "code"


terminal RNAV procedures for use in aircraft
navigation systems.
 The accepted coding format was created by
Aeronautical Radio Incorporated (ARINC3) and
is known as the ARINC 424 Navigation
Database Specification.
 The specification describes over twenty
different "path terminators" known as leg
types. Leg types describe the path before,
after or between waypoints.

2 November 2017 15

5
11/2/2017

 A two-letter code describes the path (e.g.,


heading = V, course = C, track = T, etc.) and
it’s ending point (e.g., an altitude = A,
distance = D, fix = F, 4 etc.).

 Although not explicitly depicted on charts,


controllers and pilots can determine leg types
(and thus expected aircraft behavior) by
reading the chart narrative and viewing the
graphic depiction.

2 November 2017 16

 A "track" is a magnetic course between waypoints


that must be intercepted and flown. This is the
most common leg type and is coded as “TF."
 A "course" is a magnetic course to a waypoint
that must be intercepted and flown. A "CF" leg
differs from a "TF" only in that it does not have a
beginning waypoint.
 "Direct" describes a direct course from an
aircraft's position to a waypoint. A "DF" leg allows
an immediate turn to a waypoint without
requiring intercept of a particular course.

2 November 2017 17

 A "heading" is a magnetic heading to be flown.


Heading legs are subject to wind drift. A "VA"
leg is a heading to an altitude and a "VM" is a
heading to a "manual termination." The "VA" leg
is often used as the first leg of an RNAV
departure. The "VM" leg is most often used to
end an RNAV STAR on, for example, a
downwind leg heading.

2 November 2017 18

6
11/2/2017

IF leg type
 The Initial Fix or IF Leg defines a
database fix as a point in space

 It is only required to define the


beginning of a route or procedure

2 November 2017 19

TF leg type
 Track to a Fix or TF Leg defines a great
circle track over ground between two
known databases fixes
 Preferred method for specification of
straight legs (course or heading can be
mentioned on charts, but designer
should ensure TF leg is used for coding)

2 November 2017 20

Radius to Fix (RF) defines a


constant radius turn
between two waypoints

Constant Radius Arc or RF


Leg defines a constant
radius turn between two
database fixes, lines
tangent to the arc and a
center fix

*not all attributes are required for every


approach procedure
2 November 2017 21

7
11/2/2017

 Course to a Fix or CF Leg defines a specified


course to a specific database fix
 TF legs should be used instead of CF
whenever possible to avoid magnetic
variation issues

22

 Direct to a Fix or DF Leg defines an unspecified


track starting from an undefined position to a
specified fix
 Procedure designers should take into account the
FMS flight path depends on initial aircraft heading
as well

23

 Heading to an Altitude termination or VA Leg


defines a specified heading to a specific Altitude
termination at an unspecified position

24

8
11/2/2017

 Heading to a Manual termination or VM Leg


defines a specified heading until a Manual
termination

25

2 November 2017 26

2 November 2017 27

9
11/2/2017

 Differences in the databases along with


variations in aircraft performance may result
in slightly different tracks between RNAV
aircraft on the same procedure. This will be
most apparent during turns and where fly-
over waypoints are used.

 Tracking of a defined path by an RNAV


aircraft is as accurate as, or better than, that
of aircraft flying conventional routes.

2 November 2017 28

BEFORE AFTER
 Departures are  Departures fly RNAV
vectored tracks (not vectored)
◦ Headings, altitudes – Headings, altitudes and
and speeds issued by speeds are automated (via
controllers avionics)
◦ Large number of voice – Voice transmissions
transmissions required reduced by 30-50%
 Significant  Reduced Track
dispersion Dispersion
◦ Tracks are
– Tracks are more
inconsistent and
consistent and more
inefficient
efficient
 Limited exit points
 Additional exit points
available

2 November 2017 29

2 November 2017 30

10
11/2/2017

Arrival Holding
Fix

Arrival Holding
Fix

Arrival Holding
Fix

Arrival Holding
Fix

2 November 2017 31

Thank you

2 November 2017 32

11

You might also like