7.5.1 北美航路 North American Routes
For North American Routes for North Atlantic Traffic, “Non-Common” portion and other Preferred or Preferential Routes without published identifiers but with unique initial and terminus fix points, the route identifier will be developed using the initial and terminus fix identifiers, as indicated in the table below.
对于北美的北大西洋航路, “非公用”部分以及其他优选或无代码但有唯一标识和终止定位点的优选类航路,航路识别符应使用起始和终止定位点的识别符组合而成
| Fix Type | Create Identifier Using |
|---|---|
| Airport | Three or Four Character Airport Identifier |
| Navaid | Navaid Identifier |
| Waypoint | Waypoint Identifier(five character max) |
例子：
From Airport to Airport - CYYLCYYC
From Airport to Navaid - CYYLART
From Navaid to Waypoint - ARTCOLAR
7.5.2 基于相同定位点的多条航路 Multiple Routes - Same Fix
If there is more than one routing without a published identifier between the same to fixes and the rules in Section 7.5.1 is being used to create the route identifier, then add numerics to indicate the multiple routings.
当有一条以上航路在被应用于命名航路识别代号时，如7.5.1规定的相同定位点之间无规定的识别代号，则增加数字以表示多条航路。
例子：For two routes between the airports CYYL and CYYC, CYYLCYYC1 and CYYLCYYC2
7.5.3 优选或优选类航路 Preferred or Preferential Routes
For Preferred or Preferential Routes without a published identifier and not between unique initial and terminus fix points but rather from areas or regions such as Terminal Control Areas, FIRs or Geographical Entities, the route identifier will be derived from commonly understood elements such as communications center identifiers, country or region abbreviations and the like. Note that if one end of the routing is a unique fix, the rules in Section 7.5.1 apply for that fix.
对于没有公布代号,也不是从唯一起始点/终止点，但确实是以终端管制区、FIR或地理区域为起始点的某个区域或地区之间的优选或优选类航路。使用通讯呼号，国家名称或区域简缩字之类通俗易懂的元素生成航路代码。备注：如果起始点或终止点是一个唯一的定位点，此定位点应使用规则 7.5.1.
| 区域或地区 | 生成代号的元素 |
|---|---|
| FIR,ARTCC | FIR或管制中心的ICAO四字代码 |
| 终端区 | 终端区核心机场三、四码 |
| 地理区域 | 通俗易懂的简缩字 |
| ICAO区域 | 两字ICAO区域 |
例子：
从终端区至机场- CYULCYYC
从FIR 至FIR – ENBOGCCC
从管制中心至机场 – KZTLKRDM
从地理区域至终端区- SCANDICCC
7.5.4 基于相同点/区域/地区的多条航路 Multiple Routes-Same Points/Areas/Regions
在两个相同的点/区域/地区之间有一条以上未公布代号的航路时，而且使用了7.5.3规则命名该航路的代号，需增加数字编号。
If there is more than one routing without a published identifier between the same two points/areas/regions and the rules in Section 7.5.3 is being used to create the route identifier, add numerics to indicate the multiples.
例如:
在KZTL和KRDM之间有2条航线,KZTLDRDM1和KZTLDRDM2
7.5.5 优选或优选类飞越航路 Preferred or Preferential Overfly Routings
对于优选或优选类飞越航线，设计的航路未使用机场/终端区离场或机场/终端区的进场时，该航路代号为：以飞越的定位点、地区和表示飞越方向的前缀，或飞越方向相关的原来方向为后缀，按下表表示。如果这条航线是飞越航线并且未采用方向限制，以字母“O”表示飞越航线，而不采用方向指示。
| 定位点/地区/区域 | 方向 | 生成代号的元素 |
|---|---|---|
| 机场 | 三或四字机场代码 | |
| 导航台 | 导航条呼号 | |
| 航路点 | 航路点识别符 | |
| FIR,ARTCC | FIR/中心ICAO四码 | |
| 终端区 | 终端区核心机场四码 | |
| Geographical Entity |
通常使用缩减字 | |
| ICAO区域 | 两字ICAO区域代码 | |
| 北向 | “N” | |
| 南向 | “S” | |
| 东向 | “E” | |
| 西向 | “W” | |
| 飞越 | “O” |
备注: 表中的方向代码仅用于指导.某些公布的方向代码可能会增加1,2 或3字的前缀/后缀.
7.5.6 相同定位点/区域/地区间的多条飞越航路 Multiple Routes - Overfly
在定位点/区域/地区之间有一条以上无代号的航路时，而且使用规则7.5.5进行了命名，需再增加一位用于编号的数字。
If there is more than one routing without a published identifier between the fix/area/region and the rules in Section 7.5.5 are being used to create the identifier, add a numeric to indicate the multiples.
例如:SENBO1,SENBO2,OEGLL1,OEGLL2,OEGLL3
7.5.7 优选周日/周末航路 Preferred Weekday/Weekend
对已公布的带周日和周末限制条件的优选或优选类航路，多航路规则被2字后缀代替（代替数字），“WK”表示周日，“WE”表示周末。这条规则适用于有/无代号的航路。
For Preferred or Preferential Routings that are published with a “weekday” and a “weekend” version, the rules for “multiples” are replaced with a two character suffix (replacing the numerics). “WK” is used for “weekday” and “WE” is used for “weekend.” This rule applies to routes both with and without published identifiers.
例子：
Published Identifiers:TOS1WK and TOS1WE
Unpublished Identifiers:SENBOWK and SENBOWE
7.5.8 多条周日/周末航路 Weekday/Weekend
If there is more than one routing published as “weekday” or “weekend” and the rules in Section 7.5.7 are being used to create the identifier, add a numeric to indicate the multiples.
如果有一条以上公布为周日或周末的航路，而且已经使用7.5.7规则命名代号，需增加一个用于编号的数字，以区分多条航路。
Examples: TOS1WK1 and TOS1WK2
7.5.9 地理区域间的航路 Geographical Routings
对已公布的不能以航空术语命名的大的地区之间的优选或优选类航路，通常使用地区简缩字命名航路代号。考虑到这样可能减少了地理区域名称的字符，需使用地理区域参考表来建立航路代号与地理区域之间的联系。由于航路代号只能容纳10个字节，通常用5个字标识航路的起始点，另5个字标识航路的终止点。如果用实际地名可以命名航路代号，则不必使用这一规则。
For Preferred or Preferential Routings that are published as being between large areas not definable with aeronautical terms, a convention of Geographical Entity abbreviations is used to create Route Idents. As these Route Idents will have reduced the entity name down considerably, the Geographical Entity Reference Table is used to provide a link between the Route Ident and the full entity name. While the Route Ident is 10 characters long and normal split five and five between the initial and terminus points of the route, that split does not have to be applied when creating Route Idents based on Geographical Entities.
例如：在英国(UK)北部和希腊(西部)之间的航路——UKNDGRECW或NOUKWGRECE。
7.5.10 地理区域间多航路 Multiple Routes - Geographical
If there is more than one routing without a published identifier between geographical entities and the rules in Sections 7.5.8 are being used to create the identifier, add a numeric to indicate the multiples.
如果在地理区域之间存在一条以上航路，而且已经使用了7.5.8命名规则，则需要再加上一个用于编号的数字，以区分多条航线。
Examples: UKNOGRECW1 and UKNOGRECW2
7.5.11 “Off Load”航路
For Preferred or Preferential Routings that are published with an “off load route,” the rules for “multiples” are replaced with a three character suffix (replacing the numerics). “OLR” is used for the “off load route.” The standard route would not use a suffix. This rule applies to routes both with and without published identifiers.
Examples:
Published Identifiers - TOS1 and TOS1OLR
Unpublished Identifiers - SENBO and SENBOOLR
7.5.12 Multiple Routes-Off Load
If there is more than one routing published as “off load route” and the rules in Section 7.5.11 are being used to create the identifier, add a numeric to indicate the multiples.
如果存在一条以上公布为OLR的航路，用7.5.11命名代号后要再加上用于编号的数字以区分多条航路。
Examples: SENBOOLR1 and SENBOOLR2
本文采用 署名-非商业性使用-相同方式共享 4.0 国际 许可协议，转载请注明出处。
