12ChartingPBN V1 - 2

Beijing Dec 2007 - Performance Based Navigation Course
COSCAP-North Asia
CHARTING
1
No communication, reproduction or use, without prior approval from ENAC
REGULATORY REFERENCE
Annex 4
Annex 11
Doc 8168-OPS/611
2
COSCAP-NA - Beijing Dec 2007 - PBN Course
OBJECTIVES
Know the naming convention of the waypoints

Know the method to identify the procedure
Know how and where to express additional
requirements for
– Sensor
– Functionalities
– Specific operation
– Specific system
Know how to chart Altitude constraint
Know how and where to provide coding
information
3
CHARTING
Depiction of
Depiction of all
all necessary
necessary
information
information
Clearly
Clearly
According to
According to users’
users’
needs
needs
4
Pilots
ATC
AIS
Coding Cie
Charting Cie
5
INFORMATION TRIP
• Coding CIE
AIS
FMS manufacters
6
GENERAL CONCEPTS (1)
All waypoints have

– ONE identification,
– UNIQUE coordinates published in WGS 84
Convention for procedure identification
– ONE identification per “ Final + Missed APProach” ,
SID , STAR
Publication of PROCEDURE ALTITUDES and
sometimes minimum altitudes for obstacles
clearance ( MOCA)
7
GENERAL CONCEPTS (2)
Description in a PLAN view

– SID , STAR, IAC
Description in a PROFILE view
– IAC
TEXTUAL description
– Missed approach, SID and STAR
Tabular description for CODING information
– SID, STAR, IAC
Minimum Boxes
– IAC
8
Charting Resolution
Waypoint expressed in WGS84 to the

1/10 of second except for threshold (1/100
of sec)
Track in magnetic degree and to the 1/10
of degree for coding purpose
Distance expressed in 1/10 of NM
Vertical path angle expressed in 1/10 of
degree for publication and 1/100 of
degree for coding purpose
9
COSCAP-North Asia
WAYPOINT NAMING CONVENTION
10
WAYPOINT NAMING
CONVENTION
Format:
– AAXNN
– 5 alphanumeric characters
Exception
– Navaid
– 5LNC
– Threshold : RWNNA ( RW36L)
11
ICAO NAMING CONVENTION
PART III SECTION 5 CHAPTER 1 § 1.5
Five - letter UNIQUE ICAO name code

(5LNC)
– En-route
– final waypoint of a SID
– first waypoint of a STAR
– waypoints shared by more than one TMA or
aerodromes
– waypoints used by ATC for communication or
for activation functions for specific tools
• called « STRATEGIC TERMINAL WAYPOINTS »
12
OTHER WAYPOINTS
The convention and rules of application are to be

published in AIP
Alphanumeric name code convention
– at least 2 characters from the airport designator
– 3 numbers between [361;999] as maximum
– avoid number ending by 5 or 0
– restrict number allocation to [ 361,999]
Are UNIQUE within an airport but NOT globally
– Should be listed as Terminal waypoint in AIP
No re-routing from EN ROUTE and STAR to an
alphanumeric named waypoint by ATC
13
MIQUELON
•Fix acronymes : IAF, IF, FAF, MAPt, MAHF
•Waypoint naming :Format AAXXN

AA : last two CHRs of aerodrome designator
X X : numeric code [01..36] for rwy identification

N : numeric code [0..9]
•Distance to THR
14
COSCAP-North Asia
COORDINATES CALCULATION METHOD

DOC 9368 ATTACHMENT C3
15
COORDINATE CALCULATION
The waypoints located on the extended runway

centre line are calculated using the reciprocal
landing true bearing, the landing threshold
coordinates and distance from the threshold.
e bearing reciprocal
Runway tru
a y 2 7 tr ue bearing 091.09°T
Runw
271.09°T
runway al s egm e nt
fin
16
For the waypoints offset from the runway centre

line, calculate the coordinate using the
coordinate of the intersection, the true bearing
and distance from the intersection.
17
The waypoints located on the extended runway

centre line are calculating using the runway true
bearing and distance from the threshold.
RWY 31
True bearing
Turning WP
RWY 13
True bearing
18
COSCAP-North Asia
NAMING CONVENTION FOR

