不同程序对航径终止码要求

对于所有程序的编码规则

  2.0 Coding Rules Applicable To All Procedures
  2.1 All Procedures must be coded to provide guidance specified by source documentation.
  2.2 Vertical angles are referenced to the terminating fix.
  2.3 Use of a “C” in the Altitude Description field (5.29) may only be used in SID records and there only with the following leg types: CD, CF, CR, FC, FD, TF, VD, VR The conditional termination altitude can be coded in columns 90 through 94 of the SID record. If a “+,” “-” or“blank” is coded in the Altitude Description field, input of a second altitude must imply a condition altitude termination.
  2.4 Altitude terminations must not be used in descent procedures.
  2.5 Lost Communication Procedures may be coded in place of “Vector Legs” if the procedure defines a complete route of flight to the end of a SID or STAR.
  2.6 The “Turn Direction” and “Turn Direction Valid” leg data fields are used in combination to force a particular turn direction whenever the track/heading change exceeds 135 degrees. If the turn direction is indicated with the “L” or “R,” then the turn direction valid character must be set to “Y.” If the turn direction is indicated with “E,” then the turn direction valid field must always be blank. The Turn Direction/Turn Direction Valid combination is used to indicate that turn in the specified direction must be executed prior to intercepting the path defined in the record. Turn Direction must always be indicated whenever the turn is 90 degrees or more.
  2.7 The first leg of each procedure will contain the appropriate transition “altitude.” If the transition altitude is 18,000 feet, it may be omitted. See Section 5.53 for specifics on the appropriate altitude for each type of Terminal Procedure.
  2.8 Non essential and transition essential waypoint codes are not used in the waypoint description field on terminal procedures. All waypoints must be considered as essential in these procedures.
  2.9 Required Navigation Performance (RNP) must be applied to segment on which the value is coded. RNP will be coded on every segment where it is specified by source. Lack of a RNP value on a segment indicated that no source RNP value is available for the segment.

  2.0 适用于所有程序的编码规则
  2.1 所有程序必须根据源文件提供的指导进行编码。
  2.2 垂直角度是相对于终止修正点进行参考的。
  2.3 在高度描述字段(5.29)中只能在SID记录中使用“C”,且仅限以下航段类型:CD、CF、CR、FC、FD、TF、VD、VR条件终止高度可以编码在SID记录的90至94列中。如果在高度描述字段中编码为“+”、“-”或“空白”，则输入第二个高度必须表示条件高度终止。
  2.4 不得在下降程序中使用高度终止。
  2.5 如果程序定义了一条完整的飞行路线直至SID或STAR的终点,则可以将“失去通信程序”编码替换为“向量航段”。
  2.6 “转弯方向”和“转弯方向有效”航段数据字段是结合使用的，用于在航迹/航向变化超过135度时强制执行特定的转弯方向。如果转弯方向用“L”或“R”表示,则转弯方向有效字符必须设为“Y”。如果转方向用“E”表示,则转弯方向有效字段必须始终为空白。转弯方向/转弯方向有效组合用于指示必须在拦截记录中定义的航迹之前执行的指定方向的转弯。每当转弯角度达到90度或更大时，必须始终指示转弯方向。
  2.7 每个程序的第一航段将包含适当的过渡“高度”。如果过渡高度为18,000英尺,则可以省略。有关每种类别终端程序的适当高度的详细信息,请参见第5.53节。
  2.8 在终端程序的航路点描述字段中不使用非必要和过渡必要航路点代码。在这些程序中，必须将所有航路点视为必要。
  2.9 需要导航性能(RNP)必须应用于编码的航段上。每个通过源文件指定的航段都将编码RNP值。航段上缺乏RNP值表示该航段没有可用的源RNP值。

适用于所有程序类型的路径和终止相关规则

  3.0 Path and Termination Related Rules Valid For All Procedure Types
  3.1 DF legs must be used to start from an unknown position such as an altitude or from DME or Distance terminations. A DF leg may follow a CF leg only when the CF leg fix must be overflown, otherwise a TF leg should be used. A DF may also be followed by another DF leg. In these cases, the fix at the end of the first DF leg must be overflown. When DF legs follow DME or Distance Terminations, that termination must be overflown. For distance terminations, the overfly parameter must be set, otherwise the combination is not permitted.
  3.2 The distance leg data field must be completed on all CF legs. When the CF is preceded by an intercept, the no wind intercept distance will be provided. If the CF leg is the first leg of a missed approach, the distance entered will be from the approach runway fix or missed approach fix, whichever applies.
  3.3 When a leg terminating at a fix (“XF” leg) is followed by a PI leg, the PI fix must be the same fix as the terminating fix on the preceding leg.
  3.4 Rules specific to “arc” legs, leg type AF:
   3.4.1 When an AF-AF leg sequence is coded, both legs must use the same “Recommended VHF Navaid” facility and the DME distance must be the same for both legs.
   3.4.2 When any holding leg (“HX”) or fix termination (“XF”) is followed by an AF leg, the preceding termination fix must lie on the arc defined in the AF leg.
   3.4.3 When a FD leg is followed by an AF leg type, the fix in the FD leg must have the same “Recommend VHF Navaid” as that defining the AF leg.
   3.4.4 When a CD or VD leg type is followed by an AF leg type, both legs must have the same Recommended VHF Navaid. The DME distance must be the same for both legs.
   3.4.5 When a CI leg type is followed by an AF leg type, the “course to” must be to the “Recommended VHF Navaid” which defines the AF arc.
  3.5 When an AF, CF, DF, RF, TF or “HX” leg is followed by any course-from leg type (“FX” legs), the “FX” leg must be from the same point as the preceding termination.
  3.6 Leg types of CD, CR, FD, RF, VD and VR “overfly” the terminator point. If “turn anticipation” is required to reflect the source, alternate leg types must be used.
  3.7 When the leg data type “Recommended Navaid” is coded in a CI or VI leg, it must be the same as the Recommended Navaid in the leg to be intercepted.
  3.8 The TF leg type will be coded in preference to the CF leg type in all cases where the resulting path will be the same, except when coding some types of final approach procedure legs, see Rules in Section 6.0, 7.0 and 8.0 of this Attachment.
  3.9 The FC leg type must be used when the distance in the “Time/Distance” field is the path length and is measured from the fix entered in the Waypoint Identifier field. The FD leg type must be used when the distance in the “Time/Distance” field is the “DME” distance from the Navaid entered in the Recommended Navaid field.
  3.10 FC or FD legs will not be used if the distance is greater than 60NM and are followed by a CF leg.
  3.11 A PI leg is used to make a 180 degree course reversal when a holding or a tear drop turn is not specified. The course must be coded as 45 degrees from the reciprocal of the inbound course, unless otherwise specified by government sources. The turn direction is the direction made during the 180 reversal within the PI leg. A one minute outbound leg is implied from the fix to the initial 45 degree turn.
  3.12 The IF leg type will normally be used in an initial sequence of a procedure. The IF leg type, followed by a TF leg type will be used in other than the first sequence if such is required to correctly code the procedure as published by the source documentation when one or more of the following criteria are met -
   - there is no VHF Navaid available for use as the Recommended Navaid that would permit coding with other leg types.
   - the leg to be intercepted will have a distance of more than 60 NM between the point of intercept and the terminating fix.
   This will allow a segment to be constructed, from one fix to the next fix, using an “intercept” where coding would otherwise not be possible. See the sample use of this rule below.
  3.13 When coding “arc paths,” when the source defined ARC Center is a VHF Navaid of the types VORDME or VORTAC and the path is defined as a “DME ARC,” the AF leg must be used instead of the RF leg.
  3.14 The previous leg and next leg associated with an RF leg should have a course or track which is tangent to the RF leg except when the leg combination is IF/RF, RF/RF or HX.
  3.15 Use of a single RF leg is limited to turns of equal to or greater than 2 degrees and equal to or less than 300 degrees.
  3.16 Phantom Waypoints. These database waypoints are established during procedure coding. Used to facilitate more accurate navigation under certain circumstances.

  3.0 适用于所有程序类型的路径和终止相关规则
  3.1 必须使用DF航段来起始于未知位置，例如高度或DME或距离终止点。只有当需要飞越CF航段修正点时，DF航段才能跟随CF航段，否则应使用TF航段。DF航段之后还可以跟随另一个DF航段。在这些情况下，第一个DF航段末端的修正点必须飞越。当DF航段跟随DME或距离终止时，必须飞越该终止点。对于距离终止，必须设置飞越参数，否则不允许该组合。
  3.2 必须在所有CF航段上填写“距离”航段数据字段。当CF航段之前有拦截时，将提供无风拦截距离。如果CF航段是复飞的第一航段，则输入的距离将从进近跑道修正点或复飞修正点开始，视情况而定。
  3.3 当以修正点（“XF”航段）作为终止的航段之后跟随PI航段，PI航段的修正点必须与前一航段的终止修正点相同。
  3.4 与“弧线”航段（航段类型为AF）有关的规则：
   3.4.1 当编码AF-AF航段序列时，两个航段必须使用相同的“推荐VHF导航设施”，并且DME距离必须相同。
   3.4.2 当任何一条保持航段（“HX”）或修正点终止航段（“XF”）后面跟随AF航段时，前一终止修正点必须位于AF航段定义的弧线上。
   3.4.3 当FD航段后面跟随AF航段类型时，FD航段中的修正点必须与定义AF航段的“推荐VHF导航设施”相同。
   3.4.4 当CD航段或VD航段类型后面跟随AF航段类型时，两个航段必须具有相同的推荐VHF导航设施。DME距离对两个航段必须相同。
   3.4.5 当CI航段类型后面跟随AF航段类型时，航向必须指向定义AF弧线的“推荐VHF导航设施”。
  3.5 如果在AF、CF、DF、RF、TF或“HX”航段之后跟随任何“FX”航段类型（航径出发航段），则“FX”航段的起点必须与前一个终止点相同。
  3.6 CD、CR、FD、RF、VD和VR航段类型会“飞越”终止点。如果需要反映源文件的“转弯预期”，则必须使用备用航段类型。
  3.7 当在CI或VI航段中编码“推荐导航设施”时，必须与要拦截的航段中的推荐导航设施相同。
  3.8 在所有情况下，如果结果路径相同，则优先编码TF航段类型而非CF航段类型，除非编码某些类型的最终进近程序航段，请参见本附件中的第6.0、7.0和8.0节的规则。
  3.9 当“时间/距离”字段中的距离表示路径长度，并且从航路点标识字段中输入的修正点开始测量时，必须使用FC航段类型。当“时间/距离”字段中的距离表示从推荐导航设施字段中输入的导航设施的“DME”距离时，必须使用FD航段类型。
  3.10 如果距离大于60海里并且之后跟随一个CF航段，则不使用FC或FD航段。
  3.11 当未指定保持或T形转弯时，使用PI航段进行180度航迹反转。航迹必须编码为与入航迹的逆时针方向成45度夹角，除非政府源文件另有规定。转弯方向是在PI航段内进行的180度反转方向。从修正点到初始45度转弯点有一个一分钟的出站航段。
  3.12 IF航段类型通常用于程序的初始序列。除非必须按照源文件文档发布的程序正确编码所需要，否则其他序列中会使用IF航段类型，后跟TF航段类型。当满足以下一个或多个条件时，
   - 没有可用作推荐导航设施的VHF导航设施，从而允许使用其他航段类型进行编码。
   - 将要拦截的航段在拦截点与终止修正点之间的距离超过60海里。
   这将允许通过“拦截”从一个修正点到下一个修正点构建一个航段，在其他情况下不可能进行编码。请参见下面示例用法示例。
  3.13 在编码“弧线路径”时，如果源文件定义的ARC中心是VHF导航设施类型的VORDME或VORTAC，并且路径被定义为“DME ARC”，则必须使用AF航段而不是RF航段。
  3.14 除非航段组合是IF/RF、RF/RF或HX，与RF航段相关的前一个航段和后一个航段应具有与RF航段切线相切的航向或航迹。
  3.15 仅限于转弯角度大于等于2度且小于等于300度的情况，才能使用单个RF航段。
  3.16 幻像航路点。这些数据库航路点是在程序编码过程中建立的，用于在特定情况下便于更准确的导航。

SID编码规则

  4.0 STANDARD INSTRUMENT DEPARTURE (SID) CODING RULES
  4.1 The following rules cover the altitude coding requirements of the initial leg of a departure: If a published take-off requires a turn of greater than 15 degrees from the runway bearing, code a CA, VA or FA leg on the runway bearing/heading to an altitude of 400 feet above the airport elevation (AFE). If a published take-off is straight ahead or requires a turn of less than 15 degrees and is to a fix such as a waypoint, Navaid, or DME distance termination, code an altitude on that fix when included in the government source, otherwise no altitude is coded. If a published take-off is straight ahead or requires a turn of less than 15 degree and is to a specified altitude termination, code the appropriate leg type (VA, FA, CA) to that altitude. The altitude description on a coded altitude, either a termination or at a fix, may be “at,” “at or above,” “at or below” and “at or below to at or above.”
  4.2 For the first leg of a SID, course legs (“CX” or “FX”) are preferred over heading legs unless the source requires that heading legs be coded.
  4.3 The use of FM or VM leg types in the first leg of a SID Runway Transition for Route Types of 0, 1 and 4 or F is permitted when the initial heading is defined in the source.
  4.4 If a SID ends in vectors, the heading for the FM or VM leg must be based on source documentation.
  4.5 If the last fix of a SID sequence or SID Enroute Transition sequence is a fix on an Enroute Airway, the Waypoint Description Code in the Enroute Airway record for that fix must designate that fix as “Essential” or “Transition Essential.”
  4.6 SID Enroute Transition legs will be coded using TF legs where possible to simplify coding. This rule does not apply if the use of TF legs would require the creation of additional waypoints.
  4.7 SID Enroute Transitions published in source documentation but wholly contained in other SID Enroute Transitions will not be coded separately.
  4.8 All waypoints used in SID common or Vector SIDs must be in the Enroute Waypoint File as an Off-Route Intersection unless the waypoint is also used for Enroute Airway Coding.
  4.9 A SID which consists of a single path from an origination fix to a termination fix will be coded as a Route Type 2 or 5 or M.
  4.10 A SID which consists of Enroute Transitions only can be coded with a single IF leg as a Route Type 2 or 5 or M, followed by the required Route Type 3 or 6 or S coding. The fix on which the IF leg is coded must be the first fix in all of the Enroute Transitions. The Transition Identifier must be coded in accordance with Chapter Five, Section 5.11.
  4.11 For Vector SIDs which consist of Enroute Transitions only, the coding must be a Runway Transition Route Type “V,” followed by the Enroute Transition(s), Route Type “T.” The Enroute Transition(s) must be an IF/DF leg combination with the Airport as the fix in the IF leg and the first fix of the Enroute Transition as the fix in the DF leg. The DF leg must carry a distance value equal to the total distance between the Airport and the fix along the approximated path.
  4.12 When a SID Route or portion of a SID Route is repeated with different Runway Identifiers in the Transition Identifier, it must be coded as a Runway Transition Route Type of 1 or 4 or F or V (Vector SID). When a SID Route is repeated with different fix identifiers in the Transition Identifier, it must be coded as an Enroute Transition, Route Type of 3 or 6 or S or T (Vector SID).
  4.13 “Engine Out” SIDs must be coded as Route Type “0” only. Route Type “0” is not used in combination with other SID Route Types. The Runway Transition Identifier must contain a specific Runway Identification or Helipad Identification. All other rules for Route Type 1 and 4 apply in the coding of Route Type “0.”

  4.0 标准仪表离场（SID）编码规则
  4.1以下规则涵盖了离场初始航段的高度编码要求：如果出版的起飞要求从跑道航向偏离超过15度的转弯，要在与跑道航向/航迹一致的位置上编码CA、VA或FA航段，高度设置为机场标高（AFE）上方400英尺。如果出版的起飞是直线起飞或所需转弯角度小于15度，并且目标是航路点、导航设施或DME距离终止点等修正点，只有在政府源文件中包含该修正点的高度信息时才在该修正点上编码高度，否则不编码高度。如果出版的起飞是直线起飞或所需转弯角度小于15度，并且目标是指定的高度终止点，则将相应的航段类型（VA、FA、CA）编码至该高度。编码的高度描述，无论是终止点还是修正点，可以是“在”、“至少在”、“至多在”或“至少在至至少在之间”。
  4.2对于SID的第一个航段，优先选择航向航段（“CX”或“FX”）而非航迹航段，除非源文件要求编码航迹航段。
  4.3在路线类型为0、1、4或F的SID航道过渡的第一个航段中，允许使用FM或VM航段类型，前提是源文件中定义了初始航向。
  4.4如果一个SID以向导航点的方式结束，则FM或VM航段的航向必须基于源文件的文档。
  4.5如果一个SID序列或SID航线过渡序列的最后一个修正点位于航路上的一个修正点上，则该修正点在航路上的修正点记录中的航路点描述码必须指定该修正点为“必要”或“过渡必要”。
  4.6尽可能使用TF航段对SID航线过渡航段进行编码，以简化编码。如果使用TF航段需要创建额外的航路点，则不适用此规则。
  4.7在源文件中发布的完全包含在其他SID航线过渡中的SID航线过渡将不会单独进行编码。
  4.8SID共用或矢量SID中使用的所有航路点必须作为航路航点文件中的非航路交叉点，除非该航路点还用于航路航线编码。
  4.9如果一个SID仅由从起始修正点到终止修正点的单一路径组成，则将其编码为路线类型2、5或M。
  4.10仅由航线过渡组成的SID可以使用单个IF航段作为路线类型2、5或M编码，然后按照所需的路线类型3、6或S编码给出。IF航段编码的修正点必须是所有航线过渡中的第一个修正点。过渡标识符必须按照第五章第5.11节的规定进行编码。
  4.11对于仅由航线过渡组成的矢量SID，编码必须是跑道过渡路线类型“V”，后跟航线过渡（们）路线类型“T”。航线过渡（们）必须是一个IF/DF航段组合，其中IF航段中的修正点是机场，DF航段中的修正点是航线过渡的第一个修正点。DF航段必须有一个距离值，等于沿近似路径上，从机场到修正点的总距离。
  4.12当SID航线或SID航线的一部分在过渡标识符中以不同的跑道标识符重复时，必须将其编码为过渡路线类型1、4、F或V（矢量SID）。当SID航线在过渡标识符中以不同的修正点标识符重复时，必须编码为航线过渡，过渡路线类型为3、6、S或T（矢量SID）。
  4.13“发动机关闭”SID必须仅以路线类型“0”编码。路线类型“0”不能与其他SID路线类型组合使用。跑道过渡标识符必须包含特定的跑道标识或停机坪标识。在编码路线类型“0”时，适用于路线类型1和4的其他规则。

