FAA ICAO Flight Planning Interface Reference Guide …

1 En Route and Oceanic Services aeronautical Information and Flight Planning Enhancements FAA icao Flight Planning Interface Reference Guide Version Federal Aviation Administration November 15, 2012. Air Traffic Organization En Route and Oceanic Services, ATO-E. Technical Performance Support Group, AJE- 36. FAA icao Flight Planning Interface Reference Guide Table of Contents 1. Introduction .. 7. Scope .. 7. Background .. 7. FAA FPL Services .. 8. Document Organization .. 8. 2. Operational Use of Flight Planning Messages .. 8. Initial FPL Filing .. 8. Flights Remaining Entirely within Domestic Airspace .. 8. Flights Leaving Domestic Airspace .. 9. Flights Entering Domestic Airspace (from or Through Canada) .. 9. Flights Entering Domestic Airspace (Except from Canada).

2 9. Addressing an FPL Message .. 9. Aircraft Identification .. 9. Optional Message Number .. 10. FPLs with the Same Aircraft Identification .. 10. Changing an FPL after Filing .. 11. Eligibility to Change FPL Data .. 11. Identifying an FPL to be Changed .. 11. Message Types Used to Change an FPL .. 12. 3. Automated Filing of icao -Format Flight Planning Messages .. 12. General Message Construction .. 12. 12. Message Syntax .. 12. Message 14. Filed Flight Plan (FPL) Message .. 15. FPL Contents .. 15. FPL 21. Modification (CHG) Message .. 29. CHG Contents .. 30. CHG Examples .. 32. Delay (DLA) Message .. 34. 11/15/2012 DRAFT. 2. FAA icao Flight Planning Interface Reference Guide DLA Contents .. 34. DLA Examples .. 36. Cancellation (CNL) Message.

3 36. CNL Contents .. 36. CNL Examples .. 38. ACK 38. Use of Optional Elements in Field 3 (Message Type), to Identify a Filed Flight Plan (FPL).. 39. Examples of ACK Messages .. 40. REJ 41. Examples of REJ Messages .. 42. Reason for a REJ Message .. 44. 4. FAA Guidance for Equipment and 51. Reduced Vertical Separation Minimum (RVSM) .. 51. Navigation 51. Communications/Data Link Capability .. 51. Global Navigation Satellite System (GNSS) .. 52. Performance Based Navigation .. 52. North Atlantic Minimum Navigation Performance Specification (MNPS) .. 52. Oceanic RNP10 and 50 NM lateral or 50 NM longitudinal separation .. 52. Oceanic RNP4 and 30/30 separation .. 53. Domestic Area Navigation (RNAV) Capability .. 53. Domestic RNAV 1 Capability.

4 53. Domestic RNP Capability .. 54. General Specification of RNAV Capability for FAA domestic route assignment .. 54. 5. Reference Material .. 55. Acronyms .. 55. References .. 58. ARTCC Four-letter Location 59. Attachments 11/15/2012 DRAFT. 3. FAA icao Flight Planning Interface Reference Guide Attachment 1. Route (Field 15) Additions .. 36. Attachment 2. Other Information (Item 18) Additions .. 40. 11/15/2012 DRAFT. 4. FAA icao Flight Planning Interface Reference Guide Change History Change Description Action Date Version Initial Release 12/20/07 Add change table; Insert table on pg. 3; 1/15/08 Change EET/ data filing Replace Section , para. 2, with new instructions for flights para. remaining entirely within domestic airspace Add specific information Section , insert para.

5 4 Message 4/30/08 about allowable characters Syntax, Allowable Characters in in messages accordance with icao annex 10, aeronautical Communications. CHG example did not include a complete Field 15 Replace example in Section , para. (Fields 15a/b missing); 2, with new example Add Reserved route-to- Replace Reserved para. with new 3rd route transition information para. in Attachment 1, Section 2. Revised document to See comments in document. 4/5/11 draft reflect changes associated with icao 2012. Updated filing guidance to be consistent with other FAA documents & added references. Corrected Items identified Final draft review version. 12/21/11 in reviews 2/13/12. 11/15/2012 DRAFT. 5. FAA icao Flight Planning Interface Reference Guide Change Description Action Date Version Released Version for Updates: 6/5/12 icao Amendment 1 (FPL 1.)

6 Various editorial cleanup 2012). 2. Clarified requirement for Field 8b 3. Added requirements for ADS-B. filing 4. Clarified some items where behavior is different for the en route and oceanic systems Released Version with Updates: 11/15/12 rewrite to comply with 1. Added guidance on addressing icao requirements as of domestic and international Flight November 15th 2012 plans 2. Added guidance on message processing and response 3. Added table of error messages and their resolution 4. Added sample Flight plans 5. Clarified oceanic guidance on RNP10 and 50NM separation 11/15/2012 DRAFT. 6. FAA icao Flight Planning Interface Reference Guide 1. Introduction Scope This document provides references for filing International Civil Aviation Organization ( icao ).

7 Filed Flight Plans (FPL) and associated Flight Planning messages for flights within United States domestic airspace. The information provided in this document augments instructions found in the icao Procedures for Air Navigation Services Air Traffic Management, Document 4444. ( icao Doc. 4444), including Amendment 1 effective 11/15/2012, and incorporates published supplementary requirements, instructions and guidelines for proper filing of FPLs with the Federal Aviation Administration's (FAA) En Route Automation System (ERAS). This document provides instructions for filing icao Flight Planning messages within ERAS to ensure message acceptance and the most efficient automation processing. This document describes Interface requirements for sending icao -format Flight Planning messages via aeronautical Fixed Telecommunications Network (AFTN) to ERAS.

8 It identifies the standards on which these messages are based, describes FAA-specific content requirements, and identifies data allowed in icao -format messages that is not used by FAA. The intended audiences are Flight plan service providers, military organizations, and airlines in the direct file program that send Flight Planning messages to ERAS. These Flight Planning messages include: 1. Filed Flight Plan (FPL);. 2. Modification (CHG);. 3. Delay (DLA); and 4. Cancellation (CNL). Background The ability to fly a Performance Based Navigation (PBN) route depends on both the equipage of the aircraft and the capability of the crew. The availability of a PBN route depends on current airspace configuration and compatibility of the route with current Air Traffic Control (ATC).

9 Conditions and procedures. The current ERAS uses International Flight Plan (FAA Form 7233-4), Field 10 and Field 18, NAV/RNV data, to determine a Flight 's eligibility for PBN routing. In most cases, operators filing a Domestic Flight Plan (FAA Form 7233-1) will be ineligible for assignment of PBN. routes, including Area Navigation (RNAV) departures and arrivals. FAA Form 7233-1 may not be used for flights that will enter oceanic or airspace, or when PBN procedures are requested, for the following reasons: 1. Incorrect assumptions may be made about flights filing Global Navigation Satellite System (GNSS) or PBN with respect to navigation capability; and 2. FAA-unique equipment qualifiers cannot always be accurately translated to icao .

10 Equivalents; which is an issue for flights that traverse another country's airspace (one that follows icao conventions). 11/15/2012 DRAFT. 7. FAA icao Flight Planning Interface Reference Guide FAA has resolved these issues by requiring an icao -format FPL to be filed, which accurately specifies PBN capability and is compatible with icao standards. In addition, the implemented solution improves the ability for the user to control the type of departure and arrival route assigned by ERAS. This has been done by providing the means to specify PBN capability by phase of Flight in an FPL, and adapting computer assigned routes, based on filed icao . equipment qualifiers and navigation capabilities filed in icao Field 18, NAV/RNV. FAA FPL Services FAA FPL services include the ability to: 1.