PROCEDURE
Vol II Part I Section 4 chapter 9
19
NAMING CONVENTION :
OBJECTIVE
To avoid ambiguity between chart,

electronic display and ATC clearance
Standardization of
– Procedure identification
– Additional equipements
– Minimum boxes
20
PROCEDURE IDENTIFICATION:
GENERAL REQUIREMENTS
Title of NPA procedure will be the same as LAST

navaid TYPE providing final approach LATERAL
guidance.
Title of PA will be identified by the SYSTEM name
– Eg ILS RWY 08
Title of RNAV procedure contains word “RNAV”
ADDITIONAL requirement will be specified in the
PLAN VIEW or in NOTES but not in the title
21
SOME PROCEDURE NOTES
Displayed as a procedure note to indicate equipment
requirement for execution of procedure
 “GNSS required “ or “GNSS or DMEDME /IRU” required
 “ RNAV 1 operation”
 Reference VORDME “xxx”
 Critical navaid for DME sensor “xxx”
 RF required
 Dual VHF communications required
Caution: Simultaneous 22
 COSCAP-NA close parallel
- Beijing Dec operations
2007 - PBN Course
TITLE OF PROCEDURE
WHAT’S NEW ( regarding amendment 1) ?

RNAV or RNP procedure are charted with
RNAV in the TITLE
Type of PBN Application is added as note
in the plan view
• e.g. : RNP1 or RNAV2….
Where necessary, type of SENSOR
required are specified in a NOTE in the
PLAN VIEW, NOT in parenthesis in the
TITLE
23
TITLE OF RNAV SID STAR
Chart identification should include

– an identifier (ref to annex 4 § 9.5 or 10.5 ) with reference to
RWY or Fix or navaid
– and RNAV
Route designator
– In accordance with annex 11 appendix 3
– UNIQUE
– the first 4 letters of any 5LNC used in the route designator
is unique for the aerodrome
• If BALBEL is used BABET cannot be used on the same
airport
• When the route DESIGNATOR is LONGER than 6 characters,
the FIFTH one is NOT CODED in the data base
24
TITLE OF RNAV SID STAR
Basic indicator BATEL
+
SID STAR
ROUTE Validity indicator 2
DESIGNATOR
+
Route indicator (optional) A
25
BASIC INDICATOR
Significant point name

– Ending point for departure
– Starting point for arrival
Or name code
26
VALIDITY INDICATOR
Number from 1 to 9
27
Route indicator
Optional
1 letter except « I » or « O »
28
Departure Name of city
+ RNAV + airport
RWY
For data base constraint can be shortened
to ATRE 1H
Route
designator
RNAV1 application
29
TITLE OF APPROACH
PROCEDURE
For all RNP APCH procedure ( NPA and

APV)
– Tittle is RNAV (GNSS)
– Ref part III section 5 §1.4.2.2
For RNP AR procedure
– Title is RNAV (RNP)
– Ref manual AR chapter 5 §3
30
DUPLICATE PROCEDURE
IDENTIFICATION
To avoid ambiguity add a suffix letter

starting with « Z » after the identification
of the procedure when
– Same name
– On same RWY
– Regardless the sensor type
Example of title on a same airport
RNAV (GNSS) z RWY29 - for first RNAV (GNSS) approach and a second RNAV
(GNSS ) approach to the same runway exists.
RNAV (GNSS) y RWY 29 - for second RNAV (GNSS) approach to the same runway
RNAV (GNSS) RWY 11 : no suffix letter as only one VOR approach exists on the
RWY 11
31
WHERE AND HOW TO INDICATE
THE TYPE OF APPROACH ?
The information in the MINIMUM BOXES

enable to disinguish them apart.
– NPA procedure LNAV
– BaroVNAV procedure LNAV/ VNAV
– APV procedure LPV
32
BAROVNAV PROCEDURE
LNAV/VNAV in minimum boxes
OCA/OCH CATA CATB CATC CATD

LNAV 490 (450) 490 (450)) 490 (450) 490 (450)
LNAV/VNAV 290 (250) 290 (250) 290 (250) 290 (250)
For baro-VNAV procedure publication of