STAR编码规则

  5.0 Standard Terminal Arrival Route (STAR) Coding Rules
  5.1 If a STAR ends in vectors to a final approach (VM leg), the Airport Reference Point Record will be coded in the Waypoint Ident field of the STAR Record.
  5.2 If a STAR ends in a sequence which aligns the aircraft inbound on the localizer course, the termination of the STAR sequence must be the Waypoint defined as the FACF for the localizer based Approach Procedure.
  5.3 If a STAR or Profile Descent does not begin at a fix in the source documentation, the closest named fix along the STAR or Profile Descent track must be assigned as the initial fix (IF leg) for the STAR or Profile Descent.
  5.4 If no crossing altitudes are specified on intermediate fixes of a STAR or Profile Descent, a “vertical angle” will be coded in the last leg of the procedure. This angle will be computed, based on the altitudes specified at the end fixes, to provide a constant descent path through all intermediate fixes. The angle provided will ensure compliance with minimum enroute altitudes for those segments without assigned altitudes.
  5.5 A STAR or Profile Descent which consists of a single path from an origination fix to a termination fix will be coded as a Route Type 2 or 5 or 8 or M.
  5.6 When a STAR Route/Profile Descent Route or portion of a STAR Route/Profile Descent Route is repeated with different Runway Identifiers or different Helipad Identifiers in the Transition Identifier it must be coded as a Runway Transition Route Type 3 or 6 or 9 or S. When a STAR Route/Profile Descent Route or portion of a STAR Route/Profile Descent Route is repeated with different Fix Identifiers in the Transition Identifier, it must be coded as an Enroute Transition Route Type 1 or 4 or 7 or F.
  5.7 When an Arrival Route serves the same runway or helipad as an Approach Route and the Arrival Route overlaps an Approach Transition, both the Arrival Route and the Approach Transition will be coded in their entirety in accordance with source documentation.

  5.0 标准仪表进场（STAR）编码规则
  5.1 如果STAR以向导航进近（VM航段）结束，则机场参考点记录将编码在STAR记录的航路点标识字段中。
  5.2 如果STAR以将飞机对准当地导航航线的序列结束，则STAR序列的终点必须是作为基于当地导興进近程序的FACF定义的航路点。
  5.3 如果STAR或剖面下降不是从源文件中的修正点开始的，则必须选择沿着STAR或剖面下降航迹最近的命名修正点作为STAR或剖面下降的初始修正点（IF航段）。
  5.4 如果STAR或剖面下降的中间修正点没有指定交叉高度，则在该程序的最后一个航段中将编码为“垂直角度”。该角度将根据末端修正点上指定的高度计算，以在所有中间修正点上提供恒定的下降路径。所提供的角度将确保符合没有分配高度的航段的最低航路高度要求。
  5.5 如果STAR或剖面下降只包含从起始修正点到终止修正点的单一航迹，则将其编码为路线类型2、5、8或M。
  5.6 当一个STAR航线/剖面下降航线或STAR航线/剖面下降航线的一部分在过渡标识符中重复出现且具有不同的跑道标识符或不同的停机坪标识符时，必须将其编码为过渡路线类型3、6、9或S。当一个STAR航线/剖面下降航线或STAR航线/剖面下降航线的一部分在过渡标识符中重复出现且具有不同的修正点标识符时，必须将其编码为航线过渡路线类型1、4、7或F。
  5.7 当到达航线与进近航线服务于相同的跑道或停机坪，并且到达航线与进近过渡存在重叠时，必须根据源文件的规定将到达航线和进近过渡的全部内容进行编码。

进近程序一般编码规则

适用于所有程序类型的进近程序规则

  6.0 Approach Procedure Rules Valid For All Procedure Types
  6.0 适用于所有程序类型的进近程序规则

多种进近程序编码

  6.1 Multiple Approach Procedure Coding
   6.1.1 Multiple Approach Procedure Definition
  1. ILS Localizer 8. RNAV 15. RNAV, GPS Required
  2. IGS Localizer 9. VORDME 16. FMS
  3. LDA Localizer 10. VORTAC 17. GPS
  4. SDF Localizer 11. VOR (no DME) 18. LAAS-GPS/GLS
  5. Localizer (Only) 12. TACAN 19. WAAS-GPS
  6. Localizer Backcourse 13. NDB + DME
  7. MLS (all types) 14. NDB
Notes: GPS, GLS, RNAV, LAAS, and WAAS are not facility types but rather an equipment classification. RNAV procedures use VORDME or VORTAC navaids along with the RNAV equipment. For the purpose of these rules, RNAV is to be considered a facility type. This will allow coding of a RNAV and VORDME or VORTAC procedure to the same runway or helipad. For GPS, GLS, WAAS, and LAAS a GPS or GLS sensor input to the equipment is required. Circle to Land minimum version of the various approach sensors are covered through the Approach Route Qualifier (see Section 5.7). Circle-To-Land is not a facility type but rather a weather minimum criteria. For the purpose of these rules, Circle-To-Land is to be considered an equal to the procedure reference facility. This will normally rule out coding of “straight-in” and“circling” procedures using the same reference facility to one and the same runway or helipad, even though different “Route Types” are involved. There are three types of MLS Approach, each with a unique Route Type. Normally, there will only be one approach referencing MLS to any given runway or helipad.
   6.1.2 Multiple Approach Procedure Identifiers
  Multiple approach procedures are identified by unique procedure identifiers and unique route types (refer to Sections 5.7 and 5.10 of this specification).
   6.1.3 Multiple Approach Procedure Waypoints
  Multiple approach procedures to one and the same runway or helipad may require multiple final approach segment waypoints of the same category such as FACF, FAF and missed approach point. Where such waypoints are not established with unique identifiers through source documentation, the data base supplier must create the required waypoints and assign unique identifiers, using Section 7.2.6 of this specification.
   6.1.4 Multiple Approach Procedure Detail Specific details of approach procedures such as speed, altitudes and vertical angles are considered unique for the procedure and must be coded in those records where they apply, including duplication of such detail where appropriate.
   6.1.5 Transitions in Multiple Approach Procedure Coding
    6.1.5.1 Approach transitions are coded to be used together with specific approach procedures. As such, a transition route must be unique to a given approach,“multiple use” with more than one approach cannot be coded. Transition routes required for more than one approach must be coded multiple times.
    6.1.5.2 If an approach transition route is be coded multiple times, it must be coded with an identifier that is unique to the approach procedure for which it is to be used.

  6.1 多种方法程序编码
   6.1.1 多种方法程序定义
  1. ILS航向台 8. RNAV 15. RNAV, 需要GPS
  2. IGS航向台 9. VORDME 16. FMS
  3. LDA航向台 10. VORTAC 17. GPS
  4. SDF航向台 11. VOR (无DME) 18. LAAS-GPS/GLS
  5. 仅航向台 12. TACAN 19. WAAS-GPS
  6. 反向航向台 13. NDB + DME
  7. MLS (所有类型) 14. NDB
  注:GPS、GLS、RNAV、LAAS和WAAS不是设施类型,而是设备分类。RNAV程序使用VORDME或VORTAC导航设备以及RNAV设备。对于这些规则,RNAV应被视为设施类型。这将允许将RNAV和VORDME或VORTAC程序编码到同一跑道或直升机停机坪。对于GPS、GLS、WAAS和LAAS，需要将GPS或GLS传感器输入到该设备中。各种进近传感器的盘旋着陆最低版本通过进近路线限定器进行覆盖(参见第5.7节)。盘旋着陆不是设施类型，而是天气最低标准。对于这些规则，盘旋着陆被视为等同于程序参考设施。这通常排除了使用相同的参考设施对“直飞”和“盘旋”程序进行编码的可能性，尽管涉及了不同的“航线类型”。MLS进近有三种类型，每种类型都有一个独特的航线类型。通常，任何给定的跑道或直升机停机坪只有一个引用MLS的进近。
   6.1.2 多种方法程序标识符
  多种方法程序通过唯一的程序标识符和独特的航线类型进行标识(参见本规范的第5.7和第5.10节)。
   6.1.3 多种方法程序航路点
  对于同一跑道或直升机停机坪的多种方法程序可能需要多个同一类别的最终进近航段航路点，如最后校准进近点(FACF)、最后进近航点(FAF)和复飞点。如果这些航路点没有通过源文件的唯一标识符进行确认,数据库供应商必须使用本规范的第7.2.6节创建所需的航路点并分配唯一的标识符。
   6.1.4 多种方法程序详细信息
  进近程序的特定细节，如速度、高度和垂直角度，被视为该程序特有的，并且必须在适用的记录中进行编码，包括在适当的情况下复制这些详细信息。
   6.1.5 多种方法程序编码中的过渡
    6.1.5.1 进近过渡被编码为与特定进近程序一起使用。因此，过渡航线必须对于给定的进近是唯一的，不能进行“多用途”编码用于多个进近。需要用于多个进近的过渡航线必须进行多次编码。
    6.1.5.2 如果一个进近过渡航线需要多次编码，它必须使用与其所要使用的进近程序唯一的标识符进行编码。

