5.1~5.10

5.1 总则 General

  5.1 General
  Chapter 5 sets forth definitions/descriptions and content for each type of field employed in the records discussed in Chapter 4. The following information is presented for each field:
   (i) Field Name (paragraph heading)
   (ii) Abbreviation used in proportional record layouts (Chapter 4) when different than Field Name (follows paragraph heading)
   (iii) Field Definition/Description
   (iv) Source/Content of each field
   (v) Length of field, expressed in number of characters
   (vi) Type of character allowed in each field, alpha or numeric or alpha/numeric
   (vii) Examples of field content when appropriate and/or necessary
  The following general rules apply to the format of all the fields:
   (i) All numeric fields, and the numeric parts of latitude, longitude, magnetic variation, negative elevation and station declination fields will be right justified and filled with leading zeros.
   (ii) All alpha and alpha/numeric fields will be left justified.
   (iii) Allowable field content of blank is defined as alpha/numeric content.

  5.1 总则
  第5章对第4章所述记录的各种字段的定义或描述、内容作出阐述。每一个字段都被赋予以下信息：
   (i)字段名(段落标题)
   (ii)当与字段名(跟在段落标题后面)不同时，在相应记录格式中使用的简缩字(第四章)
   (iii)字段的定义或描述
   (iv)每个字段的数据源或供选编码
   (v)字段的字节数, 用字节数表示
   (vi)每个字段中允许填写的数据类型, 字母或数字或字母与数字混合
   (vii)在必要或可能的情况下，提供的字段内容举例。
  下述通用规则适用于规范所有字段的格式:
   (i) 所有数字字段, 经纬度和磁差的数字部分, 负标高和导航台测量磁差经向右对其并前缀0.
   (ii) 所有字母字段和字母与数字混合字段将左对齐.
   (iii) 允许包含空格的字段被定义为字母与数字混合.

5.2 记录类型 Record Type (S/T)

  5.2 Record Type (S/T)
  Definition/Description: 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 (Section 1.2 of this Specification refers).Source/Content: The field contains the letter “S” when the field data are “standard” and the letter “T” when they are “tailored.”
  Used On: All records
  Length: 1 character
  Character Type: Alpha

  5.2 数据源类型(S/T)
  定义或描述：用于表示记录数据是否为标准型，即：适应用于全球应用，还是客户定制(即在主文件中包括为单独用户使用的特殊内容。参见本规定的1.2节)数据源或供选编码：标准数据，填写 “S”，而客户化数据则填写“T”。
  应用范围： 所有记录
  字节数： 1字符
  字符类型： 字母型

5.3 客户/区域码 Customer/Area Code (CUST/AREA)

  5.3 Customer/Area Code (CUST/AREA)
  Definition/Description: 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.
  Source/Content: “AREA” Codes should be derived from Figure 5-2. Airline codes should be derived from the standard list of abbreviated identifiers maintained and published in the IATA Airline Coding Directory. On Company Route and Preferred Route Records, an additional AREA field is used as a pointer to the AREA in which the Route Segment is located. For records, which do not follow geographical boundaries, the field is blank. For Preferred Routes, the field content is “PDR.”
  Used On: All records with content as defined above.
  Length: 3 characters max
  Character Type: Alpha
  Examples: Areas - USA, CAN, EUR
Customer - UAL, DAL, TWA
Preferred Routes - PDR

  5.3 客户/区域码
  定义或描述：允许对地理区域和提供的主文件中标注航空公司客户化记录进行分类。有些记录类型不遵守规定的地理边界，在这种记录中无区域(AREA)描述。数据源或供选编码：区域代码必须来自图5-2中。航空公司代码应使用IATA航空公司代码指南中公布的缩写代码。在公司航路和优选航线记录中，附加的AREA项应用于指明航段所在地区AREA。在记录中不遵守地理边界的，该域为空格。优选航线，该域填写“PDR”

  应用范围： 所有按上述规定定义的记录
  字节数： 最大3位
  字符类型： 字母
  举例： 地区-USA, CAN, EUR
客户-UAL, DAL, TWA
优选航路-PD

cs

