| Panel | ||
|---|---|---|
| ||
|
...
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, ...
...
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
...
.
...
RouteSegment.start.EnRouteSegmentPoint.reportingATC is mandatory.
...
MOCA is mandatory for ENR 3.1 Lower ATS Routes
...
AIXM-5.1_RULE-F07AB
(Rule does not take into account UNL)
...
RouteSegment.upperLimit shall not be equal-to 'FLOOR' or 'CELLING' or 'GND'.
...
AIXM-5.1_RULE-F07AC
(Rule does not take into account GND)
...
AIXM-5.1_RULE-F07A9
(Rule does not take into account UNL)
...
AIXM-5.1_RULE-F07AA
(Rule does not take into account UNL)
...
Each RouteSegment shall have assigned routeFormed value.
...
Two consecutive route segments (of the same Route) should have vertical limits that, if not overlapping, should not be further away than 1000 FT. For example, if segment 1 is FL245 to FL295 and segment 2 is FL310 to FL490, (this rule will need to be adjusted based on operational experience).
...
The angle between two consecutive segments of the same route cannot exceed 90 degrees.
...
TBD
This rule is based on the areas of responsibility defined in EAD. Shall there be a similar rules for the AIP data set based e.g.on FIR/UIR?
...
According to the rule definition the rule is violated, because four significant points "KPT", "TGO", "KRH" and "ECCHO" are used only once, either as start or end point of a route segment.
...
In the given example the rule is violated, because route segment "ECCHO - ANEKI" is described in the opposite order of the adjacent segments.
...
According to the rule definition the rule is violated, because ANEKI appears on three route segments.
Subsequently this results in multiple branches; "ANEKI - ECCHO" and ANEKI - RUDUS".
...
The position of the SignificantPoint used as the beginning of the RouteSegment must be separated by at least 30m (1 sec of arc) from the position of the SignificantPoint used as the end of the RouteSegment.
...
The value of EnRouteSegmentPoint.reportingATC for RouteSegment.start and RouteSegment.end of any two consecutive segments of the same route must be consistent.
...
The difference between length and the calculated length of the related RouteSegment cannot exceed 5 KM.
...
PANS-AIM requires an accuracy of 1/10 KM. Shall the rule be changed accordingly?
...
The difference between Initial trueTrack and the calculated initial true track of the related RouteSegment cannot exceed 2 degrees.
The difference between reverseTrueTrack and the calculated reverse initial true track of the related RouteSegment cannot exceed 2 degrees.
...
Coding Examples
The figure below gives a simple example of the encoding of the route segment from "DINKI" to "LNO".
...