适用于所有进近航线编码的一般规则。

  6.2 General Rules, Applicable to All Approach Route Coding.
   6.2.1 “Altitudes” used in approach route coding between the final approach course fix (FACF) and the runway or helipad or missed approach point will be coded in combination with Altitude Description Codes as detailed in Section 5.29 of this specification and in accordance with government source documents. This coding rule is intended to match the altitude publishing methods in official government sources, which may specify altitudes as minimum, maximum, mandatory, recommended, or between altitudes, defined with a minimum and a maximum altitude. These definitions include two kinds of altitudes. One is “procedural altitudes” information on mandatory or minimum altitudes at designated fixes along the final approach path. The other is the altitude related to the electronic Glide Slope or published vertical angle with recommended altitudes. The ordering of Procedural and Glide slope altitudes in the first and second altitude fields is accomplished in accordance with Section 5.29.
   6.2.2 All fixes associated with the lateral and vertical path of approach procedures must be coded, including stepdown fixes, both before and after the Final Approach Fix.
   6.2.3 With the exception of the NDB + DME Approach or a Helicopter version of a NDB + DME Approach, the recommended Navaid must be the same facility for all legs of a final approach (missed approach sequences not included) that require a recommended facility. The recommended Navaid must be the procedure reference facility. For Approach Transition Routes, the recommended Navaid will be the procedure reference facility or a VORDME or VORTAC facility. When a VORDME or VORTAC is coded as the recommended Navaid in approach procedure coding, the Navaid will be within 40 NM of the fix in which it is coded. GPS approach procedures do not include a recommended Navaid. GLS approach procedures will reference the GLS facility. For specific rules on recommended Navaid for NDB + DME Approach Procedures, see Rule 6.8.1.4.b of this Attachment.
   6.2.4 If a PI leg is from the FAF waypoint and the distance between the FACF and the FAF is less than 6.0 NM, code a CF leg after the PI, with the FACF as the fix in the CF. The route distance leg data field on the CF leg will be the difference between the distance coded on the PI leg and the distance between the FACF and FAF waypoints.
   6.2.5 Approach Procedure Fix Requirements:
  - All approach procedure coding requires a Final Approach Fix (FAF) and a Missed Approach Point Fix (MAP).
  - The coding of Final Approach Course Fix (FACF) must be accomplished using the following rules:
  - A FACF Waypoint is required on all localizer based approaches, including, ILS, LOC, SDF, LDA, IGS and LOC Backcourse.
  - A FACF Waypoint is required on all other Approach Procedure coding:
  - At a published Intermediate Fix
  - When published by source
  - When a named fix at common ending point for transitions exists
  - When transitions end in the intercept of a track rather than to a fix.
  When the course or track inbound to the FAF is different than the course or track from the FAF to the MAP. This requirement will be met by the addition of data supplier created FACF waypoints as indicated in Rule 6.2.5.2.
    6.2.5.1 Transitions may end at a FAF fix regardless of whether a FACF is coded for the procedure or not.
    6.2.5.2 If no waypoint is established by source documentation for the final approach course fix and one is required by the requirements in Rule 6.2.5, one must be computed by the data supplier. For Localizer based approach procedures, the computer FACF will be on the localizer course at a distance of 2 to 8NM from the Final Approach Fix (FAF). For all other approach types, the FACF will be computed on the published course to the FAF at a distance not less than 2NM to the FAF. See Section 2, Subsection 2.3, Special Navigation Terms. Altitude coding for this fix is defined in Rule 6.2.10.

  6.2 适用于所有进近航线编码的一般规则。
   6.2.1 进近航线编码中在最后校准进近点(FACF)与跑道或直升机停机坪或复飞点之间使用的“高度”将与高度描述代码结合使用，详见本规范的第5.29节，并根据政府源文件的规定进行。此编码规则旨在与官方政府源文件中的高度发布方法匹配，这些方法可能以最低、最高、强制、建议或高度之间的范围进行定义，其中高度范围由最小和最大高度确定。这些定义包括两种类型的高度。一种是“程序高度”，提供了沿着最后进近路径的指定修正点处的强制或最低高度信息。另一种是与电子下滑坡道或发布的垂直角度相关的高度和建议高度。按照第5.29节的规定，将过程高度和下滑坡高度按照第一和第二高度字段的顺序进行排序。
   6.2.2 必须编码与进近程序的横向和垂直航迹相关的所有修正点，包括最后进近修正点之前和之后的下降修正点。
   6.2.3 除了NDB + DME进近或NDB + DME进近的直升机版本外，所有最后进近的所有航段(不包括复飞序列)都必须使用相同的推荐设备。推荐设备必须是程序参考设施。对于过渡航路，推荐设备将是程序参考设施或VORDME或VORTAC设施。当在进近程式编码中将VORDME或VORTAC编码为推荐设备时，该设备与其编码的修正点之间的距离必须在40海里以内。GPS进近不能指定推荐设备。GLS进近将引用GLS设施。有关NDB + DME进近程序推荐设备的具体规则，请参阅本文附件的规则6.8.1.4.b。
   6.2.4 如果PI航段是从FAF航路点开始并且FACF和FAF之间的距离小于6.0海里，请在PI之后编码一个CF航段，以FACF作为CF中的修正点。CF航段上的航路距离数据字段将是在PI航段上编码的距离与FACF和FAF航路点之间的距离之差。
   6.2.5 进近程式修正点要求：
  - 所有进近程式编码都需要一个最后进近修正点(FAF)和一个复飞点修正点 (MAP)。
  - 对于最后进近航路修正点(FACF)的编码必须遵循以下规则：
  - 所有基于航向台的进近，包括ILS、LOC、SDF、LDA、IGS和LOC后程进近都需要一个FACF航路点。
  - 所有其他进近程式编码都需要一个FACF航路点：
  - 在已发布的中间修正点处
  - 当由源文件发布时
  - 当存在一个用于过渡的共同结束点的命名修正点时
  - 当过渡以道线交叉截面为结束点而不是修正点时
  进近到FAF的航向或航迹与FAF到MAP的航向或航迹不同时，必须添加由数据供应商创建的FACF航路点，以满足此要求，如规则6.2.5.2中所示。
    6.2.5.1 无论是否为该进近过程编码了FACF，过渡可以在FAF修正点结束。
    6.2.5.2 如果源文件没有为最后进近航路修正点建立航路点，并且根据规则6.2.5的要求需要一个航路点，则数据供应商必须计算一个航路点。对于基于航向台的进近程式，计算机计算的FACF将位于最后进近修正点(FAF)距离为2到8海里的航向台航线上。对于所有其他进近类型，FACF将在发布的FAF航向上计算，距离FAF不少于2海里。参见第2节第2.3小节，特殊导航术语。此修正点的高度编码定义在规则6.2.10中。

    6.2.5.3 If no waypoint is established by source documentation for the Final Approach Fix (FAF), one mustbe computed on the final approach course, using the initial approach altitude and the vertical escent angle (source or computed). For non-precision approach procedures such as VOR or NDB, the minimum distance between the FAF and the runway threshold or helipad alighting point (or MAP) will be 4 nautical miles. For Localizer and GLS based approach procedures, establish the FAF, when none is provided by source, at the nominal outer marker position.
    6.2.5.4 Except as indicated below, the published Missed Approach Point (MAP) is always coded as part of the approach procedure. This fix may be a runway threshold, helipad alighting point or a dedicated missed approach point fix waypoint. The published missed approach point may be replaced by a database supplier fix when it can be determined that the published fix is within 0.14NM of the landing threshold or helipad alighting point on the centerline or extended centerline. If the published MAP is a Navaid and is within 0.14NM of the threshold or helipad alighting point, the MAP will remain at the Navaid position. In these cases, the altitude assigned to the MAP will be a calculated altitude that is on a path that continues over the threshold at 50 feet. Such an altitude constraint must not be below the threshold/alighting point elevation.
   6.2.6 Straight-in Criteria, FAA type procedures Refer to Appendix 2
   6.2.7 Straight-in Criteria, ICAO type procedures Refer to Appendix 2
   6.2.8 Intentionally left blank
   6.2.9 Lateral Coding Rules
  All approach procedure coding must be to the published Missed Approach Point, as indicated below. Missed Approach Procedure coding must begin at that point. For missed approach procedure coding, refer toSection Nine of this Attachment. For the rules that follow, the term “runway threshold” is meant to refer either to the landing threshold point (LTP) of an actual runway or to a helipad alighting point (HAP), when the procedure is coded to a helipad.
    6.2.9.1 If the published Missed Approach Point is a fix prior to the runway threshold, lateral coding is to that published Missed Approach Point.
    6.2.9.2 If the published Missed Approach Point is the runway threshold, lateral coding is to the runway threshold as the published Missed Approach Point.
    6.2.9.3 If the published missed approach point is beyond the runway threshold and the runway threshold will be coded as a fix in the lateral path that fix will be on the established path, with no course changes.
    6.2.9.4 If the published Missed Approach Point is beyond the runway threshold and no runway threshold fix has been inserted into the lateral path, code a “Final End Point,” which is calculated at a location on the final approach track where a line from the runway threshold intersects the track at a 90 degree angle. Lateral coding will still be to the published missed approach point.
    6.2.9.5 If the published Missed Approach Point is abeam the runway threshold, lateral coding must be to the published Missed Approach Point. Refer to the Examples 1 through 15 at the end of this section for a visual depiction of these rules.
   6.2.10 Vertical Coding Rules, Procedure Fix Altitudes
   Approach Procedure Coding is provided through two elements, Procedure Fix Altitudes and a Vertical Angle. This section covers the Fix Altitude. Sections 7 and 8 cover the Vertical Angle for Precision and Non-Precision Approach Procedures
    6.2.10.1 Procedure Fix Altitudes, Final Approach Course Fix and Final Approach Fix.
Procedure Fix Altitudes for the Final Approach Course Fix will be coded according to official government sources and will be left blank when no altitude data is provided by the source. When coded, these altitudes will be assigned altitude descriptions codes indicating the altitude as mandatory, minimum or recommended (see Section 5.29 of this Specification). When the coded Final Approach Fix is established by the government source procedure data, the altitudes for this fix will also be coded according to official government sources.
  These altitudes will be assigned altitude descriptions codes indicating the altitude as mandatory, minimum or recommended (see Section 5.29 of this Specification). For government supplied altitude data, both Altitude 1 and Altitude 2 may be provided. If the Final Approach Fix is as an established fix rather than a published fix, the altitude for this fix must be computed using the procedures detailed in Sections 7 and 8 of this Attachment. For calculated altitude data, only Altitude 1 will be provided.
    6.2.10.2 Procedure Fix Altitudes for the published Missed Approach Point, a runway threshold fix prior to the published Missed Approach Point or a Final End Point prior to the Missed Approach Point must be as indicated below.
    6.2.10.2.a For a published Missed Approach Point prior to the runway threshold, an “at” altitude equal to the computed altitude at the published Missed Approach Point must be coded in Altitude 1. (See example 7)
    6.2.10.2.b For a published Missed Approach Point at the runway threshold, an “at” altitude equal to the runway threshold elevation plus the published TCH must be coded in Altitude 1. If TCH is not specified by source then use 50 feet.
    6.2.10.2.c For a Missed Approach Point beyond the runway threshold and where the runway threshold has been included in the lateral path, code an”at” altitude equal to the runway threshold elevation plus the published TCH. If TCH is not specified by source then use 50 feet in Altitude 1 of the runway threshold fix record. Do
not code an altitude on the MAP for this case.
    6.2.10.2.d For the Missed Approach Point beyond the runway threshold and if a Final End Point is coded, then code an “at” altitude for the Final End Point equal to the runway threshold elevation plus the published TCH in Altitude 1 of the Final End Point Record. If TCH is not specified by source, then use 50 feet. Code an “at or above” altitude on the MAP record equal to the airport elevation plus 400 feet or a value specified by source.
    6.2.10.2.e For a published Missed Approach Point abeam the runway threshold, code the altitude equal to the runway threshold elevation plus the published TCH. If TCH is not specified by source then use 50 feet.
    6.2.10.3 Step down fixes will have altitude codes according to the government source documentation. These altitudes will be assigned altitude descriptions codes indicating the altitude as mandatory, minimum or recommended and altitudes on the vertical path (see Section 5.29 of this Specification). Both Altitude 1 and Altitude 2 will be used on step-down fixes.
   6.2.11 Vertical angle information is in Section 7 and 8 of Attachment 5 in this document.
   6.2.12 Missed Approach Point
  In general, the design of missed approach procedures require that the runway, helipad or missed approach point be overflown prior to commencing any turn. In these cases, to ensure procedure coding reflects design specific intentions, the Overfly Indication must be coded into the Waypoint Description field. However, certain types of approach procedures design do require a turn prior to the runway, helipad or missed approach point. In these cases, to ensure procedure coding reflects design specific intentions, the Overfly Indication will not be set in the Waypoint Description field of the appropriate record.

    6.2.5.3 如果最后进近修正点(FAF)没有在源文件中建立航路点，则必须根据初始进近高度和垂直下降角(来自源文件或计算)在最后进近航线上计算一个。对于非精密进近，如VOR或NDB，FAF和跑道或直升机停机坪(或MAP)之间的最小距离为4海里。对于基于航向台和GLS的进近程序，当源文件未提供FAF时，在标称外部标识位置建立FAF航路点。
    6.2.5.4 除非另有说明，发布的复飞点(MAP)始终编码为进近程序的一部分。该修正点可以是跑道阈值、直升机停机坪着陆点或专用的复飞点航路点。如果确定发布的修正点距离着陆跑道或直升机着陆点在中心线或延长中心线上的0.14NM以内，则可以用数据库供应商的修正点替换发布的复飞点。在这种情况下，分配给复飞点的高度将是一个计算出的高度，沿着继续越过阈值的航道上保持在50英尺高度。这种高度限制不能低于阈值/着陆点的高度。
   6.2.6 直飞准则，FAA类型程序 请参阅附录2
   6.2.7 直飞准则，ICAO类型程序 请参阅附录2
   6.2.8 故意空白
   6.2.9 横向编码规则
  所有进近程序编码必须到达发布的复飞点，如下所示。复飞程序编码必须从该点开始。关于复飞程序编码的规则，请参阅本附件的第九节。在接下来的规则中，术语“跑道阈值”意味着要么指实际跑道的着陆入口(LTP)，要么指编码到直升机停机坪的着陆点(HAP)，当程序编码到直升机停机坪时。
    6.2.9.1 如果发布的复飞点在跑道阈值之前的修正点上，横向编码将到达该发布的复飞点。
    6.2.9.2 如果发布的复飞点是跑道阈值，横向编码将到达作为发布的复飞点的跑道阈值。
    6.2.9.3 如果发布的复飞点在跑道阈值之后，并且已在横向航迹中插入跑道阈值修正点，则该修正点将位于已建立的航迹上，没有航向变化。
    6.2.9.4 如果发布的复飞点在跑道阈值之后，并且在横向航迹中没有插入跑道阈值修正点，则编码一个“最终终点”，该点在最后进近航迹上的位置通过一条从跑道阈值垂直相交的线确定。横向编码仍然是到达发布的复飞点。
    6.2.9.5 如果发布的复飞点与跑道阈值相交，横向编码必须到达发布的复飞点。 请参考本节末尾的示例1至15,以对这些规则进行可视化描述。
   6.2.10 垂直编码规则，程序修正点高度
垂直进近程序编码通过两个元素提供，即程序修正点的高度和垂直角度。本节涵盖修正点高度。第7和第8节涵盖了精密和非精密进近程序的垂直角度。
    6.2.10.1 最后进近航路修正点和最后进近修正点的程序修正点高度。
    最后进近航路修正点的程序修正点高度将根据官方政府源文件进行编码，如果源文件没有提供高度数据，则将留空。当进行编码时，这些高度将被分配高度描述代码，表示高度为强制、最低或建议高度(参见本规范的第5.29节)。当编码的最后进近修正点是由政府源程序数据建立的而不是发布的修正点时，该修正点的高度也将根据官方政府源文件进行编码。这些高度将被分配高度描述代码，表示高度为强制、最低或建议高度(参见本规范的第5.29节)。对于政府提供的高度数据，可能会提供高度1和高度2。如果最后进近修正点是作为已建立修正点而不是发布修正点，那么必须使用本附件第7和第8节中详细说明的过程计算该修正点的高度。对于计算出的高度数据，只提供高度1。
    6.2.10.2 对于发布的复飞点、跑道阈值修正点或复飞点之前的最终终点，其程序修正点高度规则如下。
    6.2.10.2.a 如果复飞点位于跑道阈值之前，高度1的“at”高度应与复飞点处计算得到的高度相等。(参见示例7)
    6.2.10.2.b 如果复飞点位于跑道阈值上，高度1的“at”高度应为跑道阈值标高加上发布的TCH。如果源文件未指定TCH，则使用50英尺。
    6.2.10.2.c 如果复飞点位于跑道阈值之后，且在横向航迹中包括了跑道阈值，则高度1的“at”高度应为跑道阈值标高加上发布的TCH。如果源文件未指定TCH，则在跑道阈值修正点记录的高度1中使用50英尺。在此情况下，复飞点不会编码高度。
    6.2.10.2.d 如果复飞点位于跑道阈值之后，且编码了最终终点，则最终终点的高度1应为跑道阈值标高加上发布的TCH。如果源文件未指定TCH，则在最终终点记录的高度1中使用50英尺。复飞点的高度记录应为“按或以上”，等于机场标高加上400英尺，或源文件指定的值。
    6.2.10.2.e 如果发布的复飞点位于跑道阈值的旁边，则高度1的高度应为跑道阈值标高加上发布的TCH。如果源文件未指定TCH，则使用50英尺。
    6.2.10.3 降低修正点的高度将根据政府的源文件进行编码。这些高度将被分配高度描述代码，表示高度为强制、最低或建议高度，并且适用于垂直航迹上的高度(参见本规范的第5.29节)。降低修正点上将使用高度1和高度2。
   6.2.11 垂直角度的信息在本文件的附录5的第7和第8节中。
   6.2.12 复飞点
   一般情况下，复飞程序的设计要求在开始任何转弯之前必须飞越跑道、直升机停机坪或复飞点。在这些情况下，为确保程序编码反映设计具体意图，必须在航路点描述字段中编码“飞越标记”。然而，某些类型的进近程序设计要求在飞越跑道、直升机停机坪或复飞点之前进行转弯。在这些情况下，为确保程序编码反映设计具体意图，在相应记录的航路点描述字段中不设置“飞越标记”。

进近过渡航路编码规则

  6.3 Approach Transition Route Coding Rules
   6.3.1 Recommended coding on approach transitions that end in leg to fix (“XF”) is that the fix in the ending leg must be either the Final Approach Course Fix or the Final Approach Fix. If this is not the case, for example HF leg type transitions on fixes off-set from the final approach path, a series of legs must be substituted representing the original flight path, but ending with a CF or TF1leg type to one of these two fixes. If neither of these two coding recommendations can be followed, such as in cases where the “XF” would terminate atthe missed approach waypoint or a step-down fix not associated with the lateral guidance of the final approach, the transition must be omitted.
   6.3.2 When a holding pattern used for course reversal or a procedure turn is part of an approach route, it will be included in an approach transition route.
   6.3.3 If an approach transition for a specific runway or helipad is common to more than one approach, that transition must be coded for each approach, with a transition identifier that must correspond to the approach procedure identifier.
   6.3.4 Rule Deleted by Supplement 16
   6.3.5 Transitions of VOR based approach procedures, TACAN based approach procedures, and RNAV approach procedures.
    6.3.5.1 Any recommended navaid used in coding must be a VOR, VORDME, VORTAC, TACAN, DME, NDB or Un-Biased ILS DME, see Section 5.23 of this document.
   6.3.6 Transitions for Localizer Based Approach Procedures
    6.3.6.1 The ending leg of all localizer-based transitions will either –
  - end at the FACF (AF, CF, RF, TF, HF, HM) - end in an intercept of the localizer inside the FACF (PI, CI or VI)
  - end in a course reversal, normally at the FAF (HF, HM)
    6.3.6.2 The ending leg of all localizer-based transitions will contain a recommended Navaid –
  - if CF, RF, TF, CI or VI, the recommended Navaid will be the procedure reference localizer
  - if AF, HF, HM or PI, the recommended Navaid will be a VORDME or VORTAC or TACAN
  - the HF, HM and PI leg may use the procedure reference localizer when a VORDME, VORTAC or TACAN is not available.
    6.3.6.3 Deleted by Supplement 17.
    6.3.6.4 Legs ending in an intercept will ideally be at angles of 30 degrees to the track intercepted. Angles between 10 and 90 degrees may be coded as required by source documentation, provided the resulting intercept is within the reception area of the localizer.
    6.3.6.5 When a CF leg is used as the ending leg of a transition to a localizer-based procedure, the maximum leg distance will be within 8NM of the FACF or within the reception area of the localizer as depicted in Figure A5-6-1.
