Transcript CHARTING Regulation and issues

CHARTING
Regulation and issues
ACAC RNAV Procedures Workshop
10-11-12-13 September 2002-Morocco
ARAB INSTRUMENT PROCEDURE DESIGN SEMINAR
CONTENTS

Charting in the RNAV context



Regulation
Charting objectives
User needs
 RNAV procedure identification



Objectives and standards
RNAV procedure identification
Standards evolution proposals
 Waypoint naming and symbology



The issues
Waypoint symbology
Waypoint naming
REGULATION
 The ICAO defines the SARPS in the charting area, both for
conventional and RNAV procedures
Pans-Ops (vol. I and II)
Annex 4
Annex 15
 These standards are regularly updated, but with a low frequency



Technical work is conducted in specific international working groups
(Obstacle Clearance Panel, AIS/MAP section)
ICAO Air Navigation Commission approval
Consultation of Member States
REGULATION (2)
 Some other regional or industry standards have been developed for :


Support of new RNAV operations in terminal airspace
Harmonization with on-board map displays
Charting guidelines for RNAV procedures (TARA)
EUROCONTROL
User recommendations for AIS (ED77 / DO201A)
Maps MOPS
… and various national reference documents (SAE G10, etc.)
CHARTING OBJECTIVES
DEPICTION OF ALL
THE NECESSARY
INFORMATION
CLEARLY
ACCORDING TO
USER NEEDS
USERS
OPERATIONAL USERS
Pilots
TECHNICAL SUPPORT
USERS
Flight planning support
Navigation database providers
Air Traffic Control
RNAV system manufacturers
Commercial charting providers
OPERATIONAL USER NEEDS
 Sufficient data to conduct operations.
 Charts



easy to read
unambiguous
only data which is necessary for the operation.
 Coordinates, bearings and distances to a resolution that is
compatible with the operational system displays
TECHNICAL SUPPORT USER
NEEDS
 Sufficient data to define instrument procedures.
 Data resolution appropriate to meet the operational
system’s computational requirements.
 Charts used to validate the output from the operational
systems.
THE NECESSARY
INFORMATION
Procedures are currently published as charts and as
textual descriptions
The charts are used by the pilots and ATC
Database providers require clear, and unambiguous
procedure descriptions and use the charts to
validate/check
RNAV SPECIFIC
INFORMATION
RNAV procedures are defined by:

Sequence of waypoints
•
•
•





Identifier
Coordinates
Fly-over/fly-by/fixed radius
Path Terminators - ARINC 424
Altitude restrictions
Speed restrictions
Direction of turn
Required navaid
INFORMATION FOR PILOTS
INFORMATION FOR ATC
INFORMATION FOR
NAVIGATION
DATABASE SUPPLIERS
SUMMARY
Fly-over/fly-by/fixed radius
Speed/Altitude Restrictions
Leg distance & magnetic track
169° ARZ 29.3NM
236° ALM 27.4NM
113
°
FAF
PT121
4000
°
Waypoint sequence
203

PT118
5000
PT119
4000
293
°
PT120
4500
Fix information
Turn direction
MAPt
RW20
350°
PT125
ADDITIONAL TEXTUAL
DESCRIPTION
Textual description is usually used to provide formal statement of
procedure
Often open to interpretation
RNAV procedures require more specific details including path
terminators
Can result in lengthy descriptions
Alternative descriptive methods are being considered :
 Tabular layout
 Formalised textual description
 Formalised short-hand description
