PREDEFINED_LVL [Specified cruising level]
A specified cruising level, part of a column within a table of discrete cruising levels used by General Air Traffic.
Attributes
VAL_DIST_VER [Level value] mandatory
The value of the cruising level.
Domain: VAL_DIST_VER
PREDEFINED_LVL_COLUMN [Column of a table of cruising level]
A column of consecutive cruising levels within a predefined level table.
Attributes
CODE_ID [Identification] mandatory
A code identifying the column.
For example, east or west.
Domain: CODE_ID_LVL_CLMN
TXT_RMK [Remark] optional
Domain: TXT_RMK
PREDEFINED_LVL_TABLE [Table of cruising level]
A table of consecutive cruising levels described under vertical separation criteria limited by an upper and lower level and used by General Air Traffic.
Attributes
CODE_ID [Identification] mandatory
A code identifying the table of discrete cruising levels.
For example, ICAO IFR, ICAO VFR, ICAO IFR RVSM, etc.
Domain: CODE_ID_LVL_TBL
TXT_DESCR [Description] optional
The textual description of the cruising levels table.
Domain: TXT_DESCR
CODE_DIST_VER [Reference for the vertical distance] mandatory
A code indicating the convention used to measure the cruising levels that are listed in the table.
For example, Flight Level (in both feet and metres - cf. UOM_DIST_VERT), Altitude above MSL (QNH), Altitude above GND (QFE), Elevation, Height, etc..
Domain: CODE_DIST_VER
UOM_DIST_VER [Unit of measurement [vertical distance]] mandatory
The unit of measurement used to express the cruising levels that are listed in the table.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
TXT_RMK [Remark] optional
Domain: TXT_RMK
PROCEDURE_LEG [Procedure leg]
A segment of a SID, STAR, Instrument Approach Procedure or Holding Procedure with a specific type of flight path and a specific type of termination of flight path.
Notes:
This concept permits coding of SID, STAR and Instrument Approach Procedures without proliferating the number of designated points required to support such procedures and has been inspired by the ARINC Specification 424 (Attachment 5, Path and Terminator). As opposed to ARINC, no standard assumptions on the performance of aircraft are made, excepting those made in ICAO DOC 8168 - OPS/611 (Aircraft Operations).
Attributes
NO_SEQ [Sequence number] mandatory
A number in sequence indicating the order in which the procedure legs must be considered when describing the procedure.
Domain: NO_SEQ
CODE_PHASE [Phase] optional
A code indicating the phase of a SID, STAR or IAP the procedure leg is part of, according to ARINC 424, 5.7 "Route Type".
Notes:
This attribute is optional and together with the CODE_TYPE_ROUTE attribute of the SID, STAR or IAP gives the value of the RT Type field in the ARINC 424 Specification (item 5.7).
Rules:
  1. This attribute is not applicable for Holding Procedures.
Domain: CODE_PHASE_PROC
CODE_TYPE [Type] mandatory
A code defining a specific type of flight path and a specific type of termination of that flight path.

A comprehensive description of the 'path and terminator' concept is given in ARINC Specification 424, Attachment 5, Path and Terminator. The ARINC Specification sets forth recommended standards for the preparation of airborne navigation system data tapes produced for FMS equipped aircraft. Consequently, the Path and Terminator concept presented in Attachment 5 does not support the codification of SIDs, STARs and IAPs in a generic way as they are designed according to PANS-OPS. Instead ARINC establishes specific values for speed (210 knots), bank angle (25 degrees), climb rate (500 ft/NM) - typical values for most of the aircraft used by the commercial aviation companies - and does not allow the use of timing for reversal procedures descriptions.

There are two possible solutions :

1) To modify the ARINC Path and Terminator concept as necessary to accommodate the representation of SIDs, STARs and IAPs in a more generic way, without establishing specific values (for speed, climb
rate, bank angle, etc.) other than those stated in the ICAO PANS-OPS document.
Advantages:
- a more appropriate solution for a Data Model which needs to reflect as closely as possible the ICAO Documentation.
Disadvantages:
- additional work, both for the Model (rules) and for the mapping between the Model and the ARINC format (assuming that data exchange in ARINC format is a necessity for any aeronautical database) .

2) To use the Path and Termination concept 'as is', fully respecting Attachment 5 of the ARINC Specification 424.
Advantages:
- the chance of benefiting from the entire 'know-how' associated with this internationally agreed technical specification.
Disadvantages:
- the limitations highlighted above.

