Flight Plan Filing FAQs

Q:  Can a user file ICAO FPLs for all operations, including domestic only, if the filing conventions are followed? 
A:  Yes.  Users can file ICAO FPLs for all flights including domestic only..

Q:  Will flights that enter Canadian airspace be required to file an FPL with each/all Canadian Flight Information Regions (FIR)? 
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?
A:  Yes. 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?
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?
A:  Yes.  There are no changes to current procedures; please continue to follow them.

Q:  Do we file an ICAO FPL from Alaska to destination within the conterminous U.S.? 
A:  Yes. An ICAO FPL is required when crossing international boundaries.

Q:  Should the ICAO FPL be addressed to each U.S. Flight Information Region (FIR)/ARTCC?
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. 

Q:  Why is FAA diverging from ICAO standards?
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. 

NOTE:  Filers are cautioned these conventions should be filed in a domestic-only ICAO FPL, as such FPLs may be rejected by the flight plan systems of other ANSPs.

Q:  What about proposed changes to the ICAO FPL which replace “NAV/” with “PBN/”?
A: Once ICAO guidance is final, FAA will work toward implementation of FPL changes and timeframes.

Q:  Can we still file a NAS FP.
A:  Yes, but you will be assigned conventional routing, only.

Q:  What NAS equipment suffixes cannot be derived from equipment filed in an ICAO FPL?
A: NAS equipment suffixes /E, /J, /F, /K, /I, /C and /Y cannot currently be accurately derived from equipment qualifiers filed in an ICAO FPL.  FAA is exploring options to compensate for these differences between NAS and ICAO equipment qualifiers.

Q:  Can filers include the proposed departure time in an ICAO Modification (CHG) message?
A:  No.  In accordance with ICAO Doc. 4444, FAA’s En Route Automation System (ERAS) does not accept a CHG message which includes a proposed departure time; the CHG would be rejected.  Please refer to guidance on this website at Filing Instructions/Reference Guide/Message ACK/REJ

Q:  How do filers ensure a reply is sent to the responding terminal as currently done with a domestic Flight Plan (FP)?
A:  ERAS will use the 3-letter facility address in Item 3b of the FPL for acknowledgements, if present; otherwise, the acknowledgement will be sent to the originator's AFTN address.  In either case, the address must be adapted as a “responding” station in ERAS to receive acknowledgements.  If your system is not currently receiving acknowledgements, contact us to register your address as a responding station.  Please refer to comprehensive guidance with examples on this website at Filing Instructions/Reference Guide/Message ACK/REJ.

Q:  Will an FPL be automatically rejected or is that a manual function?
A:  ERAS automatically rejects an improperly formatted FPL.  The Rejection (REJ) message usually includes information which identifies the error.  The filer should correct the error and reenter the FPL.  Occasionally, messages rejected for reasons other than format errors are sent to ARTCC Flight Data personnel and result in a phone call (manual rejection).  Please refer to guidance with examples on this website at Filing Instructions/Reference Guide/Message ACK/REJ.

Q:  Does FAA plan to change guidance issued in 2003/2004 regarding ICAO FPL message assurance using Item 3b/c?  How will FAA handle the “CHG” message?
A: No.  Guidance regarding the optional use of Item 3b/c, as supplemented by Host/ERAM system specifications, was developed for filers of domestic ICAO FPLs. Optional use of Item 3b/c provides for FPL message reference/change assurance and destination routing for message replies, whereas an ICAO FPL filed without information in Item 3b/c results in a reply to the NADIN address from which the FPL was filed. Updated guidance, including the “CHG” message, can be found on this website at Filing Instructions/Reference Guide/Message ACK/REJ.

Q:  Should filers continue to follow current procedures for advanced flight plan filing (e.g., 30 minutes prior to proposed departure time)? How will FAA handle “DLA” and “ACK” inside this parameter?
A: Yes.  Flight plan filing parameters have not changed. Flight plan revisions submitted less than 30 minutes prior to proposed departure time will normally be rejected.  Filers should contact the ARTCC Flight Data Unit for changes less than 30 minutes prior to the proposed departure time.