TABULAR DESCRIPTION
RNAV Approach
Designator
Sequence
Number
RNAV(DME) RW35L
RNAV(DME) RW35L
RNAV(DME) RW35L
RNAV(DME) RW35L
RNAV(DME) RW35L
RNAV(DME) RW35L
001
002
003
004
005
006
Path
Waypoint Fly
Terminator
Name
Over
IF
TF
CF
TF
FA
DF
SUSER
CV023
CV024
RW35L
RW35L
SUSER
Y
Y
Course/Track/
Heading ºM (ºT)
Turn
Altitude
Speed Required
Direction Constraint Constraint Navaid
348º (347.8º)
348º (347.8º)
-
L
-
+5000
4000
2680
370
770
5000
250
150
-
-
Bearing/
Range to
Navaid
LOM 262/29
-
VPA/
TCH
-3º/50
-
RNAV SID
Designator
Sequence
Number
TARAH1A
TARAH1A
TARAH1A
TARAH1A
001
002
003
004
Path
Waypoint
Terminator
Name
FA
DF
TF
CF
RW20
FOKSI
PF213
TARTO
Fly
Over
Course/Track/
Heading ºM (ºT)
Y
-
201º (203.3º)
345º (346.8º)
254º (256.1º)
Turn
Altitude
Speed
Required
Direction Constraint Constraint Navaid
R
-
400
+5000
+FL100
250
250
250
-
Bearing/
Range to
Navaid
OKE 330/30
-
FORMALIZED DESCRIPTION
Climb on track 047° M to 800ft, turn right
[A800+; M047; R]-
FA
Climb on heading 123° M to 1000ft, turn right
[A1000+; M123; R]-
VA
Direct to ARDAG at or above 3000ft
ARDAG[A3000+]-
DF
To PF035 at or below 5000ft, then turn left
-PF035[A5000-;L]-
TF (Fly-over)
To OTR on course 090°M at 210kts
-OTR[M090; K210]-
CF
To STO at or above FL100, turn left
STO[F100+; L]-
TF (Fly-over)
direct to WW039 at or above FL070,
WW039[F070+]-
DF
to WW038 at 5000ft
WW038[A5000]
TF
CONTENTS
 Charting in the RNAV context




Regulation
Charting objectives
User needs
RNAV procedure identification



Objectives and standards
RNAV procedure identification
Standards evolution proposals
 Waypoint naming and symbology



The issues
Waypoint symbology
Waypoint naming
OBJECTIVES
HARMONIZATION
REGULATORY STANDARDS
EVOLUTION
 OCP 12 + AIS/MAP : RNAV procedure identification validation and publication (Annex 4, amendment 51)
 OCP 13 + AIS/MAP : Conventional and RNAV procedure
identification