Bearing in mind that the objective is to follow the ICAO documents as closely as possible and in this context, to allow the representation of flight procedures as published by the States, the first solution has been chosen. In fact, the ARINC Path and Terminator Concept has been very slightly modified for the purposes of this model.

Although we agree with the ARINC idea that procedures should be designed to permit FMS equipped aircraft to fly tracks instead of procedural headings, for the time being we must allow the representation of these procedures (especially reversal procedures) as they are published by the States. This is the explanation of the differences between the allowable values for this attribute and the ARINC leg types.
Rules:
  1. For each value of CODE_TYPE, a list of mandatory attributes for the PROCEDURE_LEG may be found in item 1.5, Attachment 5, ARINC 424 Specification.
Domain: CODE_TYPE_PROC_PATH
VAL_COURSE [Course angle] optional
The value of the course angle in degrees.
Domain: VAL_ANGLE_BRG
CODE_TYPE_COURSE [Course type] optional
A code indicating the type of course to be observed.
For example, true track, magnetic track, heading, VOR radial, true bearing, magnetic bearing.
Domain: CODE_TYPE_COURSE
CODE_DIR_TURN [Direction of the turn] optional
A code indicating the direction of the turn.
Domain: CODE_DIR_TURN
CODE_TURN_VALID [Fly-by] optional
A code indicating how the CODE_DIR_TURN should be interpreted. This attribute is a yes or no option. If the value of this attribute is 'Y', the turn is required prior to capturing the path specified by the CODE_TYPE. In this situation, the associated fix (if any) is a fly-by waypoint. If CODE_TURN_VALID='N' or it is not specified, then the associated fix is a 'fly-over' waypoint.
Domain: CODE_YES_NO
CODE_DESCR_DIST_VER [Interpretation of vertical distance] optional
A code indicating how the altitude attributes of a procedure leg should be interpreted: 'at' the lower altitude, 'at or above' the lower altitude, 'at or below' the lower altitude or 'between' the altitudes specified in the attributes VAL_DIST_VER_UPPER, VAL_DIST_VER_LOWER and the associated ones.
Rules:
  1. If CODE_DESCR_DIST_VER = 'L', 'LA' or 'B' then VAL_DIST_VER_LOWER is mandatory.
  2. If CODE_DESCR_DIST_VER = 'BH' or 'B' then VAL_DIST_VER_UPPER is mandatory.
Domain: CODE_DESCR_DIST_VER
CODE_DIST_VER_UPPER [Reference for upper limit] optional
A code indicating the base parameter for the vertical datum used to express the upper altitude.
Domain: CODE_DIST_VER
VAL_DIST_VER_UPPER [Upper limit] optional
The value of the upper altitude.
Rules:
  1. If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory.
Domain: VAL_DIST_VER
UOM_DIST_VER_UPPER [Unit of measurement [upper limit]] optional
The unit of measurement for the upper altitude.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
CODE_DIST_VER_LOWER [Reference for lower limit] optional
A code indicating the base parameter for the vertical datum used to express the lower altitude.
Domain: CODE_DIST_VER
VAL_DIST_VER_LOWER [Lower limit] optional
The value of the lower altitude.
Rules:
  1. If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory.
  2. When translated to use the same unit of measurement and the same vertical reference, VAL_DIST_VER_LOWER must be lower than VAL_DIST_VER_UPPER.
Domain: VAL_DIST_VER
UOM_DIST_VER_LOWER [Unit of measurement [lower limit]] optional
The unit of measurement of the lower altitude.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
VAL_VER_ANGLE [Vertical climb angle] optional
The value of the vertical climb angle of the aircraft on the procedure leg. A negative value means descent.
Rules:
  1. VAL_VER_ANGLE should have a value between -10 and +50 degrees.
Domain: VAL_ANGLE
VAL_SPEED_LIMIT [Speed limit] optional
The value of the speed limit on the procedure leg.
Rules:
  1. If VAL_SPEED_LIMIT is specified, then UOM_SPEED and CODE_SPEED_REF are mandatory.
Domain: VAL_SPEED
UOM_SPEED [Unit of measurement [speed limit]] optional
Unit of measurement of the speed limit.
Domain: UOM_SPEED
CODE_SPEED_REF [Reference system for speed value] optional
A code indicating the reference system for a speed value.
For example, IAS, TAS or GS (ground speed).
Domain: CODE_SPEED_REF
VAL_DIST [Declared length] optional
The length of the procedure leg.
Notes:
1) To simplify the mapping with ARINC 424, for certain values of CODE_TYPE, VAL_DIST is used to represent a DME distance rather than the length of the procedure leg.
2) The meaning of this value depends on the value of the CODE_TYPE, as described in ARINC 424, Attachment 5, 1.5 Leg Data Fields.
Rules:
  1. If VAL_DIST is specified, then UOM_DIST_HORZ is mandatory.