Q:  Can we file call signs beginning with a number?
A:  Users should file the FPL IAW ICAO Doc 4444. If the FPL is rejected, contact the ARTCC Flight Data Unit to which the FPL was sent so they can ensure acceptance in ERAS.

Q:  Is it required that filers include ICAO Items 8a/b in a domestic FPL?
A:  For domestic flights, Item 8a (Flight Rules) is required, but Item 8b (Type of Flight) is optional.

Q: Can filers continue to use the National Airspace System (NAS) aircraft designator?  What about type designator “ZZZZ”?
A: Where ICAO and FAA differ, comply with the ICAO FPL filing instructions in Doc 4444. Users should file the appropriate Type of Aircraft specified in ICAO Document 8643; aircraft Type Designators (e.g., B747-200 is indicated as “B742”); if no designator has been assigned or it is not known, insert “ZZZZ” in Item 9 and specify the type of aircraft in Item 18 following “TYP/”. Please refer to guidance on this website at Filing Instructions/Pilot Guidance.

Q:  Will FAA resolve the differences between ICAO documents and FAA handbooks regarding the Wake Turbulence Category (WTC) for Heavy (H) and Medium (M); in particular, what about differing WTC for the B757-200 series aircraft?
A: Where ICAO and FAA differ, comply with the ICAO FPL filing instructions in Doc 4444 and FAA will handle the difference procedurally. For example, the ICAO WTC for all B757s is “M”, while the FAA certified WTC for some B757-200s is “H”.  In Item 9, filers should indicate WTC as “M” for all B757s. Please refer to guidance on this website at Filing Instructions/Reference Guide/Domestic ICAO FPL.

Q:  Have the A388 and B748 been designated as a 'Super Heavy' (/J) wake turbulence category, or should we continue filing them as 'Heavy' (H/)?
A:   The Airbus 380-800 (A388) is still classified in the Heavy Wake Turbulence Category (WTC), indicator (/H).  The FAA is aware of discussions about the "Super" WTC, but the official ICAO publication (Doc 8643, Aircraft Type Designators) has not been amended to reflect this change.  ICAO guidance has indicated that the "/J" will be used to describe this new WTC, which presently applies only to the Airbus 380-800.  There is speculation that it may also include aircraft such as the Boeing 747-8 in the future.

Please continue to refer to ICAO Document 8643 for any updates of WTC descriptions and appropriate aircraft type designators at: http://www.icao.int/anb/ais/8643/index.cfm

N/A

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?
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).

Q:  Should we file a 3-letter or 4-letter location identifier (LOCID) (e.g., W66)?  Currently each center has a unique identifier table.  Will they all be configured the same with the 4-letter LOCID?
A:  Users should file the ICAO 4-letter LOCID in Item 13.  U.S. 3-letter LOCIDs can be converted by prepending a “K” (e.g., IAD is KIAD).  Center information is being standardized to include both the 3- 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 Item13 and provide the NAS identifier 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. 

Q:  Filing latitude/longitude (lat/long) coordinates is different for a domestic FP and an ICAO FPL; the domestic FP requires a slash (“/”) between the lat and the long.  Will ERAM implementation resolve the discrepancy?
A:  No.  Lat/long is filed differently in an ICAO FPL and a domestic FP.  You cannot use the "/" in an ICAO FPL.  ERAS will accept ICAO format lat/long in an FPL message and NAS format lat/long in an FP message.  Please refer to guidance on this website at Filing Instructions/Reference Guide/Domestic ICAO FPL (Item 15, Field 15c, Route) and at Filing Instructions/Reference Guide (Overview page).

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 ICAO Item 15 (Route) as you do in a NAS FP.  DUATS will accept the routing as well.

N/A

Q:   Will including domestic EET/ data cause an FPL to be rejected? 
A:  No.  ERAS does not require EET/ data in an ICAO FPL for the route portion in U.S. domestic airspace.  The FPL will not be rejected; however, ERAS will not process EET/ data if filed.  Please refer to guidance on this website at Filing Instructions/Reference Guide/Domestic ICAO FPL.

Q:   Will ERAS accept an "EET/" in Item 18 with no associated data included? 
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 the flight goes into Canadian airspace should "EET/" data be included?
A:  Yes.  EET/ data should normally be included for any international portions of the route of flight.

