Flight Plan Filing General Information
Why file an ICAO Flight Plan (FPL)?
- On June 29, 2008, the FAA implemented a change in all en route Host computer systems that automatically assigns preferential routes based on the equipment and capabilities filed in the ICAO FPL.
- This change was made to facilitate the transition from the current Host system to the new En Route Automation Modernization (ERAM) system. ERAM will replace current Host systems at the 20 domestic Air Route Traffic Control Centers (ARTCC) beginning in early 2009.
- Although both Host and ERAM will continue to accept and process traditional NAS flight plans (FP), these flight plans will not qualify for assignment of RNAV departure and/or arrival routes. Flight plans filed in NAS format will, however, still qualify for automatic assignment of conventional (non-RNAV) departures and arrivals.
What is ERAM?
- En Route Automation Modernization (ERAM) is the largest National Airspace System (NAS) equipment replacement program in FAA history
- ERAM replaces 20 Air Route Traffic Control Center (ARTCC) legacy Host computer processing systems
- First operational use of ERAM is at Salt Lake ARTCC (ZLC) in early 2009
- Last to transition to ERAM is Miami ARTCC (ZMA) in late 2009
- ERAM implementation will make the U.S. ATC system ICAO compliant
Flight Plan Processing Challenge
- Host and ERAM base automated preferential route assignment on equipment and capabilities filed in the ICAO FPL
- Some systems, including Pre-departure Clearance (PDC) still display flight plans in NAS format
- Some NAS equipment suffixes cannot be derived directly from ICAO equipment qualifiers.*
Equipment |
FPL |
Actual NAS |
On PDC |
|
DME/DME/IRU |
DI/C |
/E |
/A |
|
DME/DME/IRU/RVSM |
DIW/C |
/J |
/W |
* FAA is persuing a solution for this problem
Qualification for RNAV Departure/Arrival Procedures
In order to qualify for the application of RNAV procedures (i.e. SID, STAR, PAR, PDR or PDAR), the operator must file the character 'Z' and at least one of the following in ICAO FPL Item 10a:
- D* DME (if DME/DME RNAV)
- DO* VOR & DME (if VOR/DME RNAV)
- I* Inertial Navigation System (INS)
- C* Loran-C
- DI** DME & INS (if DME/DME/IRU RNAV)
- G** GNSS/GPS
- R** Required Navigation Performance
- Z Additional Information is filed in ICAO FPL Item 18
* These equipment qualifiers do not qualify for published RNAV SID/STARs, but they may qualify for unpublished preferential routes if they are followed by NAV/RNVE99 in ICAO FPL Item 18.
** These equipment qualifiers may qualify for any RNAV departure/arrival procedure when followed by appropriate RNAV capabilities in ICAO FPL Item 18.
Operators must file the following RNAV capabilities, as appropriate, following the NAV/ indicator in ICAO FPL Item 18. Operators should file their maximum capabilities in order to qualify for the most advanced procedures.
Examples: NAV/RNVD1E2A1 (or) NAV/RNVE99
Explanation:
NAV/ = Indicates additional navigation information
RNV = Precedes RNAV capability for each phase of flight
D# = Departure segment RNAV capability
E# = En route segment RNAV capability
A# = Arrival segment RNAV capabilityFollow each flight segment indicator with appropriate RNAV accuracy values as defined in the Advisory Circulars below.
For operators equipped for advanced RNAV procedures in accordance with Advisory Circular (AC) 90-100A, U.S. Terminal and En Route Area Navigation (RNAV) Operations
RNAV 1 = “D1” and/or “A1”
RNAV 2 = “E2”
For operators equipped for Point-to-Point (PTP) RNAV in accordance with Advisory Circular (AC) 90-45A, Approval of Area Navigation Systems for Use in the U.S. National Airspace System, follow the en route flight segment indicator 'E' with '99'
Point-to-Point RNAV = “E99”
Reminder: File your maximum RNAV capability in Item 18
If you are en route RNAV 2 qualified, file “E2” and you will be eligible for RNAV 2 and PTP
Example: NAV/RNVE2
If you are not RNAV 2 qualified but are qualified for PTP, file “E99” and you will be eligible for PTP, only
Example: NAV/RNVE99
Note: Operators filing an ICAO FPL may suppress application of particular RNAV procedures by omitting Item 18 data for any or all segments of flight.
Questions?
Please see the FAQ section – we encourage submission of questions in writing via email using the link on that page.
For questions or additional information contact:
Don Schraub, AJE-36
Northrop Grumman Corp.
Technical Performance Support
Donald.CTR.Schraub@faa.gov
940-845-4896
Keith Dutch, AJE-36
FAA/Technical Performance Support
Keith.Dutch@faa.gov
202-267-7012