Domain: VAL_DIST_HORZ
VAL_DUR [Declared duration] optional
The duration of the procedure leg.
Rules:
  1. If VAL_DUR is specified, then UOM_DUR is mandatory.
Domain: VAL_DUR
UOM_DUR [Unit of measurement [time value]] optional
The unit of measurement for the time value.
Domain: UOM_DUR
VAL_THETA [Theta] optional
A magnetic bearing or radial from the recommended navaid associated with the PROCEDURE_LEG.
Notes:
1) To simplify the mapping with ARINC 424, VAL_THETA is used to represent a radial/bearing from a navaid to the significant point associated with the procedure leg, instead of an ANGLE_INDICATION related to that SIGNIFICANT_POINT.
2) The meaning of this value depends on the value of the CODE_TYPE, as described in ARINC 424, Attachment 5, 1.5 Leg Data Fields;
Domain: VAL_ANGLE_BRG
VAL_RHO [Rho] optional
A distance from the recommended navaid associated with the PROCEDURE_LEG.
Notes:
1) To simplify the mapping with ARINC 424, VAL_RHO is used to represent a distance from a navaid to the significant point associated with the procedure leg, instead of a DISTANCE_INDICATION related to that SIGNIFICANT_POINT;
2) The meaning of this value depends on the value of the CODE_TYPE, as described in ARINC 424, Attachment 5, 1.5 Leg Data Fields.
Rules:
  1. If VAL_RHO is specified, then UOM_DIST_HORZ is mandatory.
Domain: VAL_DIST_HORZ
VAL_BANK_ANGLE [Recommended bank angle] optional
The recommended bank angle of the aircraft on the turn.
Rules:
  1. VAL_BANK_ANGLE should have a value between 5 and 35 degrees.
Domain: VAL_ANGLE
UOM_DIST_HORZ [Unit of measurement [horizontal distance]] optional
The unit of measurement for the length of the procedure leg and the radius.
Domain: UOM_DIST_HORZ
CODE_REP_ATC [ATC reporting] optional
A code indicating the type of position report required by an ATC Unit.
For example, 'compulsory' or 'on request' reporting point.
Domain: CODE_REP_ATC
CODE_ROLE_FIX [Role of fix (IAP)] optional
A code indicating the role of the fix associated with the procedure leg within the instrument approach procedure. Examples: initial approach fix, final approach fix, missed approach point, etc.
Rules:
  1. This attribute may be specified only for a procedure leg that is 'part of a IAP'.
  2. This attribute may be specified only if there is an associated fix for the procedure leg, through the relationship 'using as fix one and only one SIGNIFICANT_POINT'.
