SERVICE_IN_AIRSPACE Service provided in airspace
Attributes
TXT_RMK Remark
Relationships
must be also one and only one SERVICE Service
An AIRSPACE as a physical volume may be provided with a number and variety of different services on one or more frequencies (e.g.: ACC, APP, FIS, ATIS, VOLMET, etc.).
must be furnished within one and only one AIRSPACE Airspace
SERVICE_ON_HOLDING_PROC Service provided on holding procedure
Attributes
TXT_RMK Remark
Relationships
must be furnished on one and only one HOLDING_PROCEDURE Holding procedure
must be also one and only one SERVICE Service
Rule:
  1. CODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'.
SERVICE_ON_IAP Service provided on IAP
Attributes
TXT_RMK Remark
Relationships
must be furnished on one and only one IAP Instrument approach procedure [IAP]
must be also one and only one SERVICE Service
Rule:
  1. CODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'.
SERVICE_ON_RTE_SEG Service provided on route segment
Attributes
TXT_RMK Remark
Relationships
must be also one and only one SERVICE Service
Rule:
  1. CODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'.
must be furnished on one and only one RTE_SEG Route segment
SERVICE_ON_SID Service provided on SID
Attributes
TXT_RMK Remark
Relationships
must be furnished on one and only one SID Standard instrument departure [SID]
must be also one and only one SERVICE Service
Rule:
  1. CODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'.
SERVICE_ON_STAR Service on STAR
Attributes
TXT_RMK Remark
Relationships
must be furnished on one and only one STAR Standard instrument arrival [STAR]
must be also one and only one SERVICE Service
Rule:
  1. CODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'.
SID Standard instrument departure [SID]
Attributes
TXT_DESIG Designator
CODE_CAT_ACFT Aircraft category
CODE_RNP Required navigation performance
TXT_DESCR_COM_FAIL Communication failure description
CODE_TRANS_ID Transition identifier
CODE_TYPE_RTE Type
TXT_DESCR Description
TXT_RMK Remark
Relationships
may be used according to one or more SID_USAGE SID usage
must be for one and only one AD_HP Aerodrome / Heliport
may be associated with one and only one MSA_GROUP MSA group
may be composed of one or more PROCEDURE_LEG Procedure leg
Rule:
  1. The value of NO_SEQ of all PROCEDURE_LEG that are related to the same SID must be in a sequence, either ascending or descending (at one moment in time). This inherently implies uniqueness.
may be used as one or more TFC_FLOW_RTE_ELEMENT Flow routing element
may be used as one or more FLOW_COND_ELEMENT Flow condition element
may be served by one or more SERVICE_ON_SID Service provided on SID
either may be for one and only one RWY_DIRECTION RWY direction
... or may be for one and only one FATO_DIRECTION Approach and take-off direction of a FATO
SID_USAGE SID usage
Attributes
CODE_RTE_AVBL Usage of the standard instrument departure procedure within the flexible use of airspace context
TXT_RMK Remark
Relationships
must be based on one and only one SID Standard instrument departure [SID]
may be operating according to one and only one TIMETABLE Timetable
SIGNIFICANT_POINT Significant point
Relationships
may be referred to by one or more DISTANCE_INDICATION Navaid - Distance indication
may be the holding point for one or more HOLDING_PROCEDURE Holding procedure
may be also one or more SIGNIFICANT_POINT_IN_AS Significant point in airspace
may be the end of one or more RTE_PORTION Route portion
may be the arc center for one or more PROCEDURE_LEG Procedure leg
may be the beginning of one or more SEGMENT Route segment base
may be the beginning of one or more RTE_PORTION Route portion
may be considered as one or more AD_HP_NAV_AID Radio navigation aid at Aerodrome / Heliport
may be used as one or more FLOW_COND_ELEMENT Flow condition element
may be is the end of one or more DIRECT_FLIGHT_SEGMENT DIRECT (DCT) Segment
may be is the start of one or more DIRECT_FLIGHT_SEGMENT DIRECT (DCT) Segment
may be is used by one or more MSA_GROUP MSA group
may be is used by one or more AIRSPACE_CIRCLE_VERTEX Airspace circular vertex
may be is used by one or more AIRSPACE_VERTEX Airspace vertex
may be is used by one or more AIRSPACE_VERTEX Airspace vertex
may be a fix for one or more PROCEDURE_LEG Procedure leg
may be referred to by one or more ANGLE_INDICATION Navaid - Angular reference - Version
may be used as one or more TFC_FLOW_RTE_ELEMENT Flow routing element
may be the end of one or more SEGMENT Route segment base
either must be at one and only one DESIGNATED_POINT Designated point
... or must be at one and only one VOR VHF omnidirectional radio range beacon [VOR]
... or must be at one and only one NDB Non-directional radio beacon [NDB]
... or must be at one and only one DME Distance measuring equipment [DME]
... or must be at one and only one TACAN Tactical air navigation beacon [TACAN]
... or must be at one and only one MKR Marker [MKR]
SIGNIFICANT_POINT_IN_AS Significant point in airspace
Attributes
CODE_TYPE Type
TXT_RMK Remark
Relationships
must be also one and only one SIGNIFICANT_POINT Significant point
must be situated within one and only one AIRSPACE Airspace