Contains the date when the file was created. Format is DD-MMMYYYY. Where DD is the two-digit decimal day of month, MMM is a three-character month abbreviation, and YYYY is the four-digit decimal year. Contains the UTC time when the file was created. The format is two decimal digits each for hours, minutes, and seconds, separated by colons.
This field contains the 32 bit CRC value for the ARINC data file (including data and header records).ARINC Report 665, Loadable Software Standards, Section 4.0 defines the use of CRC codes.The CRC Polynomial used to calculate the CRC of the ARINC 424 data file shall be the 32-bit CRC (0x04C11DB7), calculated as described in ARINC Report 665
Contains information to identify the data user/customer (for example, the customer name(s), file codes). Content defined by the data supplier and/or customer.
Contains 3 decimal numbers to uniquely identify revision of this file. Initially set to 001, but will be incremented if the file is created more than once in the same cycle.
ANY element from namespace(s) 'http://www.mitre.org/ARINC/extensions, http://www.navtech.aero/ARINC/extensions,
http://www.garmin.com/ARINC/extensions, http://www.agustawestland-ans.com/ARINC/extensions,
http://www.NGA.mil'
Source
<xs:element name="supplementalData" type="SupplementalData" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is for private and/or temporary exchanges of data.</xs:documentation></xs:annotation></xs:element>
The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.
<xs:element name="custAreaCode" type="type:CustAreaCode" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.</xs:documentation></xs:annotation></xs:element>
For the concrete data type that implements A424Record the cycle date represents the last time the children elements changed. This only applies to elements with the same arity as this cycle date element. For example the cycle date that is a first child of a Procedure does not indicate if children of a Leg changed.
<xs:element name="cycleDate" type="type:CycleDate" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For the concrete data type that implements A424Record the cycle date represents the last time the children elements changed. This only applies to elements with the same arity as this cycle date element. For example the cycle date that is a first child of a Procedure does not indicate if children of a Leg changed.</xs:documentation></xs:annotation></xs:element>
<xs:element name="notes" type="type:NotesText" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is used to have relevant Notes</xs:documentation></xs:annotation></xs:element>
The “Record Type” field content indicates whether the record data are “standard,” i.e., suitable for universal application, or “tailored,” i.e. included for a single user’s specific purpose . Record type is set to tailored if any extension points are included in the record or if any content of the ARINC 424 XML schemas are altered in any way.
<xs:element name="recordType" type="enum:RecordType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Record Type” field content indicates whether the record data are “standard,” i.e., suitable for universal application, or “tailored,” i.e. included for a single user’s specific purpose . Record type is set to tailored if any extension points are included in the record or if any content of the ARINC 424 XML schemas are altered in any way.</xs:documentation></xs:annotation></xs:element>
The Datum Code field defines the Local Horizontal Reference Datum to which a geographical position, expressed in latitude and longitude, is associated.
Provisional South Chilean 1963 (also known as Hito XVIII 1963)
enumeration
HJO
Hjorsey 1955
enumeration
HKD
Hong Kong 1963
enumeration
HTN
Hu-Tzu-Shan
enumeration
IBE
Bellevue (IGN)
enumeration
IDN
Indonesian 1974
enumeration
IGF
Nouvelle Triangulation de France (FRANCE)
enumeration
IND
Indian
enumeration
INF
Indian 1954
enumeration
ING
Indian 1960
enumeration
INH
Indian 1975
enumeration
IRL
Ireland 1965
enumeration
ISG
ISTS 061 Astro 1968
enumeration
IST
ISTS 073 Astro 1969
enumeration
JOH
Johnston Island 1961
enumeration
KAN
Kandawala
enumeration
KEA
Kertau 1948
enumeration
KEG
Kerguelen Island 1949
enumeration
KUS
Kusaie Astro 1951
enumeration
LCF
L.C. 5 Astro 1961
enumeration
LEH
Leigon
enumeration
LIB
Liberia 1964
enumeration
LUZ
Luzon
enumeration
MAS
Massawa
enumeration
MCN
Manchurian Principal System
enumeration
MER
Merchich
enumeration
MID
Midway Astro 1961
enumeration
MIK
Mahe 1971
enumeration
MIN
Minna
enumeration
MOD
Rome 1940
enumeration
MOL
Montjong Lowe
enumeration
MPO
M'Poraloko
enumeration
MVS
Viti Levu 1916
enumeration
NAH
Nahrwan
enumeration
NAN
Nanking 1960
enumeration
NAP
Naparima, BWI
enumeration
NAR
North American 1983
enumeration
NAS
North American 1927
enumeration
NSD
North Sahara 1959
enumeration
OEG
Old Egyptian 1907
enumeration
OGB
Ordnance Survey of Great Britain 1936
enumeration
OHA
Old Hawaiian
enumeration
PAM
Palmer Astro
enumeration
PDM
Potsdam
enumeration
PHA
Ayabelle Lighthouse
enumeration
PIT
Pitcairn Astro 1967
enumeration
PLN
Pico de las Nieves
enumeration
POS
Porto Santo 1936
enumeration
PRD
Portuguese Datum 1973
enumeration
PRP
Provisional South American 1956
enumeration
PTB
Point 58
enumeration
PTN
Point Noire 1948
enumeration
PUK
Pulkovo 1942
enumeration
PUR
Puerto Rico
enumeration
QAT
Qatar National
enumeration
QUO
Qornoq
enumeration
REU
Reunion
enumeration
RPE
Parametrop Zemp 1990 (English translation) The Parameters of the Earth 1990
enumeration
RTS
RT90
enumeration
SAE
Santo (DOS) 1965
enumeration
SAN
South American 1969
enumeration
SAO
Sao Braz
enumeration
SAP
Sapper Hill 1943
enumeration
SCK
Schwarzeck
enumeration
SGM
Selvagem Grande 1938
enumeration
SHB
Astro DOS 71/4
enumeration
SOA
South Asia
enumeration
SPK
S-42 (Pulkovo 1942)
enumeration
SRL
Sierra Leone 1960
enumeration
STO
Stockholm 1938 (RT38)
enumeration
SYO
Sydney Observatory
enumeration
TAN
Tananarive Observatory 1925
enumeration
TDC
Tristan Astro 1968
enumeration
TIL
Timbalai 1948
enumeration
TOY
Tokyo
enumeration
TRI
Trinidad Trigonometrical Survey
enumeration
TRN
Astro Tern Island (Frig) 1961
enumeration
UNK
Unknown
enumeration
VOI
Voirol 1874
enumeration
VOR
Voirol 1960
enumeration
WAK
Wake Island Astro 1952
enumeration
WGA
World Geodetic System 1960
enumeration
WGB
World Geodetic System 1966
enumeration
WGC
World Geodetic System 1972
enumeration
WGE
World Geodetic System 1984
enumeration
YAC
Yacare
enumeration
ZAN
Zanderij
Source
<xs:element name="datumCode" type="enum:DatumCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Datum Code field defines the Local Horizontal Reference Datum to which a geographical position, expressed in latitude and longitude, is associated.</xs:documentation></xs:annotation></xs:element>
<xs:element name="icaoCode" type="type:IcaoCode" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “ICAO Code” field permits records to be categorized geographically within the limits of the categorization performed by the “Area Code” field.</xs:documentation></xs:annotation></xs:element>
The identifier field contains the five-character-name-code, or other series of characters, with which the fix is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, and Airport Identifiers
<xs:element name="identifier" type="type:CoreIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The identifier field contains the five-character-name-code, or other series of characters, with which the fix is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, and Airport Identifiers</xs:documentation></xs:annotation></xs:element>
This field is optional for convenience in data processing. The value of this field is not authoritative.
Diagram
Type
xs:decimal
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="decimalDegreesLatitude" type="xs:decimal" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is optional for convenience in data processing. The value of this field is not authoritative.</xs:documentation></xs:annotation></xs:element>
This field is optional for convenience in data processing. The value of this field is not authoritative.
Diagram
Type
xs:decimal
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="decimalDegreesLongitude" type="xs:decimal" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is optional for convenience in data processing. The value of this field is not authoritative.</xs:documentation></xs:annotation></xs:element>
The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.
<xs:element name="magneticVariation" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.</xs:documentation></xs:annotation></xs:element>
The UIR Reference field identifies the Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The reference is for the controlling Area Control Center or Flight Information Center.
Diagram
Type
xs:IDREF
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="uirRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The UIR Reference field identifies the Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The reference is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element>
The FIR Reference field identifies the Flight Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The reference is for the controlling Area Control Center or Flight Information Center.
Diagram
Type
xs:IDREF
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="firRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The FIR Reference field identifies the Flight Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The reference is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element>
<xs:element name="elevation" type="type:Elevation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Elevation of the highest elevation of any landing surface on the port in feet.</xs:documentation></xs:annotation></xs:element>
<xs:element name="ataIATADesignator" type="type:ATAIATADesignator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The ATA/IATA field contains the Airport/Heliport ATA/IATA designator code to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element>
The “Daylight” Time Indicator” field is used to indicate if the airport observes Daylight or Summer time when such time changes are in effect for the country or state the airport resides in.
<xs:element name="daylightIndicator" type="type:DaylightIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Daylight” Time Indicator” field is used to indicate if the airport observes Daylight or Summer time when such time changes are in effect for the country or state the airport resides in.</xs:documentation></xs:annotation></xs:element>
<xs:element name="ifrCapability" type="type:IFRCapability" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “IFR Capability” field indicates if the Airport/Heliport has any published Instrument Approach Procedures.</xs:documentation></xs:annotation></xs:element>
The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.
The field will be blank if details and procedures are provided in both magnetic and true for the airport. In such cases the individual detail or procedure records will contain the magnetic or true information
enumeration
True
if all detail and procedure for the airport are reported in true bearing
enumeration
Magnetic
if all detail and procedure for the airport are reported in magnetic bearing,
Source
<xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element>
Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.
Airport/Heliport is not open to the public (private)
enumeration
Civil
Airport/Heliport is open to the public (civil)
enumeration
Military
Airport/Heliport is military airport
enumeration
Joint
Airport is joint Civil and Military
Source
<xs:element name="publicMilitaryIndicator" type="enum:PublicMilitaryIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.</xs:documentation></xs:annotation></xs:element>
The “Recommended Navaid” field allows the reference facility for the waypoint in a given record “Fix Ident” field or for an Airport or Heliport to be specified. VHF, NDB (Enroute and Terminal), Localizer, TACAN, GLS and MLS Navaids may be referenced.
<xs:element name="recommendedNavaid" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Recommended Navaid” field allows the reference facility for the waypoint in a given record “Fix Ident” field or for an Airport or Heliport to be specified. VHF, NDB (Enroute and Terminal), Localizer, TACAN, GLS and MLS Navaids may be referenced.</xs:documentation></xs:annotation></xs:element>
The Speed Limit field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.
<xs:element name="speedLimit" type="type:SpeedLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Speed Limit field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.</xs:documentation></xs:annotation></xs:element>
<xs:element name="speedLimitAltitude" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Speed Limit Altitude” is the altitude below which speed limits may be imposed.</xs:documentation></xs:annotation></xs:element>
If this field is true, then the numerical value in the altitude element is populated with a flight level. Therefore, the sibling altitude element represents the altitude in hundreds of feet, else the altitude element represents altitude in feet.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isFlightLevel" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this field is true, then the numerical value in the altitude element is populated with a flight level. Therefore, the sibling altitude element represents the altitude in hundreds of feet, else the altitude element represents altitude in feet.</xs:documentation></xs:annotation></xs:element>
The standard time zone system is based on the division of world into 24 zones, each of 15 degrees longitude. The “zero” time zone is entered at Greenwich meridian with longitudes 7 degrees, 30 minutes West and 7 degrees, 30 minutes east, and there is no difference in the standard time of this time zone and Greenwich Mean Time. Time zones are designated by letters of the alphabet and numbers by which the standard time of each zone differs from that at Greenwich.
<xs:element name="timeZone" type="type:TimeZone" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The standard time zone system is based on the division of world into 24 zones, each of 15 degrees longitude. The “zero” time zone is entered at Greenwich meridian with longitudes 7 degrees, 30 minutes West and 7 degrees, 30 minutes east, and there is no difference in the standard time of this time zone and Greenwich Mean Time. Time zones are designated by letters of the alphabet and numbers by which the standard time of each zone differs from that at Greenwich.</xs:documentation></xs:annotation></xs:element>
The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.
<xs:element name="transitionAltitude" type="type:TransitionAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element>
The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.
<xs:element name="transitionLevel" type="type:TransitionAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element>
<xs:element name="terminalNDB" type="TerminalNDB" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>"Terminal NDB" field contains NDBs associated with the Airports and Heliports</xs:documentation></xs:annotation></xs:element>
Defines the location of a designated point using a combination of angles and distances based on the guidance service. The set of angles and distances must not under specify the location.
<xs:element name="portRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Defines the location of a designated point using a combination of angles and distances based on the guidance service. The set of angles and distances must not under specify the location.</xs:documentation></xs:annotation></xs:element>
<xs:element name="elevation" type="type:Elevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Elevation of the navaid location in feet.</xs:documentation></xs:annotation></xs:element>
The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.
<xs:element name="ndbClass" type="type:NdbNavaidClass" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.</xs:documentation></xs:annotation></xs:element>
BFO Operation. Use of Beat Frequency Oscillator type of equipment is required to received an aural identification signal.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isBFORequired" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>BFO Operation. Use of Beat Frequency Oscillator type of equipment is required to received an aural identification signal.</xs:documentation></xs:annotation></xs:element>
Automatic Transcribed Weather.The frequency of this Navaid is used for the continuous broadcast of some sort of automated weather system such as AWOS, ASOS, TWEB, AWIB, AWIS.
enumeration
SCHEDULED
Broadcast Scheduled Weather.The frequency of this Navaid is used for the scheduled, noncontinuous broadcast of some sort of automated weather system such as VOLMET.
<xs:element name="dmeRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field idenifies a reference to a DME navaid which originated in the same source data record as the NDB (i.e. is paired with the NDB)</xs:documentation></xs:annotation></xs:element>
Collectively, all Standard Instrument Departures (SIDs), Standard Terminal Arrivel Routes (STARs) and Instument Approach Procedures (IAPs) coded to the standards in this specification are referred to as Terminal Procedure.
<xs:element name="terminalProcedures" type="TerminalProcedures" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Collectively, all Standard Instrument Departures (SIDs), Standard Terminal Arrivel Routes (STARs) and Instument Approach Procedures (IAPs) coded to the standards in this specification are referred to as Terminal Procedure.</xs:documentation></xs:annotation></xs:element>
This element indcates whether the procedure is an RNAV procdedure.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isRnav" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indcates whether the procedure is an RNAV procdedure.</xs:documentation></xs:annotation></xs:element>
If this element is present and true the procedure is only for helicopters.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isHelicopterOnlyProcedure" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element is present and true the procedure is only for helicopters.</xs:documentation></xs:annotation></xs:element>
<xs:element name="procedureDesignAircraftCategories" type="type:ProcedureDesignAircraftCategories" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indciates the category of aircraft that this procedure was designed to support.</xs:documentation></xs:annotation></xs:element>
<xs:element name="procedureDesignAircraftTypes" type="type:ProcedureDesignAircraftTypes" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indciates the type of aircraft that this procedure was designed to support.</xs:documentation></xs:annotation></xs:element>
<xs:element name="isTypeNotLimited" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Not Limited</xs:documentation></xs:annotation></xs:element>
Definition/Description: This field provides an indicator whether the terminal procedure requires specific operational approval defined by official government sources. Special procedures may be developed based on aircraft performance, aircraft equipment, or crew training, and may also require the use of landing aids, communications, or weather services not available for public use. Examples of special procedures include: SIAP, RCAP, etc.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isSpecial" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Definition/Description: This field provides an indicator whether the terminal procedure requires specific operational approval defined by official government sources. Special procedures may be developed based on aircraft performance, aircraft equipment, or crew training, and may also require the use of landing aids, communications, or weather services not available for public use. Examples of special procedures include: SIAP, RCAP, etc.</xs:documentation></xs:annotation></xs:element>
<xs:element name="procedureDesignMagVar" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the magnetic varaiation used to design the procedure.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the procedure is VOR/DME RNAV.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isVorDmeRnav" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the procedure is VOR/DME RNAV.</xs:documentation></xs:annotation></xs:element>
<xs:element name="rnavPbnNavSpec" type="enum:RnavPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNAV PBN navigation specification applies to this procedure</xs:documentation></xs:annotation></xs:element>
<xs:element name="rnpPbnNavSpec" type="enum:RnpPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNP PBN navigation specification applies to this procedure</xs:documentation></xs:annotation></xs:element>
<xs:element name="sidRunwayTransition" type="SIDRunwayTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the runway transitions of the SID</xs:documentation></xs:annotation></xs:element>
The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.
<xs:element name="transitionAltitudeOrLevel" type="type:Altitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element>
When the terminal procedure has a simgle MSA defined, on the common or final approach route, this field will contain a reference to the MSA for the entire procedure. If the government source MSA is "by transition," the reference is populated on each transition.
Diagram
Type
xs:IDREF
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="msaRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When the terminal procedure has a simgle MSA defined, on the common or final approach route, this field will contain a reference to the MSA for the entire procedure. If the government source MSA is "by transition," the reference is populated on each transition.</xs:documentation></xs:annotation></xs:element>
For Route Type Records - A route of flight is defined by a series of legs taken in order. The “Sequence Number” field defines the position of the leg in the sequence defining the route of flight identified in the route identifier field.
<xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Route Type Records - A route of flight is defined by a series of legs taken in order. The “Sequence Number” field defines the position of the leg in the sequence defining the route of flight identified in the route identifier field.</xs:documentation></xs:annotation></xs:element>
The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.
At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
AtOrBelow
At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
At
At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.
enumeration
B
At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope
enumeration
C
"At or above" altitude specified in second "Altitude" field.
enumeration
G
Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.
enumeration
I
Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope
Source
<xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element>
The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.
<xs:element name="arcRadius" type="type:ARCRadius" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.</xs:documentation></xs:annotation></xs:element>
The “ATC Indicator” field will be used to indicate that the altitudes shown in the altitude fields can be modified by ATC or the altitude will be assigned by ATC.
official government source states that the altitude will be assigned by ATC or if no altitude is supplied
Source
<xs:element name="atcIndicator" type="enum:ATCIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ATC Indicator” field will be used to indicate that the altitudes shown in the altitude fields can be modified by ATC or the altitude will be assigned by ATC.</xs:documentation></xs:annotation></xs:element>
In SID, STAR and Approach Procedure records, this field may contain segment distances, along track distances, excursion distances, or DME distances. The actual content is dependent on the Path and Termination. For more information on the content, refer to Table Three, Leg Data Fields, in Attachment 5 of the 424 specification.
<xs:element name="distance" type="type:LegDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>In SID, STAR and Approach Procedure records, this field may contain segment distances, along track distances, excursion distances, or DME distances. The actual content is dependent on the Path and Termination. For more information on the content, refer to Table Three, Leg Data Fields, in Attachment 5 of the 424 specification.</xs:documentation></xs:annotation></xs:element>
In SID, STAR and Approach Procedure records, the field may contain segment distances/along track distances/excursion distances/DME distances or holding pattern timing.
Diagram
Type
xs:duration
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="holdTime" type="xs:duration" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>In SID, STAR and Approach Procedure records, the field may contain segment distances/along track distances/excursion distances/DME distances or holding pattern timing.</xs:documentation></xs:annotation></xs:element>
A database waypoint established during procedure coding to facilitate more accurate navigation by the Flight Management Computer than would be allowed using air-mass related Path Terminators to replicate source data. The waypoint finds use when such considerations as increased environmental restrictions and the congestion of the available airspace come into play. Used to permit route construction with track to a fix (TF) legs.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPhantomFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A database waypoint established during procedure coding to facilitate more accurate navigation by the Flight Management Computer than would be allowed using air-mass related Path Terminators to replicate source data. The waypoint finds use when such considerations as increased environmental restrictions and the congestion of the available airspace come into play. Used to permit route construction with track to a fix (TF) legs.</xs:documentation></xs:annotation></xs:element>
The “TAA Procedure Turn” field is used to indicate whether or a course reversal is necessary when flying within a particular TAA Area.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isTaaProcedureTurn" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “TAA Procedure Turn” field is used to indicate whether or a course reversal is necessary when flying within a particular TAA Area.</xs:documentation></xs:annotation></xs:element>
Compulsory Reporting Point: Essential or nonessential waypoints may be classified as ATC compulsory points. ATC requires the pilot to make a communications report at these waypoints. All other waypoints may be classified as non compulsory reporting points and are reported only when specifically requested by ATC
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isAtcCompulsoryReportingPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Compulsory Reporting Point: Essential or nonessential waypoints may be classified as ATC compulsory points. ATC requires the pilot to make a communications report at these waypoints. All other waypoints may be classified as non compulsory reporting points and are reported only when specifically requested by ATC</xs:documentation></xs:annotation></xs:element>
The Terminal Procedure Flight Planning Leg distance is the along track distance required to complete any given leg. It is used to determine a cumulative track distance for a given terminal procedure for flight planning purposes, from the beginning of the take-off or arrival point to the termination point of the procedure.
<xs:element name="legDistance" type="type:LegDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Terminal Procedure Flight Planning Leg distance is the along track distance required to complete any given leg. It is used to determine a cumulative track distance for a given terminal procedure for flight planning purposes, from the beginning of the take-off or arrival point to the termination point of the procedure.</xs:documentation></xs:annotation></xs:element>
Holding with single circuit terminating at the fix
enumeration
HM
Holding with Manual Termination
enumeration
IF
Initial Fix
enumeration
PI
045/180 Procedure Turn
enumeration
RF
Constant Radius Arc
enumeration
TF
Track to a Fix
enumeration
VA
Heading to an Altitude Termination
enumeration
VD
Heading to a DME Distance Termination
enumeration
VI
Heading to an Intercept
enumeration
VM
Heading to a Manual Termination
enumeration
VR
Heading to a Radial Termination
Source
<xs:element name="pathAndTermination" type="enum:PathAndTermination" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Path and Termination defines the path geometry for a single record of an ATC terminal procedure.</xs:documentation></xs:annotation></xs:element>
The “Procedure Design Mag Var Indicator” field is an indication of how procedure design magnetic variation was provided in official source data for the procedure defined in the record/record set.
<xs:element name="procedureDesignMagVar" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Procedure Design Mag Var Indicator” field is an indication of how procedure design magnetic variation was provided in official source data for the procedure defined in the record/record set.</xs:documentation></xs:annotation></xs:element>
“RHO” is defined as the geodesic distance in nautical miles to the waypoint identified in the record’s “Fix Ident” field from the NAVAID in the “Recommended NAVAID” field.
<xs:element name="rho" type="type:Rho" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“RHO” is defined as the geodesic distance in nautical miles to the waypoint identified in the record’s “Fix Ident” field from the NAVAID in the “Recommended NAVAID” field.</xs:documentation></xs:annotation></xs:element>
Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.
<xs:element name="rnp" type="type:RequiredNavigationPerformance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.</xs:documentation></xs:annotation></xs:element>
The “Speed Limit” field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.
<xs:element name="speedLimit" type="type:SpeedLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Speed Limit” field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.</xs:documentation></xs:annotation></xs:element>
The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed.For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limitThe STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit.For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit.The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit.For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.
Mandatory Speed, Cross Fix AT speed specified in Speed Limit
enumeration
Minimum
Minimum Speed, Cross Fix AT or ABOVE speed specified in Speed Limit
enumeration
Maximum
Maximum Speed, Cross Fix AT or BELOW speed specified in Speed Limit
Source
<xs:element name="speedLimitDescription" type="enum:SpeedLimitDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed. For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit The STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit. For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit. The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit. For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.</xs:documentation></xs:annotation></xs:element>
The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.
<xs:element name="transitionsAltitudeLevel" type="type:TransitionAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element>
The “Turn Direction” field specifies the direction in which Terminal Procedure turns are to be made. It is also used to indication direction on course reversals, see Attachment 5 Path and Termination
<xs:element name="turnDirection" type="enum:TurnDirection" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Turn Direction” field specifies the direction in which Terminal Procedure turns are to be made. It is also used to indication direction on course reversals, see Attachment 5 Path and Termination</xs:documentation></xs:annotation></xs:element>
This field is used in conjunction with Turn direction to indicate that a turn is required prior to capturing the path defined in a terminal procedure.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="turnDirectionValid" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is used in conjunction with Turn direction to indicate that a turn is required prior to capturing the path defined in a terminal procedure.</xs:documentation></xs:annotation></xs:element>
<xs:element name="vectoring" type="type:Vectoring" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides vectoring information on the route</xs:documentation></xs:annotation></xs:element>
<xs:element name="routeQualifications" type="type:routeQualifications" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides information on qualifications or details on the parent route element</xs:documentation></xs:annotation></xs:element>
If this element exists and is true, Dme is required for the parent procedure.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isDmeReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true, Dme is required for the parent procedure.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true, a GNSS is required for the parent procedure
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isGnssReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true, a GNSS is required for the parent procedure</xs:documentation></xs:annotation></xs:element>
If this element exists and is true RADAR is required for the parent procedure
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isRadarReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true RADAR is required for the parent procedure</xs:documentation></xs:annotation></xs:element>
If this element exists and is true a flight management system is required for the parent procedure
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isFmsReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true a flight management system is required for the parent procedure</xs:documentation></xs:annotation></xs:element>
If this element exists and is true the route is a conventional route
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isConventional" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true the route is a conventional route</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the SID Runway Transition was from a runway.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isFromRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the SID Runway Transition was from a runway.</xs:documentation></xs:annotation></xs:element>
<xs:element name="sidCommonRoute" type="SIDCommonRoute" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the common route of the SID</xs:documentation></xs:annotation></xs:element>
<xs:element name="routeQualifications" type="type:routeQualifications" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides information on qualifications or details on the parent route element</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the SID Common Route was from a runway.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="IsFromRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the SID Common Route was from a runway.</xs:documentation></xs:annotation></xs:element>
<xs:element name="sidEnrouteTransition" type="SIDEnrouteTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the enroute transitions of the SID</xs:documentation></xs:annotation></xs:element>
<xs:element name="vectoring" type="type:Vectoring" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides vectoring invormaiton on the route</xs:documentation></xs:annotation></xs:element>
<xs:element name="routeQualifications" type="type:routeQualifications" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides information on qualifications or details on the parent route element</xs:documentation></xs:annotation></xs:element>
This element indicates that the SID is an Engine Out SID
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isEngineOut" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that the SID is an Engine Out SID</xs:documentation></xs:annotation></xs:element>
The element indicates that the SID is a vector SID
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isVector" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The element indicates that the SID is a vector SID</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the parent is a point in space SID.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPInS" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the parent is a point in space SID.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the procedure will proceed visually.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPInSProceedVisually" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the procedure will proceed visually.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the SID will proceed under visual flight rules.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPInSProceedVfr" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the SID will proceed under visual flight rules.</xs:documentation></xs:annotation></xs:element>
<xs:element name="starRunwayTransition" type="STARRunwayTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the runway transitions.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the STAR Common Route was to a runway.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isToRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the STAR Common Route was to a runway.</xs:documentation></xs:annotation></xs:element>
<xs:element name="starEnrouteTransition" type="STAREnrouteTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the enroute transitions</xs:documentation></xs:annotation></xs:element>
<xs:element name="starCommonRoute" type="STARCommonRoute" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the common route</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the STAR Common Route was to a runway.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isToRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the STAR Common Route was to a runway.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true then the parent is a continious decent STAR.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="isContiniousDecent" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the parent is a continious decent STAR.</xs:documentation></xs:annotation></xs:element>
Area Navigation (RNAV) Approach with Required Navigation Performance (RNP) Approach
enumeration
Ils
Instrument Landing System (ILS) Approach
enumeration
Gls
GNSS Landing System (GLS)Approach
enumeration
LocOnly
Localizer Only (LOC) Approach
enumeration
Mls
Microwave Landing System (MLS) Approach
enumeration
Ndb
Non-Directional Beacon (NDB) Approach
enumeration
Gps
Global Positioning System (GPS) Approach
enumeration
NdbDme
Non-Directional Beacon + DME(NDB+DME) Approach
enumeration
Rnav
Area Navigation (RNAV) Approach
enumeration
VorUsingVordmeOrVortac
VOR Approach using VORDME/VORTAC
enumeration
Tacan
TACAN Approach
enumeration
Sdf
Simplified Directional Facility (SDF) Approach
enumeration
Vor
VOR Approach
enumeration
Lda
Localizer Directional Aid (LDA) Approach
Source
<xs:element name="approachRouteType" type="enum:ApproachRouteType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This element identifies what type of approach the parent is.</xs:documentation></xs:annotation></xs:element>
The “GNSS/FMS Indicator” field provides an indication of whether or not the responsible government agency has authorized the overlay of a conventional, ground based approach procedure with the use of a sensor capable of processing GNSS data or if the procedure may be flown with FMS as the primary navigation equipment. The field is also used to indicate when and RNAV procedure has been authorized for GNSS-based vertical navigation.
Procedure Not Authorized for GNSS or FMS Overlay ? Authorization not published.
enumeration
GnssOverlayAuthNavaidOperatingAndMonitored
Procedure Authorized for GNSS Overlay, primary Navaids operating and monitored. Authorization not published.
enumeration
GnssOverlayAuthNoMonitorNavaidAuth
Procedure Authorized for GNSS Overlay, primary Navaids installed, not monitored Authorization is published. Example: Procedure Title includes (GPS) or (GNSS)
enumeration
GnssOverlayTitleIncludesGpsOrGnss
Procedure Authorized for GNSS Overlay, Procedure Title includes GPS or GNSS
enumeration
FmsOverlayAuthorized
Procedure Authorized for FMS Overlay
enumeration
SbasVerticalAuthorized
RNAV (GPS), RNAV (RNP) or RNAV (GNSS) Procedure SBAS use authorized; SBAS-based vertical navigation authorized
enumeration
SbasVerticalNotAuthorized
RNAV (GPS), RNAV (RNP), RNAV (GNSS) or RNAV Visual Procedure, SBAS-based vertical navigation NOT Authorized
enumeration
SbasVerticalNotPublished
RNAV (GPS) RNAV (RNP), or RNAV (GNSS) Procedure, SBAS-based vertical navigation use not published
enumeration
StandAloneGNSS
Stand Alone GNSS Procedure
enumeration
SbasVerticalNA
RNAV (GPS) RNAV (RNP), or RNAV (GNSS) Procedure within the SBAS operational footprint, but SBAS-based vertical navigation NOT Authorized
enumeration
OverlayAuthNotPublished
Procedure Overlay Authorization not published
enumeration
PbnRnpGps
PBN RNP Approach provide as GPS. The GNSS/FMS IND of G indicates that the GPS approach is an PBN RNAV approach provided with route type P.
enumeration
LocOnlyIls
Localizer only coding portion of ILS. The GNSS/FMS IND of L indicates that the LOC approach is the Localizer only portion of an ILS approach which contains glideslope out information.
Source
<xs:element name="gnssFMSIndicator" type="enum:GNSSFMSIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “GNSS/FMS Indicator” field provides an indication of whether or not the responsible government agency has authorized the overlay of a conventional, ground based approach procedure with the use of a sensor capable of processing GNSS data or if the procedure may be flown with FMS as the primary navigation equipment. The field is also used to indicate when and RNAV procedure has been authorized for GNSS-based vertical navigation.</xs:documentation></xs:annotation></xs:element>
<xs:element name="gbasPathPoint" type="GBASPathPoint" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the GBAS path point record for the approach.</xs:documentation></xs:annotation></xs:element>
<xs:element name="approachPerformanceDesignator" type="enum:ApproachPerformanceDesignator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Approach Performance Designator” field is used to indicate the type or category of approach.</xs:documentation></xs:annotation></xs:element>
The “Approach Route Identifier” field contains the identifier of the approach route to be flown. To facilitate the provision of multiple approach procedures of the same type to a given runway, the field also is used to provide a “multiple indicator.”
<xs:element name="approachRouteIdentifier" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Approach Route Identifier” field contains the identifier of the approach route to be flown. To facilitate the provision of multiple approach procedures of the same type to a given runway, the field also is used to provide a “multiple indicator.”</xs:documentation></xs:annotation></xs:element>
<xs:element name="approachTypeIdentifier" type="type:ApproachTypeIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Identifies the approach types published on a given approach procedure which require Airport or Helicopter Operations SBAS path points.</xs:documentation></xs:annotation></xs:element>
The “Course Width At Threshold” field defines the width of the lateral course at the Landing Threshold Point (LTP) or Fictitious Helipoint (or helipoint). This width, in conjunction with the location of the Flight Path Alignment Point (FPAP) defines the sensitivity of the lateral deviations throughout the approach.
<xs:element name="courseWidthAtThreshold" type="type:CourseWidthAtThreshold" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Course Width At Threshold” field defines the width of the lateral course at the Landing Threshold Point (LTP) or Fictitious Helipoint (or helipoint). This width, in conjunction with the location of the Flight Path Alignment Point (FPAP) defines the sensitivity of the lateral deviations throughout the approach.</xs:documentation></xs:annotation></xs:element>
The “Final Approach Segment Data CRC Remainder” field is an eight (8) character hexadecimal representation of the 32-bit CRC value provided by the source for the information contained in the aeronautical data fields being monitored for integrity. The value is calculated by a specific mathematical algorithm, which is both machine and man processible.
<xs:element name="FASDataCRCRemainder" type="type:FinalApproachSegmentDataCRCRemainder" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Final Approach Segment Data CRC Remainder” field is an eight (8) character hexadecimal representation of the 32-bit CRC value provided by the source for the information contained in the aeronautical data fields being monitored for integrity. The value is calculated by a specific mathematical algorithm, which is both machine and man processible.</xs:documentation></xs:annotation></xs:element>
<xs:element name="flightPathAlignmentPoint" type="type:HighPrecisionLocation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
The High Precision Latitude field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.
<xs:element name="highPrecisionLatitude" type="type:HighPrecisionLatitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The High Precision Latitude field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.</xs:documentation></xs:annotation></xs:element>
The “High Precision Longitude” field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.
<xs:element name="highPrecisionLongitude" type="type:HighPrecisionLongitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “High Precision Longitude” field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.</xs:documentation></xs:annotation></xs:element>
<xs:element name="fpapEllipsoidHeight" type="type:EllipsoidHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Ellipsoidal Height” field is the height of a surveyed point in reference to the WGS-84 ellipsoid.</xs:documentation></xs:annotation></xs:element>
<xs:element name="fpapOrthometricHeight" type="type:OrthometricHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Orthometric Height” field is the height of a surveyed point in reference to Mean Sea Level (MSL).</xs:documentation></xs:annotation></xs:element>
The “Glide Path Angle” field is an angle, expressed in degrees, tenths and hundredths of degrees, measured at the Flight Path Control Point (FPCP) of those approach procedures that require the coding of a Airport or Helicopter Operations SBAS Path Point record or GBAS Path Point Record. It establishes the intended descent gradient for the final approach flight path. For an illustration of the GPA and related points.
<xs:element name="glidePathAngle" type="type:GlidePathAngle" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Glide Path Angle” field is an angle, expressed in degrees, tenths and hundredths of degrees, measured at the Flight Path Control Point (FPCP) of those approach procedures that require the coding of a Airport or Helicopter Operations SBAS Path Point record or GBAS Path Point Record. It establishes the intended descent gradient for the final approach flight path. For an illustration of the GPA and related points.</xs:documentation></xs:annotation></xs:element>
The “GNSS Channel Number” field identifies the channel that will be decoded to identify the augmentation system used. The Channel Number is derived from official government sources and is entered as five numeric characters. It consists of numeric characters in the ranges 0000 to 9999 and 20001 to 99999. In general, numbers less than 20000 are reserved for ILS and MLS. In some countries, Channel Numbers from 0000 to 9999 are reserved for SCAT-1 and will be entered as 00000 through 09999. Channel Numbers from 20001 to 39999 are reserved for GBAS (and SBAS if applicable). Channel Numbers from 40000 to 99999 are reserved for SBAS.
<xs:element name="gnssChannelNumber" type="type:Channel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “GNSS Channel Number” field identifies the channel that will be decoded to identify the augmentation system used. The Channel Number is derived from official government sources and is entered as five numeric characters. It consists of numeric characters in the ranges 0000 to 9999 and 20001 to 99999. In general, numbers less than 20000 are reserved for ILS and MLS. In some countries, Channel Numbers from 0000 to 9999 are reserved for SCAT-1 and will be entered as 00000 through 09999. Channel Numbers from 20001 to 39999 are reserved for GBAS (and SBAS if applicable). Channel Numbers from 40000 to 99999 are reserved for SBAS.</xs:documentation></xs:annotation></xs:element>
The Helicopter Procedure Course field is used on Path Point Continuation Records to define the final approach course of procedures designed for helicopter operations to runways, to helipads, and to points in space..
<xs:element name="helicopterProcedureCourse" type="type:CourseValue" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Helicopter Procedure Course field is used on Path Point Continuation Records to define the final approach course of procedures designed for helicopter operations to runways, to helipads, and to points in space..</xs:documentation></xs:annotation></xs:element>
<xs:element name="landingThresholdPoint" type="type:HighPrecisionLocation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
The “Length Offset” field is the distance from the stop end of the runway (SER) to the FPAP. This distance defines the location where lateral sensitivity changes to the missed approach sensitivity. If the FPAP is located at the designated center of the opposite runway end, the distance is zero. Additionally, if the lenfth offset is not provided then the element should not exist.
<xs:element name="lengthOffset" type="type:LengthOffset" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Length Offset” field is the distance from the stop end of the runway (SER) to the FPAP. This distance defines the location where lateral sensitivity changes to the missed approach sensitivity. If the FPAP is located at the designated center of the opposite runway end, the distance is zero. Additionally, if the lenfth offset is not provided then the element should not exist.</xs:documentation></xs:annotation></xs:element>
<xs:element name="ltpEllipsoidHeight" type="type:EllipsoidHeight" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Ellipsoidal Height” field is the height of a surveyed point in reference to the WGS-84 ellipsoid.</xs:documentation></xs:annotation></xs:element>
<xs:element name="ltpOrthometricHeight" type="type:OrthometricHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Orthometric Height” field is the height of a surveyed point in reference to Mean Sea Level (MSL).</xs:documentation></xs:annotation></xs:element>
On procedures to runways or helipads, the Path Point TCH is the height above the runway threshold (LTP) or the helicopter alighting point. On procedures which are Point in Space, the height of the fictitious helipoint (or helipoint) above the height of the heliport. It is the same as the TCH defined in Section 5.67, but has greater resolution due to the required precision.
<xs:element name="pathPointTCH" type="type:PathPointTCH" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>On procedures to runways or helipads, the Path Point TCH is the height above the runway threshold (LTP) or the helicopter alighting point. On procedures which are Point in Space, the height of the fictitious helipoint (or helipoint) above the height of the heliport. It is the same as the TCH defined in Section 5.67, but has greater resolution due to the required precision.</xs:documentation></xs:annotation></xs:element>
The “Reference Path Data Selector” field enables the automatic tuning of a procedure by Ground Based Augmentation Systems (GBAS) avionics.This data is not used for SBAS operations.
<xs:element name="referencePathDataSelector" type="type:ReferencePathDataSelector" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Reference Path Data Selector” field enables the automatic tuning of a procedure by Ground Based Augmentation Systems (GBAS) avionics.This data is not used for SBAS operations.</xs:documentation></xs:annotation></xs:element>
The Reference Path Identifier field represents the three or four alphanumeric characters used to uniquely designate the reference path. The Reference Path Identifier is synonymous with the approach ID located beneath the Channel Number on Instrument Approach Plates and is unique only for a given airport.
<xs:element name="referencePathIdentifier" type="type:ReferencePathIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Reference Path Identifier field represents the three or four alphanumeric characters used to uniquely designate the reference path. The Reference Path Identifier is synonymous with the approach ID located beneath the Channel Number on Instrument Approach Plates and is unique only for a given airport.</xs:documentation></xs:annotation></xs:element>
The “Route Indicator” field is a single alpha character used to differentiate between multiple final approach segments to the same runway or helipad contained in the Final Approach Coding.
<xs:element name="routeIndicator" type="type:RouteIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Route Indicator” field is a single alpha character used to differentiate between multiple final approach segments to the same runway or helipad contained in the Final Approach Coding.</xs:documentation></xs:annotation></xs:element>
This XML element is designed as an abstraction for Runway Identifier or Pad Identifier, this is done by using the XML attribute "choice", so that only one of the elements can be present in the XML file.
<xs:element name="runwayOrPadIdentifier" type="type:RunwayOrPadIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This XML element is designed as an abstraction for Runway Identifier or Pad Identifier, this is done by using the XML attribute "choice", so that only one of the elements can be present in the XML file.</xs:documentation></xs:annotation></xs:element>
The “TCH Units Indicator” field is used in Path Point Records to define the units, Feet or Meters for the Path Point TCH. This element is included in the “CRC Wrap” a possible metric source value cannot be converted to feet.
the Path Point TCH is provided in source documentation in Feet
enumeration
Meters
Path Point TCH is provided in source documentation in meters
Source
<xs:element name="tchUnitsIndicator" type="enum:TCHUnitsIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “TCH Units Indicator” field is used in Path Point Records to define the units, Feet or Meters for the Path Point TCH. This element is included in the “CRC Wrap” a possible metric source value cannot be converted to feet.</xs:documentation></xs:annotation></xs:element>
Terminal Area Path definition (not for FAS Datablock)
enumeration
2
Missed Approach (not for FAS Datablock)
enumeration
3
Spare
enumeration
4
Spare
enumeration
5
Spare
enumeration
6
Spare
enumeration
7
Spare
enumeration
8
Spare
enumeration
9
Spare
enumeration
10
Spare
enumeration
11
Spare
enumeration
12
Spare
enumeration
13
Spare
enumeration
14
Spare
enumeration
15
Spare
Source
<xs:element name="operationType" type="enum:GBASOperationType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Operation Type” field indicates whether the operation is an approach procedure, an advanced operation or other operational to be defined later.</xs:documentation></xs:annotation></xs:element>
<xs:element name="sbasPathPoint" type="SBASPathPoint" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the SBAS path point for the approach</xs:documentation></xs:annotation></xs:element>
The Horizontal Alert Limit (HAL) is the radius of a circle in the horizontal plane (the local plane tangent to the WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated horizontal position with the required probability for a particular navigation mode assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.
<xs:element name="hal" type="type:HorizontalAlertLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Horizontal Alert Limit (HAL) is the radius of a circle in the horizontal plane (the local plane tangent to the WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated horizontal position with the required probability for a particular navigation mode assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.</xs:documentation></xs:annotation></xs:element>
<xs:element name="operationType" type="enum:SBASOperationType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Operation Type” field indicates whether the operation is an approach procedure, an advanced operation or other operational to be defined later.</xs:documentation></xs:annotation></xs:element>
Element SBASPathPoint / sbasServiceProviderIdentifier
Namespace
No namespace
Annotations
The “SBAS Service Provider Identifier” field is used to associate the approach procedure to a particular satellite based approach system service provider.
<xs:element name="sbasServiceProviderIdentifier" type="enum:SBASServiceProviderIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “SBAS Service Provider Identifier” field is used to associate the approach procedure to a particular satellite based approach system service provider.</xs:documentation></xs:annotation></xs:element>
The Vertical Alert Limit (VAL) is half the length of a segment on the vertical axis (perpendicular to the horizontal plane of WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated vertical position with a probability of 1-10-7 per approach, assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.
<xs:element name="val" type="type:VerticalAlertLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Vertical Alert Limit (VAL) is half the length of a segment on the vertical axis (perpendicular to the horizontal plane of WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated vertical position with a probability of 1-10-7 per approach, assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.</xs:documentation></xs:annotation></xs:element>
<xs:element name="FinalApproachCourse" type="type:Course"><xs:annotation><xs:documentation>The SBAS Final Approach Course field contains the published final approach course of the PBN procedure with SBAS level of service.</xs:documentation></xs:annotation></xs:element>
<xs:element name="approachTransition" type="ApproachTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the approach transitions for the approach.</xs:documentation></xs:annotation></xs:element>
This is the final approach route, which ends at the last part of the final before the missed approach. e.g., The last point of the final approach is often the missed approach point.
<xs:element name="finalApproach" type="FinalApproach" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This is the final approach route, which ends at the last part of the final before the missed approach. e.g., The last point of the final approach is often the missed approach point.</xs:documentation></xs:annotation></xs:element>
The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.
Designated Level of Service is authorized for the procedure
enumeration
NotAuthorized
Designated Level of Service is not authorized for the procedure
Source
<xs:element name="fasBlockProvided" type="enum:LevelOfServiceAuthorised" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.</xs:documentation></xs:annotation></xs:element>
Element FinalApproach / fasBlockProvidedLevelOfServiceName
Namespace
No namespace
Annotations
The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.
<xs:element name="fasBlockProvidedLevelOfServiceName" type="enum:LevelOfServiceName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.</xs:documentation></xs:annotation></xs:element>
The field indicates whether or not the existence and use of a remote altimeter setting is applicable to the procedure. The field is true when there is a restriction on the use of LNAV/VNAV (Baro-VNAV) lines of minimum.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isRemoteAltimeterRestricted" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field indicates whether or not the existence and use of a remote altimeter setting is applicable to the procedure. The field is true when there is a restriction on the use of LNAV/VNAV (Baro-VNAV) lines of minimum.</xs:documentation></xs:annotation></xs:element>
The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.
Designated Level of Service is authorized for the procedure
enumeration
NotAuthorized
Designated Level of Service is not authorized for the procedure
Source
<xs:element name="lnavAuthorisedForSBAS" type="enum:LevelOfServiceAuthorised" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.</xs:documentation></xs:annotation></xs:element>
The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.
<xs:element name="lnavLevelOfServiceName" type="enum:LevelOfServiceName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.</xs:documentation></xs:annotation></xs:element>
The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.
Designated Level of Service is authorized for the procedure
enumeration
NotAuthorized
Designated Level of Service is not authorized for the procedure
Source
<xs:element name="lnavVNAVAuthorisedForSBAS" type="enum:LevelOfServiceAuthorised" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.</xs:documentation></xs:annotation></xs:element>
The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.
<xs:element name="lnavVNAVLevelOfServiceName" type="enum:LevelOfServiceName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.</xs:documentation></xs:annotation></xs:element>
<xs:element name="procedureTCH" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element>
This field contains the RNP level of service in decimal e.g. 1.0
Diagram
Type
xs:decimal
Properties
content
simple
minOccurs
1
maxOccurs
1
Source
<xs:element name="rnp" type="xs:decimal" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This field contains the RNP level of service in decimal e.g. 1.0</xs:documentation></xs:annotation></xs:element>
<xs:element name="missedApproach" type="MissedApproach" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elments are the missed approach routes for a procedure.</xs:documentation></xs:annotation></xs:element>
<xs:element name="approachPointRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides a reference to the point served by this approach procedure. On an approach this would reference a runway or fix.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true the parent is an Rnav Visual.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isRnavVisual" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true the parent is an Rnav Visual.</xs:documentation></xs:annotation></xs:element>
This element indicates if the procedure is Point In Space with a instructions to procede visually.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPinsProceedVisually" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates if the procedure is Point In Space with a instructions to procede visually.</xs:documentation></xs:annotation></xs:element>
This element indicates if hte procedure is Point In Space with instructions to procedure under visual flight rules.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPinsProceedVfr" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates if hte procedure is Point In Space with instructions to procedure under visual flight rules.</xs:documentation></xs:annotation></xs:element>
If this element exists and is true th eparent is a localizer backcourse.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isLocalizerBackcourse" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true th eparent is a localizer backcourse.</xs:documentation></xs:annotation></xs:element>
<xs:element name="approachPbnNavSpec" type="enum:ApproachPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides informaiton on the ICAO PBN navigation specification applicable to the approach.</xs:documentation></xs:annotation></xs:element>
Preferred Multiple Approach Indicator is used to identify the multiple approach that is generally considered to be the most likely one to be utilized/needed when there are only multiple approaches available for a given approach type at a runway. This will be defined on the Approach FAF record in the Final Approach. For a given approach type at a runway, there shall be one and only one Primary Multiple Approach Indicator provided
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPreferredProcedure" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Preferred Multiple Approach Indicator is used to identify the multiple approach that is generally considered to be the most likely one to be utilized/needed when there are only multiple approaches available for a given approach type at a runway. This will be defined on the Approach FAF record in the Final Approach. For a given approach type at a runway, there shall be one and only one Primary Multiple Approach Indicator provided</xs:documentation></xs:annotation></xs:element>
Terminal Waypoint field contains all terminal waypoints and VFR waypoints within the geographical area of each airport/heliport. Terminal waypoints utilized by two or more airports will be stored in the Enroute Waypoint Subsection to eliminate duplication. Terminal waypoints used jointly by and airoprt and a heliport are also stored in the Enroute waypoint section.
<xs:element name="terminalWaypoint" type="TerminalWaypoint" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Terminal Waypoint field contains all terminal waypoints and VFR waypoints within the geographical area of each airport/heliport. Terminal waypoints utilized by two or more airports will be stored in the Enroute Waypoint Subsection to eliminate duplication. Terminal waypoints used jointly by and airoprt and a heliport are also stored in the Enroute waypoint section.</xs:documentation></xs:annotation></xs:element>
The “Name Format Indicator” field is used to describe the format of the “Waypoint Name/Description” field (5.43). This field will be formatted according to the rules described in Chapter 7 of this Specification, Waypoint Naming Conventions.
<xs:element name="nameFormatIndicator" type="type:NameFormatIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Name Format Indicator” field is used to describe the format of the “Waypoint Name/Description” field (5.43). This field will be formatted according to the rules described in Chapter 7 of this Specification, Waypoint Naming Conventions.</xs:documentation></xs:annotation></xs:element>
The “Waypoint Type” field identifies a number of data conditions.1. The first is whether or not the waypoint has been published in an official government source or created during database coding of routes or procedures.2. The second is whether or not the waypoint is an intersection formed with reference to ground based navaids or is an RNAV Waypoint formed by the latitude and longitude.3. The third is an indication of one or more functions assigned to that waypoint in terminal procedure coding.4. The fourth is an indication of location of the waypoint with reference to airspace boundaries and/or grid lines.5. The fifth is an indication of how ATC might be using the waypoint in operational clearances.6. The sixth is an indication that the waypoint has been published for VFR use only.7. Lastly, there is an indication of whether the waypoint is published for use in terminal procedure coding of a specific type, multiple types or not published at all.
<xs:element name="waypointType" type="type:WaypointType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Waypoint Type” field identifies a number of data conditions. 1. The first is whether or not the waypoint has been published in an official government source or created during database coding of routes or procedures. 2. The second is whether or not the waypoint is an intersection formed with reference to ground based navaids or is an RNAV Waypoint formed by the latitude and longitude. 3. The third is an indication of one or more functions assigned to that waypoint in terminal procedure coding. 4. The fourth is an indication of location of the waypoint with reference to airspace boundaries and/or grid lines. 5. The fifth is an indication of how ATC might be using the waypoint in operational clearances. 6. The sixth is an indication that the waypoint has been published for VFR use only. 7. Lastly, there is an indication of whether the waypoint is published for use in terminal procedure coding of a specific type, multiple types or not published at all.</xs:documentation></xs:annotation></xs:element>
This field applies to the intersection of concepts that apply to aspects of conventional navigation. e.g., a fix at DME 10.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isIntersectionDmeFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field applies to the intersection of concepts that apply to aspects of conventional navigation. e.g., a fix at DME 10.</xs:documentation></xs:annotation></xs:element>
<xs:element name="waypointUsage" type="type:WaypointUsage" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The waypoint usage field is employed to indicate the structure in which the waypoint is utilized.</xs:documentation></xs:annotation></xs:element>
The Airport TAA (Terminal Arrival Altitude) field contains the Sector Bearing, Sector Radii, and Section Altitudes for all government published Approach Procedures
<xs:element name="taa" type="TAA" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>The Airport TAA (Terminal Arrival Altitude) field contains the Sector Bearing, Sector Radii, and Section Altitudes for all government published Approach Procedures</xs:documentation></xs:annotation></xs:element>
<xs:element name="approachTypeIdentifier" type="type:ApproachTypeIdentifier" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>Identifies the approach types published on a given approach procedure which require Airport or Helicopter Operations SBAS path points.</xs:documentation></xs:annotation></xs:element>
The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.
The field will be blank if details and procedures are provided in both magnetic and true for the airport. In such cases the individual detail or procedure records will contain the magnetic or true information
enumeration
True
if all detail and procedure for the airport are reported in true bearing
enumeration
Magnetic
if all detail and procedure for the airport are reported in magnetic bearing,
Source
<xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element>
<xs:element name="taaFixPositionIndicator" type="enum:TAASectorIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>TThe Fix Position Indicator field contains an indication as to which TAA Initial Approach Fix (IAF) the data in the record applies.</xs:documentation></xs:annotation></xs:element>
<xs:element name="sectorTAADetails" type="type:TAASectorDetails" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a TAA Sector.</xs:documentation></xs:annotation></xs:element>
The “Sector Radius Start” field in TAA records defines the start distance that defines a TAA area. It is referenced to the TAA IAF Waypoint defined in that record. As TAA information is used towards that waypoint, the radius information is provided towards that waypoint. It encloses the sector defined in the record. The value is inclusive.
<xs:element name="sectorRadiusStart" type="type:RadiusLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Sector Radius Start” field in TAA records defines the start distance that defines a TAA area. It is referenced to the TAA IAF Waypoint defined in that record. As TAA information is used towards that waypoint, the radius information is provided towards that waypoint. It encloses the sector defined in the record. The value is inclusive.</xs:documentation></xs:annotation></xs:element>
The “Sector Radius End” field in TAA records defines the end distance that defines a TAA area. It is referenced to the TAA IAF Waypoint defined in that record. As TAA information is used towards that waypoint, the radius information is provided towards that waypoint. It encloses the sector defined in the record. The value is inclusive.
<xs:element name="sectorRadiusEnd" type="type:RadiusLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Sector Radius End” field in TAA records defines the end distance that defines a TAA area. It is referenced to the TAA IAF Waypoint defined in that record. As TAA information is used towards that waypoint, the radius information is provided towards that waypoint. It encloses the sector defined in the record. The value is inclusive.</xs:documentation></xs:annotation></xs:element>
The “TAA IAF Waypoint” field contains the identifier of the Initial Approach Fix (IAF) associated with a given Terminal Area Altitude sector. There may be one, two or three such IAF waypoints defined for a single approach procedure. The TAA IAF Waypoint identified in the TAA Sector with the identifier of “C” (Section 5.272) is the fix to which all sector bearing information for the procedure TAA is defined. The TAA IAF Waypoint in the individual TAA Sector records is the fix from which radius distances are defined.
<xs:element name="taaIAFWaypointReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “TAA IAF Waypoint” field contains the identifier of the Initial Approach Fix (IAF) associated with a given Terminal Area Altitude sector. There may be one, two or three such IAF waypoints defined for a single approach procedure. The TAA IAF Waypoint identified in the TAA Sector with the identifier of “C” (Section 5.272) is the fix to which all sector bearing information for the procedure TAA is defined. The TAA IAF Waypoint in the individual TAA Sector records is the fix from which radius distances are defined.</xs:documentation></xs:annotation></xs:element>
The Sector Bearing Reference Waypoint field contains the identifier of the waypoint that the Sector Bearings are referenced to within a given Terminal Area Altitude sector
Diagram
Type
xs:IDREF
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="sectorBearingWaypointRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Sector Bearing Reference Waypoint field contains the identifier of the waypoint that the Sector Bearings are referenced to within a given Terminal Area Altitude sector</xs:documentation></xs:annotation></xs:element>
<xs:element name="portCommunication" type="PortCommunication" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Port Communication field contain all government published airport communication facilites for particular airoprts.</xs:documentation></xs:annotation></xs:element>
<xs:element name="location" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.
At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
AtOrBelow
At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
At
At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.
enumeration
B
At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope
enumeration
C
"At or above" altitude specified in second "Altitude" field.
enumeration
G
Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.
enumeration
I
Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope
Source
<xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element>
The “Communication Altitude 1 and Altitude 2” fields are used to provide information on use of communication services frequencies with reference to specific altitudes. If the communication record in which Communication Altitude data is provided includes Sectorization data (5.183), the altitude data is valid only for the specific Sector.
<xs:element name="communicationAltitude1" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Altitude 1 and Altitude 2” fields are used to provide information on use of communication services frequencies with reference to specific altitudes. If the communication record in which Communication Altitude data is provided includes Sectorization data (5.183), the altitude data is valid only for the specific Sector.</xs:documentation></xs:annotation></xs:element>
The “Communication Altitude 1 and Altitude 2” fields are used to provide information on use of communication services frequencies with reference to specific altitudes. If the communication record in which Communication Altitude data is provided includes Sectorization data (5.183), the altitude data is valid only for the specific Sector.
<xs:element name="communicationAltitude2" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Altitude 1 and Altitude 2” fields are used to provide information on use of communication services frequencies with reference to specific altitudes. If the communication record in which Communication Altitude data is provided includes Sectorization data (5.183), the altitude data is valid only for the specific Sector.</xs:documentation></xs:annotation></xs:element>
The “Call Sign” field contains the name of a communication service provider that is to be used when contacting that service/used by the service to identify itself when contacting aircraft on the frequencies contained in the record. The field is also used to provide the broadcast identification name of automated services.
<xs:element name="callSign" type="type:CallSign" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Call Sign” field contains the name of a communication service provider that is to be used when contacting that service/used by the service to identify itself when contacting aircraft on the frequencies contained in the record. The field is also used to provide the broadcast identification name of automated services.</xs:documentation></xs:annotation></xs:element>
The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing control services to aircraft.
enumeration
LIRI
The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing information services to aircraft.
enumeration
USVC
The Communication Type is that of one used within an Information Region (FIR/UIR) for purposes other than control or information services and is not linked to that Region
enumeration
ASVC
The Communication Type is that of one providing automated or broadcast services within an Information Region (FIR/UIR).
enumeration
ATCF
The Communication Type is that of one providing ATC services to aircraft within the terminal area of an airport.
enumeration
GNDF
The Communication Type is that of one providing ATC services to aircraft on the ground at an airport.
enumeration
AOTF
The Communication Type is that of one providing services other than ATC functions on the ground or within the terminal area of an airport.
enumeration
AFAC
The Communication Type is that of one provided automated or broadcast services to aircraft on the ground or with the terminal area of an airport.
Source
<xs:element name="communicationClass" type="enum:CommunicationClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Class” field will designate the major grouping of the Communication Types contained in the record.</xs:documentation></xs:annotation></xs:element>
The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.
<xs:element name="communicationType" type="enum:CommunicationType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.</xs:documentation></xs:annotation></xs:element>
The “Frequency Units” field will designate the frequency spectrum area for the frequency in the “Communication Frequency” (Section 5.103) field as indicated in the table or will designate the content of the “Communication Frequency” field as a channel. For VHF based units, the field will also designate the established frequency spacing required of the frequency for unambiguous use.
Very High Frequency (30,000 kHz to 200 MHz) Non-standard spacing
enumeration
Uhf
Ultra High Frequency (200 MHz to 3000 MHz)
enumeration
Vhf8_33Spacing
Very High Frequency Communication Channel for 8.33kHz spacing
enumeration
DigitalService
Digital Service
Source
<xs:element name="frequencyUnits" type="enum:FrequencyUnits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Frequency Units” field will designate the frequency spectrum area for the frequency in the “Communication Frequency” (Section 5.103) field as indicated in the table or will designate the content of the “Communication Frequency” field as a channel. For VHF based units, the field will also designate the established frequency spacing required of the frequency for unambiguous use.</xs:documentation></xs:annotation></xs:element>
The “Radar” field indicates whether or not the communication unit identified in the record has access to and uses information derived from primary or secondary radars while performing the communication service indicated by the Communication Type. It is not an indication of an operational radar frequency.
Primary or secondary Radar information is available to the service
enumeration
No
If the Service documentation specifically states that the service does not have access to primary or secondary radar information
enumeration
Unknown
If the Source documentation does not provide details on the radar information access for the services
Source
<xs:element name="radarService" type="enum:Radar" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Radar” field indicates whether or not the communication unit identified in the record has access to and uses information derived from primary or secondary radars while performing the communication service indicated by the Communication Type. It is not an indication of an operational radar frequency.</xs:documentation></xs:annotation></xs:element>
The “24H Indicator” field is used to indicate whether a communication service frequency is available for use on a continual, i.e. 24 hours a day, seven days a week, basis or not.
<xs:element name="h24Indicator" type="enum:H24Indicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “24H Indicator” field is used to indicate whether a communication service frequency is available for use on a continual, i.e. 24 hours a day, seven days a week, basis or not.</xs:documentation></xs:annotation></xs:element>
<xs:element name="modulation" type="enum:Modulation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Modulation” field will design the type of modulation for the frequency in the “Communication Frequency” (5.103) field.</xs:documentation></xs:annotation></xs:element>
When used on Enroute, Airport and Heliport Communication Primary and Continuation records, the Sequence Number is used as a record counter within a given Identifier and Communication Class for providing output file record uniqueness. (See ARINC 424 5.12)
<xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>When used on Enroute, Airport and Heliport Communication Primary and Continuation records, the Sequence Number is used as a record counter within a given Identifier and Communication Class for providing output file record uniqueness. (See ARINC 424 5.12)</xs:documentation></xs:annotation></xs:element>
High Frequency (HF) signals used in aeronautical communications can be the complete signal or a portion of the signal, called a sideband. The “Signal Emission” field will designate for each HF Frequency what emission is used.
<xs:element name="signalEmission" type="enum:SignalEmission" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>High Frequency (HF) signals used in aeronautical communications can be the complete signal or a portion of the signal, called a sideband. The “Signal Emission” field will designate for each HF Frequency what emission is used.</xs:documentation></xs:annotation></xs:element>
The Communication Frequency field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.
<xs:element name="transmitFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Communication Frequency field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.</xs:documentation></xs:annotation></xs:element>
The Communication Frequency field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.
<xs:element name="receiveFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Communication Frequency field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.</xs:documentation></xs:annotation></xs:element>
<xs:element name="communicationDetails" type="CommunicationDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Information contained in the ARINC 424 communication continuation records</xs:documentation></xs:annotation></xs:element>
The “Remote Facility” field is used to identify a Navaid or Airport that has been used to provide the latitude/longitude of a communication transmitter, Figure 5-8 and Notes 7 and 8 in Section 5.37 of this Specification.
<xs:element name="remoteFacility" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Remote Facility” field is used to identify a Navaid or Airport that has been used to provide the latitude/longitude of a communication transmitter, Figure 5-8 and Notes 7 and 8 in Section 5.37 of this Specification.</xs:documentation></xs:annotation></xs:element>
This field supports specifying the same time interval on multiple days of the week in a single interval instance. It should not be used if the "dayOfWeek" in the start and end times is specified (see documentation for StartOrEndTime). If this field is used, and the "end" time is earlier than the "start" time, the time interval crosses midnight (00:00).
<xs:element name="dayOfWeek" type="enum:DayOfWeek" minOccurs="0" maxOccurs="7"><xs:annotation><xs:documentation>This field supports specifying the same time interval on multiple days of the week in a single interval instance. It should not be used if the "dayOfWeek" in the start and end times is specified (see documentation for StartOrEndTime). If this field is used, and the "end" time is earlier than the "start" time, the time interval crosses midnight (00:00).</xs:documentation><!-- TIMEX: How to indicate an interval that rolls past midnight --></xs:annotation></xs:element>
This field supports specifying a continuous time interval across multiple days. It should not be used if the "dayOfWeek" in TimeOfOperationInterval is specified. If used, it should be specified for both start and end times, and they should be different otherwise the TimeOfOperationInterval field should be used.
<xs:element name="dayOfWeek" type="enum:DayOfWeek" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field supports specifying a continuous time interval across multiple days. It should not be used if the "dayOfWeek" in TimeOfOperationInterval is specified. If used, it should be specified for both start and end times, and they should be different otherwise the TimeOfOperationInterval field should be used.</xs:documentation></xs:annotation></xs:element>
This field represents the start or end time of the TimeOfOperationInterval. A timezone may be set for this field, in which case the time is specified in the local timezone. If no timezone is set, UTC is assumed. If a timezone is set indicating a local time, it should be the same for both start and end times, and the "adjustForDST" field in the enclosing TimesOfOperation instance may be set to indicate that the time follows daylight saving time in accordance with the local DST calendar.
Diagram
Type
xs:time
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="time" type="xs:time" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field represents the start or end time of the TimeOfOperationInterval. A timezone may be set for this field, in which case the time is specified in the local timezone. If no timezone is set, UTC is assumed. If a timezone is set indicating a local time, it should be the same for both start and end times, and the "adjustForDST" field in the enclosing TimesOfOperation instance may be set to indicate that the time follows daylight saving time in accordance with the local DST calendar.</xs:documentation></xs:annotation></xs:element>
This field supports specifying the StartOrEndTime as an offset from sunrise or sunset. In this case, the "time" field is just the offset amount such as 01:00:00 or 00:30:00. If used, there should be no timezone set in the "time" field.
<xs:element name="relativeTimeIndicator" type="enum:RelativeTimeIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field supports specifying the StartOrEndTime as an offset from sunrise or sunset. In this case, the "time" field is just the offset amount such as 01:00:00 or 00:30:00. If used, there should be no timezone set in the "time" field.</xs:documentation></xs:annotation></xs:element>
The “Time Narrative” field is used to provide Time of Operations and/or Conditions of Operations in a narrative form when source information is too complex to be formatted in accordance with ARINC 424 Section 5.195. This field is used in conjunction with the TimeCode value "Complex". This field is used on Airport, Heliport, and Enroute Communication Continuation records.
Diagram
Type
xs:string
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="timeNarrative" type="xs:string" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Time Narrative” field is used to provide Time of Operations and/or Conditions of Operations in a narrative form when source information is too complex to be formatted in accordance with ARINC 424 Section 5.195. This field is used in conjunction with the TimeCode value "Complex". This field is used on Airport, Heliport, and Enroute Communication Continuation records.</xs:documentation></xs:annotation></xs:element>
Restrictive Airspace areas and communications facilities may not have established active times and are activated by NOTAM only or may be active by NOTAM in addition to established times. If this field is "True", the area or communcations facility is active by NOTAM in addition to the specified time intervals. If the the area or communication facility is active by NOTAM only, this field should not be used and the timeCode "ByNotam" should be used. Used on Controlled and Restrictive Airspace Primary and Continuation records, and Airport, Heliport and Enroute Communications Continuation records.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="byNotam" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Restrictive Airspace areas and communications facilities may not have established active times and are activated by NOTAM only or may be active by NOTAM in addition to established times. If this field is "True", the area or communcations facility is active by NOTAM in addition to the specified time intervals. If the the area or communication facility is active by NOTAM only, this field should not be used and the timeCode "ByNotam" should be used. Used on Controlled and Restrictive Airspace Primary and Continuation records, and Airport, Heliport and Enroute Communications Continuation records.</xs:documentation></xs:annotation></xs:element>
Indicates that the "times" instances in this record follow daylight saving time in accordance with the local DST calendar. (See documentation for the "time" field in the StartOrEndTime records.)
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="adjustForDST" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Indicates that the "times" instances in this record follow daylight saving time in accordance with the local DST calendar. (See documentation for the "time" field in the StartOrEndTime records.)</xs:documentation></xs:annotation></xs:element>
<xs:element name="transmitterSiteElevation" type="type:FacilityElevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Facility Elevation” field provides the elevation of navaids and communication transmitters</xs:documentation></xs:annotation></xs:element>
The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.
<xs:element name="transmitterSiteMagVar" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.</xs:documentation></xs:annotation></xs:element>
The “Guard/Transmit” field is used to indicate if the frequency shown in the Communication Frequency field is used, by the station, to receive voice communication or to transmit voice on.
Diagram
Type
xs:string
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="guardTransmit" type="xs:string" minOccurs="0" maxOccurs="1"><!-- Legacy 424-18 support --><xs:annotation><xs:documentation>The “Guard/Transmit” field is used to indicate if the frequency shown in the Communication Frequency field is used, by the station, to receive voice communication or to transmit voice on.</xs:documentation></xs:annotation></xs:element>
The “Communication Distance” field is used to define the distance restriction a communication frequency is to be used within or beyond when such restrictions apply. This field is used in conjunction with the Distance Description field.
<xs:element name="communicationDistance" type="type:CommunicationDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Distance” field is used to define the distance restriction a communication frequency is to be used within or beyond when such restrictions apply. This field is used in conjunction with the Distance Description field.</xs:documentation></xs:annotation></xs:element>
The “Distance Description” field will designate whether a communication frequency is to be used from the facility out to a specified distance or from a specified distance and beyond in the Airport Communication Record. In the VHF Navaid Limitation Continuation Record, the field is used to define whether the limitation applies from the navaid out to a specified distance or from a specified distance and beyond.
The communication frequency or navaid limitation is out to a specified distance.
enumeration
AppliesBeyondDistance
The communication frequency is used or the navaid limitation applies beyond a specified distance
enumeration
NoRestriction
no restrictions/limitations apply
Source
<xs:element name="distanceDescription" type="enum:DistanceDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance Description” field will designate whether a communication frequency is to be used from the facility out to a specified distance or from a specified distance and beyond in the Airport Communication Record. In the VHF Navaid Limitation Continuation Record, the field is used to define whether the limitation applies from the navaid out to a specified distance or from a specified distance and beyond.</xs:documentation></xs:annotation></xs:element>
The “Multi-Sector Indicator” field is used to indicate that the communication service and frequency are used in more than one defined sector. The actual sector data will be contained in the primary and continuation records of the affected airport or heliport communication record set.
Multi-sector data is published in official government source for the service and frequency
enumeration
NotDefined
There is no defined sector data published for the service and frequency.
enumeration
OnlyOneFromSource
The official government source has provided only a single defined sector for the service and frequency
Source
<xs:element name="multiSectorIndicator" type="enum:MultiSectorIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Multi-Sector Indicator” field is used to indicate that the communication service and frequency are used in more than one defined sector. The actual sector data will be contained in the primary and continuation records of the affected airport or heliport communication record set.</xs:documentation></xs:annotation></xs:element>
<xs:element name="portCommunicationSectorizationNarrative" type="type:SectorizationNarrative" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Port Communication Sectorization Narrative Class description.</xs:documentation></xs:annotation></xs:element>
<xs:element name="sectorFacility" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Sector Facility” field is used to define the Navaid or Airport upon which the information in the “Sector” (5.183) field is based.</xs:documentation></xs:annotation></xs:element>
The “Sectorization” field is used to define the airspace sector a communication frequency is applicable for when an airport defines sectors by bearing from the same point.
<xs:element name="sectorization" type="type:Sectorization" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Sectorization” field is used to define the airspace sector a communication frequency is applicable for when an airport defines sectors by bearing from the same point.</xs:documentation></xs:annotation></xs:element>
<xs:element name="serviceIndicator" type="type:AirportHeliportCommunicationServiceIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Service Indicator” field is used to further define the use of the frequency for the specified Communication Type (5.101).</xs:documentation></xs:annotation></xs:element>
<xs:element name="additionalSectorization" type="type:AdditionalSectorization" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This element is used to represent the details for an Additional Sectorization used in port communications.</xs:documentation></xs:annotation></xs:element>
At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
AtOrBelow
At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
At
At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.
enumeration
B
At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope
enumeration
C
"At or above" altitude specified in second "Altitude" field.
enumeration
G
Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.
enumeration
I
Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope
<xs:element name="helipad" type="Helipad" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Helipad field will contain a listing of all helipads associated with airports.</xs:documentation></xs:annotation></xs:element>
This element is the X dimension of a rectanglular pad.
Diagram
Type
xs:int
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="padDimensionX" type="xs:int" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the X dimension of a rectanglular pad.</xs:documentation></xs:annotation></xs:element>
This element is the Y dimension of a rectanglular pad.
Diagram
Type
xs:int
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="padDimensionY" type="xs:int" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the Y dimension of a rectanglular pad.</xs:documentation></xs:annotation></xs:element>
This element provides the pad radius if it is not a square or rectangle
Diagram
Type
xs:int
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="padRadius" type="xs:int" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the pad radius if it is not a square or rectangle</xs:documentation></xs:annotation></xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="helipadShape" type="enum:HelipadShape"><xs:annotation><xs:documentation>This element provides the shape of the helipad.</xs:documentation></xs:annotation></xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="maximumHelicopterWeight" type="type:MaxHelicopterWeight"><xs:annotation><xs:documentation>This element provides the maximum weight for helicopters using this helipad.</xs:documentation></xs:annotation></xs:element>
<xs:element minOccurs="0" name="helicopterPerformanceReq" type="enum:HelicopterPerformanceReq"><xs:annotation><xs:documentation>This element provides performance requirements for helicopters using this helipad.</xs:documentation></xs:annotation></xs:element>
The Airport and Heliport Localizer Marker field contains details about all markers and locators associated with all types of localizers. It does not contain airway marker.
<xs:element name="localizerMarker" type="AirportHeliportLocalizerMarker" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>The Airport and Heliport Localizer Marker field contains details about all markers and locators associated with all types of localizers. It does not contain airway marker.</xs:documentation></xs:annotation></xs:element>
<xs:element name="elevation" type="type:Elevation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Facility Elevation field provides the elevation of navaids and communication transmitters.</xs:documentation></xs:annotation></xs:element>
The “Localizer/MLS/GLS Identifier” field identifies the localizer, MLS facility or GLS Ref Path defined in the record. In the Runway Record, two “Landing Systems” may be defined.
<xs:element name="localizerReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/MLS/GLS Identifier” field identifies the localizer, MLS facility or GLS Ref Path defined in the record. In the Runway Record, two “Landing Systems” may be defined.</xs:documentation></xs:annotation></xs:element>
The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.
<xs:element name="locatorClass" type="LocatorClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.</xs:documentation></xs:annotation></xs:element>
Automatic Transcribed Weather.The frequency of this Navaid is used for the continuous broadcast of some sort of automated weather system such as AWOS, ASOS, TWEB, AWIB, AWIS.
enumeration
SCHEDULED
Broadcast Scheduled Weather.The frequency of this Navaid is used for the scheduled, noncontinuous broadcast of some sort of automated weather system such as VOLMET.
The “Facility Characteristics” field identifies the characteristics of the NAVAID facility.
Diagram
Type
xs:string
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="locatorFacilityCharacteristics" type="xs:string" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Facility Characteristics” field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation></xs:element>
<xs:element name="locatorFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “VOR/NDB Frequency” field specifies the frequency of the NAVAID identified in the “VOR/NDB Identifier” field of the record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="markerType" type="enum:MarkerType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Marker Type” field defines the type of marker.</xs:documentation></xs:annotation></xs:element>
<xs:element name="minorAxisBearing" type="type:MinorAxisBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Minor Axis Bearing” field indicates the true bearing of the minor axis of marker beacons.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwayIdentifier" type="type:RunwayIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Identifier” fieldidentifies the runways described in runway records andrunways served by the ILS/MLS described in ILS/MLSrecords.</xs:documentation></xs:annotation></xs:element>
Localizer Glidescope field should contain all government published localizer type facilities to airport runways and/or helipad. As a minimum, this field should contain all localizer type facilities.
<xs:element name="localizerGlideslope" type="LocalizerGlideslope" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Localizer Glidescope field should contain all government published localizer type facilities to airport runways and/or helipad. As a minimum, this field should contain all localizer type facilities.</xs:documentation></xs:annotation></xs:element>
The “Glide Slope Angle” field defines the glide slope angle of an ILS facility/GLS approach. The “Minimum Elevation Angle” field defines the lowest elevation angle authorized for the MLS procedure.
<xs:element name="approachAngle" type="type:PrecisionApproachAngle" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Glide Slope Angle” field defines the glide slope angle of an ILS facility/GLS approach. The “Minimum Elevation Angle” field defines the lowest elevation angle authorized for the MLS procedure.</xs:documentation></xs:annotation></xs:element>
The “Localizer Bearing” field defines the magnetic bearing of the localizer course of the ILS facility/GLS approach described in the record. The “MLS Azimuth Bearing” and the “MLS Back Azimuth Bearing” fields define the inbound magnetic final approach course assigned to the center of the Azimuth or Back Azimuth Coverage (see Section 6.172).
<xs:element name="approachCourseBearing" type="type:Bearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer Bearing” field defines the magnetic bearing of the localizer course of the ILS facility/GLS approach described in the record. The “MLS Azimuth Bearing” and the “MLS Back Azimuth Bearing” fields define the inbound magnetic final approach course assigned to the center of the Azimuth or Back Azimuth Coverage (see Section 6.172).</xs:documentation></xs:annotation></xs:element>
The Localizer/MLS/GLS Performance Categories have established operating minimums and are listed as Category I, II, and III. The level of Performance Category does not imply that permission exists to use the facility for landing guidance to that level and does not limit minimal using designated classification. This field is also used to define the classification, non- ILS/MLS/GLS, and localizer installation such as IGS, LDA, or SDF. As used in the runway record, there are two fields, one labeled Localizer/MLS/GLS Category/Classification and the other labeled Second Localizer/MLS/GLS Category/Classification.
<xs:element name="category" type="enum:PrecisionApproachCategory" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Localizer/MLS/GLS Performance Categories have established operating minimums and are listed as Category I, II, and III. The level of Performance Category does not imply that permission exists to use the facility for landing guidance to that level and does not limit minimal using designated classification. This field is also used to define the classification, non- ILS/MLS/GLS, and localizer installation such as IGS, LDA, or SDF. As used in the runway record, there are two fields, one labeled Localizer/MLS/GLS Category/Classification and the other labeled Second Localizer/MLS/GLS Category/Classification.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwayIdentifier" type="type:RunwayIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Identifier” field identifies the runways described in runway records and runways served by the ILS/MLS described in ILS/MLSrecords.</xs:documentation></xs:annotation></xs:element>
The “Approach Route Identifier” field contains the identifier of the approach route to be flown. To facilitate the provision of multiple approach procedures of the same type to a given runway, the field also is used to provide a “multiple indicator.”
<xs:element name="approachRouteIdent" type="type:CoreIdentifier" minOccurs="0" maxOccurs="4"><xs:annotation><xs:documentation>The “Approach Route Identifier” field contains the identifier of the approach route to be flown. To facilitate the provision of multiple approach procedures of the same type to a given runway, the field also is used to provide a “multiple indicator.”</xs:documentation></xs:annotation></xs:element>
<xs:element name="glideslopeBeamWidth" type="type:GlideslopeBeamWidth" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Glide Slope Beam Width” field specifies the glide path beam width of the Glide Slope defined in the record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="glideslopeHeightAtLandingThreshold" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element>
<xs:element name="glideslopeLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
For Localizer and Azimuth positions the field is blank (@) when the antenna is situated beyond the stop end of the runway,For Back Azimuth positions the field is blank (@) when the antenna is situated ahead of the approach end of the runway
enumeration
BeforeApproachEnd
For Localizer and Azimuth positions the field contains a plus (+) sign when the antenna is situated ahead of the approach end of the runwayFor Back Azimuth positions the field contains a plus (+) sign when the antenna is situated beyond the stop end of the runway
enumeration
OffToSide
For Localizer and Azimuth positions the field contains a plus (-) sign when the antenna is located off to one side of the runwayFor Back Azimuth positions the field contains a plus (-) sign when it is located off to one side of the runway.
Source
<xs:element name="localizerPositionReference" type="enum:LocalizerAzimuthPositionReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Element which encapsulates the localizer details for the corresponding Runway. This element contains the localizer ident and localizer class.</xs:documentation></xs:annotation></xs:element>
The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth andRunway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.
<xs:element name="localizerTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element>
“True Bearing” is derived from official government sources.
enumeration
Other
“True Bearing" is derived from other sources
Source
<xs:element name="localizerTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element>
For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.
<xs:element name="stationDeclination" type="type:StationDeclination" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.</xs:documentation></xs:annotation></xs:element>
<xs:element name="supportingFacilityReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “VOR/NDB Identifier” field identifies the VHF/MF/LF facility defined in the record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="serviceVolumneRadius" type="type:ServiceVolumeRadius" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The service volume radius identifies the radius of the service volume around the transmitter in Nautical miles.</xs:documentation></xs:annotation></xs:element>
<xs:element name="stationElevationWGS84" type="type:StationElevationWGS84" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field identifies the WGS84 elevation of the GLS ground station described in the record.</xs:documentation></xs:annotation></xs:element>
The station type identifies the type of the differential ground station. The first character will be L for LAAS/GLS ground station, C for SCAT-1 station. The second and third character will be blank for the moment. They will indicate the interoperability standard to which the station conforms.
<xs:element name="stationType" type="type:StationType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The station type identifies the type of the differential ground station. The first character will be L for LAAS/GLS ground station, C for SCAT-1 station. The second and third character will be blank for the moment. They will indicate the interoperability standard to which the station conforms.</xs:documentation></xs:annotation></xs:element>
The TDMA identifies the time slot(s) in which the ground station transmits the related approach. The high precision time source available through GPS permits utilization of Time division multiplexing or TDMA (Time Division Multiple Access), allowing multiple ground stations to share a common frequency by dividing it into eight time slots. An individual station may broadcast in one or more of eight slots.
<xs:element name="tdmaSlots" type="type:TDMASlots" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The TDMA identifies the time slot(s) in which the ground station transmits the related approach. The high precision time source available through GPS permits utilization of Time division multiplexing or TDMA (Time Division Multiple Access), allowing multiple ground stations to share a common frequency by dividing it into eight time slots. An individual station may broadcast in one or more of eight slots.</xs:documentation></xs:annotation></xs:element>
The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.
<xs:element name="azimuthCoverageLeft" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element>
The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.
<xs:element name="azimuthCoverageRight" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element>
<xs:element name="azimuthPosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position” field defines the location of the facility antenna relative to one end of the runway.</xs:documentation></xs:annotation></xs:element>
The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.
For Localizer and Azimuth positions the field is blank (@) when the antenna is situated beyond the stop end of the runway,For Back Azimuth positions the field is blank (@) when the antenna is situated ahead of the approach end of the runway
enumeration
BeforeApproachEnd
For Localizer and Azimuth positions the field contains a plus (+) sign when the antenna is situated ahead of the approach end of the runwayFor Back Azimuth positions the field contains a plus (+) sign when the antenna is situated beyond the stop end of the runway
enumeration
OffToSide
For Localizer and Azimuth positions the field contains a plus (-) sign when the antenna is located off to one side of the runwayFor Back Azimuth positions the field contains a plus (-) sign when it is located off to one side of the runway.
Source
<xs:element name="azimuthPositionReference" type="enum:LocalizerAzimuthPositionReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.</xs:documentation></xs:annotation></xs:element>
The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.
<xs:element name="azimuthProportionalAngleLeft" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element>
The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.
<xs:element name="azimuthProportionalAngleRight" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element>
<xs:element name="elevationAngleSpan" type="type:ElevationAngleSpan" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Elevation Angle Span” field defines the scan of the elevation transmitter signal between the lower and upper limits</xs:documentation></xs:annotation></xs:element>
<xs:element name="elevationLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point's elevation component.</xs:documentation></xs:annotation></xs:element>
<xs:element name="elevationPosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Elevation Position” field defines the location of the antenna with respect to the approach end of the runway.</xs:documentation></xs:annotation></xs:element>
The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth andRunway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.
<xs:element name="azimuthTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element>
“True Bearing” is derived from official government sources.
enumeration
Other
“True Bearing" is derived from other sources
Source
<xs:element name="azimuthTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element>
The “MLS Azimuth Bearing” and the “MLS Back Azimuth Bearing” fields define the inbound magnetic final approach course assigned to the center of the Azimuth or Back Azimuth Coverage (see Section 6.172).
<xs:element name="backAzimuthBearing" type="type:Bearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “MLS Azimuth Bearing” and the “MLS Back Azimuth Bearing” fields define the inbound magnetic final approach course assigned to the center of the Azimuth or Back Azimuth Coverage (see Section 6.172).</xs:documentation></xs:annotation></xs:element>
The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.
<xs:element name="backAzimuthCoverageLeft" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element>
The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.
<xs:element name="backAzimuthCoverageRight" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element>
<xs:element name="backAzimuthPosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position” field defines the location of the facility antenna relative to one end of the runway.</xs:documentation></xs:annotation></xs:element>
The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.
For Localizer and Azimuth positions the field is blank (@) when the antenna is situated beyond the stop end of the runway,For Back Azimuth positions the field is blank (@) when the antenna is situated ahead of the approach end of the runway
enumeration
BeforeApproachEnd
For Localizer and Azimuth positions the field contains a plus (+) sign when the antenna is situated ahead of the approach end of the runwayFor Back Azimuth positions the field contains a plus (+) sign when the antenna is situated beyond the stop end of the runway
enumeration
OffToSide
For Localizer and Azimuth positions the field contains a plus (-) sign when the antenna is located off to one side of the runwayFor Back Azimuth positions the field contains a plus (-) sign when it is located off to one side of the runway.
Source
<xs:element name="backAzimuthPositionReference" type="enum:LocalizerAzimuthPositionReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.</xs:documentation></xs:annotation></xs:element>
The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.
<xs:element name="backAzimuthProportionalSectorLeft" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element>
The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.
<xs:element name="backAzimuthProportionalSectorRight" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element>
The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth andRunway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.
<xs:element name="backAzimuthTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element>
“True Bearing” is derived from official government sources.
enumeration
Other
“True Bearing" is derived from other sources
Source
<xs:element name="backAzimuthTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element>
<xs:element name="glidePathHeightAtLandingThreshold" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element>
<xs:element name="mlsDatumPointLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
<xs:element name="nominalElevationAngle" type="type:NominalElevationAngle" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Nominal Elevation Angle” field defines the normal glide path angle for the MLS installation.</xs:documentation></xs:annotation></xs:element>
<xs:element name="supportingFacilityReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “VOR/NDB Identifier” field identifies the VHF/MF/LF facility defined in the record.</xs:documentation></xs:annotation></xs:element>
When used on Airport and Heliport MSA Records, the “Center Fix” field represents the MSA Center; that point (Navaid or Waypoint) on which the MSA is predicated. When used on Terminal Procedure Records, it can be used in three ways:1. When the terminal procedure has an MSA defined, the field will contain the identifier of the fix on which the MSA is predicated. This will serve as a pointer to the specific MSA (PS) Record. This will be populated on the Final Approach Fix (FAF) Record only.2. When the terminal procedure has a TAA defined, the field will contain the identifier of the fix on which the TAA Sector is predicated. This will serve as a pointer to the specific TAA (PK) Record. This will be populated on the first record for each approach transition.3. When used in a terminal procedure record defined by an “RF” Path Terminator, the field will contain the fix that defines the center of the constant rate turn. If the RF Leg terminates at the FAF, where the MSA Center Fix information would normally be found, the RF Center Fix takes priority and the MSA Center Fix pointer will be moved to the FACF record.
<xs:element name="centerFix" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When used on Airport and Heliport MSA Records, the “Center Fix” field represents the MSA Center; that point (Navaid or Waypoint) on which the MSA is predicated. When used on Terminal Procedure Records, it can be used in three ways: 1. When the terminal procedure has an MSA defined, the field will contain the identifier of the fix on which the MSA is predicated. This will serve as a pointer to the specific MSA (PS) Record. This will be populated on the Final Approach Fix (FAF) Record only. 2. When the terminal procedure has a TAA defined, the field will contain the identifier of the fix on which the TAA Sector is predicated. This will serve as a pointer to the specific TAA (PK) Record. This will be populated on the first record for each approach transition. 3. When used in a terminal procedure record defined by an “RF” Path Terminator, the field will contain the fix that defines the center of the constant rate turn. If the RF Leg terminates at the FAF, where the MSA Center Fix information would normally be found, the RF Center Fix takes priority and the MSA Center Fix pointer will be moved to the FACF record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="icaoCode" type="type:IcaoCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ICAO Code” field permits records to be categorized geographically within the limits of the categorization performed by the “Area Code” field.</xs:documentation></xs:annotation></xs:element>
The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.
The field will be blank if details and procedures are provided in both magnetic and true for the airport. In such cases the individual detail or procedure records will contain the magnetic or true information
enumeration
True
if all detail and procedure for the airport are reported in true bearing
enumeration
Magnetic
if all detail and procedure for the airport are reported in magnetic bearing,
Source
<xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element>
The “Multiple Code” field will be used to indicate Restrictive Airspace Areas or MSA Centers having the same designator but subdivided or differently divided by lateral and/or vertical detail.
<xs:element name="multipleCode" type="type:MultipleCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Multiple Code” field will be used to indicate Restrictive Airspace Areas or MSA Centers having the same designator but subdivided or differently divided by lateral and/or vertical detail.</xs:documentation></xs:annotation></xs:element>
<xs:element name="sector" type="type:Sector" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class represents the details for a MSA Sector.</xs:documentation></xs:annotation></xs:element>
Element Port / flightPlanningArrivalDepartureRecords
Namespace
No namespace
Annotations
Flight Planning Arrival/Departure record is used to provide the sub-set of data defining SIDs, STARs, and Approach Procedures required for the computer generation of Flight Plans whihc include Terminal Procedure. This contains a sequential listing of published Arrival Procedures, Approach Procedures and Departure Procedures, the availabel Enroute and Runway Transitions for those procedures, the Transition waypoints, the appropriate along track distance fields, and the intermediate fixed along those routes.
<xs:element name="flightPlanningArrivalDepartureRecords" type="FlightPlanningRecords" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Flight Planning Arrival/Departure record is used to provide the sub-set of data defining SIDs, STARs, and Approach Procedures required for the computer generation of Flight Plans whihc include Terminal Procedure. This contains a sequential listing of published Arrival Procedures, Approach Procedures and Departure Procedures, the availabel Enroute and Runway Transitions for those procedures, the Transition waypoints, the appropriate along track distance fields, and the intermediate fixed along those routes.</xs:documentation></xs:annotation></xs:element>
The “Altitude” field used on Flight Planning Arrival/Departure Data Records is a simplification of the altitude concept used in the full procedure records. It will provide an altitude indication in hundreds of feet, no AGL, MSL, FL etc indication provided.
<xs:element name="altitude" type="type:FlightPlanningAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Altitude” field used on Flight Planning Arrival/Departure Data Records is a simplification of the altitude concept used in the full procedure records. It will provide an altitude indication in hundreds of feet, no AGL, MSL, FL etc indication provided.</xs:documentation></xs:annotation></xs:element>
The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.
At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
AtOrBelow
At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
At
At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.
enumeration
B
At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope
enumeration
C
"At or above" altitude specified in second "Altitude" field.
enumeration
G
Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.
enumeration
I
Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope
Source
<xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element>
The “ATC Identifier” field used on Flight Planning Arrival/Departure Data Records is the indication of the officially published procedure designation which is required for Flight Planning.
<xs:element name="atcIdentifier" type="type:ATCIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ATC Identifier” field used on Flight Planning Arrival/Departure Data Records is the indication of the officially published procedure designation which is required for Flight Planning.</xs:documentation></xs:annotation></xs:element>
The “ATC Weight Category” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, a specific aircraft weight grouping.
Heavy, all aircraft types of 136,000kg (300000LB) or more.
enumeration
Medium
Medium, aircraft types less than 136,000kg (300,000LB) and more than 7,000kg (155,000LB).
enumeration
Light
Light, aircraft types of 7,000kg (155,000LB) or less
Source
<xs:element name="atcWeightCategory" type="enum:ATCWeightCategory" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ATC Weight Category” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, a specific aircraft weight grouping.</xs:documentation></xs:annotation></xs:element>
<xs:element name="commonSegmentDetails" type="type:CommonSegmentDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This class is an abstraction used to represent a Common Segment.</xs:documentation></xs:annotation></xs:element>
<xs:element name="enrouteDetails" type="type:SegmentDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a segment.</xs:documentation></xs:annotation></xs:element>
<xs:element name="intermediateFixDetails" type="type:IntermediateFixDetails" minOccurs="0" maxOccurs="4"><!-- Can it be only 4 --><xs:annotation><xs:documentation>Representsthe details of an intermediate fix in the flight planning record</xs:documentation></xs:annotation></xs:element>
A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.
<xs:element name="initialCruiseTable" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element>
“Outbound Magnetic Course” is the published outbound magnetic course from the waypoint identified in the record’s “Fix Ident” field. In addition, this field is used for Course/Heading/Radials on SID/STAR Approach Records through requirements of the Path Terminator and coding rules contained in Attachment 5 of this specification.
<xs:element name="initialDepartureMagneticCourse" type="type:Course" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Outbound Magnetic Course” is the published outbound magnetic course from the waypoint identified in the record’s “Fix Ident” field. In addition, this field is used for Course/Heading/Radials on SID/STAR Approach Records through requirements of the Path Terminator and coding rules contained in Attachment 5 of this specification.</xs:documentation></xs:annotation></xs:element>
The “Leg Type Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Path Terminator concept. It will provide the information on the path between intermediate waypoints as straight or curved and provide an indication of the change in direction of flight, expressed as left or right, at an intermediate waypoint.
<xs:element name="legTypeCode" type="type:LegTypeCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Leg Type Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Path Terminator concept. It will provide the information on the path between intermediate waypoints as straight or curved and provide an indication of the change in direction of flight, expressed as left or right, at an intermediate waypoint.</xs:documentation></xs:annotation></xs:element>
The “Number of Engines Restriction” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific number of engines.
<xs:element name="numberOfEngines" type="type:NumberofEnginesRestriction" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Number of Engines Restriction” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific number of engines.</xs:documentation></xs:annotation></xs:element>
<xs:element name="port" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “port” references the airport or heliport to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element>
<xs:element name="procedureDescription" type="type:ProcedureDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Procedure Description” field used on Flight Planning Arrival/Departure Data Records is the textual representation of the procedure name.</xs:documentation></xs:annotation></xs:element>
The “Procedure Type” field used on Flight Planning Arrival/Departure Data Record is a single character code indication the type of procedure in the record, such as Arrival, Standard Instrument Arrival Route, Approach.
Standard Terminal Arrival Route (STAR), Available in Database
enumeration
StarNotInDb
Standard Terminal Arrival Route (STAR), Not Available in Database
enumeration
SidInDb
Standard Instrument Departure (SID), Available in Database
enumeration
SidNotInDb
Standard Instrument Departure (SID), Not Available in Database
enumeration
VectorSidInDb
Vector SID, Available in Database
enumeration
VectorSidNotInDB
Vector SID, Not Available in Database
enumeration
ApproachInDb
Approach Procedure, Available in Database
enumeration
ApproachInDb
Approach Procedure, Not Available in Database
Source
<xs:element name="procedureType" type="enum:ProcedureType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Procedure Type” field used on Flight Planning Arrival/Departure Data Record is a single character code indication the type of procedure in the record, such as Arrival, Standard Instrument Arrival Route, Approach.</xs:documentation></xs:annotation></xs:element>
The “Reporting Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Waypoint Description concept. It will provide the information on intermediate waypoints as either Position Report Required (Compulsory Report) or Position Report Not Required (On-Request Report).
<xs:element name="reportingCode" type="enum:ReportingCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Reporting Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Waypoint Description concept. It will provide the information on intermediate waypoints as either Position Report Required (Compulsory Report) or Position Report Not Required (On-Request Report).</xs:documentation></xs:annotation></xs:element>
The “RNAV Flag” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, aircraft capable of flying RNAV Procedures.
The field will indicate Yes, the procedure is an RNAV procedure
enumeration
No
The field will indicate No, the procedure is NOT an RNAV procedure
Source
<xs:element name="rnavFlags" type="enum:RNAVFlag" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “RNAV Flag” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, aircraft capable of flying RNAV Procedures.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwaySegmentDetails" type="type:SegmentDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a segment.</xs:documentation></xs:annotation></xs:element>
For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence.
<xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence.</xs:documentation></xs:annotation></xs:element>
This UML Class is the base class for SIDSTARRouteIdentifier and ApproachRouteIdentifier classes. this is used in Airport SID/STAR/Approach records. The base class is used so that any of the above mentioned classes can be used in the XML file.
<xs:element name="sidSTARApproachIdentifier" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This UML Class is the base class for SIDSTARRouteIdentifier and ApproachRouteIdentifier classes. this is used in Airport SID/STAR/Approach records. The base class is used so that any of the above mentioned classes can be used in the XML file.</xs:documentation></xs:annotation></xs:element>
The “Speed Limit” field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.
<xs:element name="speedLimit" type="type:SpeedLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Speed Limit” field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.</xs:documentation></xs:annotation></xs:element>
The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed. For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit The STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit. For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit. The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit. For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.
Mandatory Speed, Cross Fix AT speed specified in Speed Limit
enumeration
Minimum
Minimum Speed, Cross Fix AT or ABOVE speed specified in Speed Limit
enumeration
Maximum
Maximum Speed, Cross Fix AT or BELOW speed specified in Speed Limit
Source
<xs:element name="speedLimitDescription" type="enum:SpeedLimitDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed. For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit The STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit. For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit. The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit. For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.</xs:documentation></xs:annotation></xs:element>
The “Turboprop/Jet Indicator” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific kind of engines.
<xs:element name="turbopropJetIndicator" type="enum:TurbopropJetIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Turboprop/Jet Indicator” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific kind of engines.</xs:documentation></xs:annotation></xs:element>
The “Category Radii” fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.
<xs:element name="categoryDistance" type="type:CategoryDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Category Radii” fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.</xs:documentation></xs:annotation></xs:element>
<xs:element minOccurs="0" name="maxHelicopterWeight" type="type:MaxHelicopterWeight"><xs:annotation><xs:documentation>This element provides the maximum weight that the helipad or FATO can support.</xs:documentation></xs:annotation></xs:element>
<xs:element name="controlledASArptIndicator" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “port” field references the airport or heliport to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element>
The “Controlled Airspace Indicator” field is used to indicate if an airport is associated with controlled airspace of a terminal type such as a Terminal Control Area (TMA or TCA) Radar Area or Class B or C Airspace within the USA.
The Airport is within or below the lateral limits of Class C Airspace.
enumeration
WithinOrBelowCta
The Airport is within or below the lateral limits of a CTA.
enumeration
WithinOrBelowTmsTca
The Airport is within or below the lateral limits of a TMA or TCA.
enumeration
WithinOrBelowRadarZone
The Airport is within or below the lateral limits Radar Zone
enumeration
WithinOrBelowClassB
The Airport is within or below the lateral limits of Class B Airspace.
Source
<xs:element name="controlledASIndicator" type="enum:ControlledASIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Indicator” field is used to indicate if an airport is associated with controlled airspace of a terminal type such as a Terminal Control Area (TMA or TCA) Radar Area or Class B or C Airspace within the USA.</xs:documentation></xs:annotation></xs:element>
<xs:element name="longestRunway" type="type:LongestRunway" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Longest Runway” field permits airport to be classified on</xs:documentation></xs:annotation></xs:element>
The “Longest Runway Surface Code” field is used to define whether or not there is a hard surface runway at the airport, the length of which is indicated in the Longest Runway field.
Undefined, surface material not provided in source
Source
<xs:element name="longestRunwaySurfaceCode" type="enum:LongestRunwaySurfaceCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Longest Runway Surface Code” field is used to define whether or not there is a hard surface runway at the airport, the length of which is indicated in the Longest Runway field.</xs:documentation></xs:annotation></xs:element>
<xs:element name="displacedThresholdDistance" type="type:DisplacedThresholdDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The distance from the extremity of a runway to a threshold not located at that extremity of that runway.</xs:documentation></xs:annotation></xs:element>
<xs:element name="landingThresholdElevation" type="type:Elevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The elevation of the landing threshold of the runway described in a runway record is defined in the “Landing Threshold Elevation” field.</xs:documentation></xs:annotation></xs:element>
<xs:element name="ltpEllipsoidHeight" type="type:EllipsoidHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Ellipsoidal Height” field is the height of a surveyed point in reference to the WGS-84 ellipsoid.</xs:documentation></xs:annotation></xs:element>
<xs:element name="primaryApproachNavaidReference" type="type:PrecisionApproachNavaidReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Element which encapsulates the ILS/MLS/GLS details for the corresponding Runway. This element contains the navaid reference and class.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwayBearing" type="type:Bearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The bearing of the runway identified in the “runway identifier” or “pad ident” field of the record is specified in the “Runway Bearing” field.</xs:documentation></xs:annotation></xs:element>
The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth andRunway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.
<xs:element name="runwayTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element>
“True Bearing” is derived from official government sources.
enumeration
Other
“True Bearing" is derived from other sources
Source
<xs:element name="runwayTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwayDescription" type="type:RunwayDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If required, additional information concerning a runway can be included in a record in the “Runway Description” field.</xs:documentation></xs:annotation></xs:element>
The Runway Gradient field indicates an overall gradient in percent, measured from the start of take-off roll end of the runway designated in the record. The gradient is expressed as a positive or negative gradient; positive being an upward and negative being a downward gradient.
<xs:element name="runwayGradient" type="type:RunwayGradient" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Runway Gradient field indicates an overall gradient in percent, measured from the start of take-off roll end of the runway designated in the record. The gradient is expressed as a positive or negative gradient; positive being an upward and negative being a downward gradient.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwayIdentifier" type="type:RunwayIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Identifier” field identifies the runways described in runway records and runways served by the ILS/MLS described in ILS/MLS records.</xs:documentation></xs:annotation></xs:element>
The “Runway Length” field defines the total length of the runway surface declared suitable and available for ground operations of aircraft for the runway identified in the records’ Runway Identifier field.
<xs:element name="runwayLength" type="type:RunwayLength" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Length” field defines the total length of the runway surface declared suitable and available for ground operations of aircraft for the runway identified in the records’ Runway Identifier field.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwayWidth" type="type:RunwayWidth" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The width of the runway identified in the “Runway Identifier” field is specified in the “Runway Width” field.</xs:documentation></xs:annotation></xs:element>
<xs:element name="secondaryApproachNavaidReference" type="type:PrecisionApproachNavaidReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Element which encapsulates the ILS/MLS/GLS details for the corresponding Runway. This element contains the navaid reference and class.</xs:documentation></xs:annotation></xs:element>
“Stopway” means the length of an area beyond the take-off runway, no less wide than the runway and centered upon the extended centerline of the runway, and designated for use in decelerating the airplane during an aborted takeoff.
<xs:element name="stopway" type="type:StopWay" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Stopway” means the length of an area beyond the take-off runway, no less wide than the runway and centered upon the extended centerline of the runway, and designated for use in decelerating the airplane during an aborted takeoff.</xs:documentation></xs:annotation></xs:element>
TCH provided in Runway Record is that of the electronic Glide Slope
enumeration
TchRnavToRunway
TCH provided in Runway Record is that of an RNAV procedure to the runway
enumeration
TchVgsi
TCH provided in the Runway Record is that of the VGSI for the runway
enumeration
TchDefaulted
TCH provided in the Runway Record is the default value of 40 or 50 feet (See Section 5.67).
Source
<xs:element name="tchValueIndicator" type="enum:TCHValueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “TCH Value Indicator” field will define which TCH value is provided in the runway record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="tdzeLocation" type="enum:TDZELocation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the “TDZE Location” field indicates whether the TDZ elevation was obtained from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element>
<xs:element name="thresholdCrossingHeight" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element>
<xs:element name="touchDownZoneElevation" type="type:TouchDownZoneElevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Touchdown Zone Elevation” is the highest elevation in the first 3,000 feet of the landing surface beginning at the threshold.</xs:documentation></xs:annotation></xs:element>
<xs:element name="starterExtension" type="type:StarterExtension" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This data element describes a starter extension of a runway</xs:documentation></xs:annotation></xs:element>
Bituminous tar or asphalt and/or oil or bitumen bound, mix-in-place surfaces (often refered to as “earth cement”)
enumeration
BrickisLaidOrMortared
enumeration
Clay
enumeration
Concrete
enumeration
ConcreteAndAsphalt
enumeration
ConcreteAndGrass
enumeration
Coral
enumeration
Dirt
enumeration
Grass
enumeration
Gravel
enumeration
Ice
enumeration
Laterite
enumeration
Macadam
enumeration
LandingMat
Usually made of aluminium
enumeration
ProtectiveLaminate
Usually made of rubber
enumeration
Metal
Steel or Aluminium
enumeration
Mix
Non bituminous mix
enumeration
Other
enumeration
Paved
generic hard surface
enumeration
PiercedSteelPlanking
enumeration
Sand
enumeration
Sealed
enumeration
Silt
enumeration
Snow
enumeration
Soil
enumeration
Stone
enumeration
Tarmac
enumeration
Treated
enumeration
Turf
enumeration
Unknown
enumeration
Unpaved
enumeration
Water
Source
<xs:element name="surfaceType" type="enum:SurfaceType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the surface type of the runway.</xs:documentation></xs:annotation></xs:element>
<xs:element name="maximumHelicopterWeight" type="type:MaxHelicopterWeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the max weight for helicopters using this runway.</xs:documentation></xs:annotation></xs:element>
<xs:element name="helicopterPerformanceReq" type="enum:HelicopterPerformanceReq" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides a performance requirement for helicopters to use this runway.</xs:documentation></xs:annotation></xs:element>
Take Off Run Available (TORA) is the declared distance value which is available for take-off ground roll. Starter extension distances are not included in the TORA distance and may be added if a starter extension is available. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.
<xs:element name="takeOffRunwayAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Take Off Run Available (TORA) is the declared distance value which is available for take-off ground roll. Starter extension distances are not included in the TORA distance and may be added if a starter extension is available. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element>
Take Off Distance Available (TODA) is the declared distance value which is available for take-off over a 50 ft obstacle. Typically, the TODA equals the TORA plus clearway. Starter extension distances are not included in the TODA. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.
<xs:element name="takeOffDistanceAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Take Off Distance Available (TODA) is the declared distance value which is available for take-off over a 50 ft obstacle. Typically, the TODA equals the TORA plus clearway. Starter extension distances are not included in the TODA. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element>
Accelerate Stop Distance Available (ASDA) is the declared distance value which is available in case of an aborted take-off. Typically, the ASDA equals the TORA plus stopway. Starter extension distances are not included in the TODA distance and may be added if a starter extension is available. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.
<xs:element name="accelerateStopDistanceAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Accelerate Stop Distance Available (ASDA) is the declared distance value which is available in case of an aborted take-off. Typically, the ASDA equals the TORA plus stopway. Starter extension distances are not included in the TODA distance and may be added if a starter extension is available. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element>
Landing Distance Available (LDA) is the declared distance value which is available for landing. Typically, the LDA equals the runway length minus the threshold displacement distance. A value of 00000 indicates that the runway is not usable for landing. A blank field means that no value is declared in source.
<xs:element name="landingDistanceAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Landing Distance Available (LDA) is the declared distance value which is available for landing. Typically, the LDA equals the runway length minus the threshold displacement distance. A value of 00000 indicates that the runway is not usable for landing. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element>
<xs:element name="runwayUsageIndicator" type="enum:RunwayUsageIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Runway Usage Indicator field specifies if a Runway is usable for take-off, landing, or both operations.</xs:documentation></xs:annotation></xs:element>
This element indicates runway data elements meet runway accuracy requirements by confirming they are consistent with a trustworthy independent data source.
<xs:element name="runwayAccuracy" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates runway data elements meet runway accuracy requirements by confirming they are consistent with a trustworthy independent data source.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="runwayAccuracyCompliance" type="enum:RunwayAccuracyCompliance" minOccurs="0" maxOccurs="1"/><xs:element name="landingThresholdElvationAccuracyCompliance" type="enum:LandingThresholdElvationAccuracyCompliance" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType></xs:element>
<xs:element name="heliportType" type="enum:HeliportType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provies information as to what type of heliport the facility is.</xs:documentation></xs:annotation></xs:element>
<xs:element name="elevation" type="type:Elevation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Facility Elevation field provides the elevation of navaids and communication transmitters.</xs:documentation></xs:annotation></xs:element>
The “Marker Code” field contains the coded ident that provides an aural and visual indication of station passage in the cockpit. The code shall be keyed so as to transmit dots or dashes, or both, in an appropriate sequence on a radio frequency of 75 MHz. The frequency of the modulating tone is 3000 Hz.
<xs:element name="markerCode" type="type:MarkerCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Marker Code” field contains the coded ident that provides an aural and visual indication of station passage in the cockpit. The code shall be keyed so as to transmit dots or dashes, or both, in an appropriate sequence on a radio frequency of 75 MHz. The frequency of the modulating tone is 3000 Hz.</xs:documentation></xs:annotation></xs:element>
<xs:element name="markerPower" type="enum:HighLow" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “High/Low” field indicates the power of the enroute marker.</xs:documentation></xs:annotation></xs:element>
<xs:element name="markerShape" type="enum:MarkerShape" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Shape” field defines the radiation pattern of an airways marker as being either “bone” or “elliptical.”</xs:documentation></xs:annotation></xs:element>
<xs:element name="minorAxis" type="type:MinorAxisBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Minor Axis Bearing” field indicates the true bearing of the minor axis of marker beacons.</xs:documentation></xs:annotation></xs:element>
Altitude Exclusion. The record contains altitudes, normally available, that are excluded from use for the Enroute Airway Segment. May be further restricted by Time of Operation information.
enumeration
TC
Cruising Table Replacement. The record contains only a reference to a Cruising Table Identifier. That Cruise Table will be in force, replacing the Cruise Table Identifier in the Enroute Airway segment records defined in the Start Fix/End Fix fields.
enumeration
SC
Seasonal Restriction. Record is used to close an Airway or portion of an Airway on a seasonal basis.
enumeration
NR
Note Restrictions. The record contains restrictions that do not fit the pattern of formatted information allowed by other Restriction Record Types.
<xs:element name="timesOfOperation" type="type:TimesOfOperation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Time of Operation field is used to indicate the times of operation of an airway restriction.</xs:documentation></xs:annotation></xs:element>
The “Exclusion Indicator” field is an indication of how the altitudes contained in the Cruising Table record referenced by the Airway segment(s) are restricted. This is an “all altitude” restriction, further defined by direction of flight. These codes will not be used when certain altitudes remain available in a direction of flight.
All altitudes in both directions of flight are restricted. This effectively closes the airway in both direction of flight.
enumeration
AllOpposite
All altitudes in the opposite direction in which the Enroute Airway is coded are restricted. This effectively closes the airway in one direction of flight i.e., the opposite direction from that in which the airway is coded.
enumeration
AllPerAirway
All altitudes in the direction in which the Enroute Airway is coded are restricted. This effectively closes the airway in one direction of flight i.e., the direction in which the airway is coded.
enumeration
NotAll
The restriction is not an all altitude restriction.
Source
<xs:element name="exclusionIndicator" type="enum:ExclusionIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Exclusion Indicator” field is an indication of how the altitudes contained in the Cruising Table record referenced by the Airway segment(s) are restricted. This is an “all altitude” restriction, further defined by direction of flight. These codes will not be used when certain altitudes remain available in a direction of flight.</xs:documentation></xs:annotation></xs:element>
<xs:element name="restrictionAltitudeBlockIndicator" type="type:RestrictionAltitudeBlockIndicator" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction for Restriction Altitude and Block Indicator elements as they occur together in airways restriction records.</xs:documentation></xs:annotation></xs:element>
Restriction Altitudes are expressed in hundreds of feet
enumeration
MetricFlightLevel
Restriction Altitudes are expressed in metric Flight Levels
enumeration
FeetFlightLevel
Restriction Altitudes are expressed in feet Flight Levels
enumeration
TensOfMeters
Restriction Altitudes are expressed in tens of meters
Source
<xs:element name="unitsofAltitude" type="enum:UnitsofAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Units of Altitude” field is used to indicate the units of measurement for the values in the “Restriction Altitude” fields.</xs:documentation></xs:annotation></xs:element>
A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.
<xs:element name="cruiseTableIdentifier" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element>
A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.
<xs:element name="cruiseTableIdentifier" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element>
Routes of flight frequently cross geographical boundaries. The “Boundary Code” field identifies the area into, or from which a continuous route passes when such a crossing occurs.
<xs:element name="boundaryCode" type="enum:BoundaryCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Routes of flight frequently cross geographical boundaries. The “Boundary Code” field identifies the area into, or from which a continuous route passes when such a crossing occurs.</xs:documentation></xs:annotation></xs:element>
A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.
<xs:element name="cruiseTableIndicator" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element>
One way in opposite direction route is coded (backward).
enumeration
NoRestrictions
No restrictions on direction.
Source
<xs:element name="directionRestriction" type="enum:EnrouteAirwayDirectionalRestriction" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Direction Restriction” field will indicate the direction an Enroute Airway is to be flown</xs:documentation></xs:annotation></xs:element>
In Enroute Airways, Route Distance From is the distance in nautical miles from the waypoint identified in the records Fix Ident field to the next waypoint of the route.
<xs:element name="routeDistanceFrom" type="type:LegDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>In Enroute Airways, Route Distance From is the distance in nautical miles from the waypoint identified in the records Fix Ident field to the next waypoint of the route.</xs:documentation></xs:annotation></xs:element>
restriction for the segment is contained in the restriction file
Source
<xs:element name="euIndicator" type="enum:EUIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “EU Indicator” field is used to identify those Enroute Airway records that have an Airway Restriction record without identifying the restriction.</xs:documentation></xs:annotation></xs:element>
<xs:element name="fixRadiusTransitionIndicator" type="type:FixedRadiusTransitionIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Indicates that a specific turn radius from the inbound course to the outbound course is required by the airspace controlling agency.</xs:documentation></xs:annotation></xs:element>
“Inbound Magnetic Course” is the published inbound magnetic course to the waypoint in the “Fix Ident” field of the records in which it is employed. The “HX” group of Path Terminator codes is used to provide racetrack type course reversal flight paths. Government publications for these course reversal include an “inbound magnetic bearing.” The SID/STAR/Approach Procedures records do not include a dedicated field for this inbound course. Instead, the information is included in the “Outbound Magnetic Course” field of such records.
<xs:element name="inboundCourse" type="type:Course" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Inbound Magnetic Course” is the published inbound magnetic course to the waypoint in the “Fix Ident” field of the records in which it is employed. The “HX” group of Path Terminator codes is used to provide racetrack type course reversal flight paths. Government publications for these course reversal include an “inbound magnetic bearing.” The SID/STAR/Approach Procedures records do not include a dedicated field for this inbound course. Instead, the information is included in the “Outbound Magnetic Course” field of such records.</xs:documentation></xs:annotation></xs:element>
A waypoint which normally would be classified as non-essential may be required to transition from the enroute structure to the terminal structure. Waypoints falling into this category are classified as Transition Essential Waypoints
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isTransitionEssential" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A waypoint which normally would be classified as non-essential may be required to transition from the enroute structure to the terminal structure. Waypoints falling into this category are classified as Transition Essential Waypoints</xs:documentation></xs:annotation></xs:element>
Compulsory Reporting Point: Essential or nonessential waypoints may be classified as ATC compulsory points. ATC requires the pilot to make a communications report at these waypoints. All other waypoints may be classified as non compulsory reporting points and are reported only when specifically requested by ATC
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isAtcCompulsoryReportingPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Compulsory Reporting Point: Essential or nonessential waypoints may be classified as ATC compulsory points. ATC requires the pilot to make a communications report at these waypoints. All other waypoints may be classified as non compulsory reporting points and are reported only when specifically requested by ATC</xs:documentation></xs:annotation></xs:element>
<xs:element name="level" type="enum:Level" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Level field defines the airway structure of which the record is an element.</xs:documentation></xs:annotation></xs:element>
<xs:element name="rvsmMinimumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Minimum Level is the lowest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element>
<xs:element name="vsfRVSMMaximumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Maximum Level is the highest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element>
<xs:element name="maximumAltitude" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Maximum Altitude” field is used to indicate the maximum altitude allowed.</xs:documentation></xs:annotation></xs:element>
<xs:element name="rnavPbnNavSpec" type="enum:AirwayRnavPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNAV PBN navigation specification applies to this airway segment</xs:documentation></xs:annotation></xs:element>
<xs:element name="rnpPbnNavSpec" type="enum:AirwayRnpPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNP PBN navigation specification applies to this airway segment</xs:documentation></xs:annotation></xs:element>
<xs:element name="alternateDistanace" type="type:AlternateDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is used to supply the distance in nautical miles from the “To Airport/Heliport/Fix” to the Alternate Airport/Heliport.</xs:documentation></xs:annotation></xs:element>
<xs:element name="costIndex" type="type:CostIndex" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Cost Index field is used to define the relative value of fuel-related costs and time-related costs for a particular route.</xs:documentation></xs:annotation></xs:element>
When used on Company Routes and Helicopter Operations Company Routes, the “From Airport/Heliport/Fix” is the fix from which the company route originates. The “To Airport/Heliport/Fix” is the fix at which the company route terminates. When used on Alternate Records, it is the Departure, Destination or Enroute Airport/Fix for which the alternate information is being provided.
<xs:element name="fromPortFix" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When used on Company Routes and Helicopter Operations Company Routes, the “From Airport/Heliport/Fix” is the fix from which the company route originates. The “To Airport/Heliport/Fix” is the fix at which the company route terminates. When used on Alternate Records, it is the Departure, Destination or Enroute Airport/Fix for which the alternate information is being provided.</xs:documentation></xs:annotation></xs:element>
This field has two uses depending on the “VIA” field and File Code for “To Fix.” For “VIA” field content of “ALT” this field will contain the Alternate Airport Ident or Heliport Ident for this Company Route. If the file code for “To Fix” contains “P,” this field will contain the Airport Ident for REGN CODE (Section 5.41) of Terminal Waypoints (PC records) and Runway (PG records). If the file code for “To Fix” contains “H”, this field will contain the Heliport Ident for REGN CODE (Section 5.41) of Helicopter Terminal Waypoints (HC records).
<xs:element name="terminalAlternateAirport" type="type:TerminalAlternateAirport" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field has two uses depending on the “VIA” field and File Code for “To Fix.” For “VIA” field content of “ALT” this field will contain the Alternate Airport Ident or Heliport Ident for this Company Route. If the file code for “To Fix” contains “P,” this field will contain the Airport Ident for REGN CODE (Section 5.41) of Terminal Waypoints (PC records) and Runway (PG records). If the file code for “To Fix” contains “H”, this field will contain the Heliport Ident for REGN CODE (Section 5.41) of Helicopter Terminal Waypoints (HC records).</xs:documentation></xs:annotation></xs:element>
When used on Company Routes and Helicopter Operations Company Routes, the “From Airport/Heliport/Fix” is the fix from which the company route originates. The “To Airport/Heliport/Fix” is the fix at which the company route terminates. When used on Alternate Records, it is the Departure, Destination or Enroute Airport/Fix for which the alternate information is being provided.
<xs:element name="toPortFix" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When used on Company Routes and Helicopter Operations Company Routes, the “From Airport/Heliport/Fix” is the fix from which the company route originates. The “To Airport/Heliport/Fix” is the fix at which the company route terminates. When used on Alternate Records, it is the Departure, Destination or Enroute Airport/Fix for which the alternate information is being provided.</xs:documentation></xs:annotation></xs:element>
<xs:element name="airspaceName" type="type:Name" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Airspace Name” field will contain the name of the airspace when assigned.</xs:documentation></xs:annotation></xs:element>
<xs:element name="arcBearing" type="type:ArcBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Arc Bearing field contains the true bearing from the Arc Origin position to the beginning of the arc</xs:documentation></xs:annotation></xs:element>
The “Arc Distance” field is used to define the distance in nautical miles from the “ArcOrigin” position to the arc defining the lateral boundary of a FIR/UIR or Restrictive Airspace.
<xs:element name="arcDistance" type="type:ArcDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Arc Distance” field is used to define the distance in nautical miles from the “ArcOrigin” position to the arc defining the lateral boundary of a FIR/UIR or Restrictive Airspace.</xs:documentation></xs:annotation></xs:element>
<xs:element name="arcOriginLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
<xs:element name="boundaryVIA" type="enum:BoundaryVia" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Boundary VIA” defines the path of the boundary from the position identified in the record to the next defined position.</xs:documentation></xs:annotation></xs:element>
<xs:element name="level" type="enum:Level" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Level field defines the airway structure of which the record is an element.</xs:documentation></xs:annotation></xs:element>
<xs:element name="location" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
For Boundary Type Records - A boundary is defined by a series of records taken in order. The “Sequence Number” field defines the location of the record in the sequence defining a boundary.
<xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Boundary Type Records - A boundary is defined by a series of records taken in order. The “Sequence Number” field defines the location of the record in the sequence defining a boundary.</xs:documentation></xs:annotation></xs:element>
Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.
<xs:element name="controllingAgency" type="type:ControllingAgency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.</xs:documentation></xs:annotation></xs:element>
The “Controlled Airspace Classification” field will contain an alpha character indicating the published classification of the controlled airspace, when assigned.
<xs:element name="airspaceClassification" type="type:AirspaceClassification" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Classification” field will contain an alpha character indicating the published classification of the controlled airspace, when assigned.</xs:documentation></xs:annotation></xs:element>
The “Controlled Airspace Center” field is used to define the navigation element upon which the controlled airspace being defined is predicated, but not necessarily centered. Where the Airspace is not defined then the “Region Identifier” should be used. In this case, the Controlled Airspace Center will contain the ICAO Identification code for the Controlled Airspace to which the data contained in the record relates.
<xs:element name="controlledAirspaceCenter" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Center” field is used to define the navigation element upon which the controlled airspace being defined is predicated, but not necessarily centered. Where the Airspace is not defined then the “Region Identifier” should be used. In this case, the Controlled Airspace Center will contain the ICAO Identification code for the Controlled Airspace to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element>
Terminal Control Area, ICAO Designation (TMA or TCA).
enumeration
Radar
Radar Zone or Radar Area (Was TRSA within the USA).
enumeration
ClassB
Class B Airspace (Was TCA with the USA).
enumeration
ClassD
Class D Airspace within the USA, Control Zone, ICAO Designation (CTR).
Source
<xs:element name="controlledAirspaceType" type="enum:ControlledAirspaceType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Type” field is used to indicate the type of controlled airspace, using codes from the table below.</xs:documentation></xs:annotation></xs:element>
<xs:element name="airspaceSpeedRestriction" type="type:AirspaceSpeedRestriction" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>When government source provides a speed restriction then this element will be provided.</xs:documentation></xs:annotation></xs:element>
<xs:element name="speedRestriction" type="type:SpeedLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>When used on a Controlled Airspace record, the field is used to describe a speed restriction within the Airspace</xs:documentation></xs:annotation></xs:element>
<xs:element name="speedAltitude" type="type:Altitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Speed Limit Altitude is the altitude below which speed limits may be imposed</xs:documentation></xs:annotation></xs:element>
<xs:element name="restrictiveAirspaceDesignation" type="type:RestrictiveAirspaceDesignation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Designation” field contains the number or name that uniquely identifies the restrictive airspace.</xs:documentation></xs:annotation></xs:element>
<xs:element name="restrictiveAirspaceName" type="type:Name" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Name” field will contain the name of the restrictive airspace when assigned.</xs:documentation></xs:annotation></xs:element>
The “Restrictive Airspace Type” field is used to indicate the type of Airspace in which the flight of aircraft is prohibited or restricted. The restriction may be continuous or specified for certain times.
<xs:element name="restrictiveAirspaceType" type="enum:RestrictiveAirspaceType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Type” field is used to indicate the type of Airspace in which the flight of aircraft is prohibited or restricted. The restriction may be continuous or specified for certain times.</xs:documentation></xs:annotation></xs:element>
<xs:element name="activityType" type="enum:ActivityType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Activity Type is used to define the type of Special Activity that is occurring.</xs:documentation></xs:annotation></xs:element>
The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.
<xs:element name="communicationType" type="enum:CommunicationType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.</xs:documentation></xs:annotation></xs:element>
The “Communication Frequency” field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.
Diagram
Type
xs:string
Properties
content
simple
minOccurs
1
maxOccurs
1
Source
<xs:element name="communicationFrequency" type="xs:string" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Frequency” field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.</xs:documentation></xs:annotation></xs:element>
Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.
<xs:element name="controllingAgency" type="type:ControllingAgency" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.</xs:documentation></xs:annotation></xs:element>
<xs:element name="icaoCode" type="type:IcaoCode" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “ICAO Code” field permits records to be categorized geographically within the limits of the categorization performed by the “Area Code” field.</xs:documentation></xs:annotation></xs:element>
<xs:element name="location" type="type:Location" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element>
Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.
Airport/Heliport is not open to the public (private)
enumeration
Civil
Airport/Heliport is open to the public (civil)
enumeration
Military
Airport/Heliport is military airport
enumeration
Joint
Airport is joint Civil and Military
Source
<xs:element name="publicMilitaryIndicator" type="enum:PublicMilitaryIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.</xs:documentation></xs:annotation></xs:element>
<xs:element name="saaIdentifier" type="type:SAAIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Activity Identifier” field contains the number or name that uniquely identifies the Special Activity Area.</xs:documentation></xs:annotation></xs:element>
<xs:element name="saaOperatingTimes" type="type:SpecialActivityAreaOperatingTimes" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Special Activity Area Operating Times field contains the annual expected operation schedule of the Special Activity.</xs:documentation></xs:annotation></xs:element>
<xs:element name="saaSize" type="type:SpecialActivityAreaSize" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Special Activity Area Size field contains the radius around the center point where the Special Activity is expected to occur.</xs:documentation></xs:annotation></xs:element>
<xs:element name="saaVolume" type="type:SpecialActivityAreaVolume" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Special Activity Area Volume” field contains the expected annual level of intensity of the Special Activity.</xs:documentation></xs:annotation></xs:element>
<xs:element name="specialActivityAreaName" type="type:Name" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Name” field will contain the name of the restrictive airspace when assigned.</xs:documentation></xs:annotation></xs:element>
Restrictive Airspace lower and upper limits are specified as above mean sea level (MSL) or above ground level (AGL). This field permits the unit of measurement to be indicated.
<xs:element name="unitIndicator" type="enum:UnitIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Restrictive Airspace lower and upper limits are specified as above mean sea level (MSL) or above ground level (AGL). This field permits the unit of measurement to be indicated.</xs:documentation></xs:annotation></xs:element>
Special Use Airspace is described by both lateral and vertical boundaries. The “Lower/Upper Limit” fields contain the lower and upper limits of the FIR/UIR or Restrictive Airspace being described.
<xs:element name="upperLimit" type="type:AltitudeLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Special Use Airspace is described by both lateral and vertical boundaries. The “Lower/Upper Limit” fields contain the lower and upper limits of the FIR/UIR or Restrictive Airspace being described.</xs:documentation></xs:annotation></xs:element>
The FIR/UIR Entry Report field is used to indicate whether an entry report on ICAO flight plan is required for that specific FIR/UIR.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="entryReport" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The FIR/UIR Entry Report field is used to indicate whether an entry report on ICAO flight plan is required for that specific FIR/UIR.</xs:documentation></xs:annotation></xs:element>
The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.
<xs:element name="adjacentFIRIdentifier" type="type:FIRUIRIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element>
The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.
<xs:element name="adjacentUIRIdentifier" type="type:FIRUIRIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element>
<xs:element name="alternateDetails" type="type:AlternateDetails" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details of an Alternate.</xs:documentation></xs:annotation></xs:element>
<xs:element name="alternateIdentifier" type="type:PointReference" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This element points to the airport or heliport element.</xs:documentation></xs:annotation></xs:element>
The “Distance To Alternate” field defines either the direct (geodesic) distance from the Destination Airport or Fix to the Alternate Airport or the along track distance of an alternate Company Routein nautical miles.
<xs:element name="distanceToAlternate" type="type:DistanceIntegerNM" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance To Alternate” field defines either the direct (geodesic) distance from the Destination Airport or Fix to the Alternate Airport or the along track distance of an alternate Company Routein nautical miles.</xs:documentation></xs:annotation></xs:element>
<xs:element name="cruiseDetails" type="type:CruiseDetails" minOccurs="0" maxOccurs="4"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details of Cruise Level.</xs:documentation></xs:annotation></xs:element>
A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.
<xs:element name="cruiseTableIdentifier" type="type:CruiseTableIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element>
The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.
The field will be blank if details and procedures are provided in both magnetic and true for the airport. In such cases the individual detail or procedure records will contain the magnetic or true information
enumeration
True
if all detail and procedure for the airport are reported in true bearing
enumeration
Magnetic
if all detail and procedure for the airport are reported in magnetic bearing,
Source
<xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element>
For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence.
<xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence.</xs:documentation></xs:annotation></xs:element>
<xs:element name="aircraftUsageGroup" type="type:AircraftUsageGroup" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Aircraft Use Group” field provides information on what aircraft or groups of aircraft are permitted to use a certain route.</xs:documentation></xs:annotation></xs:element>
The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.
At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
AtOrBelow
At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
At
At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.
enumeration
B
At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope
enumeration
C
"At or above" altitude specified in second "Altitude" field.
enumeration
G
Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.
enumeration
I
Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope
Source
<xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element>
The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.
<xs:element name="areaCode" type="enum:AreaCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.</xs:documentation></xs:annotation></xs:element>
The “Direction Restriction” field will indicate whether the routing is available only in the direction of “from initial fix to terminus fix” or in both directions.
Uni-directional Preferred Route, usable only from Initial Fix to Terminus Fix.
enumeration
BiDirectional
Bi-directional Preferred Route, usable from Initial Fix to Terminus Fix or from Terminus Fix to Initial Fix.
Source
<xs:element name="directionRestriction" type="enum:PrefferedRouteDirectionalRestriction" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Direction Restriction” field will indicate whether the routing is available only in the direction of “from initial fix to terminus fix” or in both directions.</xs:documentation></xs:annotation></xs:element>
The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.
<xs:element name="intialAirportFix" type="type:InitialTerminusAirportFix" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.</xs:documentation></xs:annotation></xs:element>
<xs:element name="level" type="enum:Level" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Level field defines the airway structure of which the record is an element.</xs:documentation></xs:annotation></xs:element>
<xs:element name="maximumAltitude" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Maximum Altitude” field is used to indicate the maximum altitude allowed.</xs:documentation></xs:annotation></xs:element>
The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Record and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.
<xs:element name="minimumAltitude" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Record and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.</xs:documentation></xs:annotation></xs:element>
The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.
<xs:element name="preferedRouteUseIndicator" type="type:PreferedRouteUseIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.</xs:documentation></xs:annotation></xs:element>
The “Route Type” field defines the type of Enroute Airway, Preferred Route, Airport and Heliport SID/STAR/Approach Routes of which the record is an element. For Airport and Heliport SID/STAR/Approach Routes, “Route Type” includes a “primary route type,” and up to two “route type qualifiers.”
Diagram
Type
xs:string
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="routeType" type="xs:string" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Route Type” field defines the type of Enroute Airway, Preferred Route, Airport and Heliport SID/STAR/Approach Routes of which the record is an element. For Airport and Heliport SID/STAR/Approach Routes, “Route Type” includes a “primary route type,” and up to two “route type qualifiers.”</xs:documentation></xs:annotation></xs:element>
The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.
<xs:element name="terminusAirportFix" type="type:InitialTerminusAirportFix" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.</xs:documentation></xs:annotation></xs:element>
The "VIA Code" field is used to define the type of route used in the SID/STAR/Approach/Airways field (Section 5.78) on Company Route records and defines the type of route used in the AWY Identifier on Preferred Route records. On the Preferred Route records, some codes define the use, or restriction to use, of a fix or routing.
<xs:element name="viaCode" type="enum:PreferredRouteVIACodes" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "VIA Code" field is used to define the type of route used in the SID/STAR/Approach/Airways field (Section 5.78) on Company Route records and defines the type of route used in the AWY Identifier on Preferred Route records. On the Preferred Route records, some codes define the use, or restriction to use, of a fix or routing.</xs:documentation></xs:annotation></xs:element>
The “FIR/RDO Identifier” field used on Enroute Communication records is the source provided identifier for a communication service as used in message addressing. For Information Regions (FIR/UIR) it is the four-character identifier assigned to the Information Region as published in ICAO Document 7910, Location Indicators. For Flight Service Stations, it is the three or four character identifier assigned to the station by the relevant authority. For other communication services established for enroute use and not addressable under the Information Region, Flight Service Station concept, it is the identifier assigned by the relevant authority to that station for the purpose of addressing message traffic.
<xs:element name="firRDOIdent" type="type:FIRRDOIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “FIR/RDO Identifier” field used on Enroute Communication records is the source provided identifier for a communication service as used in message addressing. For Information Regions (FIR/UIR) it is the four-character identifier assigned to the Information Region as published in ICAO Document 7910, Location Indicators. For Flight Service Stations, it is the three or four character identifier assigned to the station by the relevant authority. For other communication services established for enroute use and not addressable under the Information Region, Flight Service Station concept, it is the identifier assigned by the relevant authority to that station for the purpose of addressing message traffic.</xs:documentation></xs:annotation></xs:element>
This element provides an IDREF to identify the FIRUIR element for the parent enrouteCommunication element.
Diagram
Type
xs:IDREF
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="firUirRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides an IDREF to identify the FIRUIR element for the parent enrouteCommunication element.</xs:documentation></xs:annotation></xs:element>
The “Position Narrative” field is a textual description of the location of a communication transmitter. This may be the name of a Remote Communication Outlet, a Remote Communication Air/Ground Station or the place name of the geographical location of the transmitter site.
<xs:element name="positionNarrative" type="type:PositionNarrative" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Position Narrative” field is a textual description of the location of a communication transmitter. This may be the name of a Remote Communication Outlet, a Remote Communication Air/Ground Station or the place name of the geographical location of the transmitter site.</xs:documentation></xs:annotation></xs:element>
<xs:element name="serviceIndicator" type="type:EnrouteCommunicationServiceIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Service Indicator” field is used to further define the use of the frequency for the specified Communication Type (5.101).</xs:documentation></xs:annotation></xs:element>
<xs:element name="assignedSectorName" type="type:AssignedSectorName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Associated Sector Name” field is used to indicate the published name of an Enroute Communication Sector.</xs:documentation></xs:annotation></xs:element>
The Geographical Reference Table will be used to identify “Geographical Entities” not definable by other established encoding systems. For established systems refer to Section 7 of this document.
<xs:element name="geographicalEntity" type="type:GeographicalEntity" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Geographical Reference Table will be used to identify “Geographical Entities” not definable by other established encoding systems. For established systems refer to Section 7 of this document.</xs:documentation></xs:annotation></xs:element>
The “Geographical Reference Table Identifier” will be used to provide a unique identification for each Geographical Entity. As the “Geographical Entity” field is a large field with no established content, this two character code will act as a pseudo key for the record.
<xs:element name="GeographicalRefTableID" type="type:GeographicalReferenceTableIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Geographical Reference Table Identifier” will be used to provide a unique identification for each Geographical Entity. As the “Geographical Entity” field is a large field with no established content, this two character code will act as a pseudo key for the record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="preferredRouteDetails" type="type:PreferredRouteDetails" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details Preferred Route Identifier and Preferred Route Use Indicator.</xs:documentation></xs:annotation></xs:element>
<xs:element name="startingPosition" type="type:Location" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of the lower left corner of the block of MORAs.</xs:documentation></xs:annotation></xs:element>
Grid Minimum Off-route Altitude (MORA) provides terrain and obstruction clearance within a one degree of latitude by one degree of longitude block. The first MORA in the list is for the block whose lower left corner is given by the startingPosition field. Each successive block is one degree of longitude east of the prior block. Within a single record, each MORA has the same latitude.
<xs:element name="mora" type="type:GridMORA" minOccurs="30" maxOccurs="30"><xs:annotation><xs:documentation>Grid Minimum Off-route Altitude (MORA) provides terrain and obstruction clearance within a one degree of latitude by one degree of longitude block. The first MORA in the list is for the block whose lower left corner is given by the startingPosition field. Each successive block is one degree of longitude east of the prior block. Within a single record, each MORA has the same latitude.</xs:documentation></xs:annotation></xs:element>
ANY element from namespace(s) 'http://www.mitre.org/ARINC/extensions, http://www.navtech.aero/ARINC/extensions,
http://www.garmin.com/ARINC/extensions, http://www.agustawestland-ans.com/ARINC/extensions,
http://www.NGA.mil'
The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.
<xs:element name="arcRadius" type="type:ARCRadius" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.</xs:documentation></xs:annotation></xs:element>
The “Duplicate Identifier” field is used to further define holding patterns when official government source has designated more than one Holding Pattern on a Navaid or Waypoint.
<xs:element name="duplicateIndicator" type="type:DuplicateIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Duplicate Identifier” field is used to further define holding patterns when official government source has designated more than one Holding Pattern on a Navaid or Waypoint.</xs:documentation></xs:annotation></xs:element>
<xs:element name="holdingPatternName" type="type:Name" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Name” field defines the name commonly applied to the navigation entity defined in the record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="holdingSpeed" type="type:HoldingSpeed" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Holding Speed” will be the maximum speed in a holding pattern.</xs:documentation></xs:annotation></xs:element>
The Leg Time field specifies the length of the inbound leg or outbound of a holding pattern in units of time. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the timing between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the timing from a point abeam the holding fix to the beginning of the inbound turn.
Diagram
Type
xs:duration
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="holdingTime" type="xs:duration" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Leg Time field specifies the length of the inbound leg or outbound of a holding pattern in units of time. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the timing between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the timing from a point abeam the holding fix to the beginning of the inbound turn.</xs:documentation></xs:annotation></xs:element>
The Leg Length field specifies the distance of either the inbound leg or the outbound leg of the holding pattern. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the distance between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the distance from a point abeam the holding fix to the beginning of the inbound turn.
<xs:element name="holdingDistance" type="type:HoldingLegLength" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Leg Length field specifies the distance of either the inbound leg or the outbound leg of the holding pattern. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the distance between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the distance from a point abeam the holding fix to the beginning of the inbound turn.</xs:documentation></xs:annotation></xs:element>
<xs:element name="inboundHoldingCourse" type="type:Course" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Inbound Holding Course field defines the inbound course to the holding waypoint.</xs:documentation></xs:annotation></xs:element>
<xs:element name="maximumAltitude" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Maximum Altitude” field is used to indicate the maximum altitude allowed.</xs:documentation></xs:annotation></xs:element>
The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Record and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.
<xs:element name="minimumAltitude" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Record and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.</xs:documentation></xs:annotation></xs:element>
Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.
<xs:element name="RNP" type="type:RequiredNavigationPerformance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.</xs:documentation></xs:annotation></xs:element>
<xs:element name="rvsmMaximumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Maximum Level is the highest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element>
<xs:element name="rvsmMinimumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Minimum Level is the lowest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element>
<xs:element name="turnDirection" type="enum:Turn" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Turn” field specifies the direction in which holding pattern turns are to be made.</xs:documentation></xs:annotation></xs:element>
<xs:element name="verticalScaleFactor" type="type:VerticalScaleFactor" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Vertical Scale Factor (VSF) is used to set the vertical deviation scale.</xs:documentation></xs:annotation></xs:element>
The “Fix Identifier” field contains the five-character-name-code, or other series of characters, with which the fix is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, Airport Identifiers, and Runway Identifiers
<xs:element name="fixIdentifier" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Fix Identifier” field contains the five-character-name-code, or other series of characters, with which the fix is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, Airport Identifiers, and Runway Identifiers</xs:documentation></xs:annotation></xs:element>
Step-down fix on the final approach coding indicating a segment course change that is greater than or equal to one degree different than the next leg. All RF non-procedure fixes on the final approach coding meet this requirement. This code will take precedence over a step-down fix code at the same fix.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isFixTurningFinalApproach" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Step-down fix on the final approach coding indicating a segment course change that is greater than or equal to one degree different than the next leg. All RF non-procedure fixes on the final approach coding meet this requirement. This code will take precedence over a step-down fix code at the same fix.</xs:documentation></xs:annotation></xs:element>
An Initial Approach Fix is that fix designated by the government source documentations as the fix at which the Initial Approach segment begins. An Approach Procedure may have no IAF or multiple IAFs waypoints.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isInitialApproachFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>An Initial Approach Fix is that fix designated by the government source documentations as the fix at which the Initial Approach segment begins. An Approach Procedure may have no IAF or multiple IAFs waypoints.</xs:documentation></xs:annotation></xs:element>
An Intermediate Fix is a fix designated by government source documentation as the fix at which the Intermediate Approach Segment of the approach begins
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isIntermediateApproachFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>An Intermediate Fix is a fix designated by government source documentation as the fix at which the Intermediate Approach Segment of the approach begins</xs:documentation></xs:annotation></xs:element>
Coverage, the limitations are expressed as maximum reception reliability
enumeration
Fluctuations
Fluctuations, radial(s) are affected by course fluctuations.
enumeration
Roughness
Roughness, signal roughness experienced in the sector(s) defined.
enumeration
Unreliable
Unreliable in the sector(s), at the altitude(s), at the distance(s) defined.
enumeration
Restricted
Restricted in the sector(s), at the altitude(s), at the distance(s) defined
enumeration
Unusable
Unusable in the sector(s), at the altitude(s), at the distance(s) defined.
enumeration
OutOfTollerance
Out of Tolerance in the sector(s), at the altitude(s), at the distance(s) defined.
Source
<xs:element name="navaidLimitationCode" type="enum:NavaidLimitationCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Limitation Codes” field is used to define the type of limitation to be expected with a VHF Navaid.</xs:documentation></xs:annotation></xs:element>
The VHF Navaid File contains navaids that have one or two components - azimuth and/or distance. Published limitations may apply to one or both of the components. The “Component Affected Indicator” defines which component(s) are affected by the limitation.
TACAN or VORTAC, TACAN azimuth component only affected.
enumeration
VorDmeOrVortacAzimuthAndDistance
VORDME or VORTAC, both azimuth and distance component affected.
enumeration
VordmeOrDmeDistance
VORDME or DME, distance component only affected.
enumeration
VortacOrTacanAzimth
VORTAC or TACAN, TACAN azimuth and distance component affected.
enumeration
TacanVortacDistance
TACAN or VORTAC, distance component affected.
enumeration
VorOrVordmeOrVorAzimuth
VOR, VORDME or VORDME, VOR azimuth component affected
enumeration
VorOrVordmeOrTacanOrVortacanAzimuth
VOR, VORDME or TACAN, VOR and TACAN azimuth and distance component affected.
Source
<xs:element name="componentAffectedIndicator" type="enum:ComponentAffectedIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The VHF Navaid File contains navaids that have one or two components - azimuth and/or distance. Published limitations may apply to one or both of the components. The “Component Affected Indicator” defines which component(s) are affected by the limitation.</xs:documentation></xs:annotation></xs:element>
<xs:element name="sectorDetails" type="type:SectorDetails" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a Sector.</xs:documentation></xs:annotation></xs:element>
At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
AtOrBelow
At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
At
At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.
enumeration
B
At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope
enumeration
C
"At or above" altitude specified in second "Altitude" field.
enumeration
G
Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.
enumeration
I
Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope
<xs:element name="distanceLimitationBegin" type="type:DistanceIntegerNM" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance Limitation” fields are used to define the distance range from the navaid at which the limitation applies.</xs:documentation></xs:annotation></xs:element>
<xs:element name="distanceLimitationEnd" type="type:DistanceIntegerNM" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance Limitation” fields are used to define the distance range from the navaid at which the limitation applies.</xs:documentation></xs:annotation></xs:element>
The “Sequence End Indicator” field is used to define the end of a set of sequences defining a given limitation to a given VHF Navaid Component or Component pair.
<xs:element name="sequenceEndIndicator" type="type:SequenceEndIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Sequence End Indicator” field is used to define the end of a set of sequences defining a given limitation to a given VHF Navaid Component or Component pair.</xs:documentation></xs:annotation></xs:element>
The “Decision Height” fields are used to specify a specific height in the precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established
<xs:element name="decisionHeight" type="type:DecisionHeight" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Decision Height” fields are used to specify a specific height in the precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established</xs:documentation></xs:annotation></xs:element>
The Minimum Descent Height fields specify the lowest height, expressed in feet, to which descent is authorized on final approach or during circle-toland maneuvering in execution of a standard instrument approach procedure where no electric glide slope is provided.
<xs:element name="minimumDescentHeight" type="type:MinimumDescentHeight" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Minimum Descent Height fields specify the lowest height, expressed in feet, to which descent is authorized on final approach or during circle-toland maneuvering in execution of a standard instrument approach procedure where no electric glide slope is provided.</xs:documentation></xs:annotation></xs:element>
The Category Radii fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.
<xs:element name="radii" type="type:CategoryDistance" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Category Radii fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.</xs:documentation></xs:annotation></xs:element>
Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.
<xs:element name="rnp" type="type:RequiredNavigationPerformance" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.</xs:documentation></xs:annotation></xs:element>
Automatic Transcribed Weather.The frequency of this Navaid is used for the continuous broadcast of some sort of automated weather system such as AWOS, ASOS, TWEB, AWIB, AWIS.
enumeration
SCHEDULED
Broadcast Scheduled Weather.The frequency of this Navaid is used for the scheduled, noncontinuous broadcast of some sort of automated weather system such as VOLMET.
The Initial Departure Fix indication, P in column 43, is coded for the first published fix/waypoint of an RNAV departure.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isInitialDepartureFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Initial Departure Fix indication, P in column 43, is coded for the first published fix/waypoint of an RNAV departure.</xs:documentation></xs:annotation></xs:element>
The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.
<xs:element name="communicationType" type="enum:CommunicationType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.</xs:documentation></xs:annotation></xs:element>
The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing control services to aircraft.
enumeration
LIRI
The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing information services to aircraft.
enumeration
USVC
The Communication Type is that of one used within an Information Region (FIR/UIR) for purposes other than control or information services and is not linked to that Region
enumeration
ASVC
The Communication Type is that of one providing automated or broadcast services within an Information Region (FIR/UIR).
enumeration
ATCF
The Communication Type is that of one providing ATC services to aircraft within the terminal area of an airport.
enumeration
GNDF
The Communication Type is that of one providing ATC services to aircraft on the ground at an airport.
enumeration
AOTF
The Communication Type is that of one providing services other than ATC functions on the ground or within the terminal area of an airport.
enumeration
AFAC
The Communication Type is that of one provided automated or broadcast services to aircraft on the ground or with the terminal area of an airport.
Source
<xs:element name="communicationClass" type="enum:CommunicationClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Class” field will designate the major grouping of the Communication Types contained in the record.</xs:documentation></xs:annotation></xs:element>
<xs:element name="translation" type="type:Translation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Translation” field is used to provide a decoding of a three character Communication Type (5.101).</xs:documentation></xs:annotation></xs:element>
The Communication Type is found in government source provided in accordance with ICAO standards.
enumeration
Faa
The Communication Type is found in government source provided in accordance with US FAA standards.
enumeration
IcaoAndFaa
The Communication Type is found in government source provided in accordance with both ICAO and US FAA standards.
enumeration
LocalCountry
The Communication Type is found in government source provided by the country in which the communication is used.
enumeration
OtherLocalCountry
The Communication Type is found in government source provided by the country in which the communication is used.
enumeration
MadeUp
The Communication Type has been established by the data supplier.
Source
<xs:element name="typeRecognizedBy" type="enum:TypeRecognizedBy" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Type Recognized By” field is used to provide an indication of the provider of a given Communication Type (5.101).</xs:documentation></xs:annotation></xs:element>
Type is used on Airport Communication Records only
enumeration
EnrouteComms
Type is used on Enroute Communication Records only
enumeration
HeliportComms
Type is used on Heliport Communication Records only
enumeration
AirportHeliportEnrouteComms
Type is used on Airport, Heliport and Enroute Communication Records
enumeration
AiportHeliportComms
Type is used on Airport and Heliport Communication Records
Source
<xs:element name="usedOn" type="enum:UsedOn" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Used On” field provides an indication of what kind of communication records a particular Communication Type is used on.</xs:documentation></xs:annotation></xs:element>
<xs:element name="vorFrequency" type="type:Frequency" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This data element identifies frequency information on the navaid.</xs:documentation></xs:annotation></xs:element>
The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense.
<xs:element name="navaidClass" type="type:VhfNavaidClass" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense.</xs:documentation></xs:annotation></xs:element>
<xs:element name="dmeRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field idenifies a reference to a DME navaid which originated in the same source data record as the VOR (i.e. is paired with the VOR)</xs:documentation></xs:annotation></xs:element>
For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.
<xs:element name="stationDeclination" type="type:StationDeclination" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.</xs:documentation></xs:annotation></xs:element>
The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.
Extended High Altitude Use (generally beyond 130NM)
enumeration
NotNOTAMd
Navaid Not included in a civil international NOTAM system
enumeration
OutOfService
Navaid Out of Service
Source
<xs:element name="figureOfMerit" type="enum:FigureOfMerit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.</xs:documentation></xs:annotation></xs:element>
<xs:element name="frequencyProtection" type="type:FrequencyProtectionDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Frequency Protection” field provides an indication of the distance to the next nearest NAVAID on the same frequency.</xs:documentation></xs:annotation></xs:element>
<xs:element name="navaidSynchronization" type="enum:NavaidSynchronization" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field identifies if the navaid is synchronized.</xs:documentation></xs:annotation></xs:element>
<xs:element name="navaidLimitations" type="type:NavaidLimitation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field represents the navaid limitations.</xs:documentation></xs:annotation></xs:element>
<xs:element name="vorFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This data element identifies VHF frequency that corresponds to the actual DME or TACAN frequency.</xs:documentation></xs:annotation></xs:element>
The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense.
<xs:element name="navaidClass" type="type:VhfNavaidClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense.</xs:documentation></xs:annotation></xs:element>
The DME Operational Service Volume field is used to specify the service volume information of DME Navaids to support using DMEDME and DME-DME-IRU FMS capabilities in RNAV procedures and routes.
<xs:element name="dmeOperationalServiceVolume" type="enum:DMEOperationalServiceVolume" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The DME Operational Service Volume field is used to specify the service volume information of DME Navaids to support using DMEDME and DME-DME-IRU FMS capabilities in RNAV procedures and routes.</xs:documentation></xs:annotation></xs:element>
<xs:element name="ilsDmeLocation" type="enum:ILSDMELocation" minOccurs="0" maxOccurs="1"><!-- Part of facility characteristics --><xs:annotation><xs:documentation>This field identifies information about co-location with ILS facilities if the field is related to an ILS facility.</xs:documentation></xs:annotation></xs:element>
<xs:element name="ilsDMEBias" type="type:ILSDMEBias" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is used to specify the DME offset</xs:documentation></xs:annotation></xs:element>
A “Route Inappropriate Navaid Indicator” is used when a DME navaid has source provided information identifying the navaid as inappropriate for use in navigation solutions for one or more RNAV 1 and RNAV 2 routes.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="routeInappropriateDME" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A “Route Inappropriate Navaid Indicator” is used when a DME navaid has source provided information identifying the navaid as inappropriate for use in navigation solutions for one or more RNAV 1 and RNAV 2 routes.</xs:documentation></xs:annotation></xs:element>
The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.
Extended High Altitude Use (generally beyond 130NM)
enumeration
NotNOTAMd
Navaid Not included in a civil international NOTAM system
enumeration
OutOfService
Navaid Out of Service
Source
<xs:element name="figureOfMerit" type="enum:FigureOfMerit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.</xs:documentation></xs:annotation></xs:element>
Indicates whether this DME or TACAN originates from the same source record as a VOR with the same identifier.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
maxOccurs
1
Source
<xs:element name="isPaired" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Indicates whether this DME or TACAN originates from the same source record as a VOR with the same identifier.</xs:documentation></xs:annotation></xs:element>
This field identifies if the navaid is part of a Precision MLS.
Diagram
Type
xs:boolean
Properties
content
simple
minOccurs
0
Source
<xs:element name="isMlsP" type="xs:boolean" minOccurs="0"><xs:annotation><xs:documentation>This field identifies if the navaid is part of a Precision MLS.</xs:documentation></xs:annotation></xs:element>
<xs:element name="frequencyProtection" type="type:FrequencyProtectionDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Frequency Protection” field provides an indication of the distance to the next nearest NAVAID on the same frequency.</xs:documentation></xs:annotation></xs:element>
<xs:element name="navaidLimitations" type="type:NavaidLimitation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field represents the navaid limitations.</xs:documentation></xs:annotation></xs:element>
<xs:complexType name="Airport"><xs:annotation><xs:documentation>This following record contains the fields used in Airport Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Port"><xs:sequence><xs:element name="controlledASArptIndicator" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “port” field references the airport or heliport to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element><xs:element name="controlledASIndicator" type="enum:ControlledASIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Indicator” field is used to indicate if an airport is associated with controlled airspace of a terminal type such as a Terminal Control Area (TMA or TCA) Radar Area or Class B or C Airspace within the USA.</xs:documentation></xs:annotation></xs:element><xs:element name="longestRunway" type="type:LongestRunway" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Longest Runway” field permits airport to be classified on</xs:documentation></xs:annotation></xs:element><xs:element name="longestRunwaySurfaceCode" type="enum:LongestRunwaySurfaceCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Longest Runway Surface Code” field is used to define whether or not there is a hard surface runway at the airport, the length of which is indicated in the Longest Runway field.</xs:documentation></xs:annotation></xs:element><xs:element name="runway" type="Runway" minOccurs="0" maxOccurs="unbounded"/><xs:element name="airportGate" type="AirportGate" minOccurs="0" maxOccurs="unbounded"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Port" abstract="true"><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="elevation" type="type:Elevation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Elevation of the highest elevation of any landing surface on the port in feet.</xs:documentation></xs:annotation></xs:element><xs:element name="ataIATADesignator" type="type:ATAIATADesignator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The ATA/IATA field contains the Airport/Heliport ATA/IATA designator code to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element><xs:element name="daylightIndicator" type="type:DaylightIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Daylight” Time Indicator” field is used to indicate if the airport observes Daylight or Summer time when such time changes are in effect for the country or state the airport resides in.</xs:documentation></xs:annotation></xs:element><xs:element name="ifrCapability" type="type:IFRCapability" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “IFR Capability” field indicates if the Airport/Heliport has any published Instrument Approach Procedures.</xs:documentation></xs:annotation></xs:element><xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element><xs:element name="publicMilitaryIndicator" type="enum:PublicMilitaryIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.</xs:documentation></xs:annotation></xs:element><xs:element name="recommendedNavaid" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Recommended Navaid” field allows the reference facility for the waypoint in a given record “Fix Ident” field or for an Airport or Heliport to be specified. VHF, NDB (Enroute and Terminal), Localizer, TACAN, GLS and MLS Navaids may be referenced.</xs:documentation></xs:annotation></xs:element><xs:element name="speedLimit" type="type:SpeedLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Speed Limit field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.</xs:documentation></xs:annotation></xs:element><xs:element name="speedLimitAltitude" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Speed Limit Altitude” is the altitude below which speed limits may be imposed.</xs:documentation></xs:annotation></xs:element><xs:element name="timeZone" type="type:TimeZone" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The standard time zone system is based on the division of world into 24 zones, each of 15 degrees longitude. The “zero” time zone is entered at Greenwich meridian with longitudes 7 degrees, 30 minutes West and 7 degrees, 30 minutes east, and there is no difference in the standard time of this time zone and Greenwich Mean Time. Time zones are designated by letters of the alphabet and numbers by which the standard time of each zone differs from that at Greenwich.</xs:documentation></xs:annotation></xs:element><xs:element name="transitionAltitude" type="type:TransitionAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element><xs:element name="transitionLevel" type="type:TransitionAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element><xs:element name="terminalNDB" type="TerminalNDB" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>"Terminal NDB" field contains NDBs associated with the Airports and Heliports</xs:documentation></xs:annotation></xs:element><xs:element name="terminalProcedures" type="TerminalProcedures" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Collectively, all Standard Instrument Departures (SIDs), Standard Terminal Arrivel Routes (STARs) and Instument Approach Procedures (IAPs) coded to the standards in this specification are referred to as Terminal Procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="terminalWaypoint" type="TerminalWaypoint" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Terminal Waypoint field contains all terminal waypoints and VFR waypoints within the geographical area of each airport/heliport. Terminal waypoints utilized by two or more airports will be stored in the Enroute Waypoint Subsection to eliminate duplication. Terminal waypoints used jointly by and airoprt and a heliport are also stored in the Enroute waypoint section.</xs:documentation></xs:annotation></xs:element><xs:element name="taa" type="TAA" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>The Airport TAA (Terminal Arrival Altitude) field contains the Sector Bearing, Sector Radii, and Section Altitudes for all government published Approach Procedures</xs:documentation></xs:annotation></xs:element><xs:element name="portCommunication" type="PortCommunication" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Port Communication field contain all government published airport communication facilites for particular airoprts.</xs:documentation></xs:annotation></xs:element><xs:element name="helipad" type="Helipad" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Helipad field will contain a listing of all helipads associated with airports.</xs:documentation></xs:annotation></xs:element><xs:element name="localizerMarker" type="AirportHeliportLocalizerMarker" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>The Airport and Heliport Localizer Marker field contains details about all markers and locators associated with all types of localizers. It does not contain airway marker.</xs:documentation></xs:annotation></xs:element><xs:element name="localizerGlideslope" type="LocalizerGlideslope" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Localizer Glidescope field should contain all government published localizer type facilities to airport runways and/or helipad. As a minimum, this field should contain all localizer type facilities.</xs:documentation></xs:annotation></xs:element><xs:element name="gls" type="GLS" minOccurs="0" maxOccurs="unbounded"/><xs:element name="mls" type="MLS" minOccurs="0" maxOccurs="unbounded"/><xs:element name="msa" type="MSA" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>The Minimum Sector Altitude (MSA) field contains details relating to available sector altitudes.</xs:documentation></xs:annotation></xs:element><xs:element name="flightPlanningArrivalDepartureRecords" type="FlightPlanningRecords" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Flight Planning Arrival/Departure record is used to provide the sub-set of data defining SIDs, STARs, and Approach Procedures required for the computer generation of Flight Plans whihc include Terminal Procedure. This contains a sequential listing of published Arrival Procedures, Approach Procedures and Departure Procedures, the availabel Enroute and Runway Transitions for those procedures, the Transition waypoints, the appropriate along track distance fields, and the intermediate fixed along those routes.</xs:documentation></xs:annotation></xs:element><xs:element name="categoryDistance" type="type:CategoryDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Category Radii” fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="maxHelicopterWeight" type="type:MaxHelicopterWeight"><xs:annotation><xs:documentation>This element provides the maximum weight that the helipad or FATO can support.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="A424Point" abstract="true"><xs:annotation><xs:documentation>Abstract superclass for any class that has a latitude and longitude</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="datumCode" type="enum:DatumCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Datum Code field defines the Local Horizontal Reference Datum to which a geographical position, expressed in latitude and longitude, is associated.</xs:documentation></xs:annotation></xs:element><xs:element name="icaoCode" type="type:IcaoCode" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “ICAO Code” field permits records to be categorized geographically within the limits of the categorization performed by the “Area Code” field.</xs:documentation></xs:annotation></xs:element><xs:element name="identifier" type="type:CoreIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The identifier field contains the five-character-name-code, or other series of characters, with which the fix is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, and Airport Identifiers</xs:documentation></xs:annotation></xs:element><xs:element name="location" type="type:Location" minOccurs="1" maxOccurs="1"/><xs:element name="magneticVariation" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.</xs:documentation></xs:annotation></xs:element><xs:element name="name" type="type:Name" minOccurs="0" maxOccurs="1"/><xs:element name="uirRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The UIR Reference field identifies the Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The reference is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element><xs:element name="firRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The FIR Reference field identifies the Flight Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The reference is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element></xs:sequence><xs:attribute name="referenceID" use="required" type="xs:ID"/></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="A424Record" abstract="true"><xs:annotation><xs:documentation>Represents an ARINC 424 record type</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Base"><xs:sequence><xs:element name="custAreaCode" type="type:CustAreaCode" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.</xs:documentation></xs:annotation></xs:element><xs:element name="cycleDate" type="type:CycleDate" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For the concrete data type that implements A424Record the cycle date represents the last time the children elements changed. This only applies to elements with the same arity as this cycle date element. For example the cycle date that is a first child of a Procedure does not indicate if children of a Leg changed.</xs:documentation></xs:annotation></xs:element><xs:element name="notes" type="type:NotesText" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is used to have relevant Notes</xs:documentation></xs:annotation></xs:element><xs:element name="recordType" type="enum:RecordType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Record Type” field content indicates whether the record data are “standard,” i.e., suitable for universal application, or “tailored,” i.e. included for a single user’s specific purpose . Record type is set to tailored if any extension points are included in the record or if any content of the ARINC 424 XML schemas are altered in any way.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="A424Base" abstract="true"><xs:annotation><xs:documentation>Base Class for the A424 Records.</xs:documentation></xs:annotation><xs:sequence><xs:element name="supplementalData" type="SupplementalData" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is for private and/or temporary exchanges of data.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
ANY element from namespace(s) 'http://www.mitre.org/ARINC/extensions, http://www.navtech.aero/ARINC/extensions,
http://www.garmin.com/ARINC/extensions, http://www.agustawestland-ans.com/ARINC/extensions,
http://www.NGA.mil'
Source
<xs:complexType name="SupplementalData"><xs:sequence><xs:any namespace="http://www.mitre.org/ARINC/extensions, http://www.navtech.aero/ARINC/extensions, http://www.garmin.com/ARINC/extensions, http://www.agustawestland-ans.com/ARINC/extensions, http://www.NGA.mil" processContents="strict" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>xs:any provides the ability to extend ARINC 424 with custom data. An organization that creates an extension should define a namespace for the extension. This element is what identifies a valid namespace for the extensions. A user should add the namespace, if not already provided in this element's definition to the namespace attribute. The namespace must be different than the default namespace and or any namespace used outside of extensions to this standard.</xs:documentation></xs:annotation></xs:any></xs:sequence></xs:complexType>
The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.
<xs:complexType name="CustAreaCode"><xs:annotation><xs:documentation>The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Alpha"><xs:choice><xs:element name="areaCode" type="enum:AreaCode" minOccurs="1" maxOccurs="1"/><xs:element name="customerCode" type="type:CustomerCode" minOccurs="1" maxOccurs="1"/></xs:choice></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Alpha"><xs:annotation><xs:documentation>This Class represents the "Alpha" character type of the Arinc 424 data.</xs:documentation></xs:annotation><xs:sequence/></xs:complexType>
The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.
<xs:simpleType name="AreaCode"><xs:annotation><xs:documentation>The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AFR"><xs:annotation><xs:documentation>Africa</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CAN"><xs:annotation><xs:documentation>Canada</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="EEU"><xs:annotation><xs:documentation>Eastern Europe and Asia</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="EUR"><xs:annotation><xs:documentation>Europe</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LAM"><xs:annotation><xs:documentation>Latin America</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MES"><xs:annotation><xs:documentation>Middle East</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PAC"><xs:annotation><xs:documentation>Pacific</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SAM"><xs:annotation><xs:documentation>South America</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SPA"><xs:annotation><xs:documentation>South Pacific</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="USA"><xs:annotation><xs:documentation>United States</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.
<xs:simpleType name="CustomerCode"><xs:annotation><xs:documentation>The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:pattern value="[a-zA-Z0-9]{2,3}"/></xs:restriction></xs:simpleType>
The "Cycle Date" field identifies the calendar period in which the record was added to the file or last revised. A change in any ARINC 424 field, except Dynamic Magnetic Variation, Frequency Protection, Continuation Record Number and File Record Number, requires a cycle date change. The cycle date will not change if there is no change in the data.The first two digits of the field contain the last two digits of the year in which the addition or revision was made. The last two digits contain the numeric identity of the 28-day data update cycle during which the change occurred. Each calendar year contains 13 such cycles; however, on rare occasions 14 cycles will be encountered. Note: This field does not indicate changes on elements/attributes of type ID or IDREF.
<xs:simpleType name="CycleDate"><xs:annotation><xs:documentation>The "Cycle Date" field identifies the calendar period in which the record was added to the file or last revised. A change in any ARINC 424 field, except Dynamic Magnetic Variation, Frequency Protection, Continuation Record Number and File Record Number, requires a cycle date change. The cycle date will not change if there is no change in the data. The first two digits of the field contain the last two digits of the year in which the addition or revision was made. The last two digits contain the numeric identity of the 28-day data update cycle during which the change occurred. Each calendar year contains 13 such cycles; however, on rare occasions 14 cycles will be encountered. Note: This field does not indicate changes on elements/attributes of type ID or IDREF.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:minLength value="4"/><xs:maxLength value="4"/></xs:restriction></xs:simpleType>
<xs:simpleType name="NotesText"><xs:annotation><xs:documentation>The “Notes” field is provided to accommodate any information that cannot be entered in the primary record.</xs:documentation></xs:annotation><xs:restriction base="xs:string"/></xs:simpleType>
The “Record Type” field content indicates whether the record data are “standard,” i.e., suitable for universal application, or “tailored,” i.e. included on the master file for a single user’s specific purpose . Record type is set to tailored if any extension points are included in the record or if any ARINC 424 XML schemas are modified.
<xs:simpleType name="RecordType"><xs:annotation><xs:documentation>The “Record Type” field content indicates whether the record data are “standard,” i.e., suitable for universal application, or “tailored,” i.e. included on the master file for a single user’s specific purpose . Record type is set to tailored if any extension points are included in the record or if any ARINC 424 XML schemas are modified.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Standard"><xs:annotation><xs:documentation>Standard</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Tailored"><xs:annotation><xs:documentation>Tailored</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Datum Code field defines the Local Horizontal Reference Datum to which a geographical position, expressed in latitude and longitude, is associated.
Diagram
Type
restriction of xs:string
Facets
length
3
enumeration
ADI
Adindan
enumeration
AFG
Afgooye
enumeration
AIA
Antigua Island Astro 1943
enumeration
AIN
Ain El Abd 1970
enumeration
AMA
American Samoa 1962
enumeration
ANO
Anna 1 Astro 1965
enumeration
ANS
Austria NS
enumeration
ARF
Arc 1950
enumeration
ARS
Arc 1960
enumeration
ASC
Ascension Island 1958
enumeration
ASM
Montserrat Island Astro 1958
enumeration
ASQ
Astronomical Station 1952
enumeration
ATF
Astro Beacon “E� 1945
enumeration
AUA
Australian Geodetic 1966
enumeration
AUG
Australian Geodetic 1984
enumeration
BAT
Djakarta (Batavia)
enumeration
BER
Bermuda 1957
enumeration
BID
Bissau
enumeration
BOO
Bogota Observatory
enumeration
BUR
Bukit Rimpah
enumeration
CAC
Cape Canaveral
enumeration
CAI
Campo Inchauspe 1969
enumeration
CAO
Canton Astro 1966
enumeration
CAP
Cape
enumeration
CAZ
Camp Area Astro
enumeration
CCD
S-JTSK
enumeration
CGE
Carthage
enumeration
CHI
Chatham Island Astro 1971
enumeration
CHU
Chua Astro
enumeration
COA
Corrego Alegre
enumeration
DAL
Dabola
enumeration
DAN
Danish Geodetic Institute 1934 System
enumeration
DID
Deception Island
enumeration
DOB
GUX 1 Astro
enumeration
EAS
Easter Island 1967
enumeration
ENW
Wake-Eniwetok, 1960
enumeration
EST
Co-Ordinate System 1937 of Estonia
enumeration
EUR
European 1950
enumeration
EUS
European 1979
enumeration
FAH
Oman
enumeration
FLO
Observatorio Meteorologico 1939
enumeration
FOT
Fort Thomas 1955
enumeration
GAA
Gan 1970
enumeration
GAN
Gandajika Base
enumeration
GEO
Geodetic Datum 1949
enumeration
GIZ
DOS 1968
enumeration
GRA
Graciosa Base SW 1948
enumeration
GRX
Greek Geodetic Reference System 1987
enumeration
GSE
Gunuung Segara
enumeration
GUA
Guam 1963
enumeration
HEN
Herat North
enumeration
HER
Hermannskogel
enumeration
HIT
Provisional South Chilean 1963 (also known as Hito XVIII 1963)
enumeration
HJO
Hjorsey 1955
enumeration
HKD
Hong Kong 1963
enumeration
HTN
Hu-Tzu-Shan
enumeration
IBE
Bellevue (IGN)
enumeration
IDN
Indonesian 1974
enumeration
IGF
Nouvelle Triangulation de France (FRANCE)
enumeration
IND
Indian
enumeration
INF
Indian 1954
enumeration
ING
Indian 1960
enumeration
INH
Indian 1975
enumeration
IRL
Ireland 1965
enumeration
ISG
ISTS 061 Astro 1968
enumeration
IST
ISTS 073 Astro 1969
enumeration
JOH
Johnston Island 1961
enumeration
KAN
Kandawala
enumeration
KEA
Kertau 1948
enumeration
KEG
Kerguelen Island 1949
enumeration
KUS
Kusaie Astro 1951
enumeration
LCF
L.C. 5 Astro 1961
enumeration
LEH
Leigon
enumeration
LIB
Liberia 1964
enumeration
LUZ
Luzon
enumeration
MAS
Massawa
enumeration
MCN
Manchurian Principal System
enumeration
MER
Merchich
enumeration
MID
Midway Astro 1961
enumeration
MIK
Mahe 1971
enumeration
MIN
Minna
enumeration
MOD
Rome 1940
enumeration
MOL
Montjong Lowe
enumeration
MPO
M'Poraloko
enumeration
MVS
Viti Levu 1916
enumeration
NAH
Nahrwan
enumeration
NAN
Nanking 1960
enumeration
NAP
Naparima, BWI
enumeration
NAR
North American 1983
enumeration
NAS
North American 1927
enumeration
NSD
North Sahara 1959
enumeration
OEG
Old Egyptian 1907
enumeration
OGB
Ordnance Survey of Great Britain 1936
enumeration
OHA
Old Hawaiian
enumeration
PAM
Palmer Astro
enumeration
PDM
Potsdam
enumeration
PHA
Ayabelle Lighthouse
enumeration
PIT
Pitcairn Astro 1967
enumeration
PLN
Pico de las Nieves
enumeration
POS
Porto Santo 1936
enumeration
PRD
Portuguese Datum 1973
enumeration
PRP
Provisional South American 1956
enumeration
PTB
Point 58
enumeration
PTN
Point Noire 1948
enumeration
PUK
Pulkovo 1942
enumeration
PUR
Puerto Rico
enumeration
QAT
Qatar National
enumeration
QUO
Qornoq
enumeration
REU
Reunion
enumeration
RPE
Parametrop Zemp 1990 (English translation) The Parameters of the Earth 1990
<xs:simpleType name="IcaoCode"><xs:annotation><xs:documentation>This element provides the 2 character code to identify a state</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:pattern value="[a-zA-Z0-9]{2}"/></xs:restriction></xs:simpleType>
The “Core Identifier” field contains the character-name-code, or other series of characters, with which the object is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, Airport Identifiers, Runway Identifiers, and other objects.
<xs:simpleType name="CoreIdentifier"><xs:annotation><xs:documentation>The “Core Identifier” field contains the character-name-code, or other series of characters, with which the object is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, Airport Identifiers, Runway Identifiers, and other objects.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="16"/></xs:restriction></xs:simpleType>
The “Latitude” field contains the latitude of the navigational feature identified in the record. The latitude is a complex type that consists of children elements that contain scaled integers.
<xs:complexType name="Latitude"><xs:annotation><xs:documentation>The “Latitude” field contains the latitude of the navigational feature identified in the record. The latitude is a complex type that consists of children elements that contain scaled integers.</xs:documentation></xs:annotation><xs:sequence><xs:element name="deg" type="type:LatDegree" minOccurs="1" maxOccurs="1"/><xs:element name="min" type="type:Minute" minOccurs="1" maxOccurs="1"/><xs:element name="sec" type="type:Second" minOccurs="1" maxOccurs="1"/><xs:element name="hSec" type="type:HundredthSecond" minOccurs="1" maxOccurs="1"/><xs:element name="northSouth" type="enum:NorthSouth" minOccurs="1" maxOccurs="1"/><xs:element name="decimalDegreesLatitude" type="xs:decimal" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is optional for convenience in data processing. The value of this field is not authoritative.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="LatDegree"><xs:annotation><xs:documentation>Contains degrees of a coordinate as an integer. e.g., 90, -89</xs:documentation></xs:annotation><xs:restriction base="type:LatLongDegree"><xs:maxInclusive value="90"/><xs:minInclusive value="0"/></xs:restriction></xs:simpleType>
<xs:simpleType name="LatLongDegree"><xs:annotation><xs:documentation>This is an abstract class that is the parent class for degrees.</xs:documentation></xs:annotation><xs:restriction base="xs:int"/></xs:simpleType>
<xs:simpleType name="Minute"><xs:annotation><xs:documentation>Contains minutes of a coordinate as an integer. e.g., 0, 60</xs:documentation></xs:annotation><xs:restriction base="xs:int"><xs:maxExclusive value="60"/><xs:minInclusive value="0"/></xs:restriction></xs:simpleType>
<xs:simpleType name="Second"><xs:annotation><xs:documentation>Contains seconds of a coordinate as an integer. e.g., 0, 60</xs:documentation></xs:annotation><xs:restriction base="xs:int"><xs:maxExclusive value="60"/><xs:minInclusive value="0"/></xs:restriction></xs:simpleType>
<xs:simpleType name="HundredthSecond"><xs:annotation><xs:documentation>Contains hundredths of a coordinate as an integer. e.g., 0, 99</xs:documentation></xs:annotation><xs:restriction base="xs:int"><xs:maxInclusive value="99"/><xs:minInclusive value="0"/></xs:restriction></xs:simpleType>
<xs:simpleType name="NorthSouth"><xs:annotation><xs:documentation>This data type indicates if latitude is north or south.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="North"><xs:annotation><xs:documentation>North</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="South"><xs:annotation><xs:documentation>South</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="Longitude"><xs:annotation><xs:documentation>The Longitude field contains the longitude of the geographic position of the navigational feature identified in the record.</xs:documentation></xs:annotation><xs:sequence><xs:element name="deg" type="type:longDegree" minOccurs="1" maxOccurs="1"/><xs:element name="min" type="type:Minute" minOccurs="1" maxOccurs="1"/><xs:element name="sec" type="type:Second" minOccurs="1" maxOccurs="1"/><xs:element name="hSec" type="type:HundredthSecond" minOccurs="1" maxOccurs="1"/><xs:element name="eastWest" type="enum:EastWest" minOccurs="1" maxOccurs="1"/><xs:element name="decimalDegreesLongitude" type="xs:decimal" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is optional for convenience in data processing. The value of this field is not authoritative.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="EastWest"><xs:annotation><xs:documentation>This data type indicates if the longitude is east or west.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="East"><xs:annotation><xs:documentation>East</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="West"><xs:annotation><xs:documentation>West</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.
<xs:complexType name="MagneticVariation"><xs:annotation><xs:documentation>The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.</xs:documentation></xs:annotation><xs:sequence><xs:element name="magneticVariationEWT" type="enum:MagneticVariationEWT" minOccurs="1" maxOccurs="1"/><xs:element name="magneticVariationValue" type="type:MagneticVariationValue" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
The Magnetic Variation field specifies the angular difference between True North and Magnetic North at the location defined in the record. Dynamic Magnetic Variation is a computer model derived value and takes location and date into consideration. For the Station Declination used in some record types, refer to Section 5.66.
Diagram
Type
restriction of xs:string
Facets
enumeration
East
Magnetic variation is East of TRUE North
enumeration
West
Magnetic variation is West of TRUE North
enumeration
True
The element defined in the current record is provided TRUE.
<xs:simpleType name="MagneticVariationEWT"><xs:annotation><xs:documentation>The Magnetic Variation field specifies the angular difference between True North and Magnetic North at the location defined in the record. Dynamic Magnetic Variation is a computer model derived value and takes location and date into consideration. For the Station Declination used in some record types, refer to Section 5.66.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="East"><xs:annotation><xs:documentation>Magnetic variation is East of TRUE North</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="West"><xs:annotation><xs:documentation>Magnetic variation is West of TRUE North</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="True"><xs:annotation><xs:documentation>The element defined in the current record is provided TRUE.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.
<xs:simpleType name="MagneticVariationValue"><xs:annotation><xs:documentation>The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"><xs:minInclusive value="0"/><xs:maxInclusive value="180"/><xs:totalDigits value="4"/><xs:fractionDigits value="1"/></xs:restriction></xs:simpleType>
<xs:simpleType name="Name"><xs:annotation><xs:documentation>The “Name” field defines the name commonly applied to the navigation entity defined in the record.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="50"/></xs:restriction></xs:simpleType>
<xs:simpleType name="Elevation"><xs:annotation><xs:documentation>Elevation of the respective feature.</xs:documentation></xs:annotation><xs:restriction base="xs:int"><xs:maxInclusive value="20000"/><xs:minInclusive value="-1500"/></xs:restriction></xs:simpleType>
<xs:simpleType name="ATAIATADesignator"><xs:annotation><xs:documentation>The “ATA/IATA” field contains the Airport/Heliport ATA/IATA designator code to which the data contained in the record relates.</xs:documentation></xs:annotation><xs:restriction base="xs:string"/></xs:simpleType>
The “Daylight” Time Indicator” field is used to indicate if the airport observes Daylight or Summer time when such time changes are in effect for the country or state the airport resides in.
<xs:simpleType name="DaylightIndicator"><xs:annotation><xs:documentation>The “Daylight” Time Indicator” field is used to indicate if the airport observes Daylight or Summer time when such time changes are in effect for the country or state the airport resides in.</xs:documentation></xs:annotation><xs:restriction base="xs:boolean"/></xs:simpleType>
<xs:simpleType name="IFRCapability"><xs:annotation><xs:documentation>The “IFR Capability” field indicates if the Airport/Heliport has any published Instrument Approach Procedures.</xs:documentation></xs:annotation><xs:restriction base="xs:boolean"/></xs:simpleType>
The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.
Diagram
Type
restriction of xs:string
Facets
enumeration
Both
The field will be blank if details and procedures are provided in both magnetic and true for the airport. In such cases the individual detail or procedure records will contain the magnetic or true information
enumeration
True
if all detail and procedure for the airport are reported in true bearing
enumeration
Magnetic
if all detail and procedure for the airport are reported in magnetic bearing,
<xs:simpleType name="MagneticTrueIndicator"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Both"><xs:annotation><xs:documentation>The field will be blank if details and procedures are provided in both magnetic and true for the airport. In such cases the individual detail or procedure records will contain the magnetic or true information</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="True"><xs:annotation><xs:documentation>if all detail and procedure for the airport are reported in true bearing</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Magnetic"><xs:annotation><xs:documentation>if all detail and procedure for the airport are reported in magnetic bearing,</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.
Diagram
Type
restriction of xs:string
Facets
enumeration
Private
Airport/Heliport is not open to the public (private)
<xs:simpleType name="PublicMilitaryIndicator"><xs:annotation><xs:documentation>Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Private"><xs:annotation><xs:documentation>Airport/Heliport is not open to the public (private)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Civil"><xs:annotation><xs:documentation>Airport/Heliport is open to the public (civil)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Military"><xs:annotation><xs:documentation>Airport/Heliport is military airport</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Joint"><xs:annotation><xs:documentation>Airport is joint Civil and Military</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="PointReference"><xs:annotation><xs:documentation>This element provides a way to reference any child element of A424Point.</xs:documentation></xs:annotation><xs:simpleContent><xs:extension base="xs:IDREF"/></xs:simpleContent></xs:complexType>
The Speed Limit field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.
<xs:simpleType name="SpeedLimit"><xs:annotation><xs:documentation>The Speed Limit field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:maxExclusive value="1000"/></xs:restriction></xs:simpleType>
The "Altitude/Minimum Altitude" field is a choice element that may contain one of either an element of type FlightLevel or an element of type Altitude.The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Elements and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.
<xs:complexType name="Altitude"><xs:annotation><xs:documentation>The "Altitude/Minimum Altitude" field is a choice element that may contain one of either an element of type FlightLevel or an element of type Altitude. The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Elements and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isNotDefined" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isUnknown" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFlightLevel" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this field is true, then the numerical value in the altitude element is populated with a flight level. Therefore, the sibling altitude element represents the altitude in hundreds of feet, else the altitude element represents altitude in feet.</xs:documentation></xs:annotation></xs:element><xs:element name="altitude" type="type:AltitudeValue" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
The all-numeric altitude field will contain altitudes in feet with a resolution of one foot. If isFlightLevel is true, this element represents altitude as a flight level. The contents of this field only contain the numerical portion of the flight level expressed in hundreds of feet (e.g., 120, 1, or 10).
<xs:simpleType name="AltitudeValue"><xs:annotation><xs:documentation>The all-numeric altitude field will contain altitudes in feet with a resolution of one foot. If isFlightLevel is true, this element represents altitude as a flight level. The contents of this field only contain the numerical portion of the flight level expressed in hundreds of feet (e.g., 120, 1, or 10).</xs:documentation></xs:annotation><xs:restriction base="xs:int"><xs:maxInclusive value="99999"/><xs:minInclusive value="-2000"/></xs:restriction></xs:simpleType>
The standard time zone system is based on the division of world into 24 zones, each of 15 degrees longitude. The “zero” time zone is entered at Greenwich meridian with longitudes 7 degrees, 30 minutes West and 7 degrees, 30 minutes east, and there is no difference in the standard time of this time zone and Greenwich Mean Time. Time zones are designated by an integer offset from Greenwich Mean Time, which represets the time difference from GMT in hours, and a minute offset for non-standard time zone offsets. (See ARINC 424 5.178 for further explanation.)
<xs:complexType name="TimeZone"><xs:annotation><xs:documentation>The standard time zone system is based on the division of world into 24 zones, each of 15 degrees longitude. The “zero” time zone is entered at Greenwich meridian with longitudes 7 degrees, 30 minutes West and 7 degrees, 30 minutes east, and there is no difference in the standard time of this time zone and Greenwich Mean Time. Time zones are designated by an integer offset from Greenwich Mean Time, which represets the time difference from GMT in hours, and a minute offset for non-standard time zone offsets. (See ARINC 424 5.178 for further explanation.)</xs:documentation></xs:annotation><xs:sequence><xs:element name="hourOffset"><xs:simpleType><xs:restriction base="xs:int"><xs:minInclusive value="-14"/><xs:maxInclusive value="12"/></xs:restriction></xs:simpleType></xs:element><xs:element name="minuteOffset" type="xs:int" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.
<xs:simpleType name="TransitionAltitude"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation><xs:restriction base="type:AltitudeValue"><xs:totalDigits value="5"/></xs:restriction></xs:simpleType>
<xs:complexType name="TerminalNDB"><xs:annotation><xs:documentation>This following record contains the fields used in NDB NAVAID Primary Records Record</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="NDB"><xs:sequence/></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="NDB"><xs:complexContent><xs:extension base="Navaid"><xs:sequence><xs:element name="ndbClass" type="type:NdbNavaidClass" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.</xs:documentation></xs:annotation></xs:element><xs:element name="ndbFrequency" type="type:Frequency" minOccurs="1" maxOccurs="1"/><xs:element name="typeOfEmission" type="enum:TypeOfEmission" minOccurs="0" maxOccurs="1"/><xs:element name="repititionRate" type="type:RepetitionRate" minOccurs="0" maxOccurs="1"/><xs:element name="navaidNdbEmissionType" type="enum:NavaidNDBEmissionType" minOccurs="0" maxOccurs="1"/><xs:element name="dmeRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field idenifies a reference to a DME navaid which originated in the same source data record as the NDB (i.e. is paired with the NDB)</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Navaid" abstract="true"><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="portRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Defines the location of a designated point using a combination of angles and distances based on the guidance service. The set of angles and distances must not under specify the location.</xs:documentation></xs:annotation></xs:element><!-- Note: 'elevation' is in the primary record for DME and precision approach navaids, and in the simulation continuation record for VORs and NDBs --><xs:element name="elevation" type="type:Elevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Elevation of the navaid location in feet.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="NdbNavaidClass"><xs:sequence><xs:element name="isBFORequired" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>BFO Operation. Use of Beat Frequency Oscillator type of equipment is required to received an aural identification signal.</xs:documentation></xs:annotation></xs:element><xs:element name="ndbNavaidCoverage" type="enum:NdbNavaidCoverage" minOccurs="0" maxOccurs="1"/><xs:element name="ndbNavaidIfMarker" type="enum:NdbNavaidIfMarkerInfo" minOccurs="0" maxOccurs="1"/><xs:element name="ndbNavaidType" type="enum:NdbNavaidType" minOccurs="1" maxOccurs="1"/><xs:element name="ndbNavaidWeatherInfo" type="enum:NavaidWeatherInfo" minOccurs="0" maxOccurs="1"/><xs:element name="isNoVoice" type="xs:boolean" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="NdbNavaidCoverage"><xs:annotation><xs:documentation>The field NDBNavaidCoverage is the first character of the 5 character Navaid class, When used in NDB Navaid Record –NDBs and Terminal NDBs.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="HighPowerNdb"><xs:annotation><xs:documentation>High-powered NDB. Generally usable within 75NM of the facility at all altitudes.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LowPowerNdb"><xs:annotation><xs:documentation>Low-powered NDB. Generally usable within 25NM of the facility at all altitude.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Locator"><xs:annotation><xs:documentation>Locator. Generally usable within 15NM of the facility at all altitudes.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NDB"><xs:annotation><xs:documentation>NDB. Generally usable within 50NM of the facility at all altitude.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="NdbNavaidIfMarkerInfo"><xs:annotation><xs:documentation>The field NDBNavaidFacility2 is the second character of the 5 character Navaid class, when used in NDB Navaid Record – NDBs and Terminal NDBs.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="InnerMarker"><xs:annotation><xs:documentation>Inner Marker. There is an Inner Marker beacon at this location.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MiddleMarker"><xs:annotation><xs:documentation>Middle Marker. There is a Middle Marker beacon at this location.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OuterMarker"><xs:annotation><xs:documentation>Outer Marker. There is an Outer Marker beacon at this location.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="BackMarker"><xs:annotation><xs:documentation>Back Marker. There is a Backcourse Marker at this location.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The field NDBNavaidFacility1 is the first character of the 5 character Navaid class,when used in NDB Navaid Record –NDBs and Terminal NDBs. It indicates the type of navaid represented by the NDB
<xs:simpleType name="NdbNavaidType"><xs:annotation><xs:documentation>The field NDBNavaidFacility1 is the first character of the 5 character Navaid class,when used in NDB Navaid Record –NDBs and Terminal NDBs. It indicates the type of navaid represented by the NDB</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Ndb"><xs:annotation><xs:documentation>NDB</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Sabh"><xs:annotation><xs:documentation>SABH</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MarineBeacon"><xs:annotation><xs:documentation>Marine Beacon.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
This data type provides information on weather information that is broadcast from this navaid.
Diagram
Type
restriction of xs:string
Facets
enumeration
AUTOMATED
Automatic Transcribed Weather.The frequency of this Navaid is used for the continuous broadcast of some sort of automated weather system such as AWOS, ASOS, TWEB, AWIB, AWIS.
enumeration
SCHEDULED
Broadcast Scheduled Weather.The frequency of this Navaid is used for the scheduled, noncontinuous broadcast of some sort of automated weather system such as VOLMET.
<xs:simpleType name="NavaidWeatherInfo"><xs:annotation><xs:documentation>This data type provides information on weather information that is broadcast from this navaid.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AUTOMATED"><xs:annotation><xs:documentation>Automatic Transcribed Weather.The frequency of this Navaid is used for the continuous broadcast of some sort of automated weather system such as AWOS, ASOS, TWEB, AWIB, AWIS.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SCHEDULED"><xs:annotation><xs:documentation>Broadcast Scheduled Weather.The frequency of this Navaid is used for the scheduled, noncontinuous broadcast of some sort of automated weather system such as VOLMET.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="Frequency"><xs:annotation><xs:documentation>This field specifies frequency and unit of measure of the frequency information.</xs:documentation></xs:annotation><xs:sequence><xs:element name="freqUnitOfMeasure" type="enum:FreqUnitOfMeasure" minOccurs="1" maxOccurs="1"/><xs:element name="frequencyValue" type="xs:decimal" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="TypeOfEmission"><xs:annotation><xs:documentation>The Facility Characteristics field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:enumeration value="400"><xs:annotation><xs:documentation>400 Hertz</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1020"><xs:annotation><xs:documentation>1020 Hertz</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="RepetitionRate"><xs:annotation><xs:documentation>The Facility Characteristics field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:maxExclusive value="10"/><xs:minInclusive value="0"/></xs:restriction></xs:simpleType>
<xs:simpleType name="NavaidNDBEmissionType"><xs:annotation><xs:documentation>The NavaidNDBEmissionType field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="UnmodulatedCarrier"><xs:annotation><xs:documentation>Unmodulated carrier</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CarrierKeyed"><xs:annotation><xs:documentation>Carrier keyed, bandwidth less than .1 kHz and/or carrier keyed, bandwidth greater than .1 kHz</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ToneKeyModulation"><xs:annotation><xs:documentation>Tone keyed modulation</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="SID"><xs:annotation><xs:documentation>This element represents a standard instrument departure.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="SIDSTAR"><xs:sequence><xs:element name="sidRunwayTransition" type="SIDRunwayTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the runway transitions of the SID</xs:documentation></xs:annotation></xs:element><xs:element name="sidCommonRoute" type="SIDCommonRoute" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the common route of the SID</xs:documentation></xs:annotation></xs:element><xs:element name="sidEnrouteTransition" type="SIDEnrouteTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the enroute transitions of the SID</xs:documentation></xs:annotation></xs:element><xs:element name="isEngineOut" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that the SID is an Engine Out SID</xs:documentation></xs:annotation></xs:element><xs:element name="isVector" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The element indicates that the SID is a vector SID</xs:documentation></xs:annotation></xs:element><xs:element name="isPInS" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the parent is a point in space SID.</xs:documentation></xs:annotation></xs:element><xs:element name="isPInSProceedVisually" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the procedure will proceed visually.</xs:documentation></xs:annotation></xs:element><xs:element name="isPInSProceedVfr" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the SID will proceed under visual flight rules.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="SIDSTAR" abstract="true"><xs:annotation><xs:documentation>This class is the base class for SID and STAR records. It contains all the fields that are common to both SID and STAR.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Procedure"><xs:sequence><xs:element name="isVorDmeRnav" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true then the procedure is VOR/DME RNAV.</xs:documentation></xs:annotation></xs:element><xs:element name="rnavPbnNavSpec" type="enum:RnavPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNAV PBN navigation specification applies to this procedure</xs:documentation></xs:annotation></xs:element><xs:element name="rnpPbnNavSpec" type="enum:RnpPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNP PBN navigation specification applies to this procedure</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Procedure" abstract="true"><xs:annotation><xs:documentation>This abstract element is used to represent elements common to different types of terminal procedures.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424ObjectWithId"><xs:sequence><xs:element name="isRnav" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indcates whether the procedure is an RNAV procdedure.</xs:documentation></xs:annotation></xs:element><xs:element name="isHelicopterOnlyProcedure" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element is present and true the procedure is only for helicopters.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureDesignAircraftCategories" type="type:ProcedureDesignAircraftCategories" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indciates the category of aircraft that this procedure was designed to support.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureDesignAircraftTypes" type="type:ProcedureDesignAircraftTypes" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indciates the type of aircraft that this procedure was designed to support.</xs:documentation></xs:annotation></xs:element><xs:element name="isSpecial" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Definition/Description: This field provides an indicator whether the terminal procedure requires specific operational approval defined by official government sources. Special procedures may be developed based on aircraft performance, aircraft equipment, or crew training, and may also require the use of landing aids, communications, or weather services not available for public use. Examples of special procedures include: SIAP, RCAP, etc.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureDesignMagVar" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the magnetic varaiation used to design the procedure.</xs:documentation></xs:annotation></xs:element></xs:sequence><xs:attribute name="referenceID" use="required" type="xs:ID"/></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="ProcedureDesignAircraftTypes"><xs:annotation><xs:documentation>This type provides the aircraft type(s) for which the procedure or portion of a procedure (transition) was designed.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isTypeJet" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Jets only</xs:documentation></xs:annotation></xs:element><xs:element name="isTypeTurbojet" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Turbojet only</xs:documentation></xs:annotation></xs:element><xs:element name="isTypeTuroprop" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Turboprop only</xs:documentation></xs:annotation></xs:element><xs:element name="isTypeProp" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Prop only</xs:documentation></xs:annotation></xs:element><xs:element name="isTypePiston" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Pistons only</xs:documentation></xs:annotation></xs:element><xs:element name="isTypeNonJets" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Non-Jets only</xs:documentation></xs:annotation></xs:element><xs:element name="isTypeNotLimited" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Not Limited</xs:documentation></xs:annotation></xs:element><xs:element name="isTypeNonTurbojets" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Aircraft Type Non-Turbojets only</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="RnavPbnNavSpec"><xs:annotation><xs:documentation>This field provides information on the ICAO PBN Navigation Specification applicable to this procedure</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Rnav5"/><xs:enumeration value="Rnav2"/><xs:enumeration value="Rnav1"/><xs:enumeration value="BRnav"/><xs:enumeration value="PRnav"/><xs:enumeration value="PbnUnspecified"/></xs:restriction></xs:simpleType>
<xs:simpleType name="RnpPbnNavSpec"><xs:annotation><xs:documentation>This field provides information on the ICAO PBN Navigation Specification appliable to this procedure</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Rnp2"/><xs:enumeration value="Rnp1"/><xs:enumeration value="RnpAr"/><xs:enumeration value="AdvRnp"/><xs:enumeration value="Rnp0_3"/><xs:enumeration value="PbnUnspecified"/></xs:restriction></xs:simpleType>
<xs:complexType name="SIDRunwayTransition"><xs:annotation><xs:documentation>This element represents a SID runway transition.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="RunwayTransition"><xs:sequence><xs:element minOccurs="0" name="isFromRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the SID Runway Transition was from a runway.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="RunwayTransition" abstract="true"><xs:annotation><xs:documentation>This atstract element represents of shared information between SID and STAR Runway Transitions.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="ProcedureRoute"><xs:sequence><xs:element name="vectoring" type="type:Vectoring" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides vectoring information on the route</xs:documentation></xs:annotation></xs:element><xs:element name="routeQualifications" type="type:routeQualifications" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides information on qualifications or details on the parent route element</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="ProcedureRoute" abstract="true"><xs:annotation><xs:documentation>This class represents a Transition. This is the base class for other Transitions for inheriting the attributes of this class.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Route"><xs:sequence><xs:element name="transitionAltitudeOrLevel" type="type:Altitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element><xs:element name="msaRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When the terminal procedure has a simgle MSA defined, on the common or final approach route, this field will contain a reference to the MSA for the entire procedure. If the government source MSA is "by transition," the reference is populated on each transition.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureLeg" type="ProcedureLeg" minOccurs="1" maxOccurs="unbounded"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="ProcedureLeg" abstract="true"><xs:annotation><xs:documentation>This class is an abstraction of Procedure Leg. all the details pertaining to a Procedure leg are captured here.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Leg"><xs:sequence><xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element><xs:element name="arcRadius" type="type:ARCRadius" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.</xs:documentation></xs:annotation></xs:element><xs:element name="atcIndicator" type="enum:ATCIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ATC Indicator” field will be used to indicate that the altitudes shown in the altitude fields can be modified by ATC or the altitude will be assigned by ATC.</xs:documentation></xs:annotation></xs:element><xs:element name="distance" type="type:LegDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>In SID, STAR and Approach Procedure records, this field may contain segment distances, along track distances, excursion distances, or DME distances. The actual content is dependent on the Path and Termination. For more information on the content, refer to Table Three, Leg Data Fields, in Attachment 5 of the 424 specification.</xs:documentation></xs:annotation></xs:element><xs:element name="holdTime" type="xs:duration" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>In SID, STAR and Approach Procedure records, the field may contain segment distances/along track distances/excursion distances/DME distances or holding pattern timing.</xs:documentation></xs:annotation></xs:element><xs:element name="waypointDescriptor" type="type:ProcedureWaypointDescription" minOccurs="1" maxOccurs="1"/><xs:element name="legDistance" type="type:LegDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Terminal Procedure Flight Planning Leg distance is the along track distance required to complete any given leg. It is used to determine a cumulative track distance for a given terminal procedure for flight planning purposes, from the beginning of the take-off or arrival point to the termination point of the procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="legInboundIndicator" type="type:LegInboundIndicator" minOccurs="0" maxOccurs="1"/><xs:element name="legInboundOutboundIndicator" type="enum:LegInboundOutboundIndicator" minOccurs="0" maxOccurs="1"/><xs:element name="pathAndTermination" type="enum:PathAndTermination" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Path and Termination defines the path geometry for a single record of an ATC terminal procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureDesignMagVar" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Procedure Design Mag Var Indicator” field is an indication of how procedure design magnetic variation was provided in official source data for the procedure defined in the record/record set.</xs:documentation></xs:annotation></xs:element><xs:element name="rho" type="type:Rho" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“RHO” is defined as the geodesic distance in nautical miles to the waypoint identified in the record’s “Fix Ident” field from the NAVAID in the “Recommended NAVAID” field.</xs:documentation></xs:annotation></xs:element><xs:element name="rnp" type="type:RequiredNavigationPerformance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.</xs:documentation></xs:annotation></xs:element><xs:element name="speedLimit" type="type:SpeedLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Speed Limit” field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.</xs:documentation></xs:annotation></xs:element><xs:element name="speedLimitDescription" type="enum:SpeedLimitDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed. For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit The STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit. For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit. The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit. For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.</xs:documentation></xs:annotation></xs:element><xs:element name="theta" type="type:Theta" minOccurs="0" maxOccurs="1"/><xs:element name="transitionsAltitudeLevel" type="type:TransitionAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Transition Altitude” field defines the altitude in the vicinity of an airport or heliport at or below which the vertical position of an aircraft is controlled by reference to altitudes (MSL). The “Transition Level” field defines the lowest flight level available for use above the transition altitude. Aircraft descending through the transition layer will use altimeters set to local station pressure, while departing aircraft climbing through the layer will be using standard altimeter setting (QNE) of 29.92 inches of mercury, 1013.2 millibars or 1013.2 hectopascals.</xs:documentation></xs:annotation></xs:element><xs:element name="turnDirection" type="enum:TurnDirection" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Turn Direction” field specifies the direction in which Terminal Procedure turns are to be made. It is also used to indication direction on course reversals, see Attachment 5 Path and Termination</xs:documentation></xs:annotation></xs:element><xs:element name="turnDirectionValid" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is used in conjunction with Turn direction to indicate that a turn is required prior to capturing the path defined in a terminal procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="verticalScaleFactor" type="type:VerticalScaleFactor" minOccurs="0" maxOccurs="1"/><xs:element name="alt1" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="alt2" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="course" type="type:Course" minOccurs="0" maxOccurs="1"/><xs:element name="centerFix" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"/><xs:element name="centerFixRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Leg" abstract="true"><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Route Type Records - A route of flight is defined by a series of legs taken in order. The “Sequence Number” field defines the position of the leg in the sequence defining the route of flight identified in the route identifier field.</xs:documentation></xs:annotation></xs:element><xs:element name="fixRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/><xs:element name="fixIdent" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"/><xs:element name="recNavaidIdent" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"/><xs:element name="recNavaidRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
For Route Type Records - A route of flight is defined by a series of records taken in order. The “Sequence Number” field defines the location of the record in the sequence defining the route of flight identified in the route identifier field. For Boundary Type Records - A boundary is defined by a series of records taken in order. The “Sequence Number” field defines the location of the record in the sequence defining a boundary. For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence. For Airport and Heliport TAA Records – Sequence Number 1 will always be assigned to the record based on the Center Fix upon which the Straight-In Area is predicated, Sequence Number 2 will always be assigned to the record based on the Center Fix upon which the Left Base Area is predicated, and Sequence Number 3 will always be assigned to the record based on the Center Fix upon which the Right Base Area is predicated. Therefore, if a TAA Record has a Straight-In Area and a Right Base Area, but no Left Base Area, only Sequence Numbers 1 and 3 will be used. If a TAA Record has a Straight-In Area and a Left Base Area but no Right Base Area, only Sequence Numbers 1 and 2 will be used.
<xs:simpleType name="SequenceNumber"><xs:annotation><xs:documentation>For Route Type Records - A route of flight is defined by a series of records taken in order. The “Sequence Number” field defines the location of the record in the sequence defining the route of flight identified in the route identifier field. For Boundary Type Records - A boundary is defined by a series of records taken in order. The “Sequence Number” field defines the location of the record in the sequence defining a boundary. For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence. For Airport and Heliport TAA Records – Sequence Number 1 will always be assigned to the record based on the Center Fix upon which the Straight-In Area is predicated, Sequence Number 2 will always be assigned to the record based on the Center Fix upon which the Left Base Area is predicated, and Sequence Number 3 will always be assigned to the record based on the Center Fix upon which the Right Base Area is predicated. Therefore, if a TAA Record has a Straight-In Area and a Right Base Area, but no Left Base Area, only Sequence Numbers 1 and 3 will be used. If a TAA Record has a Straight-In Area and a Left Base Area but no Right Base Area, only Sequence Numbers 1 and 2 will be used.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="4"/></xs:restriction></xs:simpleType>
The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.
Diagram
Type
restriction of xs:string
Facets
enumeration
AtOrAboveFirst
At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
AtOrBelow
At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.
enumeration
At
At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.
enumeration
B
At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope
enumeration
C
"At or above" altitude specified in second "Altitude" field.
enumeration
G
Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.
enumeration
I
Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope
<xs:simpleType name="AltitudeDescription"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AtOrAboveFirst"><xs:annotation><xs:documentation>At or above altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AtOrBelow"><xs:annotation><xs:documentation>At or below altitude specified in first Altitude field. Also used with Localizer Only Altitude field and the FACF Waypoint on Precision Approach Procedures with Electronic Glide Slope.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="At"><xs:annotation><xs:documentation>At altitude specified in first Altitude field. Also used with Localizer Only Altitude field, and the FACF Waypoint on Precision Approach Coding with Electronic Glide Slope.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="B"><xs:annotation><xs:documentation>At or above to at or below altitudes specified in the first and second Altitude fields. Not used on FAF or MAP Waypoint Records in Precision Approach Coding with Electronic Glide Slope</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="C"><xs:annotation><xs:documentation>"At or above" altitude specified in second "Altitude" field.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="G"><xs:annotation><xs:documentation>Glide Slope Altitude (MSL) At Fix, specified in the first Altitude field on the FAF Waypoint and Glide Slope Intercept Altitude (MSL) in second altitude of FAF Waypoint in Precision Approach Coding with electronic Glide Slope.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="I"><xs:annotation><xs:documentation>Glide Slope Intercept Altitude specified in second "Altitude" field and "at" altitude specified in first "Altitude" field on the FACF Waypoint in Precision Approach Coding with electronic Glide Slope</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.
<xs:simpleType name="ARCRadius"><xs:annotation><xs:documentation>The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceNMThousanths"/></xs:simpleType>
The ATC Indicator field will be used to indicate that the altitudes shown in the altitude fields can be modified by ATC or the altitude will be assigned by ATC.
Diagram
Type
restriction of xs:string
Facets
enumeration
ModifiedOrAssigned
Altitude can be modified or assigned by ATC.
enumeration
AssignedIfNotProvided
official government source states that the altitude will be assigned by ATC or if no altitude is supplied
<xs:simpleType name="ATCIndicator"><xs:annotation><xs:documentation>The ATC Indicator field will be used to indicate that the altitudes shown in the altitude fields can be modified by ATC or the altitude will be assigned by ATC.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="ModifiedOrAssigned"><xs:annotation><xs:documentation>Altitude can be modified or assigned by ATC.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AssignedIfNotProvided"><xs:annotation><xs:documentation>official government source states that the altitude will be assigned by ATC or if no altitude is supplied</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="LegDistance"><xs:annotation><xs:documentation>Leg distance element used on procedure and airway legs, and terminal procedure flight planning records.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceNM"/></xs:simpleType>
<xs:complexType name="ProcedureWaypointDescription"><xs:annotation><xs:documentation>This class represents the waypoint description information used by procedure legs.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isEssential" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFlyOver" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isHolding" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isNoProcedureTurn" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isPhantomFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A database waypoint established during procedure coding to facilitate more accurate navigation by the Flight Management Computer than would be allowed using air-mass related Path Terminators to replicate source data. The waypoint finds use when such considerations as increased environmental restrictions and the congestion of the available airspace come into play. Used to permit route construction with track to a fix (TF) legs.</xs:documentation></xs:annotation></xs:element><xs:element name="isSourceProvidedEnrouteWaypoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isTaaProcedureTurn" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “TAA Procedure Turn” field is used to indicate whether or a course reversal is necessary when flying within a particular TAA Area.</xs:documentation></xs:annotation></xs:element><xs:element name="isAtcCompulsoryReportingPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Compulsory Reporting Point: Essential or nonessential waypoints may be classified as ATC compulsory points. ATC requires the pilot to make a communications report at these waypoints. All other waypoints may be classified as non compulsory reporting points and are reported only when specifically requested by ATC</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
The Leg Inbound/Outbound Indicator is used to identify the Leg Length or Leg Time field values (5.64 or 5.65) as being applicable to either the inbound or the outbound leg of a holding pattern or race track course reversal.
<xs:simpleType name="LegInboundOutboundIndicator"><xs:annotation><xs:documentation>The Leg Inbound/Outbound Indicator is used to identify the Leg Length or Leg Time field values (5.64 or 5.65) as being applicable to either the inbound or the outbound leg of a holding pattern or race track course reversal.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Inbound"><xs:annotation><xs:documentation>Inbound</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Outbound"><xs:annotation><xs:documentation>Inbound</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="PathAndTermination"><xs:annotation><xs:documentation>The Path and Termination defines the path geometry for a single record of an ATC terminal procedure.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AF"><xs:annotation><xs:documentation>Arc to a Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CA"><xs:annotation><xs:documentation>Course to an Altitude</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CD"><xs:annotation><xs:documentation>Course to a DME Distance</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CF"><xs:annotation><xs:documentation>Course to a Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CI"><xs:annotation><xs:documentation>Course to an Intercept</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CR"><xs:annotation><xs:documentation>Course to a Radial Termination</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FA"><xs:annotation><xs:documentation>Fix to an Altitude</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DF"><xs:annotation><xs:documentation>Distance to a Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FC"><xs:annotation><xs:documentation>Track from a Fix for a Distance</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FD"><xs:annotation><xs:documentation>Track from a Fix to a DME Distance</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FM"><xs:annotation><xs:documentation>From a Fix to a Manual Termination</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HA"><xs:annotation><xs:documentation>Holding with Altitude Termination</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HF"><xs:annotation><xs:documentation>Holding with single circuit terminating at the fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HM"><xs:annotation><xs:documentation>Holding with Manual Termination</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="IF"><xs:annotation><xs:documentation>Initial Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PI"><xs:annotation><xs:documentation>045/180 Procedure Turn</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RF"><xs:annotation><xs:documentation>Constant Radius Arc</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TF"><xs:annotation><xs:documentation>Track to a Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VA"><xs:annotation><xs:documentation>Heading to an Altitude Termination</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VD"><xs:annotation><xs:documentation>Heading to a DME Distance Termination</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VI"><xs:annotation><xs:documentation>Heading to an Intercept</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VM"><xs:annotation><xs:documentation>Heading to a Manual Termination</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VR"><xs:annotation><xs:documentation>Heading to a Radial Termination</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
“RHO” is defined as the geodesic distance in nautical miles to the waypoint identified in the record’s “Fix Ident” field from the NAVAID in the “Recommended NAVAID” field.
<xs:simpleType name="Rho"><xs:annotation><xs:documentation>“RHO” is defined as the geodesic distance in nautical miles to the waypoint identified in the record’s “Fix Ident” field from the NAVAID in the “Recommended NAVAID” field.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceNM"/></xs:simpleType>
Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules. e.g., .15, 4, 1, .3
<xs:simpleType name="RequiredNavigationPerformance"><xs:annotation><xs:documentation>Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules. e.g., .15, 4, 1, .3</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"><xs:fractionDigits value="9"/></xs:restriction></xs:simpleType>
The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed.For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limitThe STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit.For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit.The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit.For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.
Diagram
Type
restriction of xs:string
Facets
enumeration
Manditory
Mandatory Speed, Cross Fix AT speed specified in Speed Limit
enumeration
Minimum
Minimum Speed, Cross Fix AT or ABOVE speed specified in Speed Limit
enumeration
Maximum
Maximum Speed, Cross Fix AT or BELOW speed specified in Speed Limit
<xs:simpleType name="SpeedLimitDescription"><xs:annotation><xs:documentation>The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed. For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit The STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit. For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit. The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit. For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Manditory"><xs:annotation><xs:documentation>Mandatory Speed, Cross Fix AT speed specified in Speed Limit</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Minimum"><xs:annotation><xs:documentation>Minimum Speed, Cross Fix AT or ABOVE speed specified in Speed Limit</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Maximum"><xs:annotation><xs:documentation>Maximum Speed, Cross Fix AT or BELOW speed specified in Speed Limit</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
“Theta” is defined as the magnetic bearing to the waypoint identified in the record’s “FIX Ident” field from the Navaid in the “Recommended Navaid” field.
<xs:simpleType name="Theta"><xs:annotation><xs:documentation>“Theta” is defined as the magnetic bearing to the waypoint identified in the record’s “FIX Ident” field from the Navaid in the “Recommended Navaid” field.</xs:documentation></xs:annotation><xs:restriction base="type:BearingValue"/></xs:simpleType>
The “Turn Direction” field specifies the direction in which Terminal Procedure turns are to be made. It is also used to indication direction on course reversals, see Attachment 5 Path and Termination
<xs:simpleType name="TurnDirection"><xs:annotation><xs:documentation>The “Turn Direction” field specifies the direction in which Terminal Procedure turns are to be made. It is also used to indication direction on course reversals, see Attachment 5 Path and Termination</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Left"><xs:annotation><xs:documentation>Left</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Right"><xs:annotation><xs:documentation>Right</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Either"><xs:annotation><xs:documentation>Either Left or Right</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="VerticalScaleFactor"><xs:annotation><xs:documentation>Vertical Scale Factor (VSF) is used to set the vertical deviation scale.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
“Outbound Magnetic Course” is the published outbound magnetic course from the waypoint identified in the record’s “Fix Ident” field. In addition, this field is used for Course/Heading/Radials on SID/STAR Approach Records through requirements of the Path Terminator and coding rules contained in Attachment 5 of this specification.
<xs:complexType name="Course"><xs:annotation><xs:documentation>“Outbound Magnetic Course” is the published outbound magnetic course from the waypoint identified in the record’s “Fix Ident” field. In addition, this field is used for Course/Heading/Radials on SID/STAR Approach Records through requirements of the Path Terminator and coding rules contained in Attachment 5 of this specification.</xs:documentation></xs:annotation><xs:sequence><xs:element name="courseValue" type="type:CourseValue" minOccurs="1" maxOccurs="1"/><xs:element name="isTrue" type="xs:boolean" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
“Outbound Magnetic Course” is the published outbound magnetic course from the waypoint identified in the record’s “Fix Ident” field. In addition, this field is used for Course/Heading/Radials on SID/STAR Approach Records through requirements of the Path Terminator and coding rules contained in Attachment 5 of this specification.
<xs:simpleType name="CourseValue"><xs:annotation><xs:documentation>“Outbound Magnetic Course” is the published outbound magnetic course from the waypoint identified in the record’s “Fix Ident” field. In addition, this field is used for Course/Heading/Radials on SID/STAR Approach Records through requirements of the Path Terminator and coding rules contained in Attachment 5 of this specification.</xs:documentation></xs:annotation><xs:restriction base="type:CompassValue"><xs:totalDigits value="4"/><xs:fractionDigits value="1"/></xs:restriction></xs:simpleType>
This element provides boolean expressions describing qualifications of the route. The qualifications in this element are common to different types of routes
<xs:complexType name="routeQualifications"><xs:annotation><xs:documentation>This element provides boolean expressions describing qualifications of the route. The qualifications in this element are common to different types of routes</xs:documentation></xs:annotation><xs:sequence><xs:element minOccurs="0" name="isDmeReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true, Dme is required for the parent procedure.</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="isGnssReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true, a GNSS is required for the parent procedure</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="isRadarReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true RADAR is required for the parent procedure</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="isFmsReq" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true a flight management system is required for the parent procedure</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="isConventional" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true the route is a conventional route</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="SIDCommonRoute"><xs:annotation><xs:documentation>This element represents a SID common route.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="CommonRoute"><xs:sequence><xs:element minOccurs="0" name="IsFromRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the SID Common Route was from a runway.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="CommonRoute" abstract="true"><xs:annotation><xs:documentation>This atstract element represents of shared information between SID and STAR common routes.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="ProcedureRoute"><xs:sequence><xs:element name="routeQualifications" type="type:routeQualifications" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides information on qualifications or details on the parent route element</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="SIDEnrouteTransition"><xs:annotation><xs:documentation>This element represents a SID Enroute Transition.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="EnrouteTransition"><xs:sequence/></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="EnrouteTransition" abstract="true"><xs:annotation><xs:documentation>This atstract element represents of shared information between SID and STAR Enroute Transitions.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="ProcedureRoute"><xs:sequence><xs:element name="vectoring" type="type:Vectoring" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides vectoring invormaiton on the route</xs:documentation></xs:annotation></xs:element><xs:element name="routeQualifications" type="type:routeQualifications" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides information on qualifications or details on the parent route element</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="STAR"><xs:annotation><xs:documentation>This class is an abstraction of STAR. STAR records are represented by this class.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="SIDSTAR"><xs:sequence><xs:element name="starRunwayTransition" type="STARRunwayTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the runway transitions.</xs:documentation></xs:annotation></xs:element><xs:element name="starEnrouteTransition" type="STAREnrouteTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the enroute transitions</xs:documentation></xs:annotation></xs:element><xs:element name="starCommonRoute" type="STARCommonRoute" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the common route</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="isContiniousDecent" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the parent is a continious decent STAR.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="STARRunwayTransition"><xs:annotation><xs:documentation>This element represents a STAR Runway Transition.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="RunwayTransition"><xs:sequence><xs:element minOccurs="0" name="isToRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the STAR Common Route was to a runway.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="STAREnrouteTransition"><xs:annotation><xs:documentation>This element represents a STAR enroute transition.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="EnrouteTransition"><xs:sequence/></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="STARCommonRoute"><xs:annotation><xs:documentation>The element represents a STAR Common Route.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="CommonRoute"><xs:sequence><xs:element minOccurs="0" name="isToRunway" type="xs:boolean"><xs:annotation><xs:documentation>If this element exists and is true then the STAR Common Route was to a runway.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Approach"><xs:annotation><xs:documentation>This class is an abstraction of Approach. Approach records are represented by this class.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Procedure"><xs:sequence><xs:element name="approachRouteType" type="enum:ApproachRouteType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This element identifies what type of approach the parent is.</xs:documentation></xs:annotation></xs:element><xs:element name="gnssFMSIndicator" type="enum:GNSSFMSIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “GNSS/FMS Indicator” field provides an indication of whether or not the responsible government agency has authorized the overlay of a conventional, ground based approach procedure with the use of a sensor capable of processing GNSS data or if the procedure may be flown with FMS as the primary navigation equipment. The field is also used to indicate when and RNAV procedure has been authorized for GNSS-based vertical navigation.</xs:documentation></xs:annotation></xs:element><xs:element name="gbasPathPoint" type="GBASPathPoint" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the GBAS path point record for the approach.</xs:documentation></xs:annotation></xs:element><xs:element name="sbasPathPoint" type="SBASPathPoint" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the SBAS path point for the approach</xs:documentation></xs:annotation></xs:element><xs:element name="approachTransition" type="ApproachTransition" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elements are the approach transitions for the approach.</xs:documentation></xs:annotation></xs:element><xs:element name="finalApproach" type="FinalApproach" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This is the final approach route, which ends at the last part of the final before the missed approach. e.g., The last point of the final approach is often the missed approach point.</xs:documentation></xs:annotation></xs:element><xs:element name="missedApproach" type="MissedApproach" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>These elments are the missed approach routes for a procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="approachPointRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides a reference to the point served by this approach procedure. On an approach this would reference a runway or fix.</xs:documentation></xs:annotation></xs:element><!-- The remainder of these fields are related to route qualifiers --><xs:element name="isRnavVisual" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true the parent is an Rnav Visual.</xs:documentation></xs:annotation></xs:element><xs:element name="isPinsProceedVisually" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates if the procedure is Point In Space with a instructions to procede visually.</xs:documentation></xs:annotation></xs:element><xs:element name="isPinsProceedVfr" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates if hte procedure is Point In Space with instructions to procedure under visual flight rules.</xs:documentation></xs:annotation></xs:element><xs:element name="isLocalizerBackcourse" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If this element exists and is true th eparent is a localizer backcourse.</xs:documentation></xs:annotation></xs:element><xs:element name="approachPbnNavSpec" type="enum:ApproachPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides informaiton on the ICAO PBN navigation specification applicable to the approach.</xs:documentation></xs:annotation></xs:element><xs:element name="isPreferredProcedure" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Preferred Multiple Approach Indicator is used to identify the multiple approach that is generally considered to be the most likely one to be utilized/needed when there are only multiple approaches available for a given approach type at a runway. This will be defined on the Approach FAF record in the Final Approach. For a given approach type at a runway, there shall be one and only one Primary Multiple Approach Indicator provided</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="ApproachRouteType"><xs:annotation><xs:documentation>The "Route Type" field defines the type of Airport Approach (PF) and Heliport Approach (HF) Records</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="LocBackcourse"><xs:annotation><xs:documentation>Localizer/Backcourse Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VorDme"><xs:annotation><xs:documentation>VORDME Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Fms"><xs:annotation><xs:documentation>Flight Management System (FMS) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Igs"><xs:annotation><xs:documentation>Instrument Guidance System (IGS) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Rnp"><xs:annotation><xs:documentation>Area Navigation (RNAV) Approach with Required Navigation Performance (RNP) Approach</xs:documentation><xs:documentation>Route types of Rnp or Rnav indicate a procedure titled RNAV, e.g., RNAV (GPS) or RNAV (RNP). Route Type H indicates a procedure titled RNP. COMMENTARY: The Route Types H and R are coded to differentiate between the approach procedure titles published in state source. The words in brackets will not be considered for the coding of the Route Type. While according to the PBN manual there is no RNAV approach specification, many approaches are still published using an RNAV title. Additionally, there are still non PBN RNAV approaches published, e.g., VOR/DME RNAV. The following old titles will be coded with a Route Type R: RNAV (GPS) RWY 09 RNAV (GNSS) RWY 09 RNAV (RNP) RWY 09 The following new titles will be coded with Route Type H: RNP RWY 09 RNP RWY 09 (AR) The following new titles will be coded with Route Type R: RNAV RWY 09 RNAV RWY 09 (AR</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Ils"><xs:annotation><xs:documentation>Instrument Landing System (ILS) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Gls"><xs:annotation><xs:documentation>GNSS Landing System (GLS)Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LocOnly"><xs:annotation><xs:documentation>Localizer Only (LOC) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Mls"><xs:annotation><xs:documentation>Microwave Landing System (MLS) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Ndb"><xs:annotation><xs:documentation>Non-Directional Beacon (NDB) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Gps"><xs:annotation><xs:documentation>Global Positioning System (GPS) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NdbDme"><xs:annotation><xs:documentation>Non-Directional Beacon + DME(NDB+DME) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Rnav"><xs:annotation><xs:documentation>Area Navigation (RNAV) Approach</xs:documentation><xs:documentation>Route Type R indicates a procedure titled RNAV, e.g., RNAV (GPS) or RNAV (RNP). Route Type H indicates a procedure titled RNP. COMMENTARY: The Route Types H and R are coded to differentiate between the approach procedure titles published in state source. The words in brackets will not be considered for the coding of the Route Type. While according to the PBN manual there is no RNAV approach specification, many approaches are still published using an RNAV title. Additionally, there are still non PBN RNAV approaches published, e.g., VOR/DME RNAV. The following old titles will be coded with a Route Type R: RNAV (GPS) RWY 09 RNAV (GNSS) RWY 09 RNAV (RNP) RWY 09 The following new titles will be coded with Route Type H: RNP RWY 09 RNP RWY 09 (AR) The following new titles will be coded with Route Type R: RNAV RWY 09 RNAV RWY 09 (AR</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VorUsingVordmeOrVortac"><xs:annotation><xs:documentation>VOR Approach using VORDME/VORTAC</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Tacan"><xs:annotation><xs:documentation>TACAN Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Sdf"><xs:annotation><xs:documentation>Simplified Directional Facility (SDF) Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Vor"><xs:annotation><xs:documentation>VOR Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Lda"><xs:annotation><xs:documentation>Localizer Directional Aid (LDA) Approach</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The GNSS/FMS Indicator field provides an indication of whether or not the responsible government agency has authorized the overlay of a conventional, ground based approach procedure with the use of a sensor capable of processing GNSS data or if the procedure may be flown with FMS as the primary navigation equipment. The field is also used to indicate when and RNAV procedure has been authorized for GNSS-based vertical navigation.
Diagram
Type
restriction of xs:string
Facets
enumeration
GnssFmsOverlayAuthNotPublished
Procedure Not Authorized for GNSS or FMS Overlay ? Authorization not published.
enumeration
GnssOverlayAuthNavaidOperatingAndMonitored
Procedure Authorized for GNSS Overlay, primary Navaids operating and monitored. Authorization not published.
enumeration
GnssOverlayAuthNoMonitorNavaidAuth
Procedure Authorized for GNSS Overlay, primary Navaids installed, not monitored Authorization is published. Example: Procedure Title includes (GPS) or (GNSS)
enumeration
GnssOverlayTitleIncludesGpsOrGnss
Procedure Authorized for GNSS Overlay, Procedure Title includes GPS or GNSS
enumeration
FmsOverlayAuthorized
Procedure Authorized for FMS Overlay
enumeration
SbasVerticalAuthorized
RNAV (GPS), RNAV (RNP) or RNAV (GNSS) Procedure SBAS use authorized; SBAS-based vertical navigation authorized
enumeration
SbasVerticalNotAuthorized
RNAV (GPS), RNAV (RNP), RNAV (GNSS) or RNAV Visual Procedure, SBAS-based vertical navigation NOT Authorized
enumeration
SbasVerticalNotPublished
RNAV (GPS) RNAV (RNP), or RNAV (GNSS) Procedure, SBAS-based vertical navigation use not published
enumeration
StandAloneGNSS
Stand Alone GNSS Procedure
enumeration
SbasVerticalNA
RNAV (GPS) RNAV (RNP), or RNAV (GNSS) Procedure within the SBAS operational footprint, but SBAS-based vertical navigation NOT Authorized
enumeration
OverlayAuthNotPublished
Procedure Overlay Authorization not published
enumeration
PbnRnpGps
PBN RNP Approach provide as GPS. The GNSS/FMS IND of G indicates that the GPS approach is an PBN RNAV approach provided with route type P.
enumeration
LocOnlyIls
Localizer only coding portion of ILS. The GNSS/FMS IND of L indicates that the LOC approach is the Localizer only portion of an ILS approach which contains glideslope out information.
<xs:simpleType name="GNSSFMSIndicator"><xs:annotation><xs:documentation>The GNSS/FMS Indicator field provides an indication of whether or not the responsible government agency has authorized the overlay of a conventional, ground based approach procedure with the use of a sensor capable of processing GNSS data or if the procedure may be flown with FMS as the primary navigation equipment. The field is also used to indicate when and RNAV procedure has been authorized for GNSS-based vertical navigation.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="GnssFmsOverlayAuthNotPublished"><xs:annotation><xs:documentation>Procedure Not Authorized for GNSS or FMS Overlay ? Authorization not published.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GnssOverlayAuthNavaidOperatingAndMonitored"><xs:annotation><xs:documentation>Procedure Authorized for GNSS Overlay, primary Navaids operating and monitored. Authorization not published.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GnssOverlayAuthNoMonitorNavaidAuth"><xs:annotation><xs:documentation>Procedure Authorized for GNSS Overlay, primary Navaids installed, not monitored Authorization is published. Example: Procedure Title includes (GPS) or (GNSS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GnssOverlayTitleIncludesGpsOrGnss"><xs:annotation><xs:documentation>Procedure Authorized for GNSS Overlay, Procedure Title includes GPS or GNSS</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FmsOverlayAuthorized"><xs:annotation><xs:documentation>Procedure Authorized for FMS Overlay</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SbasVerticalAuthorized"><xs:annotation><xs:documentation>RNAV (GPS), RNAV (RNP) or RNAV (GNSS) Procedure SBAS use authorized; SBAS-based vertical navigation authorized</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SbasVerticalNotAuthorized"><xs:annotation><xs:documentation>RNAV (GPS), RNAV (RNP), RNAV (GNSS) or RNAV Visual Procedure, SBAS-based vertical navigation NOT Authorized</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SbasVerticalNotPublished"><xs:annotation><xs:documentation>RNAV (GPS) RNAV (RNP), or RNAV (GNSS) Procedure, SBAS-based vertical navigation use not published</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="StandAloneGNSS"><xs:annotation><xs:documentation>Stand Alone GNSS Procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SbasVerticalNA"><xs:annotation><xs:documentation>RNAV (GPS) RNAV (RNP), or RNAV (GNSS) Procedure within the SBAS operational footprint, but SBAS-based vertical navigation NOT Authorized</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OverlayAuthNotPublished"><xs:annotation><xs:documentation>Procedure Overlay Authorization not published</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PbnRnpGps"><xs:annotation><xs:documentation>PBN RNP Approach provide as GPS. The GNSS/FMS IND of G indicates that the GPS approach is an PBN RNAV approach provided with route type P.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LocOnlyIls"><xs:annotation><xs:documentation>Localizer only coding portion of ILS. The GNSS/FMS IND of L indicates that the LOC approach is the Localizer only portion of an ILS approach which contains glideslope out information.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="GBASPathPoint"><xs:complexContent><xs:extension base="PathPoint"><xs:sequence><xs:element name="operationType" type="enum:GBASOperationType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Operation Type” field indicates whether the operation is an approach procedure, an advanced operation or other operational to be defined later.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="PathPoint"><xs:annotation><xs:documentation>Path Point Primary Record Description</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="approachPerformanceDesignator" type="enum:ApproachPerformanceDesignator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Approach Performance Designator” field is used to indicate the type or category of approach.</xs:documentation></xs:annotation></xs:element><xs:element name="approachRouteIdentifier" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Approach Route Identifier” field contains the identifier of the approach route to be flown. To facilitate the provision of multiple approach procedures of the same type to a given runway, the field also is used to provide a “multiple indicator.”</xs:documentation></xs:annotation></xs:element><xs:element name="approachTypeIdentifier" type="type:ApproachTypeIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Identifies the approach types published on a given approach procedure which require Airport or Helicopter Operations SBAS path points.</xs:documentation></xs:annotation></xs:element><xs:element name="courseWidthAtThreshold" type="type:CourseWidthAtThreshold" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Course Width At Threshold” field defines the width of the lateral course at the Landing Threshold Point (LTP) or Fictitious Helipoint (or helipoint). This width, in conjunction with the location of the Flight Path Alignment Point (FPAP) defines the sensitivity of the lateral deviations throughout the approach.</xs:documentation></xs:annotation></xs:element><xs:element name="FASDataCRCRemainder" type="type:FinalApproachSegmentDataCRCRemainder" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Final Approach Segment Data CRC Remainder” field is an eight (8) character hexadecimal representation of the 32-bit CRC value provided by the source for the information contained in the aeronautical data fields being monitored for integrity. The value is calculated by a specific mathematical algorithm, which is both machine and man processible.</xs:documentation></xs:annotation></xs:element><xs:element name="flightPathAlignmentPoint" type="type:HighPrecisionLocation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element><xs:element name="fpapEllipsoidHeight" type="type:EllipsoidHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Ellipsoidal Height” field is the height of a surveyed point in reference to the WGS-84 ellipsoid.</xs:documentation></xs:annotation></xs:element><xs:element name="fpapOrthometricHeight" type="type:OrthometricHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Orthometric Height” field is the height of a surveyed point in reference to Mean Sea Level (MSL).</xs:documentation></xs:annotation></xs:element><xs:element name="glidePathAngle" type="type:GlidePathAngle" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Glide Path Angle” field is an angle, expressed in degrees, tenths and hundredths of degrees, measured at the Flight Path Control Point (FPCP) of those approach procedures that require the coding of a Airport or Helicopter Operations SBAS Path Point record or GBAS Path Point Record. It establishes the intended descent gradient for the final approach flight path. For an illustration of the GPA and related points.</xs:documentation></xs:annotation></xs:element><xs:element name="gnssChannelNumber" type="type:Channel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “GNSS Channel Number” field identifies the channel that will be decoded to identify the augmentation system used. The Channel Number is derived from official government sources and is entered as five numeric characters. It consists of numeric characters in the ranges 0000 to 9999 and 20001 to 99999. In general, numbers less than 20000 are reserved for ILS and MLS. In some countries, Channel Numbers from 0000 to 9999 are reserved for SCAT-1 and will be entered as 00000 through 09999. Channel Numbers from 20001 to 39999 are reserved for GBAS (and SBAS if applicable). Channel Numbers from 40000 to 99999 are reserved for SBAS.</xs:documentation></xs:annotation></xs:element><xs:element name="helicopterProcedureCourse" type="type:CourseValue" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Helicopter Procedure Course field is used on Path Point Continuation Records to define the final approach course of procedures designed for helicopter operations to runways, to helipads, and to points in space..</xs:documentation></xs:annotation></xs:element><xs:element name="landingThresholdPoint" type="type:HighPrecisionLocation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element><xs:element name="lengthOffset" type="type:LengthOffset" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Length Offset” field is the distance from the stop end of the runway (SER) to the FPAP. This distance defines the location where lateral sensitivity changes to the missed approach sensitivity. If the FPAP is located at the designated center of the opposite runway end, the distance is zero. Additionally, if the lenfth offset is not provided then the element should not exist.</xs:documentation></xs:annotation></xs:element><xs:element name="ltpEllipsoidHeight" type="type:EllipsoidHeight" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Ellipsoidal Height” field is the height of a surveyed point in reference to the WGS-84 ellipsoid.</xs:documentation></xs:annotation></xs:element><xs:element name="ltpOrthometricHeight" type="type:OrthometricHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Orthometric Height” field is the height of a surveyed point in reference to Mean Sea Level (MSL).</xs:documentation></xs:annotation></xs:element><xs:element name="pathPointTCH" type="type:PathPointTCH" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>On procedures to runways or helipads, the Path Point TCH is the height above the runway threshold (LTP) or the helicopter alighting point. On procedures which are Point in Space, the height of the fictitious helipoint (or helipoint) above the height of the heliport. It is the same as the TCH defined in Section 5.67, but has greater resolution due to the required precision.</xs:documentation></xs:annotation></xs:element><xs:element name="referencePathDataSelector" type="type:ReferencePathDataSelector" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Reference Path Data Selector” field enables the automatic tuning of a procedure by Ground Based Augmentation Systems (GBAS) avionics.This data is not used for SBAS operations.</xs:documentation></xs:annotation></xs:element><xs:element name="referencePathIdentifier" type="type:ReferencePathIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Reference Path Identifier field represents the three or four alphanumeric characters used to uniquely designate the reference path. The Reference Path Identifier is synonymous with the approach ID located beneath the Channel Number on Instrument Approach Plates and is unique only for a given airport.</xs:documentation></xs:annotation></xs:element><xs:element name="routeIndicator" type="type:RouteIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Route Indicator” field is a single alpha character used to differentiate between multiple final approach segments to the same runway or helipad contained in the Final Approach Coding.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayOrPadIdentifier" type="type:RunwayOrPadIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This XML element is designed as an abstraction for Runway Identifier or Pad Identifier, this is done by using the XML attribute "choice", so that only one of the elements can be present in the XML file.</xs:documentation></xs:annotation></xs:element><xs:element name="tchUnitsIndicator" type="enum:TCHUnitsIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “TCH Units Indicator” field is used in Path Point Records to define the units, Feet or Meters for the Path Point TCH. This element is included in the “CRC Wrap” a possible metric source value cannot be converted to feet.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="ApproachPerformanceDesignator"><xs:annotation><xs:documentation>The “Approach Performance Designator” field is used to indicate the type or category of approach.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="0"><xs:annotation><xs:documentation>GAST A or GAST B</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1"><xs:annotation><xs:documentation>GAST C</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="2"><xs:annotation><xs:documentation>GAST C or GAST D</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="3"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="4"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="5"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="6"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="7"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ApproachTypeIdentifier"><xs:annotation><xs:documentation>Identifies the approach types published on a given approach procedure which require Airport or Helicopter Operations SBAS path points.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="10"/></xs:restriction></xs:simpleType>
The “Course Width At Threshold” field defines the width of the lateral course at the Landing Threshold Point (LTP) or Fictitious Helipoint (or helipoint). This width, in conjunction with the location of the Flight Path Alignment Point (FPAP) defines the sensitivity of the lateral deviations throughout the approach.
<xs:simpleType name="CourseWidthAtThreshold"><xs:annotation><xs:documentation>The “Course Width At Threshold” field defines the width of the lateral course at the Landing Threshold Point (LTP) or Fictitious Helipoint (or helipoint). This width, in conjunction with the location of the Flight Path Alignment Point (FPAP) defines the sensitivity of the lateral deviations throughout the approach.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"/></xs:simpleType>
Simple Type type:FinalApproachSegmentDataCRCRemainder
Namespace
http://www.arinc424.com/xml/datatypes
Annotations
The “Final Approach Segment Data CRC Remainder” field is an eight (8) character hexadecimal representation of the 32-bit CRC value provided by the source for the information contained in the aeronautical data fields being monitored for integrity. The value is calculated by a specific mathematical algorithm, which is both machine and man processible.
<xs:simpleType name="FinalApproachSegmentDataCRCRemainder"><xs:annotation><xs:documentation>The “Final Approach Segment Data CRC Remainder” field is an eight (8) character hexadecimal representation of the 32-bit CRC value provided by the source for the information contained in the aeronautical data fields being monitored for integrity. The value is calculated by a specific mathematical algorithm, which is both machine and man processible.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="8"/></xs:restriction></xs:simpleType>
<xs:complexType name="HighPrecisionLocation"><xs:annotation><xs:documentation>High Precision Location</xs:documentation></xs:annotation><xs:sequence><xs:element name="highPrecisionLatitude" type="type:HighPrecisionLatitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The High Precision Latitude field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.</xs:documentation></xs:annotation></xs:element><xs:element name="highPrecisionLongitude" type="type:HighPrecisionLongitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “High Precision Longitude” field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
The “High Precision Latitude” field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.
<xs:simpleType name="HighPrecisionLatitude"><xs:annotation><xs:documentation>The “High Precision Latitude” field contains the latitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.</xs:documentation></xs:annotation><xs:restriction base="xs:string"/></xs:simpleType>
The “High Precision Longitude” field contains the longitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.
<xs:simpleType name="HighPrecisionLongitude"><xs:annotation><xs:documentation>The “High Precision Longitude” field contains the longitude of the navigation feature identified in the record. When used on Airport Path Point Records, one navigation feature is the LTP/FTP, the other is the FPAP. When used on Helicopter Operations Path Point Records, one navigation feature is the Fictitious Helipoint (or Helipoint), the other is the FPAP.</xs:documentation></xs:annotation><xs:restriction base="xs:string"/></xs:simpleType>
<xs:simpleType name="EllipsoidHeight"><xs:annotation><xs:documentation>The “Ellipsoidal Height” field is the height of a surveyed point in reference to the WGS-84 ellipsoid.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"/></xs:simpleType>
<xs:simpleType name="OrthometricHeight"><xs:annotation><xs:documentation>The “Orthometric Height” field is the height of a surveyed point in reference to Mean Sea Level (MSL).</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"><xs:maxInclusive value="+9999"/><xs:minInclusive value="-9999"/></xs:restriction></xs:simpleType>
The “Glide Path Angle” field is an angle, expressed in degrees, tenths and hundredths of degrees, measured at the Flight Path Control Point (FPCP) of those approach procedures that require the coding of a Airport or Helicopter Operations SBAS Path Point record or GBAS Path Point Record. It establishes the intended descent gradient for the final approach flight path. For an illustration of the GPA and related points.
<xs:simpleType name="GlidePathAngle"><xs:annotation><xs:documentation>The “Glide Path Angle” field is an angle, expressed in degrees, tenths and hundredths of degrees, measured at the Flight Path Control Point (FPCP) of those approach procedures that require the coding of a Airport or Helicopter Operations SBAS Path Point record or GBAS Path Point Record. It establishes the intended descent gradient for the final approach flight path. For an illustration of the GPA and related points.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"/></xs:simpleType>
The “GNSS Channel Number” field identifies the channel to be used for a given approach.The “MLS Channel” field specifies the channel of the Azimuth, Elevation and Data transmissions for the MLS identified in the “MLS Identifier” field of the record.
<xs:simpleType name="Channel"><xs:annotation><xs:documentation>The “GNSS Channel Number” field identifies the channel to be used for a given approach. The “MLS Channel” field specifies the channel of the Azimuth, Elevation and Data transmissions for the MLS identified in the “MLS Identifier” field of the record.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="5"/></xs:restriction></xs:simpleType>
The “Length Offset” field is the distance from the stop end of the runway (SER) to the FPAP. This distance defines the location where lateral sensitivity changes to the missed approach sensitivity. If the FPAP is located at the designated center of the opposite runway end, the distance is zero.Additionally, if the procedure is a Point in Space procedure and there is no runway, the value is set to 0000 (all zeros).
<xs:simpleType name="LengthOffset"><xs:annotation><xs:documentation>The “Length Offset” field is the distance from the stop end of the runway (SER) to the FPAP. This distance defines the location where lateral sensitivity changes to the missed approach sensitivity. If the FPAP is located at the designated center of the opposite runway end, the distance is zero.Additionally, if the procedure is a Point in Space procedure and there is no runway, the value is set to 0000 (all zeros).</xs:documentation></xs:annotation><xs:restriction base="type:DistanceFeet"/></xs:simpleType>
On procedures to runways or helipads, the Path Point TCH is the height above the runway threshold (LTP) or the helicopter alighting point. On procedures which are Point in Space, the height of the fictitious helipoint (or helipoint) above the height of the heliport. It is the same as the TCH defined in Section 5.67, but has greater resolution due to the required precision. The value may be expressed in feet to a resolution of tenths of feet, or meters to a resolution of hundredths of meters. Whether the value is in feet or meters can be determined from the TCH Units Indicator.
<xs:simpleType name="PathPointTCH"><xs:annotation><xs:documentation>On procedures to runways or helipads, the Path Point TCH is the height above the runway threshold (LTP) or the helicopter alighting point. On procedures which are Point in Space, the height of the fictitious helipoint (or helipoint) above the height of the heliport. It is the same as the TCH defined in Section 5.67, but has greater resolution due to the required precision. The value may be expressed in feet to a resolution of tenths of feet, or meters to a resolution of hundredths of meters. Whether the value is in feet or meters can be determined from the TCH Units Indicator.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"><xs:totalDigits value="6"/><xs:fractionDigits value="2"/></xs:restriction></xs:simpleType>
The “Reference Path Data Selector” field enables the automatic tuning of a procedure by Ground Based Augmentation Systems (GBAS) avionics.This data is not used for SBAS operations.
<xs:simpleType name="ReferencePathDataSelector"><xs:annotation><xs:documentation>The “Reference Path Data Selector” field enables the automatic tuning of a procedure by Ground Based Augmentation Systems (GBAS) avionics.This data is not used for SBAS operations.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="2"/></xs:restriction></xs:simpleType>
The Reference Path Identifier field represents the three or four alphanumeric characters used to uniquely designate the reference path. The Reference Path Identifier is synonymous with the approach ID located beneath the Channel Number on Instrument Approach Plates and is unique only for a given airport.
<xs:simpleType name="ReferencePathIdentifier"><xs:annotation><xs:documentation>The Reference Path Identifier field represents the three or four alphanumeric characters used to uniquely designate the reference path. The Reference Path Identifier is synonymous with the approach ID located beneath the Channel Number on Instrument Approach Plates and is unique only for a given airport.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="4"/></xs:restriction></xs:simpleType>
The “Route Indicator” field is a single alpha character used to differentiate between multiple final approach segments to the same runway or helipad contained in the Final Approach Coding.
<xs:simpleType name="RouteIndicator"><xs:annotation><xs:documentation>The “Route Indicator” field is a single alpha character used to differentiate between multiple final approach segments to the same runway or helipad contained in the Final Approach Coding.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="1"/></xs:restriction></xs:simpleType>
This XML element is designed as an abstraction for Runway Identifier or Pad Identifier, this is done by using the XML attribute "choice", so that only one of the elements can be present in the XML file.
<xs:complexType name="RunwayOrPadIdentifier"><xs:annotation><xs:documentation>This XML element is designed as an abstraction for Runway Identifier or Pad Identifier, this is done by using the XML attribute "choice", so that only one of the elements can be present in the XML file.</xs:documentation></xs:annotation><xs:choice><xs:element name="padIdentifier" type="type:CoreIdentifier" minOccurs="1" maxOccurs="1"/><xs:element name="runwayIdentifier" type="type:RunwayIdentifier" minOccurs="1" maxOccurs="1"/></xs:choice></xs:complexType>
<xs:complexType name="RunwayIdentifier"><xs:annotation><xs:documentation>The “Runway Identifier” field identifies the runways described in runway records and runways served by the ILS/MLS described in ILS/MLS records.</xs:documentation></xs:annotation><xs:sequence><xs:element name="runwayLeftRightCenterType" type="enum:RunwayLeftRightCenterType" minOccurs="0" maxOccurs="1"/><xs:element name="runwayNumber" type="type:RunwayNumber" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="RunwayLeftRightCenterType"><xs:annotation><xs:documentation>Runway Left/Right/Centre Indicator</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Left"><xs:annotation><xs:documentation>Left (Runway of two or three parallel runways)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Right"><xs:annotation><xs:documentation>Right (Runway of two or three parallel runways)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Center"><xs:annotation><xs:documentation>Center (Runway of three parallel runways)</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “RunwayNumber” field identifies the runways described in runway records and runways served by the ILS/MLS described in ILS/MLS records. The runway Number is only part of the Runway Identifier.
<xs:simpleType name="RunwayNumber"><xs:annotation><xs:documentation>The “RunwayNumber” field identifies the runways described in runway records and runways served by the ILS/MLS described in ILS/MLS records. The runway Number is only part of the Runway Identifier.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:maxInclusive value="36"/><xs:minInclusive value="1"/></xs:restriction></xs:simpleType>
<xs:simpleType name="TCHUnitsIndicator"><xs:annotation><xs:documentation>The TCH Units Indicator field is used in Path Point Records to define the units, Feet or Meters for the Path Point TCH.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Feet"><xs:annotation><xs:documentation>the Path Point TCH is provided in source documentation in Feet</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Meters"><xs:annotation><xs:documentation>Path Point TCH is provided in source documentation in meters</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="GBASOperationType"><xs:annotation><xs:documentation>The “Operation Type” field indicates whether the operation is an approach procedure, an advanced operation or other operational to be defined later.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="0"><xs:annotation><xs:documentation>Straight-in approach path</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1"><xs:annotation><xs:documentation>Terminal Area Path definition (not for FAS Datablock)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="2"><xs:annotation><xs:documentation>Missed Approach (not for FAS Datablock)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="3"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="4"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="5"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="6"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="7"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="8"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="9"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="10"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="11"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="12"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="13"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="14"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="15"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="SBASPathPoint"><xs:annotation><xs:documentation>This following record contains the fields used in Path Point Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="PathPoint"><xs:sequence><xs:element name="hal" type="type:HorizontalAlertLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Horizontal Alert Limit (HAL) is the radius of a circle in the horizontal plane (the local plane tangent to the WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated horizontal position with the required probability for a particular navigation mode assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.</xs:documentation></xs:annotation></xs:element><xs:element name="operationType" type="enum:SBASOperationType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Operation Type” field indicates whether the operation is an approach procedure, an advanced operation or other operational to be defined later.</xs:documentation></xs:annotation></xs:element><xs:element name="sbasServiceProviderIdentifier" type="enum:SBASServiceProviderIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “SBAS Service Provider Identifier” field is used to associate the approach procedure to a particular satellite based approach system service provider.</xs:documentation></xs:annotation></xs:element><xs:element name="val" type="type:VerticalAlertLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Vertical Alert Limit (VAL) is half the length of a segment on the vertical axis (perpendicular to the horizontal plane of WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated vertical position with a probability of 1-10-7 per approach, assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.</xs:documentation></xs:annotation></xs:element><xs:element name="FinalApproachCourse" type="type:Course"><xs:annotation><xs:documentation>The SBAS Final Approach Course field contains the published final approach course of the PBN procedure with SBAS level of service.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The Horizontal Alert Limit (HAL) is the radius of a circle in the horizontal plane (the local plane tangent to the WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated horizontal position with the required probability for a particular navigation mode assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.
<xs:simpleType name="HorizontalAlertLimit"><xs:annotation><xs:documentation>The Horizontal Alert Limit (HAL) is the radius of a circle in the horizontal plane (the local plane tangent to the WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated horizontal position with the required probability for a particular navigation mode assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceMeters"/></xs:simpleType>
<xs:simpleType name="SBASOperationType"><xs:annotation><xs:documentation>The “Operation Type” field indicates whether the operation is an approach procedure, an advanced operation or other operational to be defined later.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="0"><xs:annotation><xs:documentation>Straight-in or point-in-space approach procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1"><xs:annotation><xs:documentation>Reserved for future definition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="2"><xs:annotation><xs:documentation>Reserved for future definition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="3"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="4"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="5"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="6"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="7"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="8"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="9"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="10"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="11"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="12"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="13"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="14"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="15"><xs:annotation><xs:documentation>Spare</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “SBAS Service Provider Identifier” field is used to associate the approach procedure to a particular satellite based approach system service provider.
<xs:simpleType name="SBASServiceProviderIdentifier"><xs:annotation><xs:documentation>The “SBAS Service Provider Identifier” field is used to associate the approach procedure to a particular satellite based approach system service provider.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="0"><xs:annotation><xs:documentation>WAAS</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1"><xs:annotation><xs:documentation>EGNOS</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="2"><xs:annotation><xs:documentation>MSAS</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="14"><xs:annotation><xs:documentation>Not intended for SBAS</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="15"><xs:annotation><xs:documentation>Any Service provider may be used</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Vertical Alert Limit (VAL) is half the length of a segment on the vertical axis (perpendicular to the horizontal plane of WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated vertical position with a probability of 1-10-7 per approach, assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.
<xs:simpleType name="VerticalAlertLimit"><xs:annotation><xs:documentation>The Vertical Alert Limit (VAL) is half the length of a segment on the vertical axis (perpendicular to the horizontal plane of WGS-84 ellipsoid), with its center being at the true position, which describes the region which is required to contain the indicated vertical position with a probability of 1-10-7 per approach, assuming the probability of a GPS satellite integrity failure being included in the position solution is less than or equal to 10-4 per hour.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"/></xs:simpleType>
<xs:complexType name="ApproachTransition"><xs:annotation><xs:documentation>This class is an abstraction of Approach Transition.</xs:documentation></xs:annotation><xs:complexContent mixed="false"><xs:extension base="ApproachRoute"><xs:sequence><xs:element name="multipleIndicator" type="type:MultipleIndicator" minOccurs="0" maxOccurs="1"/><xs:element name="taaReference" type="xs:IDREF" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="ApproachRoute" abstract="true"><xs:annotation><xs:documentation>This atstract element represents of shared information between SID and STAR Enroute Transitions.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="ProcedureRoute"><xs:sequence><xs:element name="qualifier1" type="enum:ApproachQualifier1" minOccurs="0" maxOccurs="1"/><xs:element name="qualifier2" type="enum:ApproachQualifier2" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="ApproachQualifier1"><xs:annotation><xs:documentation>Route Qualifier 1 for Airport Approach (PF) and Heliport (HF) Records – Route Type</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="RnavVisual"><xs:annotation><xs:documentation>RNAV Visual Procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DmeRequired"><xs:annotation><xs:documentation>DME Required for Procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GpsRequiredDmeDmeNotAuthorized"><xs:annotation><xs:documentation>GPS (GNSS) required, DME/DME to RNP xx.x not authorized</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RnpAr"><xs:annotation><xs:documentation>RNP SAAAR/AR</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AdvancedRnp"><xs:annotation><xs:documentation>Advanced (RNAV RNP, SAAAR/AR not required)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Gbas"><xs:annotation><xs:documentation>GBAS Procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DmeNotRequired"><xs:annotation><xs:documentation>DME Not Required for Procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GnssRequired"><xs:annotation><xs:documentation>GNSS Required</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GnssorDmeDmeRequired"><xs:annotation><xs:documentation>GPS (GNSS) or DME/DME to RNP xx.x required</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DmeDmeRequired"><xs:annotation><xs:documentation>DME/DME Required for Procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RnavSensorNotSpecified"><xs:annotation><xs:documentation>RNAV, Sensor Not Specified</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VorDmeRnav"><xs:annotation><xs:documentation>VOR/DME RNAV</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RnavRequiresFasDataBlock"><xs:annotation><xs:documentation>RNAV Procedure that Requires FAS Data Block</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ApproachQualifier2"><xs:annotation><xs:documentation>Route Type Qualifier 2 for Airport Approach (PF) and Heliport (HF) Records – Route Type</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="PrimaryMissedApproach"><xs:annotation><xs:documentation>Primary Missed Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SecondaryMissedApproach"><xs:annotation><xs:documentation>Secondary Missed Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="EngineOutMissedApproach"><xs:annotation><xs:documentation>Engine Out Missed Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CircleToLandMinimums"><xs:annotation><xs:documentation>Procedure with Circle-To-Land Minimums</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HelicopterStraightInMinimums"><xs:annotation><xs:documentation>Helicopter with straight-in minimums</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HelicopterCircleToLandMinimums"><xs:annotation><xs:documentation>Helicopter with circle-to-land minimums</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HelicopterLandingMinimums"><xs:annotation><xs:documentation>Helicopter with Helicopter Landing Minimums</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="StraightInMinimums"><xs:annotation><xs:documentation>Procedure with Straight-in Minimums</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VmcMinimums"><xs:annotation><xs:documentation>Procedure with VMC minimums</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="FinalApproach"><xs:annotation><xs:documentation>This class is an abstraction of Final Transition.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="ApproachRoute"><xs:sequence><xs:element name="fasBlockProvided" type="enum:LevelOfServiceAuthorised" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="fasBlockProvidedLevelOfServiceName" type="enum:LevelOfServiceName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.</xs:documentation></xs:annotation></xs:element><xs:element name="isRemoteAltimeterRestricted" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field indicates whether or not the existence and use of a remote altimeter setting is applicable to the procedure. The field is true when there is a restriction on the use of LNAV/VNAV (Baro-VNAV) lines of minimum.</xs:documentation></xs:annotation></xs:element><xs:element name="lnavAuthorisedForSBAS" type="enum:LevelOfServiceAuthorised" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="lnavLevelOfServiceName" type="enum:LevelOfServiceName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.</xs:documentation></xs:annotation></xs:element><xs:element name="lnavVNAVAuthorisedForSBAS" type="enum:LevelOfServiceAuthorised" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="lnavVNAVLevelOfServiceName" type="enum:LevelOfServiceName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureTCH" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element><xs:element name="rnpLOS" type="type:RNPLOS" minOccurs="0" maxOccurs="unbounded"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.
Diagram
Type
restriction of xs:string
Facets
enumeration
Authorized
Designated Level of Service is authorized for the procedure
enumeration
NotAuthorized
Designated Level of Service is not authorized for the procedure
<xs:simpleType name="LevelOfServiceAuthorised"><xs:annotation><xs:documentation>The “Level of Service Authorized” field defines whether the Level of Service designated in an associated field (Section 5.275) is authorized or not authorized for a procedure.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Authorized"><xs:annotation><xs:documentation>Designated Level of Service is authorized for the procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotAuthorized"><xs:annotation><xs:documentation>Designated Level of Service is not authorized for the procedure</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.
<xs:simpleType name="LevelOfServiceName"><xs:annotation><xs:documentation>The “Level of Service Name” field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for SBAS and/or RNP.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="10"/><xs:enumeration value="LPV"/><xs:enumeration value="LPV200"/><xs:enumeration value="LP"/><xs:enumeration value="LNAV"/><xs:enumeration value="LNAV/VNAV"/></xs:restriction></xs:simpleType>
<xs:simpleType name="ThresholdCrossingHeight"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
<xs:complexType name="RNPLOS"><xs:sequence><xs:element name="rnp" type="xs:decimal" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This field contains the RNP level of service in decimal e.g. 1.0</xs:documentation></xs:annotation></xs:element><xs:element name="rnpLOSAuthorized" type="enum:RnpLOSAuthorized" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="MissedApproach"><xs:annotation><xs:documentation>This class is an abstraction of Missed Approach Transition.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="ApproachRoute"/></xs:complexContent></xs:complexType>
<xs:simpleType name="ApproachPbnNavSpec"><xs:annotation><xs:documentation>This field provides information on the ICAO PBN Navigation Specification appliable to this approach</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Rnav1"/><xs:enumeration value="Rnp1"/><xs:enumeration value="RnpAr"/><xs:enumeration value="AdvRnp"/><xs:enumeration value="Rnp0_3"/><xs:enumeration value="PbnUnspecified"/><xs:enumeration value="RnpApch"/></xs:restriction></xs:simpleType>
<xs:complexType name="TerminalWaypoint"><xs:annotation><xs:documentation>This following record contains the fields used in Waypoint Record</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Waypoint"><xs:sequence/></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Waypoint"><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="nameFormatIndicator" type="type:NameFormatIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Name Format Indicator” field is used to describe the format of the “Waypoint Name/Description” field (5.43). This field will be formatted according to the rules described in Chapter 7 of this Specification, Waypoint Naming Conventions.</xs:documentation></xs:annotation></xs:element><xs:element name="waypointType" type="type:WaypointType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Waypoint Type” field identifies a number of data conditions. 1. The first is whether or not the waypoint has been published in an official government source or created during database coding of routes or procedures. 2. The second is whether or not the waypoint is an intersection formed with reference to ground based navaids or is an RNAV Waypoint formed by the latitude and longitude. 3. The third is an indication of one or more functions assigned to that waypoint in terminal procedure coding. 4. The fourth is an indication of location of the waypoint with reference to airspace boundaries and/or grid lines. 5. The fifth is an indication of how ATC might be using the waypoint in operational clearances. 6. The sixth is an indication that the waypoint has been published for VFR use only. 7. Lastly, there is an indication of whether the waypoint is published for use in terminal procedure coding of a specific type, multiple types or not published at all.</xs:documentation></xs:annotation></xs:element><xs:element name="waypointUsage" type="type:WaypointUsage" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The waypoint usage field is employed to indicate the structure in which the waypoint is utilized.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Name Format Indicator” field is used to describe the format of the “Waypoint Name/Description” field (5.43). This field will be formatted according to the rules described in Chapter 7 of this Specification, Waypoint Naming Conventions.
<xs:complexType name="NameFormatIndicator"><xs:annotation><xs:documentation>The “Name Format Indicator” field is used to describe the format of the “Waypoint Name/Description” field (5.43). This field will be formatted according to the rules described in Chapter 7 of this Specification, Waypoint Naming Conventions.</xs:documentation></xs:annotation><xs:sequence><xs:element name="fixType" type="enum:FixType" minOccurs="1" maxOccurs="1"/><xs:element name="localizerMarkerIndicator" type="enum:LocalizerMarkerIndicator" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="FixType"><xs:annotation><xs:documentation>Fix Type Enums for the field Name Format Indicator</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Abeam"><xs:annotation><xs:documentation>Abeam a Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="BearingDistance"><xs:annotation><xs:documentation>Bearing and Distance Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AirportName"><xs:annotation><xs:documentation>Airport Name as Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Fir"><xs:annotation><xs:documentation>FIR Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PhoeneticLetterName"><xs:annotation><xs:documentation>Phoenetic Letter Name Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AirportIdent"><xs:annotation><xs:documentation>Airport Ident as Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LatLong"><xs:annotation><xs:documentation>Latitude/Longitude Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MultipleWord"><xs:annotation><xs:documentation>Multiple Word as Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Navaid"><xs:annotation><xs:documentation>Navaid Ident as Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PublishedFiveLetterName"><xs:annotation><xs:documentation>Published Five - Letter - Name Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PublishedLessThanFiveLetterName"><xs:annotation><xs:documentation>Published Name Fix, less than Five Letters</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PublishedMoreThanFiveName"><xs:annotation><xs:documentation>Published Name Fix, more than Five Letters</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AptRwyRelated"><xs:annotation><xs:documentation>Apt/Rwy Related Fix (Note 2)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Uir"><xs:annotation><xs:documentation>UIR Fix</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="LocalizerMarkerIndicator"><xs:annotation><xs:documentation>The localizer Marker Indicator enums for the Name format Indicator Field.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="OfficialFiveLetter"><xs:annotation><xs:documentation>Localizer Marker with official published five - letter identifier</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NoPublishedFiveLetter"><xs:annotation><xs:documentation>Localizer Marker without official published five - letter identifier</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Waypoint Type” field identifies a number of data conditions.1. The first is whether or not the waypoint has been published in an official government source or created during database coding of routes orprocedures. 2. The second is whether or not the waypoint is an intersection and/or DME fix formed with reference to ground based navaids or is an RNAV Waypoint formed by thelatitude and longitude. 3. The third is an indication of one or more functions assigned to that waypoint in terminal procedure coding.4. The fourth is an indication of location of the waypoint with reference to airspace boundaries and/or grid lines.5. The fifth is an indication of how ATC might be using the waypoint in operational clearances.6. The sixth is an indication that the waypoint has been published for VFR use only.7. Lastly, there is an indication of whether the waypoint is published for use in terminal procedure coding of a specific type, multiple types or not published at all.
<xs:complexType name="WaypointType"><xs:annotation><xs:documentation>The “Waypoint Type” field identifies a number of data conditions. 1. The first is whether or not the waypoint has been published in an official government source or created during database coding of routes or procedures. 2. The second is whether or not the waypoint is an intersection and/or DME fix formed with reference to ground based navaids or is an RNAV Waypoint formed by the latitude and longitude. 3. The third is an indication of one or more functions assigned to that waypoint in terminal procedure coding. 4. The fourth is an indication of location of the waypoint with reference to airspace boundaries and/or grid lines. 5. The fifth is an indication of how ATC might be using the waypoint in operational clearances. 6. The sixth is an indication that the waypoint has been published for VFR use only. 7. Lastly, there is an indication of whether the waypoint is published for use in terminal procedure coding of a specific type, multiple types or not published at all.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isAirwayIntersection" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isArcCenter" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isBackMarker" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isControlledAirspaceIntersesction" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isEnroute" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFACF" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFAF" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFIRorFRAEntryPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFIRorFRAExitPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFirUirFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isForApproach" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isForSID" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isForStar" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isForMultipleProcedures" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFRAArrivalTransitionPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFRADepatureTransitionPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFRAIntermediatePoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFRATerminalHoldingPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFullDegreeLatFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isHalfDegreeLatFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isHelicopterOnlyAirwayFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isInitialApproachFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isInitialDepartureFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isInnerMarker" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isIntermediateApproachFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isIntersectionDmeFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field applies to the intersection of concepts that apply to aspects of conventional navigation. e.g., a fix at DME 10.</xs:documentation></xs:annotation></xs:element><xs:element name="isMiddleMarker" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isMissedApproachPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isNDB" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isOceanicGateway" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isOffRoute" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isOuterMarker" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isRequiredOffRoute" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isRfLegNotProcedureFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><!-- These two RNAV flags can be set independently in 424 --><xs:element name="isRNAV" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isUsageRNAV" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isSourceProvidedEnroute" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isStepDownFix" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isUncharted" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isUnnamed" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isVFR" type="xs:boolean" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="WaypointUsage"><xs:annotation><xs:documentation>The waypoint usage field is employed to indicate the structure in which the waypoint is utilized.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isHi" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isLo" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isTerminal" type="xs:boolean" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="TAA"><xs:annotation><xs:documentation>The Airport Terminal Arrival Altitude (TAA) file contains details relating to TAA sectorization and sector altitudes.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="approachTypeIdentifier" type="type:ApproachTypeIdentifier" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>Identifies the approach types published on a given approach procedure which require Airport or Helicopter Operations SBAS path points.</xs:documentation></xs:annotation></xs:element><xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element><xs:element name="taaFixPositionIndicator" type="enum:TAASectorIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>TThe Fix Position Indicator field contains an indication as to which TAA Initial Approach Fix (IAF) the data in the record applies.</xs:documentation></xs:annotation></xs:element><xs:element name="sectorTAADetails" type="type:TAASectorDetails" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a TAA Sector.</xs:documentation></xs:annotation></xs:element><xs:element name="taaIAFWaypointReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “TAA IAF Waypoint” field contains the identifier of the Initial Approach Fix (IAF) associated with a given Terminal Area Altitude sector. There may be one, two or three such IAF waypoints defined for a single approach procedure. The TAA IAF Waypoint identified in the TAA Sector with the identifier of “C” (Section 5.272) is the fix to which all sector bearing information for the procedure TAA is defined. The TAA IAF Waypoint in the individual TAA Sector records is the fix from which radius distances are defined.</xs:documentation></xs:annotation></xs:element><xs:element name="sectorBearingWaypointRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Sector Bearing Reference Waypoint field contains the identifier of the waypoint that the Sector Bearings are referenced to within a given Terminal Area Altitude sector</xs:documentation></xs:annotation></xs:element></xs:sequence><xs:attribute name="referenceID" use="required" type="xs:ID"/></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="TAASectorIdentifier"><xs:annotation><xs:documentation>The Fix Position Indicator field contains an indication as to which TAA Initial Approach Fix (IAF) the data in the record applies.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="StraightInOrCenterFix"><xs:annotation><xs:documentation>Straight-In or Center Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LeftBase"><xs:annotation><xs:documentation>Left Base Area</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RightBase"><xs:annotation><xs:documentation>Right Base Area</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="TAASectorDetails"><xs:annotation><xs:documentation>This class represents the details for a TAA Sector.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Sector"><xs:sequence><xs:element name="sectorRadiusStart" type="type:RadiusLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Sector Radius Start” field in TAA records defines the start distance that defines a TAA area. It is referenced to the TAA IAF Waypoint defined in that record. As TAA information is used towards that waypoint, the radius information is provided towards that waypoint. It encloses the sector defined in the record. The value is inclusive.</xs:documentation></xs:annotation></xs:element><xs:element name="sectorRadiusEnd" type="type:RadiusLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Sector Radius End” field in TAA records defines the end distance that defines a TAA area. It is referenced to the TAA IAF Waypoint defined in that record. As TAA information is used towards that waypoint, the radius information is provided towards that waypoint. It encloses the sector defined in the record. The value is inclusive.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureTurn" type="xs:boolean" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
When used on MSA Records, the “Sector Bearing” contains beginning and ending bearing values, referenced to the MSA Center, for each sector of the MSA. When used on TAA records, the “Sector Bearing” contains the beginning and ending bearings that define a TAA Area and are referenced to the TAA Initial Approach Fix (IAF) Waypoint.
<xs:simpleType name="SectorBearing"><xs:annotation><xs:documentation>When used on MSA Records, the “Sector Bearing” contains beginning and ending bearing values, referenced to the MSA Center, for each sector of the MSA. When used on TAA records, the “Sector Bearing” contains the beginning and ending bearings that define a TAA Area and are referenced to the TAA Initial Approach Fix (IAF) Waypoint.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
The altitude shown in the Sector Altitude field provides a 1000 foot obstacle clearance with a specified radius from the navigational facility/fix. The Radius Limit, field allows the radius to be specified.
<xs:simpleType name="RadiusLimit"><xs:annotation><xs:documentation>The altitude shown in the Sector Altitude field provides a 1000 foot obstacle clearance with a specified radius from the navigational facility/fix. The Radius Limit, field allows the radius to be specified.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceIntegerNMTwoDigits"/></xs:simpleType>
<xs:complexType name="PortCommunication"><xs:annotation><xs:documentation>This following record contains the fields used in Communication records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Communication"><xs:sequence><xs:element name="communicationDistance" type="type:CommunicationDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Distance” field is used to define the distance restriction a communication frequency is to be used within or beyond when such restrictions apply. This field is used in conjunction with the Distance Description field.</xs:documentation></xs:annotation></xs:element><xs:element name="distanceDescription" type="enum:DistanceDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance Description” field will designate whether a communication frequency is to be used from the facility out to a specified distance or from a specified distance and beyond in the Airport Communication Record. In the VHF Navaid Limitation Continuation Record, the field is used to define whether the limitation applies from the navaid out to a specified distance or from a specified distance and beyond.</xs:documentation></xs:annotation></xs:element><xs:element name="multiSectorIndicator" type="enum:MultiSectorIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Multi-Sector Indicator” field is used to indicate that the communication service and frequency are used in more than one defined sector. The actual sector data will be contained in the primary and continuation records of the affected airport or heliport communication record set.</xs:documentation></xs:annotation></xs:element><xs:element name="portCommunicationSectorizationNarrative" type="type:SectorizationNarrative" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Port Communication Sectorization Narrative Class description.</xs:documentation></xs:annotation></xs:element><xs:element name="sectorFacility" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Sector Facility” field is used to define the Navaid or Airport upon which the information in the “Sector” (5.183) field is based.</xs:documentation></xs:annotation></xs:element><xs:element name="sectorization" type="type:Sectorization" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Sectorization” field is used to define the airspace sector a communication frequency is applicable for when an airport defines sectors by bearing from the same point.</xs:documentation></xs:annotation></xs:element><xs:element name="serviceIndicator" type="type:AirportHeliportCommunicationServiceIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Service Indicator” field is used to further define the use of the frequency for the specified Communication Type (5.101).</xs:documentation></xs:annotation></xs:element><xs:element name="additionalSectorization" type="type:AdditionalSectorization" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This element is used to represent the details for an Additional Sectorization used in port communications.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Communication"><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="location" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element><xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationAltitude1" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Altitude 1 and Altitude 2” fields are used to provide information on use of communication services frequencies with reference to specific altitudes. If the communication record in which Communication Altitude data is provided includes Sectorization data (5.183), the altitude data is valid only for the specific Sector.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationAltitude2" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Altitude 1 and Altitude 2” fields are used to provide information on use of communication services frequencies with reference to specific altitudes. If the communication record in which Communication Altitude data is provided includes Sectorization data (5.183), the altitude data is valid only for the specific Sector.</xs:documentation></xs:annotation></xs:element><xs:element name="callSign" type="type:CallSign" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Call Sign” field contains the name of a communication service provider that is to be used when contacting that service/used by the service to identify itself when contacting aircraft on the frequencies contained in the record. The field is also used to provide the broadcast identification name of automated services.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationClass" type="enum:CommunicationClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Class” field will designate the major grouping of the Communication Types contained in the record.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationType" type="enum:CommunicationType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.</xs:documentation></xs:annotation></xs:element><xs:element name="frequencyUnits" type="enum:FrequencyUnits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Frequency Units” field will designate the frequency spectrum area for the frequency in the “Communication Frequency” (Section 5.103) field as indicated in the table or will designate the content of the “Communication Frequency” field as a channel. For VHF based units, the field will also designate the established frequency spacing required of the frequency for unambiguous use.</xs:documentation></xs:annotation></xs:element><xs:element name="radarService" type="enum:Radar" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Radar” field indicates whether or not the communication unit identified in the record has access to and uses information derived from primary or secondary radars while performing the communication service indicated by the Communication Type. It is not an indication of an operational radar frequency.</xs:documentation></xs:annotation></xs:element><xs:element name="h24Indicator" type="enum:H24Indicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “24H Indicator” field is used to indicate whether a communication service frequency is available for use on a continual, i.e. 24 hours a day, seven days a week, basis or not.</xs:documentation></xs:annotation></xs:element><xs:element name="modulation" type="enum:Modulation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Modulation” field will design the type of modulation for the frequency in the “Communication Frequency” (5.103) field.</xs:documentation></xs:annotation></xs:element><xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>When used on Enroute, Airport and Heliport Communication Primary and Continuation records, the Sequence Number is used as a record counter within a given Identifier and Communication Class for providing output file record uniqueness. (See ARINC 424 5.12)</xs:documentation></xs:annotation></xs:element><xs:element name="signalEmission" type="enum:SignalEmission" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>High Frequency (HF) signals used in aeronautical communications can be the complete signal or a portion of the signal, called a sideband. The “Signal Emission” field will designate for each HF Frequency what emission is used.</xs:documentation></xs:annotation></xs:element><xs:element name="transmitFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Communication Frequency field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.</xs:documentation></xs:annotation></xs:element><xs:element name="receiveFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Communication Frequency field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationDetails" type="CommunicationDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Information contained in the ARINC 424 communication continuation records</xs:documentation></xs:annotation></xs:element><xs:element name="guardTransmit" type="xs:string" minOccurs="0" maxOccurs="1"><!-- Legacy 424-18 support --><xs:annotation><xs:documentation>The “Guard/Transmit” field is used to indicate if the frequency shown in the Communication Frequency field is used, by the station, to receive voice communication or to transmit voice on.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Call Sign” field contains the name of a communications service provider that is to be used when contacting that service/used by the service to identify itself when contacting aircraft on the frequencies contained in the record. The field is also used to provide the broadcast identification name of automated services.
<xs:simpleType name="CallSign"><xs:annotation><xs:documentation>The “Call Sign” field contains the name of a communications service provider that is to be used when contacting that service/used by the service to identify itself when contacting aircraft on the frequencies contained in the record. The field is also used to provide the broadcast identification name of automated services.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="25"/></xs:restriction></xs:simpleType>
The Communication Class field will designate the major grouping of the Communication Types contained in the record.
Diagram
Type
restriction of xs:string
Facets
enumeration
LIRC
The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing control services to aircraft.
enumeration
LIRI
The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing information services to aircraft.
enumeration
USVC
The Communication Type is that of one used within an Information Region (FIR/UIR) for purposes other than control or information services and is not linked to that Region
enumeration
ASVC
The Communication Type is that of one providing automated or broadcast services within an Information Region (FIR/UIR).
enumeration
ATCF
The Communication Type is that of one providing ATC services to aircraft within the terminal area of an airport.
enumeration
GNDF
The Communication Type is that of one providing ATC services to aircraft on the ground at an airport.
enumeration
AOTF
The Communication Type is that of one providing services other than ATC functions on the ground or within the terminal area of an airport.
enumeration
AFAC
The Communication Type is that of one provided automated or broadcast services to aircraft on the ground or with the terminal area of an airport.
<xs:simpleType name="CommunicationClass"><xs:annotation><xs:documentation>The Communication Class field will designate the major grouping of the Communication Types contained in the record.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="LIRC"><xs:annotation><xs:documentation>The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing control services to aircraft.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LIRI"><xs:annotation><xs:documentation>The Communication Type is that of one linked to an Information Region (FIR/UIR) for the purposes of providing information services to aircraft.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="USVC"><xs:annotation><xs:documentation>The Communication Type is that of one used within an Information Region (FIR/UIR) for purposes other than control or information services and is not linked to that Region</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ASVC"><xs:annotation><xs:documentation>The Communication Type is that of one providing automated or broadcast services within an Information Region (FIR/UIR).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ATCF"><xs:annotation><xs:documentation>The Communication Type is that of one providing ATC services to aircraft within the terminal area of an airport.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GNDF"><xs:annotation><xs:documentation>The Communication Type is that of one providing ATC services to aircraft on the ground at an airport.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AOTF"><xs:annotation><xs:documentation>The Communication Type is that of one providing services other than ATC functions on the ground or within the terminal area of an airport.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AFAC"><xs:annotation><xs:documentation>The Communication Type is that of one provided automated or broadcast services to aircraft on the ground or with the terminal area of an airport.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Communication Type” is a three-character code indicating the type of communications service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.
<xs:simpleType name="CommunicationType"><xs:annotation><xs:documentation>The “Communication Type” is a three-character code indicating the type of communications service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="ACC"><xs:annotation><xs:documentation>Area Control Center</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ACP"><xs:annotation><xs:documentation>Airlift Command Post</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AIR"><xs:annotation><xs:documentation>Air to Air</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="APP"><xs:annotation><xs:documentation>Approach Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ARR"><xs:annotation><xs:documentation>Arrival Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ASO"><xs:annotation><xs:documentation>Automatic Surface Observing System (ASOS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ATI"><xs:annotation><xs:documentation>Automatic Terminal Info Service (ATIS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AWI"><xs:annotation><xs:documentation>Airport Weather Information Broadcast (AWIB)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AWO"><xs:annotation><xs:documentation>Automatic Weather Observing Service (AWOS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AWS"><xs:annotation><xs:documentation>Aerodrome Weather Information Services (AWIS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CBA"><xs:annotation><xs:documentation>Class B Airspace</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CCA"><xs:annotation><xs:documentation>Class C Airspace</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CLD"><xs:annotation><xs:documentation>Clearance Delivery</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CPT"><xs:annotation><xs:documentation>Clearance, Pre-Taxi</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CTA"><xs:annotation><xs:documentation>Control Area (Terminal)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CTF"><xs:annotation><xs:documentation>Common Traffic Advisory Frequencies (Note 2)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CTL"><xs:annotation><xs:documentation>Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DEP"><xs:annotation><xs:documentation>Departure Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DIR"><xs:annotation><xs:documentation>Director (Approach Control Radar)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="EFS"><xs:annotation><xs:documentation>Enroute Flight Advisory Service (EFAS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="EMR"><xs:annotation><xs:documentation>Emergency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FSS"><xs:annotation><xs:documentation>Flight Service Station</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GCO"><xs:annotation><xs:documentation>Ground Comm Outlet</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GND"><xs:annotation><xs:documentation>Ground Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GTE"><xs:annotation><xs:documentation>Gate Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HEL"><xs:annotation><xs:documentation>Helicopter Frequency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="INF"><xs:annotation><xs:documentation>Information</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MBZ"><xs:annotation><xs:documentation>Mandatory Broadcast</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MIL"><xs:annotation><xs:documentation>Military Frequency Zone (note 2)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MUL"><xs:annotation><xs:documentation>Multicom</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OPS"><xs:annotation><xs:documentation>Operations</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PAL"><xs:annotation><xs:documentation>Pilot Activated Lighting (Note 1)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RDO"><xs:annotation><xs:documentation>Radio</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RDR"><xs:annotation><xs:documentation>Radar</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RFS"><xs:annotation><xs:documentation>Remote Flight Service Station (RFSS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RMP"><xs:annotation><xs:documentation>Ramp/Taxi Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RSA"><xs:annotation><xs:documentation>Airport Radar Service Area (ARSA)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TCA"><xs:annotation><xs:documentation>Terminal Control Area (TCA)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TMA"><xs:annotation><xs:documentation>Terminal Control Area (TMA)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TML"><xs:annotation><xs:documentation>Terminal</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TRS"><xs:annotation><xs:documentation>Terminal Radar Service Area (TRSA)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TWE"><xs:annotation><xs:documentation>Transcriber Weather Broadcast (TWEB)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TWR"><xs:annotation><xs:documentation>Tower, Air Traffic Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="UAC"><xs:annotation><xs:documentation>Upper Area Control</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="UNI"><xs:annotation><xs:documentation>Unicom</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VOL"><xs:annotation><xs:documentation>Volnet</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Frequency Units field will designate the frequency spectrum area for the frequency in the Communication Frequency (Section 5.103) field as indicated in the table or will designate the content of the Communication Frequency field as a channel. For VHF based units, the field will also designate the established frequency spacing required of the frequency for unambiguous use.
Diagram
Type
restriction of xs:string
Facets
enumeration
LowFreq
Low Frequency
enumeration
MediumFreq
Medium Frequency
enumeration
HighFreq
High Frequency(3000 kHz to 30,000 kHz)
enumeration
Vhf100kHzSpacing
Very High Frequency 100 kHz spacing
enumeration
Vhf50kHzSpacing
Very High Frequency 50 kHz spacing
enumeration
Vhf25kHzSpacing
Very High Frequency 25 kHz spacing
enumeration
VhfNonStandard
Very High Frequency (30,000 kHz to 200 MHz) Non-standard spacing
enumeration
Uhf
Ultra High Frequency (200 MHz to 3000 MHz)
enumeration
Vhf8_33Spacing
Very High Frequency Communication Channel for 8.33kHz spacing
<xs:simpleType name="FrequencyUnits"><xs:annotation><xs:documentation>The Frequency Units field will designate the frequency spectrum area for the frequency in the Communication Frequency (Section 5.103) field as indicated in the table or will designate the content of the Communication Frequency field as a channel. For VHF based units, the field will also designate the established frequency spacing required of the frequency for unambiguous use.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="LowFreq"><xs:annotation><xs:documentation>Low Frequency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MediumFreq"><xs:annotation><xs:documentation>Medium Frequency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HighFreq"><xs:annotation><xs:documentation>High Frequency(3000 kHz to 30,000 kHz)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Vhf100kHzSpacing"><xs:annotation><xs:documentation>Very High Frequency 100 kHz spacing</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Vhf50kHzSpacing"><xs:annotation><xs:documentation>Very High Frequency 50 kHz spacing</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Vhf25kHzSpacing"><xs:annotation><xs:documentation>Very High Frequency 25 kHz spacing</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VhfNonStandard"><xs:annotation><xs:documentation>Very High Frequency (30,000 kHz to 200 MHz) Non-standard spacing</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Uhf"><xs:annotation><xs:documentation>Ultra High Frequency (200 MHz to 3000 MHz)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Vhf8_33Spacing"><xs:annotation><xs:documentation>Very High Frequency Communication Channel for 8.33kHz spacing</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DigitalService"><xs:annotation><xs:documentation>Digital Service</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Radar field indicates whether or not the communication unit identified in the record has access to and uses information derived from primary or secondary radars while performing the communication service indicated by the Communication Type. It is not an indication of an operational radar frequency.
Diagram
Type
restriction of xs:string
Facets
enumeration
PrimaryOrSecondary
Primary or secondary Radar information is available to the service
enumeration
No
If the Service documentation specifically states that the service does not have access to primary or secondary radar information
enumeration
Unknown
If the Source documentation does not provide details on the radar information access for the services
<xs:simpleType name="Radar"><xs:annotation><xs:documentation>The Radar field indicates whether or not the communication unit identified in the record has access to and uses information derived from primary or secondary radars while performing the communication service indicated by the Communication Type. It is not an indication of an operational radar frequency.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="PrimaryOrSecondary"><xs:annotation><xs:documentation>Primary or secondary Radar information is available to the service</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="No"><xs:annotation><xs:documentation>If the Service documentation specifically states that the service does not have access to primary or secondary radar information</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unknown"><xs:annotation><xs:documentation>If the Source documentation does not provide details on the radar information access for the services</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “24H Indicator” field is used to indicate whether a communication service frequency is available for use on a continual, i.e. 24 hours a day, seven days a week, basis or not.
<xs:simpleType name="H24Indicator"><xs:annotation><xs:documentation>The “24H Indicator” field is used to indicate whether a communication service frequency is available for use on a continual, i.e. 24 hours a day, seven days a week, basis or not.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Continious"><xs:annotation><xs:documentation>Frequency is continually available,</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotContinious"><xs:annotation><xs:documentation>Frequency is not continually available,</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unknown"><xs:annotation><xs:documentation>Unknown</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="Modulation"><xs:annotation><xs:documentation>The Modulation field will design the type of modulation for the frequency in the Communication Frequency (5.103) field.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AmFreq"><xs:annotation><xs:documentation>Amplitude Modulated Frequency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FmFreq"><xs:annotation><xs:documentation>Frequency Modulated Frequency</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
High Frequency (HF) signals used in aeronautical communications can be the complete signal or a portion of the signal, called a sideband. The Signal Emission field will designate for each HF Frequency what emission is used.
<xs:simpleType name="SignalEmission"><xs:annotation><xs:documentation>High Frequency (HF) signals used in aeronautical communications can be the complete signal or a portion of the signal, called a sideband. The Signal Emission field will designate for each HF Frequency what emission is used.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="A3"><xs:annotation><xs:documentation>Double Sideband (A3)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="A3a"><xs:annotation><xs:documentation>Single sideband, reduced carrier (A3A)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="A3b"><xs:annotation><xs:documentation>Two Independent sidebands (A3B)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="A3h"><xs:annotation><xs:documentation>Single sideband, full carrier (A3H)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="A3j"><xs:annotation><xs:documentation>Single sideband, suppressed carrier (A3J)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LsbCarrierUnk"><xs:annotation><xs:documentation>Lower (single) sideband, carrier unknown</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="UsbCarrierUnk"><xs:annotation><xs:documentation>Upper (single) sideband, carrier unknow</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="CommunicationDetails"><xs:annotation><xs:documentation>The Communication Details record contains the fields used in Communication Continuation Records.</xs:documentation></xs:annotation><xs:sequence><xs:element name="remoteFacility" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Remote Facility” field is used to identify a Navaid or Airport that has been used to provide the latitude/longitude of a communication transmitter, Figure 5-8 and Notes 7 and 8 in Section 5.37 of this Specification.</xs:documentation></xs:annotation></xs:element><xs:element name="timesOfOperation" type="type:TimesOfOperation" minOccurs="0" maxOccurs="1"/><xs:element name="transmitterSiteElevation" type="type:FacilityElevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Facility Elevation” field provides the elevation of navaids and communication transmitters</xs:documentation></xs:annotation></xs:element><xs:element name="transmitterSiteMagVar" type="type:MagneticVariation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Variation” field specifies the angular difference between True North and Magnetic North at the location defined in the record. “Dynamic Magnetic Variation” is a computer model derived value and takes location and date into consideration. For the “Station Declination” used in some record types, refer to Section 5.66.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="TimesOfOperation"><xs:annotation><xs:documentation>Used on airspace, flight planning, communications, and preferred route records to specify the times of operations of those entities.</xs:documentation></xs:annotation><xs:sequence><xs:element name="timeCode" type="enum:TimeCode" minOccurs="1" maxOccurs="1"/><xs:element name="times" type="type:TimeOfOperationInterval" minOccurs="0" maxOccurs="unbounded"/><xs:element name="timeNarrative" type="xs:string" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Time Narrative” field is used to provide Time of Operations and/or Conditions of Operations in a narrative form when source information is too complex to be formatted in accordance with ARINC 424 Section 5.195. This field is used in conjunction with the TimeCode value "Complex". This field is used on Airport, Heliport, and Enroute Communication Continuation records.</xs:documentation></xs:annotation></xs:element><xs:element name="byNotam" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Restrictive Airspace areas and communications facilities may not have established active times and are activated by NOTAM only or may be active by NOTAM in addition to established times. If this field is "True", the area or communcations facility is active by NOTAM in addition to the specified time intervals. If the the area or communication facility is active by NOTAM only, this field should not be used and the timeCode "ByNotam" should be used. Used on Controlled and Restrictive Airspace Primary and Continuation records, and Airport, Heliport and Enroute Communications Continuation records.</xs:documentation></xs:annotation></xs:element><xs:element name="adjustForDST" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Indicates that the "times" instances in this record follow daylight saving time in accordance with the local DST calendar. (See documentation for the "time" field in the StartOrEndTime records.)</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="TimeCode"><xs:annotation><xs:documentation>“Time Code” is used in a Time of Operations Record to indicate how to interpret the other fields in Time of Operations records.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="ContinuousIncludingHolidays"><xs:annotation><xs:documentation>Active Continuously, including holidays</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ContinuousExcludingHolidays"><xs:annotation><xs:documentation>Active Continuously, excluding holidays</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SpecifiedExcludingHolidays"><xs:annotation><xs:documentation>Active times are provided in Time of Operation record and exclude holidays</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SpecifiedIncludingHolidays"><xs:annotation><xs:documentation>Active times are provided in Time of Operation record and include holidays</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Complex"><xs:annotation><xs:documentation>Activation Times are too complex for Time of Operation format and are provided in the timeNarrative field</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ByNotam"><xs:annotation><xs:documentation>Active times announced by NOTAM</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unspecified"><xs:annotation><xs:documentation>Active times are not specified in source documentation</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="TimeOfOperationInterval"><xs:annotation><xs:documentation>The “Time of Operation” field is used to indicate the times of operation of a Facility or Restriction (See ARINC 424 5.195).</xs:documentation></xs:annotation><xs:sequence><xs:element name="dayOfWeek" type="enum:DayOfWeek" minOccurs="0" maxOccurs="7"><xs:annotation><xs:documentation>This field supports specifying the same time interval on multiple days of the week in a single interval instance. It should not be used if the "dayOfWeek" in the start and end times is specified (see documentation for StartOrEndTime). If this field is used, and the "end" time is earlier than the "start" time, the time interval crosses midnight (00:00).</xs:documentation><!-- TIMEX: How to indicate an interval that rolls past midnight --></xs:annotation></xs:element><xs:element name="start" type="type:StartOrEndTime" minOccurs="1" maxOccurs="1"/><xs:element name="end" type="type:StartOrEndTime" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="StartOrEndTime"><xs:sequence><xs:element name="dayOfWeek" type="enum:DayOfWeek" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field supports specifying a continuous time interval across multiple days. It should not be used if the "dayOfWeek" in TimeOfOperationInterval is specified. If used, it should be specified for both start and end times, and they should be different otherwise the TimeOfOperationInterval field should be used.</xs:documentation></xs:annotation></xs:element><xs:element name="time" type="xs:time" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field represents the start or end time of the TimeOfOperationInterval. A timezone may be set for this field, in which case the time is specified in the local timezone. If no timezone is set, UTC is assumed. If a timezone is set indicating a local time, it should be the same for both start and end times, and the "adjustForDST" field in the enclosing TimesOfOperation instance may be set to indicate that the time follows daylight saving time in accordance with the local DST calendar.</xs:documentation></xs:annotation></xs:element><xs:element name="relativeTimeIndicator" type="enum:RelativeTimeIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field supports specifying the StartOrEndTime as an offset from sunrise or sunset. In this case, the "time" field is just the offset amount such as 01:00:00 or 00:30:00. If used, there should be no timezone set in the "time" field.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="RelativeTimeIndicator"><xs:annotation><xs:documentation>Indicates that the start or end time is relative to sunset or sunrise.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="BeforeSunrise"/><xs:enumeration value="AfterSunrise"/><xs:enumeration value="BeforeSunset"/><xs:enumeration value="AfterSunset"/></xs:restriction></xs:simpleType>
<xs:simpleType name="FacilityElevation"><xs:annotation><xs:documentation>The “Facility Elevation” field provides the elevation of navaids and communication transmitters</xs:documentation></xs:annotation><xs:restriction base="xs:int"/></xs:simpleType>
The “Communication Distance” field is used to define the distance restriction a communication frequency is to be used within or beyond when such restrictions apply. This field is used in conjunction with the Distance Description field.
<xs:simpleType name="CommunicationDistance"><xs:annotation><xs:documentation>The “Communication Distance” field is used to define the distance restriction a communication frequency is to be used within or beyond when such restrictions apply. This field is used in conjunction with the Distance Description field.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="2"/></xs:restriction></xs:simpleType>
The “Distance Description” field will designate whether a communication frequency is to be used from the facility out to a specified distance or from a specified distance and beyond in the Airport Communication Record. In the VHF Navaid Limitation Continuation Record, the field is used to define whether the limitation applies from the navaid out to a specified distance or from a specified distance and beyond.
Diagram
Type
restriction of xs:string
Facets
enumeration
OutToSpecifiedDistance
The communication frequency or navaid limitation is out to a specified distance.
enumeration
AppliesBeyondDistance
The communication frequency is used or the navaid limitation applies beyond a specified distance
<xs:simpleType name="DistanceDescription"><xs:annotation><xs:documentation>The “Distance Description” field will designate whether a communication frequency is to be used from the facility out to a specified distance or from a specified distance and beyond in the Airport Communication Record. In the VHF Navaid Limitation Continuation Record, the field is used to define whether the limitation applies from the navaid out to a specified distance or from a specified distance and beyond.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="OutToSpecifiedDistance"><xs:annotation><xs:documentation>The communication frequency or navaid limitation is out to a specified distance.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AppliesBeyondDistance"><xs:annotation><xs:documentation>The communication frequency is used or the navaid limitation applies beyond a specified distance</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NoRestriction"><xs:annotation><xs:documentation>no restrictions/limitations apply</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Multi-Sector Indicator field is used to indicate that the communication service and frequency are used in more than one defined sector. The actual sector data will be contained in the primary and continuation records of the affected airport or heliport communication record set.
Diagram
Type
restriction of xs:string
Facets
enumeration
MultiSector
Multi-sector data is published in official government source for the service and frequency
enumeration
NotDefined
There is no defined sector data published for the service and frequency.
enumeration
OnlyOneFromSource
The official government source has provided only a single defined sector for the service and frequency
<xs:simpleType name="MultiSectorIndicator"><xs:annotation><xs:documentation>The Multi-Sector Indicator field is used to indicate that the communication service and frequency are used in more than one defined sector. The actual sector data will be contained in the primary and continuation records of the affected airport or heliport communication record set.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="MultiSector"><xs:annotation><xs:documentation>Multi-sector data is published in official government source for the service and frequency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotDefined"><xs:annotation><xs:documentation>There is no defined sector data published for the service and frequency.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OnlyOneFromSource"><xs:annotation><xs:documentation>The official government source has provided only a single defined sector for the service and frequency</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Sectorization Narrative” field is used to define sectors of operations for communications services on specific frequencies in a narrative format when that data cannot be formatted in the Sectorization (5.183) field. The field may also be used to qualify the Sectorization information. This is usually the “and” situation, meaning the communications service/frequency is to be used in the defined sector and in some other defined situation that cannot be formatted such as Sectorization An example is “309127” in the Sectorization field and “When Departing Runway 31L/R” in the Narrative field.
<xs:simpleType name="SectorizationNarrative"><xs:annotation><xs:documentation>The “Sectorization Narrative” field is used to define sectors of operations for communications services on specific frequencies in a narrative format when that data cannot be formatted in the Sectorization (5.183) field. The field may also be used to qualify the Sectorization information. This is usually the “and” situation, meaning the communications service/frequency is to be used in the defined sector and in some other defined situation that cannot be formatted such as Sectorization An example is “309127” in the Sectorization field and “When Departing Runway 31L/R” in the Narrative field.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="60"/></xs:restriction></xs:simpleType>
The “Sectorization” field is used to define the airspace sector a communication frequency is applicable for when an airport defines sectors by bearing from the same point.
<xs:simpleType name="Sectorization"><xs:annotation><xs:documentation>The “Sectorization” field is used to define the airspace sector a communication frequency is applicable for when an airport defines sectors by bearing from the same point.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="6"/></xs:restriction></xs:simpleType>
<xs:complexType name="AirportHeliportCommunicationServiceIndicator"><xs:annotation><xs:documentation>The “Service Indicator” field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:sequence><xs:element name="serviceIndicatorAirportHeliportFrequency" type="enum:ServiceIndicatorAirportHeliportFrequency" minOccurs="0" maxOccurs="1"/><xs:element name="serviceIndicatorAirportHeliportInformation" type="enum:ServiceIndicatorAirportHeliportInformation" minOccurs="0" maxOccurs="1"/><xs:element name="serviceIndicatorAirportHeliportService" type="enum:ServiceIndicatorAirportHeliportService" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="ServiceIndicatorAirportHeliportFrequency"><xs:annotation><xs:documentation>The Service Indicator field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="ATF"><xs:annotation><xs:documentation>Aerodrome Traffic Frequency (ATF)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CTAF"><xs:annotation><xs:documentation>Common Traffic Advisory Frequency (CTAF)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MF"><xs:annotation><xs:documentation>Mandatory Frequency (MF)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SF"><xs:annotation><xs:documentation>Secondary Frequency</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ServiceIndicatorAirportHeliportInformation"><xs:annotation><xs:documentation>The Service Indicator field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="VDF"><xs:annotation><xs:documentation>VHF Direction Finding Service (VDF)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotEnglish"><xs:annotation><xs:documentation>Language other than English</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MilitaryUseFreq"><xs:annotation><xs:documentation>Military Use Frequency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PCL"><xs:annotation><xs:documentation>Pilot Controlled Light (PCL)</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ServiceIndicatorAirportHeliportService"><xs:annotation><xs:documentation>The Service Indicator field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AAS"><xs:annotation><xs:documentation>Airport Advisory Service (AAS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CARC"><xs:annotation><xs:documentation>Community Aerodrome Radio Station (CARS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DepartureService"><xs:annotation><xs:documentation>Departure Service (Other than Departure Control Unit)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FIS"><xs:annotation><xs:documentation>Flight Information Service (FIS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="IC"><xs:annotation><xs:documentation>Initial Contact (IC)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ArrivalService"><xs:annotation><xs:documentation>Arrival Service (Other than Arrival Control Unit)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AFIS"><xs:annotation><xs:documentation>Aerodrome Flight Information Service(AFIS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TerminalAeraControl"><xs:annotation><xs:documentation>Terminal Area Control (Other than dedicated Terminal Control Unit)</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="AdditionalSectorization"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for an Additional Sectorization used in Airport Communications.</xs:documentation></xs:annotation><xs:sequence><xs:element name="additionalSectorizationAltitude1" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="additionalSectorizationAltitude2" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="additionalSectorizationAltitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="Helipad"><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="padDimensionX" type="xs:int" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the X dimension of a rectanglular pad.</xs:documentation></xs:annotation></xs:element><xs:element name="padDimensionY" type="xs:int" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element is the Y dimension of a rectanglular pad.</xs:documentation></xs:annotation></xs:element><xs:element name="padRadius" type="xs:int" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the pad radius if it is not a square or rectangle</xs:documentation></xs:annotation></xs:element><xs:element maxOccurs="1" minOccurs="0" name="helipadShape" type="enum:HelipadShape"><xs:annotation><xs:documentation>This element provides the shape of the helipad.</xs:documentation></xs:annotation></xs:element><xs:element maxOccurs="1" minOccurs="0" name="maximumHelicopterWeight" type="type:MaxHelicopterWeight"><xs:annotation><xs:documentation>This element provides the maximum weight for helicopters using this helipad.</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="helicopterPerformanceReq" type="enum:HelicopterPerformanceReq"><xs:annotation><xs:documentation>This element provides performance requirements for helicopters using this helipad.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The Helipad Shape field defines the geometric shape of a helipad as being either circle, or rectangular. If the object is a runway the port contains runway elements.
<xs:simpleType name="HelipadShape"><xs:annotation><xs:documentation>The Helipad Shape field defines the geometric shape of a helipad as being either circle, or rectangular. If the object is a runway the port contains runway elements.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Circle"/><xs:enumeration value="SqureAndOrRectangle"/><xs:enumeration value="Undefined"/></xs:restriction></xs:simpleType>
<xs:simpleType name="MaxHelicopterWeight"><xs:annotation><xs:documentation>The Maximum Allowable Helicopter Weight represents the maximum weight, expressed in hundreds of pounds, that a helipad or FATO can support</xs:documentation></xs:annotation><xs:restriction base="xs:int"><xs:maxInclusive value="999"/><xs:minInclusive value="0"/></xs:restriction></xs:simpleType>
<xs:simpleType name="HelicopterPerformanceReq"><xs:annotation><xs:documentation>The Helipad Performance Requirement is used to identify any restriction imposed on helicopter performance in order to use a given helipad.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="MultiEngine"/><xs:enumeration value="SingleEngineOnly"/><xs:enumeration value="Unkown"/></xs:restriction></xs:simpleType>
<xs:complexType name="AirportHeliportLocalizerMarker"><xs:annotation><xs:documentation>The Airport and Heliport Localizer Marker File (PM) contains details of all markers and locators associated with all types of localizers.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="elevation" type="type:Elevation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Facility Elevation field provides the elevation of navaids and communication transmitters.</xs:documentation></xs:annotation></xs:element><xs:element name="localizerReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/MLS/GLS Identifier” field identifies the localizer, MLS facility or GLS Ref Path defined in the record. In the Runway Record, two “Landing Systems” may be defined.</xs:documentation></xs:annotation></xs:element><xs:element name="locatorClass" type="LocatorClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.</xs:documentation></xs:annotation></xs:element><xs:element name="locatorFacilityCharacteristics" type="xs:string" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Facility Characteristics” field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation></xs:element><xs:element name="locatorFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “VOR/NDB Frequency” field specifies the frequency of the NAVAID identified in the “VOR/NDB Identifier” field of the record.</xs:documentation></xs:annotation></xs:element><xs:element name="markerType" type="enum:MarkerType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Marker Type” field defines the type of marker.</xs:documentation></xs:annotation></xs:element><xs:element name="minorAxisBearing" type="type:MinorAxisBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Minor Axis Bearing” field indicates the true bearing of the minor axis of marker beacons.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayIdentifier" type="type:RunwayIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Identifier” fieldidentifies the runways described in runway records andrunways served by the ILS/MLS described in ILS/MLSrecords.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="AhLocalizerMarkerLocatorFacility1"><xs:annotation><xs:documentation>The field NDBNavaidFacility1 is the first character of the 5 character Navaid class,when used in NDB Navaid Record –NDBs and Terminal NDBs.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Ndb"><xs:annotation><xs:documentation>NDB</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Sabh"><xs:annotation><xs:documentation>SABH</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MarineBeacon"><xs:annotation><xs:documentation>Marine Beacon.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The field NDBNavaidAddInfo is the fourth character of the 5 character Navaid class, when used in NDB Navaid Record –NDBs and Terminal NDBs. It contains additional information on the Navaid.
Diagram
Type
restriction of xs:string
Facets
enumeration
NoVoiceOnFrequency
No Voice on Frequency.The frequency of this Navaid is not used to support two-way communication between a ground station and aircraft.
enumeration
VoiceOnFrequency
Voice on Frequency.The frequency of this Navaid is used to support two-way communication between a ground station and aircraft.
<xs:simpleType name="AhLocalizerMarkerLocatorAddInfo"><xs:annotation><xs:documentation>The field NDBNavaidAddInfo is the fourth character of the 5 character Navaid class, when used in NDB Navaid Record –NDBs and Terminal NDBs. It contains additional information on the Navaid.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="NoVoiceOnFrequency"><xs:annotation><xs:documentation>No Voice on Frequency.The frequency of this Navaid is not used to support two-way communication between a ground station and aircraft.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VoiceOnFrequency"><xs:annotation><xs:documentation>Voice on Frequency.The frequency of this Navaid is used to support two-way communication between a ground station and aircraft.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
Simple Type enum:AhLocalizerMarkerLocatorCollocation
Namespace
http://www.arinc424.com/xml/enumerations
Annotations
The field NDBNavaidCollocation is the fifth character of the 5 character Navaid class, when used in NDB Navaid Record –NDBs and Terminal NDBs. It contains additional information on the Navaid. It has information on the Navaid collocation.
Diagram
Type
restriction of xs:string
Facets
enumeration
BfoOperation
BFO Operation. Use of Beat Frequency Oscillator type of equipment is required to received an aural identification signal.
enumeration
LocatorMarkerCollocated
Locator/Marker Collocated. The latitude/longitude position of the Locator and Marker are identical.
enumeration
LocatorMiddleMarkerNotCollocated
Locator/Middle Marker Not Collocated. The latitude/longitude position of Locator and Marker are not identical.
<xs:simpleType name="AhLocalizerMarkerLocatorCollocation"><xs:annotation><xs:documentation>The field NDBNavaidCollocation is the fifth character of the 5 character Navaid class, when used in NDB Navaid Record –NDBs and Terminal NDBs. It contains additional information on the Navaid. It has information on the Navaid collocation.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="BfoOperation"><xs:annotation><xs:documentation>BFO Operation. Use of Beat Frequency Oscillator type of equipment is required to received an aural identification signal.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LocatorMarkerCollocated"><xs:annotation><xs:documentation>Locator/Marker Collocated. The latitude/longitude position of the Locator and Marker are identical.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LocatorMiddleMarkerNotCollocated"><xs:annotation><xs:documentation>Locator/Middle Marker Not Collocated. The latitude/longitude position of Locator and Marker are not identical.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="AhLocalizerMarkerLocatorCoverage"><xs:annotation><xs:documentation>The field NDBNavaidCoverage is the first character of the 5 character Navaid class, When used in NDB Navaid Record –NDBs and Terminal NDBs.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="HighPowerNdb"><xs:annotation><xs:documentation>High-powered NDB. Generally usable within 75NM of the facility at all altitudes.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Ndb"><xs:annotation><xs:documentation>NDB. Generally usable within 50NM of the facility at all altitude.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LowPowerNdb"><xs:annotation><xs:documentation>Low-powered NDB. Generally usable within 25NM of the facility at all altitude.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Locator"><xs:annotation><xs:documentation>Locator. Generally usable within 15NM of the facility at all altitudes.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="AhLocalizerMarkerLocatorFacility2"><xs:annotation><xs:documentation>The field NDBNavaidFacility2 is the second character of the 5 character Navaid class, when used in NDB Navaid Record –NDBs and Terminal NDBs.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="InnerMarker"><xs:annotation><xs:documentation>Inner Marker. There is an Inner Marker beacon at this location.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MiddleMarker"><xs:annotation><xs:documentation>Middle Marker. There is a Middle Marker beacon at this location.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OuterMarker"><xs:annotation><xs:documentation>Outer Marker. There is an Outer Marker beacon at this location.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="BackMarker"><xs:annotation><xs:documentation>Back Marker. There is a Backcourse Marker at this location.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="MarkerType"><xs:annotation><xs:documentation>The “Marker Type” field defines the type of marker.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="IM"><xs:annotation><xs:documentation>Inner Marker</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MM"><xs:annotation><xs:documentation>Middle Marker</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OM"><xs:annotation><xs:documentation>Outer Marker</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="BM"><xs:annotation><xs:documentation>Back Marker</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="L"><xs:annotation><xs:documentation>Locator at Marker</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="MinorAxisBearing"><xs:annotation><xs:documentation>The “Minor Axis Bearing” field indicates the true bearing of the minor axis of marker beacons.</xs:documentation></xs:annotation><xs:restriction base="type:BearingValue"/></xs:simpleType>
<xs:complexType name="LocalizerGlideslope"><xs:annotation><xs:documentation>This following record contains the fields used in Localizer and Glideslope Records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="PrecisionApproachNavaid"><xs:sequence><xs:element name="approachRouteIdent" type="type:CoreIdentifier" minOccurs="0" maxOccurs="4"><xs:annotation><xs:documentation>The “Approach Route Identifier” field contains the identifier of the approach route to be flown. To facilitate the provision of multiple approach procedures of the same type to a given runway, the field also is used to provide a “multiple indicator.”</xs:documentation></xs:annotation></xs:element><xs:element name="glideslopeBeamWidth" type="type:GlideslopeBeamWidth" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Glide Slope Beam Width” field specifies the glide path beam width of the Glide Slope defined in the record.</xs:documentation></xs:annotation></xs:element><xs:element name="glideslopeHeightAtLandingThreshold" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element><xs:element name="glideslopeLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element><xs:element name="glideslopePosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"/><xs:element name="localizerPosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"/><xs:element name="localizerPositionReference" type="enum:LocalizerAzimuthPositionReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Element which encapsulates the localizer details for the corresponding Runway. This element contains the localizer ident and localizer class.</xs:documentation></xs:annotation></xs:element><xs:element name="localizerTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element><xs:element name="localizerTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element><xs:element name="localizerWidth" type="xs:decimal" minOccurs="0" maxOccurs="1"/><xs:element name="stationDeclination" type="type:StationDeclination" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.</xs:documentation></xs:annotation></xs:element><xs:element name="supportingFacilityReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “VOR/NDB Identifier” field identifies the VHF/MF/LF facility defined in the record.</xs:documentation></xs:annotation></xs:element><xs:element name="localizerGlideslopeFrequency" type="type:Frequency" minOccurs="1" maxOccurs="1"/><xs:element name="ilsBackCourse" type="enum:ILSBackCourse" minOccurs="0" maxOccurs="1"/><xs:element name="ilsDmeLocation" type="enum:ILSDMELocation" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="PrecisionApproachNavaid" abstract="true"><xs:complexContent><xs:extension base="Navaid"><xs:sequence><xs:element name="approachAngle" type="type:PrecisionApproachAngle" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Glide Slope Angle” field defines the glide slope angle of an ILS facility/GLS approach. The “Minimum Elevation Angle” field defines the lowest elevation angle authorized for the MLS procedure.</xs:documentation></xs:annotation></xs:element><xs:element name="approachCourseBearing" type="type:Bearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer Bearing” field defines the magnetic bearing of the localizer course of the ILS facility/GLS approach described in the record. The “MLS Azimuth Bearing” and the “MLS Back Azimuth Bearing” fields define the inbound magnetic final approach course assigned to the center of the Azimuth or Back Azimuth Coverage (see Section 6.172).</xs:documentation></xs:annotation></xs:element><xs:element name="category" type="enum:PrecisionApproachCategory" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Localizer/MLS/GLS Performance Categories have established operating minimums and are listed as Category I, II, and III. The level of Performance Category does not imply that permission exists to use the facility for landing guidance to that level and does not limit minimal using designated classification. This field is also used to define the classification, non- ILS/MLS/GLS, and localizer installation such as IGS, LDA, or SDF. As used in the runway record, there are two fields, one labeled Localizer/MLS/GLS Category/Classification and the other labeled Second Localizer/MLS/GLS Category/Classification.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayIdentifier" type="type:RunwayIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Identifier” field identifies the runways described in runway records and runways served by the ILS/MLS described in ILS/MLSrecords.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayReference" type="type:PointReference" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Glide Slope Angle” field defines the glide slope angle of an ILS facility/GLS approach. The “Minimum Elevation Angle” field defines the lowest elevation angle authorized for the MLS procedure.
<xs:simpleType name="PrecisionApproachAngle"><xs:annotation><xs:documentation>The “Glide Slope Angle” field defines the glide slope angle of an ILS facility/GLS approach. The “Minimum Elevation Angle” field defines the lowest elevation angle authorized for the MLS procedure.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"/></xs:simpleType>
The Localizer/MLS/GLS Performance Categories have established operating minimums and are listed as Category I, II, and III. The level of Performance Category does not imply that permission exists to use the facility for landing guidance to that level and does not limit minimal using designated classification. This field is also used to define the classification, non- ILS/MLS/GLS, and localizer installation such as IGS, LDA, or SDF. As used in the runway record, there are two fields, one labeled Localizer/MLS/GLS Category/Classification and the other labeled Second Localizer/MLS/GLS Category/Classification.
<xs:simpleType name="PrecisionApproachCategory"><xs:annotation><xs:documentation>The Localizer/MLS/GLS Performance Categories have established operating minimums and are listed as Category I, II, and III. The level of Performance Category does not imply that permission exists to use the facility for landing guidance to that level and does not limit minimal using designated classification. This field is also used to define the classification, non- ILS/MLS/GLS, and localizer installation such as IGS, LDA, or SDF. As used in the runway record, there are two fields, one labeled Localizer/MLS/GLS Category/Classification and the other labeled Second Localizer/MLS/GLS Category/Classification.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="IlsLocOnly"><xs:annotation><xs:documentation>ILS Localizer Only, No Glideslope</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="IlsMlsGlsCat1"><xs:annotation><xs:documentation>ILS Localizer/MLS/GLS Category I</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="IlsMlsGlsCat2"><xs:annotation><xs:documentation>ILS Localizer/MLS/GLS Category II</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="IlsMlsGlsCat3"><xs:annotation><xs:documentation>ILS Localizer/MLS/GLS Category III</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Igs"><xs:annotation><xs:documentation>IGS Facility</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LdaGlideslope"><xs:annotation><xs:documentation>LDA Facility with Glideslope</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LdaNoGlideslope"><xs:annotation><xs:documentation>LDA Facility, no Glideslope</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SdfGlideslope"><xs:annotation><xs:documentation>SDF Facility with Glideslope</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SdfNoGlideSlope"><xs:annotation><xs:documentation>SDF Facility, no Glideslope</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="GlideslopeBeamWidth"><xs:annotation><xs:documentation>The “Glide Slope Beam Width” field specifies the glide path beam width of the Glide Slope defined in the record.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"/></xs:simpleType>
<xs:simpleType name="BeamPosition"><xs:annotation><xs:documentation>The Beam Position” field defines the location of the facility antenna relative to one end of the runway or threshold.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="4"/></xs:restriction></xs:simpleType>
Simple Type enum:LocalizerAzimuthPositionReference
Namespace
http://www.arinc424.com/xml/enumerations
Annotations
The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.
Diagram
Type
restriction of xs:string
Facets
enumeration
BeyondStopEnd
For Localizer and Azimuth positions the field is blank (@) when the antenna is situated beyond the stop end of the runway,For Back Azimuth positions the field is blank (@) when the antenna is situated ahead of the approach end of the runway
enumeration
BeforeApproachEnd
For Localizer and Azimuth positions the field contains a plus (+) sign when the antenna is situated ahead of the approach end of the runwayFor Back Azimuth positions the field contains a plus (+) sign when the antenna is situated beyond the stop end of the runway
enumeration
OffToSide
For Localizer and Azimuth positions the field contains a plus (-) sign when the antenna is located off to one side of the runwayFor Back Azimuth positions the field contains a plus (-) sign when it is located off to one side of the runway.
<xs:simpleType name="LocalizerAzimuthPositionReference"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="BeyondStopEnd"><xs:annotation><xs:documentation>For Localizer and Azimuth positions the field is blank (@) when the antenna is situated beyond the stop end of the runway, For Back Azimuth positions the field is blank (@) when the antenna is situated ahead of the approach end of the runway</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="BeforeApproachEnd"><xs:annotation><xs:documentation>For Localizer and Azimuth positions the field contains a plus (+) sign when the antenna is situated ahead of the approach end of the runway For Back Azimuth positions the field contains a plus (+) sign when the antenna is situated beyond the stop end of the runway</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OffToSide"><xs:annotation><xs:documentation>For Localizer and Azimuth positions the field contains a plus (-) sign when the antenna is located off to one side of the runway For Back Azimuth positions the field contains a plus (-) sign when it is located off to one side of the runway.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.
<xs:simpleType name="TrueBearing"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation><xs:restriction base="type:CompassValue"><xs:totalDigits value="5"/><xs:fractionDigits value="2"/></xs:restriction></xs:simpleType>
<xs:simpleType name="TrueBearingSource"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Official"><xs:annotation><xs:documentation>“True Bearing” is derived from official government sources.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Other"><xs:annotation><xs:documentation>“True Bearing" is derived from other sources</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.
<xs:complexType name="StationDeclination"><xs:annotation><xs:documentation>For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.</xs:documentation></xs:annotation><xs:sequence><xs:element name="stationDeclinationEWT" type="enum:StationDeclinationEWT" minOccurs="1" maxOccurs="1"/><xs:element name="stationDeclinationValue" type="type:MagneticVariationValue" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
For VHF NAVAIDS, the Station Declination field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.
Diagram
Type
restriction of xs:string
Facets
enumeration
East
Declination is East of True North
enumeration
West
Declination is East of West North
enumeration
True
Station is oriented to True North in an area in which the local variation is not zero.
<xs:simpleType name="StationDeclinationEWT"><xs:annotation><xs:documentation>For VHF NAVAIDS, the Station Declination field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="East"><xs:annotation><xs:documentation>Declination is East of True North</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="West"><xs:annotation><xs:documentation>Declination is East of West North</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="True"><xs:annotation><xs:documentation>Station is oriented to True North in an area in which the local variation is not zero.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Grid"><xs:annotation><xs:documentation>Station is oriented to Grid North</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ILSBackCourse"><xs:annotation><xs:documentation>The Facility Characteristics field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Usable"><xs:annotation><xs:documentation>Usable</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unusable"><xs:annotation><xs:documentation>Unusable</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Restricted"><xs:annotation><xs:documentation>Restricted</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Undefined"><xs:annotation><xs:documentation>Undefined</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ILSDMELocation"><xs:annotation><xs:documentation>The “ILSDMELocation” field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="NotCollocated"><xs:annotation><xs:documentation>Not collocated with Localizer or Glide Slope</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CollocatedLocalizer"><xs:annotation><xs:documentation>Collocated with localizer</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CollocatedGlideSlope"><xs:annotation><xs:documentation>Collocated with Glide Slope</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
This record contains a sequential listing of all GNSS Landing Systems (GLS) approaches, including the slope, course and reference path idents of the GLS approach. A GLS approach is identified by its ident and channel. Note that several GLS approaches can be supported by a single differential GLS ground station.
<xs:complexType name="GLS"><xs:annotation><xs:documentation>This record contains a sequential listing of all GNSS Landing Systems (GLS) approaches, including the slope, course and reference path idents of the GLS approach. A GLS approach is identified by its ident and channel. Note that several GLS approaches can be supported by a single differential GLS ground station.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="PrecisionApproachNavaid"><xs:sequence><xs:element name="serviceVolumneRadius" type="type:ServiceVolumeRadius" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The service volume radius identifies the radius of the service volume around the transmitter in Nautical miles.</xs:documentation></xs:annotation></xs:element><xs:element name="stationElevationWGS84" type="type:StationElevationWGS84" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field identifies the WGS84 elevation of the GLS ground station described in the record.</xs:documentation></xs:annotation></xs:element><xs:element name="stationType" type="type:StationType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The station type identifies the type of the differential ground station. The first character will be L for LAAS/GLS ground station, C for SCAT-1 station. The second and third character will be blank for the moment. They will indicate the interoperability standard to which the station conforms.</xs:documentation></xs:annotation></xs:element><xs:element name="tdmaSlots" type="type:TDMASlots" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The TDMA identifies the time slot(s) in which the ground station transmits the related approach. The high precision time source available through GPS permits utilization of Time division multiplexing or TDMA (Time Division Multiple Access), allowing multiple ground stations to share a common frequency by dividing it into eight time slots. An individual station may broadcast in one or more of eight slots.</xs:documentation></xs:annotation></xs:element><xs:element name="glsChannel" type="type:Channel" minOccurs="1" maxOccurs="1"/><xs:element maxOccurs="1" minOccurs="0" name="thresholdCrossingHeight" type="type:ThresholdCrossingHeight"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="ServiceVolumeRadius"><xs:annotation><xs:documentation>The service volume radius identifies the radius of the service volume around the transmitter in Nautical miles.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceIntegerNMTwoDigits"/></xs:simpleType>
<xs:simpleType name="StationElevationWGS84"><xs:annotation><xs:documentation>This field identifies the WGS84 elevation of the GLS ground station described in the record.</xs:documentation></xs:annotation><xs:restriction base="type:Elevation"/></xs:simpleType>
The station type identifies the type of the differential ground station. The first character will be L for LAAS/GLS ground station, C for SCAT-1 station. The second and third character will be blank for the moment. They will indicate the interoperability standard to which the station conforms.
<xs:simpleType name="StationType"><xs:annotation><xs:documentation>The station type identifies the type of the differential ground station. The first character will be L for LAAS/GLS ground station, C for SCAT-1 station. The second and third character will be blank for the moment. They will indicate the interoperability standard to which the station conforms.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="3"/></xs:restriction></xs:simpleType>
The TDMA identifies the time slot(s) in which the ground station transmits the related approach. The high precision time source available through GPS permits utilization of Time division multiplexing or TDMA (Time Division Multiple Access), allowing multiple ground stations to share a common frequency by dividing it into eight time slots. An individual station may broadcast in one or more of eight slots.
<xs:simpleType name="TDMASlots"><xs:annotation><xs:documentation>The TDMA identifies the time slot(s) in which the ground station transmits the related approach. The high precision time source available through GPS permits utilization of Time division multiplexing or TDMA (Time Division Multiple Access), allowing multiple ground stations to share a common frequency by dividing it into eight time slots. An individual station may broadcast in one or more of eight slots.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="2"/></xs:restriction></xs:simpleType>
<xs:complexType name="MLS"><xs:annotation><xs:documentation>This record represents a Microwave Landing System, including the Azimuth station, the Elevation station and the Back Azimuth station if installed.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="PrecisionApproachNavaid"><xs:sequence><xs:element name="azimuthCoverageLeft" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element><xs:element name="azimuthCoverageRight" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element><xs:element name="azimuthPosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position” field defines the location of the facility antenna relative to one end of the runway.</xs:documentation></xs:annotation></xs:element><xs:element name="azimuthPositionReference" type="enum:LocalizerAzimuthPositionReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.</xs:documentation></xs:annotation></xs:element><xs:element name="azimuthProportionalAngleLeft" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element><xs:element name="azimuthProportionalAngleRight" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element><xs:element name="elevationAngleSpan" type="type:ElevationAngleSpan" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Elevation Angle Span” field defines the scan of the elevation transmitter signal between the lower and upper limits</xs:documentation></xs:annotation></xs:element><xs:element name="elevationLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point's elevation component.</xs:documentation></xs:annotation></xs:element><xs:element name="elevationPosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Elevation Position” field defines the location of the antenna with respect to the approach end of the runway.</xs:documentation></xs:annotation></xs:element><xs:element name="mlsBackAzimuthDetails" type="MLSBackAzimuthDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>MLS Back Azimuth Details</xs:documentation></xs:annotation></xs:element><xs:element name="nominalElevationAngle" type="type:NominalElevationAngle" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Nominal Elevation Angle” field defines the normal glide path angle for the MLS installation.</xs:documentation></xs:annotation></xs:element><xs:element name="supportingFacilityReference" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “VOR/NDB Identifier” field identifies the VHF/MF/LF facility defined in the record.</xs:documentation></xs:annotation></xs:element><xs:element name="mlsChannel" type="type:Channel" minOccurs="1" maxOccurs="1"/><xs:element name="mlsDmeLocation" type="enum:MLSDMELocation" minOccurs="0" maxOccurs="1"/><xs:element name="mlsApproachAzimuthScanRate" type="enum:MLSApproachAzimuthScanRate" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.
<xs:simpleType name="AzimuthCoverageSectorRightLeft"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:maxExclusive value="360"/><xs:minInclusive value="0"/><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
Simple Type type:AzimuthProportionalAngleRightLeft
Namespace
http://www.arinc424.com/xml/datatypes
Annotations
The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.
<xs:simpleType name="AzimuthProportionalAngleRightLeft"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:maxExclusive value="360"/><xs:minInclusive value="0"/><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
<xs:simpleType name="ElevationAngleSpan"><xs:annotation><xs:documentation>The “Elevation Angle Span” field defines the scan of the elevation transmitter signal between the lower and upper limits</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:maxExclusive value="360"/><xs:minInclusive value="0"/><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
<xs:complexType name="MLSBackAzimuthDetails"><xs:annotation><xs:documentation>This following record contains the fields used in MLS Back Azimuth Details.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="azimuthTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element><xs:element name="azimuthTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthBearing" type="type:Bearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “MLS Azimuth Bearing” and the “MLS Back Azimuth Bearing” fields define the inbound magnetic final approach course assigned to the center of the Azimuth or Back Azimuth Coverage (see Section 6.172).</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthCoverageLeft" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthCoverageRight" type="type:AzimuthCoverageSectorRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Azimuth Coverage Sector” fields define the limit of the azimuth transmitter signal on the right and left side of the MLS Bearing (Section 6.167). The Back Azimuth Coverage Sector is identical to the Azimuth Coverage Sector and also provides guidance for Missed Approach Procedures and departures.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthPosition" type="type:BeamPosition" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position” field defines the location of the facility antenna relative to one end of the runway.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthPositionReference" type="enum:LocalizerAzimuthPositionReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Localizer/Azimuth Position Reference” field indicates whether the antenna is situated beyond the stop end of the runway, ahead of or beyond the approach end of the runway. The “Back Azimuth Position Reference” field indicates whether the antenna is situated ahead of the approach end of the runway, ahead of or beyond the stop end of the runway.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthProportionalSectorLeft" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthProportionalSectorRight" type="type:AzimuthProportionalAngleRightLeft" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The MLS Azimuth and Back Azimuth Proportional Angle fields define the limits of proportional guidance of the azimuth transmitter signal on the right and left side of the MLS Azimuth bearing (Section 6.167). The BAZ is identical to the AZ and also provides guidance for Missed Approach Procedures and departures. See figure under Section 6.172.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element><xs:element name="backAzimuthTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element><xs:element name="glidePathHeightAtLandingThreshold" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element><xs:element name="mlsDatumPointLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="NominalElevationAngle"><xs:annotation><xs:documentation>The “Nominal Elevation Angle” field defines the normal glide path angle for the MLS installation.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"/></xs:simpleType>
<xs:simpleType name="MLSDMELocation"><xs:annotation><xs:documentation>The Facility Characteristics field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="CollocatedAzimuth"><xs:annotation><xs:documentation>Collocated with Azimuth</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CollocatedElevation"><xs:annotation><xs:documentation>Collocated with Elevation.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotCollocated"><xs:annotation><xs:documentation>Not Collocated with Azimuth or Elevation</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="MLSApproachAzimuthScanRate"><xs:restriction base="xs:string"><xs:enumeration value="AzimuthNotAvailable"><xs:annotation><xs:documentation>Where a high-rate approach azimuth guidance is not available, enter blank.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AzimuthAvailable"><xs:annotation><xs:documentation>Where a high-rate approach azimuth guidance is available, enter “H,”</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="MSA"><xs:annotation><xs:documentation>The Minimum Sector Altitude (MSA) file contains details relating to available sector MSA Extension Class.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="centerFix" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When used on Airport and Heliport MSA Records, the “Center Fix” field represents the MSA Center; that point (Navaid or Waypoint) on which the MSA is predicated. When used on Terminal Procedure Records, it can be used in three ways: 1. When the terminal procedure has an MSA defined, the field will contain the identifier of the fix on which the MSA is predicated. This will serve as a pointer to the specific MSA (PS) Record. This will be populated on the Final Approach Fix (FAF) Record only. 2. When the terminal procedure has a TAA defined, the field will contain the identifier of the fix on which the TAA Sector is predicated. This will serve as a pointer to the specific TAA (PK) Record. This will be populated on the first record for each approach transition. 3. When used in a terminal procedure record defined by an “RF” Path Terminator, the field will contain the fix that defines the center of the constant rate turn. If the RF Leg terminates at the FAF, where the MSA Center Fix information would normally be found, the RF Center Fix takes priority and the MSA Center Fix pointer will be moved to the FACF record.</xs:documentation></xs:annotation></xs:element><xs:element name="icaoCode" type="type:IcaoCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ICAO Code” field permits records to be categorized geographically within the limits of the categorization performed by the “Area Code” field.</xs:documentation></xs:annotation></xs:element><xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element><xs:element name="multipleCode" type="type:MultipleCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Multiple Code” field will be used to indicate Restrictive Airspace Areas or MSA Centers having the same designator but subdivided or differently divided by lateral and/or vertical detail.</xs:documentation></xs:annotation></xs:element><xs:element name="sector" type="type:Sector" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class represents the details for a MSA Sector.</xs:documentation></xs:annotation></xs:element><xs:element name="centerFixRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/></xs:sequence><xs:attribute name="referenceID" use="required" type="xs:ID"/></xs:extension></xs:complexContent></xs:complexType>
The “Multiple Code” field will be used to indicate Restrictive Airspace Areas or MSA Centers having the same designator but subdivided or differently divided by lateral and/or vertical detail.
<xs:simpleType name="MultipleCode"><xs:annotation><xs:documentation>The “Multiple Code” field will be used to indicate Restrictive Airspace Areas or MSA Centers having the same designator but subdivided or differently divided by lateral and/or vertical detail.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="1"/></xs:restriction></xs:simpleType>
The Flight Planning Arrival/Departure Data Record (424 PR record) is used to provide the sub-set of data defining SIDs (PD), STARs (PE) and Approach Procedures (PF) from Section 4.1.9 required for the computer generation of Flight Plans which include Terminal Procedures. The file contains a sequential listing of published Arrival Procedures, Approach Procedures and Departure Procedures, the available Enroute and Runway Transitions for those procedures, the Transition waypoints, the appropriate along track distance fields and the intermediate fixes along those routes.
<xs:complexType name="FlightPlanningRecord"><xs:annotation><xs:documentation>The Flight Planning Arrival/Departure Data Record (424 PR record) is used to provide the sub-set of data defining SIDs (PD), STARs (PE) and Approach Procedures (PF) from Section 4.1.9 required for the computer generation of Flight Plans which include Terminal Procedures. The file contains a sequential listing of published Arrival Procedures, Approach Procedures and Departure Procedures, the available Enroute and Runway Transitions for those procedures, the Transition waypoints, the appropriate along track distance fields and the intermediate fixes along those routes.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="altitude" type="type:FlightPlanningAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Altitude” field used on Flight Planning Arrival/Departure Data Records is a simplification of the altitude concept used in the full procedure records. It will provide an altitude indication in hundreds of feet, no AGL, MSL, FL etc indication provided.</xs:documentation></xs:annotation></xs:element><xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element><xs:element name="atcIdentifier" type="type:ATCIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ATC Identifier” field used on Flight Planning Arrival/Departure Data Records is the indication of the officially published procedure designation which is required for Flight Planning.</xs:documentation></xs:annotation></xs:element><xs:element name="atcWeightCategory" type="enum:ATCWeightCategory" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ATC Weight Category” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, a specific aircraft weight grouping.</xs:documentation></xs:annotation></xs:element><xs:element name="commonSegmentDetails" type="type:CommonSegmentDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This class is an abstraction used to represent a Common Segment.</xs:documentation></xs:annotation></xs:element><xs:element name="enrouteDetails" type="type:SegmentDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a segment.</xs:documentation></xs:annotation></xs:element><xs:element name="intermediateFixDetails" type="type:IntermediateFixDetails" minOccurs="0" maxOccurs="4"><!-- Can it be only 4 --><xs:annotation><xs:documentation>Representsthe details of an intermediate fix in the flight planning record</xs:documentation></xs:annotation></xs:element><xs:element name="timesOfOperation" type="type:TimesOfOperation" minOccurs="0" maxOccurs="1"/><xs:element name="initialCruiseTable" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element><xs:element name="initialDepartureMagneticCourse" type="type:Course" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Outbound Magnetic Course” is the published outbound magnetic course from the waypoint identified in the record’s “Fix Ident” field. In addition, this field is used for Course/Heading/Radials on SID/STAR Approach Records through requirements of the Path Terminator and coding rules contained in Attachment 5 of this specification.</xs:documentation></xs:annotation></xs:element><xs:element name="legTypeCode" type="type:LegTypeCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Leg Type Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Path Terminator concept. It will provide the information on the path between intermediate waypoints as straight or curved and provide an indication of the change in direction of flight, expressed as left or right, at an intermediate waypoint.</xs:documentation></xs:annotation></xs:element><xs:element name="numberOfEngines" type="type:NumberofEnginesRestriction" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Number of Engines Restriction” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific number of engines.</xs:documentation></xs:annotation></xs:element><xs:element name="port" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “port” references the airport or heliport to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureDescription" type="type:ProcedureDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Procedure Description” field used on Flight Planning Arrival/Departure Data Records is the textual representation of the procedure name.</xs:documentation></xs:annotation></xs:element><xs:element name="procedureType" type="enum:ProcedureType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Procedure Type” field used on Flight Planning Arrival/Departure Data Record is a single character code indication the type of procedure in the record, such as Arrival, Standard Instrument Arrival Route, Approach.</xs:documentation></xs:annotation></xs:element><xs:element name="reportingCode" type="enum:ReportingCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Reporting Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Waypoint Description concept. It will provide the information on intermediate waypoints as either Position Report Required (Compulsory Report) or Position Report Not Required (On-Request Report).</xs:documentation></xs:annotation></xs:element><xs:element name="rnavFlags" type="enum:RNAVFlag" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “RNAV Flag” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, aircraft capable of flying RNAV Procedures.</xs:documentation></xs:annotation></xs:element><xs:element name="runwaySegmentDetails" type="type:SegmentDetails" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a segment.</xs:documentation></xs:annotation></xs:element><xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence.</xs:documentation></xs:annotation></xs:element><xs:element name="sidSTARApproachIdentifier" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This UML Class is the base class for SIDSTARRouteIdentifier and ApproachRouteIdentifier classes. this is used in Airport SID/STAR/Approach records. The base class is used so that any of the above mentioned classes can be used in the XML file.</xs:documentation></xs:annotation></xs:element><xs:element name="speedLimit" type="type:SpeedLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Speed Limit” field defines a speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in a terminal procedure or for an airport or heliport terminal environment.</xs:documentation></xs:annotation></xs:element><xs:element name="speedLimitDescription" type="enum:SpeedLimitDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Speed Limit Description" field will designate whether the speed limit coded at a fix in a terminal procedure description is a mandatory, minimum or maximum speed. For Maximum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit The STAR and Approach Procedure Record speed limit will be applied forward to the end of the arrival (excluding the missed approach procedure) or until superseded by another speed limit. For Minimum speeds: The SID Procedure Records and Missed Approach Procedures speed limit will be applied forward to the end of the SID or Missed Approach Procedure or until superseded by another speed limit. The STAR and Approach Procedure Record speed limit will apply to all legs up to and including the termination of the leg on which the speed is coded from the beginning of the procedure or a previous speed limit. If a different speed is coded on a subsequent leg, the limit will be applied for that leg and from that leg backwards to the previous terminator which contained a speed limit. For Mandatory speeds: The speed requirement shall be met at the fix. The speed will not be applied to previous legs or applied forward to the next legs of the procedure record.</xs:documentation></xs:annotation></xs:element><xs:element name="turbopropJetIndicator" type="enum:TurbopropJetIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Turboprop/Jet Indicator” field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific kind of engines.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Altitude” field used on Flight Planning Arrival/Departure Data Records is a simplification of the altitude concept used in the full procedure records. It will provide an altitude indication in hundreds of feet, no AGL, MSL, FL etc indication provided.
<xs:simpleType name="FlightPlanningAltitude"><xs:annotation><xs:documentation>The “Altitude” field used on Flight Planning Arrival/Departure Data Records is a simplification of the altitude concept used in the full procedure records. It will provide an altitude indication in hundreds of feet, no AGL, MSL, FL etc indication provided.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
The “ATC Identifier” field used on Flight Planning Arrival/Departure Data Records is the indication of the officially published procedure designation which is required for Flight Planning.
<xs:simpleType name="ATCIdentifier"><xs:annotation><xs:documentation>The “ATC Identifier” field used on Flight Planning Arrival/Departure Data Records is the indication of the officially published procedure designation which is required for Flight Planning.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="7"/></xs:restriction></xs:simpleType>
The ATC Weight Category field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, a specific aircraft weight grouping.
Diagram
Type
restriction of xs:string
Facets
enumeration
Heavy
Heavy, all aircraft types of 136,000kg (300000LB) or more.
enumeration
Medium
Medium, aircraft types less than 136,000kg (300,000LB) and more than 7,000kg (155,000LB).
enumeration
Light
Light, aircraft types of 7,000kg (155,000LB) or less
<xs:simpleType name="ATCWeightCategory"><xs:annotation><xs:documentation>The ATC Weight Category field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, a specific aircraft weight grouping.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Heavy"><xs:annotation><xs:documentation>Heavy, all aircraft types of 136,000kg (300000LB) or more.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Medium"><xs:annotation><xs:documentation>Medium, aircraft types less than 136,000kg (300,000LB) and more than 7,000kg (155,000LB).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Light"><xs:annotation><xs:documentation>Light, aircraft types of 7,000kg (155,000LB) or less</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="CommonSegmentDetails"><xs:annotation><xs:documentation>This type represents the details for a Common Segment.</xs:documentation></xs:annotation><xs:sequence><xs:element name="alongTrackDistance" type="type:AlongTrackDistance" minOccurs="1" maxOccurs="1"/><xs:element name="fix" type="type:PointReference" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
The Along Track Distance field used on Flight Planning Arrival/Departure Data Records is the total distance for a given transition, from the initial fix to the ending fix in the transition. A single occurrence of a Flight Planning Arrival/Departure Data record can contain up to three Along Track Distance fields, one for each of the transition types that can make up a single terminal route in the Primary Record and up to four possible intermediate fix points in each Continuation Record. Collectively, the values equal the along track distance from the first fix in the first transition to the last fix in the last transition.
<xs:simpleType name="AlongTrackDistance"><xs:annotation><xs:documentation>The Along Track Distance field used on Flight Planning Arrival/Departure Data Records is the total distance for a given transition, from the initial fix to the ending fix in the transition. A single occurrence of a Flight Planning Arrival/Departure Data record can contain up to three Along Track Distance fields, one for each of the transition types that can make up a single terminal route in the Primary Record and up to four possible intermediate fix points in each Continuation Record. Collectively, the values equal the along track distance from the first fix in the first transition to the last fix in the last transition.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceIntegerNM"/></xs:simpleType>
The Fix Related Transition Code is used on Flight Planning Arrival/Departure Data Continuation Records containing Intermediate Fix information and provides an indication, through use of the standard coding practices of separating the procedure into transitions, as to where in the procedure the intermediate fix is located.
<xs:simpleType name="FixRelatedTransitionCode"><xs:annotation><xs:documentation>The Fix Related Transition Code is used on Flight Planning Arrival/Departure Data Continuation Records containing Intermediate Fix information and provides an indication, through use of the standard coding practices of separating the procedure into transitions, as to where in the procedure the intermediate fix is located.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:enumeration value="1"><xs:annotation><xs:documentation>Fix Located in SID Runway Transition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="2"><xs:annotation><xs:documentation>Fix Located in SID Common Portion</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="3"><xs:annotation><xs:documentation>Fix Located in SID Enroute Transition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="4"><xs:annotation><xs:documentation>Fix Located in STAR Enroute Transition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="5"><xs:annotation><xs:documentation>Fix Located in STAR Common Portion</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="6"><xs:annotation><xs:documentation>Fix Located in STAR Runway Transition</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.
<xs:simpleType name="CruiseTableIdentifier"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="2"/></xs:restriction></xs:simpleType>
The “Leg Type Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Path Terminator concept. It will provide the information on the path between intermediate waypoints as straight or curved and provide an indication of the change in direction of flight, expressed as left or right, at an intermediate waypoint.
<xs:complexType name="LegTypeCode"><xs:annotation><xs:documentation>The “Leg Type Code” field used on Flight Planning Arrival/Departure Data Records is a simplification of the Path Terminator concept. It will provide the information on the path between intermediate waypoints as straight or curved and provide an indication of the change in direction of flight, expressed as left or right, at an intermediate waypoint.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Alpha"><xs:sequence><xs:element name="legTypeCodeSC" type="enum:LegTypeCodeSC" minOccurs="1" maxOccurs="1"/><xs:element name="legTypeTurnIndication" type="enum:LegTypeTurnIndication" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="LegTypeCodeSC"><xs:restriction base="xs:string"><xs:enumeration value="PointToPoint"><xs:annotation><xs:documentation>Straight Point to Point</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Curved"><xs:annotation><xs:documentation>Curved line Flight Track</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Number of Engines Restriction field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific number of engines.
<xs:simpleType name="NumberofEnginesRestriction"><xs:annotation><xs:documentation>The Number of Engines Restriction field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure, normally departure, is restricted to, or designed for, aircraft with a specific number of engines.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="4"/></xs:restriction></xs:simpleType>
<xs:simpleType name="ProcedureDescription"><xs:annotation><xs:documentation>The “Procedure Description” field used on Flight Planning Arrival/Departure Data Records is the textual representation of the procedure name.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="15"/></xs:restriction></xs:simpleType>
The Procedure Type field used on Flight Planning Arrival/Departure Data Record is a single character code indication the type of procedure in the record, such as Arrival, Standard Instrument Arrival Route, Approach.
Diagram
Type
restriction of xs:string
Facets
enumeration
ArrivalInDb
Arrival Procedure, Available in Database
enumeration
ArrivalNotInDb
Arrival Procedure, Not Available in Database
enumeration
DepartureInDb
Departure Procedure, Available in Database
enumeration
DepartureNotInDb
Departure Procedure, Not Available in Database
enumeration
StarInDb
Standard Terminal Arrival Route (STAR), Available in Database
enumeration
StarNotInDb
Standard Terminal Arrival Route (STAR), Not Available in Database
enumeration
SidInDb
Standard Instrument Departure (SID), Available in Database
enumeration
SidNotInDb
Standard Instrument Departure (SID), Not Available in Database
<xs:simpleType name="ProcedureType"><xs:annotation><xs:documentation>The Procedure Type field used on Flight Planning Arrival/Departure Data Record is a single character code indication the type of procedure in the record, such as Arrival, Standard Instrument Arrival Route, Approach.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="ArrivalInDb"><xs:annotation><xs:documentation>Arrival Procedure, Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ArrivalNotInDb"><xs:annotation><xs:documentation>Arrival Procedure, Not Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DepartureInDb"><xs:annotation><xs:documentation>Departure Procedure, Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DepartureNotInDb"><xs:annotation><xs:documentation>Departure Procedure, Not Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="StarInDb"><xs:annotation><xs:documentation>Standard Terminal Arrival Route (STAR), Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="StarNotInDb"><xs:annotation><xs:documentation>Standard Terminal Arrival Route (STAR), Not Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SidInDb"><xs:annotation><xs:documentation>Standard Instrument Departure (SID), Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SidNotInDb"><xs:annotation><xs:documentation>Standard Instrument Departure (SID), Not Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VectorSidInDb"><xs:annotation><xs:documentation>Vector SID, Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VectorSidNotInDB"><xs:annotation><xs:documentation>Vector SID, Not Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ApproachInDb"><xs:annotation><xs:documentation>Approach Procedure, Available in Database</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ApproachInDb"><xs:annotation><xs:documentation>Approach Procedure, Not Available in Database</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Reporting Code field used on Flight Planning Arrival/Departure Data Records is a simplification of the Waypoint Description concept. It will provide the information on intermediate waypoints as either Position Report Required (Compulsory Report) or Position Report Not Required (On-Request Report).
<xs:simpleType name="ReportingCode"><xs:annotation><xs:documentation>The Reporting Code field used on Flight Planning Arrival/Departure Data Records is a simplification of the Waypoint Description concept. It will provide the information on intermediate waypoints as either Position Report Required (Compulsory Report) or Position Report Not Required (On-Request Report).</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Required"><xs:annotation><xs:documentation>Position Report Required</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotRequired"><xs:annotation><xs:documentation>Position Report Not Required</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The RNAV Flag field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, aircraft capable of flying RNAV Procedures.
Diagram
Type
restriction of xs:string
Facets
enumeration
Yes
The field will indicate Yes, the procedure is an RNAV procedure
enumeration
No
The field will indicate No, the procedure is NOT an RNAV procedure
<xs:simpleType name="RNAVFlag"><xs:annotation><xs:documentation>The RNAV Flag field used on Flight Planning Arrival/Departure Data Records is derived from government source and is included whenever a given procedure included in the record is restricted to, or designed for, aircraft capable of flying RNAV Procedures.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Yes"><xs:annotation><xs:documentation>The field will indicate Yes, the procedure is an RNAV procedure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="No"><xs:annotation><xs:documentation>The field will indicate No, the procedure is NOT an RNAV procedure</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Turboprop/Jet Indicator” field used on Flight Planning Arrival/Departure Data Records is included whenever a given procedure, normally a departure, is restricted to, or designed for, aircraft with a specific kind of engines.
<xs:simpleType name="TurbopropJetIndicator"><xs:annotation><xs:documentation>The “Turboprop/Jet Indicator” field used on Flight Planning Arrival/Departure Data Records is included whenever a given procedure, normally a departure, is restricted to, or designed for, aircraft with a specific kind of engines.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="All"><xs:annotation><xs:documentation>All Aircraft</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="JetsAndTurboProps"><xs:annotation><xs:documentation>Jets and Turbo Props</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AllCruise250OrLess"><xs:annotation><xs:documentation>All Aircraft, Cruise speed 250 kts or less</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NonJetAndTurboProp"><xs:annotation><xs:documentation>Non-jet and Turbo Prop</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MultiEngineProps"><xs:annotation><xs:documentation>Multi-Engine Props Only</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Jets"><xs:annotation><xs:documentation>Jets</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NonJetNonTurboprop"><xs:annotation><xs:documentation>Non-Jet, Non-Turbo Prop</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TurboProp"><xs:annotation><xs:documentation>Turbo Props</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Category Radii” fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.
<xs:simpleType name="CategoryDistance"><xs:annotation><xs:documentation>The “Category Radii” fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceNMTwoDigits"/></xs:simpleType>
The “Controlled Airspace Indicator” field is used to indicate if an airport is associated with controlled airspace of a terminal type such as a Terminal Control Area (TMA or TCA) Radar Area or Class B or C Airspace within the USA.
Diagram
Type
restriction of xs:string
Facets
enumeration
WithinOrBelowClassC
The Airport is within or below the lateral limits of Class C Airspace.
enumeration
WithinOrBelowCta
The Airport is within or below the lateral limits of a CTA.
enumeration
WithinOrBelowTmsTca
The Airport is within or below the lateral limits of a TMA or TCA.
enumeration
WithinOrBelowRadarZone
The Airport is within or below the lateral limits Radar Zone
enumeration
WithinOrBelowClassB
The Airport is within or below the lateral limits of Class B Airspace.
<xs:simpleType name="ControlledASIndicator"><xs:annotation><xs:documentation>The “Controlled Airspace Indicator” field is used to indicate if an airport is associated with controlled airspace of a terminal type such as a Terminal Control Area (TMA or TCA) Radar Area or Class B or C Airspace within the USA.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="WithinOrBelowClassC"><xs:annotation><xs:documentation>The Airport is within or below the lateral limits of Class C Airspace.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="WithinOrBelowCta"><xs:annotation><xs:documentation>The Airport is within or below the lateral limits of a CTA.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="WithinOrBelowTmsTca"><xs:annotation><xs:documentation>The Airport is within or below the lateral limits of a TMA or TCA.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="WithinOrBelowRadarZone"><xs:annotation><xs:documentation>The Airport is within or below the lateral limits Radar Zone</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="WithinOrBelowClassB"><xs:annotation><xs:documentation>The Airport is within or below the lateral limits of Class B Airspace.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="LongestRunway"><xs:annotation><xs:documentation>The Longest Runway field permits airport to be classified on</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="5"/></xs:restriction></xs:simpleType>
The “Longest Runway Surface Code” field is used to define whether or not there is a hard surface runway at the airport, the length of which is indicated in the Longest Runway field.
Diagram
Type
restriction of xs:string
Facets
enumeration
Hard
Hard Surface, for example, asphalt or concrete
enumeration
Soft
Soft Surface, for example, gravel, grass or soil
enumeration
Water
Water Runway
enumeration
Undefined
Undefined, surface material not provided in source
<xs:simpleType name="LongestRunwaySurfaceCode"><xs:annotation><xs:documentation>The “Longest Runway Surface Code” field is used to define whether or not there is a hard surface runway at the airport, the length of which is indicated in the Longest Runway field.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Hard"><xs:annotation><xs:documentation>Hard Surface, for example, asphalt or concrete</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Soft"><xs:annotation><xs:documentation>Soft Surface, for example, gravel, grass or soil</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Water"><xs:annotation><xs:documentation>Water Runway</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Undefined"><xs:annotation><xs:documentation>Undefined, surface material not provided in source</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="Runway"><xs:annotation><xs:documentation>This following record contains the fields used in Runway Records</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="displacedThresholdDistance" type="type:DisplacedThresholdDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The distance from the extremity of a runway to a threshold not located at that extremity of that runway.</xs:documentation></xs:annotation></xs:element><xs:element name="landingThresholdElevation" type="type:Elevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The elevation of the landing threshold of the runway described in a runway record is defined in the “Landing Threshold Elevation” field.</xs:documentation></xs:annotation></xs:element><xs:element name="ltpEllipsoidHeight" type="type:EllipsoidHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Ellipsoidal Height” field is the height of a surveyed point in reference to the WGS-84 ellipsoid.</xs:documentation></xs:annotation></xs:element><xs:element name="primaryApproachNavaidReference" type="type:PrecisionApproachNavaidReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Element which encapsulates the ILS/MLS/GLS details for the corresponding Runway. This element contains the navaid reference and class.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayBearing" type="type:Bearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The bearing of the runway identified in the “runway identifier” or “pad ident” field of the record is specified in the “Runway Bearing” field.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayTrueBearing" type="type:TrueBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Magnetic Bearing” for ILS localizer, MLS Azimuth, MLS Back Azimuth and Runway records is given in the primary record. This field allows the true bearing to be entered independently of the magnetic variation.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayTrueBearingSource" type="enum:TrueBearingSource" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the source field indicates whether the “True Bearing” is derived from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayDescription" type="type:RunwayDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>If required, additional information concerning a runway can be included in a record in the “Runway Description” field.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayGradient" type="type:RunwayGradient" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Runway Gradient field indicates an overall gradient in percent, measured from the start of take-off roll end of the runway designated in the record. The gradient is expressed as a positive or negative gradient; positive being an upward and negative being a downward gradient.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayIdentifier" type="type:RunwayIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Identifier” field identifies the runways described in runway records and runways served by the ILS/MLS described in ILS/MLS records.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayLength" type="type:RunwayLength" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Runway Length” field defines the total length of the runway surface declared suitable and available for ground operations of aircraft for the runway identified in the records’ Runway Identifier field.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayWidth" type="type:RunwayWidth" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The width of the runway identified in the “Runway Identifier” field is specified in the “Runway Width” field.</xs:documentation></xs:annotation></xs:element><xs:element name="secondaryApproachNavaidReference" type="type:PrecisionApproachNavaidReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Element which encapsulates the ILS/MLS/GLS details for the corresponding Runway. This element contains the navaid reference and class.</xs:documentation></xs:annotation></xs:element><xs:element name="stopway" type="type:StopWay" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Stopway” means the length of an area beyond the take-off runway, no less wide than the runway and centered upon the extended centerline of the runway, and designated for use in decelerating the airplane during an aborted takeoff.</xs:documentation></xs:annotation></xs:element><xs:element name="tchValueIndicator" type="enum:TCHValueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “TCH Value Indicator” field will define which TCH value is provided in the runway record.</xs:documentation></xs:annotation></xs:element><xs:element name="tdzeLocation" type="enum:TDZELocation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The content of the “TDZE Location” field indicates whether the TDZ elevation was obtained from official government sources or from other sources.</xs:documentation></xs:annotation></xs:element><xs:element name="thresholdCrossingHeight" type="type:ThresholdCrossingHeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Threshold Crossing Height” specifies the height above the landing threshold on a normal glide path.</xs:documentation></xs:annotation></xs:element><xs:element name="touchDownZoneElevation" type="type:TouchDownZoneElevation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Touchdown Zone Elevation” is the highest elevation in the first 3,000 feet of the landing surface beginning at the threshold.</xs:documentation></xs:annotation></xs:element><xs:element name="starterExtension" type="type:StarterExtension" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This data element describes a starter extension of a runway</xs:documentation></xs:annotation></xs:element><!-- Runway continuation record fields --><xs:element name="surfaceType" type="enum:SurfaceType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the surface type of the runway.</xs:documentation></xs:annotation></xs:element><xs:element name="maximumHelicopterWeight" type="type:MaxHelicopterWeight" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides the max weight for helicopters using this runway.</xs:documentation></xs:annotation></xs:element><xs:element name="helicopterPerformanceReq" type="enum:HelicopterPerformanceReq" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides a performance requirement for helicopters to use this runway.</xs:documentation></xs:annotation></xs:element><xs:element name="takeOffRunwayAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Take Off Run Available (TORA) is the declared distance value which is available for take-off ground roll. Starter extension distances are not included in the TORA distance and may be added if a starter extension is available. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element><xs:element name="takeOffDistanceAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Take Off Distance Available (TODA) is the declared distance value which is available for take-off over a 50 ft obstacle. Typically, the TODA equals the TORA plus clearway. Starter extension distances are not included in the TODA. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element><xs:element name="accelerateStopDistanceAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Accelerate Stop Distance Available (ASDA) is the declared distance value which is available in case of an aborted take-off. Typically, the ASDA equals the TORA plus stopway. Starter extension distances are not included in the TODA distance and may be added if a starter extension is available. A value of 00000 indicates that the runway is not usable for take-off. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element><xs:element name="landingDistanceAvailable" type="type:DistanceFeetFiveDigits" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Landing Distance Available (LDA) is the declared distance value which is available for landing. Typically, the LDA equals the runway length minus the threshold displacement distance. A value of 00000 indicates that the runway is not usable for landing. A blank field means that no value is declared in source.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayUsageIndicator" type="enum:RunwayUsageIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Runway Usage Indicator field specifies if a Runway is usable for take-off, landing, or both operations.</xs:documentation></xs:annotation></xs:element><xs:element name="runwayAccuracy" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates runway data elements meet runway accuracy requirements by confirming they are consistent with a trustworthy independent data source.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="runwayAccuracyCompliance" type="enum:RunwayAccuracyCompliance" minOccurs="0" maxOccurs="1"/><xs:element name="landingThresholdElvationAccuracyCompliance" type="enum:LandingThresholdElvationAccuracyCompliance" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="DisplacedThresholdDistance"><xs:annotation><xs:documentation>The distance from the extremity of a runway to a threshold not located at that extremity of that runway, in feet.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceFeet"/></xs:simpleType>
<xs:complexType name="PrecisionApproachNavaidReference"><xs:annotation><xs:documentation>Element which encapsulates the localizer details for the corresponding Runway. This element contains the localizer ident and localizer class.</xs:documentation></xs:annotation><xs:sequence><xs:element name="approachCategory" type="enum:PrecisionApproachCategory" minOccurs="1" maxOccurs="1"/><xs:element name="navaidReference" type="type:PointReference" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="RunwayDescription"><xs:annotation><xs:documentation>If required, additional information concerning a runway can be included in a record in the “Runway Description” field.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="22"/></xs:restriction></xs:simpleType>
The Runway Gradient field indicates an overall gradient in percent, measured from the start of take-off roll end of the runway designated in the record. The gradient is expressed as a positive or negative gradient; positive being an upward and negative being a downward gradient.
<xs:simpleType name="RunwayGradient"><xs:annotation><xs:documentation>The Runway Gradient field indicates an overall gradient in percent, measured from the start of take-off roll end of the runway designated in the record. The gradient is expressed as a positive or negative gradient; positive being an upward and negative being a downward gradient.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"><xs:maxInclusive value="9.0"/><xs:minInclusive value="-9.0"/></xs:restriction></xs:simpleType>
The “Runway Length” field defines the total length of the runway surface declared suitable and available for ground operations of aircraft for the runway identified in the records’ Runway Identifier field, in feet.
<xs:simpleType name="RunwayLength"><xs:annotation><xs:documentation>The “Runway Length” field defines the total length of the runway surface declared suitable and available for ground operations of aircraft for the runway identified in the records’ Runway Identifier field, in feet.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceFeetFiveDigits"/></xs:simpleType>
<xs:simpleType name="RunwayWidth"><xs:annotation><xs:documentation>The width of the runway identified in the “Runway Identifier” field is specified in the “Runway Width” field.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
“Stopway” means the length of an area beyond the take-off runway, no less wide than the runway and centered upon the extended centerline of the runway, and designated for use in decelerating the airplane during an aborted takeoff.
<xs:simpleType name="StopWay"><xs:annotation><xs:documentation>“Stopway” means the length of an area beyond the take-off runway, no less wide than the runway and centered upon the extended centerline of the runway, and designated for use in decelerating the airplane during an aborted takeoff.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceFeet"/></xs:simpleType>
<xs:simpleType name="TCHValueIndicator"><xs:annotation><xs:documentation>The “TCH Value Indicator” field will define which TCH value is provided in the runway record.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="TchOfElectricGlideSlope"><xs:annotation><xs:documentation>TCH provided in Runway Record is that of the electronic Glide Slope</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TchRnavToRunway"><xs:annotation><xs:documentation>TCH provided in Runway Record is that of an RNAV procedure to the runway</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TchVgsi"><xs:annotation><xs:documentation>TCH provided in the Runway Record is that of the VGSI for the runway</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TchDefaulted"><xs:annotation><xs:documentation>TCH provided in the Runway Record is the default value of 40 or 50 feet (See Section 5.67).</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="TDZELocation"><xs:annotation><xs:documentation>The content of the “TDZE Location” field indicates whether the TDZ elevation was obtained from official government sources or from other sources.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Official"><xs:annotation><xs:documentation>Official Source</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LandingThreshold"><xs:annotation><xs:documentation>Landing Threshold</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AirportElevation"><xs:annotation><xs:documentation>Airport Elevation</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="TouchDownZoneElevation"><xs:annotation><xs:documentation>The “Touchdown Zone Elevation” is the highest elevation in the first 3,000 feet of the landing surface beginning at the threshold.</xs:documentation></xs:annotation><xs:restriction base="xs:int"/></xs:simpleType>
An area made available for take-off, prior to the normal runway end at the beginning of the takeoff run. Starter extensions are established where additional takeoff distance, takeoff run, or acelerated-stop distance is required, but physical limiations do not allow provision of the manditory runway strip or width.
<xs:simpleType name="StarterExtension"><xs:annotation><xs:documentation>An area made available for take-off, prior to the normal runway end at the beginning of the takeoff run. Starter extensions are established where additional takeoff distance, takeoff run, or acelerated-stop distance is required, but physical limiations do not allow provision of the manditory runway strip or width.</xs:documentation></xs:annotation><xs:restriction base="xs:int"><xs:maxInclusive value="9999"/><xs:minInclusive value="1"/></xs:restriction></xs:simpleType>
<xs:simpleType name="SurfaceType"><xs:annotation><xs:documentation>The Surface Type field defines the predominant surface type of the runway/helipad described in the record</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Asphalt"/><xs:enumeration value="AsphaltAndGrass"/><xs:enumeration value="BituminousTarOrAsphalt"><xs:annotation><xs:documentation>Bituminous tar or asphalt and/or oil or bitumen bound, mix-in-place surfaces (often refered to as “earth cement”)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="BrickisLaidOrMortared"/><xs:enumeration value="Clay"/><xs:enumeration value="Concrete"/><xs:enumeration value="ConcreteAndAsphalt"/><xs:enumeration value="ConcreteAndGrass"/><xs:enumeration value="Coral"/><xs:enumeration value="Dirt"/><xs:enumeration value="Grass"/><xs:enumeration value="Gravel"/><xs:enumeration value="Ice"/><xs:enumeration value="Laterite"/><xs:enumeration value="Macadam"/><xs:enumeration value="LandingMat"><xs:annotation><xs:documentation>Usually made of aluminium</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ProtectiveLaminate"><xs:annotation><xs:documentation>Usually made of rubber</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Metal"><xs:annotation><xs:documentation>Steel or Aluminium</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Mix"><xs:annotation><xs:documentation>Non bituminous mix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Other"/><xs:enumeration value="Paved"><xs:annotation><xs:documentation>generic hard surface</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PiercedSteelPlanking"/><xs:enumeration value="Sand"/><xs:enumeration value="Sealed"/><xs:enumeration value="Silt"/><xs:enumeration value="Snow"/><xs:enumeration value="Soil"/><xs:enumeration value="Stone"/><xs:enumeration value="Tarmac"/><xs:enumeration value="Treated"/><xs:enumeration value="Turf"/><xs:enumeration value="Unknown"/><xs:enumeration value="Unpaved"/><xs:enumeration value="Water"/></xs:restriction></xs:simpleType>
The Runway Usage Indicator field specifies if a Runway is usable for take-off, landing, or both operations. A value of LandingOnly will require the TORA, TODA, and ASDA to be 0 and the LDA either blank or non-0. A field content TakeoffOnly will require the TORA, TODA, and ASDA to be blank or non-0 and the LDA to be 0.
<xs:simpleType name="RunwayUsageIndicator"><xs:annotation><xs:documentation>The Runway Usage Indicator field specifies if a Runway is usable for take-off, landing, or both operations. A value of LandingOnly will require the TORA, TODA, and ASDA to be 0 and the LDA either blank or non-0. A field content TakeoffOnly will require the TORA, TODA, and ASDA to be blank or non-0 and the LDA to be 0.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="LandingOnly"/><xs:enumeration value="TakeoffOnly"/><xs:enumeration value="TakeoffAndLanding"/></xs:restriction></xs:simpleType>
Accuracy of Runway Length (A424 PG 5.57) is 5 meters (compared to measured length of runway surface - stopways, aligned taxiways and starter extensions excluded, as per A424 runway length definition). Accuracy of Runway Threshold Position (A424 PG 5.36 and 5.37) is 5 meters (compared to measured runway landing threshold location). Accuracy of Runway Threshold Displacement Distance (A424 PG 5.69) is 5 meters (compared to measured length of displaced area). Accuracy of Runway Magnetic Bearing (A424 PG 5.58) and Airport Magnetic Variation (A424 PA 5.39) is such that the runway true bearing accuracy is 0.5 degree (NDB Magnetic Runway Bearing will be converted in runway true bearing using NDB Airport Magnetic Variation, then will be validated by comparison with measured True Bearing of runway).
<xs:simpleType name="RunwayAccuracyCompliance"><xs:annotation><xs:documentation>Accuracy of Runway Length (A424 PG 5.57) is 5 meters (compared to measured length of runway surface - stopways, aligned taxiways and starter extensions excluded, as per A424 runway length definition). Accuracy of Runway Threshold Position (A424 PG 5.36 and 5.37) is 5 meters (compared to measured runway landing threshold location). Accuracy of Runway Threshold Displacement Distance (A424 PG 5.69) is 5 meters (compared to measured length of displaced area). Accuracy of Runway Magnetic Bearing (A424 PG 5.58) and Airport Magnetic Variation (A424 PA 5.39) is such that the runway true bearing accuracy is 0.5 degree (NDB Magnetic Runway Bearing will be converted in runway true bearing using NDB Airport Magnetic Variation, then will be validated by comparison with measured True Bearing of runway).</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Compliant"/><xs:enumeration value="NotCompliant"/><xs:enumeration value="NotEvaluated"/></xs:restriction></xs:simpleType>
Simple Type enum:LandingThresholdElvationAccuracyCompliance
Namespace
http://www.arinc424.com/xml/enumerations
Annotations
Difference between Runway Landing Threshold Elevation (A424 PG 5.68) and runway landing threshold elevation measured with an independent means is 5 meters or less.
<xs:simpleType name="LandingThresholdElvationAccuracyCompliance"><xs:annotation><xs:documentation>Difference between Runway Landing Threshold Elevation (A424 PG 5.68) and runway landing threshold elevation measured with an independent means is 5 meters or less.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Compliant"/><xs:enumeration value="NotCompliant"/><xs:enumeration value="NotEvaluated"/></xs:restriction></xs:simpleType>
<xs:complexType name="AirportGate"><xs:annotation><xs:documentation>This following record contains the fields used in Airport Gate Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Point"><xs:sequence/></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Heliport"><xs:annotation><xs:documentation>This following record contains the fields used in Heliport Record</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Port"><xs:sequence><xs:element name="heliportType" type="enum:HeliportType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provies information as to what type of heliport the facility is.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="HeliportType"><xs:annotation><xs:documentation>This field provides information on the type of heliport facility.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Hospital"/><xs:enumeration value="OilRig"/><xs:enumeration value="Other"/><xs:enumeration value="NotProvided"/></xs:restriction></xs:simpleType>
<xs:complexType name="AirwaysMarker"><xs:annotation><xs:documentation>This following record contains the fields used in Airways Marker Records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Point"><xs:sequence><xs:element name="elevation" type="type:Elevation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Facility Elevation field provides the elevation of navaids and communication transmitters.</xs:documentation></xs:annotation></xs:element><xs:element name="markerCode" type="type:MarkerCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Marker Code” field contains the coded ident that provides an aural and visual indication of station passage in the cockpit. The code shall be keyed so as to transmit dots or dashes, or both, in an appropriate sequence on a radio frequency of 75 MHz. The frequency of the modulating tone is 3000 Hz.</xs:documentation></xs:annotation></xs:element><xs:element name="markerPower" type="enum:HighLow" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “High/Low” field indicates the power of the enroute marker.</xs:documentation></xs:annotation></xs:element><xs:element name="markerShape" type="enum:MarkerShape" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Shape” field defines the radiation pattern of an airways marker as being either “bone” or “elliptical.”</xs:documentation></xs:annotation></xs:element><xs:element name="minorAxis" type="type:MinorAxisBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Minor Axis Bearing” field indicates the true bearing of the minor axis of marker beacons.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Marker Code” field contains the coded ident that provides an aural and visual indication of station passage in the cockpit. The code shall be keyed so as to transmit dots or dashes, or both, in an appropriate sequence on a radio frequency of 75 MHz. The frequency of the modulating tone is 3000 Hz.
<xs:simpleType name="MarkerCode"><xs:annotation><xs:documentation>The “Marker Code” field contains the coded ident that provides an aural and visual indication of station passage in the cockpit. The code shall be keyed so as to transmit dots or dashes, or both, in an appropriate sequence on a radio frequency of 75 MHz. The frequency of the modulating tone is 3000 Hz.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="4"/></xs:restriction></xs:simpleType>
<xs:simpleType name="HighLow"><xs:annotation><xs:documentation>The High/Low field indicates the power of the enroute marker.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Low"><xs:annotation><xs:documentation>Low Power</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="High"><xs:annotation><xs:documentation>High Power</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="MarkerShape"><xs:annotation><xs:documentation>The “Shape” field defines the radiation pattern of an airways marker as being either “bone” or “elliptical.”</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Bone"><xs:annotation><xs:documentation>Bone Shape</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Elliptical"><xs:annotation><xs:documentation>Elliptical Shape</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="EnrouteAirwaysRestrictionAltitudeExclusion"><xs:annotation><xs:documentation>This following record contains the fields used in Enroute Airways Restriction Altitude Exclusion Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="EnrouteAirwaysRestriction"><xs:sequence><xs:element name="exclusionIndicator" type="enum:ExclusionIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Exclusion Indicator” field is an indication of how the altitudes contained in the Cruising Table record referenced by the Airway segment(s) are restricted. This is an “all altitude” restriction, further defined by direction of flight. These codes will not be used when certain altitudes remain available in a direction of flight.</xs:documentation></xs:annotation></xs:element><xs:element name="restrictionAltitudeBlockIndicator" type="type:RestrictionAltitudeBlockIndicator" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction for Restriction Altitude and Block Indicator elements as they occur together in airways restriction records.</xs:documentation></xs:annotation></xs:element><xs:element name="unitsofAltitude" type="enum:UnitsofAltitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Units of Altitude” field is used to indicate the units of measurement for the values in the “Restriction Altitude” fields.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The Airway Restriction Start Date field is used to indicate the earliest GMT date at which the restriction takes effect. The Airway Restriction End Date is used to indicate the latest GMT date at which the restriction is still in effect. This date information may be supplemented by Time of Operation information contained in an Airway Restriction Record, Type AE or TC. When no AE or TC record exists for the Restriction Identifier, the Start time is 0000 GMT and the end time is 2359 GMT of the dates indicated.
<xs:simpleType name="AirwayRestrictionStartEndDate"><xs:annotation><xs:documentation>The Airway Restriction Start Date field is used to indicate the earliest GMT date at which the restriction takes effect. The Airway Restriction End Date is used to indicate the latest GMT date at which the restriction is still in effect. This date information may be supplemented by Time of Operation information contained in an Airway Restriction Record, Type AE or TC. When no AE or TC record exists for the Restriction Identifier, the Start time is 0000 GMT and the end time is 2359 GMT of the dates indicated.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="7"/></xs:restriction></xs:simpleType>
The “Restriction Identifier” is used to assign a unique identifier to a restriction record and to multiple restrictions records for a particular route or route segment.
<xs:simpleType name="RestrictionIdentifier"><xs:annotation><xs:documentation>The “Restriction Identifier” is used to assign a unique identifier to a restriction record and to multiple restrictions records for a particular route or route segment.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
The “Restriction Record Type” field is used to define what type of a restriction is contained in the Enroute Airway Restriction Record in question.
Diagram
Type
restriction of xs:string
Facets
enumeration
AE
Altitude Exclusion. The record contains altitudes, normally available, that are excluded from use for the Enroute Airway Segment. May be further restricted by Time of Operation information.
enumeration
TC
Cruising Table Replacement. The record contains only a reference to a Cruising Table Identifier. That Cruise Table will be in force, replacing the Cruise Table Identifier in the Enroute Airway segment records defined in the Start Fix/End Fix fields.
enumeration
SC
Seasonal Restriction. Record is used to close an Airway or portion of an Airway on a seasonal basis.
enumeration
NR
Note Restrictions. The record contains restrictions that do not fit the pattern of formatted information allowed by other Restriction Record Types.
<xs:simpleType name="RestrictionRecordType"><xs:annotation><xs:documentation>The “Restriction Record Type” field is used to define what type of a restriction is contained in the Enroute Airway Restriction Record in question.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AE"><xs:annotation><xs:documentation>Altitude Exclusion. The record contains altitudes, normally available, that are excluded from use for the Enroute Airway Segment. May be further restricted by Time of Operation information.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TC"><xs:annotation><xs:documentation>Cruising Table Replacement. The record contains only a reference to a Cruising Table Identifier. That Cruise Table will be in force, replacing the Cruise Table Identifier in the Enroute Airway segment records defined in the Start Fix/End Fix fields.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SC"><xs:annotation><xs:documentation>Seasonal Restriction. Record is used to close an Airway or portion of an Airway on a seasonal basis.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NR"><xs:annotation><xs:documentation>Note Restrictions. The record contains restrictions that do not fit the pattern of formatted information allowed by other Restriction Record Types.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Route Identifier” field identifies a route of flight or traffic orientation, using the coding employed on aeronautical navigation charts and related publications.
<xs:simpleType name="RouteIdentifier"><xs:annotation><xs:documentation>The “Route Identifier” field identifies a route of flight or traffic orientation, using the coding employed on aeronautical navigation charts and related publications.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="10"/></xs:restriction></xs:simpleType>
The Exclusion Indicator field is an indication of how the altitudes contained in the Cruising Table record referenced by the Airway segment(s) are restricted. This is an all altitude restriction, further defined by direction of flight. These codes will not be used when certain altitudes remain available in a direction of flight.
Diagram
Type
restriction of xs:string
Facets
enumeration
AllBoth
All altitudes in both directions of flight are restricted. This effectively closes the airway in both direction of flight.
enumeration
AllOpposite
All altitudes in the opposite direction in which the Enroute Airway is coded are restricted. This effectively closes the airway in one direction of flight i.e., the opposite direction from that in which the airway is coded.
enumeration
AllPerAirway
All altitudes in the direction in which the Enroute Airway is coded are restricted. This effectively closes the airway in one direction of flight i.e., the direction in which the airway is coded.
enumeration
NotAll
The restriction is not an all altitude restriction.
<xs:simpleType name="ExclusionIndicator"><xs:annotation><xs:documentation>The Exclusion Indicator field is an indication of how the altitudes contained in the Cruising Table record referenced by the Airway segment(s) are restricted. This is an all altitude restriction, further defined by direction of flight. These codes will not be used when certain altitudes remain available in a direction of flight.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AllBoth"><xs:annotation><xs:documentation>All altitudes in both directions of flight are restricted. This effectively closes the airway in both direction of flight.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AllOpposite"><xs:annotation><xs:documentation>All altitudes in the opposite direction in which the Enroute Airway is coded are restricted. This effectively closes the airway in one direction of flight i.e., the opposite direction from that in which the airway is coded.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AllPerAirway"><xs:annotation><xs:documentation>All altitudes in the direction in which the Enroute Airway is coded are restricted. This effectively closes the airway in one direction of flight i.e., the direction in which the airway is coded.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotAll"><xs:annotation><xs:documentation>The restriction is not an all altitude restriction.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="RestrictionAltitudeBlockIndicator"><xs:annotation><xs:documentation>This class is an abstraction for Restriction Altitude and Block Indicator elements as they occur together in airways restriction records.</xs:documentation></xs:annotation><xs:sequence><xs:element name="blockIndicator" type="enum:BlockIndicator" minOccurs="0" maxOccurs="1"/><xs:element name="restrictionAltitude" type="type:RestrictionAltitude" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
The “Block Indicator” field is used to specify that the altitudes that follow in the restriction record are either “block” of altitudes that are restricted (not available for flight) or are individual altitudes that are restricted.
<xs:simpleType name="BlockIndicator"><xs:annotation><xs:documentation>The “Block Indicator” field is used to specify that the altitudes that follow in the restriction record are either “block” of altitudes that are restricted (not available for flight) or are individual altitudes that are restricted.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Block"><xs:annotation><xs:documentation>indicating an altitude block</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Individual"><xs:annotation><xs:documentation>indicating individual altitudes</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="RestrictionAltitude"><xs:annotation><xs:documentation>The “Restriction Altitude” fields are used to specify the altitude profile for a specific restriction.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
<xs:simpleType name="UnitsofAltitude"><xs:annotation><xs:documentation>The Units of Altitude field is used to indicate the units of measurement for the values in the Restriction Altitude fields.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="HundredsFeet"><xs:annotation><xs:documentation>Restriction Altitudes are expressed in hundreds of feet</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MetricFlightLevel"><xs:annotation><xs:documentation>Restriction Altitudes are expressed in metric Flight Levels</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FeetFlightLevel"><xs:annotation><xs:documentation>Restriction Altitudes are expressed in feet Flight Levels</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TensOfMeters"><xs:annotation><xs:documentation>Restriction Altitudes are expressed in tens of meters</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="EnrouteAirwaysRestrictionSeasonalClosure"><xs:annotation><xs:documentation>This following record contains the fields used in Enroute Airways Restriction Seasonal class.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="EnrouteAirwaysRestriction"><xs:sequence><xs:element name="cruiseTableIdentifier" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="EnrouteAirwaysRestrictionCruisingTableReplacement"><xs:annotation><xs:documentation>This following record contains the fields used in Enroute Airways Restriction Cruising Table Replacement Primary Records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="EnrouteAirwaysRestriction"><xs:sequence><xs:element name="cruiseTableIdentifier" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="cruiseTableRef" type="xs:IDREF"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="AirwaySegment"><xs:complexContent><xs:extension base="Route"><xs:sequence><xs:element name="airwayLeg" type="AirwayLeg" minOccurs="2" maxOccurs="unbounded"/><xs:element name="qualifier1" type="enum:AirwayQualifier1" minOccurs="0" maxOccurs="1"/><xs:element name="qualifier2" type="enum:AirwayQualifier2" minOccurs="0" maxOccurs="1"/><xs:element name="rnavPbnNavSpec" type="enum:AirwayRnavPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNAV PBN navigation specification applies to this airway segment</xs:documentation></xs:annotation></xs:element><xs:element name="rnpPbnNavSpec" type="enum:AirwayRnpPbnNavSpec" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element indicates that an RNP PBN navigation specification applies to this airway segment</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="AirwayLeg"><xs:annotation><xs:documentation>This following leg contains the fields used in Enroute Airway leg.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Leg"><xs:sequence><xs:element name="boundaryCode" type="enum:BoundaryCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Routes of flight frequently cross geographical boundaries. The “Boundary Code” field identifies the area into, or from which a continuous route passes when such a crossing occurs.</xs:documentation></xs:annotation></xs:element><xs:element name="cruiseTableIndicator" type="type:CruiseTableIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element><xs:element name="directionRestriction" type="enum:EnrouteAirwayDirectionalRestriction" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Direction Restriction” field will indicate the direction an Enroute Airway is to be flown</xs:documentation></xs:annotation></xs:element><xs:element name="routeDistanceFrom" type="type:LegDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>In Enroute Airways, Route Distance From is the distance in nautical miles from the waypoint identified in the records Fix Ident field to the next waypoint of the route.</xs:documentation></xs:annotation></xs:element><xs:element name="euIndicator" type="enum:EUIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “EU Indicator” field is used to identify those Enroute Airway records that have an Airway Restriction record without identifying the restriction.</xs:documentation></xs:annotation></xs:element><xs:element name="fixRadiusTransitionIndicator" type="type:FixedRadiusTransitionIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Indicates that a specific turn radius from the inbound course to the outbound course is required by the airspace controlling agency.</xs:documentation></xs:annotation></xs:element><xs:element name="inboundCourse" type="type:Course" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>“Inbound Magnetic Course” is the published inbound magnetic course to the waypoint in the “Fix Ident” field of the records in which it is employed. The “HX” group of Path Terminator codes is used to provide racetrack type course reversal flight paths. Government publications for these course reversal include an “inbound magnetic bearing.” The SID/STAR/Approach Procedures records do not include a dedicated field for this inbound course. Instead, the information is included in the “Outbound Magnetic Course” field of such records.</xs:documentation></xs:annotation></xs:element><xs:element name="waypointDescription" type="type:AirwayWaypointDescription" minOccurs="1" maxOccurs="1"/><xs:element name="level" type="enum:Level" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Level field defines the airway structure of which the record is an element.</xs:documentation></xs:annotation></xs:element><xs:element name="rho" type="type:Rho" minOccurs="0" maxOccurs="1"/><xs:element name="rnp" type="type:RequiredNavigationPerformance" minOccurs="0" maxOccurs="1"/><xs:element name="rvsmMinimumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Minimum Level is the lowest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element><xs:element name="theta" type="type:Theta" minOccurs="0" maxOccurs="1"/><xs:element name="verticalScaleFactor" type="type:VerticalScaleFactor" minOccurs="0" maxOccurs="1"/><xs:element name="vsfRVSMMaximumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Maximum Level is the highest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element><xs:element name="outboundCourse" type="type:Course" minOccurs="0" maxOccurs="1"/><xs:element name="minAltitude1" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="minAltitude2" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="maximumAltitude" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Maximum Altitude” field is used to indicate the maximum altitude allowed.</xs:documentation></xs:annotation></xs:element><xs:element name="restrictiveAirspaceRef" type="RestrictiveAirspaceReference" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
Routes of flight frequently cross geographical boundaries. The “Boundary Code” field identifies the area into, or from which a continuous route passes when such a crossing occurs.
<xs:simpleType name="BoundaryCode"><xs:annotation><xs:documentation>Routes of flight frequently cross geographical boundaries. The “Boundary Code” field identifies the area into, or from which a continuous route passes when such a crossing occurs.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="U"><xs:annotation><xs:documentation>USA (USA)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="C"><xs:annotation><xs:documentation>Canada and Alaska (CAN)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="P"><xs:annotation><xs:documentation>Pacific (PAC)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="L"><xs:annotation><xs:documentation>Latin America (LAM)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="S"><xs:annotation><xs:documentation>South America (SAM)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1"><xs:annotation><xs:documentation>South Pacific (SPA)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="E"><xs:annotation><xs:documentation>Europe (EUR)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="2"><xs:annotation><xs:documentation>Eastern Europe (EEU)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="M"><xs:annotation><xs:documentation>Middle East South Asia (MES)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="A"><xs:annotation><xs:documentation>Africa (AFR</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
Simple Type enum:EnrouteAirwayDirectionalRestriction
Namespace
http://www.arinc424.com/xml/enumerations
Annotations
The Direction Restriction field, when used on Enroute Airway records, will indicate the direction an Enroute Airway is to be flown. The Direction Restriction field, when used on Preferred Route records, will indicate whether the routing is available only in the direction of from initial fix to terminus fix or in both directions.
Diagram
Type
restriction of xs:string
Facets
enumeration
Oneway
One way in direction route is coded (Forward).
enumeration
Backward
One way in opposite direction route is coded (backward).
<xs:simpleType name="EnrouteAirwayDirectionalRestriction"><xs:annotation><xs:documentation>The Direction Restriction field, when used on Enroute Airway records, will indicate the direction an Enroute Airway is to be flown. The Direction Restriction field, when used on Preferred Route records, will indicate whether the routing is available only in the direction of from initial fix to terminus fix or in both directions.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Oneway"><xs:annotation><xs:documentation>One way in direction route is coded (Forward).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Backward"><xs:annotation><xs:documentation>One way in opposite direction route is coded (backward).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NoRestrictions"><xs:annotation><xs:documentation>No restrictions on direction.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="EUIndicator"><xs:annotation><xs:documentation>The “EU Indicator” field is used to identify those Enroute Airway records that have an Airway Restriction record without identifying the restriction.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="NoRestriction"><xs:annotation><xs:documentation>no restriction record exists.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Restriction"><xs:annotation><xs:documentation>restriction for the segment is contained in the restriction file</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="FixedRadiusTransitionIndicator"><xs:annotation><xs:documentation>Indicates that a specific turn radius from the inbound course to the outbound course is required by the airspace controlling agency.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"/></xs:simpleType>
<xs:complexType name="AirwayWaypointDescription"><xs:annotation><xs:documentation>This class represents the waypoint description information used by airway legs.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isEssential" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isHolding" type="xs:boolean" minOccurs="1" maxOccurs="1"/><xs:element name="isNonEssential" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isOceanicGateway" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isOffAirwayFloating" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isSourceProvidedEnrouteWaypoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isTransitionEssential" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A waypoint which normally would be classified as non-essential may be required to transition from the enroute structure to the terminal structure. Waypoints falling into this category are classified as Transition Essential Waypoints</xs:documentation></xs:annotation></xs:element><xs:element name="isUnchartedIntersection" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isAtcCompulsoryReportingPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Compulsory Reporting Point: Essential or nonessential waypoints may be classified as ATC compulsory points. ATC requires the pilot to make a communications report at these waypoints. All other waypoints may be classified as non compulsory reporting points and are reported only when specifically requested by ATC</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="Level"><xs:annotation><xs:documentation>The Level field defines the airway structure of which the record is an element.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AllAlt"><xs:annotation><xs:documentation>All Altitudes</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HighAlt"><xs:annotation><xs:documentation>High Altitudes</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LowAlt"><xs:annotation><xs:documentation>Low Altitudes</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="RestrictiveAirspaceDesignation"><xs:annotation><xs:documentation>The “Restrictive Airspace Designation” field contains the number or name that uniquely identifies the restrictive airspace.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="10"/></xs:restriction></xs:simpleType>
The “Restrictive Airspace Type” field is used to indicate the type of Airspace in which the flight of aircraft is prohibited or restricted. The restriction may be continuous or specified for certain times.
<xs:simpleType name="RestrictiveAirspaceType"><xs:annotation><xs:documentation>The “Restrictive Airspace Type” field is used to indicate the type of Airspace in which the flight of aircraft is prohibited or restricted. The restriction may be continuous or specified for certain times.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Alert"><xs:annotation><xs:documentation>Alert</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Caution"><xs:annotation><xs:documentation>Caution</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Danger"><xs:annotation><xs:documentation>Danger</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MilitaryOps"><xs:annotation><xs:documentation>Military Operations Area</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NationalSecurity"><xs:annotation><xs:documentation>National Security Area</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Prohibited"><xs:annotation><xs:documentation>Prohibited</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Restricted"><xs:annotation><xs:documentation>Restricted</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Training"><xs:annotation><xs:documentation>Training</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Warning"><xs:annotation><xs:documentation>Warning</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unspecified"><xs:annotation><xs:documentation>Unspecified or Unknown</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="AirwayRnavPbnNavSpec"><xs:annotation><xs:documentation>This field provides information on the ICAO PBN Navigation Specification applicable to this airway segment</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Rnav5"/><xs:enumeration value="Rnav4"/><xs:enumeration value="Rnav2"/><xs:enumeration value="Rnav1"/><xs:enumeration value="BRnav"/><xs:enumeration value="PRnav"/><xs:enumeration value="PbnUnspecified"/></xs:restriction></xs:simpleType>
<xs:simpleType name="AirwayRnpPbnNavSpec"><xs:annotation><xs:documentation>This field provides information on the ICAO PBN Navigation Specification appliable to this airway segment</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Rnp4"/><xs:enumeration value="Rnp2"/><xs:enumeration value="Rnp1"/><xs:enumeration value="RnpAr"/><xs:enumeration value="AdvRnp"/><xs:enumeration value="Rnp0_3"/><xs:enumeration value="PbnUnspecified"/></xs:restriction></xs:simpleType>
This data type represents the company route. It contains children starting with the letters via. The company route is made up of references to other data. e.g., the company route is to proceed via a SID then via an enroute ...etc.
<xs:complexType name="CompanyRoute"><xs:annotation><xs:documentation>This data type represents the company route. It contains children starting with the letters via. The company route is made up of references to other data. e.g., the company route is to proceed via a SID then via an enroute ...etc.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="alternateDistanace" type="type:AlternateDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is used to supply the distance in nautical miles from the “To Airport/Heliport/Fix” to the Alternate Airport/Heliport.</xs:documentation></xs:annotation></xs:element><xs:element name="costIndex" type="type:CostIndex" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Cost Index field is used to define the relative value of fuel-related costs and time-related costs for a particular route.</xs:documentation></xs:annotation></xs:element><xs:element name="cruiseAltitude" type="type:CruiseAltitude" minOccurs="0" maxOccurs="1"/><xs:element name="enrouteEmergencyPortRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/><xs:element name="fromPortFix" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When used on Company Routes and Helicopter Operations Company Routes, the “From Airport/Heliport/Fix” is the fix from which the company route originates. The “To Airport/Heliport/Fix” is the fix at which the company route terminates. When used on Alternate Records, it is the Departure, Destination or Enroute Airport/Fix for which the alternate information is being provided.</xs:documentation></xs:annotation></xs:element><xs:element name="identifier" type="type:CoreIdentifier" minOccurs="1" maxOccurs="1"/><xs:element name="terminalAlternateAirport" type="type:TerminalAlternateAirport" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field has two uses depending on the “VIA” field and File Code for “To Fix.” For “VIA” field content of “ALT” this field will contain the Alternate Airport Ident or Heliport Ident for this Company Route. If the file code for “To Fix” contains “P,” this field will contain the Airport Ident for REGN CODE (Section 5.41) of Terminal Waypoints (PC records) and Runway (PG records). If the file code for “To Fix” contains “H”, this field will contain the Heliport Ident for REGN CODE (Section 5.41) of Helicopter Terminal Waypoints (HC records).</xs:documentation></xs:annotation></xs:element><xs:element name="toPortFix" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>When used on Company Routes and Helicopter Operations Company Routes, the “From Airport/Heliport/Fix” is the fix from which the company route originates. The “To Airport/Heliport/Fix” is the fix at which the company route terminates. When used on Alternate Records, it is the Departure, Destination or Enroute Airport/Fix for which the alternate information is being provided.</xs:documentation></xs:annotation></xs:element><xs:element name="viaSID" type="ViaSID" minOccurs="0" maxOccurs="1"/><xs:element name="viaEnrouteLegs" type="ViaEnrouteLeg" minOccurs="0" maxOccurs="unbounded"/><xs:element name="viaSTAR" type="ViaSTAR" minOccurs="0" maxOccurs="1"/><xs:element name="viaApproachConnectorLegs" type="ViaEnrouteLeg" minOccurs="0" maxOccurs="unbounded"/><xs:element name="viaApproach" type="ViaApproach" minOccurs="0" maxOccurs="1"/><xs:element name="alternateRef" type="type:PointReference" minOccurs="1" maxOccurs="1"/></xs:sequence><xs:attribute name="referenceID" use="required" type="xs:ID"/></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="AlternateDistance"><xs:annotation><xs:documentation>This field is used to supply the distance in nautical miles from the “To Airport/Heliport/Fix” to the Alternate Airport/Heliport.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceIntegerNMFourDigits"/></xs:simpleType>
<xs:simpleType name="CostIndex"><xs:annotation><xs:documentation>The Cost Index field is used to define the relative value of fuel-related costs and time-related costs for a particular route.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
<xs:simpleType name="CruiseAltitude"><xs:annotation><xs:documentation>This field will be used to establish an Enroute Cruise Altitude. It will be entered on Company Route records as specified by the customer.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="5"/></xs:restriction></xs:simpleType>
This field has two uses depending on the VIA field and File Code for To Fix. For VIA field content of ALT this field will contain the Alternate Airport Ident or Heliport Ident for this Company Route. If the file code for To Fix contains P, this field will contain the Airport Ident for REGN CODE (Section 5.41) of Terminal Waypoints (PC records) and Runway (PG records). If the file code for To Fix contains H, this field will contain the Heliport Ident for REGN CODE (Section 5.41) of Helicopter Terminal Waypoints (HC records).
<xs:simpleType name="TerminalAlternateAirport"><xs:annotation><xs:documentation>This field has two uses depending on the VIA field and File Code for To Fix. For VIA field content of ALT this field will contain the Alternate Airport Ident or Heliport Ident for this Company Route. If the file code for To Fix contains P, this field will contain the Airport Ident for REGN CODE (Section 5.41) of Terminal Waypoints (PC records) and Runway (PG records). If the file code for To Fix contains H, this field will contain the Heliport Ident for REGN CODE (Section 5.41) of Helicopter Terminal Waypoints (HC records).</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="4"/></xs:restriction></xs:simpleType>
<xs:complexType name="ViaSID"><xs:annotation><xs:documentation>This data type contains all of the information that is needed to identify parts of a SID used in the company route</xs:documentation></xs:annotation><xs:sequence><xs:element name="sidRef" type="xs:IDREF" minOccurs="1" maxOccurs="1"/><xs:element name="SIDSelectedRoutes" type="SIDSTARSelectedRoutes" minOccurs="1" maxOccurs="1"/><xs:element name="cycleDate" type="type:CycleDate" minOccurs="1" maxOccurs="1"/><xs:element minOccurs="0" name="cruiseAltitude" type="type:Altitude"/></xs:sequence></xs:complexType>
<xs:complexType name="SIDSTARSelectedRoutes"><xs:annotation><xs:documentation>This datatype contains the routes that are selected for ViaSIDs and ViaSTARs as part of the CompanyRoute.</xs:documentation></xs:annotation><xs:sequence><xs:element name="viaEnroute" type="ViaEnroute" minOccurs="0" maxOccurs="1"/><xs:element name="viaCommon" type="ViaCommon" minOccurs="0" maxOccurs="1"/><xs:element name="viaRunway" type="ViaRunway" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="ViaEnroute"><xs:annotation><xs:documentation>This data type defines the enroute portion of the SID/STAR selected for this company route.</xs:documentation></xs:annotation><xs:sequence><xs:element name="enrouteIdent" type="type:CoreIdentifier" minOccurs="1" maxOccurs="1"/><xs:element name="toFixRef" type="type:PointReference" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="ViaCommon"><xs:annotation><xs:documentation>This data type defines the common portion of the SID/STAR selected for this company route.</xs:documentation></xs:annotation><xs:sequence><xs:element name="commonIdent" type="type:CoreIdentifier" minOccurs="1" maxOccurs="1"/><xs:element name="toFixRef" type="type:PointReference" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="ViaRunway"><xs:annotation><xs:documentation>This data type defines the runway portion of the SID/STAR selected for this company route.</xs:documentation></xs:annotation><xs:sequence><xs:element name="runwayIdent" type="type:CoreIdentifier" minOccurs="1" maxOccurs="1"/><xs:element name="toFixRef" type="type:PointReference" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="ViaEnrouteLeg"><xs:annotation><xs:documentation>This data type is a child of Leg and allows for a choice between having the leg reference a fix or airway.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Leg"><xs:sequence><xs:element name="selectedEnroute" type="SelectedEnroute" minOccurs="1" maxOccurs="1"/><xs:element name="cruisingAltitude" type="type:Altitude" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="ViaSTAR"><xs:annotation><xs:documentation>This data type contains all of the information that is needed to identify parts of a STAR used in the company route</xs:documentation></xs:annotation><xs:sequence><xs:element name="starRef" type="xs:IDREF" minOccurs="1" maxOccurs="1"/><xs:element name="STARselectedRoutes" type="SIDSTARSelectedRoutes" minOccurs="1" maxOccurs="1"/><xs:element name="cycleDate" type="type:CycleDate" minOccurs="1" maxOccurs="1"/><xs:element minOccurs="0" name="cruiseAltitude" type="type:Altitude"/></xs:sequence></xs:complexType>
<xs:complexType name="ViaApproach"><xs:annotation><xs:documentation>This data type contains all of the information that is needed to identify parts of an Approach used in the company route</xs:documentation></xs:annotation><xs:sequence><xs:element name="approachRef" type="xs:IDREF" minOccurs="1" maxOccurs="1"/><xs:element name="cycleDate" type="type:CycleDate" minOccurs="1" maxOccurs="1"/><xs:element name="approachSelectedRoutes" type="ApproachSelectedRoutes" minOccurs="1" maxOccurs="1"/><xs:element name="cruiseAlt" type="type:Altitude" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="ControlledAirspace"><xs:annotation><xs:documentation>This following record contains the fields used in Controlled Airspace Records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Airspace"><xs:sequence><xs:element name="airspaceClassification" type="type:AirspaceClassification" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Classification” field will contain an alpha character indicating the published classification of the controlled airspace, when assigned.</xs:documentation></xs:annotation></xs:element><xs:element name="controlledAirspaceCenter" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Center” field is used to define the navigation element upon which the controlled airspace being defined is predicated, but not necessarily centered. Where the Airspace is not defined then the “Region Identifier” should be used. In this case, the Controlled Airspace Center will contain the ICAO Identification code for the Controlled Airspace to which the data contained in the record relates.</xs:documentation></xs:annotation></xs:element><xs:element name="controlledAirspaceType" type="enum:ControlledAirspaceType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Controlled Airspace Type” field is used to indicate the type of controlled airspace, using codes from the table below.</xs:documentation></xs:annotation></xs:element><xs:element name="rnp" type="type:RequiredNavigationPerformance" minOccurs="0" maxOccurs="1"/><xs:element name="airspaceSpeedRestriction" type="type:AirspaceSpeedRestriction" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>When government source provides a speed restriction then this element will be provided.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Airspace" abstract="true"><xs:complexContent><xs:extension base="A424Base"><xs:sequence><xs:element name="airspaceName" type="type:Name" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Airspace Name” field will contain the name of the airspace when assigned.</xs:documentation></xs:annotation></xs:element><xs:element name="multipleCode" type="type:MultipleCode" minOccurs="0" maxOccurs="1"/><xs:element name="timesOfOperation" type="type:TimesOfOperation" minOccurs="0" maxOccurs="1"/><xs:element name="unitIndicatorLower" type="enum:UnitIndicator" minOccurs="0" maxOccurs="1"/><xs:element name="unitIndicatorUpper" type="enum:UnitIndicator" minOccurs="0" maxOccurs="1"/><xs:element name="airspaceSegment" type="AirspaceSegment" minOccurs="1" maxOccurs="unbounded"/><xs:element name="upperLimit" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"/><xs:element name="lowerLimit" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"/><xs:element name="controllingAgency" type="type:ControllingAgency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
Restrictive Airspace lower and upper limits are specified as above mean sea level (MSL) or above ground level (AGL). This field permits the unit of measurement to be indicated.
<xs:simpleType name="UnitIndicator"><xs:annotation><xs:documentation>Restrictive Airspace lower and upper limits are specified as above mean sea level (MSL) or above ground level (AGL). This field permits the unit of measurement to be indicated.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Msl"><xs:annotation><xs:documentation>MSL</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Agl"><xs:annotation><xs:documentation>AGL</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="AirspaceSegment"><xs:annotation><xs:documentation>This following record contains the fields used in Airspace Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="arcBearing" type="type:ArcBearing" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Arc Bearing field contains the true bearing from the Arc Origin position to the beginning of the arc</xs:documentation></xs:annotation></xs:element><xs:element name="arcDistance" type="type:ArcDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Arc Distance” field is used to define the distance in nautical miles from the “ArcOrigin” position to the arc defining the lateral boundary of a FIR/UIR or Restrictive Airspace.</xs:documentation></xs:annotation></xs:element><xs:element name="arcOriginLocation" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element><xs:element name="boundaryVIA" type="enum:BoundaryVia" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Boundary VIA” defines the path of the boundary from the position identified in the record to the next defined position.</xs:documentation></xs:annotation></xs:element><xs:element name="isEndOfDescription" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="level" type="enum:Level" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Level field defines the airway structure of which the record is an element.</xs:documentation></xs:annotation></xs:element><xs:element name="location" type="type:Location" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element><xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Boundary Type Records - A boundary is defined by a series of records taken in order. The “Sequence Number” field defines the location of the record in the sequence defining a boundary.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="ArcBearing"><xs:annotation><xs:documentation>The “Arc Bearing” field contains the true bearing from the “Arc Origin” position to the beginning of the arc</xs:documentation></xs:annotation><xs:restriction base="type:BearingValue"/></xs:simpleType>
The “Arc Distance” field is used to define the distance in nautical miles from the “ArcOrigin” position to the arc defining the lateral boundary of a FIR/UIR or Restrictive Airspace.
<xs:simpleType name="ArcDistance"><xs:annotation><xs:documentation>The “Arc Distance” field is used to define the distance in nautical miles from the “ArcOrigin” position to the arc defining the lateral boundary of a FIR/UIR or Restrictive Airspace.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceNM"/></xs:simpleType>
<xs:simpleType name="BoundaryVia"><xs:annotation><xs:documentation>The “Boundary VIA” defines the path of the boundary from the position identified in the record to the next defined position.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Circle"><xs:annotation><xs:documentation>Circle</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GreatCircle"><xs:annotation><xs:documentation>Great Circle</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RhumbLine"><xs:annotation><xs:documentation>Rhumb Line</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CounterClockwiseArc"><xs:annotation><xs:documentation>Counter Clockwise ARC</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ClockwiseArc"><xs:annotation><xs:documentation>Clockwise ARC</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.
<xs:simpleType name="ControllingAgency"><xs:annotation><xs:documentation>Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="25"/></xs:restriction></xs:simpleType>
The “Controlled Airspace Classification” field will contain an alpha character indicating the published classification of the controlled airspace, when assigned.
<xs:simpleType name="AirspaceClassification"><xs:annotation><xs:documentation>The “Controlled Airspace Classification” field will contain an alpha character indicating the published classification of the controlled airspace, when assigned.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:pattern value="[A-G]"/><xs:length value="1"/></xs:restriction></xs:simpleType>
<xs:simpleType name="ControlledAirspaceType"><xs:annotation><xs:documentation>The “Controlled Airspace Type” field is used to indicate the type of controlled airspace, using codes from the table below.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="ClassC"><xs:annotation><xs:documentation>Class C Airspace (Was ARSA within the USA).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Control"><xs:annotation><xs:documentation>Control Area, ICAO Designation (CTA).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TerminalControl"><xs:annotation><xs:documentation>Terminal Control Area, ICAO Designation (TMA or TCA).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Radar"><xs:annotation><xs:documentation>Radar Zone or Radar Area (Was TRSA within the USA).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ClassB"><xs:annotation><xs:documentation>Class B Airspace (Was TCA with the USA).</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ClassD"><xs:annotation><xs:documentation>Class D Airspace within the USA, Control Zone, ICAO Designation (CTR).</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="AirspaceSpeedRestriction"><xs:annotation><xs:documentation>When government source provides a speed restriction then this element will be provided</xs:documentation></xs:annotation><xs:sequence><xs:element name="speedRestriction" type="type:SpeedLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>When used on a Controlled Airspace record, the field is used to describe a speed restriction within the Airspace</xs:documentation></xs:annotation></xs:element><xs:element name="speedAltitude" type="type:Altitude" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Speed Limit Altitude is the altitude below which speed limits may be imposed</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="RestrictiveAirspace"><xs:annotation><xs:documentation>This following record contains the fields used in Restrictive Airspace Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Airspace"><xs:sequence><xs:element name="ICAOCode" type="type:IcaoCode" minOccurs="0" maxOccurs="1"/><xs:element name="restrictiveAirspaceDesignation" type="type:RestrictiveAirspaceDesignation" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Designation” field contains the number or name that uniquely identifies the restrictive airspace.</xs:documentation></xs:annotation></xs:element><xs:element name="restrictiveAirspaceName" type="type:Name" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Name” field will contain the name of the restrictive airspace when assigned.</xs:documentation></xs:annotation></xs:element><xs:element name="restrictiveAirspaceType" type="enum:RestrictiveAirspaceType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Type” field is used to indicate the type of Airspace in which the flight of aircraft is prohibited or restricted. The restriction may be continuous or specified for certain times.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The Special Activity Area (SAA) file contains details relating to operation that could be hazardous to aeronautical navigation around a specified location
<xs:complexType name="SpecialActivityArea"><xs:annotation><xs:documentation>The Special Activity Area (SAA) file contains details relating to operation that could be hazardous to aeronautical navigation around a specified location</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="activityType" type="enum:ActivityType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Activity Type is used to define the type of Special Activity that is occurring.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationType" type="enum:CommunicationType" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationFrequency" type="xs:string" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Frequency” field specifies either transmit or receive frequency of the communication service, dependent on in which column the frequency is located. Each communication record will contain both transmit and receive frequencies unless the service is published as a Transmit Only or Receive Only service. The content will be identical if the service transmits and receives on the same frequency. The fields will be left blank when the service provided is a digital service.</xs:documentation></xs:annotation></xs:element><xs:element name="controllingAgency" type="type:ControllingAgency" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Some “Restrictive Airspace” areas are designated joint use and IFR operations in the area may be authorized by the controlling agency when it is not being utilized by the using agency.</xs:documentation></xs:annotation></xs:element><xs:element name="icaoCode" type="type:IcaoCode" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “ICAO Code” field permits records to be categorized geographically within the limits of the categorization performed by the “Area Code” field.</xs:documentation></xs:annotation></xs:element><xs:element name="location" type="type:Location" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of this point.</xs:documentation></xs:annotation></xs:element><xs:element name="publicMilitaryIndicator" type="enum:PublicMilitaryIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Airports can be classified into four categories, airports open to the general public, military airports, joint use civil and military, and airports closed to the public. This field permits these airports to be categorized by their use.</xs:documentation></xs:annotation></xs:element><xs:element name="saaIdentifier" type="type:SAAIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Activity Identifier” field contains the number or name that uniquely identifies the Special Activity Area.</xs:documentation></xs:annotation></xs:element><xs:element name="saaOperatingTimes" type="type:SpecialActivityAreaOperatingTimes" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Special Activity Area Operating Times field contains the annual expected operation schedule of the Special Activity.</xs:documentation></xs:annotation></xs:element><xs:element name="saaSize" type="type:SpecialActivityAreaSize" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Special Activity Area Size field contains the radius around the center point where the Special Activity is expected to occur.</xs:documentation></xs:annotation></xs:element><xs:element name="saaVolume" type="type:SpecialActivityAreaVolume" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Special Activity Area Volume” field contains the expected annual level of intensity of the Special Activity.</xs:documentation></xs:annotation></xs:element><xs:element name="specialActivityAreaName" type="type:Name" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Restrictive Airspace Name” field will contain the name of the restrictive airspace when assigned.</xs:documentation></xs:annotation></xs:element><xs:element name="unitIndicator" type="enum:UnitIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Restrictive Airspace lower and upper limits are specified as above mean sea level (MSL) or above ground level (AGL). This field permits the unit of measurement to be indicated.</xs:documentation></xs:annotation></xs:element><xs:element name="upperLimit" type="type:AltitudeLimit" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Special Use Airspace is described by both lateral and vertical boundaries. The “Lower/Upper Limit” fields contain the lower and upper limits of the FIR/UIR or Restrictive Airspace being described.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="ActivityType"><xs:annotation><xs:documentation>The Activity Type is used to define the type of Special Activity that is occurring.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Parachute"><xs:annotation><xs:documentation>Parachute Jump Area</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Glider"><xs:annotation><xs:documentation>Glider Operations</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HangGlider"><xs:annotation><xs:documentation>Hang Glider Activities</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="UltraLight"><xs:annotation><xs:documentation>Ultra Light Activities</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="SAAIdentifier"><xs:annotation><xs:documentation>The “Activity Identifier” field contains the number or name that uniquely identifies the Special Activity Area.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="6"/></xs:restriction></xs:simpleType>
<xs:complexType name="SpecialActivityAreaOperatingTimes"><xs:annotation><xs:documentation>The Special Activity Area Operating Times field contains the annual expected operation schedule of the Special Activity.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Alpha"><xs:sequence><xs:element name="holidayQualifier" type="enum:HolidayQualifier" minOccurs="1" maxOccurs="1"/><xs:element name="holidays" type="enum:Holidays" minOccurs="1" maxOccurs="1"/><xs:element name="timeOfUse" type="enum:TimeOfUse" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="HolidayQualifier"><xs:annotation><xs:documentation>The Special Activity Area Operating Times field contains the annual expected operation schedule of the Special Activity.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="IncludesHolidays"><xs:annotation><xs:documentation>Including Holidays</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ExcludesHolidays"><xs:annotation><xs:documentation>Excluding Holidays</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="U"><xs:annotation><xs:documentation>Unknown</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="Holidays"><xs:annotation><xs:documentation>The Special Activity Area Operating Times field contains the annual expected operation schedule of the Special Activity.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Continious"><xs:annotation><xs:documentation>Continuous</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Weekdays"><xs:annotation><xs:documentation>Weekdays</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Weekends"><xs:annotation><xs:documentation>Weekends</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Other"><xs:annotation><xs:documentation>Other</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unkown"><xs:annotation><xs:documentation>Unknown</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="WeekendsAndHolidays"><xs:annotation><xs:documentation>Weekends and holidays</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="TimeOfUse"><xs:annotation><xs:documentation>The Special Activity Area Operating Times field contains the annual expected operation schedule of the Special Activity.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="SrSs"><xs:annotation><xs:documentation>SR-SS</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Night"><xs:annotation><xs:documentation>Night Use</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Continious"><xs:annotation><xs:documentation>Continous</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ActiveByNotam"><xs:annotation><xs:documentation>Active by NOTAM</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="SpecialActivityAreaSize"><xs:annotation><xs:documentation>The Special Activity Area Size field contains the radius around the center point where the Special Activity is expected to occur.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
<xs:simpleType name="SpecialActivityAreaVolume"><xs:annotation><xs:documentation>The “Special Activity Area Volume” field contains the expected annual level of intensity of the Special Activity.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="1"/></xs:restriction></xs:simpleType>
<xs:simpleType name="FIRUIRAddress"><xs:annotation><xs:documentation>The “FIR/UIR Address” field contains the four character communication address of the FIR/UIR to supplement the FIR/UIR Ident.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="4"/></xs:restriction></xs:simpleType>
The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.
<xs:simpleType name="FIRUIRIdentifier"><xs:annotation><xs:documentation>The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="4"/></xs:restriction></xs:simpleType>
When used on Enroute Communication Records, the content definition above for the FIR/UIR Record is to be applied when ever the FIR/RDO (5.190) field of the Enroute Communication Record contains an Information Region Identifier. In all other cases, the Indicator field of the Enroute Communication Record will be blank.
<xs:simpleType name="FIRUIRIndicator"><xs:annotation><xs:documentation>When used on Enroute Communication Records, the content definition above for the FIR/UIR Record is to be applied when ever the FIR/RDO (5.190) field of the Enroute Communication Record contains an Information Region Identifier. In all other cases, the Indicator field of the Enroute Communication Record will be blank.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Fir"><xs:annotation><xs:documentation>FIR</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Uir"><xs:annotation><xs:documentation>UIR</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Combined"><xs:annotation><xs:documentation>Combined FIR/UIR</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="FIRUIRSegment"><xs:annotation><xs:documentation>The following record contains the fields used in FIR UIR Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="AirspaceSegment"><xs:sequence><xs:element name="adjacentFIRIdentifier" type="type:FIRUIRIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element><xs:element name="adjacentUIRIdentifier" type="type:FIRUIRIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “FIR/UIR Identifier” field identifies the Flight Information Region and Upper Information Region of airspace with defined dimensions within which Flight Information Service and Alerting Service are provided. The Identifier is for the controlling Area Control Center or Flight Information Center.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="FIRUIRName"><xs:annotation><xs:documentation>The “FIR/UIR Name” field contains the official name of the controlling agency of the FIR/UIR of which this record is an element.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="25"/></xs:restriction></xs:simpleType>
The “FIR/UIR ATC Reporting Units Altitude" is used to indicate the units of measurement concerning Altitude in the specific FIR/UIR to fulfill the requirements of ICAO flight plan.
<xs:simpleType name="FIRUIRATCReportingUnitsAltitude"><xs:annotation><xs:documentation>The “FIR/UIR ATC Reporting Units Altitude" is used to indicate the units of measurement concerning Altitude in the specific FIR/UIR to fulfill the requirements of ICAO flight plan.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="NotSpecified"><xs:annotation><xs:documentation>Not specified</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FlightLevel"><xs:annotation><xs:documentation>ALT in Flight Level</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Meters"><xs:annotation><xs:documentation>ALT in Meters</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Feet"><xs:annotation><xs:documentation>TAS in Feet</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The FIR/UIR ATC Reporting Units Speed is used to indicate the units of measurement concerning True Air Speed used in the specific FIR/UIR to fulfill the requirements of ICAO flight plan.
<xs:simpleType name="FIRUIRATCReportingUnitsSpeed"><xs:annotation><xs:documentation>The FIR/UIR ATC Reporting Units Speed is used to indicate the units of measurement concerning True Air Speed used in the specific FIR/UIR to fulfill the requirements of ICAO flight plan.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="NotSpecified"><xs:annotation><xs:documentation>Not specified</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Knots"><xs:annotation><xs:documentation>TAS in Knots</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Mach"><xs:annotation><xs:documentation>TAS in Mach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="KilometersHr"><xs:annotation><xs:documentation>TAS in Kilometers/hr</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Alternate Record file contains a listing of up to six Alternate Airport Identifiers or, up to six Alternate Company Route Identifiers or any combination of Alternate Airport or Alternate Route Identifiers for a given departure airport, destination airport or enroute fix. The data content of the record is customer defined.
<xs:complexType name="Alternate"><xs:annotation><xs:documentation>The Alternate Record file contains a listing of up to six Alternate Airport Identifiers or, up to six Alternate Company Route Identifiers or any combination of Alternate Airport or Alternate Route Identifiers for a given departure airport, destination airport or enroute fix. The data content of the record is customer defined.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="alternateDetails" type="type:AlternateDetails" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details of an Alternate.</xs:documentation></xs:annotation></xs:element><xs:element name="departureOrArrivalPort" type="DepatureOrArrivalPort" minOccurs="1" maxOccurs="1"/></xs:sequence><xs:attribute name="referenceID" use="required" type="xs:ID"/><!-- Do we need this? --></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="AlternateDetails"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details of an Alternate.</xs:documentation></xs:annotation><xs:sequence><xs:element name="alternateIdentifier" type="type:PointReference" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This element points to the airport or heliport element.</xs:documentation></xs:annotation></xs:element><xs:element name="distanceToAlternate" type="type:DistanceIntegerNM" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance To Alternate” field defines either the direct (geodesic) distance from the Destination Airport or Fix to the Alternate Airport or the along track distance of an alternate Company Routein nautical miles.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="CruisingTableLeg"><xs:annotation><xs:documentation>The Cruising Tables file contains details relating to available Cruising Levels for IFR flights.</xs:documentation></xs:annotation><xs:sequence><xs:element name="cruiseDetails" type="type:CruiseDetails" minOccurs="0" maxOccurs="4"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details of Cruise Level.</xs:documentation></xs:annotation></xs:element><xs:element name="cruiseTableIdentifier" type="type:CruiseTableIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>A standard cruising level table is established by ICAO and is to be observed except when, on the basis of regional air navigation agreements, a modified table of cruising levels is prescribed for use. This field permits the enroute airway record to identify the Cruise Table record that is to be used for cruise levels.</xs:documentation></xs:annotation></xs:element><xs:element name="magneticTrueIndicator" type="enum:MagneticTrueIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The field has multiple definitions. For Airport and Heliport Primary Records, it is used to indicate that all bearing and course detail for that airport are included in the data base with a reference to either Magnetic North or to True North. The field is blank in Airport Record when the data base contains a mix of magnetic and true bearing or course information for the airport. The Magnetic/True Indicator field is also used to indicate if the Course From and Course To fields of the Cruise Table record and the Sector Bearing fields of the MSA and TAA record are in magnetic or true degrees.</xs:documentation></xs:annotation></xs:element><xs:element name="sequenceNumber" type="type:SequenceNumber" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>For Record Types requiring more than one primary record to define the complete content – In a series of records used to define a complete condition, the “Sequence Number” is used to define each primary record in the sequence.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="CruiseDetails"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details of Cruise Level.</xs:documentation></xs:annotation><xs:sequence><xs:element name="cruiseLevelTo" type="type:CruiseLevelFromTo" minOccurs="1" maxOccurs="1"/><xs:element name="cuiseLevelFrom" type="type:CruiseLevelFromTo" minOccurs="1" maxOccurs="1"/><xs:element name="verticalSeparation" type="type:VerticalSeparation" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
The Cruise Level From field is used to indicate the lowest cruising level prescribed for use within the Course From/To fields. The Cruise Level To field is used to indicate the highest cruising level prescribed for use within the Course From/To fields.
<xs:simpleType name="CruiseLevelFromTo"><xs:annotation><xs:documentation>The Cruise Level From field is used to indicate the lowest cruising level prescribed for use within the Course From/To fields. The Cruise Level To field is used to indicate the highest cruising level prescribed for use within the Course From/To fields.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="5"/></xs:restriction></xs:simpleType>
<xs:simpleType name="VerticalSeparation"><xs:annotation><xs:documentation>The Vertical Separation field is used to indicate the minimum separation prescribed to be maintained between the cruising levels.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="5"/></xs:restriction></xs:simpleType>
<xs:complexType name="PreferedRoute"><xs:annotation><xs:documentation>This following record contains the fields used in Preferred Route Record.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Route"><xs:sequence><xs:element name="preferedRouteRouteType" type="enum:PreferedRouteRouteType" minOccurs="1" maxOccurs="1"/><xs:element name="timesOfOperation" type="type:TimesOfOperation" minOccurs="0" maxOccurs="1"/><xs:element name="preferedRouteLeg" type="PreferedRouteLeg" minOccurs="1" maxOccurs="unbounded"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:simpleType name="PreferedRouteRouteType"><xs:annotation><xs:documentation>The "Route Type" field defines the type of Preferred Route Records(ET)</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="NorthAmericanNorthAtlantic"><xs:annotation><xs:documentation>North American Route for North Atlantic Traffic</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Common"><xs:annotation><xs:documentation>Common Portion</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Preferntial"><xs:annotation><xs:documentation>Preferential Route</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PacificOceanTransition"><xs:annotation><xs:documentation>Pacific Oceanic Transition Routes (PACOTS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TacanAustralia"><xs:annotation><xs:documentation>TACAN Route - Australia</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NatNonCommon"><xs:annotation><xs:documentation>North American Routes for North Atlantic Traffic - Non-common Portion</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PeferredPreferentialOverfly"><xs:annotation><xs:documentation>Preferred/Preferential Overfly Routes</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Preferred"><xs:annotation><xs:documentation>Preferred Routes</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Tos"><xs:annotation><xs:documentation>Traffic Orientation System Routes (TOS)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Tec"><xs:annotation><xs:documentation>Tower Enroute Control Routes (TEC)</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="PreferedRouteLeg"><xs:annotation><xs:documentation>This following record contains the fields used in Preferred Route Leg.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Leg"><xs:sequence><xs:element name="aircraftUsageGroup" type="type:AircraftUsageGroup" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Aircraft Use Group” field provides information on what aircraft or groups of aircraft are permitted to use a certain route.</xs:documentation></xs:annotation></xs:element><xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "Altitude Description" field will designate whether a waypoint should be crossed "at," "at or above," "at or below" or "at or above to at or below" specified altitudes. The field is also used to designate recommended altitudes and cases where two distinct altitudes are provided at a single fix.</xs:documentation></xs:annotation></xs:element><xs:element name="areaCode" type="enum:AreaCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Customer Area Code” field permits the categorization of standard records by geographical area and of tailored records by the airlines for whom they are provided in the master file. Several record types do not adhere to the established geographical boundaries. There is no “AREA” in such records.</xs:documentation></xs:annotation></xs:element><xs:element name="directionRestriction" type="enum:PrefferedRouteDirectionalRestriction" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Direction Restriction” field will indicate whether the routing is available only in the direction of “from initial fix to terminus fix” or in both directions.</xs:documentation></xs:annotation></xs:element><xs:element name="intialAirportFix" type="type:InitialTerminusAirportFix" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.</xs:documentation></xs:annotation></xs:element><xs:element name="level" type="enum:Level" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Level field defines the airway structure of which the record is an element.</xs:documentation></xs:annotation></xs:element><xs:element name="maximumAltitude" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Maximum Altitude” field is used to indicate the maximum altitude allowed.</xs:documentation></xs:annotation></xs:element><xs:element name="minimumAltitude" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Record and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.</xs:documentation></xs:annotation></xs:element><xs:element name="preferedRouteUseIndicator" type="type:PreferedRouteUseIndicator" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.</xs:documentation></xs:annotation></xs:element><xs:element name="routeType" type="xs:string" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Route Type” field defines the type of Enroute Airway, Preferred Route, Airport and Heliport SID/STAR/Approach Routes of which the record is an element. For Airport and Heliport SID/STAR/Approach Routes, “Route Type” includes a “primary route type,” and up to two “route type qualifiers.”</xs:documentation></xs:annotation></xs:element><xs:element name="terminusAirportFix" type="type:InitialTerminusAirportFix" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.</xs:documentation></xs:annotation></xs:element><xs:element name="viaCode" type="enum:PreferredRouteVIACodes" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The "VIA Code" field is used to define the type of route used in the SID/STAR/Approach/Airways field (Section 5.78) on Company Route records and defines the type of route used in the AWY Identifier on Preferred Route records. On the Preferred Route records, some codes define the use, or restriction to use, of a fix or routing.</xs:documentation></xs:annotation></xs:element><xs:element name="airwayRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"/><xs:element name="procedureRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"/><xs:element name="alt1" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="alt2" type="type:Altitude" minOccurs="0" maxOccurs="1"/><xs:element name="initialAirportFixRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/><xs:element name="toTerminusFixRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="AircraftUsageGroup"><xs:annotation><xs:documentation>The Aircraft Use Group field provides information on what aircraft or groups of aircraft are permitted to use a certain route.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Alpha"><xs:sequence><xs:element name="aircraftOrAircraftGroup" type="enum:AircraftOrAircraftGroup" minOccurs="1" maxOccurs="1"/><xs:element name="alternateAircraftorAircraftGroup" type="type:AircraftUsageFieldContent2" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The Aircraft Use Group field provides information on what aircraft or groups of aircraft are permitted to use a certain route.This enumeration gives the Aircraft or Aircraft Group Code valid for Routing (Field 1)
Diagram
Type
restriction of xs:string
Facets
enumeration
All
All Aircraft
enumeration
AllSpeed250OrLess
All Aircraft, Cruise speed 250 kts or less
enumeration
NonJetAndTurboProp
Non-Jet and Turbo Prop
enumeration
MultiEnginePropsOnly
Multi-Engine Props Only
enumeration
JetsTurbopropsSpecialCruise190OrGreater
Jets and Turbo Props/Special, Cruise Speed 190 kts or greater
enumeration
Helicopter
Helicopter Only
enumeration
JetPower
Jet Power
enumeration
TurbopropSpecialCruise190orGreater
Turbo-Prop/Special, Cruise Speed 190 kts or greater
enumeration
NonJetNonTurboprop
Non-Jet, Non-Turbo Prop
enumeration
NonJetCruise190OrGreater
Non-Jet, Cruise speed 190 kts or greater
enumeration
NonJetCruise190OrLess
Non-Jet, Cruise speed 189 kts or less
enumeration
AircraftAsDefinedInNotes
Aircraft as defined in a Notes Continuation Record
<xs:simpleType name="AircraftOrAircraftGroup"><xs:annotation><xs:documentation>The Aircraft Use Group field provides information on what aircraft or groups of aircraft are permitted to use a certain route. This enumeration gives the Aircraft or Aircraft Group Code valid for Routing (Field 1)</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="All"><xs:annotation><xs:documentation>All Aircraft</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AllSpeed250OrLess"><xs:annotation><xs:documentation>All Aircraft, Cruise speed 250 kts or less</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NonJetAndTurboProp"><xs:annotation><xs:documentation>Non-Jet and Turbo Prop</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MultiEnginePropsOnly"><xs:annotation><xs:documentation>Multi-Engine Props Only</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="JetsTurbopropsSpecialCruise190OrGreater"><xs:annotation><xs:documentation>Jets and Turbo Props/Special, Cruise Speed 190 kts or greater</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Helicopter"><xs:annotation><xs:documentation>Helicopter Only</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="JetPower"><xs:annotation><xs:documentation>Jet Power</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TurbopropSpecialCruise190orGreater"><xs:annotation><xs:documentation>Turbo-Prop/Special, Cruise Speed 190 kts or greater</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NonJetNonTurboprop"><xs:annotation><xs:documentation>Non-Jet, Non-Turbo Prop</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NonJetCruise190OrGreater"><xs:annotation><xs:documentation>Non-Jet, Cruise speed 190 kts or greater</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NonJetCruise190OrLess"><xs:annotation><xs:documentation>Non-Jet, Cruise speed 189 kts or less</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AircraftAsDefinedInNotes"><xs:annotation><xs:documentation>Aircraft as defined in a Notes Continuation Record</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SingleEngine"><xs:annotation><xs:documentation>Single Engine</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TwinEngine"><xs:annotation><xs:documentation>Twin Engine</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="AircraftUsageFieldContent2"><xs:annotation><xs:documentation>The Aircraft Use Group field provides information on what aircraft or groups of aircraft are permitted to use a certain route.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="1"/></xs:restriction></xs:simpleType>
Simple Type enum:PrefferedRouteDirectionalRestriction
Namespace
http://www.arinc424.com/xml/enumerations
Annotations
The Direction Restriction field, when used on Enroute Airway records, will indicate the direction an Enroute Airway is to be flown. The Direction Restriction field, when used on Preferred Route records, will indicate whether the routing is available only in the direction of from initial fix to terminus fix or in both directions.
Diagram
Type
restriction of xs:string
Facets
enumeration
UniDirectional
Uni-directional Preferred Route, usable only from Initial Fix to Terminus Fix.
enumeration
BiDirectional
Bi-directional Preferred Route, usable from Initial Fix to Terminus Fix or from Terminus Fix to Initial Fix.
<xs:simpleType name="PrefferedRouteDirectionalRestriction"><xs:annotation><xs:documentation>The Direction Restriction field, when used on Enroute Airway records, will indicate the direction an Enroute Airway is to be flown. The Direction Restriction field, when used on Preferred Route records, will indicate whether the routing is available only in the direction of from initial fix to terminus fix or in both directions.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="UniDirectional"><xs:annotation><xs:documentation>Uni-directional Preferred Route, usable only from Initial Fix to Terminus Fix.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="BiDirectional"><xs:annotation><xs:documentation>Bi-directional Preferred Route, usable from Initial Fix to Terminus Fix or from Terminus Fix to Initial Fix.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.
<xs:simpleType name="InitialTerminusAirportFix"><xs:annotation><xs:documentation>The “Initial Fix” and the “Terminus Fix” fields are used to define the departure airport or initial fix and the destination airport or terminus fix of a preferred route.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="5"/></xs:restriction></xs:simpleType>
The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.
<xs:complexType name="PreferedRouteUseIndicator"><xs:annotation><xs:documentation>The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Alpha"><xs:sequence><xs:element name="preferredRouteUseIndicatorPointArea" type="enum:PreferredRouteUseIndicatorPointArea" minOccurs="1" maxOccurs="1"/><xs:element name="preferredRouteUseIndicatorRNAV" type="enum:PreferredRouteUseIndicatorRNAV" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
Simple Type enum:PreferredRouteUseIndicatorPointArea
Namespace
http://www.arinc424.com/xml/enumerations
Annotations
The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.
<xs:simpleType name="PreferredRouteUseIndicatorPointArea"><xs:annotation><xs:documentation>The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="P"><xs:annotation><xs:documentation>the route is point-to-point</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="A"><xs:annotation><xs:documentation>the route is area-to-area</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.
<xs:simpleType name="PreferredRouteUseIndicatorRNAV"><xs:annotation><xs:documentation>The “Preferred Route Use Indicator” provides information on whether the route in question is point-to-point and therefore usable for navigation, or area-to-area and usable only as advisory information which requires further processing. The field will also provide information on whether or not RNAV equipment is required to use the route.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="RnavEquipRequired"><xs:annotation><xs:documentation>RNAV equipment is required</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RnavEquipNotRequired"><xs:annotation><xs:documentation>RNAV equipment is NOT required</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The "VIA Code" field is used to define the type of route used in the SID/STAR/Approach/Airways field (Section 5.78) on Company Route records and defines the type of route used in the AWY Identifier on Preferred Route records. On the Preferred Route records, some codes define the use, or restriction to use, of a fix or routing.
<xs:simpleType name="PreferredRouteVIACodes"><xs:annotation><xs:documentation>The "VIA Code" field is used to define the type of route used in the SID/STAR/Approach/Airways field (Section 5.78) on Company Route records and defines the type of route used in the AWY Identifier on Preferred Route records. On the Preferred Route records, some codes define the use, or restriction to use, of a fix or routing.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AWY"><xs:annotation><xs:documentation>Designated Airway</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DIR"><xs:annotation><xs:documentation>Direct to Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="INT"><xs:annotation><xs:documentation>Initial Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RVF"><xs:annotation><xs:documentation>Route via Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="RNF"><xs:annotation><xs:documentation>Route via Fix not permitted</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SID"><xs:annotation><xs:documentation>Standard Instrument Departure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="STR"><xs:annotation><xs:documentation>Standard Terminal Arrival and Profile Descent</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="EnrouteCommunication"><xs:annotation><xs:documentation>This following record contains the fields used in Enroute Communication Records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Communication"><xs:sequence><xs:element name="firRDOIdent" type="type:FIRRDOIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “FIR/RDO Identifier” field used on Enroute Communication records is the source provided identifier for a communication service as used in message addressing. For Information Regions (FIR/UIR) it is the four-character identifier assigned to the Information Region as published in ICAO Document 7910, Location Indicators. For Flight Service Stations, it is the three or four character identifier assigned to the station by the relevant authority. For other communication services established for enroute use and not addressable under the Information Region, Flight Service Station concept, it is the identifier assigned by the relevant authority to that station for the purpose of addressing message traffic.</xs:documentation></xs:annotation></xs:element><xs:element name="firUirRef" type="xs:IDREF" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This element provides an IDREF to identify the FIRUIR element for the parent enrouteCommunication element.</xs:documentation></xs:annotation></xs:element><xs:element name="positionNarrative" type="type:PositionNarrative" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Position Narrative” field is a textual description of the location of a communication transmitter. This may be the name of a Remote Communication Outlet, a Remote Communication Air/Ground Station or the place name of the geographical location of the transmitter site.</xs:documentation></xs:annotation></xs:element><xs:element name="serviceIndicator" type="type:EnrouteCommunicationServiceIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Service Indicator” field is used to further define the use of the frequency for the specified Communication Type (5.101).</xs:documentation></xs:annotation></xs:element><xs:element name="assignedSectorName" type="type:AssignedSectorName" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Associated Sector Name” field is used to indicate the published name of an Enroute Communication Sector.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “FIR/RDO Identifier” field used on Enroute Communication records is the source provided identifier for a communication service as used in message addressing. For Information Regions (FIR/UIR) it is the four-character identifier assigned to the Information Region as published in ICAO Document 7910, Location Indicators. For Flight Service Stations, it is the three or four character identifier assigned to the station by the relevant authority. For other communication services established for enroute use and not addressable under the Information Region, Flight Service Station concept, it is the identifier assigned by the relevant authority to that station for the purpose of addressing message traffic.
<xs:simpleType name="FIRRDOIdentifier"><xs:annotation><xs:documentation>The “FIR/RDO Identifier” field used on Enroute Communication records is the source provided identifier for a communication service as used in message addressing. For Information Regions (FIR/UIR) it is the four-character identifier assigned to the Information Region as published in ICAO Document 7910, Location Indicators. For Flight Service Stations, it is the three or four character identifier assigned to the station by the relevant authority. For other communication services established for enroute use and not addressable under the Information Region, Flight Service Station concept, it is the identifier assigned by the relevant authority to that station for the purpose of addressing message traffic.</xs:documentation></xs:annotation><xs:restriction base="xs:string"/></xs:simpleType>
The “Position Narrative” field is a textual description of the location of a communication transmitter. This may be the name of a Remote Communication Outlet, a Remote Communication Air/Ground Station or the place name of the geographical location of the transmitter site.
<xs:simpleType name="PositionNarrative"><xs:annotation><xs:documentation>The “Position Narrative” field is a textual description of the location of a communication transmitter. This may be the name of a Remote Communication Outlet, a Remote Communication Air/Ground Station or the place name of the geographical location of the transmitter site.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="25"/></xs:restriction></xs:simpleType>
<xs:complexType name="EnrouteCommunicationServiceIndicator"><xs:annotation><xs:documentation>The Service Indicator field is used to further define the use of the frequency for the specified Communication Type (5.101).</xs:documentation></xs:annotation><xs:sequence><xs:element name="serviceIndicatorEnrouteFrequency" type="enum:ServiceIndicatorEnrouteFrequency" minOccurs="0" maxOccurs="1"/><xs:element name="serviceIndicatorEnrouteInformation" type="enum:ServiceIndicatorEnrouteInformation" minOccurs="0" maxOccurs="1"/><xs:element name="serviceIndicatorEnrouteService" type="enum:ServiceIndicatorEnrouteService" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="ServiceIndicatorEnrouteFrequency"><xs:annotation><xs:documentation>The Service Indicator field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AirGround"><xs:annotation><xs:documentation>Air/Ground</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Distance"><xs:annotation><xs:documentation>Discrete Frequency</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MF"><xs:annotation><xs:documentation>Mandatory Frequency (MF)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SF"><xs:annotation><xs:documentation>Secondary Frequency</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ServiceIndicatorEnrouteInformation"><xs:annotation><xs:documentation>The Service Indicator field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Vdf"><xs:annotation><xs:documentation>VHF Direction Finding Service (VDF)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotEnglish"><xs:annotation><xs:documentation>Language other than English</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MilitaryUseFreq"><xs:annotation><xs:documentation>Military Use Frequency</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="ServiceIndicatorEnrouteService"><xs:annotation><xs:documentation>The “Service Indicator” field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AEI"><xs:annotation><xs:documentation>Aeronautical Enroute Information</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FIS"><xs:annotation><xs:documentation>Flight Information Service (FIS)</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="AssignedSectorName"><xs:annotation><xs:documentation>The “Associated Sector Name” field is used to indicate the published name of an Enroute Communication Sector.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="25"/></xs:restriction></xs:simpleType>
The Geographical Reference Table file contains information that permits the cross referencing of otherwise undefined geographical entities and Route Identifiers in the Preferred Route file. The contents are not standardized and may vary from data supplier to data supplier. The contents of such a file can only be used in conjunction with the Preferred Route file of the same database in which the file is presented.
<xs:complexType name="GeographicalReference"><xs:annotation><xs:documentation>The Geographical Reference Table file contains information that permits the cross referencing of otherwise undefined geographical entities and Route Identifiers in the Preferred Route file. The contents are not standardized and may vary from data supplier to data supplier. The contents of such a file can only be used in conjunction with the Preferred Route file of the same database in which the file is presented.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="geographicalEntity" type="type:GeographicalEntity" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Geographical Reference Table will be used to identify “Geographical Entities” not definable by other established encoding systems. For established systems refer to Section 7 of this document.</xs:documentation></xs:annotation></xs:element><xs:element name="GeographicalRefTableID" type="type:GeographicalReferenceTableIdentifier" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Geographical Reference Table Identifier” will be used to provide a unique identification for each Geographical Entity. As the “Geographical Entity” field is a large field with no established content, this two character code will act as a pseudo key for the record.</xs:documentation></xs:annotation></xs:element><xs:element name="preferredRouteDetails" type="type:PreferredRouteDetails" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details Preferred Route Identifier and Preferred Route Use Indicator.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The Geographical Reference Table will be used to identify “Geographical Entities” not definable by other established encoding systems. For established systems refer to Section 7 of this document.
<xs:simpleType name="GeographicalEntity"><xs:annotation><xs:documentation>The Geographical Reference Table will be used to identify “Geographical Entities” not definable by other established encoding systems. For established systems refer to Section 7 of this document.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="29"/></xs:restriction></xs:simpleType>
Complex Type type:GeographicalReferenceTableIdentifier
Namespace
http://www.arinc424.com/xml/datatypes
Annotations
The “Geographical Reference Table Identifier” will be used to provide a unique identification for each Geographical Entity. As the “Geographical Entity” field is a large field with no established content, this two character code will act as a pseudo key for the record.
<xs:complexType name="GeographicalReferenceTableIdentifier"><xs:annotation><xs:documentation>The “Geographical Reference Table Identifier” will be used to provide a unique identification for each Geographical Entity. As the “Geographical Entity” field is a large field with no established content, this two character code will act as a pseudo key for the record.</xs:documentation></xs:annotation><xs:sequence><xs:element name="geographicalReferenceTableIdentifierPos1" type="type:GeographicalReferenceTableIdentifierPos1" minOccurs="1" maxOccurs="1"/><xs:element name="geographicalReferenceTableIdentifierPos2" type="type:GeographicalReferenceTableIdentifierPos2" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="PreferredRouteDetails"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details Preferred Route Identifier and Preferred Route Use Indicator.</xs:documentation></xs:annotation><xs:sequence><xs:element name="preferedRouteIdentifier" type="type:RouteIdentifier" minOccurs="0" maxOccurs="1"/><xs:element name="preferredRouteUseIndicator" type="type:PreferedRouteUseIndicator" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
This following record contains the fields used in Grid Mora Record. The Grid MORA table will contain records describing the MORA for each Latitude and Longitude block. Each record will contain thirty blocks and the “Starting Longitude” field defines the lower left corner for the first block of each record. Grid MORA values clear all terrain and obstructions by 1000 feet in areas where the highest elevations are 5000 feet MSL or lower. MORA values clear all terrain by 2000 feet in areas where the highest elevations are 5001 feet MSL or higher.
<xs:complexType name="GridMora"><xs:annotation><xs:documentation>This following record contains the fields used in Grid Mora Record. The Grid MORA table will contain records describing the MORA for each Latitude and Longitude block. Each record will contain thirty blocks and the “Starting Longitude” field defines the lower left corner for the first block of each record. Grid MORA values clear all terrain and obstructions by 1000 feet in areas where the highest elevations are 5000 feet MSL or lower. MORA values clear all terrain by 2000 feet in areas where the highest elevations are 5001 feet MSL or higher.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="startingPosition" type="type:Location" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Latitude and Longitude details of the lower left corner of the block of MORAs.</xs:documentation></xs:annotation></xs:element><xs:element name="mora" type="type:GridMORA" minOccurs="30" maxOccurs="30"><xs:annotation><xs:documentation>Grid Minimum Off-route Altitude (MORA) provides terrain and obstruction clearance within a one degree of latitude by one degree of longitude block. The first MORA in the list is for the block whose lower left corner is given by the startingPosition field. Each successive block is one degree of longitude east of the prior block. Within a single record, each MORA has the same latitude.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
Grid Minimum Off-route Altitudes (MORA) provides terrain and obstruction clearance within the section defined by the enclosing record. For unknown MORAs, the isUnknown flag will be set to true, and the altitude field will not be set.
<xs:complexType name="GridMORA"><xs:annotation><xs:documentation>Grid Minimum Off-route Altitudes (MORA) provides terrain and obstruction clearance within the section defined by the enclosing record. For unknown MORAs, the isUnknown flag will be set to true, and the altitude field will not be set.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isUnknown" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="altitude" type="type:AltitudeValue" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:complexType name="HoldingPattern"><xs:annotation><xs:documentation>This following record contains the fields used in Holding Pattern Records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="A424Record"><xs:sequence><xs:element name="isEnroute" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="arcRadius" type="type:ARCRadius" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “ARC Radius” field is used to define the radius of a precision turn. In Terminal Procedures, this is the “Constant Radius To A Fix” Path and Termination, for “RF” Leg. In Holding Patterns, this is the turning radius, inbound to outbound leg, for RNP Holding. The ARC Radius field is also used to specify the turn radius of RNP holding patterns included in SID, STAR, and Approach Records as HA, HF, and HM legs.</xs:documentation></xs:annotation></xs:element><xs:element name="duplicateIndicator" type="type:DuplicateIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Duplicate Identifier” field is used to further define holding patterns when official government source has designated more than one Holding Pattern on a Navaid or Waypoint.</xs:documentation></xs:annotation></xs:element><xs:element name="holdingPatternName" type="type:Name" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Name” field defines the name commonly applied to the navigation entity defined in the record.</xs:documentation></xs:annotation></xs:element><xs:element name="holdingSpeed" type="type:HoldingSpeed" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Holding Speed” will be the maximum speed in a holding pattern.</xs:documentation></xs:annotation></xs:element><xs:element name="holdingTime" type="xs:duration" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Leg Time field specifies the length of the inbound leg or outbound of a holding pattern in units of time. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the timing between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the timing from a point abeam the holding fix to the beginning of the inbound turn.</xs:documentation></xs:annotation></xs:element><xs:element name="holdingDistance" type="type:HoldingLegLength" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Leg Length field specifies the distance of either the inbound leg or the outbound leg of the holding pattern. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the distance between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the distance from a point abeam the holding fix to the beginning of the inbound turn.</xs:documentation></xs:annotation></xs:element><xs:element name="inboundHoldingCourse" type="type:Course" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Inbound Holding Course field defines the inbound course to the holding waypoint.</xs:documentation></xs:annotation></xs:element><xs:element name="legInboundOutboundIndicator" type="enum:LegInboundOutboundIndicator" minOccurs="0" maxOccurs="1"/><xs:element name="maximumAltitude" type="type:AltitudeLimit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Maximum Altitude” field is used to indicate the maximum altitude allowed.</xs:documentation></xs:annotation></xs:element><xs:element name="minimumAltitude" type="type:Altitude" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Altitude/Minimum Altitude” field indicates the reference altitude associated with (1) Enroute Airways (MEA, MFA or other minimum altitudes as defined by source), (2) holding pattern path of Holding Pattern record, (3) altitudes at fixes in terminal procedures and terminal procedure path termination defined by the Path Terminator in the Airport or Heliport SID/STAR/Approach Record and (4) lowest altitude of the “blocked altitudes” for a Preferred Route.</xs:documentation></xs:annotation></xs:element><xs:element name="RNP" type="type:RequiredNavigationPerformance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.</xs:documentation></xs:annotation></xs:element><xs:element name="rvsmMaximumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Maximum Level is the highest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element><xs:element name="rvsmMinimumLevel" type="type:FlightLevel" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>RVSM Minimum Level is the lowest defined cruising level for an airway or holding pattern.</xs:documentation></xs:annotation></xs:element><xs:element name="turnDirection" type="enum:Turn" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Turn” field specifies the direction in which holding pattern turns are to be made.</xs:documentation></xs:annotation></xs:element><xs:element name="verticalScaleFactor" type="type:VerticalScaleFactor" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Vertical Scale Factor (VSF) is used to set the vertical deviation scale.</xs:documentation></xs:annotation></xs:element><xs:element name="fixIdentifier" type="type:CoreIdentifier" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Fix Identifier” field contains the five-character-name-code, or other series of characters, with which the fix is identified. This includes Waypoint Identifiers, VHF NAVAID Identifiers, NDB NAVAID identifier, Airport Identifiers, and Runway Identifiers</xs:documentation></xs:annotation></xs:element><xs:element name="fixRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/><xs:element name="portRef" type="type:PointReference" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
The “Duplicate Indicator” field is used to further define holding patterns when official government source has designated more than one Holding Pattern on a Navaid or Waypoint.
<xs:complexType name="DuplicateIndicator"><xs:annotation><xs:documentation>The “Duplicate Indicator” field is used to further define holding patterns when official government source has designated more than one Holding Pattern on a Navaid or Waypoint.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Numeric"><xs:sequence><xs:element name="duplicatorIndicatorPos1" type="enum:DuplicateIndicatorPos1" minOccurs="1" maxOccurs="1"/><xs:element name="duplicatorIndicatorPos2" type="type:DuplicateIndicatorPos2" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="Numeric"><xs:annotation><xs:documentation>This Class represents the "Numeric" character type of the Arinc 424 data.</xs:documentation></xs:annotation><xs:sequence/></xs:complexType>
The “Duplicate Indicator” field is used to further define holding patterns when official government source has designated more than one Holding Pattern on a Navaid or Waypoint.
<xs:simpleType name="DuplicateIndicatorPos1"><xs:annotation><xs:documentation>The “Duplicate Indicator” field is used to further define holding patterns when official government source has designated more than one Holding Pattern on a Navaid or Waypoint.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Undefined"><xs:annotation><xs:documentation>Undefined (None Defined)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HighAlt"><xs:annotation><xs:documentation>High Altitude</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LowAlt"><xs:annotation><xs:documentation>Low Altitude</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Sid"><xs:annotation><xs:documentation>SID</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Star"><xs:annotation><xs:documentation>STAR</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Approach"><xs:annotation><xs:documentation>Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MissedApproach"><xs:annotation><xs:documentation>Missed Approach</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Undefined"><xs:annotation><xs:documentation>Undefined (with other defined)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AllAlt"><xs:annotation><xs:documentation>All Altitude</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
Position Two MultipleIf there is only one holding pattern on a given fix within an airspace structure, position 2 will contain a 0. For additional (multiple) holdings on that same fix within the same airspace structure, position 2 will be incremented by 1, e.g. 0 for the first 1 for the second, etc.
<xs:simpleType name="DuplicateIndicatorPos2"><xs:annotation><xs:documentation>Position Two Multiple If there is only one holding pattern on a given fix within an airspace structure, position 2 will contain a 0. For additional (multiple) holdings on that same fix within the same airspace structure, position 2 will be incremented by 1, e.g. 0 for the first 1 for the second, etc.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"/></xs:simpleType>
<xs:simpleType name="HoldingSpeed"><xs:annotation><xs:documentation>The “Holding Speed” will be the maximum speed in a holding pattern.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
The Leg Length field specifies the distance of either the inbound leg or the outbound leg of the holding pattern. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the distance between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the distance from a point abeam the holding fix to the beginning of the inbound turn (Figure 5-4).
<xs:simpleType name="HoldingLegLength"><xs:annotation><xs:documentation>The Leg Length field specifies the distance of either the inbound leg or the outbound leg of the holding pattern. The determination of inbound or outbound is identified by the content of Section 5.298 of the applicable record. Inbound is defined as the distance between the point at which the aircraft rolls out on the inbound leg of the holding pattern and the fix at which the holding pattern is defined. Outbound is defined as the distance from a point abeam the holding fix to the beginning of the inbound turn (Figure 5-4).</xs:documentation></xs:annotation><xs:restriction base="type:DistanceNM"><xs:totalDigits value="3"/><xs:fractionDigits value="1"/></xs:restriction></xs:simpleType>
<xs:simpleType name="Turn"><xs:annotation><xs:documentation>The Turn field specifies the direction in which holding pattern turns are to be made.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Left"><xs:annotation><xs:documentation>Left</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Right"><xs:annotation><xs:documentation>Right</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
A Universally Unique Identifier (UUID) consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens). For example: 550e8400-e29b-41d4-a716-446655440000. See RFC 4122 for further details
<xs:simpleType name="UUID"><xs:annotation><xs:documentation>A Universally Unique Identifier (UUID) consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens). For example: 550e8400-e29b-41d4-a716-446655440000. See RFC 4122 for further details</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:pattern value="[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}"/><xs:length value="36"/></xs:restriction></xs:simpleType>
The Helicopter Procedure Course field is used on Path Point Continuation Records to define the final approach course of procedures designed for helicopter operations to runways, to helipads, and to points in space..
<xs:simpleType name="HelicopterProcedureCourse"><xs:annotation><xs:documentation>The Helicopter Procedure Course field is used on Path Point Continuation Records to define the final approach course of procedures designed for helicopter operations to runways, to helipads, and to points in space..</xs:documentation></xs:annotation><xs:restriction base="type:CourseValue"><xs:totalDigits value="3"/><xs:fractionDigits value="0"/></xs:restriction></xs:simpleType>
<xs:simpleType name="ILSDMEBias"><xs:annotation><xs:documentation>This field is used to specify the DME offset</xs:documentation></xs:annotation><xs:restriction base="type:DistanceNMTwoDigits"/></xs:simpleType>
<xs:simpleType name="FrequencyProtectionDistance"><xs:annotation><xs:documentation>The “Frequency Protection Distance” field provides an indication of the distance to the next nearest NAVAID on the same frequency.</xs:documentation></xs:annotation><xs:restriction base="type:DistanceIntegerNM"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
The “Waypoint Name/Description” field sets the unabbreviated name of a named waypoint or a definition of an unnamed waypoint.
Diagram
Type
restriction of xs:string
Facets
maxLength
25
Source
<xs:simpleType name="WaypointNameDescription"><xs:annotation><xs:documentation>The “Waypoint Name/Description” field sets the unabbreviated name of a named waypoint or a definition of an unnamed waypoint.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="25"/></xs:restriction></xs:simpleType>
<xs:complexType name="ApproachWaypointDescription"><xs:annotation><xs:documentation>This class represents the additional waypoint description information used by approach procedure legs.</xs:documentation></xs:annotation><xs:sequence><xs:element name="isEngineOutDisarmPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFACF" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isMissedApproachPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFAF" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFinalEndPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isFixTurningFinalApproach" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Step-down fix on the final approach coding indicating a segment course change that is greater than or equal to one degree different than the next leg. All RF non-procedure fixes on the final approach coding meet this requirement. This code will take precedence over a step-down fix code at the same fix.</xs:documentation></xs:annotation></xs:element><xs:element name="isInitialApproachFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>An Initial Approach Fix is that fix designated by the government source documentations as the fix at which the Initial Approach segment begins. An Approach Procedure may have no IAF or multiple IAFs waypoints.</xs:documentation></xs:annotation></xs:element><xs:element name="isIntermediateApproachFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>An Intermediate Fix is a fix designated by government source documentation as the fix at which the Intermediate Approach Segment of the approach begins</xs:documentation></xs:annotation></xs:element><xs:element name="stepDownFix" type="enum:StepDownFix" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
The “Vertical Angle” field defines the angular portion of vertical navigation path in STAR Route and Approach Procedure Route records. The Vertical Angle should cause the aircraft to fly at the last coded altitude and then descend on the VNAV path, projected back from the fix and altitude contained in the route sequence that contains the Vertical Angle.
<xs:simpleType name="VerticalAngle"><xs:annotation><xs:documentation>The “Vertical Angle” field defines the angular portion of vertical navigation path in STAR Route and Approach Procedure Route records. The Vertical Angle should cause the aircraft to fly at the last coded altitude and then descend on the VNAV path, projected back from the fix and altitude contained in the route sequence that contains the Vertical Angle.</xs:documentation></xs:annotation><xs:restriction base="xs:decimal"><xs:maxExclusive value="15"/><xs:minInclusive value="0"/></xs:restriction></xs:simpleType>
The “Decision Height” fields are used to specify a specific height in the precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established
<xs:simpleType name="DecisionHeight"><xs:annotation><xs:documentation>The “Decision Height” fields are used to specify a specific height in the precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established</xs:documentation></xs:annotation><xs:restriction base="xs:int"/></xs:simpleType>
The Minimum Descent Height fields specify the lowest height, expressed in feet, to which descent is authorized on final approach or during circle-toland maneuvering in execution of a standard instrument approach procedure where no electric glide slope is provided.
<xs:simpleType name="MinimumDescentHeight"><xs:annotation><xs:documentation>The Minimum Descent Height fields specify the lowest height, expressed in feet, to which descent is authorized on final approach or during circle-toland maneuvering in execution of a standard instrument approach procedure where no electric glide slope is provided.</xs:documentation></xs:annotation><xs:restriction base="xs:int"/></xs:simpleType>
The “Enroute Alternate Airport/Heliport” field identifies the most suitable emergency airport or heliport along a Company Route or Helicopter Operations Company Route.
Diagram
Type
restriction of xs:string
Facets
length
4
Source
<xs:simpleType name="EnrouteAlternateAirportHeliport"><xs:annotation><xs:documentation>The “Enroute Alternate Airport/Heliport” field identifies the most suitable emergency airport or heliport along a Company Route or Helicopter Operations Company Route.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="4"/></xs:restriction></xs:simpleType>
The “Region Code” permits the categorization of waypoints and holding patterns as either enroute or terminal area waypoints. In the latter case the terminal area airport is identified in the field.
Diagram
Type
restriction of xs:string
Facets
maxLength
4
Source
<xs:simpleType name="RegionCode"><xs:annotation><xs:documentation>The “Region Code” permits the categorization of waypoints and holding patterns as either enroute or terminal area waypoints. In the latter case the terminal area airport is identified in the field.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="4"/></xs:restriction></xs:simpleType>
<xs:complexType name="NavaidLimitation"><xs:annotation><xs:documentation>This class represends the information in the 424 navaid limitation continuation record.</xs:documentation></xs:annotation><xs:sequence><xs:element name="navaidLimitationCode" type="enum:NavaidLimitationCode" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Limitation Codes” field is used to define the type of limitation to be expected with a VHF Navaid.</xs:documentation></xs:annotation></xs:element><xs:element name="componentAffectedIndicator" type="enum:ComponentAffectedIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The VHF Navaid File contains navaids that have one or two components - azimuth and/or distance. Published limitations may apply to one or both of the components. The “Component Affected Indicator” defines which component(s) are affected by the limitation.</xs:documentation></xs:annotation></xs:element><xs:element name="sectorDetails" type="type:SectorDetails" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a Sector.</xs:documentation></xs:annotation></xs:element><xs:element name="sequenceEndIndicator" type="type:SequenceEndIndicator" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Sequence End Indicator” field is used to define the end of a set of sequences defining a given limitation to a given VHF Navaid Component or Component pair.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="NavaidLimitationCode"><xs:annotation><xs:documentation>The Navaid Limitation Codes field is used to define the type of limitation to be expected with a VHF Navaid.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Coverage"><xs:annotation><xs:documentation>Coverage, the limitations are expressed as maximum reception reliability</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Fluctuations"><xs:annotation><xs:documentation>Fluctuations, radial(s) are affected by course fluctuations.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Roughness"><xs:annotation><xs:documentation>Roughness, signal roughness experienced in the sector(s) defined.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unreliable"><xs:annotation><xs:documentation>Unreliable in the sector(s), at the altitude(s), at the distance(s) defined.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Restricted"><xs:annotation><xs:documentation>Restricted in the sector(s), at the altitude(s), at the distance(s) defined</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unusable"><xs:annotation><xs:documentation>Unusable in the sector(s), at the altitude(s), at the distance(s) defined.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OutOfTollerance"><xs:annotation><xs:documentation>Out of Tolerance in the sector(s), at the altitude(s), at the distance(s) defined.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The VHF Navaid File contains navaids that have one or two components - azimuth and/or distance. Published limitations may apply to one or both of the components. The “Component Affected Indicator” defines which component(s) are affected by the limitation.
Diagram
Type
restriction of xs:string
Facets
enumeration
TacanOrVortacAzimuth
TACAN or VORTAC, TACAN azimuth component only affected.
enumeration
VorDmeOrVortacAzimuthAndDistance
VORDME or VORTAC, both azimuth and distance component affected.
enumeration
VordmeOrDmeDistance
VORDME or DME, distance component only affected.
enumeration
VortacOrTacanAzimth
VORTAC or TACAN, TACAN azimuth and distance component affected.
enumeration
TacanVortacDistance
TACAN or VORTAC, distance component affected.
enumeration
VorOrVordmeOrVorAzimuth
VOR, VORDME or VORDME, VOR azimuth component affected
enumeration
VorOrVordmeOrTacanOrVortacanAzimuth
VOR, VORDME or TACAN, VOR and TACAN azimuth and distance component affected.
<xs:simpleType name="ComponentAffectedIndicator"><xs:annotation><xs:documentation>The VHF Navaid File contains navaids that have one or two components - azimuth and/or distance. Published limitations may apply to one or both of the components. The “Component Affected Indicator” defines which component(s) are affected by the limitation.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="TacanOrVortacAzimuth"><xs:annotation><xs:documentation>TACAN or VORTAC, TACAN azimuth component only affected.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VorDmeOrVortacAzimuthAndDistance"><xs:annotation><xs:documentation>VORDME or VORTAC, both azimuth and distance component affected.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VordmeOrDmeDistance"><xs:annotation><xs:documentation>VORDME or DME, distance component only affected.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VortacOrTacanAzimth"><xs:annotation><xs:documentation>VORTAC or TACAN, TACAN azimuth and distance component affected.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="TacanVortacDistance"><xs:annotation><xs:documentation>TACAN or VORTAC, distance component affected.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VorOrVordmeOrVorAzimuth"><xs:annotation><xs:documentation>VOR, VORDME or VORDME, VOR azimuth component affected</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VorOrVordmeOrTacanOrVortacanAzimuth"><xs:annotation><xs:documentation>VOR, VORDME or TACAN, VOR and TACAN azimuth and distance component affected.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="SectorDetails"><xs:annotation><xs:documentation>This class is an abstraction used to represent the details for a Sector.</xs:documentation></xs:annotation><xs:sequence><xs:element name="altitudeDescription" type="enum:AltitudeDescription" minOccurs="1" maxOccurs="1"/><xs:element name="altitudeLimitation" type="type:AltitudeLimitation" minOccurs="1" maxOccurs="1"/><xs:element name="distanceDescription" type="enum:DistanceDescription" minOccurs="1" maxOccurs="1"/><xs:element name="distanceLimitationBegin" type="type:DistanceIntegerNM" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance Limitation” fields are used to define the distance range from the navaid at which the limitation applies.</xs:documentation></xs:annotation></xs:element><xs:element name="distanceLimitationEnd" type="type:DistanceIntegerNM" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Distance Limitation” fields are used to define the distance range from the navaid at which the limitation applies.</xs:documentation></xs:annotation></xs:element><xs:element name="sectorFrom" type="enum:SectorCodes" minOccurs="1" maxOccurs="1"/><xs:element name="sectorTo" type="enum:SectorCodes" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
<xs:simpleType name="AltitudeLimitation"><xs:annotation><xs:documentation>The “Altitude Limitation” field is used to define the altitude(s) at which the limitation applies.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="6"/></xs:restriction></xs:simpleType>
<xs:simpleType name="SectorCodes"><xs:annotation><xs:documentation>Sector Codes</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="000To015"><xs:annotation><xs:documentation>from 000 to 015</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="015To030"><xs:annotation><xs:documentation>From 015 to 030</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="030To045"><xs:annotation><xs:documentation>From 030 to 045</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="045To060"><xs:annotation><xs:documentation>From 045 to 060</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="060To075"><xs:annotation><xs:documentation>From 060 to 075</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="075To090"><xs:annotation><xs:documentation>From 075 to 090</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="090To105"><xs:annotation><xs:documentation>From 090 to 105</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="105To120"><xs:annotation><xs:documentation>From 105 to 120</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="120To135"><xs:annotation><xs:documentation>From 120 to 135</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="135to150"><xs:annotation><xs:documentation>From 135 to 150</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="150To165"><xs:annotation><xs:documentation>From 150 to 165</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="165To180"><xs:annotation><xs:documentation>From 165 to 180</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="180To195"><xs:annotation><xs:documentation>From 180 to 195</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="195To210"><xs:annotation><xs:documentation>From 195 to 210</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="210To225"><xs:annotation><xs:documentation>From 210 to 225</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="225To240"><xs:annotation><xs:documentation>From 225 to 240</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="240To225"><xs:annotation><xs:documentation>From 240 to 255</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="225To270"><xs:annotation><xs:documentation>From255 to 270</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="270To285"><xs:annotation><xs:documentation>From 270 to 285</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="285To300"><xs:annotation><xs:documentation>From 285 to 300</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="300To315"><xs:annotation><xs:documentation>From 300 to 315</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="315To330"><xs:annotation><xs:documentation>From 315 to 330</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="330To345"><xs:annotation><xs:documentation>From 330 to 345</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="345To000"><xs:annotation><xs:documentation>From 345 to 000</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Sequence End Indicator” field is used to define the end of a set of sequences defining a given limitation to a given VHF Navaid Component or Component pair.
<xs:simpleType name="SequenceEndIndicator"><xs:annotation><xs:documentation>The “Sequence End Indicator” field is used to define the end of a set of sequences defining a given limitation to a given VHF Navaid Component or Component pair.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="1"/></xs:restriction></xs:simpleType>
<xs:complexType name="ServiceIndicator"><xs:annotation><xs:documentation>The “Service Indicator” field is used to further define the use of the frequency for the specified Communication Type.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="type:Alpha"><xs:choice><xs:element name="airportHeliportCommunicationServiceIndicator" type="type:AirportHeliportCommunicationServiceIndicator" minOccurs="1" maxOccurs="1"/><xs:element name="enrouteCommunicationServiceIndicator" type="type:EnrouteCommunicationServiceIndicator" minOccurs="1" maxOccurs="1"/></xs:choice></xs:extension></xs:complexContent></xs:complexType>
The Final Approach Course as Runway field is a method of providing data for Point in Space approach procedure that are not to a runway.
Diagram
Type
restriction of xs:string
Facets
length
5
Source
<xs:simpleType name="FinalApproachCourseAsRunway"><xs:annotation><xs:documentation>The Final Approach Course as Runway field is a method of providing data for Point in Space approach procedure that are not to a runway.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:length value="5"/></xs:restriction></xs:simpleType>
The “Restriction Notes” field may contain any restriction not otherwise covered by the altitude or time restriction.
Diagram
Type
restriction of xs:string
Facets
maxLength
104
Source
<xs:simpleType name="RestrictionNotes"><xs:annotation><xs:documentation>The “Restriction Notes” field may contain any restriction not otherwise covered by the altitude or time restriction.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="104"/></xs:restriction></xs:simpleType>
The Level of Service field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for RNP.
<xs:simpleType name="RNPLevelOfService"><xs:annotation><xs:documentation>The Level of Service field identifies the official procedure level of service based on published procedure operating minimums information for Approach Procedures authorized for RNP.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="3"/></xs:restriction></xs:simpleType>
Simple Type type:PrimaryandAdditionalAlternateIdentifier
Namespace
http://www.arinc424.com/xml/datatypes
Annotations
The Primary Alternate Identifier and the Additional Alternate Identifiers (two through five) uniquely identify either an Alternate Airport or an Alternate Company Route. The determination of whether the content is an Airport Identifier or a Company Route Identifier is accomplished through the Alternate Type field.
Diagram
Type
restriction of xs:string
Facets
maxLength
10
Source
<xs:simpleType name="PrimaryandAdditionalAlternateIdentifier"><xs:annotation><xs:documentation>The Primary Alternate Identifier and the Additional Alternate Identifiers (two through five) uniquely identify either an Alternate Airport or an Alternate Company Route. The determination of whether the content is an Airport Identifier or a Company Route Identifier is accomplished through the Alternate Type field.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="10"/></xs:restriction></xs:simpleType>
<xs:simpleType name="Translation"><xs:annotation><xs:documentation>The “Translation” field is used to provide a decoding of a three character Communication Type (5.101).</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:maxLength value="80"/></xs:restriction></xs:simpleType>
<xs:complexType name="Minimums"><xs:annotation><xs:documentation>This class encapsulates the various minimum values, depending on the aircraft category</xs:documentation></xs:annotation><xs:sequence><xs:element name="aircraftCategory" type="type:AircraftCategory" minOccurs="1" maxOccurs="1"/><xs:element name="decisionHeight" type="type:DecisionHeight" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Decision Height” fields are used to specify a specific height in the precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established</xs:documentation></xs:annotation></xs:element><xs:element name="minimumDescentHeight" type="type:MinimumDescentHeight" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Minimum Descent Height fields specify the lowest height, expressed in feet, to which descent is authorized on final approach or during circle-toland maneuvering in execution of a standard instrument approach procedure where no electric glide slope is provided.</xs:documentation></xs:annotation></xs:element><xs:element name="radii" type="type:CategoryDistance" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The Category Radii fields, expressed in tenths of nautical miles, specifies the obstacle clearance area for aircraft maneuvering to land on a runway which is not aligned with the FAC of the approach procedure. The limits of the circling area are defined to be an arc from the center of the end of each usable runway. The extremities of the adjacent arcs are joined by lines drawn tangent to the arcs. The area thus enclosed is the circling approach area.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="OperationalConditions"><xs:annotation><xs:documentation>OperationalConditions is a class used to encapsulate the attributes related to RNP, and minimums.</xs:documentation></xs:annotation><xs:sequence><xs:element name="climbGradient" type="type:ClimbGradient" minOccurs="1" maxOccurs="1"/><xs:element name="minimums" type="type:Minimums" minOccurs="1" maxOccurs="1"/><xs:element name="minType" type="type:MinType" minOccurs="1" maxOccurs="1"/><xs:element name="rnp" type="type:RequiredNavigationPerformance" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>Required Navigation Performance (RNP) is a statement of the Navigation Performance necessary for operation within a defined airspace in accordance with ICAO Annex 15 and/or State published rules.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="RNPLevelOfServiceDetails"><xs:annotation><xs:documentation>This class contains the RNP Level of service details.</xs:documentation></xs:annotation><xs:sequence><xs:element name="rnpAuthorised" type="enum:LevelOfServiceAuthorised" minOccurs="1" maxOccurs="1"/><xs:element name="rnpLevelOfService" type="type:RNPLevelOfService" minOccurs="1" maxOccurs="1"/></xs:sequence></xs:complexType>
The “Localizer Width” field specifies the localizer course width of the ILS facility defined in the record.
Diagram
Type
restriction of xs:unsignedInt
Facets
totalDigits
4
Source
<xs:simpleType name="LocalizerWidth"><xs:annotation><xs:documentation>The “Localizer Width” field specifies the localizer course width of the ILS facility defined in the record.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedInt"><xs:totalDigits value="4"/></xs:restriction></xs:simpleType>
The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.
<xs:complexType name="VhfNavaidClass"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense. The field is made up of five columns of codes that define this information.</xs:documentation></xs:annotation><xs:sequence><xs:element name="vhfNavaidCoverage" type="enum:VhfNavaidCoverage" minOccurs="0" maxOccurs="1"/><xs:element name="vhfNavaidWeatherInfo" type="enum:NavaidWeatherInfo" minOccurs="0" maxOccurs="1"/><xs:element name="isNotCollocated" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isBiased" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isNoVoice" type="xs:boolean" minOccurs="0" maxOccurs="1"/></xs:sequence></xs:complexType>
The field VHFNavaidCoverage is the first character of the 5 character Navaid class. When used in VHF Navaid Record – Includes VOR, VORDME, VORTAC, TACAN, ILSDME and MLSDME type navaids.
Diagram
Type
restriction of xs:string
Facets
enumeration
Terminal
Terminal. Generally usable within 25NM of the facility and below 12000 feet
enumeration
Low
Low Altitude.Generally usable within 40NM of the facility and up to 18000 feet.
enumeration
High
High Altitude. Generally usable Within 130NM of the facility and up 60000 feet.
enumeration
Undefined
Undefined. Coverage not defined by government source.
enumeration
IlsTacan
ILS/TACAN. Full TACAN facility frequency-paired and operating with the same identifier as an ILS Localizer. Coverage is Terminal.
<xs:simpleType name="VhfNavaidCoverage"><xs:annotation><xs:documentation>The field VHFNavaidCoverage is the first character of the 5 character Navaid class. When used in VHF Navaid Record – Includes VOR, VORDME, VORTAC, TACAN, ILSDME and MLSDME type navaids.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Terminal"><xs:annotation><xs:documentation>Terminal. Generally usable within 25NM of the facility and below 12000 feet</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Low"><xs:annotation><xs:documentation>Low Altitude.Generally usable within 40NM of the facility and up to 18000 feet.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="High"><xs:annotation><xs:documentation>High Altitude. Generally usable Within 130NM of the facility and up 60000 feet.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Undefined"><xs:annotation><xs:documentation>Undefined. Coverage not defined by government source.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="IlsTacan"><xs:annotation><xs:documentation>ILS/TACAN. Full TACAN facility frequency-paired and operating with the same identifier as an ILS Localizer. Coverage is Terminal.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Step Climb Indicator” field is used to indicate if step climb up or down is permitted.
Diagram
Type
restriction of xs:string
Facets
enumeration
StepUpDownPermitted
Step climb up or down is permitted
enumeration
StepDownPermitted
Only step climb down is permitted
enumeration
NoStepPermitted
No step climb is permitted
enumeration
OnlyStepUpPermitted
Only step climb up is permitted
Source
<xs:simpleType name="StepClimbIndicator"><xs:annotation><xs:documentation>The “Step Climb Indicator” field is used to indicate if step climb up or down is permitted.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="StepUpDownPermitted"><xs:annotation><xs:documentation>Step climb up or down is permitted</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="StepDownPermitted"><xs:annotation><xs:documentation>Only step climb down is permitted</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NoStepPermitted"><xs:annotation><xs:documentation>No step climb is permitted</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OnlyStepUpPermitted"><xs:annotation><xs:documentation>Only step climb up is permitted</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “Restrictive Airspace Link Continuation” field is used to indicate cases where it is not possible to store all Enroute Airway to Restrictive Airspace Links in the Flight Planning Continuation Record defined in 4.6.3 (more than four area links required).
Diagram
Type
restriction of xs:string
Facets
enumeration
AddNotReq
additional Continuation Record is not required
enumeration
AddIsReq
additional Continuation Record is required
Source
<xs:simpleType name="RestrictiveAirspaceLink"><xs:annotation><xs:documentation>The “Restrictive Airspace Link Continuation” field is used to indicate cases where it is not possible to store all Enroute Airway to Restrictive Airspace Links in the Flight Planning Continuation Record defined in 4.6.3 (more than four area links required).</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AddNotReq"><xs:annotation><xs:documentation>additional Continuation Record is not required</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AddIsReq"><xs:annotation><xs:documentation>additional Continuation Record is required</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.
Diagram
Type
restriction of xs:string
Facets
enumeration
TerminalUse
Terminal Use (generally within 25NM)
enumeration
LowAlt
Low Altitude Use (generally within 40NM)
enumeration
HighAlt
High Altitude Use (generally within 130NM)
enumeration
ExtendedHighAlt
Extended High Altitude Use (generally beyond 130NM)
enumeration
NotNOTAMd
Navaid Not included in a civil international NOTAM system
<xs:simpleType name="FigureOfMerit"><xs:annotation><xs:documentation>The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="TerminalUse"><xs:annotation><xs:documentation>Terminal Use (generally within 25NM)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LowAlt"><xs:annotation><xs:documentation>Low Altitude Use (generally within 40NM)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HighAlt"><xs:annotation><xs:documentation>High Altitude Use (generally within 130NM)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="ExtendedHighAlt"><xs:annotation><xs:documentation>Extended High Altitude Use (generally beyond 130NM)</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NotNOTAMd"><xs:annotation><xs:documentation>Navaid Not included in a civil international NOTAM system</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OutOfService"><xs:annotation><xs:documentation>Navaid Out of Service</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Airport and Heliport SID/STAR/Approach Procedure Route Type supports the “All Sensor RNAV” Approach procedure. This kind of approach will have multiple sets of weather minimums (DH and NDA) associated with it. This field identifies the Procedure Categories for which these minimums apply.
Diagram
Type
restriction of xs:string
Facets
enumeration
LAAS
Local Area Differencial Augmentation System
enumeration
WAAS
Wide Area Differencial Augmentation System
enumeration
FMS
Flight Managment System
enumeration
GPS
Global Positioning System, no Augmentation
enumeration
VDME
VORDME, VORTACAN
enumeration
CIRC
Circle-to-Land
Source
<xs:simpleType name="ProcedureCategory"><xs:annotation><xs:documentation>The Airport and Heliport SID/STAR/Approach Procedure Route Type supports the “All Sensor RNAV” Approach procedure. This kind of approach will have multiple sets of weather minimums (DH and NDA) associated with it. This field identifies the Procedure Categories for which these minimums apply.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="LAAS"><xs:annotation><xs:documentation>Local Area Differencial Augmentation System</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="WAAS"><xs:annotation><xs:documentation>Wide Area Differencial Augmentation System</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="FMS"><xs:annotation><xs:documentation>Flight Managment System</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GPS"><xs:annotation><xs:documentation>Global Positioning System, no Augmentation</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VDME"><xs:annotation><xs:documentation>VORDME, VORTACAN</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CIRC"><xs:annotation><xs:documentation>Circle-to-Land</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The DME Operational Service Volume field is used to specify the service volume information of DME Navaids to support using DMEDME and DME-DME-IRU FMS capabilities in RNAV procedures and routes.
<xs:simpleType name="DMEOperationalServiceVolume"><xs:annotation><xs:documentation>The DME Operational Service Volume field is used to specify the service volume information of DME Navaids to support using DMEDME and DME-DME-IRU FMS capabilities in RNAV procedures and routes.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="40OrLess"><xs:annotation><xs:documentation>40NM or less</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="70OrLess"><xs:annotation><xs:documentation>70NM or less</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="130OrLess"><xs:annotation><xs:documentation>130NM or less</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="GreaterThan130"><xs:annotation><xs:documentation>Greater than 130NM</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unspecified"><xs:annotation><xs:documentation>Unspecified</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Procedure Design Mag Var Indicator field is an indication of how procedure design magnetic variation was provided in official source data for the procedure defined in the record/record set.
Diagram
Type
restriction of xs:string
Facets
enumeration
AppliesToAllProcedure
procedure mag var applies to all the proceure
enumeration
AppliesToLeg
procedure mag var applies to the associated leg
Source
<xs:simpleType name="ProcedureDesignMagVarIndicator"><xs:annotation><xs:documentation>The Procedure Design Mag Var Indicator field is an indication of how procedure design magnetic variation was provided in official source data for the procedure defined in the record/record set.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AppliesToAllProcedure"><xs:annotation><xs:documentation>procedure mag var applies to all the proceure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AppliesToLeg"><xs:annotation><xs:documentation>procedure mag var applies to the associated leg</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The "VIA Code" field is used to define the type of route used in the SID/STAR/Approach/Airways field (Section 5.78) on Company Route records and defines the type of route used in the AWY Identifier on Preferred Route records. On the Preferred Route records, some codes define the use, or restriction to use, of a fix or routing.
Diagram
Type
restriction of xs:string
Facets
enumeration
ALT
Alternate Airport
enumeration
APP
Approach Route
enumeration
APT
Approach Transition
enumeration
AWY
Designated Airway
enumeration
DIR
Direct to Fix
enumeration
INT
Initial Fix
enumeration
PRE
Preferred Route
enumeration
SID
Standard Instrument Departure
enumeration
SDE
Standard Instrument Departure - Enroute Transition
enumeration
SDY
Standard Instrument Departure - Runway Transition
enumeration
STR
Standard Terminal Arrival and Profile Descent
enumeration
STE
Standard Terminal Arrival and Profile Descent - Enroute Transition
enumeration
STY
Standard Terminal Arrival and Profile Descent - Runway Transition
Source
<xs:simpleType name="CompanyRouteVIACodes"><xs:annotation><xs:documentation>The "VIA Code" field is used to define the type of route used in the SID/STAR/Approach/Airways field (Section 5.78) on Company Route records and defines the type of route used in the AWY Identifier on Preferred Route records. On the Preferred Route records, some codes define the use, or restriction to use, of a fix or routing.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="ALT"><xs:annotation><xs:documentation>Alternate Airport</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="APP"><xs:annotation><xs:documentation>Approach Route</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="APT"><xs:annotation><xs:documentation>Approach Transition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AWY"><xs:annotation><xs:documentation>Designated Airway</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DIR"><xs:annotation><xs:documentation>Direct to Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="INT"><xs:annotation><xs:documentation>Initial Fix</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="PRE"><xs:annotation><xs:documentation>Preferred Route</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SID"><xs:annotation><xs:documentation>Standard Instrument Departure</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SDE"><xs:annotation><xs:documentation>Standard Instrument Departure - Enroute Transition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="SDY"><xs:annotation><xs:documentation>Standard Instrument Departure - Runway Transition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="STR"><xs:annotation><xs:documentation>Standard Terminal Arrival and Profile Descent</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="STE"><xs:annotation><xs:documentation>Standard Terminal Arrival and Profile Descent - Enroute Transition</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="STY"><xs:annotation><xs:documentation>Standard Terminal Arrival and Profile Descent - Runway Transition</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="NavaidSynchronization"><xs:annotation><xs:documentation>The “NavaidSynchronization” field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Synchronous"><xs:annotation><xs:documentation>Synchronous</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Asynchronous"><xs:annotation><xs:documentation>ASynchronous</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Unknown"><xs:annotation><xs:documentation>Unknown</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The “NavaidVoice” field identifies the characteristics of the NAVAID facility.
Diagram
Type
restriction of xs:string
Facets
enumeration
VoiceIdent
Voice Ident
enumeration
NoVoiceIdent
No Voice Ident
enumeration
Undefined
Undefined
Source
<xs:simpleType name="NavaidVoice"><xs:annotation><xs:documentation>The “NavaidVoice” field identifies the characteristics of the NAVAID facility.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="VoiceIdent"><xs:annotation><xs:documentation>Voice Ident</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NoVoiceIdent"><xs:annotation><xs:documentation>No Voice Ident</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Undefined"><xs:annotation><xs:documentation>Undefined</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Alternate Record Type field identifiers the record as being applicable to the departure airport (take-off alternate), destination airport (arrival alternate) or a fix along the route (enroute alternate).
Diagram
Type
restriction of xs:string
Facets
enumeration
AA
The Airport identifier in Columns 7 through 11 of the Primary Record are the identifier of the Arrival Airport.
enumeration
DA
The Airport identifier in Columns 7 through 11 of the Primary Record are the identifier of the Departure Airport.
enumeration
EA
The end fix of a Company Route is identified in Columns 7 through 15 of the Primary Record.
Source
<xs:simpleType name="AlternateRecordType"><xs:annotation><xs:documentation>The Alternate Record Type field identifiers the record as being applicable to the departure airport (take-off alternate), destination airport (arrival alternate) or a fix along the route (enroute alternate).</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AA"><xs:annotation><xs:documentation>The Airport identifier in Columns 7 through 11 of the Primary Record are the identifier of the Arrival Airport.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="DA"><xs:annotation><xs:documentation>The Airport identifier in Columns 7 through 11 of the Primary Record are the identifier of the Departure Airport.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="EA"><xs:annotation><xs:documentation>The end fix of a Company Route is identified in Columns 7 through 15 of the Primary Record.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The Alternate Type field is an information processing indicator. The Alternate Destination can be defined as an airport or an airport and route to an airport. This field defines that an alternate airport or, an company route is defined in the Alternate Identifier fields.
Diagram
Type
restriction of xs:string
Facets
enumeration
Airport
Airport is provided
enumeration
CompanyRoute
Company Route is provided
Source
<xs:simpleType name="AlternateType"><xs:annotation><xs:documentation>The Alternate Type field is an information processing indicator. The Alternate Destination can be defined as an airport or an airport and route to an airport. This field defines that an alternate airport or, an company route is defined in the Alternate Identifier fields.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Airport"><xs:annotation><xs:documentation>Airport is provided</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="CompanyRoute"><xs:annotation><xs:documentation>Company Route is provided</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="TypeRecognizedBy"><xs:annotation><xs:documentation>The Type Recognized By field is used to provide an indication of the provider of a given Communication Type (5.101).</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Icao"><xs:annotation><xs:documentation>The Communication Type is found in government source provided in accordance with ICAO standards.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Faa"><xs:annotation><xs:documentation>The Communication Type is found in government source provided in accordance with US FAA standards.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="IcaoAndFaa"><xs:annotation><xs:documentation>The Communication Type is found in government source provided in accordance with both ICAO and US FAA standards.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="LocalCountry"><xs:annotation><xs:documentation>The Communication Type is found in government source provided by the country in which the communication is used.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="OtherLocalCountry"><xs:annotation><xs:documentation>The Communication Type is found in government source provided by the country in which the communication is used.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="MadeUp"><xs:annotation><xs:documentation>The Communication Type has been established by the data supplier.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:simpleType name="UsedOn"><xs:annotation><xs:documentation>The Used On field provides an indication of what kind of communication records a particular Communication Type is used on.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="AirportComms"><xs:annotation><xs:documentation>Type is used on Airport Communication Records only</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="EnrouteComms"><xs:annotation><xs:documentation>Type is used on Enroute Communication Records only</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="HeliportComms"><xs:annotation><xs:documentation>Type is used on Heliport Communication Records only</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AirportHeliportEnrouteComms"><xs:annotation><xs:documentation>Type is used on Airport, Heliport and Enroute Communication Records</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="AiportHeliportComms"><xs:annotation><xs:documentation>Type is used on Airport and Heliport Communication Records</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
The field NDBNavaidAddInfo is the fourth character of the 5 character Navaid class, when used in NDB Navaid Record (NDBs and Terminal NDBs). It contains additional information on the Navaid.
Diagram
Type
restriction of xs:string
Facets
enumeration
Automatic
Automatic Transcribed Weather Broadcast.The frequency of this Navaid is used for the continuous broadcast of some sort of automated weather system such as AWOS, ASOS, TWEB, AWIB, AWIS.
enumeration
Scheduled
Scheduled Weather Broadcast.The frequency of this Navaid is used for the scheduled, non-continuous broadcast of some sort of automated weather system such as VOLMET.
enumeration
NoVoice
No Voice on Frequency.The frequency of this Navaid is not used to support two-way communication between a ground station and aircraft.
enumeration
VoiceTwoWay
Voice on Frequency.The frequency of this Navaid is used to support two-way communication between a ground station and aircraft.
Source
<xs:simpleType name="NDBNavaidAddInfo"><xs:annotation><xs:documentation>The field NDBNavaidAddInfo is the fourth character of the 5 character Navaid class, when used in NDB Navaid Record (NDBs and Terminal NDBs). It contains additional information on the Navaid.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:enumeration value="Automatic"><xs:annotation><xs:documentation>Automatic Transcribed Weather Broadcast.The frequency of this Navaid is used for the continuous broadcast of some sort of automated weather system such as AWOS, ASOS, TWEB, AWIB, AWIS.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="Scheduled"><xs:annotation><xs:documentation>Scheduled Weather Broadcast.The frequency of this Navaid is used for the scheduled, non-continuous broadcast of some sort of automated weather system such as VOLMET.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="NoVoice"><xs:annotation><xs:documentation>No Voice on Frequency.The frequency of this Navaid is not used to support two-way communication between a ground station and aircraft.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="VoiceTwoWay"><xs:annotation><xs:documentation>Voice on Frequency.The frequency of this Navaid is used to support two-way communication between a ground station and aircraft.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType>
<xs:complexType name="SidLeg"><xs:complexContent><xs:extension base="SidStarLeg"><xs:sequence><xs:element name="isEngineOutDisarmPoint" type="xs:boolean" minOccurs="0" maxOccurs="1"/><xs:element name="isInitialDepartureFix" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Initial Departure Fix indication, P in column 43, is coded for the first published fix/waypoint of an RNAV departure.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="CommunicationTypeTranslation"><xs:annotation><xs:documentation>This following record contains the fields used in Communication Type Translation Record.</xs:documentation></xs:annotation><xs:sequence><xs:element name="communicationType" type="enum:CommunicationType" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Type” is a three-character code indicating the type of communication service available on the frequency contained in the record. Decoding is available in the Communication Type Translation Table.</xs:documentation></xs:annotation></xs:element><xs:element name="communicationClass" type="enum:CommunicationClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Communication Class” field will designate the major grouping of the Communication Types contained in the record.</xs:documentation></xs:annotation></xs:element><xs:element name="translation" type="type:Translation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Translation” field is used to provide a decoding of a three character Communication Type (5.101).</xs:documentation></xs:annotation></xs:element><xs:element name="typeRecognizedBy" type="enum:TypeRecognizedBy" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Type Recognized By” field is used to provide an indication of the provider of a given Communication Type (5.101).</xs:documentation></xs:annotation></xs:element><xs:element name="usedOn" type="enum:UsedOn" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Used On” field provides an indication of what kind of communication records a particular Communication Type is used on.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="Vor"><xs:annotation><xs:documentation>This following record contains the fields used in VOR Records.</xs:documentation></xs:annotation><xs:complexContent><xs:extension base="Navaid"><xs:sequence><xs:element name="vorFrequency" type="type:Frequency" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>This data element identifies frequency information on the navaid.</xs:documentation></xs:annotation></xs:element><xs:element name="navaidClass" type="type:VhfNavaidClass" minOccurs="1" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense.</xs:documentation></xs:annotation></xs:element><xs:element name="dmeRef" type="type:PointReference" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field idenifies a reference to a DME navaid which originated in the same source data record as the VOR (i.e. is paired with the VOR)</xs:documentation></xs:annotation></xs:element><xs:element name="stationDeclination" type="type:StationDeclination" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>For VHF NAVAIDS, the “Station Declination” field contains the angular difference between true north and the zero degree radial of the NAVAID at the time the NAVAID was last site checked. For ILS localizers, the field contains the angular difference between true north and magnetic north at the localizer antenna site at the time the magnetic bearing of the localizer course was established.</xs:documentation></xs:annotation></xs:element><xs:element name="figureOfMerit" type="enum:FigureOfMerit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.</xs:documentation></xs:annotation></xs:element><xs:element name="frequencyProtection" type="type:FrequencyProtectionDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Frequency Protection” field provides an indication of the distance to the next nearest NAVAID on the same frequency.</xs:documentation></xs:annotation></xs:element><!-- Continuation records --><!-- Flight planning continuation records require: FIR, UIR. See A424Point --><!-- Simulation continuation records require:
- Mag var - in AeroPoint,
- Elevation - in Navaid
- Facility Characteristics --><!--navaidSynchronization and voice ident are the only facility characteristics subfields that apply to VHF Navaid/VOR --><xs:element name="navaidSynchronization" type="enum:NavaidSynchronization" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field identifies if the navaid is synchronized.</xs:documentation></xs:annotation></xs:element><!-- Navigation Limitation Continuation Record (see section 4.1.2.6) --><xs:element name="navaidLimitations" type="type:NavaidLimitation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field represents the navaid limitations.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
<xs:complexType name="DmeTacan" abstract="true"><xs:complexContent><xs:extension base="Navaid"><xs:sequence><xs:element name="vorFrequency" type="type:Frequency" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This data element identifies VHF frequency that corresponds to the actual DME or TACAN frequency.</xs:documentation></xs:annotation></xs:element><xs:element name="navaidClass" type="type:VhfNavaidClass" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Navaid Class” field provides information in coded format on the type of navaid, the coverage of the navaid, information carried on the navaid signal and collocation of navaids in both an electronic and aeronautical sense.</xs:documentation></xs:annotation></xs:element><xs:element name="dmeOperationalServiceVolume" type="enum:DMEOperationalServiceVolume" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The DME Operational Service Volume field is used to specify the service volume information of DME Navaids to support using DMEDME and DME-DME-IRU FMS capabilities in RNAV procedures and routes.</xs:documentation></xs:annotation></xs:element><xs:element name="ilsDmeLocation" type="enum:ILSDMELocation" minOccurs="0" maxOccurs="1"><!-- Part of facility characteristics --><xs:annotation><xs:documentation>This field identifies information about co-location with ILS facilities if the field is related to an ILS facility.</xs:documentation></xs:annotation></xs:element><xs:element name="ilsDMEBias" type="type:ILSDMEBias" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field is used to specify the DME offset</xs:documentation></xs:annotation></xs:element><xs:element name="routeInappropriateDME" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>A “Route Inappropriate Navaid Indicator” is used when a DME navaid has source provided information identifying the navaid as inappropriate for use in navigation solutions for one or more RNAV 1 and RNAV 2 routes.</xs:documentation></xs:annotation></xs:element><xs:element name="figureOfMerit" type="enum:FigureOfMerit" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The Figure of Merit field is used to denote those situations where information has been made available that indicate a VHF Navaid facility is usable beyond the range value that is specified through the Class field. It is also used to denote when a VHF Navaid contained in the database is not available for operational use, i.e., is out of service and to flag a VHF Navaid that is not included in a civilian international NOTAM system.</xs:documentation></xs:annotation></xs:element><xs:element name="isPaired" type="xs:boolean" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>Indicates whether this DME or TACAN originates from the same source record as a VOR with the same identifier.</xs:documentation></xs:annotation></xs:element><xs:element name="isMlsP" type="xs:boolean" minOccurs="0"><xs:annotation><xs:documentation>This field identifies if the navaid is part of a Precision MLS.</xs:documentation></xs:annotation></xs:element><xs:element name="frequencyProtection" type="type:FrequencyProtectionDistance" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>The “Frequency Protection” field provides an indication of the distance to the next nearest NAVAID on the same frequency.</xs:documentation></xs:annotation></xs:element><!-- Navigation Limitation Continuation Record (see section 4.1.2.6) --><xs:element name="navaidLimitations" type="type:NavaidLimitation" minOccurs="0" maxOccurs="1"><xs:annotation><xs:documentation>This field represents the navaid limitations.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:extension></xs:complexContent></xs:complexType>
Contains the date when the file was created. Format is DD-MMMYYYY. Where DD is the two-digit decimal day of month, MMM is a three-character month abbreviation, and YYYY is the four-digit decimal year. Contains the UTC time when the file was created. The format is two decimal digits each for hours, minutes, and seconds, separated by colons.
<xs:attribute name="creationDateTime" use="required" type="xs:dateTime"><xs:annotation><xs:documentation>Contains the date when the file was created. Format is DD-MMMYYYY. Where DD is the two-digit decimal day of month, MMM is a three-character month abbreviation, and YYYY is the four-digit decimal year. Contains the UTC time when the file was created. The format is two decimal digits each for hours, minutes, and seconds, separated by colons.</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="databasePartNumber" use="optional" type="xs:string"><xs:annotation><xs:documentation>Unique part number for database</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="dataSupplierIdent" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains information to identify the data supplier. Content defined by the data supplier.</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="desupplierTextField" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains description of file contents, or other information agreed upon by data supplier and customer.</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="endOfValidity" use="required" type="xs:dateTime"><xs:annotation><xs:documentation>This XML Attribute represents the end date of the validity of the data.</xs:documentation></xs:annotation></xs:attribute>
This field contains the 32 bit CRC value for the ARINC data file (including data and header records).ARINC Report 665, Loadable Software Standards, Section 4.0 defines the use of CRC codes.The CRC Polynomial used to calculate the CRC of the ARINC 424 data file shall be the 32-bit CRC (0x04C11DB7), calculated as described in ARINC Report 665
<xs:attribute name="fileCRC" use="optional" type="xs:int"><xs:annotation><xs:documentation>This field contains the 32 bit CRC value for the ARINC data file (including data and header records).ARINC Report 665, Loadable Software Standards, Section 4.0 defines the use of CRC codes. The CRC Polynomial used to calculate the CRC of the ARINC 424 data file shall be the 32-bit CRC (0x04C11DB7), calculated as described in ARINC Report 665</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="recordCount" use="optional" type="xs:int"><xs:annotation><xs:documentation>Contains the decimal count of the number of XML data Elements in the file.</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="startOfValidity" use="required" type="xs:dateTime"><xs:annotation><xs:documentation>This XML Attribute field is used to represent the effective date of the data.</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="supplierTextField" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains information specific to data supplier, contents to be defined by data supplier</xs:documentation></xs:annotation></xs:attribute>
Contains information to identify the data user/customer (for example, the customer name(s), file codes). Content defined by the data supplier and/or customer.
<xs:attribute name="targetCustomerIdent" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains information to identify the data user/customer (for example, the customer name(s), file codes). Content defined by the data supplier and/or customer.</xs:documentation></xs:annotation></xs:attribute>
Contains 3 decimal numbers to uniquely identify revision of this file. Initially set to 001, but will be incremented if the file is created more than once in the same cycle.
<xs:attribute name="versionNumber" use="optional" type="xs:int"><xs:annotation><xs:documentation>Contains 3 decimal numbers to uniquely identify revision of this file. Initially set to 001, but will be incremented if the file is created more than once in the same cycle.</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="codingRuleVersion" type="type:UUID"><xs:annotation><xs:documentation>This contains a version number of the coding rule specification used to capture this data set.</xs:documentation></xs:annotation></xs:attribute>
Contains the date when the file was created. Format is DD-MMMYYYY. Where DD is the two-digit decimal day of month, MMM is a three-character month abbreviation, and YYYY is the four-digit decimal year. Contains the UTC time when the file was created. The format is two decimal digits each for hours, minutes, and seconds, separated by colons.
This field contains the 32 bit CRC value for the ARINC data file (including data and header records).ARINC Report 665, Loadable Software Standards, Section 4.0 defines the use of CRC codes.The CRC Polynomial used to calculate the CRC of the ARINC 424 data file shall be the 32-bit CRC (0x04C11DB7), calculated as described in ARINC Report 665
Contains information to identify the data user/customer (for example, the customer name(s), file codes). Content defined by the data supplier and/or customer.
Contains 3 decimal numbers to uniquely identify revision of this file. Initially set to 001, but will be incremented if the file is created more than once in the same cycle.
Source
<xs:attributeGroup name="MetaData"><xs:annotation><xs:documentation>Basic Attribute Group which contains the start, end dates of the Cycle and other header Information.</xs:documentation></xs:annotation><xs:attribute name="creationDateTime" use="required" type="xs:dateTime"><xs:annotation><xs:documentation>Contains the date when the file was created. Format is DD-MMMYYYY. Where DD is the two-digit decimal day of month, MMM is a three-character month abbreviation, and YYYY is the four-digit decimal year. Contains the UTC time when the file was created. The format is two decimal digits each for hours, minutes, and seconds, separated by colons.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="cycleDate" use="optional" type="xs:int"><xs:annotation><xs:documentation>Contains Cycle Date</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="databasePartNumber" use="optional" type="xs:string"><xs:annotation><xs:documentation>Unique part number for database</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="dataSupplierIdent" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains information to identify the data supplier. Content defined by the data supplier.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="desupplierTextField" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains description of file contents, or other information agreed upon by data supplier and customer.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="endOfValidity" use="required" type="xs:dateTime"><xs:annotation><xs:documentation>This XML Attribute represents the end date of the validity of the data.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="fileCRC" use="optional" type="xs:int"><xs:annotation><xs:documentation>This field contains the 32 bit CRC value for the ARINC data file (including data and header records).ARINC Report 665, Loadable Software Standards, Section 4.0 defines the use of CRC codes. The CRC Polynomial used to calculate the CRC of the ARINC 424 data file shall be the 32-bit CRC (0x04C11DB7), calculated as described in ARINC Report 665</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="headerIdent" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains HDR</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="language" use="optional" type="xs:language"/><xs:attribute name="recordCount" use="optional" type="xs:int"><xs:annotation><xs:documentation>Contains the decimal count of the number of XML data Elements in the file.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="startOfValidity" use="required" type="xs:dateTime"><xs:annotation><xs:documentation>This XML Attribute field is used to represent the effective date of the data.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="supplierTextField" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains information specific to data supplier, contents to be defined by data supplier</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="targetCustomerIdent" use="optional" type="xs:string"><xs:annotation><xs:documentation>Contains information to identify the data user/customer (for example, the customer name(s), file codes). Content defined by the data supplier and/or customer.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="uuid" use="optional" type="type:UUID"/><xs:attribute name="versionNumber" use="optional" type="xs:int"><xs:annotation><xs:documentation>Contains 3 decimal numbers to uniquely identify revision of this file. Initially set to 001, but will be incremented if the file is created more than once in the same cycle.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="codingRuleVersion" type="type:UUID"><xs:annotation><xs:documentation>This contains a version number of the coding rule specification used to capture this data set.</xs:documentation></xs:annotation></xs:attribute></xs:attributeGroup>