Q:  Is there any scenario where a user would insert “NAV/D1E99A1” in Item 18 as an RNAV value?
A:  Any operator 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 that 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.

Q:  How do users comply with differing requirements for data in Item 18?  For example, WATRS+ requires RNP-qualified operators to file an ICAO FPL with equipment codes “R” and “Z” in Item 10 and “NAV/RNP 10” in Item 18.  Non-RNP 10 operators must insert “STS/NONRNP10” in Item 18.  If a flight operates TJSJ/KJFK/KLAX, will ERAS accept such an FPL and keep the RNP 10 remarks in the FPL for all legs of the flight, both oceanic and domestic?
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 between.  Each automation system (e.g., Ocean21, Host/ERAM) looks for its own string and ignores others.  In your example, insert "NAV/RNVD1E2  RNP10" or "NAV/RNVD1E2  STS/NONRNP10", as appropriate. Please refer to guidance on this website at Filing Instructions/Reference Guide/RNAV Requirements.

Q:  In order to be assigned RNAV PTP, do you file RNVE99 or RNVE2? 
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? 
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. 

Q:  We have seen examples of both E1 and E2 in the NAV/RNV string of an FPL; can E1 be filed and will it be shown as E1?
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"? 
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).  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.

Q:  Does ICAO FPL Item 18 have a character limitation? Air Navigation Service Providers (ANSP) have varying requirements.
A: ICAO Doc 4444 does not limit the number of characters in Item 18; Host/ERAM will handle FPLs with any/all ANSP-required data. FAA is aware the Eurocontrol/CFMU flight plan system will reject an FPL with:

• Information in Optional fields b/c of Item 3; and/or
• More than 20 characters in Item 18 after “NAV/”, a problem for those needing to file RNAV/RNP

   information for multiple ANSPs.

Q:  Does use of ICAO Item 18 solve the current “pass-back” problem wherein RNAV-equipped aircraft are taken off an RNAV route by a subsequent Air Route Traffic Control Center (ARTCC) because the equipment suffix presented to the controller does not indicate RNAV capability?
A: The problem described is related to a component of the NAS Host system, and will occur less frequently at facilities which have completed the transition to ERAM. In the interim, it may lessen the problem you described but it may not completely solve it.

Q:  What process do we use to modify Item 18?
A:  Filers should use an ICAO CHG message.  Please refer to guidance with examples on this website at Filing Instructions/Reference Guide/Message ACK/REJ. 

Q:  Can “RMK/” be filed anywhere in Item 18 of an ICAO FPL? 
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.

Q:  Will FAA guidance change regarding information currently filed in the Remarks section of a NAS FP?
A:  No. 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”).

Q:  Host rejects Item 19 data if filed in the ICAO FPL.  Will ERAM do the same?
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:   Is there a list of critical DME facilities?
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.  It is the operator's responsibility to monitor the requirements/availability of infrastructure supporting procedures for each location to which aircraft are dispatched.

Q:  Is ETMS able to process early intent filing in the new format?
A:  Yes.  ETMS is able to process early intent messages. 

Q:  What is the difference between “preferred routes” and “preferential routes”?
A: “Preferential routes” are RNAV and/or conventional departure and arrival routes that may be automatically assigned by Host/ERAM.  These routes are assigned based on equipment and other data filed in the ICAO FPL.  “Preferred routes” are routes described in Airport/Facility Directories (AFD) intended to guide route planning and better provide for efficient departure, en route and arrival air traffic service.  These routes can be filed/assigned to filers of either a NAS FP or an ICAO FPL.

Q:  Do filing requirements change for automatic assignment of Preferential Departure Arrival Routes (PDAR) and Preferred Arrival Routes (PAR)?
A:  No.  ERAM will process consistent with current Host procedures.  NAS FPs will only qualify  for conventional routes, while FPLs will qualify for either conventional or RNAV routes. 

Q:  Will FAA documents relating to ICAO FPLs be updated?
A:  Please refer to guidance on this website at Filing Instructions and at Filing Instructions/Reference Guide/Domestic ICAO FPL.