Flight Plan Filing FAQs

A:  ERAS will use the 3-letter facility address in Field 3b of the FPL for acknowledgements, if present; otherwise, the acknowledgement will be sent to the AFTN originator address.  In either case, the address must be adapted as a “responding” facility in ERAS to receive acknowledgements; if your system is not currently receiving acknowledgements, contact us to register your address as a responding facility.Please refer to comprehensive guidance with examples on this website at Filing Instructions/Reference Guide/Message ACK/REJ.  
NOTE:  POC information with an email link appears at the bottom of this section.

Q:  Currently, if an FP is filed and there is no activity with respect to the flight two (2) hours after the proposed departure time (“P time”), the FP will drop out of the system; is that also the case for an ICAO FPL and ERAM?  New 1/11/08

A:  Yes – the FP or FPL will drop out in accordance with an adaptable parameter based on the “P” time; at most facilities this is nominally set to 2 hours.  It works the same for FPs and FPLs, and will not change with ERAM implementation.
NOTE:  If an Expect Departure Clearance Time (EDCT) is applied to a flight, the later of the EDCT and the “P” time will apply (i.e., if the “P” time is 1200 and EDCT is 1330, the FPL/FP will drop at 1530 if not activated, not at 1400).

A:  Users should file the ICAO four-letter LOCID in Item 13; US three-letter LOCIDs can be converted by prepending a “K” (e.g., IAD is KIAD).  Center information is being standardized to include both the three- and 4-letter LOCIDs, as we will be accepting both ICAO FPLs and NAS Flight Plans (FP).  If no four-letter LOCID is assigned or it is not known, insert “ZZZZ” in Item 13 and provide the name of the departure airport in Item 18 following “DEP/” (e.g., “DEP/W66”).  Please refer to guidance on this website at Filing Instructions/Reference Guide/Domestic ICAO FPL.  Answer updated 1/11/08

Q:  Will users be able to file “T-routes” using the ICAO FPL and using DUATS (e.g., Caribbean)?

A:  Yes – continue to file “T-route” information in Item 15, Route, as you do in a NAS FP.  DUATS will accept the routing as well. Answer updated & moved 1/11/08

Q:   Will including domestic EET/ data cause an FPL to be rejected?  New 1/11/08

Q:   Can we file “EET/” with no data?  New 1/11/08

A:   ERAS will reject an ICAO FPL which has “EET/” with no trailing data string in Item 18.  If your filing system automatically inserts “EET/”, please contact us to discuss mitigating this issue by inserting a trailing data string which will work for your system (e.g., “EET/NONE”).  ERAS will not process the data string you enter; however, we will test the suggested data string to ensure your FPLs are accepted.  Please refer to guidance on this website at Filing Instructions/Reference Guide/Domestic ICAO FPL.

Q:   If flight goes into Canadian Airspace should EET/ data be included?  New 1/11/08

A:  EET/data should normally be included for any international portions of the route of flight.

A:  Any aircraft/crew capable of RNAV 1 can file E2 or E1 (we recommend “E2”), but it would not be an error to file E99 and the FPL would be accepted.  Please note we request you file your maximum RNAV capability in Item 18; filing E99 would make the flight ineligible for any portions of an RNAV Standard Instrument Departure (SID) or Standard Terminal Arrival Route (STAR) which extend into the en route environment.  Please refer to guidance on this website at Filing Instructions/Reference Guide/RNAV Requirements.

A:  Comply with both WATRS+ and domestic ICAO FPL filing guidance by inserting any/all required data strings in Item 18 of the FPL after "NAV/" with spaces in between.  Each automation system (e.g., Ocean21, Host/ERAM) looks for its own string and ignores others.  In your example, insert "NAV/RNVD1E21 RNP10" or "NAV/RNVD1E21 STS/NONRNP10", as appropriate.  Please refer to guidance on this website at Filing Instructions/Reference Guide/RNAV Requirements.

A:  It can be appropriate to file either value - you can qualify for PTP using AC 90-45A (RNVE99) or AC 90-100A (RNVE2) IAW guidance on this website at Filing Instructions/Reference Guide/RNAV Requirements.  Please file your maximum RNAV capability in Item 18.

