d) Route segment
- Wolfgang Scheucher
- POROSNICU Eduard
- François Germain
Basic mapping
The properties of the Route segment subject listed in PANS-AIM are mapped to the following AIXM 5 features:
%20Route%20segment%20-%20Basic%20Mapping.png?version=2&modificationDate=1490977110000&cacheVersion=1&api=v2)
In AIXM 5, a SignificantPoint is used as start and end point of a Route Segment. The diagram below shows the choice of all the possible AIXM 5 classes that can be used as Significant Point.
Note:
Not all choice classes for SignificantPoint make sense to be used as EnRouteSegmentPoint for a RouteSegment. For the mapping only Navaid, DesignatedPoint and AirportHeliport are considered.
| PANS-AIM | Description (PANS-AIM) | AIXM 5 | Definition (AIXM 5.1.1) | Remarks |
|---|---|---|---|---|
| Navigation specification | Designation of the navigation specification(s) applicable to a specified segment(s) - There are two kinds of navigation specifications: Required navigation performance (RNP) specification. A navigation specification based on area navigation that includes the requirement for performance monitoring and alerting, designated by the prefix RNP, e.g. RNP 4, RNP APCH. Area navigation (RNAV) specification. A navigation specification based on area navigation that does not include the requirement for performance monitoring and alerting, designated by the prefix RNAV, e.g. RNAV 5, RNAV 1. | RouteSegment.navigationType | RouteSegment: A portion of a route to be flown usually without an intermediate stop, as defined by two consecutive significant points. navigationType: Classification of the Route Portion for navigational purposes. Examples: conventional, RNAV. | AIXM 5.1.1 issue_005:RouteSegment.navigationType PANS-AIM makes reference to PBN (Performance Based Navigation) classification. The current AIXM 5.1.1 version does not support all PBN values. The navigationType attribute of AIXM only provides as values 'RNAV', 'CONV' and 'TACAN', but no PBN specifications (such as RNAV 10 , RNP 4 etc). Most missing PBN values can be coded using navigationType equal to 'RNAV' or 'OTHER:RNP' and requiredNavigationPerformance with the navigation accuracy value, e.g. '10' or '4'. AIXM 5.2 Improvement A change proposal (AIXM-472) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which aligns the list of values for navigationSpecification with the ICAO PBN Manual. The coding guidelines provided here are aligned with the forward/backward conversion rules contained in the AIXM-472 Change Proposal. |
| From point - Designator | Reference to the first point of a route segment The coded designators or name-codes of significant point | RouteSegment.start.EnRouteSegmentPoint.pointChoice_navaidSystem or RouteSegment.start.EnRouteSegmentPoint.pointChoice_fixDesignatedPoint | start: The start EnRouteSegmentPoint for the Route Segment EnRouteSegmentPoint: Indicates a point associated with a defined EnRoute segment. | Note For the mapping the assumption is made that RunwayCentrelinePoint, TouchDownLiftOff, AirportHeliport and Point are not used as "From" point. |
| From point - Reporting | Indication of ATS / MET reporting requirement “compulsory” or “on-request” | RouteSegment.start.EnRouteSegmentPoint.reportingATC | reportingATC: An indicator of the type of position report (e.g., compulsory or on request ) required by an ATC Unit. | |
| To point - Designator | Reference to the second point of a route segment. The coded designators or name-codes of significant point | RouteSegment.end.EnRouteSegmentPoint.pointChoice_navaidSystem or RouteSegment.end.EnRouteSegmentPoint.pointChoice_fixDesignatedPoint | end: The end EnRouteSegmentPoint for the Route Segment | Note For the mapping the assumption is made that RunwayCentrelinePoint, TouchDownLiftOff, AirportHeliport and Point are not used as "To" point. |
| To point - Reporting | Indication of ATS / MET reporting requirement “compulsory” or “on-request” | RouteSegment.end.EnRouteSegmentPoint.reportingATC | see above | |
| Track | Track, VOR radial or magnetic bearing of a route segment | RouteSegment.trueTrack, and/or RouteSegment.reverseTrueTrack, and/or RouteSegment.magneticTrack, and/or RouteSegment.reverseMagneticTrack, | trueTrack: The initial true track. reverseTrueTrack: The reverse initial true track. magneticTrack: The initial magnetic track. reverseMagneticTrack: The reverse initial magnetic track. | PANS-AIM only requires an accuracy to be defined for terminal arrival departure. |
| Length | The geodesic distance between from point and to point | RouteSegment.length, | length: The length of the path (depending on the type of the path) | AIXM 5.1.1 issue_006_RouteSegment.length PANS-AIM requires a accuracy to be specified for the Airway segments length. 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. Info For ENR 3.2 Area navigation routes PANS AIM states
It reads as if 2 distances are required. However, as in the Aeronautical Data Catalogue only one length attribute is defined the geodesic distance, only this distance is considered for the mapping. |
| Upper limit | The upper limit of the route segment | RouteSegment.upperLimit, and RouteSegment.upperLimitReference | upperLimit: The vertical position of the route segment ceiling. upperLimitReference: The reference surface used for the value of the upper limit. For example, Mean Sea Level, Ground, standard pressure, etc.. | |
| Lower limit | The lower limit of the route segment | RouteSegment.lowerLimit, and RouteSegment.lowerLimitReference | lowerLimit: The vertical position of the route segment floor. lowerLimitReference: The reference surface used for the value of the lower limit. For example, Mean Sea Level, Ground, standard pressure, etc.. | |
| MEA | 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. | RouteSegment.minimumEnrouteAltitude, and RouteSegment.annotation.Note.propertyName | minimumEnrouteAltitude: 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. | Note Listed as minimum data item in PANS-AIM chapter 5.3.3.1.1, but according to the Aeronautical Data Catalogue and PANS-AIM Appendix 2 only required for ENR 3.1. AIXM 5.1.1 issue_007_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. AIXM 5.2 Improvement A change proposal (AIXM-428) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which allows coding of multiple MEA values, based on direction and aircraft equipment. The coding guidelines provided here are compatible with the backward conversion rules contained in the AIXM-428 Change Proposal. |
| MOCA | Minimum obstacle clearance altitude (MOCA). The minimum altitude for a defined segment of flight that provides the required obstacle clearance. | RouteSegment.minimumObstacleClearanceAltitude, and RouteSegment.annotation.Note.propertyName | minimumObstacleClearanceAltitude: The minimum altitude for a defined segment of flight that provides the required obstacle clearance. | Note Listed as minimum data item in PANS-AIM chapter 5.3.3.1.1, but according to the Aeronautical Data Catalogue and PANS-AIM Appendix 2 only required for ENR 3.1. 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 flight altitude | Minimum flight altitude | ( RouteSegment.minimumObstacleClearanceAltitude, and RouteSegment.annotation.Note.propertyName ) or ( RouteSegment.minimumEnrouteAltitude, and RouteSegment.annotation.Note.propertyName value equal-to 'minimumEnrouteAltitude' ) | Note According to the Aeronautical Data Catalogue and PANS-AIM Appendix 2 only required for ENR 3.4 Helicopter Routes. Acc. to PANS-AIM Appendix 2: "GEN 3.3.5 Minimum flight altitude" AIXM 5.1.1 issue-009_Minimum flight 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 | |
| Lateral Limits | Lateral limits of route | RouteSegment.widthLeft, and RouteSegment.widthRight | widthLeft: The distance from the centreline of the route segment to the left edge, when considering the direction from the start point to the end point. widthRight: The distance from the centreline of the route segment to the right edge, when considering the direction from the start point to the end point. | Info In PANS-AIM required for only for ENR 3.1 & ENR 3.2 AIXM 5.2 Improvements A change proposal (AIXM-435) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which allows adding new attributes to indicate the cardinal directions for the left/right side of a route segment. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-435 Change Proposal. |
| Direction of cruise levels - Forward | Indication on the direction of the cruising level (even, odd, NIL) from first point to second point of route segment | RouteSegment.availability.RouteAvailability.direction value equal-to ‘FORWARD' .levels.AirspaceLayer.discreteLevelSeries.series | availability: The operational availability of the RouteSegment. direction: A code indicating the direction in which the route segment is considered when a specific usage is described, ie. forward or backward. levels:The level and time block referenced by the usage. discreteLevelSeries: Restriction of the AirspaceLayer to a number of standard IFR or VFR levels. series: A code identifying the column. For example, ODD or EVEN. | |
| Direction of cruise levels - Backward | Indication on the direction of the cruising level (even, odd, NIL) from second point to first point of route segment | RouteSegment.availability.RouteAvailability.direction value equal-to ‘BACKWARD' .levels.AirspaceLayer.discreteLevelSeries.series | see above | |
| Class of airspace | Classification of airspace (A, B, … G) which determines the operating rules, flight requirements, and services provided. According to Annex 11, Appendix 4 | Not applicable: See Remarks | AIXM 5.1.1 issue-012_Class of airspace for Route.Segment In AIXM 5.1(.1) there is no dedicated attribute for class of airspace for the RouteSegment. The class of airspace has to be derived (by a system) from the Airspace the Route segment is located in. Workaround for AIXM 5.1(.1): NA Status AIXM 5.2: A CP was created to provide a corresponding attribute; see CCB AIXM-183 | |
| PBN requirements - Navigation performance requirements | Area navigation based on performance requirements for aircraft operating along an ATS route, on an instrument approach procedure or in a designated airspace requirements The navigation accuracy requirement for each PBN (RNAV or RNP) route segment | RouteSegment.requiredNavigationPerformance | requiredNavigationPerformance: A code indicating the required navigation performance for the route portion | |
| PBN requirements - Sensor requirements | Indication on the sensor requirements including any navigation specification limitations | NA | This data item is defined in the PANS-AIM Aeronautical Data Catalogue but not in ENR 3.3. As such it is considered optional and is not mapped. | |
| RouteSegment.level | level: A code indicating if the route segment is in the upper airspace, the lower airspace or both. | The level of a route segment (Upper, lower or both) is not part of the PANS-AIM chapter 5.3.3.1.1 nor Appendix 1 (Aeronautical Data Catalogue) nor of Appendix 2. However, it is part of the coding guidelines as it is contained in the ARINC 424 Enroute Airways Records (ER); data field is named "Level (LEVEL)". Another reason is that the level attribute is related to several coding rules. |
Additional mapping (Controlling Unit)
Besides the minimum AIP data set items listed in PANS-AIM chapter 5.3.3.1.1, additional data items specified in the following sections of Appendix 2 of PANS-AIM - which are marked with #AIP-DS# - are taken into consideration for the mapping:
- ENR 3.1 Conventional navigation routes
ENR 3.2 Area navigation routes
- ENR 3.3 Other routes
The data items defined for the Controlling unit are mapped to the following main AIXM 5 features and its properties:
%20Route%20segment%20-%20Controlling%20unit%20Mapping.png?version=4&modificationDate=1490978438000&cacheVersion=1&api=v2)
| PANS-AIM | Description (PANS-AIM) | AIXM 5 | Definition (AIXM 5.1.1) | Remarks |
|---|---|---|---|---|
| Controlling unit | ( SearchRescueService.clientRoute.RoutePortion and ) and/or ( InformationService.clientRoute.RoutePortion and ) and/or ( AirTrafficControlService.clientRoute.RoutePortion and AirTrafficControlService.serviceProvider ) | clientRoute: The route portion for which the information/air traffic control/ search and rescue service is provided. serviceProvider: The Unit that provides the Service. | Note: AIXM 5.1(.1) does not provide the possibility to directly link a Unit to a RouteSegment. Instead, specialisations of the abstract Services class may reference a RoutePortion as clientRoute. Such a Service isProvidedBy an Unit. A RoutePortion starts and ends at two different SignificantPoint of the same Route. AIXM 5.2 Change A Change Proposal approved by the AIXM CCB for the next version will support the coding of direct associations from InformationService, AirTrafficControlService, AirTrafficManagementService and SearchAndRescueService towards RouteSegment. See [AIXM-532] Direct associations between certain services and RouteSegment For the AIP data set the AirTrafficManagementService class is not relevant as it is not an ATS. | |
| Controlling unit - Name | Name of the unit providing the service | ( InformationService.serviceProvider, and/or AirTrafficControlService.serviceProvider, ) and Unit.name | name: The full textual name of a unit. This name must be established according to the rules specified by International Civil Aviation Organisation (ICAO), and specifically in the official language of the country, transposed into the Latin Alphabet where necessary. | |
| Controlling unit - Channel | Operating channel / frequency of controlling unit | ( AirTrafficControlService.radioCommunication, and/or InformationService.radioCommunication, and/or SearchRescueService.radioCommunication ) and ( RadioCommunicationChannel.frequencyTransmission, and/or RadioCommunicationChannel.frequencyReception, and/or RadioCommunicationChannel.channel ) | radioCommunication: The radio frequency on which the service is provided. frequencyTransmission: The value of the transmission frequency. frequencyReception: The value of the reception frequency. channel The identifier of the radio channel on which the communication takes place. | |
| Controlling unit - Logon address | A specified code used for data link logon to the controlling ATS unit | TBD | AIXM 5.1(.1) issue_10_Logon address Currently, there are several options to encode datalink information in AIXM 5. For TrafficSeperationService two dedicated attributes are provided: dataLinkEnable and dataLinkChannel. For InformationService only one attribute dataLink is provided. In addition it is possible to encode datalink information for an Unit via the object OnlineContact using the attributes linkage, network and protocol. Workaround: Not defined yet, Waiting for AIXM CCB Status: To be reported to CCB |
Additional mapping (Change Over Point)
Besides the minimum AIP data set items listed in PANS-AIM chapter 5.3.3.1.1, additional data items specified in the following sections of Appendix 2 of PANS-AIM - which are marked with #AIP-DS# - are taken into consideration for the mapping:
- ENR 3.1 Lower ATS routes,
- ENR 3.2 Upper ATS routes,
- ENR 3.4 Helicopter routes,
2) ... changeover points;
The Change over point data item is mapped to the following main AIXM 5 features and its properties:
%20Route%20segment%20-%20Change%20Over%20Point%20Mapping.png?version=2&modificationDate=1490977612000&cacheVersion=1&api=v2)
| PANS-AIM | Description (PANS-AIM) | AIXM 5 | Definition (AIXM 5.1.1) | Remarks |
|---|---|---|---|---|
| Change over point | The point at which an aircraft navigating on an ATS route segment defined by reference to very high frequency omnidirectional radio ranges is expected to transfer its primary navigational reference from the facility behind the aircraft to the next facility ahead of the aircraft. | ChangeOverPoint.distance, ChangeOverPoint.applicableRoutePortion ChangeOverPoint.isLocatedAt | distance The distance from the start of the route portion to position of the change over point. applicableRoutePortion: The Route Portion that the change over point applies to. location: Location of the change over point. | Info In PANS-AIM required for ENR 3.1, 3.2 & 3.4 in case of VOR radials. Note: In AIXM the ChangeOverPoint does not reference a RouteSegment but a RoutePortion. A RoutePortion starts and ends at a SignificantPoint. In order to relate a Change Over Point to a Route Portion, the Route Portion concerned has also to be defined in the AIP data set. |