Procedure Identification, Description and Charting Jeremy Jeremy Davidson AMN Unit EUROCONTROL Agenc

1
Procedure Identification Description and
ChartingJeremy Jeremy Davidson AMN
Unit EUROCONTROL Agency
2
Users

• Operational Users
• Pilots
• ATC
• Technical Support Users
• RNAV System Manufacturers
• Navigation Database Providers
• Commercial Charting Providers
• Flight Planning Support

3
Operational Users

• Sufficient data to conduct operations.
• Charts
• easy to read
• unambiguous
• only data which is necessary for the operation.
• Co-ordinates bearings and distances to a
  resolution that is compatible with the
  operational system displays.

4
Technical Support

• Sufficient data to define instrument procedures.
• Data resolution appropriate to meet the
  operational systems computational requirements.
• Charts used to validate the output from the
  operational systems.

5
Procedure Identification

• All RNAV procedures must be identified as such.

6

• Both DME/DME and Basic GNSS (GPS) may be used.
• Reversion to VOR/DME or 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.
• Where 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.

7
Procedure Identification

• All RNAV procedures must be identified as such.

Identification may also include reference to the
navigation infrastructure available RNAV(DME/DME)

8

• Only DME/DME may be used.
• Reversion to VOR/DME is not allowed.
• 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.

9
Procedure Identification

• All RNAV procedures must be identified as such.

Identification may also include reference to the
navigation infrastructure available RNAV(DME/DME)
RNAV(GNSS)
10

• Only GNSS may be used.
• 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.
• Reversion to VOR/DME is not allowed.
• Reversion to IRS is acceptable in accordance with
  JAA guidance.

11
Procedure Identification

• All RNAV procedures must be identified as such.

Identification may also include reference to the
navigation infrastructure available RNAV(DME/DME)
RNAV(GNSS) RNAV(Except Class A GNSS)
12

• Both DME/DME and Class B and C GNSS may be used.
• Reversion to VOR/DME or 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.
• 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.

13
Procedure Identification

• All RNAV procedures must be identified as such.

Identification may also include reference to the
navigation infrastructure available RNAV(DME/DME)
RNAV(GNSS) RNAV(Except Class A GNSS) RNP(x)
14

• The procedure is for RNP 0.3 RNAV capable
  aircraft only.

15
Where part of a SID or STAR is to be flown
conventionally and part is designated as
appropriate for B-RNAV P-RNAV or RNP (x) RNAV
capable aircraft it should be annotated on the
chart itself.
16
Description

• 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.

17
Description

• RNAV procedures defined by
• Sequence of waypoints
• Identifier
• Co-ordinates
• Fly-over/fly-by/fixed radius
• Path Terminators - ARINC 424
• Altitude restrictions
• Speed restrictions
• Direction of turn
• Required navaid

18
Description

• Pilots need to know
• Waypoint names and sequence
• Fly-over/fly-by/fixed radius
• Turn direction
• Speed restrictions
• Altitude restrictions
• Required navaid
• Leg distance and magnetic track for error checks
• Fixes at certain waypoints for gross error checks

19
Description for Operational Use

• Waypoint sequence

• Fly-over/fly-by/fixed radius

• Speed/Altitude Restrictions

• Leg distance magnetic track

• Fix information

• Turn direction

20
Description

• Database providers require to know
• Waypoint identifier and co-ordinates
• Waypoint sequence
• Fly-over/fly-by/fixed radius
• Speed restrictions
• Altitude restrictions
• Turn direction
• Required path terminator
• Required magnetic track if CF leg
• Required navaid for VOR/DME and for CF leg to
  obtain magnetic variation!

21
Procedure 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

22
Tabular Description
23
Formalised Descriptions
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 ARDAGA3000- DF To PF035 at or below
5000ft then turn left -PF035A5000-L- TF
(Fly-over) To OTR on course 090M at
210kts -OTRM090 K210- CF To STO at or above
FL100 turn left STOF100 L- TF
(Fly-over) direct to WW039 at or above FL070
WW039F070- DF to WW038 at 5000ft WW038A5000
TF
24
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.

25
Waypoint Identification

• Significant points identified by co-located
  navaid or by unique five-letter pronounceable
  name-code (5LNC).
• HOWEVER some waypoints in the terminal area used
  for vectoring for sequencing and must be easy to
  enter in an RNAV system.
• 5LNCs not appropriate for this.
• Proceed direct ALECS (or ALEKX ALECS ALECX
  ALLEX ALIKS ALIKX ALICX ALLIX ALYKS ALYKX
  ALYCS ALYCX ALLYX).
• ECAC States have adopted a concept of strategic
  and tactical waypoints to address this problem.

26
Tactical 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 co-located with a navaid when
the 3 letter navaid ID is used.
27
Tactical Strategic Waypoints
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. 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.
28
Tactical Strategic Waypoints
Exceptions 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. If
designated by the ATS provider as a Strategic TMA
Waypoint the 5LNC is used.
29
Waypoints and Fixes

• A waypoint is defined by co-ordinates.
• 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.

30
Charting - Symbology
RNAV route defined by waypoints
Fly-by
Fly-over
Fixed Radius
31
Charting - Symbology
Fly-by with VOR/DME
Fly-over with Reporting -Point
32
Charting - Altitude Restrictions
An at or above altitude 7000
33
(No Transcript)
34
(No Transcript)
35
Questions