Note: An FC/CF is preferred over a TF as illustrated in Figure A5-6-1 for those legs ending at a fix.

    6.3.6.6 When a CI or VI leg is used as the ending leg of a transition to a localizer-based procedure, the intercept will be between the FACF and the FAF, at no less than 2 NM to the FAF.
   6.3.7 Transitions for NDB Based Approach Procedures:
    6.3.7.1 Transitions for NDB based approach procedures may use a NDB Navaid as the recommended Navaid, except for transitions that are DME Arcs.
   6.3.8 Transitions for MLS/GLS Approach Procedures:
    6.3.8.1 MLS/GLS approach procedure coding is such that the rules can be identical to those used for Localizer based procedure coding.
   6.3.9 Transitions for Circle-To-Landing Approach Procedures
    6.3.9.1 If the Circle-To-Land approach procedure is runway or helipad dependent, the rules on transition route coding are identical to those of the reference facility procedure type, e.g. for a VOR Circle-To-Land that is runway dependent, follow the VOR based approach procedure rules for approach transition route coding.
    6.3.9.2 If the Circle-To-Land approach procedure is not runway or helipad dependent, being valid for more than one landing direction, the rules for coding approach transitions routes are as follows.
    6.3.9.3 Recommended navaids used in coding all legs except ending legs must be a VOR, VORDME, VORTAC, DME or Un-Biased ILSDME. For the ending leg sequences, the recommended navaid, where required, must be the procedure reference facility, see Section 5.23 of this document.

  6.3 进近过渡航路编码规则
   6.3.1 对于以航路点为终点的进近过渡，该航路点必须是最后进近航路修正点或最后进近修正点。如果不是这种情况，例如HF类型的航路段转变到与最后进近航迹偏离的修正点，必须用一系列航路段替代，表示原始飞行航迹，但以CF或TF1类型航路段终止在这两个修正点之一。如果不能按照这两个编码建议进行编码，比如在“XF”结束于复飞航路点或与最后进近航迹的横向指导无关的下降修正点的步骤情况下，必须省略过渡航路。
   6.3.2 如果倒转航向或程序转弯中使用了盘旋保持航迹，则它将包含在进近过渡航路中。
   6.3.3 如果一个特定跑道或直升机停机坪的进近过渡适用于多个进近，每个进近都必须对该过渡进行编码，过渡标识符必须与进近程序标识符对应。
   6.3.4 由第16版补充删除。
   6.3.5 VOR进近程序、TACAN进近程序和RNAV进近程序的过渡航路。6.3.5.1 编码中使用的推荐导航设施必须是VOR、VORDME、VORTAC、TACAN、DME、NDB或Un-Biased ILS DME，参见本文档的第5.23节。
   6.3.6 基于航向台的进近程序的过渡航路。6.3.6.1 所有基于航向台的过渡的末尾航路段将以FACF (AF、CF、RF、TF、HF、HM)结束，或以FACF内的航向台拦截结束(PI、CI或VI)，或在FAF正常情况下进行航迹反转(HF、HM)。
    6.3.6.2 所有基于航向台的过渡的末尾航路段将包括一个推荐设施 – 如果是CF、RF、TF、CI或VI，推荐设施将是程序参考航向台；如果是AF、HF、HM或PI，推荐设施将是VORDME、VORTAC或TACAN；如果没有可用的VORDME、VORTAC或TACAN，则在HF、HM和PI航路段中可以使用程序参考航向台。
    6.3.6.3 末尾航路段中的拦截角度理想情况下应为与被拦截航迹成30度角。根据源文件的要求，可以编码介于10到90度之间的角度，但要确保拦截结果位于航向台的接收范围内。
    6.3.6.4 如果CF航段用作进近过渡的最后一段，最大航段距离将在FACF附近8海里内，或者根据图A5-6-1中显示的航向台接收范围进行编码。
  注：对于以修正点结束的情况，FC/CF优于TF，如图A5-6-1所示。
    6.3.6.5 如果CI或VI航段用作进近过渡的最后一段，拦截点将位于FACF和FAF之间，与FAF距离不少于2海里。
   6.3.7 基于NDB的进近程序的过渡。
    6.3.7.1 基于NDB的进近程序的过渡可以使用NDB导航设施作为推荐导航设施，但DME弧线的过渡除外。
   6.3.8 基于MLS/GLS的进近程序的过渡。
    6.3.8.1 MLS/GLS进近程序的编码规则可以与基于航向台的进近程序的编码规则相同。
   6.3.9 盘旋着陆型进近程序的过渡。
    6.3.9.1 如果盘旋着陆的进近程序是以跑道或直升机停机坪为依据的，则进近过渡航路的编码规则与参考设施程序类型的规则相同，例如对于以VOR为依据的盘旋着陆程序，遵循基于VOR的进近程序的过渡航路编码规则。
    6.3.9.2 如果盘旋着陆程序不依赖于特定跑道或直升机停机坪，而适用于多个降落方向，则编码盘旋着陆过程的过渡航路的规则如下。
    6.3.9.3 在编码的所有航段，除了结束航段，推荐的导航设施必须是VOR、VORDME、VORTAC、DME或无偏航向仪ILS DME。对于结束航段序列，如果需要推荐的导航设施，则必须是程序参考设施，请参见本文档的第5.23节。

基于航向台的进近程序编码

  6.4 Localizer Based Approach Procedure Coding
   6.4.1 The following rules apply to the coding of the “final approach segment” of all Localizer based approach procedures. Localizer based approach procedures include Full ILS (Localizer and GS), Localizer only, IGS (Instrument Guidance System), LDA (Localizer type Directional Aid) and SDF (Simplified Directional Aid) procedures.
    6.4.1.1 All Localizer based approach procedures must begin at the FACF. They must consist of a FACF, FAF and runway Fix (precision approach) or missed approach point fix (non-precision approach). A Runway Centerline Intercept (RCI) point may be coded in some non-precision, Localizer based procedures.
    6.4.1.2 The FACF is defined as a fix located on the localizer beam center, 8NM or less from the FAF or within the reception range of the Localizer. This may be a source document provided fix or a fix created using these positioning rules.
    6.4.1.3 The FACF is coded as an IF leg with an altitude assigned, based on the source document or equal to the altitude of a procedure turn or the altitude of the last transition leg.
    6.4.1.4 The track from the FACF to the FAF is coded as a CF or a TF leg with altitude constraints as indicated for the specific procedure types below.
    6.4.1.5 The recommended navaid will be the procedure reference localizer. Theta and Rho will be provided from the localizer for each sequence of the final approach, including the runway fix and/or missed approach point.
    6.4.1.6 The “Outbound Magnetic Course” field in all sequences will be equal to the localizer magnetic bearing, rounded to the nearest whole degree, derived from official government source.
   6.4.2 Full ILS (Localizer and Glide Slope) Precision Approach Procedure
    6.4.2.1 For full ILS procedures, code the glide slope intercept altitude in the altitude 2 field of the FACF record, if an intercept altitude is required. If the procedure requires a constant descent from the FACF to the runway, then altitude 2 will be blank.
    6.4.2.2 For full ILS procedures, a missed approach point beyond the runway is not allowed, therefore rules 6.2.9.3,
    6.2.9.4, 6.2.9.5, 6.2.10.2.c, 6.2.10.2.d, and 6.2.10.2.e do not apply.

  6.4 基于航向台的进近程序编码。
   6.4.1 适用于所有基于航向台的进近程序的“最后进近航段”的编码规则。基于航向台的进近程序包括完整的ILS(航向台和下滑坡道)进近、仅航向台进近、IGS（仪表引导系统）、LDA（航向台类型定向设备）和SDF（简化型定向设备）进近。
    6.4.1.1 所有基于航向台的进近程序必须从FACF开始。它们必须包括一个FACF、FAF和航道修正点（精密进近）或复飞点（非精密进近）。某些非精密的基于航向台的程序中可以编码跑道中心线拦截(RCI)点。
    6.4.1.2 FACF被定义为航向台波束中心的一个修正点，距离FAF不超过8NM，或者在航向台的接收范围内。它可以是源文件中提供的修正点，也可以是使用这些定位规则创建的修正点。
    6.4.1.3 FACF以一个IF航段进行编码，并分配一个高度，该高度可以根据源文件进行设定，或者等于程序转弯或最后过渡航段的高度。
    6.4.1.4 从FACF到FAF的航迹编码为CF或TF航段，具体的高度约束规则如下所示，针对不同的程序类型。
    6.4.1.5 推荐的导航设施将是程序参考航向台。对于最终进近过程中的每个航段，包括航道修正点和/或复飞点，航向台将提供Theta和Rho。
    6.4.1.6 所有航段中的“外行磁向”字段将等于航向台的磁向，四舍五入取整，根据官方政府源文件获得。
   6.4.2 完整的ILS（航向台和下滑坡道）精密进近程序。
    6.4.2.1 对于完整的ILS程序，如果需要拦截高度，则将下滑坡拦截高度编码到FACF记录的高度2字段中。如果该程序要求从FACF到跑道的高度保持恒定下降，则高度2将为空白。
    6.4.2.2 对于完整的ILS程序，不允许在跑道之外设置复飞点，因此规则6.2.9.3、6.2.9.4、6.2.9.5、6.2.10.2.c、6.2.10.2.d和6.2.10.2.e不适用。

基于MLS的进近程序编码

  6.5 MLS Approach Procedure Coding
  MLS Approach Procedure Code utilizing raw azimuth and elevation data is limited to those procedures which are designed as a localizer equivalent. If such a procedures is coded, the rules for the “final approach segments” are to be identical with those stated in Section 6.4 above. The Route Type of such approaches will be coded as “M” in column 20 of the primary approach record. Approach procedures predicated on the use of MLS Area Navigation (MLS/RNAV) will be coded with a “W” or “Y” in column 20 of the primary approach record. MLS/RNAV approaches are coded as described below.
  There are three types of MLS/RNAV approaches, listed in increasing level of complexity, computed lateral/raw vertical guidance, computer lateral and vertical guidance and curved path.
   6.5.1 Approaches using computed lateral path and raw vertical path guidance, also referred to as Type “A,” will be used primarily where the MLS azimuth transmitter cannot be located on the extended runway centerline, but the elevation transmitter is sited normally abeam the touchdown point. All legs will be straight and aligned with the inbound course. The will be codes with Route Type “W” in column 20 of the primary approach record. Path definition will be the equivalent of a full ILS approach (Rule 6.4.2) with the exception that the leg from the PFAF inbound will be a “TF” leg, terminating at the runway waypoint, with the published final approach source in the Outbound Magnetic Course field. The PFAF will be coded as the Final Approach Fix in the Waypoint Description field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix.
   6.5.2 Approach using computed lateral and vertical guidance by no curved legs, also referred to as Type “B,” will be coded as Route Type “Y” in column 20 of the primary approach record. All legs will be straight and aligned with the inbound course. Path definition will be the equivalent of the full ILS approach (Rule 6.4.2) with the exception that the leg from the PFAF inbound will be a “TF” leg, with the published final approach course in the Outbound Magnetic Course field. The altitude of the PFAF and all waypoints inbound from it will be the glide path altitude at that point. The PFAF will be coded as the Final Approach Fix in Waypoint Description field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix.
   6.5.3 MLS/RNAV approaches using curved legs, also referred to as Type “C,” will be used for a variety of reasons, including parallel sidestep approaches, separation of different categories of aircraft, noise abatement, etc. These will always be precision approaches. They will be coded a with a Route type of “Y” in column 20 of the primary approach record. The following rules apply:
    6.5.3.1 The first leg of an MLS/RNAV approach with curved legs will be an “IF/TF” leg combination. All other straight legs will be coded as “TF” legs. All “TF” legs in an MLS/RNAV with curved legs procedure will have the published course included in the Outbound Magnetic Course field.
    6.5.3.2 All curved legs will be coded as “RF” legs. Every leg preceding or following an “RF” leg will be tangent to the “RF” leg at that point.
    6.5.3.3 The initial portion of a MLS/RNAV approach with curved legs may be an “IF/RF” combination provided a straight leg approach transition is coded to the point in the “IF” and the rules in Section 6.5.2 are complied with.
    6.5.3.4 The PFAF will be coded as the Final Approach Fix in the Waypoint Description field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix. If there is not a fix at the glide path intercept, then the first fix after the intercept will be the PFAF. There must be one and only one PFAF for each MLS/RNAV approach with curved legs.
    6.5.3.5 The last leg of an approach transition prior to an MLS/RNAV approach will be one of the following types CF, CI, HF, PI, RF or TF, except as indicated in Section 6.5.3.3. If the leg type is CF, CI, RF or TF, then the Recommended Navaid will contain the identifier of the MLS used for the approach. If the leg type is PI or HF, then the Recommended Navaid will contain the VHF Navaid the defines the PI or HF leg.
    6.5.3.6 If the last leg prior to the approach is a “CI” leg, the intercept angle will be 300 or less, and the intercept point will be between the first and second terminator fixes in the approach, but no closer that 2NM to the second fix.
    6.5.3.7 The PFAF and the FACF altitudes will be coded according to the rules outlined for Precision Approach Procedures in Rule 6.4.2.
   6.5.4 The PFAF will be used in precision MLS/RNAV approaches. It is defined as that fix along the lateral path where the published barometric altitude intercepts the glide slope. Prior to the PFAF, the aircraft is expected to fly barometric altitude to intercept the glide path. All waypoints up to the PFAF should be coded using the published barometric crossing altitude. The PFAF and all waypoints after it should be coded using the true altitude of the glide path at those points.

  6.5 MLS进近程序编码
  使用原始方位角和仰角数据的MLS进近程序编码仅适用于设计为航向台等效的程序。如果编码此类程序，则“最后进近航段”的规则与上述第6.4节中的规则相同。该类进近的航线类型将在主进近记录的第20列编码为“M”。以MLS区域导航（MLS/RNAV）为基础的进近程序将在主进近记录的第20列编码为“W”或“Y”。MLC/RNAV进近程序的编码如下所述。
  有三种类型的MLS/RNAV进近程序，按照复杂性递增，分别为计算横向/原始垂直引导、计算横向和垂直引导以及曲线路径。
   6.5.1 使用计算横向航迹和原始垂直航迹引导的进近，也称为“A型”，主要用于MLS方位发射机无法位于延长的跑道中心线上，但高度发射机通常位于离着陆点的位置。所有航段将是直线，并与入航航线对齐。在主进近记录的第20列编码为“W”，路径定义将相等于完整的ILS进近（规则6.4.2），除了PFAF入航的航段将是一个“TF”航段，终止于跑道航路点，外行磁向字段中填写了出发磁向航迹。
   6.5.2 使用计算横向航迹和垂直航迹引导的进近，也称为“B型”，不包含曲线航段，将在主进近记录的第20列编码为“Y”。所有航段将是直线，并与入航航线对齐。路径定义将相等于完整的ILS进近（规则6.4.2），除了PFAF入航的航段将是一个“TF”航段，外行磁向字段中填写了出发磁向航迹。
   6.5.3 使用曲线航段的MLS/RNAV进近，也称为“C型”，将用于各种原因，包括平行并线的盘旋着陆、不同类别飞机的分隔、降噪等。这些将始终是精密进近。在主进近记录的第20列编码为“Y”。以下规则适用：
    6.5.3.1 带有曲线航段的MLS/RNAV进近的第一段将是“IF/TF”航段组合。所有其他直线航段将被编码为“TF”航段。在MLS/RNAV曲线进近程序中的所有“TF”航段中，外行磁向字段中将包括发布的航向。
    6.5.3.2 所有曲线航段将被编码为“RF”航段。每个“RF”航段前后的所有航段将在该点切线。
    6.5.3.3 MLS/RNAV曲线进近的初始部分可以是“IF/RF”组合，只要将直线航段过渡编码到“IF”点，并遵守第6.5.2节的规则。
    6.5.3.4 PFAF将在航路点描述字段中被编码为最后进近修正点，而在PFAF之前的第一个修正点将被编码为最后进近航路修正点。
    6.5.3.5 在每个带有曲线航段的MLS/RNAV进近程序中，必须有一个且仅有一个PFAF。
    6.5.3.6 使用精密MLS/RNAV进近中的PFAF。它被定义为横向航迹上的一个航路点，发布的气压高度与下滑坡交叉。在到达PFAF之前，预计飞机将按照气压高度飞行以拦截下滑坡。所有PFAF之前的航路点应使用发布的气压穿越高度进行编码。 PFAF和其后的所有航路点应使用这些点的实际高度进行编码。
   6.5.4 PFAF将在精密MLS/RNAV进近中使用。它被定义为横向航迹上的一个修正点，在该点，发布的气压高度与下滑坡相交。在PFAF之前，飞机预计将按照气压高度飞行以拦截下滑坡。所有PFAF之前的航路点都应使用这些点的真实高度进行编码。