5.4 章代码 Section Code (SEC CODE)

  5.4 Section Code (SEC CODE)
  Definition/Description: The “Section Code” field defines the major section of the navigation system data base in which the record resides.
  Source/Content: Figure 5-1 shows the data base section encoding scheme.
  Used On: All records
  Length: 1 character
  Character Type: Alpha

  5.4 章代码
  定义或描述：用于定义记录所在的导航数据库中主要部分。
  数据源或供选编码：见右表。
  应用范围：所有记录
  字节数：1字符
  字符类型：字母型

5.5 节代码 Subsection Code (SUB CODE)

  5.5 Subsection Code (SUB CODE)
  Definition/Description: The “Subsection Code” field defines the specific part of the database major section in which the record resides. Additionally, records that reference other records within the database use Section/Subsection Codes to make the reference, together with the record identifier. This is true for “fix” information in Holdings, Enroute Airways, Airport and Heliport SID/STAR/APPROACH, all kinds of Communications, Airport and Heliport MSA, Airport and Heliport TAA, Company Routes, Enroute Airway Restrictions, Preferred Routes and Alternate Records. The Section Code will define the major database section, the Subsection Code permits the exact section (file) to be identified and the “fix” (record) can then be located within this file.
  Source/Content: Figure 5-1 shows the database Subsection Encoding Scheme.
  Used On: All records
  Length: 1 character
  Character Type: Alpha

  5.5 节代码(SUB CODE)
  定义或描述：定义记录在数据库大的那一部分(字段)中的特定位置。此外，要参照数据库中其它记录的记录，应将字段/节编号与记录名称一起使用作为引用参照。在等待、航路航线、机场/直升机机场的SID/STAR/APP的“定位点”数据中，所有通信、机场/直升机机场的MSA，机场TAA、公司航路，航路航线的航路限制，优选航线和备降记录中完全按此方法使用。字段编号表示大的数据库部分，而“节编号”允许能够对确定的字段(文件)进行识别。这样，该“定位点”(记录)即可定位在该文件中。
  数据源或供选编码： 见上表
  应用范围： 所有记录
  字节数： 1位
  字符类型： 字母型

5.6 机场四字码 Airport/Heliport Identifier (ARPT/HELI IDENT)

  5.6 Airport/Heliport Identifier (ARPT/HELI IDENT)
  Definition/Description: The “Airport Identifier” and the “Heliport Identifier” fields contain the identification of the airport or heliport to which the data contained in the record relates.
  Source/Content: The content of this field is derived from official government sources. It will be the four characterICAO Location Identifier of the airport or heliport when such is published. It will be the three or four character Domestic Identifier when published and no ICAO Location Identifier is available for the airport or heliport. When used on Airport or Heliport Flight Planning Continuation Records, it will be the Airport or Heliport Identifier owning the terminal controlled airspace referenced in that record.
  Note: Within the continental United States and within Canada, in addition to using the published four character ICAO Location Identifiers, data suppliers append the character “K” for the USA or “C” for Canada to certain Domestic Identifiers to present an ICAO look-alike four character identifier.
COMMENTARY
  Where no officially published identifier is available, a data supplier may create a unique, temporary and unofficial identifier. Airports or Heliports within such identifiers may supply Tailored Data only and with full knowledge and concurrence of the data user.
Whenever possible, such temporary identifiers should be coordinated among the various data suppliers prior to its release.
  The content of this Airport/Heliport Identifier should not be confused with the perhaps more familiar ATA/IATA two or three character identifiers often user by airlines for other than navigation purposes. These ATA/IATA identifiers are included in the ARINC 424 database in accordance with Section 5.107 of this Specification.