Domain: CODE_IAP_FIX
TXT_RMK [Remark] optional
Domain: TXT_RMK
RTE_PORTION [Route portion]
A convenient way of grouping together two or more consecutive segments of the same route, as necessary to formulate traffic flow restrictions which concerns all those segments.
RTE_SEG [Route segment]
(ICAO) A portion of a route to be flown usually without an intermediate stop, as defined by two consecutive significant points.
Rules:
  1. At the border (defined as a buffer area of 2 km on each side) between two areas of responsibility , route segments should be continued by route segments of the same or another EN_ROUTE_RTE.
  2. CODE_REP_ATC_START and CODE_REP_ATC_END of any two consecutive segments of the same route must be consistent.
  3. The angle between two consecutive segments of the same route cannot exceed 90 degrees.
  4. Two consecutive route segments (of the same EN_ROUTE_RTE) 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, than a warning message should be triggered. (this rule will need to be adjusted based on operational experience.
Attributes
CODE_TYPE [Type] mandatory
The type of route from a navigation point of view
(for example, conventional, RNAV, etc.).
Rules:
  1. If the first letter of the TXT_DESIG of the related EN_ROUTE_RTE is 'S', then CODE_TYPE must have the value 'SSN' (see ICAO Annex 11, Appendix 1, item 2.3).
  2. If CODE_TYPE = 'ADV' (advisory), there has to exist a related (via the RTE_SEG) SERVICE_ON_RTE_SEG with the CODE_TYPE of the related SERVICE having the values 'ADVS' or 'EFAS (advisory).
Domain: CODE_TYPE_RTE
CODE_RNP [Required navigation performance] optional
A code indicating the required navigation performance for the route segment.
Domain: CODE_RNP
CODE_LVL [Level] optional
A code indicating if the route segment is in the upper airspace, in the lower airspace or in both.
Domain: CODE_LVL
CODE_CLASS_ACFT [Class of aircraft] optional
A code indicating the class of aircraft that may use the route segment.
(For example, jet, heli, prop).
Rules:
  1. If the first letter of the TXT_DESIG of the related EN_ROUTE_RTE is 'K', then CODE_CLASS_ACFT must have one of the values 'H', 'HP' or 'ALL' (see ICAO Annex 11, Appendix 1, item 2.3).
Domain: CODE_CLASS_ACFT
CODE_INTL [Route classification] optional
A code indicating whether a route segment is international or domestic.
Domain: CODE_INTL_RTE
CODE_TYPE_FLT_RULE [Flight rules observation] optional
A code indicating the flight rules to be observed by aircraft.
For example, VFR and/or IFR.
Domain: CODE_TYPE_FLT_RULE
CODE_CIV [Civil / military status of route] optional
A code indicating the civil/military status of the route segment.
Domain: CODE_CIV_RTE
VAL_DIST_VER_UPPER [Upper limit] optional
The numerical value of the upper limit.
Rules:
  1. If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory.
Domain: VAL_DIST_VER
UOM_DIST_VER_UPPER [Unit of measurement [upper limit]] optional
The unit of measurement expressing the upper limit.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
CODE_DIST_VER_UPPER [Reference for upper limit] optional
A code expressing the convention used to calculate the upper limit.
For example, Flight Level (in both feet and metres - cf. UOM_DIST_VERT), Altitude above MSL (QNH), Altitude above GND (QFE), Elevation, Height, etc....
Domain: CODE_DIST_VER
VAL_DIST_VER_LOWER [Lower limit] optional
The numerical value of the lower limit.
Rules:
  1. If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory.
  2. When translated to use the same unit of measurement and the same vertical reference, VAL_DIST_VER_LOWER must be lower than or equal to VAL_DIST_VER_UPPER.
Domain: VAL_DIST_VER
UOM_DIST_VER_LOWER [Unit of measurement [lower limit]] optional
The unit of measurement expressing the lower limit.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
CODE_DIST_VER_LOWER [Reference for lower limit] optional
A code expressing the convention used to calculate the lower limit.
For example, Flight Level (in both feet and metres - cf. UOM_DIST_VERT), Altitude above MSL (QNH), Altitude above GND (QFE), Elevation, Height, etc....
Domain: CODE_DIST_VER
VAL_DIST_VER_MNM [Minimum limit] optional
The numerical value of the minimum limit.
Rules:
  1. If VAL_DIST_VER_MNM is specified, then UOM_DIST_VER_MNM and CODE_DIST_VER_MNM are mandatory.
Domain: VAL_DIST_VER
UOM_DIST_VER_MNM [Unit of measurement [minimum limit]] optional
The unit of measurement expressing the minimum limit.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_MNM must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
CODE_DIST_VER_MNM [Reference for minimum limit] optional
A code expressing the convention used to calculate the minimum limit.
For example, Flight Level (in both feet and metres - cf. UOM_DIST_VERT), Altitude above MSL (QNH), Altitude above GND (QFE), Elevation, Height, etc....
Domain: CODE_DIST_VER
VAL_DIST_VER_LOWER_OVRDE [Lower limit override] optional
The numerical value of the lower override limit.
Rules:
  1. If VAL_DIST_VER_LOWER_OVRDE is specified, then UOM_DIST_VER_LOWER_OVRDE and CODE_DIST_VER_LOWER_OVRDE are mandatory.
Domain: VAL_DIST_VER
UOM_DIST_VER_LOWER_OVRDE [Unit of measurement [lower limit override]] optional
The unit of measurement used to express the lower override limit.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER_OVRDE must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
CODE_DIST_VER_LOWER_OVRDE [Reference for lower limit override] optional
A code expressing the convention used to calculate the lower override limit.
For example, Flight Level (in both feet and metres - cf. UOM_DIST_VERT), Altitude above MSL (QNH), Altitude above GND (QFE), Elevation, Height, etc....
Rules:
  1. The only allowable value for CODE_DIST_VER_LOWER_OVRDE is 'HEI' (height above ground).
Domain: CODE_DIST_VER
VAL_WID [Width] optional
The width of the route segment.
Rules:
  1. If VAL_WID is specified, then UOM_WID is mandatory.
  2. VAL_WID must have a value between 1 (NM) and 20 (NM).
Domain: VAL_DIST_HORZ
UOM_WID [Unit of measurement [width]] optional
The unit of measurement used to express the route segment width (for example, NM, KM).
Domain: UOM_DIST_HORZ
CODE_REP_ATC_START [ATC report at start point] optional
A code indicating the type of position report required by an ATC Unit for the start point of the route segment.
For example, 'compulsory', 'on request' reporting point or 'no report' point.
Domain: CODE_REP_ATC
CODE_REP_ATC_END [ATC report at end point] optional
A code indicating the type of position report required by an ATC Unit for the end point of the route segment.
For example, 'compulsory', 'on request' reporting point or 'no report' point.
Domain: CODE_REP_ATC
CODE_RVSM_START [RVSM role of start point] optional
A code indicating that start point of the route segment has a specific role in the RVSM context.
Domain: CODE_RVSM_POINT
CODE_RVSM_END [RVSM role of end point] optional
A code indicating that end point of the route segment has a specific role in the RVSM context.
Domain: CODE_RVSM_POINT
CODE_TYPE_PATH [Type of segment path] optional
The type of segment path to be flown between the two points of the route segment, as published by the State, if any.
For example, great circle, rhumbline, geodesic line, etc.
Domain: CODE_TYPE_SEG_PATH
VAL_TRUE_TRACK [Initial true track] optional
The initial true track, as published by the State.
Rules:
  1. The difference between the VAL_TRUE_TRACK in the RTE_SEG and the (calculated) VAL_TRUE_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 2 (degrees).
Domain: VAL_ANGLE_BRG
VAL_MAG_TRACK [Initial magnetic track] optional
The initial magnetic track, as published by the State.
Rules:
  1. The difference between the VAL_MAG_TRACK in the RTE_SEG and the (calculated) VAL_MAG_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 3 (degrees).
Domain: VAL_ANGLE_BRG
VAL_REVERS_TRUE_TRACK [Reverse initial true track] optional
The reverse initial true track, as published by the State.
Rules:
  1. The difference between the VAL_REVERS_TRUE_TRACK in the RTE_SEG and the (calculated) VAL_REVERS_TRUE_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 2 (degrees).
Domain: VAL_ANGLE_BRG
VAL_REVERS_MAG_TRACK [Reverse initial magnetic track] optional
The reverse initial magnetic track, as published by the State.
Rules:
  1. The difference between the VAL_REVERS_MAG_TRACK in the RTE_SEG and the (calculated) VAL_REVERS_MAG_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 3 (degrees).
Domain: VAL_ANGLE_BRG
VAL_LEN [Length] optional
The length of the path (depending on the type of the path), as published by the State.
Rules:
  1. The difference between the VAL_LEN in the RTE_SEG and the (calculated) VAL_LEN of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 5 (KM).
  2. If VAL_LEN is specified, then UOM_DIST is mandatory.
Domain: VAL_DIST_HORZ
VAL_COP_DIST [Distance from the start to the change over point] optional
The distance from the start point to the change over point, if provided, for a VOR-defined segment.
Notes:
If the change over point is the start point, this distance is assumed to be 0. If the change-over point is the end point, this distance is assumed to be the entire length of the segment.
Rules:
  1. VAL_COP_DIST must be lower than VAL_LEN.
Domain: VAL_DIST_HORZ
UOM_DIST [Unit of measurement [horizontal distance]] optional
The unit of measurement used to express the length of the segment and the change-over point distance.
Domain: UOM_DIST_HORZ
TXT_RMK [Remark] optional
Domain: TXT_RMK
RTE_SEG_USE [Route segment usage condition]
The usage of a particular route segment with regard to direction, timetable, cruising levels and whether or not it is subject to Flexible Use of Airspace (FUA).
Rules:
  1. For every possible combination of level and time there may be not more than one entry defined for one direction in the RTE_SEG_USE entity
    In other words: We define a Cartesian co-ordinate system with the time of the week (as specified by relation 'available according to TIMETABLE') on the x-axis and the level (as specified in the RTE_SEG_USE_LVL entity) on the y-axis. Now all entries of a specific route segment and direction (CODE_DIR) are drawn in this co-ordinate system using all their levels and timesheets. Level bands result in rectangles and single levels and level series result in lines (zero extension on y-axis). In the resulting image no figure (rectangle, line) may overlap with another figure.
Attributes
CODE_RTE_AVBL [Availability of the route segment] mandatory
A code indicating the availability of the route segment whether covered by the Flexible Use of Airspace concept or outside this context.
Ex: NON-FUA, CDR1, SPECIAL, etc..
Notes:
A SPECIAL value is needed for this attribute also as long as 'special' types of routes exist.
Examples:
- routes which are closed during some time periods, but still may be used for landings on a specified aerodrome;
-'routes' on which flights may be performed below the minimum level of the route in order to arrive at a specified aerodrome.
- ...
Domain: CODE_RTE_AVBL
NO_SEQ [Sequence number] mandatory
A number in sequence applied to each 'route segment usage' having the same value for the CODE_RTE_AVBL.
For example, a route might be used:
- as CDR 1 from FL250 to FL330 from MON till FRI and
- as CDR 1 from FL 270 to FL 490 on SAT and SUN;
This situation will be described using two occurrences of the Route Segment Usage entity, both having the CODE_RTE_AVBL = 'CDR 1', but with two different sequence numbers.
Domain: NO_SEQ
CODE_DIR [Direction] mandatory
A code indicating the direction in which the route segment is considered when a specific usage is described, ie. forward or backward.
Domain: CODE_DIR
TXT_RMK [Remark] optional
Domain: TXT_RMK
RTE_SEG_USE_LVL [Level associated with a route segment usage]
A single level, a level band or series of levels associated with a route segment usage.
'series of levels' = a set of consecutive levels, part of a column within a table of predefined cruising levels, prescribed under vertical separation criteria and limited by an upper and lower level.
'level band' = band of airspace limited by two specific cruising altitudes/levels within which 'free vertical movement' may be permitted.
An entity containing all the attributes that may vary over time.
Notes:
1) single levels are represented using the VAL_DIST_VER_LOWER, UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER attributes; single levels are not related to any PREDEFINED LEVEL COLUMN.

