|
|
All limitations of the same type (such as, coverage, usability, out of tolerance, etc.) of a VOR, described using circular sector volumes.
|
|
|
Attributes
|
|
CODE_COMP
[Component]
mandatory
|
|
|
A code indicating which of the two components of the TACAN is affected by the limitation.
|
|
|
Domain:
CODE_COMPONENT_TACAN
|
|
CODE_TYPE
[Limitation type]
mandatory
|
|
|
A code indicating the type of radio navigation aid limitation.
|
|
|
Rules:
- If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory.
- If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory.
|
|
|
Domain:
CODE_TYPE_NAV_AID_LIMIT
|
|
TXT_RMK
[Remark]
optional
|
|
|
|
|
|
Domain:
TXT_RMK
|
|
|
|
A rule meant to regulate the use of the route network, by identifying a set of flights which fulfil a combination of elementary flow conditions and either forbidding them on a particular routing or obliging them to follow one routing out of a set of mandatory alternatives.
|
Notes:
|
Flow restrictions are created mainly to protect a portion of the route network or an airspace from being used in excess of its traffic capacity. Other reasons, such as prohibiting overflying of an airspace by a specific Aircraft Operator, can occasionally lead to the establishment of flow restrictions.
|
|
|
Attributes
|
|
CODE_ID
[Identifier]
mandatory
|
|
|
A coded value which uniquely identifies the restriction.
|
|
|
Domain:
CODE_ID_RESTR
|
|
CODE_TYPE
[Restriction type]
mandatory
|
|
|
A code indicating if the restriction is an interdiction or a mandatory routing.
|
|
|
Notes:
|
|
|
If more routes of type 'mandatory' are specified for a given traffic restriction, they must be considered as alternative options.
|
|
|
Rules:
- If CODE_TYPE='M', than the relationship 'regulating the use of TFC_FLOW_RTE' is mandatory.
|
|
|
Domain:
CODE_TYPE_RESTR
|
|
TXT_OPR_GOAL
[Operational goal]
optional
|
|
|
A textual description of the operational goal of the restriction.
|
|
|
Domain:
TXT_DESCR
|
|
TXT_DESCR
[Textual description]
optional
|
|
|
A textual description of the restriction.
|
|
|
Notes:
|
|
|
This textual description is supposed to facilitate checking the codification of the restriction. For a complicated restriction, it might happen that its codification is not fully in agreement with the intention of those having established the restriction. The textual description would allow manual checking to be done at any moment.
|
|
|
Domain:
TXT_DESCR
|
|
TXT_REMARK
[Remark]
optional
|
|
|
|
|
|
Domain:
TXT_RMK
|
|
|
|
A sequence of traffic flow routing elements (points, route portions or airspace) that must/must not appear in the specified order in the flight plan of an aircraft fulfilling the conditions of the related TFC_ FLOW_RESTR (according to its CODE_TYPE attribute).
|
|
|
Attributes
|
|
NO_SEQ
[Sequence number]
mandatory
|
|
|
A sequence number which uniquely identifies each mandatory routing alternative or routing interdiction associated with one traffic flow restriction.
|
|
|
Domain:
NO_SEQ
|
|
|
|
An airspace, route or point that is concerned by a specified traffic flow restriction.
|
|
|
Attributes
|
|
VAL_SPEED
[Speed]
optional
|
|
|
The value of the speed limit imposed on a traffic floz routing element.
|
|
|
Rules:
- If VAL_SPEED is specified, then UOM_SPEED, CODE_SPEED_REF and CODE_SPEED_CRITERIA are mandatory..
|
|
|
Domain:
VAL_SPEED
|
|
UOM_SPEED
[Unit of measurement [speed]]
optional
|
|
|
The unit of measurement of the speed limit.
|
|
|
Domain:
UOM_SPEED
|
|
CODE_SPEED_REF
[Speed reference]
optional
|
|
|
A code indicating the reference system for the speed value. For example: IAS, TAS or GS (ground speed).
|
|
|
Domain:
CODE_SPEED_REF
|
|
CODE_SPEED_CRITERIA
[Speed limit criteria]
optional
|
|
|
A code indicating whether the speed is a maximum, a minimum or an imposed value.
|
|
|
Domain:
CODE_COMPARISON
|
|
NO_SEQ
[Sequence number]
mandatory
|
|
|
A number in sequence used to indicate the order of the traffic flow routing element in the traffic flow routing (TFC_FLOW_RTE) to which it belongs.
|
|
|
Domain:
NO_SEQ
|
|
|
|
A single level or a level band associated with a traffic flow routing element.
|
Notes:
|
1) single levels are represented using the VAL_DIST_VER_LOWER, UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER attributes. 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.
|
|
|
Attributes
|
|
VAL_DIST_VER_LOWER
[Lower limit]
mandatory
|
|
|
The value of the lowermost cruising level.
|
|
|
Rules:
- 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 between VAL_DIST_VER_LOWER and VAL_DIST_VER_UPPER of the related RTE_SEG.
|
|
|
Domain:
VAL_DIST_VER
|
|
UOM_DIST_VER_LOWER
[Unit of measurement [lower limit]]
mandatory
|
|
|
The unit of measurement used to express the lowermost cruising level.
|
|
|
Rules:
- 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]
mandatory
|
|
|
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:
- If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory.
- 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 between VAL_DIST_VER_LOWER and VAL_DIST_VER_UPPER of the related RTE_SEG.
- 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 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:
- 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
|
|
|
|
A component of a timetable, which must be specified with only one set of attributes, indicating the working hours of an other element.
|
Rules:
- At least one of the two attributes TIME_WEF or CODE_EVENT_WEF must be specified.
- If both TIME_WEF and CODE_EVENT_WEF are specified, then CODE_COMB_WEF is mandatory as it indicates which of the two sets takes precedence, i.e. which is the latest and which is the earliest.
- TIME_REL_EVENT_WEF may be specified only if CODE_EVENT_WEF was specified.
- At least one of the two attributes TIME_TIL or CODE_EVENT_TIL must be specified.
- If both TIME_TIL and CODE_EVENT_TIL are specified, then CODE_COMB_TIL is mandatory as it indicates which of the two sets takes precedence, i.e. which is the latest and which is the earliest.
- TIME_REL_EVENT_TIL may be specified only if CODE_EVENT_TIL was specified.
|
|
|
Attributes
|
|
CODE_TIME_REF
[Time reference system]
mandatory
|
|
|
A code indicating the time reference system (for example, 'UTC').
|
|
|
Rules:
- If CODE_TIME_REF = 'UTCW', then the attributes DATE_VALID_WEF and DATE_VALID_TILL cannot take the values 'SDLST' or 'EDLST'..
|
|
|
Domain:
CODE_TIME_REF
|
|
DATE_VALID_WEF
[Yearly start date]
mandatory
|
|
|
The start date of the validity of a timesheet. Used together with DATE_VALID_TIL to express repetitive time periods like 15 May to 15 November.
|
|
|
Notes:
|
|
|
1) This date is included. 2) When the schedule specified in the Timesheet is valid all year long, this attribute has the value "01-01" and the attribute DATE_VALID_TIL has the value "31-12".
|
|
|
Domain:
DATE_MONTH_DAY
|
|
DATE_VALID_TIL
[Yearly end date]
mandatory
|
|
|
The end date of the validity of a timesheet. Used together with DATE_VALID_WEF to express repetitive time periods like 15 May to 15 November.
|
|
|
Notes:
|
|
|
1) This date is included. 2) When the schedule specified in the Timesheet is valid all year long, this attribute has the value "31-12" and the attribute DATE_VALID_WEF has the value "01-01".
|
|
|
Domain:
DATE_MONTH_DAY
|
|
CODE_DAY
[Affected day or start of affected period]
mandatory
|
|
|
A code indicating the day the timesheet is referring to.
|
|
|
Domain:
CODE_DAY
|
|
CODE_DAY_TIL
[End of affected period]
optional
|
|
|
A code indicating the days affected by a timesheet, as follows: - if the value of this attribute is NULL, the TIME_TIL, CODE_EVENT_TIL, TIME_REL_EVENT_TIL and CODE_COMB_TIL must be considered as occurring on the day specified in the attribute CODE_DAY (e.g. MON from 07:30 till 16:00); - if the value of this attribute is not NULL, the TIME_TIL, CODE_EVENT_TIL, TIME_REL_EVENT_TIL and CODE_COMB_TIL must be considered as occurring on the day specified in this attribute and the period described by the timesheet is considered to be a continuous one (e.g. MON 07:30 till FRI 16:00);
|
|
|
Rules:
- The allowable values for the CODE_DAY and CODE_DAY_TIL belong to 4 distinct sets:
- {MON, TUE, WED, THU, FRI, SAT or SUN}, - {PWD, WD, AWD}, - {PLH, LH, ALH}, -{ANY}. CODE_DAY_TIL must either be NULL or have a value in the same set as the CODE_DAY. If CODE_DAY='ANY', then CODE_DAY_TIL must be NULL.
|
|
|
Domain:
CODE_DAY
|
|
TIME_WEF
[Start - Time]
optional
|
|
|
The time of the day (specified in the CODE_DAY attribute) when the period described in the timesheet starts.
|
|
|
Domain:
TIME
|
|
CODE_EVENT_WEF
[Start - Event]
optional
|
|
|
A coded reference to an event (like sunset or sunrise), the occurrence of which indicates when the period described in the Timesheet starts.
|
|
|
Domain:
CODE_TIME_EVENT
|
|
TIME_REL_EVENT_WEF
[Start - Relative to event]
optional
|
|
|
The number of minutes before or after the event referred to in the CODE_EVENT_WEF attribute when the period described in the Timesheet starts.
|
|
|
Domain:
TIME_LAP
|
|
CODE_COMB_WEF
[Start - Interpretation]
optional
|
|
|
When both the TIME_WEF and CODE_EVENT_WEF values are not NULL, this attribute explains how the combination of the two attributes should be interpreted, i.e. which of the two moments in time is the beginning of the period described by the timesheet.
|
|
|
Domain:
CODE_COMB_TIME_EVENT
|
|
TIME_TIL
[End - Time]
optional
|
|
|
The time of the day when the period described in the timesheet ends.
|
|
|
Domain:
TIME
|
|
CODE_EVENT_TIL
[End - Event]
optional
|
|
|
A coded reference to an event (like sunset or sunrise), the occurrence of which indicates when the period described in the Timesheet ends.
|
|
|
Domain:
CODE_TIME_EVENT
|
|
TIME_REL_EVENT_TIL
[End - Relative to event]
optional
|
|
|
The number of minutes before or after the event referred to in the CODE_EVENT_TIL attribute when the period described in the Timesheet ends.
|
|
|
Domain:
TIME_LAP
|
|
CODE_COMB_TIL
[End - Interpretation]
optional
|
|
|
When both the TIME_TIL and CODE_EVENT_TIL values are not NULL, this attribute explains how the combination of the two attributes should be interpreted, i.e. which of the two moments in time is the end of the period described by the timesheet.
|
|
|
Domain:
CODE_COMB_TIME_EVENT
|
|
|
|
(ICAO) An entity used to describe operational hours, working hours, activation hours, hours of watch, etc. .
|
|
|
Attributes
|
|
CODE_WORK_HR
[Working hours]
mandatory
|
|
|
A code indicating the type of working hours.
|
|
|
Notes:
|
|
|
Both CODE_WORK_HR and one or more related TIMESHEET(s) may be specified. The interpretation to be given to such combinations depends on the value of CODE_WORK_HR: H24 - excluding the periods specified in the related TIMESHEET(s); HJ - excluding the periods specified in the related TIMESHEET(s); HN - excluding the periods specified in the related TIMESHEET(s); HX - within the periods specified in the related TIMESHEET(s); HO - within the periods specified in the related TIMESHEET(s); NOTAM - within the periods specified in the related TIMESHEET(s); TIMSH - as specified in the related TIMESHEET(s).
|
|
|
Rules:
- If the value of this attribute is 'TIMSH', then the relationship between TIMETABLE and TIMESHEET is mandatory.
|
|
|
Domain:
CODE_TYPE_TIMETABLE
|
|
TXT_RMK_WORK_HR
[Remark to working hours]
optional
|
|
|
Free text remarks concerning the working hours.
|
|
|
Domain:
TXT_RMK
|
|
|
|
(ICAO) A load bearing area on which an aircraft/helicopter may touch down or lift-off.
|
Rules:
- 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.
|
|
|
Attributes
|
|
TXT_DESIG
[Designator]
mandatory
|
|
|
The textual designator of the touch down and lift-off area.
|
|
|
Domain:
TXT_DESIG
|
|
GEO_LAT
[Latitude]
mandatory
|
|
|
The latitude of the position of the aiming point.
|
|
|
Domain:
GEO_LAT
|
|
GEO_LONG
[Longitude]
mandatory
|
|
|
The longitude of the position of the aiming point.
|
|
|
Domain:
GEO_LONG
|
|
CODE_DATUM
[Datum]
mandatory
|
|
|
A code indicating the geodetic datum in which the geographical co-ordinates are expressed.
|
|
|
Rules:
- All geographical coordinates should be expressed in the WGS 84 system.
|
|
|
Domain:
CODE_DATUM
|
|
VAL_GEO_ACCURACY
[Geographical accuracy]
optional
|
|
|
The value of the horizontal distance from the stated geographical position within which there is a defined confidence of the true position falling.
|
|
|
Rules:
- 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 geographical co-ordinates.
|
|
|
Domain:
UOM_DIST_HORZ
|
|
VAL_ELEV
[Elevation]
optional
|
|
|
The value of the vertical distance of the aiming point from Mean Sea Level. The geoidal height of the position.
|
|
|
Rules:
- If VAL_ELEV is specified, then UOM_DIST_VER is mandatory.
|
|
|
Domain:
VAL_DIST_VER
|
|
VAL_ELEV_ACCURACY
[Elevation accuracy]
optional
|
|
|
The value of the vertical distance from the stated elevation within which there is a defined confidence of the true position falling.
|
|
|
Rules:
- VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified.
|
|
|
Domain:
VAL_DIST_VER
|
|
VAL_GEOID_UNDULATION
[Geoid undulation]
optional
|
|
|
The value of the 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 the geoidal undulation.
|
|
|
Rules:
- 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
|
|
VAL_LEN
[Length]
optional
|
|
|
The value of the physical length of the touchdown and lift-off area.
|
|
|
Rules:
- If specified, VAL_LEN must correspond (within 5 metres) to the length calculated using the coordinates of the related TLOF_SHAPE_POINTs.
- If VAL_LEN is specified, then UOM_DIM is mandatory.
|
|
|
Domain:
VAL_DIST_HORZ
|
|
VAL_WID
[Width]
optional
|
|
|
The value of the physical width of the touchdown and lift-off area.
|
|
|
Rules:
- If specified, VAL_WID must correspond (within 5 metres) to the width calculated using the coordinates of the related TLOF_SHAPE_POINTs.
- If VAL_WID is specified, then UOM_DIM is mandatory.
|
|
|
Domain:
VAL_DIST_HORZ
|
|
UOM_DIM
[Unit of measurement [horizontal dimension]]
optional
|
|
|
The unit of measurement for the horizontal dimensions of the touchdown and lift-off area.
|
|
|
Domain:
UOM_DIST_HORZ
|
|
VAL_SLOPE
[Slope angle]
optional
|
|
|
The value of the maximum profile slope of the touchdown and lift-off area. This value is always expressed as a percent.
|
|
|
Domain:
VAL_SLOPE
|
|
[CODE_COMPOSITION]
DEPRECATED-4.5
[Surface composition]
optional
|
|
|
A code indicating the composition of a TLOF surface. For example, asphalt, concrete etc..
|
|
|
Domain:
CODE_COMPOSITION_SFC
|
|
[CODE_COND_SFC]
DEPRECATED-4.5
[Surface condition]
optional
|
|
|
A code indicating the condition of a TLOF 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:
- 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.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
|
|
CODE_CLASS_HEL
[Helicopter class]
optional
|
|
|
A code indicating the performance class of helicopters that the Touch Down and Lift-Off Area is intended to serve.
|
|
|
Domain:
CODE_CLASS_HEL
|
|
TXT_MARKING
[Marking]
optional
|
|
|
A textual description of the TLOF marking.
|
|
|
Domain:
TXT_DESCR
|
|
CODE_STS
[Operational status]
optional
|
|
|
A code indicating the operational status of a TLOF. For example, serviceable, unserviceable, closed, work in progress, etc.
|
|
|
Domain:
CODE_STS_SFC
|
|
TXT_RMK
[Remark]
optional
|
|
|
|
|
|
Domain:
TXT_RMK
|
|
... a type of
SURFACE_LGT_SYS
|
|
The lighting system provided for a TLOF surface at an aerodrome/heliport.
|
|
|
Attributes
... see as well the attributes of the super-type entity
|
|
CODE_PSN
[Part]
mandatory
|
|
|
A code indicating the part of the TLOF surface the lighting system is serving. For example, TDZ, THR, centre line, edge, etc..
|
|
|
Domain:
CODE_PSN_TLOF
|
|
... a type of
LANDING_PROTECTION_AREA
|
|
An area situated in the vicinity of a touch down and lift-off area, provided to protect helicopters during manoeuvring, take-off and/or landing operations.
|
|
|
Attributes
... see as well the attributes of the super-type entity
|
|