Used On:
  Airport Identifier - VHF Navaid, NDB Navaid, Airport Terminal Waypoint, Airport, Airport Gate, Airport SID/STAR/Approach, Runway, Airport and Heliport Localizer, Airport and Heliport Localizer Marker, Holding Pattern, Airport Communications, Airport and Heliport MLS, GLS Airport MSA, Airport TAA, Path Point Flight Planning Arrival Departure Data, GLS Record, and Enroute Airway Restriction and Company Route to the Airport Identifier.
  Heliport Identifier - VHF Navaid, NDB Navaid, Heliport Terminal Waypoint, Heliport, Heliport SID/STAR/Approach, Airport and Heliport Localizer, Airport and Heliport Localizer Marker, Holding Pattern, Heliport Communications, Airport and MLS, GLS Heliport MSA, Heliport TAA, Path Point Flight Planning Arrival/Departure Data, GLS Records, and Enroute Airway Restriction and Company Route to the Airport Identifier.
  Length: 4 characters maximum
  Character Type: Alpha/numeric
  Examples: KJFK, DMIA, 9Y9, CYUL, EDDF, 53Y, CA14

  5.6 机场四字码
  定义或描述：国际民航组织为某机场指定的四字识别符，该项数据包括在记录有关内容中。
  数据源或供选编码：来源于政府部门，以ICAO 4字地名代码形式公布。如果无ICAO的地名代码，可为国内3字或4字代码。当应用于机场的计划续记录时，应为机场四码，
因为有关终端管制空域在其记录中。
  注：美国大陆和加拿大在使用公布的4字代码之外，数据商在其国内代码之前加K(美国)或C(加拿大)当作ICA0 4字代码使用。
  建议：无正式公布代码可供使用时，数据商可以生成一个唯一的、临时性非官方代码。有这样代号的机场，只有在数据用户了解和同意时才能提供客户化服务。只要可
能，应当在分发前就这种临时代码问题在几个数据商之间进行协调。
  机场代码不要与ATA/IATA的2字/3字代码混淆，航空公司常将这些代码应用于其它导航用途。这些代码在ARINC424数据库中按照5.107的标准规范使用。
  应用范围：VHF NAVAID、NDB NAVAID 、机场终端航路点、机场登机门、机场SID/STAR/APP、跑道、航向台、航向指点标(Localizer Marker)、等待程序、机场通信、ILS、MLS、GLS、机场MSA，机场TAA、航径点、飞行计划到达/离场数据和GLS记录以及航路航线限制和公司航路涉及的机场四码。
  字节数：最多4位
  字符类型：字母/数字
  举例：KJFK、DIMA、9Y9、CYUL、EDDF、53Y、CA14

5.7 航径类型 Route Type (RT TYPE)

  5.7 Route Type (RT TYPE)
  Definition/Description: 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 Approach Routes, “Route Type” includes a “primary route type,” and up to two “route type qualifiers.”
  Source/Content: The content of this field (for approach procedures) will be as indicated in the following tables:
  Used On: Enroute Airways, Airport and Heliport SID/STAR/Approach, Preferred Route
  Length: 1 character for Enroute Airways, Airport and Heliport SID and STAR and Preferred Routes.