– minimal temperature
– RDH
– VPA
x.x° for charting and x.xx° for coding
33
APV SBAS procedure
• LPV in the minimum boxes
OCA/OCH CATA CATB CATC CATD

LNAV 490 (450) 490 (450)) 490 (450) 490 (450)
LPV 250 (210) 250 (210) 250 (210) 250 (210)
34
PUBLICATION
RNAV ( GNSS)
WAAS Channel
Number
Miminum temperature
SBAS Minimum Line
baroVNAV Minimum Line
NPA Minimum Line

35
COSCAP-North Asia
PROCEDURE ALTITUDE CONCEPT
36
NEED OF DEPICTION OF DIFFERENT
TYPES OF ALTITUDE
Minimum altitudes include provision for

obstacle clearance but also for different
items, such as :
– controlled airspace
– radionavigation
– communication
Need to define two types of altitudes
– MOCA : Minimum Obstacle Clearance Altitude
– Procedure altitude
37
TYPES OF ALTITUDE
• What does mean minimum altitude?
Always
 Respect MOC
Sometimes
 Respect Airspace constraint
 Respect Radionavigation constraint
 Respect Environmental constraint
 Advoid CFIT(stabilized approach)
♥ Need to define two types of altitudes
– MOCA: Minimum Obstacle Clearance Altitude
– Procedure altitude 38
TYPES OF ALTITUDE
Operational Altitude
PROCEDURE ALTITUDE
USERS
Minimum Obstacle Clearance Altitude

MOCA
Procedure altitude
COSCAP-NA are
- Beijing Dec 2007ALWAYS
- PBN Course ≥ MOCA 39
PROCEDURE ALTITUDE
DEFINITION
From Vol II Part I Section 4 chap1

Procedure altitude/height.
– A specified altitude/height flown operationally
at or above the minimum altitude/height and
established to accommodate a stabilized
descent at a prescribed descent gradient/angle
in the intermediate/final approach segment.
40
APPLICABLE TO WHICH PHASE OF
FLIGHT
To support CFIT prevention initiative,

procedure altitude should be defined for
all NPA ( ref part III § 1.7.1)
Arrival and departure procedure altitudes

are developed to separate arriving and
departing traffic( ref part III § 3.3.1 and
part II § 2.8.1)
41
DEPICTION OF PROCEDURE ALTITUDE
FOR SID AND STAR
At or below : altitude
At or above : altitude
At : altitude
At or above to at or below :
altitude1
altitude2
Recommended altitude : altitude

Expected altitude : Expect altitude
42
DEPICTION OF PROCEDURE ALTITUDE
FOR SID AND STAR
MATTI
FL070
A/C are AT OR ABOVE

FL 070 at MATTI
43
DEPICTION OF PROCEDURE
ALTITUDE / MOCA IN NPA
APPROACH CHART
Procedure altitude is provided in the profile view

(ref § 11.10.6.3 annex 4)
Minimum altitude (MOCA) or a ground profile is

RECOMMENDED to be depicted (ref § 11.10.6.5
annex 4)
MOCA along intermediate and final segments are

depicted with SHADED BLOCKS
44
PROCEDURE ALTITUDE / MOCA
Procedure Altitude
“Procedure Altitudes”
2,000’ not in database

Shaded block
45
COSCAP-North Asia
CODING INFORMATION
46
PUBLICATION FOR CODING
PURPOSE
Ref Part III section 4 chapter 1

Description of the procedure
– Formal description
– Abbreviated description
– Tabular description
47
FORMAL description
• (Waypoint) (underlined) denotes 'fly-over'.
• (Waypoint) (not underlined) denotes 'fly-by' or RF waypoint
as appropriate.
• To (Waypoint) denotes a TF path terminator.
• To (Waypoint) on course XXX° denotes a CF path terminator.
• Direct to (Waypoint) denotes a DF path terminator.
• (Waypoint) {R, NN.N, LatLong} denotes an RF path
terminator, the radius and the centre point of a fixed radius
turn in terminal airspace.
• Climb on track XXX°, at or above yyy feet turn right/left
denotes an FA path terminator.
• From (Waypoint) to XXXX feet on track XXX° denotes an FA
path terminator.
48
ILLUSTRATION OF FORMAL AND
ABBREVIATED DESCRIPTION METHODS
Formal Description Abbreviated Expected Path Fly-over

