Basic Data of Route Segment

Introduction

For Route Segment, PANS-AIM requires some basic properties as part of the minimum AIP data set. This is

...,from point, to point, track, distance, upper limit, lower limit, MEA, MOCA, ...

The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information:

From Point & To Point

ICAO defines a route segment as

A portion of a route to be flown usually without an intermediate stop, as defined by two consecutive significant points.

In AIXM 5, the start and the end properties of the RouteSegment class are used to define the "From point", i.e. the first point of the route segment and "To point", i.e. the second point of a route segment.

The EnrouteSegmentPoint class used for that purpose is a specialisation of the SegmentPoint. It provides the reportingATC attribute which is used for the indication of the ATS / MET reporting requirement 'COMPULSORY' or 'ON_REQUEST' for the corresponding point.

The actual start or end point of a RouteSegment is defined via the pointChoice property that allows to select a SignificantPoint. Not all available choices of significant points (e.g. RunwayCentrelinePoint, etc.) will make sense to be used for a route segment point (see also page SignificantPoint [SPN] ).

Mainly DesignatedPoint and Navaid will be the start or end point of a RouteSegment. In a few countries, also the airport reference point of an AirportHeliport may be used for that purpose.

For defining that the point used for the route segment is an RNAV waypoint (see also topic Designated Point (Overview)) the EnrouteSegmentPoint.waypoint attribute will be encoded with 'YES'.

In addition, AIXM 5 provides as an option to encode the extend of the route segment as geometrical element, using the Curve class. This data may be used for charting purposes. The curve will be encoded according to the corresponding GML specification (see topic Geometry (Overview)). It will contain the coordinates of the start and end point of the route segment. It shall be ensured that the data (i.e. coordinates) provided in the Curve element(s) match with those provided as start and end of the RouteSegment.

Implicit direction

As every route segment is defined 'from' a start point 'to' an end point, it has an implicit direction. This direction should be consistent with the direction of the route. The start point of a route should also be the 'from' point of the first route segment and the end point of the route should be the 'to' point of the last segment.

The implicit direction of a route segment is relevant when specifying the route availability (see also page Direction of Cruise Levels).

Rules are included in the model to enforce consistency between the general direction of the route and the implicit direction of every segment (see below).

Track & Length

The RouteSegment class provides several attributes to define the initial trueTrack, initial magneticTrack, the initial reverseTrueTrack and the initial reverseMagneticTrack of it.

For "ENR 3.3 Area navigation routes", PANS-AIM explicitly requires that the magnetic bearing of the route segment is provided. For all other routes defined in ENR 3, PANS-AIM requires a track or VOR radial applying the following note

Bearings, tracks and radials are normally magnetic. In areas of high latitude, where it is determined by the appropriate authority that reference to Magnetic North is impractical, another suitable reference, i.e. True North or Grid North, may be used.

Tracks and reverse tracks if any, shall be encoded taking into account the implicit direction of the route segment, i.e. the defined start and end point, (see also above). In this regard, the tracks are from the start point of the segment, whereas the reverse tracks are from the end point of the route segment.

The length attribute allows to define the distance of the path of the RouteSegment. The length depends on the pathType, which may be a great circle ('GRC'), a rhumbline ('RHL') or a geodesic line ('GDS'). 

Lateral Limits

For "ENR 3.1 Lower ATS routes" and "ENR 3.2 Upper ATS routes", PANS-AIM requires the provision of lateral limits.

The RouteSegment class provides the attributes widthLeft and widthRight to define the lateral limits. These are the distances from the centreline of the route segment to the left and right edge respectively. For example, if the route segment has a defined width of 10 NM for each of the attributes will carry the value '5' uom equal-to 'NM'.

Vertical Limits

PANS-AIM requires that all routes/route segments have at least a lower limit and an upper limit.

For some types of routes, viz. ENR 3.1 (Lower ATS Routes) and ENR 3.4 (Helicopter Routes), also minimum obstacle clearance altitudes and minimum flight altitudes, respectively shall be provided.

According to ICAO Annex 11:

The minimum flight altitudes determined shall provide a minimum clearance above the controlling obstacle located within the areas concerned.

Whereas, the States should publish, “The criteria used to determine minimum flight altitudes”, in AIP section GEN 3.3.5.

Depending on the purpose and classification of the route different vertical limits may be required by PANS-AIM:

ENR 3.1 (Lower ATS Routes):

• upper and lower limits or minimum en-route altitudes.
• minimum obstacle clearance altitudes;
• Since en-route flights at or above the lowest usable flight level are flown at flight levels, it is suggested that these limits be expressed in flight levels (FL) whenever such flight levels are not likely to fall below the lowest safe altitude; otherwise, they should be expressed in altitude.

ENR 3.2 (Upper ATS Routes):