3 characters for Airport and Heliport Approach primary records.
  Character Type: Alpha/numeric Approach
  Examples:
  LDC = a Localizer-based procedure, for localizer only, no glide slope, with DME required, Circle-To-Land Minimums.
  LNC = A Localizer-based procedure, for localizer only, no glide slope, DME not required, Circle-To-Land Minimums
  S S = A VOR procedure, using VORDME or VORTAC Navaid, the DME is not required for the procedure, the minimums are straight-in.
  S C = A VOR procedure, using VORDME or VORTAC Navaid, the DME is not required for the procedure, the minimums are Circle-To-Land
  D S = A VOR/DME procedure, using a VORDME or VORTAC Navaid, the DME is required for the procedure, the minimums are straight-in.
  V_S = A VOR procedure using VOR Navaid with only NAVAID, no DME installed, minimums are straight-in.
  V C = A VOR procedure, using a VOR Navaid with no DME capability, the minimums are Circle-To-Land
  N S = A NDB procedure, minimums are straight-in.
  Q S = A NDB + DME procedure, the DME is required, the minimums are straight-in.

  5.7 航径类型
  定义或描述： 用于定义高中低空航路、优选、机场的SIDs/STARs/APCH的类型，此类型用于表明此记录属于哪一种数据元素。对于机场的APCH，它包括一个“首选航径类型”和最多两个“航径类型限制词”。
  数据源/内容： 此字段的内容(就进近程序而言)应按照后续列表填写。
  应用范围： 航路航线、SID/STAR/APCH、优选航线、公司航路$19版。
  字节数： 航路航线、SID/STAR/APCH、优选航线使用1个字节，然而只能与相同记录不同位置的限定词1&2才能完整表达含义。
  字符属性： 字母/数字。
  进近举例：
  LDC=程序基于航向台，仅航向台无下滑台、要DME，用盘旋进近最低标准。
  LNC=程序基于航向台，仅航向台无下滑台、无DME，用盘旋进近最低标准。
  S_S=程序基于VOR(如VORDME、VORTAC)，无DME，用直线进近最低标准。
  S_C=程序基于VOR，用VORDME或VORTAC，程序不需DME设备，用盘旋进近最低标准。
  D_S=程序基于VOR，用VORDME或VORTAC，程序不需DME设备，用直线进近最低标准。
  V_S=程序基于VOR，仅用VOR、未装DME，用直线进近最低标准。
  V_C=程序基于VOR，是无DME能力的VOR台，用盘旋进近最低标准。
  N_S=程序基于NDB，用直线进近最低标准。
  Q_S=程序基于NDB+DME，需要DME，用直线进近最低标准。
  I_H=程序基于ILS，不需DME。为直升机向某机场某跑道运行设计，编码记录放在机场的进近（PF）文件中。
  I_ _=程序基于ILS，不需DME。为直升机向某直升机场某起降坪运行设计，编码记录放在直升机场的进近（HF）文件中

  Table 5-2 航路航线记录(ER)

  Table 5-3 优选航路记录(ET)

  Table 5-4 机场SID记录(PD)

  Table 5-6 机场STAR(PE)记录

  Table 5-7 机场进近程序记录 (PF)