Q:  Will the system accept RNAV arrival data only?  Do you have to file values for all RNAV flight segments (i.e., D1, E2 or E99, A1) in every FPL?  New 1/11/08

A:  ERAS will accept an “A” value without a “D” or “E” value; you can file values for any combination of flight segments – one, two or all three.  Omit Item 18 RNAV value information for any segment for which RNAV preferential route application is not desired.  Please refer to guidance on this website at Filing Instructions/Reference Guide/RNAV Requirements. 

A:  Yes, E1 can be filed, although we are recommending filers use E2.  If E1 is filed, ERAS will assign any E2 or E99 routes.  Please refer to guidance on this website at Filing Instructions/Reference Guide/RNAV Requirements.

Q:  What is meant when you say RNAV preferential routes will be "automatically assigned by Host/ ERAM"?  New 1/11/08

A:  When an FPL/FP is filed through AFTN/NADIN, ERAS checks FPL/FP fields for information on equipage, requested route, requested procedures, etc.  It uses that information to determine whether to assign conventional routes/procedures or RNAV preferential routes (RNAV SID/STAR/PTP).  Beginning June 5, 2008, when an ICAO FPL is filed, ERAS will:

• Check Item 10, Equipment, to determine whether the aircraft is equipped for and requesting RNAV routes; and

• If “no” – apply an appropriate conventional route/procedure.
• If "yes" – Check Item 18, Other Information, for an acceptable data string following "NAV/" to determine if the flight/crew is capable and desirous of an RNAV SID/STAR/PTP; and
• If “no” – apply a conventional route/procedure.
• If "yes" – automatically apply appropriate RNAV SID/STAR/PTP to the FPL and present it to the controller.

• In each case, the appropriate route/procedure assigned may be the route requested; however, in cases where the route requested is not active or is otherwise not appropriate ERAS will automatically assign a different one.

A:  Filers should use an ICAO FPL CHG message.  Please refer to guidance with examples on this website at Filing Instructions/Reference Guide/Message ACK/REJ.  Answer updated 1/11/08

Q:  Can “RMK/” be filed anywhere in Item 18 of an ICAO FPL?  New 1/11/08

A:  Yes – ERAS will accept “RMK/” information anywhere in Item 18; for standardization, our preference is the “RMK/” information be placed last in Item 18.  Please refer to guidance on this website at Filing Instructions/Reference Guide/Domestic ICAO FPL.

A:  Filers should continue to follow the conventions currently requested by placing the information after “RMK/” in Item 18 of the ICAO FPL (e.g., “RMK/HAR,” “RMK/PTP”).  Answer moved 1/11/08