2) level bands are represented using the VAL_DIST_VER_LOWER, UOM_DIST_VER_LOWER, CODE_DIST_VER_LOWER attributes to specify the lowest cruising level/altitude and the VAL_DIST_VER_UPPER, UOM_DIST_VER_UPPER, CODE_DIST_VER_UPPER attributes to specify the uppermost cruising level/altitude; level bands are not related to any PREDEFINED LEVEL COLUMN.

3) series of level bands are represented using the VAL_DIST_VER_LOWER, UOM_DIST_VER_LOWER, CODE_DIST_VER_LOWER attributes to specify the lowest cruising level/altitude and the VAL_DIST_VER_UPPER, UOM_DIST_VER_UPPER, CODE_DIST_VER_UPPER attributes to specify the uppermost cruising level/altitude; for series of levels it is mandatory to have a PREDEFINED LEVEL COLUMN related.
Attributes
VAL_DIST_VER_LOWER [Lower limit] optional
The value of the lowermost cruising level.
Rules:
  1. If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory.
  2. When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), VAL_DIST_VER_LOWER must be higher than or equal to VAL_DIST_VER_LOWER and lower than or equal to VAL_DIST_VER_UPPER of the related RTE_SEG.
Domain: VAL_DIST_VER
UOM_DIST_VER_LOWER [Unit of measurement [lower limit]] optional
The unit of measurement used to express the lowermost cruising level.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
CODE_DIST_VER_LOWER [Reference for lower limit] optional
A code indicating the convention used to measure the lowermost cruising level.
For example, flight level (in both feet and metres - cf. UOM_DIST_VER), altitudes above MSL (QNH), altitude above GND (QFE), elevation, height etc.
Domain: CODE_DIST_VER
VAL_DIST_VER_UPPER [Upper limit] optional
The value of the uppermost cruising level.
Notes:
1) if the type of levels described is not 'single level', this attribute is mandatory;
Rules:
  1. If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory.
  2. When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), VAL_DIST_VER_UPPER must be higher than or equal to VAL_DIST_VER_LOWER and lower than or equal to VAL_DIST_VER_UPPER of the related RTE_SEG.
  3. When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), the value of VAL_DIST_VER_UPPER must be higher than or equal to the value of VAL_DIST_VER_LOWER.
