2.
NAV/RNVA1 or NAV/RNVD0E0A1 (Same meaning)
3.
NAV/RNVE2 or NAV/RNVD0E2A0 (Same meaning)
4.
NAV/RNVD1A1 or NAV/RNVD1E0A1 (Same meaning),
5.
NAV/RNVD1E2A1.
12.5.2 If you are RNAV PTP capable, but not RNAV 1 and/or RNAV 2 capable:
12.5.2.1 Item 10, Equipment
In addition to identifying all available and serviceable communication, navigation, approach aid, and surveillance equipment carried on your aircraft, insert the character “Z”.
12.5.2.2 Item 18, Other Information Insert “RMK/PTP” and “NAV/RNVE99”.
EXAMPLE.
RMK/PTP NAV/RNVE99
12.5.2.3 The following variations will be accepted in ERAS for automatic assignment of RNAV routes: One or more spaces may follow “NAV/.”
EXAMPLE.
NAV/ RNVD1A1. The “D”, “E”, and “A” characters may appear in any order following “NAV/RNV”.
EXAMPLE.
NAV/RNVD1A1E2 NAV/RNVA1D1E2.
Additional items required by other automation systems may be filed after “NAV/” in any order.
EXAMPLE.
NAV/RNP10 RNVD1E2A1, NAV/RNVD1E2A1 RNP4 NAV/RNAV1 RNAV5 RNVD1E2A1.
12.5.2.4 If the Item 18 entries following “NAV/” do not follow the above instructions, the flight plan will be accepted by ERAS, but you will not be automatically assigned RNAV. Common errors include: Putting spaces between RNV, D1, A1, and/or E2 – no spaces are allowed between the segments. Filing “RNAV” instead of “RNV” – RNAV is not acceptable in the U.S. domestic string after “NAV/”.
12.6 If the pilot intends to operate in RVSM airspace, he/she should file the qualifier “W” in order to be cleared into RVSM airspace.
12.7 For a copy of FAA Form 7233.4, and for information on how to complete the form, please go to: www.faa.gov/ato?k=fpl.
12.8 Planned Changes to Filed Flight Plans in 2012. On November 15, 2012, the ICAO FPL will undergo significant changes regarding item and field contents for FPLs and related messages. For additional information go to: www.faa.gov/go/ fpl2012.
Federal Aviation Administration Twentieth Edition
ENR 1.11 Addressing of Flight Plans for Domestic
or International Flight Planning
1. General Information
1.1 In order to safely and efficiently exercise their responsibilities, controllers must receive the most current and accurate flight plan information available. For departing aircraft, this information is normally received in the form of an ICAO Filed Flight Plan (FPL). For aircraft inbound from an adjacent facility, flight plan information may also be received in the form of an FPL, however, if available, the most current information is received via inter.facility automated interface in the form of a Current Flight Plan (CPL). Although the FPL and CPL are similar, they differ in that the FPL contains the requested route/altitude, while the CPL contains the route/altitude actually assigned to the aircraft.
1.2 Within domestic U.S. (contiguous 48 states) airspace, only the first en route facility needs to receive flight plan data, whether from the filer or an adjacent facility. This is due to the fact that U.S. en route computer systems automatically forward current flight plan data and revisions from facility to facility. The inappropriate addressing of an FPL by the filer may create processing and/or controller workload issues, resulting in delays.
1.3
Please refer to guidance in the scenarios below to ensure that FPLs are addressed correctly.
2.
Addressing Guidance
NOTE.
In this section, U.S. Domestic Airspace includes the 48 contiguous states and Puerto Rico.
Please use the following criteria when selecting addresses for transmission of the ICAO FPL to U.S. Air Traffic Control (ATC):
2.1 Address the FPL to the departure ARTCC only. Do not address subsequent U.S. domestic facilities.
NOTE.
If a flight leaves U.S. domestic airspace and later re.enters
U.S. domestic airspace, the return portion of the flight should be addressed per guidance in Scenarios 2.3 or 2.4 below, as applicable.
2.2 U.S. Domestic to International Destinations
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：美国航行情报汇编 AERONAUTICAL INFORMATION PUBLICATION AIP 2(143)