A:  There is no requirement in ICAO Doc. 4444 to include Item 19 in an FPL.  We understand various filing conventions have evolved which may loosely conform to ICAO guidance, but Host/ERAM does not accept an FPL with an appended Item 19.  Additionally, other interfaced automation systems (e.g., Mexico's Eurocat X) have compatibility problems accepting Item 19 data in cross border messaging.  Please refer to guidance which can be downloaded from this website at Filing Instructions/Reference Guide.

Q:  It appears FAA intends to provide the same functionality in the ICAO FPL as in the NAS FP.  Can a user file ICAO FPLs for all operations, including domestic only, if the filing conventions are followed?  New 1/11/08 

A:  Yes – after June 5, 2008, users can file ICAO FPLs for all flights (RNAV or non-RNAV); however, before that date RNAV preferential routings may not be applied to ICAO FPLs (i.e., FPLs filed with RNP or GPS capability will be considered for RNAV 1 routes; DME/DME/IRU capability cannot be detected).

Q:  Will flights that enter Canadian airspace be required to file an FPL with each/all Canadian Flight Information Regions (FIR)?  New 1/11/08 

A:  (Response by NavCanada) Yes, Canada requires the FPL to be filed with all Canadian FIRs along the route of flight in accordance with ICAO. 

Q:  Will DUATS handle ICAO flight planning?  New 1/11/08

A:  Yes; drop down help menus are being added.  Please see links on this website at Filing Instructions/Pilot Guidance. 

Q:  Point-to-Point (PTP), RNAV and “T” routes can be auto assigned today using a NAS FP; will filing an ICAO FPL provide the same service?   New 1/11/08

A:  Yes; follow the same procedures and put the information in Item 18 after “RMK/” or “NAV/”, as applicable.

Q:  Do we continue to follow current procedures for PTP, RNAV and the CDR Playbook?  New 1/11/08

A:  There are no changes to current procedures; please continue to follow them.

Q:  Do we file an ICAO FPL from Alaska to enter the CONUS?  New 1/11/08

A:  Yes – an ICAO FPL is required when crossing international boundaries.

A:  Domestic-only ICAO FPLs and international flights which remain in North America (i.e., destination Canada or Mexico) should only be addressed to the departure US FIR/ARTCC.  International ICAO FPLs should be addressed to the departure US FIR/ARTCC only, domestically, and to each FIR IAW Doc 4444 instructions.  Answer updated 1/11/08

A:  FAA will accept ICAO FPLs filed IAW Document 4444 in compliance with ICAO standards.  Our software will also accommodate some NAS FP-only conventions for domestic-only ICAO FPLs, such as block altitudes and message assurance responses to a third party; these will be documented in the Flight Plan Filing section of the website.  Please refer to guidance on this website at Filing Instructions/Reference Guide/Domestic ICAO FPL.  Answer updated 1/11/08
NOTE:  Filers are cautioned these conventions should only be filed in a domestic-only ICAO FPL, as such FPLs may be rejected by the flight plan systems of other ANSPs.

Q:  As an international airline operating flights to the U.S., when should we begin to file FPLs according to your requirements?  New 1/11/08  

A:All airlines will need to comply as of June 5, 2008 -if- you desire assignment of RNAV departure, arrival and/or PTP services in the portion of the flight in U.S. domestic airspace.

A:  Transition details (e.g., exact Zulu date/time to switch from NAS FP to ICAO FPL) will be finalized in early calendar year 2008.  Please refer to schedule information on this website at General Information/Schedules & Testing.Answer updated 1/11/08

A:  Yes, but you will be assigned conventional routing, only.

A:  The Phase I test report highlights common errors and can be found on this website at General Information/Schedules & Testing.

Q:   Do you plan any testing outside of the continental U.S.?  New 1/11/08

A:  No, though we are coordinating with our neighboring ANSPs and submitting ICAO working papers to various international meetings on the change.

Q:  Are there plans to provide testing after Phase 1 and before the June 5, 2008, implementation date?  Will it be possible to test with all 20 ARTCCs, or with individual ARTCCs?  Are those test plans available for review?  New 1/11/08 

A:  Phase 2 testing will be conducted from mid-February through May 2008.  Filers may request to test with any or all of the 20 ARTCCs.  Instructions for Phase 2 can be found on this website at General Information/Schedules & Testing.

Q:   Is there a list of critical DME facilities?  New 1/11/08

A:   The RNAV/RNP office does not maintain a master list of critical DME facilities to be cross-referenced with procedures. The critical DMEs are published on the individual charts as "xxx DME required".  Per Advisory Circular (AC) 90-100A paragraphs 6b and c, we validate the infrastructure, provide the information on required facilities and NOTAM as appropriate; however, it is the operator's responsibility to monitor the requirements/availability of infrastructure supporting procedures for each location to which aircraft are dispatched.

Q:  Will ETMS be able to process early intent filing in the new format?  New 1/11/08 

A:  ETMS will be able to process early intent messages.

Q:  Will other ANSP automation systems accept our format?  New 1/11/08

A:  Working papers on the transition are being submitted to ICAO meetings attended by the U.S.  Other ANSP systems currently handle “NAV/” strings IAW requirements from multiple countries without issue.  We are not aware of any potential problems with ANSP handling of U.S. Item 18 format requirements other than the 20 character limit to the “NAV/” string in the Eurocontrol flight planning system.

A:  No – ERAM will process consistent with the June 5, 2008 procedures.  NAS FPs will only be considered for conventional routes, and FPLs can be used for either conventional or RNAV routes.  Answer updated 1/11/08

Q:  Is the DLA problem fixed in Host 1.6?

A:  The software fix is ready and expected to be deployed by February 2008.  Answer updated 1/11/08

A:  Please refer to guidance on this website at Filing Instructions and atFiling Instructions/Reference Guide/Domestic ICAO FPL.  Answer updated 1/11/08