• upper and lower limits (usually in flight levels "FL”).

ENR 3.3 (RNAV Routes):

• upper and lower limits (usually in flight levels "FL”).

ENR 3.4 (Helicopter Routes):

• upper and lower limits; minimum flight altitudes

ENR 3.5 (Other Routes):

• No requirements stated regarding vertical limits.

The following table gives an overview which vertical limits are required by PANS-AIM for the AIP data set and the corresponding AIXM attributes of the RouteSegment class (Note 1):

PANS-AIM			AIXM 5.1.1		Remarks
Property	Definition/Description	Relevance	Attribute	Description
Upper limit	The upper limit of the route segment	ENR 3.1-3.4	upperLimit	The vertical position of the route segment ceiling.
Lower Limit	The lower limit of the route segment	ENR 3.1-3.4 (Note 2)	lowerLimit	The vertical position of the route segment floor.	Note 2 According to PANS-AIM for ENR 3.1 Lower ATS Route, lower limits or minimum en-route altitudes shall be defined. In the "old" ICAO Annex 15 it was lower limits or minimum flight altitudes
Minimum obstacle clearance altitude (MOCA)	The minimum altitude for a defined segment of flight that provides the required obstacle clearance. minimumObstacleClearingAltitude	ENR 3.1 Lower ATS Route	minimumObstacleClearanceAltitude, RouteSegment.annotation.Note.propertyName value equal-to 'minimumObstacleClearanceAltitude'	Minimum obstacle clearance altitude (MOCA). The minimum altitude for a defined segment of flight that provides the required obstacle clearance.	According to ICAO PANS-OPS  A MOCA is determined and published for each segment of the route. In PANS-AIM it is only required for ENR 3.1 Lower ATS Routes. The MOC value to be applied in the primary area for the en-route phase of an IFR flight is 300 m (1 000 ft) as a minimum. AIXM 5.1.1 issue_008_MOCA PANS-AIM requires a accuracy to be specified for the MOCA. AIXM does not have a dedicated attribute for that purpose. Workaround for AIXM 5.1(.1): Code a corresponding Note. Status: For AIXM 5.2 see CCB AIXM-269.
Minimum en-route altitude (MEA)	The altitude for an en-route segment that provides adequate reception of relevant navigation facilities and ATS communications, complies with the airspace structure and provides the required obstacle clearance.	ENR 3.1 Lower ATS Route (Note 2)	minimumEnrouteAltitude, RouteSegment.annotation.Note.propertyName value equal-to 'minimumEnrouteAltitude'	Minimum en-route altitude (MEA). The altitude for an en-route segment that provides adequate reception of relevant navigation facilities and ATS communications, complies with the airspace structure and provides the required obstacle clearance.	According to ICAO PANS-OPS The MEA is the greatest of: the MOCA; the minimum altitude for proper reception of the relevant facilities; the minimum altitude for proper reception of ATS communications; the minimum altitude that complies with the ATS structure. AIXM 5.1.1 issue007_MEA PANS-AIM requires a accuracy to be specified for the MEA. AIXM 5.1.1 does not have a dedicated attribute for that purpose. Workaround for AIXM 5.1(.1): Code a corresponding Note. Status: For AIXM 5.2 see CCB AIXM-269.
Minimum flight altitude	Minimum flight altitude	ENR 3.4 Helicopter routes	minimumObstacleClearanceAltitude, RouteSegment.annotation.Note.propertyName value equal-to 'minimumObstacleClearanceAltitude'		According to PANS-AIM The criteria used to determine minimum flight altitudes shall be provided in GEN 3.3.5. In PANS-AIM the term is only used for "ENR 3.4 Helicopter routes" ICAO Annex 11, 2.23 Minimum flight altitudes Minimum flight altitudes shall be determined and promulgated by each Contracting State for each ATS route and control area over its territory. The minimum flight altitudes determined shall provide a minimum clearance above the controlling obstacle located within the areas concerned. AIXM 5.1.1 issue_009_Minimum fight altitude  AIXM 5.1.1 does not have a dedicated attribute for that purpose. As, in PANS-AIM there is no definition for for Minimum flight altitude. For this mapping it is assumed that it may be the either the MEA or the MOCA for helicopters. Workaround for AIXM 5.1(.1): Code a RouteSegment.minimumObstacleClearanceAltitude,  or RouteSegment.minimumEnrouteAltitude. Status: To be reported to CCB

Regarding the general encoding guidelines and rules for vertical limits see topic Vertical Limits.

Level

Although this information is not explicitly required by PANS-AIM it should be coded at least for route segments published in an AIP in Section ENR 3.1 Lower ATS routes and  ENR 3.2 Upper ATS Routes, with 'LOWER' and 'UPPER' respectively. This is also relevant as some Coding Rules relate on this information (see below).

Coding Rules for Basic Data for Route Segment 

Coding Examples

The figure below gives a simple example of the encoding of the route segment from "DINKI" to "LNO".

The figures below give an example of the encoding of the route segment (from "BARIM" to "WOB"), including the mapping from AIXM UML to AIXM XML.

More coding examples can be found in the AIP Data Set - Specimen (DONLON).

References