以下关于进近航段类别的列表是按照字母顺序排序，并不表示优先。

  Table 5-8 机场进近程序记录(PF)

  Note 1: Qualifier 1 and 2 are carried on each sequence of every transition for Approach Procedure Coding (Approach Transition, Final Approach and Missed Approach) and will be identical for each sequence in a specific transition. Qualifier 2 will be different between Approach Transitions/Final approach coding where “S” or “C” will be used and Missed Approach where “A”, “B” or “E” will be used (See Note 6).
  注 1：在进近程序编码（进近过渡、最后进近和复飞进近）的每个过渡的每个序列中都携带限定符 1 和 2，并且在特定过渡的每个序列中都是相同的。在进近过渡/最后进近编码中，将使用“S”或“C”，而复飞进近中将使用“A”、“B”或“E”（见注 6），限定符 2 在进近过渡/最后进近编码和复飞进近之间会有所不同。

  Note 2: Route Type “R” is used for all types of RNAV procedure coding, excluding GLS Procedures that are coded as Route Type “J”. The type of RNAV Procedure is further defined through the content of Qualifier 1.
  a. Conventional Area Navigation Approach Procedures using RHO-RHO or RHO-THETA equipment are coded as Route Type “R” and Qualifier 1 of “T” or “V”.
  b. GNSS based RNAV Approach Procedures are coded as Route Type “R” with Qualifier 1 set to “J”, “L”, “R” or “U” as required by source publications and mapped to this table.
  注 2：路线类型“R”用于所有类型的 RNAV 程序编码，但 GLS 程序除外，GLS 程序被编码为路线类型“J”。RNAV 程序的类型通过限定符 1 的内容进一步定义。
  a. 使用 RHO-RHO 或 RHO-THETA 设备的常规区域导航进近程序被编码为航线类型“R”和限定符 1 为“T”或“V”。
  b. 基于全球导航卫星系统（GNSS）的 RNAV 进近程序被编码为路线类型“R”，限定符 1 根据源出版物的要求设置为“J”、“L”、“R”或“U”，并映射到此表。

  Note 3: In Approach Transition and Final Approach Coding, Qualifier 2 is set to “S” if the Approach Procedure is published with straight-in minimums or straight-in and circle-to-land minimums. Qualifier 2 is set to “C” if the Approach Procedure is published with circle-to-land minimums only. Qualifier 2 is required for all Route Types and is independent of the content of Qualifier 1.
  注 3：在进近过渡和最后进近编码中，如果进近程序公布的是直线进近最低标准或直线进近和盘旋进近最低标准，则限定符 2 设置为“S”。如果进近程序公布的仅为盘旋进近最低标准，则限定符 2 设置为“C”。限定符 2 对于所有航线类型都是必需的，并且与限定符 1 的内容无关。

  Note 4: A Qualifier 1 value of “W” is used to indicate that the RNAV Procedure is authorized for SBAS only and requires the ARINC 424 Path Point with the Final approach Segment (FAS) Data Block. No other navigation senor is authorized for these procedures. Examples:
  (1)A RNAV (GPS) or RNAV (GNSS) Approach Procedure is authorized for SBAS navigation and requires the FAS Data Block. The Route Type would be coded as “R” and Qualifier 1 would be coded as “W”. The associated GNSS/FMS Indicator (Section 5.222) would be set to indicate that SBAS is authorized. A Path Point Record carrying the FAS Data Block would be provided for the procedure. A Procedure Data Continuation Record would be provided and would be used to define the Levels of Service authorized and the official government source documentation Names for these Services.
  (2)A RNAV (GPS) or RNAV (GNSS) Approach Procedure is authorized for SBAS and also for single or multiple sensors other than SBAS. The Route Type would be coded as “R” and Qualifier 1 would be coded as “J” or “R”, as appropriate. The setting of the GNSS/FMS Indicator would be appropriate to the level of authorization. A Path Point Record would or would not be provided, according to government source publications. A Procedure Data Continuation Record would be provided and would be used to define the Levels of Services authorized for SBAS and the official government source documentation Names for these Services.
  (3)A RNAV (GPS) or RNAV (GNSS) Approach Procedure is authorized for a single or multiple sensors other than SBAS; SBAS is not authorized. The Route Type would be coded as “R” and Qualifier 1 would be coded as “J”, “R” “L”, “U” or “P” as appropriate. The setting of the GNSS/FMS Indicator would be appropriate to the level of authorization. No Path Point Record would be provided. No Procedure Data Continuation Record would be provided.
  注 4：“W”的限定符 1 值用于表明 RNAV 程序仅授权用于 SBAS，并需要带有最终进近段（FAS）数据块的 ARINC 424 路径点。对于这些程序，不授权使用任何其他导航传感器。例如：
  （1）RNAV（GPS）或 RNAV（GNSS）进近程序被授权用于 SBAS 导航，并且需要 FAS 数据块。路线类型将被编码为“R”，限定符 1 将被编码为“W”。相关的 GNSS/FMS 指示器（第 5.222 节）将被设置为表明 SBAS 已被授权。将为该程序提供携带 FAS 数据块的路径点记录。将提供程序数据延续记录，并将用于定义授权的服务级别和这些服务的官方政府源文档名称。
  （2）RNAV（GPS）或 RNAV（GNSS）进近程序被授权用于 SBAS，也适用于除 SBAS 以外的单个或多个传感器。路线类型将被编码为“R”，限定符 1 将根据情况被编码为“J”或“R”。GNSS/FMS 指示器的设置将与授权级别相适应。根据政府来源出版物，路径点记录可能会提供，也可能不会提供。将提供程序数据延续记录，并用于定义为 SBAS 授权的服务级别以及这些服务的官方政府来源文档名称。
  （3）RNAV（GPS）或 RNAV（GNSS）进近程序被授权用于除 SBAS 以外的单个或多个传感器；SBAS 未被授权。路线类型将被编码为“R”，限定符 1 将根据情况被编码为“J”、“R”、“L”、“U”或“P”。GNSS/FMS 指示器的设置应与授权级别相适应。不会提供路径点记录。不会提供程序数据延续记录。

  Note 5: The Qualifier 1 codes of “D” and “N” are not used on RNAV Procedures (Route Type “R”) of any kind. Additionally, these codes are not used in conjunction with Route Types that provide a “DME Option” of a procedure; specifically, they are not used in conjunction with the Route Types “D”, “N”, “Q”, “S” or “V”.
  注 5：“D”和“N”的限定符 1 代码在任何类型的 RNAV 程序（路线类型“R”）上均不使用。此外，这些代码也不与提供程序“DME 选项”的路线类型一起使用；具体而言，它们不与路线类型“D”、“N”、“Q”、“S”或“V”一起使用。

  Note 6: The Qualifier 2 codes of “A”, “B” and “E” can only be used in conjunction with a Route Type of “Z” = Missed Approach Coding. Qualifier 2 codes of “C” and “S” can be used in conjunction with any Route Type except “Z”.
  注 6：“A”、“B”和“E”的限定符 2 代码只能与“Z”的航线类型（即复飞编码）结合使用。“C”和“S”的限定符 2 代码可与除“Z”以外的任何航线类型结合使用。

