5.11 过渡识别符 Transition Identifier (TRANS IDENT)
5.11 Transition Identifier (TRANS IDENT)
Definition/Description: The “Transition Identifier” field describes the type of transition to be made from the enroute environment into the terminal area and vice versa, and from the terminal area to the approach or from the runway or helipad to the terminal area.
Source Content: The content of the transition identifier field should be determined from the content of the Route Type field (See Section 5.7) in accordance with the rules set forth in Figure 5.3
Figure 5-3 Transition Identifier Field Content
Note 1: If there is no Route Type 1 or 4 or F for the SID, then the SID records with the Route Type of 2 or 5 or M will have an entry in the Transition Identifier field. If there is a Route Type of 1 or 4 or F for the procedure, then the records with the Route Type of 2 or 5 or M will carry a blank transition identifier field.
Note 2: If there is no Route Type 3 or 6 or 9 or S for the STAR, then the STAR record with the Route Type of 2 or 5 or 8 or M will have an entry in the Transition Identifier field. If there is a Route Type 3 or 6 or 9 or S for the procedure, then the Transition Identifier in the Route Type 2 or 5 or 8 or M will carry a blank transition identifier field.
Note 3: The use of “ALL” in the Transition Identifier field indicates that the procedure is valid for two or more runways at an airport or all helipads at a heliport. The use of the character “B” along with a runway designation such as RW08B in the Transition Identifier field indicates that the transition is valid for two or more parallel runways, e.g. RW08L and RW08R.
Note 4: The Missed Approach Transition Identifier will be the identifier of the Missed Approach Holding Fix or the last fix in the missed approach path if there is no holding fix. If multiple missed approach paths are published to the same termination but with different paths or constraints, a transition identifier closely aligned with the published source indication for each missed approach will be used.
Enroute Transition Identifiers are normally the identifier of a navaid or waypoint. Transition Identifiers should be derived from official government sources, where provided.
Used On: Airport and Heliport SID/STAR/Approach, Flight Planning Arrival/Departure Data and Company Route Records
Length: 5 characters max.
Character Type: Alpha/numeric
Examples: 9TU, ETX, KEENE, DEN, RW08R, Blank
5.11 过渡识别符
定义或描述:描述以下过渡的类型–从航路阶段到终端区或终端区到航路阶段的过渡类型;以及从终端区至进近或从跑道或直升机起降点到终端区的过渡类型。
数据源或供选编码:过渡识别字段的内容应根据航径类型字段(5.7)内容按照表5-14过渡识别符供选项。
航路航线过渡识别代号通常为NAVAID或航路点的识别,过渡航线代号应来源于官方文件,如提供。
应用范围:机场SID/STAR/APP,飞行计划进场/离场数据和公司航路记录
字节数:最多5字
字符类型:字母/数字
举例:9TU、ETX、 KEENE、 DEN、RW08R、
5.12 序号 Sequence Number (SEQ NR)
5.12 Sequence Number (SEQ NR)
Definition/Description: 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.
Source/Content: Sequence numbers are assigned during the route, boundary or sequence definition phase of the data file assembly. Sequence numbers are assigned so as not be duplicated within the route, boundary or sequence assigned a unique identification/designation. For three or four digit Sequence Numbers, initially, an increment of ten should be maintained between the sequence numbers assigned to consecutive records. For one or two digit Sequence Numbers, the initial increment is one. In route or boundary records, should subsequent maintenance of the file necessitate the addition of a record or records, the new record(s) should be located in the correct position in the sequence and assigned a sequence number whose most significant characters are identical to those in the sequence number of the preceding record in sequence. The unit character should be assigned a value midway between the units character values of the preceding and following record sequence numbers. For example, if it is desired to add one record to the sequence and the units characters of both the preceding and following records at the desired location are zeros (indicating no previous modification at this point), the units character or the inserted record’s sequence number should be five (5). For records taken in sequence with one or two digit sequence numbers, additional data must be entered in the proper sequence and all subsequent records will be up numbered accordingly.
When an enroute airway crosses the boundary separating two geographical areas (Section 5.3), the airway fix lying on or closest to the boundary shall be coded twice, once for each geographical area, and should be assigned the same sequence number in each case. Record uniqueness in such cases is maintained through the “Boundary Code” (Section 5.18). Enroute airway record sequence numbers should be assigned in a manner which permits them to be arranged into continuous airway routes in flight sequence order when sorted according to the Route Identifier and Sequence Number only, without regard to their applicable Geographical Area Code.
Used On: Enroute Airways, Airport and Heliport MSA Records, Airport and Heliport TAA Records, Airport and Heliport SID/STAR/Approach, Company Route, Cruise Tables, FIR/UIR, Restrictive Airspace, Controlled Airspace, Preferred Routes, Flight Planning Arrival/Departure Data and VHF Navaid Limitation Continuation Records
Length:
4 characters - Enroute Airways, Preferred Routes, FIR/UIR and Restrictive Airspace
3 characters - SID/STAR/Approach and Company Routes
2 characters - VHF Navaid Limitation Continuation Records
1 character - MSA Table, TAA Table, Cruise Table
Character Type: Numeric
Examples: 0010, 0135, 2076, 120, 030, 01, 84, 3
5.12 序号
定义或描述:在航线类型记录中,飞行航线以一系列有顺序的记录来定义。顺序号字段确定航线识别字段中所标出的飞行航线按顺序记录的位置。在边界型记录中,边界按照记录编号顺序定义。顺序号字段定义表示边界顺序的记录的位置。需要一个以上主记录定义完整内容的,以一系列主记录定义一个完整的情况,顺序号应用于定义系列中每个主记录的顺序。在机场TAA记录中,序号1总是分配给直线进近所基于的中心定位点的记录,序号2总是分配给左侧区字段所基于的中心定位点的记录,序号3总是分配给右侧区字段所基于的中心定位点的记录。因此,如果TAA记录有直线区和右侧区而无左侧区,只使用序号1和3;如果TAA记录有直线区和左侧区而无右侧区,只使用序号1和2。
数据源或供选编码:在集成航线、边界或数据文件顺序定义的阶段,分配序号。在分配一个唯一识别或代号的航线、边界或分配顺序内,所分配的序号不得重号。首先,在连续纪录分配的顺序号中,要采用十进位的3位或 4位数字。1位或2位数字的序号,首位为1。航线或边界记录,如果其后文件的维护另外需要1个记录或若干记录时,新的记录应插入到正确顺序位置,并且分配一个顺序号,该纪录的最重要的特性是同排序以前记录的顺序号一样。该单元字符应在前一个记录和后一个记录顺序号之间分配一个中间值。例如,如欲加一个记录到顺序中,在期望位置的先前纪录和后来记录两者的单元字符均为0(表示此处以前无修改),则单元字符或加入的记录的顺序号为5。由于排序的记录有1位或2位数字顺序号,增加的数据必须插入在适当顺序中,并且其后的记录序号应相应升位。
当一条航路穿过两个地区的分隔边界时(5.3),在边界上或最靠近边界的航路定位点应编两次码,每个区编一个码,并且在每个区分配的序号是相同的,在这种情况下记录的唯一性通过“边界代码”实现(5.18)。航路航线记录顺序号的分配应遵循一个原则,即允许其在按照航线识别代号或只用顺序号检索时,能以飞行的顺序连续列出航路航线,而不需要使用区域代码。
应用范围:航路、机场SID/STAR/APP、机场TAA、公司航路、高度层配置表、FIR/UIR、管制空字段、飞行计划进场/离场数据和VHF NAVAID限制的续记录。
字节数:4位—航路航线、优选航线、FIR/UIR、限制空域字段
3位—SID/STAR/APP和公司航路
2位—VHF NAVAID限制续记录
1位—MSA表、高度层配置表、TAA表
字符类型:数字
举例: 0010、0135、 2076、 120、 030、 01、 84、 3
5.13 定位点识别符 Fix Identifier
5.13 Fix Identifier
Definition/Description: 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.
Source/Content: Officially published identifiers or identifiers derived in accordance with Chapter 7, Naming Conventions, of this document.
Used On: Holding Patterns, Enroute Airways, Airport and Heliport SID/STAR/Approach, Enroute Airway Restrictions, and Enroute Waypoints, Airport and Heliport Terminal Waypoints (Waypoint Ident) and Flight Planning Arrival/Departure Data Records.
Length: 5 characters max
Character Type: Alpha/numeric (no embedded blanks)
Examples: SHARP, DEN43, BHM, RW27L, KGRR
5.13 定位点识别符
定义或描述:包括识别定位点的5字代码或其它字符串。包括航路点识别、VHF NAVAID识别,NDB识别,机场识别和跑道识别
数据源或供选编码:官方公布的识别或按照第7章定名规则形成的识别。
应用范围:等待程序、航路航线、机场SID/STAR/APP、航路航线的航路限制、航路航线点、机场终端航路点和飞行计划进场/离场数据记录。
字节数:最多5位
字符类型:字母/数字(不能留空位)
举例:SHARP、 DEN43、 BHM、 RW27L、KGRR
5.14 行政区码 ICAO Code (ICAO CODE)
5.14 ICAO Code
Definition/Description: The “ICAO Code” field permits records to be categorized geographically within the limits of the categorization performed by the “Area Code” field.
Source/Content: The code is to be employed in the ICAO code field may be found in ICAO Document No. 7910, “Location Indicators.”
In order to permit sub-division of the United States into more easily manageable regions, the ICAO code for the USA (K) is followed by a numeric character obtained from Figure 5-5.
Used On: All records except Cruising Tables and Grid MORA
Length: 2 characters max
Character Type: Alpha/numeric
Examples: K1,K7,PA,MM,EG,UT
5.14 行政区码
定义或描述:允许记录在区域代码分类范围内按照地理分类。
数据源或供选编码:本项使用的代码可以在ICAO 7910文件“地名代码”中查询。
为了使美国的分区范围成为更容易管理的地区,美国的情报区二码K之后可以使用图5-5中的数字。
应用范围:所有记录,除高度层配置表和网格MORA。
字节数;最多2位
字符类型;字母/数字
举例:K1、 K7、PA、MM 、EG、UT
5.16 续记录号 Continuation Record Number (CONT NR)
5.16 Continuation Record Number (CONT NR)
Definition/Description: When it is not possible to store all the information needed on a record within the 132 columns of the record itself, the so-called Primary Record; one or more continuation records may be used. The “Continuation Record Number” identifies the position of a continuation record in a sequence of such records.
Source/Content: Primary records contain the numeric “0” when no Continuation Records are included in the file for that Primary. The numeric “1” in this field of the Primary Record indicates that one or more Continuation Records follow the Primary Record. Continuation Records are numbered sequentially starting with the numeric “2” in the first continuation. If the information requirement goes beyond a Continuation Record with the numeric “9,” the sequence is continued with alpha characters, starting with “A” and continuing through to “Z” as required.
Used On: All records except Company Route, Airport Localizer Marker/Locator, Enroute Markers, Cruising Tables, FIR/UIR and Grid MORA
Length: 1 character
Character Type: Alpha/numeric
Examples: 0, 1, 2 (through 9) A, B, C (through Z)
5.16 续记录号
定义或描述:当不能在一个记录本身,即主记录的132列中存储需要的所有资料时,可以使用一个以上续记录,续记录号表示在这种记录排序中续记录的位置。
数据源或供选编码:续记录编号规则是在没有续记录的情况下,主记录的编号是0;在还有续记录的情况下,主记录、续记录统一从1开始编号,如果续记录超过9个,再从A-Z编号。
应用范围:除公司航路以外的所有记录、机场LOC/MKR/示位台、航路MKR、高度层配置表、FIR/UIR、网格MORA
字节数:1位
字符类型:字母/数字
举例:0、1、2(到9)、A、B、C(到Z)
5.17 航路点描述代码 Waypoint Description Code (DESC CODE)
Definition/Description: Fixes are located at positions significant to navigation in the Enroute, Terminal Area and Approach Procedure path definitions. The “Waypoint Description Code” field enables that significance or function of a fix at a specific location in a route to be identified. The field provides information on the type of fix. As a single fix can be used in different route structures and multiple times within a given structure, the field provides the function for each occurrence of a fix.
定义或描述:在航路、终端区和APP程序航径定义时,定位点位于对航行有重要意义的位置。航路点描述码字段是使要定义的航线上一个特定位置的定位点的重要性或作用能够表示出来。该字段提供定位点类型资料。由于一个单一的定位点可以应用于不同的航线结构,并在一个特定的结构中多次使用,该项提供一个定位点在每次应用中的作用。
Source/Content: Valid contents for the “Waypoint Description Code” are contained in the table below. The contents of Column 40 provide information on the fix type. Column 41 is used to define whether the fix is a “fly-over” or “fly-by” fix and to indicate the charting status of some waypoints. Columns 42 and 43 provide the fix function information. Column 40, Code “G,” is valid for Runway as Waypoint and Helipad as Waypoint.
数据源或供选编码:航路点描述码的有效内容包括在图表5-4航路点描述表中。40列的内容提供定位点类型资料。41列指示是飞越还是旁切,并表示某些航路点在航图中的情况。42和43列提供定位点作用的资料。在跑道和直升机起降点作为航路点,40列填G有效。
Explanation of superscript notes and other details required to understand this table:
解释理解此表所需的上标注释和其他细节:
(1)Any waypoint (not Navaid, Airport or Runway) in Terminal Procedures or any waypoint (not Navaid or airport) on Enroute Airways, required for navigation such as a change in bearing, intersection of two airways, beginning or end of continuous segment. See Special Navigation Terms in Section 2.
(1)在终端程序中的任何航路点(不是导航设施、机场或跑道),或在航路航线中的任何航路点(不是导航设施或机场),例如航向改变、两条航线的交叉点、连续段的起点或终点,这些都是导航所需的。请参阅第 2 节中的特殊导航术语。
(2)Any waypoint published by government source but not part of any route structure.
(2)任何由政府来源发布但不属于任何航线结构的航路点。
(3)A waypoint established during procedure coding on the nominal track.
(3)在标称轨道的程序编码期间建立的航路点。
(4)Any waypoint (not Navaid or airport) on Enroute Airways that is not considered “Essential” or “Transition Essential.” See Special Navigation Terms in Section 2.
(4)在航路航线的任何航路点(非导航台或机场),若不被视为“必要”或“过渡必要”。见第 2 节中的特殊导航术语。
(5)Any waypoint (not Navaid or airport) on Enroute Airways for the purpose of transitioning between the Enroute and Terminal structures. See Special Navigation Terms in Section 2.
(5)在航路航线的任何航路点(不是导航设施或机场),用于在航路和终端结构之间过渡。见第 2 节中的特殊导航术语。
(6)A fly-over waypoint (including Navaid) specified by the procedure: (a) at the end of a SID or STAR Route Type; (b) at the end of an Approach Transition for FMS, GPS, or MLS/RNAV approach; or (c) at the missed approach point in an Approach Procedure.
(6)一种由程序指定的飞越航路点(包括导航设施):(a)在标准仪表离场(SID)或标准仪表进场(STAR)航线类型的末端;(b)在飞行管理系统(FMS)、全球定位系统(GPS)或微波着陆系统/区域导航(MLS/RNAV)进近的进近过渡末端;或者(c)在进近程序中的复飞点。
(7)Any waypoint (not Navaid and airport) on Enroute Airways that has not been established by government source. Used only in conjunction with “E” in Column40.
(7)任何在航路航线上(非导航台和机场)未由政府来源设立的航路点。仅与第 40 列中的“E”结合使用。
(8)Any waypoint (including Navaid and airport) that must be over flown before establishing on the following leg.
(8)在建立后续航段之前必须飞越的任何航路点(包括导航台和机场)。
(9)Any waypoint (including Navaid and airport) on Enroute Airways at which a “position report” must be made to the appropriate Air Traffic Control unit. See Special Navigation Terms in Section 2.
(9)在航路航线的任何航路点(包括导航设施和机场),必须向相应的空中交通管制单位进行“位置报告”。见第 2 节中的特殊导航术语。
(10)Any waypoint (including Navaid) designated as the start/end of an oceanic organized track system. See Special Navigation Terms in Section 2.
(10)任何被指定为海洋有组织航线系统起始/终点的航路点(包括导航设施)。见第 2 节中的特殊导航术语。
(11)Coded on the first leg after a runway fix or missed approach point fix dependent on approach procedure coding rules in Attachment 5. The leg may be the first leg of a published missed approach procedure or a leg to the published missed approach point.
(11)根据附件 5 中的进近程序编码规则,在跑道修复或复飞点修复后的第一段航段进行编码。该航段可能是已公布的复飞程序的第一段航段,也可能是到已公布复飞点的航段。
(12)Any waypoint (including Navaid) established as an Initial Approach Fix. See Special Navigation Terms in Section 2.
(12)任何航路点(包括导航设施)被确立为初始进近定位点。见第 2 节中的特殊导航术语。
(13)Any waypoint (including Navaid) established as an Intermediate Approach Fix and not coded as a Final Approach Course Fix. See Special Navigation Terms in Section 2.
(13)任何被确立为中间进近定位点(包括导航设施)但未被编码为最终进近航线定位点的航路点。请参阅第 2 节中的特殊导航术语。
(14)Any waypoint (including Navaid) established as a Final Approach Fix. This may be a fix published as the Final Approach Fix by government source or, when no such fix is published, one established by a data supplier according to the rules in Attachment 5. See Special Navigation Terms in Section 2.
(14)任何航路点(包括导航台)被确立为最终进近定位点。这可能是由政府来源公布的最终进近定位点,或者在没有公布此类定位点的情况下,由数据供应商根据附件 5 中的规则设立。请参阅第 2 节中的特殊导航术语。
(15)Any waypoint (including Navaid) established as a Final Approach Course Fix. This may be a fix published as the Final Approach Course Fix by government source or, when no such fix is published but yet required, one established by a data supplier according to the rules in Attachment 5. See Special Navigation Terms in Section 2.
(15)任何航路点(包括导航设施)被确立为最终进近航道定位点。这可能是由政府来源公布的作为最终进近航道定位点的定位点,或者当没有公布此类定位点但仍有需要时,由数据供应商根据附件 5 中的规则确立的定位点。参见第 2 节中的特殊导航术语。
(16)Any waypoint established as the Final End Point. This may be a fix published as the FEP by the government source or, when no such fix is published but yet required, one established by the data supplier. It is used in vertical coding of non-precision approach procedures. See Special Navigation Terms in Section 2.
(16)任何被确立为最终端点的航路点。这可能是由政府来源公布的作为最终端点(FEP)的定位点,或者当没有公布此类定位点但又需要时,由数据供应商确立的一个。它用于非精密进近程序的垂直编码。参见第 2 节中的特殊导航术语。
(17)Any waypoint (including Navaid or Runway) established as a Missed Approach Point by government source, may follow a Runway Fix when such is required by the rule in Attachment 5. The code is used in conjunction with “G” in Column 40 when the Runway is the published Missed Approach Point.
(17)任何由政府来源确立为复飞点的航路点(包括导航设施或跑道),当附件 5 中的规则有要求时,都可以遵循跑道定位点。当跑道是公布的复飞点时,该代码与第 40 列中的“G”一起使用。
(18)Any waypoint established and named by the government source lying between the Final Approach Fix and the Missed Approach Point or between a published Final Approach Course Fix and a Final Approach Fix.
(18)在最终进近定位点与复飞点之间,或已公布的最终进近航线定位点与最终进近定位点之间,由政府部门设立并命名的任何航路点。
(19)Any waypoint established by the government source in support of RNAV-GPS/GLS Approach Procedures. Path Points are not part of the defined procedure track but are provided in a separate record where required. The points are not named and are always referred to as Path Point 1 and Path Point 2.
(19)任何由政府部门设立的用于支持 RNAV-GPS/GLS 进近程序的航路点。路径点不属于规定的程序轨迹的一部分,但在需要时会在单独的记录中提供。这些点未命名,总是被称为路径点 1 和路径点 2 。
(20)Any published but unnamed waypoint lying between the Final Approach Fix and the Missed Approach Point (Code “A”) or between the Final Approach Course Fix and the Final Approach Fix (Code “B”).
(20)在最终进近定位点和复飞点之间(代码“A”)或在最终进近航线定位点和最终进近定位点之间(代码“B”)的任何已公布但未命名的航路点。
Note 1: Column 40, the fix type column, may be blank when a particular leg of a procedure does not include a fix, such as those legs ending in intercepts or terminating altitudes. For more information on such legs, refer to the Leg Data Table in Attachment 5.
注 1:第 40 列,即定位类型列,在程序的特定航段不包含定位时可能为空,例如那些以拦截或终止高度结束的航段。关于此类航段的更多信息,请参考附件 5 中的航段数据表。
Note 2: With the rules provided for Columns 42 and 43, as further explained by references 11 and 17, it is possible to have the code “M” in both of the columns for one leg in cases where a runway fix which is not the designated missed approach point has been inserted into the procedure coding.
注 2:对于第 42 列和第 43 列所提供的规则,正如参考文献 11 和 17 所进一步解释的那样,在将并非指定复飞点的跑道定位点插入程序编码的情况下,有可能在其中一“段”的两列中都出现代码“M”。
Used On: Airport and Heliport SID/STAR/Approach, Enroute Airway Records
应用范围: 机场SID/STAR/APP、航路航线记录
Length: 4 Characters
字节数: 4位
Character Type: Alpha
字符类型: 字母
5.18 边界代码 Boundary Code (BDY CODE)
5.18 Boundary Code (BDY CODE)
Definition/Description: 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.
Source/Content: See Table 5-6.
Used On: Enroute Airways records
Length: 1 character
Character Type: Alpha/numeric
Area | Area Code* | Boundary Code |
---|---|---|
USA | USA | U |
Canada and Alaska | CAN | C |
Pacific | PAC | P |
Latin America | LAM | L |
South America | SAM | S |
South Pacific | SPA | 1 |
Europe | EUR | E |
Eastern Europe | EEU | 2 |
Middle East-South Asia | MES | M |
Africa | AFR | A |
Notes;* From Figure 5-2 Table 5-6 - Boundary Codes
5.18 边界代码
定义或描述:飞行航线频繁的穿越地理边界。当出现穿越时,此字段内容用于定义航路航线来自的区域或航路航线进入的区域。
数据源或供选编码:见图表5-6边界代码.
应用范围:航路航线记录.
字节数:1位
字符类型:字母/数字
5.19 高度代码 Level (LEVEL)
5.19 Level(LEVEL)
Definition/Description: The Level field defines the airway structure of which the record is an element.
Source/Content:
B:All Altitudes
H:High Level Airways
L:Low Level Airways
Used On: Enroute Airway, Preferred Routes, Restrictive Airspace, and Controlled Airspace records
Length: 1 character
Character Type: Alpha
5.19 高度代码
定义或描述:用于定义记录是一部分的航路结构
数据源或供选编码:
B:所有高度
H:高空航路航线
L:低空航路航线
应用范围:航路、优选航线、限制空域和管制空域记录
字节数:1位
字符类型:字母
5.20 转弯方向 Turn Direction (TURN DIR)
5.20 Turn Direction (TURN DIR)
Definition/Description: 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.
Source/Content: The field contains the alpha character “L” for Left turns, “R” for Right turns and “E” for turns in either direction.
Used On: Airport and Heliport SID/STAR/Approach records
Length: 1 character
Character Type: Alpha
5.20 转弯方向
定义或描述:转弯方向字段说明要进行终端程序转弯的方向。也应用于指示反向程序的方向。见附录5-航径和终端形式代码
数据源或供选编码:该项包括字母L为左转弯,R为右转弯,E表示左右均可。
应用范围:机场SID/STAR/APP 记录
字节数:1位
字符类型:字母