VOR、VORDME、VORTAC和RNAV进近程序编码

  6.6 VOR, VORDME, VORTAC and RNAV Approach Procedure Coding
  The following rules apply to the coding of the “final approach segment” of all VOR based approach procedures, regardless of the reference facility type, and to RNAV Procedures.
   6.6.1 Reference Facility Specific Rules
  The following rules apply to the coding of the “final approach segment” of specific reference facility VOR based approach procedures.
    6.6.1.1 When the reference facility is VOR only or there is no DME collocated with VOR (see VOR coding examples 1, 3 and 8), the following applies:
    6.6.1.1.a Final approach segments will be coded using IF and CF or TF legs only.
    6.6.1.1.b Final approach must include either a FAF and a runway fix or FAF and missed approach point fix.
    6.6.1.1.c The recommended navaid will be the procedure reference VOR. Theta values will be provided from that facility in all final approach sequences.
    6.6.1.2 When the reference facility is VORDME or VORTAC (see VOR coding examples 2 and 6), the following applies:
    6.6.1.2.a Final approach segments will be coded using IF and CF or TF legs only.
    6.6.1.2.b Final approach must include FACF, FAF and either a runway fix or missed approach point fix. The final approach will include a FACF when one is required by Rule 6.2.5.
    6.6.1.2.c The recommended navaid will be the procedure reference VORDME or VORTAC. Theta and Rho values will be provided from that facility in all final approach sequences.
   6.6.2 Examples of VOR Coding
    6.6.2.1 Example of missed approach point before the runway threshold, refer to VOR coding examples 7 and 8.
    6.6.2.2 Example of missed approach point at the runway threshold, refer to VOR coding example 1 and 2.
    6.6.2.3 Example of missed approach point beyond the runway threshold and the final course passes over the runway threshold, refer to VOR coding examples 3 and 4.
    6.6.2.4 Example of missed approach point beyond the runway threshold and the final approach course does not cross runway threshold, refer to VOR coding examples 5 and 6.
   6.6.3 RNAV Procedures
    6.6.3.1 All RNAV approach procedures will be coded to a runway threshold or missed approach point as the last leg in the final approach.
    6.6.3.2 The recommended navaid for VORDME RNAV approaches will be the procedure VORDME or VORTAC. Theta and Rho values will be provided from that facility in all final approach sequences.
    6.6.3.3 Final approach segments will be coded using IF and CF or TF legs only. RF legs may be used in the final approach segment of RNAV approaches.
    6.6.3.4 Final approach must include either a FAF and a runway fix or FAF and missed approach point fix.

  6.6 VOR、VORDME、VORTAC和RNAV进近程序编码
  以下规则适用于所有基于VOR的进近程序的“最终进近段”编码，无论参考设施类型如何，以及适用于RNAV程序。
   6.6.1 参考设施特定规则
  以下规则适用于特定参考设施的基于VOR的进近程序的“最终进近段”编码。
    6.6.1.1 当参考设施仅为VOR或VOR附近没有DME（参见VOR编码示例1、3和8）时，适用以下规则：
    6.6.1.1.a 最终进近段将仅使用IF和CF或TF航段编码。
    6.6.1.1.b 最终进近必须包括一个FAF和一个跑道修正点或FAF和复飞点修正点。
    6.6.1.1.c 推荐导航设施将是该程序参考的VOR。在所有最终进近序列中，将提供来自该设施的Theta值。
    6.6.1.2 当参考设施为VORDME或VORTAC（参见VOR编码示例2和6）时，适用以下规则：
    6.6.1.2.a 最终进近段将仅使用IF和CF或TF航段编码。
    6.6.1.2.b 最终进近必须包括FACF、FAF和一个跑道修正点或复飞点修正点。当规则6.2.5要求时，最终进近将包括一个FACF。
    6.6.1.2.c 推荐导航设施将是该程序参考的VORDME或VORTAC。在所有最终进近序列中，将提供来自该设施的Theta和Rho值。
   6.6.2 VOR编码示例
    6.6.2.1 在跑道阈值之前的复飞点示例，请参考VOR编码示例7和8。
    6.6.2.2 在跑道阈值处的复飞点示例，请参考VOR编码示例1和2。
    6.6.2.3 超过跑道阈值的复飞点示例，且最终航向经过跑道阈值，请参考VOR编码示例3和4。
    6.6.2.4 超过跑道阈值的复飞点示例，且最终进近航向不穿越跑道阈值，请参考VOR编码示例5和6。
   6.6.3 RNAV程序
    6.6.3.1 所有RNAV进近程序都将以跑道阈值或复飞点作为最终进近的最后一段航路进行编码。
    6.6.3.2 对于VORDME RNAV进近，推荐导航设施将是程序VORDME或VORTAC。在所有最终进近序列中，将提供来自该设施的Theta和Rho值。
    6.6.3.3 最终进近段将仅使用IF和CF或TF航段进行编码。RF航段可以在RNAV进近的最终进近段中使用。
    6.6.3.4 最终进近必须包括一个FAF和一个跑道修正点或FAF和复飞点修正点。

TACAN进近程序编码

  6.7 TACAN Approach Procedure Coding
  When the reference facility is TACAN (see VOR coding example 9), the following applies.
   6.7.1 Final approach segments will be coded using IF and CF or TF legs only.
   6.7.2 Final approach must include FACF, FAF and either a Runway Fix or Missed Approach Point Fix.
    6.7.2.1 Final approach segments will be coded using IF and CF or TF legs only.
    6.7.2.2 Final approach must include FAF and either a Runway Fix or Missed Approach Point Fix. The final approach will include a FACF when one is required by Rule 6.2.5.
   6.7.3 The Recommended Navaid will be the procedure reference TACAN. Theta and Rho values will be provided from that facility in all final approach sequences.
   6.7.4 Vertical Angle Rules
  Vertical angle will be coded per the rules in Section 6.2.11.

  6.7 TACAN进近程序编码
  当参考设施为TACAN（参见VOR编码示例9）时，适用以下规定。
   6.7.1 最终进近段将仅使用IF和CF或TF航段进行编码。
   6.7.2 最终进近必须包括FACF、FAF和一个跑道修正点或复飞点修正点。
    6.7.2.1 最终进近段将仅使用IF和CF或TF航段进行编码。
    6.7.2.2 最终进近必须包括FAF和一个跑道修正点或复飞点修正点。当规则6.2.5要求时，最终进近将包括一个FACF。
   6.7.3 推荐导航设施将是程序参考的TACAN。在所有最终进近序列中，将提供来自该设施的Theta和Rho值。
   6.7.4 垂直角规则
  垂直角度将按照第6.2.11节的规则进行编码。

NDB进近程序编码

  6.8 NDB Approach Procedure Coding
  The following rules apply to the coding of the “final approach segment” of all NDB based approach procedures. NDB based approach procedures include procedures using a NDB or Locator as the reference facility and procedures using a NDB or Locator and a DME (NDB + DME) as reference facilities. NDB approach procedures not requiring DME but using the DME for reduced minimums will be coded as NDB + DME procedures.
   6.8.1 Specific Reference Facility Rules
  The following rules apply to the coding of the “final approach segment” of specific reference facility NDB based approach procedures.
    6.8.1.1 NDB approach procedures must include at least FAF and a runway fix or missed approach point fix.
    6.8.1.1.a Rule deleted by Supplement 17.
    6.8.1.2 NDB + DME approach procedures must include a FAF and runway fix or missed approach point fix. The final approach will include a FACF when one is required by Rule 6.2.5.
    6.8.1.3 Coding will use IF and CF or TF legs only through to the runway fix or missed approach point fix. The IF leg will be at the FAF or FACF when coded.
    6.8.1.4 Recommended Navaid Requirements
    6.8.1.4.a On NDB procedures, the recommended navaid information will be provided on the FACF (where coded), the FAF and the Missed Approach Fix record. It will be the procedure reference NDB or Locator. Theta and Rho information will not be provided on any sequence.
    6.8.1.4.b On NDB + DME procedures, the recommended navaid information will be provided on all sequences. On the FACF (when coded) and FAF, this navaid will be the procedure reference NDB or Locator. On the runway fix or missed approach point fix, the recommended navaid will be the procedure reference DME. A procedure reference DME may be any navaid with DME, including ILSDMEs. The Theta and Rho information will not be provided in any sequence of the NDB + DME final approach except in the runway fix or missed approach point fix sequence. That sequence will include Rho information from the procedure reference DME Navaid.
   6.8.2 Examples of NDB Coding
    6.8.2.1 Example of missed approach point before the runway threshold, refer to NDB coding example 4.
    6.8.2.2 Example of missed approach point at the runway threshold, refer to NDB coding example 1.
    6.8.2.3 Example of missed approach point beyond the runway threshold and the final course passes over the runway threshold, refer to NDB coding example 2.
    6.8.2.4 Example of missed approach point beyond the runway threshold and the final approach course does not cross runway threshold, refer to NDB coding example 3.

  6.8 NDB进近程序编码
  以下规则适用于所有基于NDB的进近程序的“最终进近段”的编码。基于NDB的进近程序包括使用NDB或定向无线电信标作为参考设施的程序，以及使用NDB或定位无线电信标和DME（NDB + DME）作为参考设施的程序。不需要DME但使用DME降低最低高度的NDB进近程序将被编码为NDB + DME程序。
   6.8.1 特定参考设施规则
  以下规则适用于特定参考设施的基于NDB的进近程序的“最终进近段”的编码。
    6.8.1.1 NDB进近程序必须包括至少一个FAF和一个跑道修正点或复飞点修正点。
    6.8.1.1.a 规则已被第17号补充取消。
    6.8.1.2 NDB + DME进近程序必须包括一个FAF和一个跑道修正点或复飞点修正点。当规则6.2.5要求时，最终进近将包括一个FACF。
    6.8.1.3 编码将仅使用IF和CF或TF航段直至跑道修正点或复飞点修正。当编码时，IF航段将位于FAF或FACF。
    6.8.1.4 推荐导航设施要求
    6.8.1.4.a 在NDB程序中，建议的导航设施信息将提供在FACF（如果有编码）、FAF和复飞修正点记录上。它将是程序参考的NDB或定位无线电信标。在任何序列中，不会提供Theta和Rho信息。
    6.8.1.4.b 在NDB + DME程序中，将在所有序列中提供推荐的导航设施信息。在FACF（如果有编码）和FAF上，该设施将是程序参考的NDB或定位无线电信标。在跑道修正点或复飞点修正上，推荐的导航设施将是程序参考的DME。程序参考的DME可以是任何带有DME的导航设施，包括ILSDME。在NDB + DME最终进近的任何序列中，除了跑道修正点或复飞点修正序列外，不会提供Theta和Rho信息。该序列将包括来自程序参考DME导航设施的Rho信息。
   6.8.2 NDB编码示例
    6.8.2.1 跑道阈值之前的复飞点示例，请参考NDB编码示例4。
    6.8.2.2 跑道阈值处的复飞点示例，请参考NDB编码示例1。
    6.8.2.3 超过跑道阈值的复飞点示例，且最终航线经过跑道阈值，请参考NDB编码示例2。
    6.8.2.4 超过跑道阈值的复飞点示例，且最终进近航线不穿越跑道阈值，请参考NDB编码示例3。

Loran罗兰编码规则

  6.9 Loran Coding rules Deleted by Supplement 14
  6.9 Loran编码规则,已在第14号补充中删除

盘旋进近着陆编码规则

  6.10 Circle-To-Land Approach Procedure Coding
   6.10.1 Circle-To-Land approach procedures may be coded for the following types of specific reference facilities:
    a. Localizer Only
    b. Localizer Backcourse
    c. IGS Procedure
    d. LDA Procedure
    e. SDF Procedure
    f. VOR Procedure
    g. NDB Procedure
   6.10.2 Circle-To-Land approach procedures may be coded referencing a specific runway or not referencing a specific runway. Coding rules to be followed are:
    6.10.2.1 Use the coding rules for the reference facility type if the circle-to land is runway dependent.
    6.10.2.2 The Circle-To-Land coding rules if the circle-to-land is not runway dependent.
   6.10.3 The following are the Circle-To-Land coding rules for all types of valid reference facilities:
    6.10.3.1 The last segment in the final approach sequence will be the missed approach point fix.
    6.10.3.2 The Altitude 1 value in the missed approach point fix segment will be the highest published OCH(A) or MDA for the procedure.
    6.10.3.3 The vertical angle information will be in the missed approach point fix segment and will be coded as “0.00.”

  6.10 环绕着降落的进近程序编码
   6.10.1 环绕着降落进近程序可以根据以下特定参考设施进行编码：
    a. 仅航向台
    b. 反向航向台
    c. IGS程序
    d. LDA程序
    e. SDF程序
    f. VOR程序
    g. NDB程序
   6.10.2 如果环绕着降落依赖于特定跑道，则应使用参考设施类型的编码规则。
    6.10.2.1 如果着陆圈取决于跑道，请使用参考设施类型的编码规则。
    6.10.2.2 如果环绕着降落不依赖于特定跑道，则应遵循环绕着降落的编码规则。
   6.10.3 对于所有类型的有效参考设施，以下是环绕着降落的编码规则：
    6.10.3.1 最终进近序列中的最后一段航线将是复飞点修正段。
    6.10.3.2 复飞点修正段中的Altitude 1值将是该程序的最高发布OCH（A）或MDA。
    6.10.3.3 垂直角信息将在复飞点修正段中，并以“0.00”编码。

FMS和GPS程序编码

  6.11 FMS and GPS Procedure Coding
  The following rules apply to the coding of the “final approach segments” of all FMS and GPS Approach Procedure Coding.
   6.11.1 Lateral Guidance Rules
  For FMS and GPS procedures, a missed approach point beyond the runway is not allowed, therefore Rules 6.2.9.3, 6.2.9.4, 6.2.9.5, 6.2.10.2.c, 6.2.10.2.d, and 6.2.10.2.e do not apply.
   6.11.2 The track from the FACF to the FAF, where an FACF exists, is coded with TF or RF legs. The RF leg is not allowed as the first leg of the approach coding according to the Beginning/Ending Leg Table. The preferred coding when an approach starts with a precision arc is “IF” at the FACF, followed by “RF” to the FAF. According to the rules on “RF” legs, this will require that a straight line, fix terminated approach transition to the FACF has been included. The track in the transition must be tangent to the arc and the fix at the end of the transition must be overflown. The rule also does not exclude the use of an RF leg in between FAF and the final TF leg of the approach. Such RF legs will be coded with the 4th character of the Waypoint Description field blank.

  6.11 FMS和GPS程序编码
  以下规则适用于所有FMS和GPS进近程序的“最终进近段”的编码。
   6.11.1 横向引导规则
  对于FMS和GPS程序，不允许将复飞点设在跑道之外，因此规则6.2.9.3、6.2.9.4、6.2.9.5、6.2.10.2.c、6.2.10.2.d和6.2.10.2.e不适用。
   6.11.2 从FACF到FAF的航向，如果存在FACF，则使用TF或RF航段进行编码。根据“起始/结束航段表”，RF航段不允许作为进近编码的第一航段。当进近以精密弧形开始时，首选的编码为FACF处的“IF”，然后是到FAF的“RF”。根据“RF”航段的规则，这将要求进近的起始航段为直线航段，并以FACF终止。过渡航段的航迹必须与弧线相切，并且过渡结束点的修正点必须在上方。该规则也不排除在FAF和进近的最后一个TF航段之间使用RF航段。此类RF航段将使用航路点描述字段的第四个字符为空白进行编码。