5.8 航路航线代号 Route Identifier (ROUTE IDENT)

  5.8 Route Identifier (ROUTE IDENT)
  Definition/Description: The “Route Identifier” field identifies a route of flight or traffic orientation, using the coding employed on aeronautical navigation charts and related publications.
  Source/Content: For Enroute Airways, Route Identifier codes should be derived from official government publications. For Preferred Routes, Route Identifiers may or may not be provided in government publications. Where they are available, they will be used.
For North American Routes for North Atlantic Traffic, “Common Portion” and other similar route system, route identifier code shall be those published in government sources. For the European Traffic Orientation System or other similar route systems such as North American Routes for North Atlantic Traffic, “Non-common Portion,” Preferred Routes and Preferential Routes published without official and/or flight plan identifiers, but published as between specific airports or other navigation fixes, route identifiers define the initial fix and the terminus fix idents according to the naming rules in Chapter 7. For routings which do not include a unique initial or terminus fix, rules on creating unique Route Identifiers are also contained in Chapter 7. Those rules have been developed with use of the Geographical Reference Tables (TG). Refer to Chapter 3, Section 3.2.7.2 and Chapter 4, Section 4.1.26 for more detail.
  Used On: Enroute Airway, Preferred Route Records and Geographical Reference Table
  Length: Enroute Airway - 5 character maximum
Preferred Route - 10 character maximum
  Character Type: Alpha/numeric
  Examples:
  Enroute Airway - V216, C1150, J380, UA16, UB414
  Preferred Routes - N111B, TOS13, TOS14WK, CYYLCYYC, ARTCOLAR, KZTLKSAV, SCNDICANRY
  Refer to Section 7 for specific examples and their meaning.

  5.8 航路航线代号
  定义或描述：使用航图或其它出版物中采用的编码，标识一条飞行路线或一个交通流向。
  数据源或供选编码：
  (1)对于航路航线记录，航路航线代号应源自政府出版物。
  (2)对于优选航线记录，航路航线代号不一定来自政府出版物，在提供时，即可使用。
  (3)对于北大西洋交通网的北美航路，“共用部分”或其它类似的航路系统，航路航线代码应源自政府出版物。而欧洲交通系统或其它类似航线系统，例如飞往北大西洋交通网的北美航线、优选航线、无官方或飞行计划识别的优选航线，但其在特定机场或其它导航定位点之间公布的，航路航线代号根据第7章命名规则，定义起始定位点和终结定位点识别。关于无唯一起始定位点和终止定位的航线，第7章中同样载有生成航路航线代号的规定。应用优选航线列表(TG)已经制定出这些规则，详见第3章的3.2.7.2，第4章的4.1.26
  应用范围：航路、优选航线记录和优选航线列表
  字节数：航路为最多5位，优选航线最多10位
  字符类型：字母/数字
  举例：
  航路—V216、C1150、J380、UA16、UB414
  优选航线—N111B、 TOS13、TOS14WK、CYYLCYYC，ARTCOLAR、KZTLKSAV、SCNDICANRY参见第7章的举例及解释