Domain: VAL_DIST_VER
UOM_DIST_VER_UPPER [Unit of measurement [upper limit]] optional
The unit of measurement used to express the uppermost cruising level.
Rules:
  1. If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure)..
Domain: UOM_DIST_VER
CODE_DIST_VER_UPPER [Reference for upper limit] optional
A code indicating the convention used to measure the uppermost cruising level.
For example, flight level (in both feet and metres - cf. UOM_DIST_VER), altitudes above MSL (QNH), altitude above GND (QFE), elevation, height etc.
Domain: CODE_DIST_VER
RWY [Runway [RWY]]
(ICAO) A defined rectangular area on a land aerodrome prepared for the landing and take-off of aircraft.
Notes:
This entity describes the physical area of the runway. The associated characteristics of the two approach and take-off directions are described in another entity.
Attributes
TXT_DESIG [Designator] mandatory
The full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport which has more than one.
E.g. 09/27, 02R/20L, RWY 1.
Domain: TXT_DESIG
VAL_LEN [Length] optional
The value of the physical length of the runway.
Rules:
  1. If this value is specified, then UOM_DIM_RWY is mandatory.
Domain: VAL_DIST_HORZ
VAL_WID [Width] optional
The value of the physical width of the runway.
Rules:
  1. If this value is specified, then UOM_DIM_RWY is mandatory.