直升机进近程序编码

  6.12 Helicopter Procedure Coding
  The following rules apply to the coding of the “final approach segment” of all Helicopter Approach Procedure Coding. These rules cover Helicopter Approach Procedures which may be coded to Airports and Runways included in Sub-sections PA and PG only.
   6.12.1 Helicopter Approach Procedures will be coding using the rules in Section 6 of this Attachment, appropriate to the type of sensor required for the procedure, such as VORDME or ILS or RNAV. This includes rules for Recommended Navaid, FACF requirements and leg types.
   6.12.2 The Lateral Path Rules for the sensor related procedure coding reference a “runway fix” as a missed approach point or a missed approach point. Those same rules apply to helicopter procedures. For procedures designed with a dedicated helipad as the missed approach point, a Terminal Waypoint will be established and used as the missed approach point fix.
   6.12.3 The Vertical Path Rules in Section 6 apply without exception, using the rules appropriate for the sensor type.
   6.12.4 Missed Approach code will be accomplished according to the rule in Section 7 of this Attachment, appropriate for the sensor type.

  6.12 直升机进近程序编码
  以下规则适用于所有直升机进近程序的“最终进近段”的编码。这些规则适用于编码到仅包括在PA和PG小节中的机场和跑道的直升机进近程序。
   6.12.1 直升机进近程序将使用本附件第6节中的规则进行编码，具体取决于所需传感器类型，如VORDME、ILS或RNAV等。这包括推荐导航设施、FACF要求和航段类型的规则。
   6.12.2 与传感器相关的程序编码的横向路径规则引用“跑道修正点”作为复飞点或复飞点。同样的规则适用于直升机程序。对于设计有专用直升机停机坪作为复飞点的程序，将建立一个终端航路点，并将其用作复飞点修正点。
   6.12.3 第6节的垂直路径规则适用于所有情况，根据传感器类型选择相应的规则。
   6.12.4 根据本附件第7节关于传感器类型的规则，完成复飞程序的编码。

精密进近程序编码规则

精密进近程序编码通则

  7.0 Precision Approach Procedure Coding
  7.1 Final Approach Segment
  The following rules apply to the coding of “final approach segments” of full ILS Localizer based approach procedures. These procedures may include full ILS (localizer and GS), converging ILS, and those IGS (Instrument Guidance System) that are full ILS equivalent. These rules also apply to all type of MLS Approach Procedures and to GLS Approach Procedures.
   7.1.1 All such approach procedures must begin at the FACF. They must consist of a FACF, FAF and missed approach point fix and all step-down fixes published in the vertical path.
   7.1.2 For localizer based procedures, the FACF is defined as a fix located on the localizer beam center, 8NM or less from the FAF or within the reception range of the Localizer. This may be a source document provided fix or a fix created using these positioning rules.
   7.1.3 The FACF is coded as an IF leg. An altitude will not be assigned to the FACF unless specified in government source documents.
   7.1.4 The track from the FACF to the FAF is coded as a CF or TF leg with altitude constraints as indicated for the specific procedure types below.
   7.1.5 The recommended navaid must be the procedure reference localizer. Theta and Rho must be provided from that navaid for each sequence of the final approach, including any step-down fixes, the runway or helipad fix and/or missed approach point.
   7.1.6 The “Outbound Magnetic Course” field in all sequences must be equal to the localizer magnetic bearing or MLS course, derived from official government source.
   7.1.7 For approach procedures with an electronic glide slope, the vertical angle must be coded in both the Final Approach Fix and the fix, which carries the missed approach point coding. The FAF record carries the Final Approach Fix waypoint description code of “F” in position four of that field. The missed approach point fix carries the waypoint description code of “M” in this position four. The vertical angle will be the published glide slope angle for the installation or procedure. If the altitude 1 and 2 constraints for the FAF are “at” (G) and equal to the FACF altitude with an altitude description of “I,” the vertical angle is omitted from the FAF record.
   7.1.8 The Coding of FAF and FACF Altitude description fields are as follows:

  7.0 精密进近程序编码
  7.1 最终进近段
  以下规则适用于完整的ILS航向台进近程序的“最终进近段”的编码。这些程序可能包括完整的ILS（航向台和下滑道）程序、收敛ILS程序，以及与完整ILS等效的IGS（仪表引导系统）程序。这些规则还适用于MLS进近程序和GLS进近程序的所有类型。
   7.1.1 所有这些进近程序必须从FACF开始。它们必须包括FACF、FAF、复飞点修正点和垂直路径上公布的所有下降修正点。
   7.1.2 对于基于航向台的程序，FACF被定义为位于局放信标中心、距离FAF 8NM或更近，或者在局放接收范围内的修正点。这可以是提供的源文件修正点，也可以是使用这些定位规则创建的修正点。
   7.1.3 FACF编码为IF航段。除非在政府源文件中明确说明，否则不会为FACF分配高度。
   7.1.4 从FACF到FAF的航向将编码为CF或TF航段，并按照下面特定程序类型的要求设置高度约束条件。
   7.1.5 推荐的导航设施必须是程序参考的航向台。每个最终进近序列中，包括任何下降修正点、跑道或直升机停机坪修正点以及复飞点，都必须提供来自该导航设施的Theta和Rho值。
   7.1.6 所有序列中的“出站磁航向”字段必须等于局放磁方位或从正式政府来源中获取的MLS航向。
   7.1.7 对于带有电子下滑道的进近程序，必须在最终进近修正点和携带复飞点编码的修正点中编码垂直角度。FAF记录中在航路点描述字段的位置四上携带最终进近修正点航路点描述代码“F”。携带复飞点编码的修正点在此位置四上携带航路点描述代码“M”。垂直角度将是安装或程序的已发布下滑道角度。如果FAF的高度“约束1”和“约束2”为“at”（G）且与FACF高度相等，并且具有“I”的高度描述，FAF记录中将省略垂直角度。
   7.1.8 FAF and FACF高度描述字段的编码如下：

GLS精密进近程序编码

  7.3 GLS Precision Approach Procedure Coding
   7.3.1 The rules for coding GLS Approach Procedures are understood to be identical to those of Localizer coding as found in Section 7.1 of this Attachment.
  7.3 GLS精密进近程序编码
   7.3.1 GLS进近程序的编码规则与本附件第7.1节中的航向台编码规则完全相同。

MLS进近程序编码

  7.4 MLS Approach Procedure Coding
  MLS Approach Procedure Code utilizing raw azimuth and elevation data is limited to those procedures that are designed as a localizer equivalent. If such a procedures is coded, the rules for the “final approach segments” are to be identical with those stated in Rule 7.1 above. The Route Type of such approaches must be coded as “M” in column 20 of the primary approach record. Approach procedures predicated on the use of MLS Area Navigation (MLS/RNAV) must be coded with a “W” or “Y” in column 20 of the primary approach record. MLS/RNAV approaches are coded as described below. There are three types of MLS/RNAV approach, listed in increasing levels of complexity, computed lateral/raw vertical guidance, computed lateral and vertical guidance and curved path.
   7.4.1 Approaches using computed lateral path and raw vertical path guidance, also referred to as Type “A,” will be used primarily where the MLS azimuth transmitter cannot be located on the extended runway centerline, but the elevation transmitter is sited normally abeam the touchdown point. All legs will be straight and aligned with the inbound course. They must be codes with Route Type “W” in column 20 of the primary approach record. Path definition will be the equivalent of a full ILS approach (Rule 6.4.2) with the exception that the leg from the PFAF inbound will be a “TF” leg, terminating at the runway or helipad waypoint, with the published final approach source in the Outbound Magnetic Course field. The PFAF will be coded as the Final Approach Fix in the Waypoint Description field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix.
   7.4.2 Approach using computed lateral and vertical guidance but no curved legs, also referred to as Type “B,” must be coded as Route Type “Y” in column 20 of the primary approach record. All legs will be straight and aligned with the inbound course. Path definition will be the equivalent of the full ILS approach (Rule 6.4.2) with the exception that the leg from the PFAF inbound will be a “TF” leg, with the published final approach course in the Outbound Magnetic Course field. The altitude of the PFAF and all waypoints inbound from it must be the glide path altitude at that point. The PFAF will be coded as the Final Approach Fix in Waypoint Description field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix.
   7.4.3 MLS/RNAV approaches using curved legs, also referred to as Type “C,” will be used for a variety of reasons, including parallel sidestep approaches, separation of different categories of aircraft, noise abatement, etc. These must always be precision approaches. They must be coded a with a Route type of “Y” in column 20 of the primary approach record. The following rules apply:
    7.4.3.1 The first leg of an MLS/RNAV approach with curved legs must be an “IF/TF” leg combination. All other straight legs must be coded as “TF” legs. All “TF” legs in an MLS/RNAV with curved legs procedure must have the published course included in the Outbound Magnetic Course field.
    7.4.3.2 All curved legs will be code as “RF” legs. Every leg preceding or following the “RF” leg will be tangent to the “RF” leg at that point.
    7.4.3.3 The initial portion of a MLS/RNAV approach with curved legs may be an “IF/RF” combination, provided a straight leg approach transition is coded to the point in the “IF” and Rule 7.4.2 are complied with.
    7.4.3.4 The PFAF will be coded as the Final Approach Fix in the Waypoint Description field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix. If there is not a fix at the glide path intercept, then the first fix after the intercept will be the PFAF. There must be one and only one PFAF for each MLS/RNAV approach with curved legs.
    7.4.3.5 The last leg of an approach transition prior to an MLS/RNAV approach must be one of the following types CF, CI, HF, PI, RF or TF, except as indicated in Rule 6.5.3.3. If the leg type is CF, CI, RF or TF, then the Recommended Navaid must contain the identifier of the MLS used for the approach. If the leg type is PI or HF, then the Recommended Navaid must contain the VHF Navaid that defines the PI or HF leg.
    7.4.3.6 If the last leg prior to the approach is a “CI” leg, the intercept angle will be 30° or less, and the intercept point must be between the first and second terminator fixes in the approach, but no closer that 2NM to the second fix.
    7.4.3.7 The PFAF and the FACF altitudes must be coded according to Precision Approach Procedures Rule 6.4.2.
    7.4.4 The PFAF will be used in precision MLS/RNAV approaches. It is defined as that fix along the lateral path where the published barometric altitude intercepts the glide slope. Prior to the PFAF, the aircraft is expected to fly barometric altitude to intercept the glide path. All waypoints up to the PFAF should be coded using the published barometric crossing altitude. The PFAF and all waypoints after it should be coded using the true altitude of the glide path at those points.

  7.4 MLS进近程序编码
  使用原始方位角和俯仰角数据的MLS进近程序仅限于设计为航向台等效的程序。如果编码了此类程序，则其“最终进近段”的规则与上述第7.1条规定的规则完全相同。这些方法的航线类型必须在主要进近记录的第20列中编码为“M”。基于MLS区域导航（MLS/RNAV）的进近程序必须在主要进近记录的第20列中编码为“W”或“Y”。下面描述了MLS/RNAV进近的三种类型，根据复杂程度的增加分为计算横向/原始垂向引导、计算横向和垂向引导以及曲线路径。
   7.4.1 使用计算的横向路径和原始垂向路径引导的进近，也称为类型“A”，主要用于无法将MLS方位角发射机放置在延长的跑道中心线上，但俯仰角发射机按常规方式位于触地点旁边。所有航段都必须是直线，并与进近航向对齐。它们必须在主要进近记录的第20列中以航线类型“W”编码。路径定义相当于完整的ILS进近（规则6.4.2），但除了PFAF内部通道以外的航段将是一个“TF”航段，终止于跑道或直升机停机坪航路点，并在“出站磁航向”字段中携带已发布的最终进近源。 PFAF将在航路点描述字段中编码为最终进近修正点，而PFAF之前的第一个航路点将被编码为最终进近航路修正点。
   7.4.2 使用计算的横向和垂向引导但无曲线航段的进近，也称为类型“B”，必须在主要进近记录的第20列中编码为航线类型“Y”。所有航段都必须是直线，并与进近航向对齐。路径定义相当于完整的ILS进近（规则6.4.2），但除了PFAF内部通道以外的航段将是一个“TF”航段，终止于跑道或直升机停机坪航路点，并在“出站磁航向”字段中携带已发布的最终进近航迹。 PFAF的高度以及从PFAF开始的所有航路点的高度必须是该点的下滑道高度。PFAF将在航路点描述字段中编码为最终进近修正点，而PFAF之前的第一个航路点将被编码为最终进近航路修正点。
   7.4.3 使用曲线航段的MLS/RNAV进近，也称为类型“C”，可用于多种原因，包括并行侧步进近、不同类别飞机的分开、降噪等。这些进近必须始终是精密进近。它们必须在主要进近记录的第20列中以航线类型“Y”编码。以下规则适用：
    7.4.3.1 具有曲线航段的MLS/RNAV进近的第一航段必须是“IF/TF”航段组合。所有其他直线航段必须编码为“TF”航段。在具有曲线航段的MLS/RNAV程序中，“TF”航段必须在“出站磁航向”字段中包含已发布的航迹。
    7.4.3.2 所有曲线航段均被编码为“RF”航段。与“RF”航段在同一点处的每个航段必须与“RF”航段相切。
    7.4.3.3 MLS/RNAV进近的初始部分可以是“IF/RF”组合，前提是编码了直线航段进近过渡，并符合第7.4.2条的规定。
    7.4.3.4 PFAF将在航路点描述字段中被编码为最终进近修正点，而PFAF之前的第一个航路点将被编码为最终进近航路修正点。如果在下滑道拦截点之前没有修正点，则在拦截点之后的第一个修正点将成为PFAF。每个具有曲线航段的MLS/RNAV进近必须有一个且仅有一个PFAF。
    7.4.3.5 MLS/RNAV进近之前的最后一个航段必须是以下类型之一：CF、CI、HF、PI、RF或TF，除非在规则6.5.3.3中另有说明。如果航段类型为CF、CI、RF或TF，则推荐导航设施必须包含用于该进近的MLS的标识符。如果航段类型为PI或HF，则推荐导航设施必须包含定义PI或HF航段的VHF导航设施。
    7.4.3.6 如果进近之前的最后一个航段为“CI”航段，则拦截角度应小于等于30°，并且拦截点必须位于进近中的第一和第二终止修正点之间，但距离第二个修正点不得小于2NM。
    7.4.3.7 PFAF和FACF的高度必须根据精密进近程序规则6.4.2进行编码。
   7.4.4 PFAF将用于精密MLS/RNAV进近。它被定义为沿着横向路径，在该点上，已发布的气压高度与下滑道相交。在到达PFAF之前，飞机预计以气压高度飞行以拦截下滑道。所有路径点都应使用已发布的气压越过高度进行编码。在PFAF和其后的所有航路点，必须使用该点处下滑道的真实高度进行编码。

非精密进近程序编码规则

非精密进近程序编码

  8.0 Non-precision Approach Procedure Coding
  8.1 General
   8.1.1 For approach procedures without an electronic glide slope, the Final Approach Fix will be that designated by government source. If no FAF is established in the government source, one will be computed according to Rule 6.2.5.2 of this Attachment. The fix, whether published or established, must carry the Final Approach Fix Waypoint Description code of “F” in position four of that code field. Note that only one record in a coded approach procedure can carry the “F” in position four of the Waypoint Description. Altitudes for this fix are coded in accordance with Rule 6.2.10.1 of this Attachment.
   8.1.2 A Vertical Angle must be coded in the Missed Approach Point, Runway Threshold or the Final End Point, which ever occurs first, for each approach procedure. Vertical Angles must be derived from the official government source or computed. This vertical angle will only be repeated on all step-down fixes after the FAF.
   8.1.3 Missed Approach Point (MAP) Location - The MAP will be the MAP as shown on the non-precision approach procedure by the civil aviation authority. If the intent of the procedure designer is to locate the MAP at the LTP and it is within 0.1 NM radius of the landing threshold point, the MAP will be defined at the LTP.