5.9 SID/STAR程序代号 SID/STAR Route Identifier (SID/STAR IDENT)

  5.9 SID/STAR Route Identifier (SID/STAR IDENT)
  Definition/Description: “The SID/STAR Route Identifier” field contains the name of the SID or STAR, using the basic indicator, validity indicator and route indicator abbreviated to six characters with the naming rules in Chapter 7 of this document.
  Source/Content: SID/STAR route identifier codes should be derived from official government publications describing the terminal procedures structure.
  Used On: Airport SID/STAR, Heliport SID/STAR and Flight Planning Arrival/Departure Data Records
  Length: 6 characters max
  Character Type: Alpha/numeric
  Examples: DEPU2, SCK4, TRP7, 41M3, MONTH6

  5.9 SID/STAR程序代号
  定义或描述：包括SID 或STAR的名称，使用基本代码，时效性代码，按照第7章的定名规则，航线代号缩减为6位字符。
  数据源或供选编码：应来源于描述终端航线结构的政府出版物。
  应用范围：机场SID STAR和飞行计划的进场/离场数据记录。
  字节数：最多6位
  字符类型：字母/数字
  举例；DEPU2、SCK4、TRP7、41M3、MONTH6

5.10 进近程序标识 Approach Route Identifier (APPROACH IDENT)

  5.10 Approach Route Identifier (APPROACH IDENT)
  Definition/Description: 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.”
  Source/Content:

  For Approach procedures that are not specific to a runway such as circle-to-land procedures a 4 character Alpha entry should be used with the fifth alphanumeric character used for multiple indicator if necessary.
  For Helicopter Approach Procedures to Runways, the first position of the identifier will be the type of approach. The second through fourth positions will carry a three digit numeric character representing the runway designated or the procedure final approach course, expressed in full degrees. Where the same final approach course is used multiple times in official source, the fifth position will carry a multiple indicator.
  For Helicopter Approach Procedures to Heliports and coded to a specific pad, the first position of the identifier will carry a character indicating the type of approach. The second through sixth characters will carry the pad identification. There is no provision for a multiple indicator for more than one approach of the same type to the same pad in this identifier field. When required, a multiple indicator is provided in a separate field.
  Used On: Airport and Heliport Approach Route Records, Flight Planning Arrival/Departure Data, Path Point and Airport, Heliport Localizer, Airport and Heliport TAA, and Simulation Continuation Records.
  Length: 6 characters max.
  Character Type: Alpha/numeric
  Examples:
  Runway Dependent: I26L, B08R, R29, V01L, N35 L16RA, L16RB, V08-A, V08-B I18L1, I18L2, N08T R35-Y, R35-Z
  Circle-To-Land: VORA, VORB VOR-A, VOR-B, NDBB,CVOR, VDMA, LOCD,BI P168, NDAT (NDB, DME, Alpha, True), NDB-1, NDB-2
  Helicopter to Runway: I13L, L040, V175, N175B
  Helicopter to Helipad: IA127 = ILS Procedure to a pad designated A127
VBRAVO =VOR Procedure to a Pad designated BRAVO
N23 =NDB Procedure to a Pad designated 23 RWESTA RNAV Procedure to a Pad designated West Alpha

  5.10 进近程序标识
  定义或描述：包括所飞进近程序的识别。为方便提供一条特定跑道同类型的多个进近程序，该项可应用于多程序代码。
  不是专用于一条跑道的进近程序，例如盘旋着陆，填写4位字母，如果需要第5位填写字母数字型表示多用指示码。
  应用范围：机场SID/STAR/APP航线记录、飞行计划进场/离场数据、航径点和机场、直升机场航向台模拟续记录。
  字节数：最多6位
  字符类型：字母/数字
  举例：
  基于跑道－126L 、B08R 、R29、 V01L、 N35、 L16RA、L16RB 、V08-A 、V08-B、 I18L2、N08T、R35-Y、R35-Z；
  盘旋着陆－VORA、VORB、VOR-A、VOR-B、 NDBB 、CVOR 、VDMA、 LOCD 、BIP168、NDAT(NDB 、DME、字母、真名)、NDB-1、NDB-2

许可协议

本文采用 署名-非商业性使用-相同方式共享 4.0 国际 许可协议，转载请注明出处。

分享文章