Domain: VAL_DIST_HORZ
UOM_DIM_RWY [Unit of measurement [horizontal dimension]] optional
The unit of measurement for the horizontal dimensions of the runway.
Domain: UOM_DIST_HORZ
[CODE_COMPOSITION] DEPRECATED-4.5 [Surface composition] optional
A code indicating the composition of a runway surface.
For example, asphalt, concrete etc..
Rules:
  1. If CODE_COMPOSITION is 'WATER', then CODE_COND_SFC, CODE_STRENGTH and TXT_DESCR_STRENGTH may not be specified.
Domain: CODE_COMPOSITION_SFC
[CODE_COND_SFC] DEPRECATED-4.5 [Surface condition] optional
A code indicating the condition of a runway surface.
Domain: CODE_COND_SFC
[CODE_STRENGTH] DEPRECATED-4.5 [Surface strength method] optional
A code indicating the method used to measure the surface strength.
Rules:
  1. If CODE_STRENGTH has the value 'PCN', then the value of TXT_DESCR_STRENGTH shall conform to the rules for the PCN-ACN method, as specified in ICAO Annex 14, item 2.2.6.
    Examples:
    - '80/R/B/W/T'
    - '40/ F/ B /0.80 MPa /T'
    - '50/F/A/Y/U Note: - Composite construction'
    - '50/F/A/Y/U Note: - The reported PCN is subject to a B747-400 all-up mass limitation of 390 000 kg.'
    If no method is indicated in the 'Surface strength method' field, then there are no restrictions with regard to the content of this field. For example: 'LCN 72, h= 56'.
Domain: [CODE_STRENGTH_SFC]
[TXT_DESCR_STRENGTH] DEPRECATED-4.5 [Surface strength] optional
The surface strength, in character format, according to the value of the CODE_STRENGTH attribute.
For example, 80/R/B/W/T for a PCN type value.
Domain: TXT_DESCR
VAL_LEN_STRIP [Physical length of the strip] optional
The value of the physical length of the strip.
Rules:
  1. VAL_LEN_STRIP must exceed VAL_LEN with at least 60 M.
  2. If this value is specified, then UOM_DIM_STRIP is mandatory.
Domain: VAL_DIST_HORZ
VAL_WID_STRIP [Physical width of the strip] optional
The value of the physical width of the strip.
Rules:
  1. VAL_WID_STRIP must exceed VAL_WID.
  2. VAL_WID_STRIP must be at least 150 M.
  3. If this value is specified, then UOM_DIM_STRIP is mandatory.
Domain: VAL_DIST_HORZ
VAL_LEN_OFFSET [Longitudinal offset of the strip] optional
A value specifying the longitudinal offset of the strip, when it is not symmetrically extended beyond the two runway ends.
Notes:
The longitudinal offset defines the distance along the centreline from the middle of the runway centreline towards the middle of the strip centreline. An offset in the direction defined from the threshold with the lower runway direction designation number towards the opposite runway threshold is indicated by a positive value. An offset in the opposite sense is indicated by a negative value.

Example: a runway oriented 09/27 has a strip that is extending 120 m before the threshold of the runway direction 09 and only 100 m before the threshold of the runway direction 27. The value of the longitudinal offset will be -10 m.
Rules:
  1. If this value is specified, then UOM_DIM_STRIP is mandatory.