Note: If the source document states that the MAP and the LTP are not at the same location even if the distance is 0.1 mile or less, the MAP will not be placed at the LTP.

  8.0 非精密进近程序编码
  8.1 概述
   8.1.1 对于没有电子下滑道的进近程序，最终进近修正点将由政府来源指定。如果政府来源中没有设定FAF，则根据本附件第6.2.5.2条的规定进行计算。无论是已发布或设定的修正点，都必须在该代码字段的第四位位置携带最终进近修正点的航路点描述代码“F”。请注意，编码进近程序中只能有一条记录在航路点描述字段的第四位位置携带“F”。该修正点的高度编码要符合本附件第6.2.10.1条的规定。
   8.1.2 必须在每个进近程序的复飞点、跑道阈值或最终终点中编码垂直角度，取决于它们哪个首先出现。垂直角度必须来源于正式的政府来源或进行计算。这个垂直角度仅在FAF之后的所有下降修正点上重复。
   8.1.3 复飞点（MAP）位置 - 复飞点将是民航当局在非精密进近程序中显示的复飞点。如果程序设计者的意图是将复飞点定位在LTP（降落阈值点），并且它与降落阈值点在0.1NM半径范围内，那么复飞点将被定义为LTP。
  注意：如果源文件指定复飞点和LTP不在同一位置（即使距离在0.1英里或更短），则复飞点将不会放置在LTP。

基于航向台的最终进近路径编码

  8.2 Final Approach Path Coding - Localizer-Based Procedures
  The following rules apply to the coding of “final approach segments” of non-precision Localizer-based approach procedures. These procedures may include Localizer Only, IGS (Instrument Guidance System) LDA, Localizer type Directional Aid) and SDF (Simplified Directional Aid) procedures.
   8.2.1 All such approach procedures must begin at the FACF. They must consist of a FACF, FAF and missed approach point fix and all step-down fixes published in the vertical path.
   8.2.2 The FACF is defined as a fix located on the localizer beam center, 8NM or less from the FAF or within the reception range of the Localizer. This may be a source document provided fix or a fix created using these positioning rules.
   8.2.3 The FACF is coded as an IF leg with an altitude only when assigned by government source.
   8.2.4 The track from the FACF to the FAF is coded as a CF or TF leg with altitude constraints as indicated for the specific procedure types below.
   8.2.5 The recommended navaid must be the procedure reference localizer. Theta and Rho must be provided from the localizer for each sequence of the final approach, including any step-down fixes, the runway or helipad fix and/or missed approach point.
   8.2.6 The “Outbound Magnetic Course” field in all sequences must be equal to the localizer magnetic bearing, derived from official government source.

  8.2 基于航向台的最终进近路径编码
  以下规则适用于非精密航向台进近程序的“最终进近段”的编码。这些程序可能包括仅航向台、IGS（仪表引导系统）LDA（局放型定位无线电信标）和SDF（简易型定位无线电信标）程序。
   8.2.1 所有这些进近程序必须从FACF开始。它们必须包括FACF、FAF和复飞点修正点，以及垂直路径中公布的所有下降修正点。
   8.2.2 FACF被定义为位于航向台波束中心的修正点，距离FAF不超过8NM，或者在航向台接收范围内。这可能是由源文件提供的修正点，也可能是使用这些定位规则创建的修正点。
   8.2.3 FACF编码为IF航段，仅在由政府来源指定时附带高度。
   8.2.4 从FACF到FAF的航向将编码为CF或TF1航段，并根据下面特定程序类型的要求设置高度约束条件。
   8.2.5 推荐导航设施必须是程序参考的航向台。必须从该航向台获取每个最终进近序列（包括任何下降修正点、跑道或直升机停机坪修正点以及复飞点）的Theta和Rho值。
   8.2.6 所有序列中的“出站磁航向”字段必须与航向台的磁方位角相等，由正式的政府来源获取。

基于VOR的最终进近路径编码

  8.3 Final Approach Path Coding - VOR-Based Procedures
  The following rules apply to the coding of the “final approach segments” of non-precision VOR-based approach procedures. These procedures may include VOR, VORDME, VORTAC, RNAV and TACAN procedures.
   8.3.1 Final approach segments must be coded using IF and CF or TF1 legs only.
   8.3.2 Final approach must include both a FAF and missed approach fix. The missed approach fix may be a runway or helipad fix or a designated missed approach point. Coding of a FACF is defined in Rule 6.2.5.
   8.3.3 The recommended navaid must be the procedure reference VOR or TACAN. Theta values must be provided from that facility in all final approach sequences, including any step-down fixes that are included.
   8.3.4 When the reference facility is VORDME or VORTAC or TACAN, the following applies:
    8.3.4.1 Final approach segments must be coded using IF and CF or TF1legs only.
    8.3.4.2 Final approach must include FACF, FAF and a missed approach point which may be a missed approach point fix, a runway fix or a helipad fix, and all step-down fixes published in the vertical path. The final approach will include an FACF when one is required by Rule 6.2.5.
    8.3.4.3 The recommended navaid must be the procedure reference VORDME or VORTAC or TACAN. Theta and Rho values must be provided from that facility in all final approach sequences, including any step-down fixes that are included.
   8.3.5 When the procedure reference is RNAV, the following applies:
    8.3.5.1 Final approach segments must be coded using IF and CF or TF1legs only.
    8.3.5.2 All RNAV approach procedure missed approach points must be at or prior to a runway threshold or helipad alighting point. These points may be a source defined named waypoint.
    8.3.5.3 The recommended navaid is not required unless specified by the state, or if required by leg type. The recommended navaid must be procedure reference VORDME or VORTAC. Theta and Rho values must be provided from that facility in all final approach sequences, including any step-down fixes that are included.
   8.3.6 Rule deleted by Supplement 17.
    8.3.6.1 Rule deleted by Supplement 17.
    8.3.6.2 Rule deleted by Supplement 17.
    8.3.6.3 Rule deleted by Supplement 17.

  8.3 基于VOR的最终进近路径编码
  以下规则适用于非精密基于VOR的进近程序的“最终进近段”的编码。这些程序可能包括VOR、VORDME、VORTAC、RNAV和TACAN程序。
   8.3.1 最终进近段必须仅使用IF和CF或TF1航段进行编码。
   8.3.2 最终进近必须包括FAF和复飞修正点。复飞修正点可以是复飞点修正点、跑道修正点或直升机停机坪修正点，并且必须包括在垂直路径中公布的所有下降修正点。当根据规则6.2.5要求时，最终进近将包括一个FACF。
   8.3.3 推荐的导航设施必须是程序参考的VOR或TACAN。必须从该设施获取每个最终进近序列（包括任何下降修正点）的Theta和Rho值。
   8.3.4 当参考设施为VORDME、VORTAC或TACAN时，适用以下规定：
   8.3.4.1 最终进近段必须仅使用IF和CF或TF1航段进行编码。
   8.3.4.2 最终进近必须包括FACF、FAF和一个复飞点修正点，该修正点可以是复飞点修正点、跑道修正点或直升机停机坪修正点，并且必须包括在垂直路径中公布的所有下降修正点。当根据规则6.2.5要求时，最终进近将包括一个FACF。
   8.3.4.3 推荐的导航设施必须是程序参考的VORDME、VORTAC或TACAN。必须从该设施获取每个最终进近序列（包括任何下降修正点）的Theta和Rho值。
  8.3.5 当参考设施为RNAV时，适用以下规定：
   8.3.5.1 最终进近段必须仅使用IF和CF或TF1航段进行编码。
   8.3.5.2 所有RNAV进近程序的复飞点必须位于跑道阈值或直升机停机坪着陆点之前。这些点可以是源文件定义的命名航路点。
   8.3.5.3 推荐导航设施不是必须的，除非由国家规定或航段类型要求。推荐导航设施必须为程序参考的VORDME或VORTAC。必须从该设施获取每个最终进近序列（包括任何下降修正点）的Theta和Rho值。
  8.3.6 条款已被第17号补充删除。
   8.3.6.1 条款已被第17号补充删除。
   8.3.6.2 条款已被第17号补充删除。
   8.3.6.3 条款已被第17号补充删除。

基于NDB程序的最后进近程序的编码

  8.4 Final Approach Path Coding - NDB-Based Procedures
  The following rules apply to the coding of the “final approach segment” of all NDB based approach procedures. NDB based approach procedures include procedures using a NDB or Locator as the reference facility and procedures using a NDB or Locator and a DME (NDB + DME) as reference facilities. NDB approach procedures not requiring DME but using the DME for reduced minimums will be coded as NDB + DME procedures.
  8.4.1 NDB approach procedures must include a FAF and a runway or helipad fix or missed approach point fix and all step-down fixes published in the vertical path. They may also include a FACF fix.
   8.4.2 Rule deleted by Supplement 17.
   8.4.3 NDB + DME approach procedures must include a FAF and runway or helipad fix or missed approach point fix and all step-down fixes published in the vertical path. The final approach will include a FACF when one is required by Rule 6.2.5.
   8.4.4 Coding must use IF and CF or TF1 legs only through to the runway or helipad fix or missed approach point fix.
The IF leg must be at the FAF (or at the optional FACF) for NDB procedures or at the FACF for NDB + DME procedures.

  8.4 最终进场路径编码 - 基于NDB的程序
  以下规则适用于所有基于NDB的进场程序的“最终进场段”的编码。基于NDB的进场程序包括使用NDB或定位无线电信标作为参考设施的程序，以及使用NDB或定位无线电信标和DME（NDB + DME）作为参考设施的程序。不需要DME但使用DME降低最低高度的NDB进场程序将被编码为NDB + DME程序。
   8.4.1 NDB进场程序必须包括FAF、跑道或直升机停机坪修正点或复飞点修正点，以及垂直路径中公布的所有下降修正点。它们还可以包括FACF修正点。
   8.4.2 被第17号补充删除。
   8.4.3 NDB + DME进场程序必须包括FAF、跑道或直升机停机坪修正点或复飞点修正点，以及垂直路径中公布的所有下降修正点。当规则6.2.5要求时，最终进场将包括一个FACF。
   8.4.4 编码必须仅使用IF和CF或TF1航段直至跑道或直升机停机坪修正点或复飞点修正点。对于NDB进场程序，IF航段必须位于FAF（或可选的FACF）处，对于NDB + DME进场程序，IF航段必须位于FACF处。

盘旋着陆最后进近方式的编码

  8.6 Final Approach Path Coding - Circle-to-Land Procedures
  Procedures which are Circle-To-Land may be included in the database. When they are included, they are identified with the route type appropriate to the sensor involved and the “Circle-To-Land” Approach Procedure Route Qualifier of “C.” These rules applies to approach routes so identified:
   8.6.1 The last segment in the final approach sequence must be the missed approach point fix.
   8.6.2 For Circle-To-Land Procedures that are to a runway or helipad, all the rules listed above in Sections 6, 7 and 8 apply, as well as the rules for Missed Approach Procedure coding in Section 9.
   8.6.3 For Circle-To-Land Procedures that are not to a runway or helipad, the missed Approach Point will be the center of the airport or heliport.
   8.6.4 The vertical angle information must be in the missed approach point fix segment, or in the Final End Point segment if a Final End Point is designated for the approach. Vertical angle information must be in accordance with the rules in Section 6, 7 and 8 of this Attachment for the type of reference facility on which the procedure is based.

  8.6 最终进场路径编码 - 环绕着降落程序
  环绕着降落程序可以包含在数据库中。当它们包含在内时，它们将使用适用于相关传感器的航线类型进行标识，并使用“C”作为“环绕着降落”进场程序航线限定词。适用以下规则的被标识为环绕着降落的进场航线：
   8.6.1 最终进场序列中的最后一段必须是复飞点修正点。
   8.6.2 对于以跑道或直升机停机坪为目标的环绕着降落程序，适用上述第6、7和8节中列出的所有规则，以及第9节中关于复飞程序的编码规则。
   8.6.3 对于不以跑道或直升机停机坪为目标的环绕着降落程序，复飞点将是机场或直升机停机坪的中心点。
   8.6.4 垂直角度信息必须位于复飞点修正点段中，如果为该进场指定了最终终点，则必须位于最终终点段中。垂直角度信息必须符合本附件第6、第7和第8节关于所基于的参考设施类型的规则。

基于GNSS的最后进近方式的编码

  8.7 Final Approach Path Coding – GNSS-Based Procedure
  The rules for final approach path GNSS-based procedures are currently under development.
   8.7.1 The track from the FACF (when coded) to the FAF is coded with TF or RF legs. The RF leg is not allowed as the first leg of the approach coding according to the Beginning/Ending Leg Table. The preferred coding when an approach starts with a precision arc is the use of an “IF” leg at the FACF or FAF, followed by “RF” to the FAF or MAP. According to the rules on “RF” legs, this must require that a straight line, fix terminated, approach transition to the FACF or FAF has been included. The track in the transition must be tangent to the arc and the fix at the end of the transition must be overflown. The rule also does not exclude the use of an RF leg in between FAF and the final TF leg to the missed approach point. Such RF legs must be coded with the 4th character of the Waypoint Description field blank.

  8.7 GNSS基于最终进场路径编码的程序的编码。
  基于 GNSS 的最终进近路径程序的规则目前正在制定中。
   8.7.1 从FACF（如果编码）到FAF的航迹将使用TF或RF航段进行编码。根据“起始/结束航段表”，RF航段不能作为进场编码的第一航段。当进场以精密弧线开始时，最佳编码是在FACF或FAF处使用“IF”航段，然后使用“RF”航段到FAF或MAP。根据“RF”航段的规则，这要求必须有一个以直线结束的进场过渡航段，过渡航段必须与弧线相切，并且在过渡结束点的航路点修正上飞越。规则还不排除在FAF和最终的TF航段之间使用RF航段。此类RF航段必须在航路点描述字段的第四个字符为空白。

直升机进场程序的最后进近路径的编码

  8.8 Final Approach Path Coding - Helicopter Approach Procedures
  Helicopter Approach Procedures will be coding using the rules in Sections 6, 7 and 8 and 9 of this Attachment, appropriate to the type of sensor required for the procedure, such as VORDME or ILS or RNAV or GNSS. This includes rules for Recommended Navaid, FACF requirements, beginning and ending leg types, etc.
  The Lateral Path Rules for the sensor related procedure coding reference a “missed approach point fix,” a “runway fix” or a “helipad fix” as the missed approach point. Those same rules apply to the coding of helicopter procedure.

  8.8 直升机进场程序的最终进场路径编码规则
  直升机进场程序将使用本附件第6、7、8和9节中的规则进行编码，具体取决于所需的传感器类型，例如VORDME、ILS、RNAV或GNSS等。这包括推荐导航设施、FACF要求、起始和结束航段类型等规则。
  与传感器相关的程序编码的横向路径规则以“复飞点修正点”、”跑道修正点”或”直升机停机坪修正点”作为复飞点的参考。这些规则也适用于直升机程序的编码。