Description Terminator Required
Climb on track M047, A800+, FA or CA N

047°M, at or above R
800 ft turn right.
49
TABULAR DESCRIPTION
Enable description of the procedure to

propose a « coding solution according to
ARINC 424 »
Waypoint description
Altitude description
Course description
50
TABULAR DESCRIPTION
Departure
Designator Path WP WP Course Turn altitude Speed Required VPA
terminator name Descr dir Navaid
TARAH1A FA RW20 - - R 400 205
DF FOKSI - - 250
TF PF213 Y - +5000 250
CF TARTO 256.3 250 OKE
Approach
Designator Path WP WP Course Tur altitude Speed Requir VPA
terminator name Descr n dir ed
Navaid
RNAV IF SUSER - - +5000 230
RWY35L
TF CV403 - -
TF CV404 - 2500 -3.00/50
TF RW35L Y
FA RW35L L @700 210
DF SUSER
51
RWY and initial turn direction SID RNAV (GNSS or DMEDME)
General instructions in AIP
Sequencing description in AIP
Underline=Fly-over
Coding instructions in
AIP cf Eurocontrol document
Publication of WP co-ordinates in AIP
52
COSCAP-North Asia
END
53
Description of altitude (cf ARINC424)
At or above : + altitude
At or below : - altitude
At : @
At or above to at or below :
– B altitude1 altitude2
For a step down fix in final
– at or above : V
54
Few extracts from ARINC 424
For CF path terminator

– Course and identification of a required VOR to use the
associated magnetic variation
Add « T » when expressed relative to true north
The first PT of a STAR or NPA is called « IF »
For CA or FA
– Express the altitude
– designation of a VOR to use the associated declination
55

12ChartingPBN V1 - 2

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

12ChartingPBN V1 - 2

Uploaded by

Copyright:

Available Formats

Beijing Dec 2007 - Performance Based Navigation Course

Know the naming convention of the waypoints

All waypoints have

Description in a PLAN view

Waypoint expressed in WGS84 to the

WAYPOINT NAMING CONVENTION

Five - letter UNIQUE ICAO name code

The convention and rules of application are to be

•Fix acronymes : IAF, IF, FAF, MAPt, MAHF

•Waypoint naming :Format AAXXN

X X : numeric code [01..36] for rwy identification

COORDINATES CALCULATION METHOD

The waypoints located on the extended runway

For the waypoints offset from the runway centre

The waypoints located on the extended runway

NAMING CONVENTION FOR

Vol II Part I Section 4 chapter 9

To avoid ambiguity between chart,

Title of NPA procedure will be the same as LAST

 “GNSS required “ or “GNSS or DMEDME /IRU” required

 Reference VORDME “xxx”

 Critical navaid for DME sensor “xxx”

 Dual VHF communications required

WHAT’S NEW ( regarding amendment 1) ?

Chart identification should include

Basic indicator BATEL

Route indicator (optional) A

Significant point name

For all RNP APCH procedure ( NPA and

To avoid ambiguity add a suffix letter

The information in the MINIMUM BOXES

LNAV/VNAV in minimum boxes

OCA/OCH CATA CATB CATC CATD

For baro-VNAV procedure publication of

• LPV in the minimum boxes

OCA/OCH CATA CATB CATC CATD

SBAS Minimum Line

baroVNAV Minimum Line

NPA Minimum Line

PROCEDURE ALTITUDE CONCEPT

Minimum altitudes include provision for

• What does mean minimum altitude?

Minimum Obstacle Clearance Altitude

From Vol II Part I Section 4 chap1

To support CFIT prevention initiative,

Arrival and departure procedure altitudes

Recommended altitude : altitude

A/C are AT OR ABOVE

Procedure altitude is provided in the profile view

Minimum altitude (MOCA) or a ground profile is

MOCA along intermediate and final segments are

2,000’ not in database

Ref Part III section 4 chapter 1

Formal Description Abbreviated Expected Path Fly-over

Climb on track M047, A800+, FA or CA N

Enable description of the procedure to

General instructions in AIP

Sequencing description in AIP

Publication of WP co-ordinates in AIP

For CF path terminator

You might also like