Titles
Required equipment
Operational minima
RNAV PROCEDURE
IDENTIFICATION
All RNAV procedures
(departures, arrivals and approaches)
must be identified as such
INSTRUMENT
APPROACH
CHART - ICAO
ELEV 372
OCH RELATED TO
THR 20 ELEV 310
MIN TEMP -15°C
VAR 1.5° W
121.700 TOWER
127.950 GROUND
118.020 APRON
ATIS
RADAR
ARRIVAL
PATEON EXPT
RNAV RWY 20
124.850
121.775
123.125
MSA ARP 25 NM
15
Both DME/DME and Basic GNSS (GPS) may be used.
0°
3426
AIRIEZ
115.95 ARZ
CH 106Y
3333
3972
3 0 00
2400'
270°
Reversion to VOR/DME or IRS is acceptable in accordance with
JAA guidance.
1500'
3500'
360°
MATTVILLE
1250
Bearings and tracks are magnetic.
Tracks in brackets are true.
Altitudes, elevations and heights
in feet AMSL
1163
If more than 2 DME inputs cannot be guaranteed at all times,
this should be highlighted in explanatory text.
11
8°
60
1 m 00
in
IAF
KENNY
2000
233° ARZ 12.6NM
1750
(2 9 2 9 8 °
7. 0
°T)
991
997
1164
Where reversion to a specific VOR/DME is required for part of
the procedure, the navaid must be clearly identified as the
recommended navaid.
9°
14 5°T)
7.
(14
ALMERUS
109.20 ALM
CH 29X
064
PT118
5000
1000
PT119
4000
1
(11 13°
1.5
°T)
2
FAF
(29 93°
1
.5°T
PT121
)
4000
°
0
700 in
m
1
4°
1301
TOMASO
LIZBOURG
993
24 °T)
3. 0
2
( 4
407
169° ARZ 29.3NM
236° ALM 27.4NM
SUNGA
MIO
MAPt
2
(20 03°
1.5
°T)
Where a reversion to VOR/DME is allowed but is NOT
mandated, recommended navaids are NOT required.
MIOTTA
370 MIO
258°
°T)
(256.5
IAF
BECKA
162° ALM 10.8NM
PT120
4500
BUGEON
638
RNAV PROCEDURE
IDENTIFICATION
Identification may also include reference to the
navigation infrastructure available:
RNAV(DME/DME)
RNAV(GNSS)
RNAV(Except Class A GNSS)
RNP(x)
INSTRUMENT
APPROACH
CHART - ICAO
ELEV 372
OCH RELATED TO
THR 20 ELEV 310
MIN TEMP -15°C
VAR 1.5° W
ATIS
RADAR
ARRIVAL
121.700 TOWER 124.850
127.950 GROUND 121.775
123.125
118.020 APRON
PATEON EXPT
RNAV (DME/DME)RWY 20
MSA ARP 25 NM
15
0°
Only DME/DME may be used.
3426
AIRIEZ
115.95 ARZ
CH 106Y
3333
3972
3000
270°
1500'
3500'
360°
Reversion to VOR/DME is not allowed.
MATTVILLE
2400'
1250
Reversion to IRS is acceptable in accordance with JAA
guidance.
If more than 2 DME inputs cannot be guaranteed at all
times, this should be highlighted in explanatory text
INSTRUMENT
APPROACH
CHART - ICAO
ELEV 372
OCH RELATED TO
THR 20 ELEV 310
MIN TEMP -15°C
VAR 1.5° W
ATIS
RADAR
ARRIVAL
121.700 TOWER 124.850
127.950 GROUND 121.775
123.125
118.020 APRON
PATEON EXPT
RNAV (GNSS) RWY 20
MSA ARP 25 NM
0°
AIRIEZ
115.95 ARZ
CH 106Y
15
Only GNSS may be used.
3426
3333
3972
3000
2400'
270°
1500'
When Galileo and the Space Based Augmentation Services
are available, it is anticipated that the generic terms B-GNSS,
or ABAS, and SBAS will be used instead.
360°
MATTVILLE
3500'
1250
Reversion to VOR/DME is not allowed.
Reversion to IRS is acceptable in accordance with JAA
guidance.
INSTRUMENT
APPROACH
CHART - ICAO
ELEV 372
OCH RELATED TO
THR 20 ELEV 310
MIN TEMP -15°C
VAR 1.5° W
ATIS
RADAR
ARRIVAL
121.700 TOWER 124.850
127.950 GROUND 121.775
123.125
118.020 APRON
PATEON EXPT
RNAV (Except Class A GNSS) RWY 20
MSA ARP 25 NM
15
Both DME/DME and Class B and C GNSS may be used.
0°
3426
AIRIEZ
115.95 ARZ
CH 106Y
2400'
270°
Reversion to VOR/DME or IRS is acceptable in accordance with JAA
guidance.
3333
1500'
3500'
360°
MATTVILLE
3972
3000
1250
If more than 2 DME inputs cannot be guaranteed at all times, this
should be highlighted in explanatory text.
Where a reversion to a specific VOR/DME is required for part of the
procedure, the navaid must be clearly identified as the recommended
navaid.
Where a reversion to VOR/DME is allowed but is NOT mandated,
recommended navaids are NOT required.
INSTRUMENT
APPROACH
CHART - ICAO
ELEV 372
OCH RELATED TO
THR 20 ELEV 310
MIN TEMP -15°C
VAR 1.5° W
ATIS
RADAR
ARRIVAL
121.700 TOWER 124.850
127.950 GROUND 121.775
123.125
118.020 APRON
PATEON EXPT
RNP (0.3) RWY 20
MSA ARP 25 NM
15
0°
3426
AIRIEZ
115.95 ARZ
CH 106Y
3333
3972
3000
2400'
270°
1500'
3500'
1250
360°
The procedure is for RNP 0.3 RNAV capable
aircraft only.
MATTVILLE
8M
LW
RNAV SID & STAR
R 19
P- 032°
RN
AV
R 198 MLW 33D
Where part of a P-RNAV
SIDrequired
or STAR is to be flown conventionally
100 or
MIOTTA
and part is designated as appropriate
P-RNAV
MIO for B-RNAV,
0
MATTI
370 MIO
FL 70
RNP (x) RNAV capable aircraft, it should be annotated on the
chart itself.
450
1E
°
LNT 1W
KA
J
°
PT015
ES
P
20 3
97
ON
018
R2
297
°
267°
PT019
PT017
237
R 297 ESP 18D
P-RNAV required
2465
PT018
4500
MAX 230 KIAS
ATECA 1E
084°
P-RNAV
ATEC
EASPORT
115.45 ESP
CH 101Y
1
P-R 17° ESP
NA
2E
V
572
STANDARDS EVOLUTION
PROPOSALS
 Current situation : conventional procedure should be named according
to the navaid(s) to be used
 This standard causes :



many variations in chart titles from State to State
pilots to hear different clearances from State to State
different expectations for equipment requirements
 In the future


title of approach procedure will be the same as the navigation system
providing the final approach lateral guidance (LLZ, VOR, NDB) or the
precision approach system (ILS, MLS).
Other navaids required for the procedure will appear on the chart (not
in the title)
STANDARDS EVOLUTION
 Guidance for procedure designers, to be included in PANS-OPS
Volume II
 References to PANS-OPS Volume II to be included in Annex 4
 OCP 13 + AIS/MAP : Conventional and RNAV procedure
identification



Information to be contained in the titles
Navigation equipment requirements
Navigation equipment optional to obtain better minimums
 Applicable in November 2004
PROPOSED NEW PROCEDURE
TITLES (EXAMPLES)
 ILS or LLZ Rwy 25 - localizer required and glide slope available


When glide slope available, clearance from controller would be for ILS Rwy 25.
When glide slope not available, clearance from controller would be for Localizer Rwy 25
 ILS Rwy 25 - localizer required and glide slope required. (There are cases
where the glide slope must be used because of final approach segment
obstacles.)
 ILS or LLZ Rwy 07L - localizer and DME required and glide slope available.
Note on chart for DME required.
 VOR Rwy 04 - only VOR required - also used when DME available for better
minima or stepdown fixes, etc.
 VOR Rwy 11 - VOR and DME required. Note on chart for DME required
 NDB Rwy 17R - NDB or locator and DME required. Note on chart for DME
required.
CONTENTS
 Charting in the RNAV context



Regulation
Charting objectives
User needs
 RNAV procedure identification




Objectives and standards
RNAV procedure identification
Standards evolution proposals
Waypoint naming and symbology



The issues
Waypoint symbology
Waypoint naming
WAYPOINT SYMBOLOGY
ISSUES
 Need to standardize the symbology
used both for charts and onboard
equipment
ICAO
Symbol type
 The symbology shall encompass the
different kinds of waypoints


Fly-over waypoints
Fly-by waypoints
 The waypoint symbology shall
accomodate other symbols such as
the navaids or the significant points
(fixes) ones
VOR
DME
TACAN
VORDME
VORTAC
NDB
Intersection
Waypoint
Airport
Jeppesen
Boeing
Airbus
WAYPOINT SYMBOLOGY
OCP 12
PROPOSALS
consistency with navaids
and fixes symbology
Fly-by with VOR/DME
Fly-over with Reporting Point
WAYPOINT SYMBOLOGY
PROPOSALS
ILLUSTRATION OF NAMING
CONVENTION ISSUES








High workload due to runway change.
ATC clears to Rozo
Rozo is “R” NDB on the chart.
Crew enter “R” in the FMS, Bogota Romeo
NDB (Romeo, 1st “R” on the list as the
closest of the data base, among 12 other “R”)
Romeo and Rozo are about 150 Nm away
from each other.
The plane starts a left turn, which is detected
and corrected after a 90° turn.
A GPWS alarm is triggered
Despite a quick crew response the plane
crashed into a 12000 ft summit.
Direct to
NDB « R »
NAMING CONVENTION
ISSUES
 The information created by States may work very well in the paper
world but the electronic world creates new challenges.
 It is essential to create new awareness of the differences that happen
between the charts and what pilots see on their avionics
 The consistency of wording for waypoints used by ATC, Airspace
Authorities, and database providers is a major issue
 This issue is a top level/cross border issue involving every speciality
(not only FMS Safety Assessment)
WAYPOINT NAMING ISSUES
 The current ICAO naming convention is based upon the use of 5
letter name codes (5LNC)
 This convention ensures global uniqueness…
 … but it does not provide the flexibility required for RNAV
procedures


Waypoints correlation within a given procedure
Ease for pilots / controllers to recognize the sequence of waypoints
 Hence, extension (not amendment) to the ICAO convention is
proposed
 The extension is already applied in several States
WAYPOINT IDENTIFICATION
 Waypoints are used to define ‘RNAV routes and flight paths of
aircraft employing RNAV systems’.
 Significant points are used to describe a ‘specified geographical
location used in defining an ATS route or the flight path of an
aircraft and for other navigation and ATS purposes’.
 All waypoints = significant points.
WAYPOINT IDENTIFICATION
 Significant points identified by co-located navaid or by unique fiveletter pronounceable “name-code” (5LNC).
 However some waypoints in the terminal area used for vectoring or
for sequencing and must be easy to enter in an RNAV system.
 5LNCs are not appropriate for this.
 Some regional organizations (EUROCONTROL, AUSTRALIA
CAA, ECAC States) have adopted a concept of strategic and tactical
waypoints to address this problem
 The proposals are being examined, harmonized and submitted for
approval by OCP (OCP 13)
TACTICAL AND STRATEGIC
WAYPOINTS
 A strategic waypoint is a waypoint in the terminal area which is:


of such significance to the ATS provider that it must be easily
remembered and stand out on any display, or
used as an ‘activation point’ to generate a message between
computer systems when an aircraft passes it.
 Strategic waypoints are identified with 5LNCs unless they are colocated with a navaid, when the 3 letter navaid ID is used.
 A tactical waypoint is a waypoint which is defined solely for use
in the specific terminal area and has not been designated a
strategic waypoint.
TACTICAL WAYPOINT
NAMING CONVENTION
 Identified as AAXNN, where:
 AA - the last two characters of the aerodrome location indicator,

X - a numeric code from 0 to 9 (N, E, W and S may be used instead if a
State has a requirement for quadrantal information)
 NN - a numeric code from 00 to 99.
 If co-located with a navaid, the navaid three letter identifier is used.
 If co-located with the runway threshold, an identifier in the format
RWNNA is used, where:

NN - a numeric code from 01 to 36 and
 A is an optional alphabetic code of ‘L’, ’C’ or ‘R’.
WAYPOINT VERSUS FIX
 A waypoint is defined by coordinates.
 A fix may be defined by the intersection of 2 radials or
radial and distance.
 HOWEVER, on RNAV approaches:





Initial approach waypoint - IAF
Intermediate waypoint - IF
Final approach waypoint - FAF
Final approach point (ILS/Baro VNAV) - FAP
Missed approach waypoint - MAPt.
R 198 MLW 33D
P-RNAV required
P- 032°
RN
AV
R 19
8M
LW
WAYPOINT NAMING AND
SYMBOLOGY
MIOTTA
370 MIO
MIO
Proposed waypoint symbology
MATTI
FL 70
100
0
450
1E
°
267°
PT019
PT017
237
R 297 ESP 18D
P-RNAV required
PT018
4500
MAX 230 KIAS
E ARZ 29.3NM
ATECA 1169°
084°
P-RNAV
236° ALM
27.4NM
ATECA
EASPORT
115.45 ESP
CH 101Y
1
P-R 17° ESP
NA
2E
V
113
°
FAF
PT121
4000
°
KA
J
°
297
PT118
5000
203
LNT 1W
PT015
ES
P
203
97
ON
01 8
°
R2
2465
PT119
4000
293
°
PT120
4500
572
Waypoint naming convention
MAPt
RW20
350°
PT125
SUMMARY
PATEON
RWY 20
121.700 TOWER
127.950 GROUND
118.020 APRON
ATIS
RADAR
ARRIVAL
RNAV(Except Class A GPS) STAR TO FINAL APPROACH
124.850
121.775
123.125
TRANSITION ALTITUDE 8000'
TRANSITION FLIGHT LEVEL 90
MSA ARP
MATTVILLE
233° ARZ 12.6NM
270°
1500'
3500'
8°
1750
Y
991
997
360°
00
N
29
2400'
1163
N
KE
60
8°
IAF
KENNY
0°
11
15
AIRIEZ
115.95 ARZ
CH 106 Y
1250
VAR 1.0° W
ELIZABETH
1A
ALMERUS
109.20 ALM
CH 29 X
1164
13
7°
PT117
TOMASO
700
1000
BECKA
1A
023
SUZER
°
FAF
PT121
4000
162° ALM 10.8NM
PT120
4500
842
BUGEON
022
699
MIOTTA
370 MIO
638
018
NOODEL
PT029
2A
OCTONAU
635
6
05
°
1564
LNT 1A
089°
PT016
377
ATLANTO
112.50 LNT
CH 72 X
284
290
°
ES P
1A
IAF
1000
EASPORT
115.45 ESP
CH 101 Y
P
237
SCHNOOKI
IAF
ES
8°
8°
00
2465
7°
80
29
RW20
32
11
858
HAGAR
°
203
T
LN
°
IAF
BECKA
°
450
05
0
244
PT116
PT119
SUNGA
0°
°
726
°
4000
MAX 220 KIAS
407
PT115
HERON
PT118
5000
LIZBOURG
993
064
1301
PT114
Bearings and tracks are magnetic.
Tracks in brackets are true.
Altitudes and elevations in feet AMSL.
110
2A
500
572
290
°
0
°
Carriage of Dual RNAV Systems
is mandatory.
ARZ, ALM, LNT and ESP
must all be serviceable
for DME/DME operations.
THANK YOU FOR YOUR
ATTENTION
ANY QUESTION?