垂直导航路径（VNAV路径）或下降梯度考虑因素

  8.9 Vertical Navigation Path (VNAV Path) or Descent Gradient Considerations
  If the government source provides a vertical angle and/or TCH, it will be used. The only exception is when the source provides more than one angle for the final approach segment. If more than one angle is provided for the final approach segment, the highest angle will be used.
  The following guidelines have been developed for the coding of the vertical angles on the final approach course when the vertical angle is not provided by the government sources.

  8.9 垂直导航路径（VNAV路径）或下降梯度考虑因素
  如果政府来源提供了垂直角度和/或TCH（阈高），则将使用它。唯一的例外是当源文件提供了多个垂直角度用于最终进场段时。如果为最终进场段提供了多个角度，则将使用最高的角度。
  对于当政府来源未提供垂直角度时，我们已制定了以下的垂直角度编码指南。

   8.9.1 The descent angle is to be calculated from published TCH or a point 50 feet above the Landing Threshold Point (LTP) to the altitude at the final approach fix (FAF). The curvature of the earth should not be used in the calculations of the descent angle. Refer to examples 1, 7, and 8. The descent angle will always be rounded up to the nearest one hundredth of a degree.
  Examples of Rounding:
   3.111 = 3.12
   3.346 = 3.35
    8.9.1.1 The published TCH for a procedure used in these calculations is the procedure TCH or 50 feet when no TCH is published. TCH is further defined in Chapter Five, Sections 5.67 and 5.265 of this document.
   8.9.2 If the calculated angle is less than three degrees, it will be raised to a minimum of three degrees.
   8.9.3 If a step-down fix is included in the final approach segment and it is determined that the calculated descent angle will be above the step-down fix altitude, that calculated descent angle will be used. If it is determined that the step-down fix altitude is above the descent path, the descent angle will be calculated from the LTP plus 50 feet to the altitude at the step-down fix. Refer to Examples 3 and 4.
   8.9.4 The descent angle should not be less than the Visual Glide Slope Indicator (VGSI) associated with the landing runway. If the calculated descent angle is less than the VGSI, the descent angle should be raised to match the VGSI or to 3.77 degrees whichever is lower.
   8.9.5 If the final approach course does not pass over the runway threshold, a position abeam the runway threshold on the final approach course will be calculated and coded as a Final End Point. The descent angle will be computed from the abeam position to the altitude at the FAF. The altitude to be used at the Final End Point is the LTP plus 50 feet. Refer to Examples 6, 9, and 10.
   8.9.6 If the missed approach point is prior to the runway threshold, the descent angle will be computed from the LTP plus 50 feet to the altitude at the FAF. An altitude will be specified at the MAP and will be the altitude where the descent angle passes through the MAP. Refer to Examples 7 and 8.
   8.9.7 When circling-to-land minimums are the only landing minimums and the runway is in alignment with the final approach segment, a descent angle will be provided. The descent angle will be calculated from the LTP plus 50 feet to the altitude at the FAF. Refer to Examples 11 and 12.
   8.9.8 When circling-to-land minimums are the only landing minimums and the runway is not in alignment with the final approach segment, a descent angle will be provided. The descent angle will be calculated from a point on the final approach track Abeam the LTP of the nearest landing runway to the altitude at the FAF. The altitude to be used at the abeam position is the airport elevation. Refer to Example 13.
   8.9.9 If step-down fix is published in government source in the initial or intermediate segment, the fix and the appropriate altitude will be coded as part of the procedure. A vertical angle will be coded on the FAF waypoint that will ensure any step-down fix altitude in the intermediate segment FACF to FAF is cleared. Vertical angle information is not provided in the initial segment IAF to FACF. All step-down fixes will be coded with the appropriate altitude.

   8.9.1 下降角应从公布的TCH或着陆点（LTP）上方50英尺的点计算到最终进近点（FAF）的高度。下降角的计算不应使用地球曲率。请参阅示例1、7和8。下降角将始终四舍五入到最接近的百分之一度。
  四舍五入的例子:
   3.111 = 3.12
   3.346 = 3.35
    8.9.1.1 这些计算中使用的程序的已发布TCH是程序TCH或未发布TCH时的50英尺。TCH在本文档的第五章第5.67节和第5.265节中进一步定义。
   8.9.2 如果计算的角度小于三度，它将被提高到最小三度。
   8.9.3 如果最后进场段包括降压固定，并且确定计算的下降角将高于降压固定高度，则将使用该计算的下降角。如果确定降压固定高度高于下降路径，则将从LTP加50英尺到降压固定高度计算下降角。参见示例3和4。
   8.9.4 下降角不应小于与着陆跑道相关的视觉滑翔斜率指示器（VGSI）。如果计算的下降角小于VGSI，下降角应提高到与VGSI匹配或3.77度，以较低者为准。
   8.9.5 如果最终进近航向没有超过跑道阈值，最终进近航向上跑道阈值对开的位置将被计算并编码为最终终点。下降角将从反方向位置计算到FAF的高度。最终终点使用的高度是LTP加50英尺。请参阅示例6、9和10。
   8.9.6 如果错过的进近点在跑道阈值之前，下降角将从LTP加50英尺计算到FAF高度。高度将在地图上指定，并且将是下降角通过地图的高度。参见示例7和8。
   8.9.7 当盘旋至着陆最小值是唯一的着陆最小值，而跑道与最后进近段对齐时，将提供下降角。下降角将从LTP加50英尺到FAF高度计算。参见示例11和12。
   8.9.8 当盘旋至着陆最小值是唯一的着陆最小值，而跑道与最后进场段不对齐时，将提供下降角。下降角将从最后进场跑道上的一点计算到最近着陆跑道的LTP到FAF的高度。在正侧位置使用的高度是机场高程。参见示例13。
   8.9.9 如果降压固定在初始或中间段的政府来源中公布，该固定和适当的高度将作为程序的一部分进行编码。FAF航点上将编码垂直角度，以确保FACF到FAF中间段的任何降压固定高度都被清除。初始段IAF到FACF中不提供垂直角度信息。所有降压固定都将使用适当的高度进行编码。

复飞点在跑道入口后的的VNAV引导的非精密进近程序的编码

  8.10 VNAV Coding of Non-Precision Approach Procedures With Missed Approach Points - Other Than Landing Threshold
  Coding standards for Non-Precision Approach Procedures that have a published missed approach point other than the Landing Threshold Point (LTP) have been developed. Examples of coding three VNAV coding scenarios have been developed. The three examples are:
   8.10.1 Missed Approach Point beyond the landing threshold, more than 0.14NM from the landing threshold and the published Final Approach Course crosses the landing threshold. The ARINC 424 rules for this case call for inserting the Landing Threshold Point as a fix in the procedure coding. See VNAV Coding Example A.
   8.10.2 Missed Approach Point beyond the landing threshold, more than 0.14NM from the landing threshold and the published Final Approach Course does not cross the landing threshold, the Final Approach Course is no closer than 0.14NM to the landing threshold at any given point. ARINC 424 rules for this case call for inserting a Final End Point as a fix in the procedure coding. See Coding Example B.
   8.10.3 Missed Approach Point is a Navaid beyond the landing threshold. The Navaid is within 0.14NM of the landing threshold. According to ARINC 424 rules, this Navaid will be coded as the missed approach point. No fixes will be inserted into the procedure coding. VNAV information will be provided on the Missed Approach Point sequence. See Coding Example C.

  8.10 复飞点在跑道入口后的的VNAV引导的非精密进近程序的编码
  已制定了具有非着陆入口以外的已发布复飞点的非精密进场程序的编码标准。已开发了三个VNAV编码场景的示例。这三个示例分别是：
   8.10.1 跑道入口后的复飞点，距离跑道入口超过0.14NM，并且已发布的最终进场航线穿过跑道入口。此情况下，根据ARINC 424规则，应在程序编码中插入着陆入口作为一个修正点。请参阅VNAV编码示例A。
   8.10.2 跑道入口后的复飞点，距离跑道入口超过0.14NM，并且已发布的最终进场航线不穿过跑道入口，最终进场航线任意一点距离跑道入口不得小于0.14NM。此情况下，根据ARINC 424规则，应在程序编码中插入终点作为一个修正点。请参阅编码示例B。
   8.10.3 复飞点是距离跑道入口较远的导航设施。该导航设施距离跑道入口不超过0.14NM。根据ARINC 424规则，该导航设施将被编码为复飞点。在程序编码中不需要插入修正点。VNAV信息将在复飞点序列上提供。请参阅编码示例C。

例子

所有类型的复飞程序规则

  9.0 Missed Approach Procedure Rules Valid For All Procedure Types
  Missed Approach Procedure coding must be accomplished as an integral part of the Approach Procedure Coding and will be provided for each approach procedure contained in the data base. Specific coding must be incorporated to facilitate identification of where the Missed Approach Coding starts within any given approach procedure. The structure of the procedure records included in this Specification as defined in this Attachment is such that multiple missed approach procedure paths may be coded for a single approach procedure. This will accommodate those procedures with alternative missed approach paths based on aircraft climb performance. Coding for multiple missed approach paths for a single approach procedure must commence at the same missed approach point. Identification of multiple missed approach procedures, when coded, will be accomplished through the coding of a specific Transition Identifier which closely aligns with published information.

  必须作为进场程序编码的一个组成部分来完成复飞程序的编码，并且必须为数据库中包含的每个进场程序提供。具体的编码必须被纳入到方便确定复飞编码在任何给定进场程序中起始位置的标识中。本规范中包含的进场程序记录的结构如本附件所定义，这样可以为单个进场程序编码多个复飞程序路径。这将适应那些基于飞机爬升性能的备用复飞路径的程序。对于单个进场程序的多个复飞路径的编码必须从相同的复飞点开始。编码多个复飞程序时，将通过编码与已发布信息紧密对齐的特定过渡标识符来进行标识。

复飞点

  9.1 Missed Approach Point
   9.1.1 All Approach Procedure coding must have a segment that identifies the Missed Approach Point Fix. Such a fix must be the published Missed Approach Point, either a IFR Landing Threshold or a Helipad Alighting Point or a dedicated Missed Approach Point (MAP Fix).
   9.1.2 Identification of the fix within a sequence of procedure records and the type of fix, must be accomplished through code in the “Waypoint Description” field (see Section 5.17).
    9.1.2.1 When the Missed Approach Point Fix is a Runway or Helipad Fix, Waypoint Description Position One, must carry a character “G” and the “M” in Position Four.
    9.1.2.2 When the Missed Approach Point Fix is MAP Fix, Waypoint Description Position One will carry a code equal to the type of fix such a Navaid or waypoint and must carry a character “M” in Position Four.

  9.1 复飞点
   9.1.1 所有进场程序编码必须包括一个标识复飞点修正点的航段。此类修正点必须是已发布的复飞点，可以是IFR着陆阈高或直升机停机坪着陆点或专用的复飞点（MAP修正点）。
   9.1.2 在程序记录序列中标识修正点以及修正点的类型，必须通过“航路点描述”字段中的编码完成（参见第5.17节）。
    9.1.2.1 当复飞点修正点为跑道或直升机停机坪修正点时，航路点描述的第一个位置必须携带字符“G”，第四个位置必须携带字符“M”。
    9.1.2.2 当复飞点修正点为MAP修正点时，航路点描述的第一个位置必须携带等于修正点类型的导航设施或航路点的代码，并且第四个位置必须携带字符“M”。

复飞程序的第一航段

  9.2 First Leg of Missed Approach Procedure
   9.2.1 The first sequence of the Missed Approach Procedure must always be coded with the character “M” in Position Three of the “Waypoint Description” field.
   9.2.2 Coding of the Missed Approach Procedure assumes that the procedure will be flown commencing at the Missed Approach Point Fix.

  9.2 复飞程序的第一航段
   9.2.1 复飞程序的第一个序列必须在“航路点描述”字段的第三个位置编码字符“M”。
   9.2.2 对复飞程序的编码假设该程序将从复飞点修正点开始飞行。

复飞程序的垂直路径

  9.3 Vertical Path of Missed Approach Procedure
   9.3.1 If the published Missed Approach Point Fix is a Runway fix or a Helipad Fix, then the following rules apply:
    9.3.1.1 The Altitude 1 value in the Missed Approach Point sequence must be equal to Runway Threshold or Helipad Alighting Point Elevation plus the published TCH. If TCH is not specified by source then use 50 feet.
    9.3.1.2 The first leg of a Missed Approach Procedure will contain any government source provided altitude constraints. These altitudes may be provided as “At,” “At or Above,” “At or Below,” “At or Below to At or Above,” dependent on the government source documentation and coded in accordance with Section Five, Subsection 5.29 of this Specification. Except as indicated below, if the government source does not provide an altitude constraint for the first leg of the Missed Approach Procedure, none will be coded
    9.3.1.3 In precision approach procedures or “Full ILS” (Localizer and Glide Slope) or GLS, the Altitude 1 value in the Missed Approach Point Fix sequence must be equal to runway threshold or the helipad alighting point elevation plus the published TCH. If TCH is not specified by source then use 50 feet. The “Decision Height” value at which the Missed Approach Procedure would normally be commenced is not coded as part of the Approach Procedure. The Altitude values in the first leg of the Missed Approach Procedure, when coded, will be the source provided values.
    9.3.1.4 In non-precision approach procedure coding, the Altitude 1 value in the Missed Approach Point Fix sequence must be equal to the runway threshold or helipad aligning point elevation plus the published TCH, or 50 feet if not specified by source. The “Minimum Descent Altitude” value at which the missed approach decision would normally be made is not coded as part of the Approach Procedure. The Altitude values in the first leg of the Missed Approach Procedure, when provided, will be the source provided values.
    9.3.1.5 When an immediate turn is specified in an ILS, MLS, or GLS missed approach, or if the source describes a turn greater than 15 degrees from the final approach path, without an altitude specified before the turn, as the first leg of a missed approach a course from or heading to an altitude (CA, FA, VA) leg must be coded as the first leg of the missed approach, using the approach course for the leg heading or course. The altitude will be coded as a minimum altitude, at least 400 feet above the airport elevation and the leg will terminate at that altitude.

  9.3 复飞程序的垂直路径
   9.3.1 如果已发布的复飞点修正点是跑道修正点或直升机停机坪修正点，则适用以下规则：
    9.3.1.1 复飞点修正点序列中的高度1值必须等于跑道阈高或直升机停机坪降落点标高加上已发布的TCH（阈高超过高度）。如果源文件未指定TCH，则使用50英尺。
    9.3.1.2 复飞程序的第一个航段将包含任何政府来源提供的高度约束条件。这些高度可以是“在”、“至少”、“至多”、“至多至少”等形式，根据政府源文件的要求，并根据该规范第五节5.29小节的规定进行编码。除非下文另有说明，如果政府来源未对复飞程序的第一个航段提供高度约束条件，则不会进行编码。
    9.3.1.3 在精密进场程序中，或者完整ILS（局放系统和下滑道）或GLS中，复飞点修正点序列中的高度1值必须等于跑道阈限或直升机降落点标高加上已发布的TCH。如果源文件未指定TCH，则使用50英尺。正常情况下，决断高度并不作为进场程序的一部分进行编码。当编码复飞程序的第一个航段时，如果提供了高度值，则将使用源文件中提供的高度值。
    9.3.1.4 在非精密进场程序的编码中，复飞点修正点序列中的高度1值必须等于跑道阈限或直升机降落点标高加上已发布的TCH，或者如果源文件未指定，则使用50英尺。正常情况下，决断最低高度并不作为进场程序的一部分进行编码。当提供了复飞程序的第一个航段的高度值时，将使用源文件中提供的值。
    9.3.1.5 当在ILS、MLS或GLS复飞程序中指定立即转弯，或者如果源文件描述了大于15度的转弯但没有在转弯前指定高度时，作为复飞程序的第一个航段，必须以离场高度（CA，FA，VA）航段或面对高度（CA，FA，VA）航段的方式编码第一个航段，使用进场航迹作为航段的航向或航迹。这个高度将作为最低高度编码，至少高于机场标高400英尺，并且航段将在该高度结束。

复飞程序其他注意事项

  9.5 Other Missed Approach Procedure Considerations.
   9.5.1 Opposite end runway or helipad fixes must not be used in the coding of missed approach procedures.
   9.5.2 The procedure reference Navaid must be used as the Recommended Navaid when required, with the following exceptions:
    9.5.2.1 The first leg of a Missed Approach Procedure may be a CD, FD or VD leg. For these legs a DME may be used as the Recommended Navaid, with the Theta field left blank and the DME distance entered in the Rho field.
    9.5.2.2 Rule deleted by Supplement 17.
    9.5.2.3 The first leg of the Missed Approach Procedure may be a CR or a VR leg. For these legs, a VOR facility (without or without DME) may be used as the Recommended Navaid. When the facility has no DME, the Rho field is left blank and the VOR radial is ente red in the Theta field.
    9.5.2.4 When the first leg of a Missed Approach Procedure is coded as a “HA or HM” leg, the coding will also include a government source provided altitude.

  9.5 其他复飞程序注意事项
   9.5.1 不得在复飞程序的编码中使用相反方向的跑道或直升机停机坪修正点。
   9.5.2 当需要时，必须使用程序参考导航设施作为推荐导航设施，但有以下例外：
    9.5.2.1 复飞程序的第一个航段可以是CD、FD或VD航段。对于这些航段，可以使用DME作为推荐导航设施，Theta字段留空，DME距离填入Rho字段。
    9.5.2.2 此规则已在第17号补充中删除。
    9.5.2.3 复飞程序的第一个航段可以是CR或VR航段。对于这些航段，可以使用VOR设施（有或无DME）作为推荐导航设施。当设施没有DME时，将Rho字段留空，并将VOR径向填入Theta字段。
    9.5.2.4 当复飞程序的第一个航段编码为“HA或HM”航段时，还必须包含政府来源提供的高度。

参考资料

• ARINC424规范

许可协议

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

分享文章