Domain: VAL_OFFSET
VAL_WID_OFFSET [Lateral offset of the strip] optional
A value specifying the lateral offset of the strip, when it is not symmetrically extended beyond the two runway edges.
Notes:
The lateral offset defines the distance from the runway centreline to the strip centreline in direction perpendicular to the runway centreline. An offset to the right, based on the direction defined from the threshold with the lower runway direction designation number towards the opposite runway threshold, is indicated by a positive value. An offset to the left is indicated by a negative value.

Example: a runway oriented 09/27 has a strip that is extending 150 m to the right of the runway direction 09 and 300 m to the left of the same runway direction. The value of the lateral offset will be -75 m.
Rules:
  1. If this value is specified, then UOM_DIM_STRIP is mandatory.
Domain: VAL_OFFSET
UOM_DIM_STRIP [Unit of measurement [strip dimension]] optional
The unit of measurement for the strip dimensions.
Domain: UOM_DIST_HORZ
CODE_STS [Operational status] optional
A code indicating the operational status of a runway.
For example, serviceable, unserviceable, closed, work in progress, etc.
Domain: CODE_STS_SFC
TXT_PROFILE [Profile description] optional
A textual description of the RWY profile.
Notes:
The profile shall be described in the direction defined from the threshold with the lower runway direction designation number towards the opposite runway threshold.
Domain: TXT_DESCR
TXT_MARKING [Marking] optional
A textual description of the RWY marking.
Domain: TXT_DESCR
TXT_RMK [Remark] optional
Domain: TXT_RMK
RWY_CLINE_POINT [Position on the centre line of a RWY]
A position on the centre line of a runway.
Notes:

Rules:
  1. The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP.
  2. The points on the centre line of one Runway must define a straight line (with a tolerance of 50 M).
  3. The distance between the first and the last RWY_CLINE_POINT associated to the same RWY cannot exceed 10 KM.
Attributes
GEO_LAT [Latitude] mandatory
The latitude of the position of the centre line point.
Domain: GEO_LAT
GEO_LONG [Longitude] mandatory
The longitude of the position of the centre line point.
Domain: GEO_LONG
CODE_DATUM [Datum] mandatory
A code indicating the geodetic datum in which the geographical co-ordinates are expressed.
Rules:
  1. All geographical coordinates should be expressed in the WGS 84 system.
Domain: CODE_DATUM
VAL_GEO_ACCURACY [Geographical accuracy] optional
The horizontal distance from the stated geographical position within which there is a defined confidence of the true position falling.
Rules:
  1. If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
    .
Domain: VAL_DIST_HORZ
UOM_GEO_ACCURACY [Unit of measurement [geographical accuracy]] optional
The unit of measurement for the value expressing the accuracy of the geographic co-ordinates.
Domain: UOM_DIST_HORZ
VAL_ELEV [Elevation] optional
The vertical distance of the position from Mean Sea Level. The geoidal height of the position.
Rules:
  1. If an occurrence of this entity is at the same time threshold of a runway, this attribute is mandatory
    .
  2. If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
    .
Domain: VAL_DIST_VER
VAL_ELEV_ACCURACY [Elevation accuracy] optional
The vertical distance from the stated elevation within which there is a defined confidence of the true position falling.
Rules:
  1. VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
    .
Domain: VAL_DIST_VER
VAL_GEOID_UNDULATION [Geoid undulation] optional
A distance separating the geoid and the ellipsoid at that position. In respect of WGS-84 geodetic datum, the difference between the WGS-84 ellipsoidal height and geoidal height represents geoidal undulation.
Rules:
  1. VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
    .
Domain: VAL_DIST_VER
UOM_DIST_VER [Unit of measurement [vertical distance]] optional
The unit of measurement for vertical distances: elevation, geoidal undulation.
Domain: UOM_ELEV
VAL_CRC [Cyclic redundancy check] optional
Hexadecimal value of a 32-bit polynominal cyclic redundancy check (CRC) over the values of a selected set of attributes that model critical, essential and routine data, according to ICAO Annex 15, item 3.2.10.
Notes:
Applications implementing the model shall decide and notify the specific attributes which are used for the CRC calculations, taking into consideration the requirements of the ICAO Annex 15.
Domain: VAL_HEX
TXT_VER_DATUM [Vertical Datum] optional
Attribute to take the "Vertical Datum" (viz. the tide gauge to determine MSL - for example, "AMSTERDAM GAUGE", "NEWLYN" etc.).
Domain: TXT_DESCR
TXT_RMK [Remark] optional
Domain: TXT_RMK