FAA ICAO Flight Planning Interface Reference Guide Version 2
En Route and Oceanic ServicesAeronautical Information and Flight Planning EnhancementsFAA ICAO Flight Planning Interface Reference GuideVersion 2.1Federal AviationAdministrationNovember 15, 2012Air Traffic Organization En Route and Oceanic Services, ATO-ETechnical Performance Support Group, AJE- 36
FAA ICAO Flight Planning Interface Reference GuideTable of Contents1.Introduction . 71.1Scope . 71.2Background . 71.3FAA FPL Services . 81.4Document Organization . 82.Operational Use of Flight Planning Messages . 8Initial FPL Filing . 82.12.1.1Flights Remaining Entirely within U.S. Domestic Airspace . 82.1.2Flights Leaving U.S. Domestic Airspace . 92.1.3Flights Entering U.S. Domestic Airspace (from or Through Canada) . 92.1.4Flights Entering U.S. Domestic Airspace (Except from Canada). 92.1.5Addressing an FPL Message . 92.1.6Aircraft Identification . 92.1.7Optional Message Number . 102.1.8FPLs with the Same Aircraft Identification . 102.23.Changing an FPL after Filing . 112.2.1Eligibility to Change FPL Data . 112.2.2Identifying an FPL to be Changed . 112.2.3Message Types Used to Change an FPL . 12Automated Filing of ICAO-Format Flight Planning Messages . 123.1General Message Construction . 123.1.1Header. 123.1.2Message Syntax . 123.1.3Message Content. 143.2Filed Flight Plan (FPL) Message . 153.2.1FPL Contents . 153.2.2FPL Examples. 213.3Modification (CHG) Message . 293.3.1CHG Contents . 303.3.2CHG Examples . 323.411/15/2012Delay (DLA) Message . 34DRAFT2
FAA ICAO Flight Planning Interface Reference Guide3.4.1DLA Contents . 343.4.2DLA Examples . 363.5Cancellation (CNL) Message . 363.5.1CNL Contents . 363.5.2CNL Examples . 383.6ACK Responses. 383.6.1Use of Optional Elements in Field 3 (Message Type), to Identify a Filed FlightPlan (FPL). . 393.6.23.74.Examples of ACK Messages . 40REJ Response. 413.7.1Examples of REJ Messages . 423.7.2Reason for a REJ Message . 44FAA Guidance for Equipment and Capabilities. 514.1Reduced Vertical Separation Minimum (RVSM) . 514.2Navigation Capability. 514.3Communications/Data Link Capability . 514.4Global Navigation Satellite System (GNSS) . 524.5Performance Based Navigation . 524.5.1North Atlantic Minimum Navigation Performance Specification (MNPS) . 524.5.2Oceanic RNP10 and 50 NM lateral or 50 NM longitudinal separation . 524.5.3Oceanic RNP4 and 30/30 separation . 534.5.4Domestic Area Navigation (RNAV) Capability . 534.5.5Domestic U.S. RNAV 1 Capability . 534.5.6Domestic U.S. RNP Capability . 544.5.7General Specification of RNAV Capability for FAA domestic routeassignment . 545.Reference Material . 555.1Acronyms . 555.2References . 585.3ARTCC Four-letter Location Identifiers. 59Attachments11/15/2012DRAFT3
FAA ICAO Flight Planning Interface Reference GuideAttachment 1. Route (Field 15) Additions . 36Attachment 2. Other Information (Item 18) Additions . 4011/15/2012DRAFT4
FAA ICAO Flight Planning Interface Reference GuideChange HistoryChange DescriptionActionInitial ReleaseAdd change table;Insert table on pg. 3;Change EET/ data filinginstructions for flightsremaining entirely withinU.S. domestic airspaceReplace Section 2.1.1, para. 2, with newpara.Add specific informationabout allowable charactersin messagesSection 3.1.2, insert para. 4 MessageSyntax, Allowable Characters inaccordance with ICAO Annex 10,Aeronautical Communications.CHG example did notinclude a complete Field 15(Fields 15a/b missing);Add “Reserved” route-toroute transition informationRevised document toreflect changes associatedwith ICAO /112.0 draft12/21/112.0Replace example in Section 3.3.2, para.2, with new exampleReplace “Reserved” para. with new 3rdpara. in Attachment 1, Section 2See comments in document.Updated filing guidance tobe consistent with otherFAA documents & addedreferences.Corrected Items identifiedin reviews11/15/2012Final draft review version.2/13/12DRAFT5
FAA ICAO Flight Planning Interface Reference GuideChange DescriptionReleased 2.0 Version forICAO Amendment 1 22.11. Various editorial cleanup2. Clarified requirement for Field 8b3. Added requirements for ADS-Bfiling4. Clarified some items wherebehavior is different for the enroute and oceanic systemsReleased 3.0 Version withrewrite to comply withICAO requirements as ofNovember 15th 2012Updates:1. Added guidance on addressingdomestic and international flightplans2. Added guidance on messageprocessing and response3. Added table of error messages andtheir resolution4. Added sample flight plans5. Clarified oceanic guidance onRNP10 and 50NM separation11/15/2012DRAFT6
FAA ICAO Flight Planning Interface Reference Guide1. Introduction1.1ScopeThis document provides references for filing International Civil Aviation Organization (ICAO)Filed Flight Plans (FPL) and associated flight planning messages for flights within United Statesdomestic airspace. The information provided in this document augments instructions found inthe ICAO Procedures for Air Navigation Services – Air Traffic Management, Document 4444(ICAO Doc. 4444), including Amendment 1 effective 11/15/2012, and incorporates publishedsupplementary requirements, instructions and guidelines for proper filing of FPLs with theFederal Aviation Administration’s (FAA) En Route Automation System (ERAS).This document provides instructions for filing ICAO flight planning messages within ERAS toensure message acceptance and the most efficient automation processing.This document describes interface requirements for sending ICAO-format flight planningmessages via Aeronautical Fixed Telecommunications Network (AFTN) to ERAS. It identifiesthe 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 intendedaudiences are flight plan service providers, military organizations, and airlines in the direct fileprogram that send flight planning messages to ERAS. These flight planning messages include:1. Filed Flight Plan (FPL);2. Modification (CHG);3. Delay (DLA); and4. Cancellation (CNL).1.2BackgroundThe ability to fly a Performance Based Navigation (PBN) route depends on both the equipage ofthe aircraft and the capability of the crew. The availability of a PBN route depends on currentairspace configuration and compatibility of the route with current Air Traffic Control (ATC)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, operatorsfiling a Domestic Flight Plan (FAA Form 7233-1) will be ineligible for assignment of PBNroutes, including Area Navigation (RNAV) departures and arrivals. FAA Form 7233-1 may notbe used for flights that will enter oceanic or non-U.S. airspace, or when PBN procedures arerequested, for the following reasons:1. Incorrect assumptions may be made about flights filing Global Navigation SatelliteSystem (GNSS) or PBN with respect to navigation capability; and2. FAA-unique equipment qualifiers cannot always be accurately translated to ICAOequivalents; which is an issue for flights that traverse another country’s airspace (one thatfollows ICAO conventions)11/15/2012DRAFT7
FAA ICAO Flight Planning Interface Reference GuideFAA has resolved these issues by requiring an ICAO-format FPL to be filed, which accuratelyspecifies PBN capability and is compatible with ICAO standards. In addition, the implementedsolution improves the ability for the user to control the type of departure and arrival routeassigned by ERAS. This has been done by providing the means to specify PBN capability byphase of flight in an FPL, and adapting computer assigned routes, based on filed ICAOequipment qualifiers and navigation capabilities filed in ICAO Field 18, NAV/RNV.1.3FAA FPL ServicesFAA FPL services include the ability to:1. File an FPL up to 24 hours in advance of the filed Estimated Off-Blocks Time (EOBT);2. Make modifications (CHG/DLA) to that FPL up to a set time before EOBT (nominally30 minutes); and3. Cancel a previously filed FPL up to a set time before EOBT (nominally 30 minutes).Flight plan filer addresses adapted within ERAS will receive acknowledgement messages (i.e.,acceptance (ACK) and/or rejection (REJ)) for each flight planning message sent to ERAS.1.4Document OrganizationSection 2 describes the operational use of FPL messages, including rules and limitations for use,expected responses and use by ATC.Section 3 describes the format and content accepted by the ERAS for each type of flightplanning message and its associated fields.Section 4 identifies FAA and ICAO documents, defines terms and acronyms, and providesdetailed reference material for field content.Section 5 provides suggested guidelines for user flight planning interfaces.2. Operational Use of Flight Planning Messages2.1Initial FPL Filing2.1.1Flights Remaining Entirely within U.S. Domestic AirspaceFile an ICAO FPL if your flight will remain entirely within U.S. domestic airspace1 and theoperator desires application of RNAV routes. File only with the Air Route Traffic ControlCenter (ARTCC) containing the departure airport; flight information is automatically passed toeach ARTCC along the route of flight. FPLs filed with any other ARTCCs along the route maycreate duplicate flight plans and/or unnecessary flight plan rejections by downstream facilities.ERAS does not require EET/ data in an ICAO FPL for the route portion in U.S. domesticairspace. ERAS will accept EET/ data; however, it will not process that data if filed.1U.S. Domestic Airspace: In this document U.S. domestic airspace includes that airspace over the 48 contiguousUnited States and Puerto Rico. It does not include any foreign or international airspace (e.g. oceanic airspacecontrolled by Oakland, New York and/or Anchorage ARTCCs).11/15/2012DRAFT8
FAA ICAO Flight Planning Interface Reference GuideNote: U.S. domestic airspace does not include any foreign or international airspace (e.g.oceanic airspace controlled by ARTCCs at Oakland, New York and/or Anchorage).2.1.2Flights Leaving U.S. Domestic AirspaceFile an FPL for any flight leaving U.S. domestic airspace. For the U.S. domestic portion of theflight, file only with the ARTCC containing the departure airport. Flight information isautomatically passed to each ARTCC along the route of flight within U.S. airspace. FPLs filedwith any other U.S. domestic ARTCC along the route may be discarded or rejected bysubsequent ARTCCs.Provide EET/ data starting with the first Oceanic or non-U.S. Flight Information Region (FIR) inaccordance with (IAW) guidance in ICAO Doc. 4444.Note: If a flight leaves U.S. domestic airspace and later re-enters U.S. domestic airspace,the reentry portion of the flight should be handled per Section 2.1.3, and 2.1.4 below.2.1.3Flights Entering U.S. Domestic Airspace (from or Through Canada)Do not address the FPL to any U.S. domestic facility when entering U.S. domestic airspace from,or through Canada. Current flight plan data will be automatically forwarded from the CanadianAutomated Air Traffic System (CAATS) to ERAS, prior to boundary crossing. FPLs addressedto any U.S. domestic ARTCC along the route may create processing problems, includingduplicate flight plans and/or flight plan rejections by downstream facilities.2.1.4Flights Entering U.S. Domestic Airspace (Except from Canada)An FPL is required when entering U.S. domestic airspace from international or oceanic airspace,except from or through Canada. The FPL should be addressed to the first U.S. domestic FIR inthe route of flight. FPLs addressed to any other U.S. domestic ARTCC along the route maycreate processing problems for downstream facilities. They may also be discarded or rejected bythose ARTCCs.2.1.5Addressing an FPL MessageGuidance on addressing flight plans for domestic or international flight planning can be found inthe Aeronautical Information Publication (AIP) ENR Section 1.11. AFTN addresses for sendingFPLs to ERAS are documented in ICAO Doc. 8585, Designators for Aircraft OperatingAgencies, Aeronautical Authorities and Services. The list of relevant addresses is also found insection 5.3.Identifying a Flight in an FPL2.1.6Aircraft IdentificationA 2 - 7 character aircraft identification is required in Item 7 of an FPL in compliance with ICAODoc. 4444 and ICAO Annex 7, Aircraft Nationality and Registration Marks, with the followingexception:Exception: For FPLs filed with ERAS, if the aircraft identification starts with a number,the FPL will be rejected. If this occurs, contact Flight Data at the ARTCC to which theFPL was sent so they can ensure acceptance in ERAS. (FPLs filed with oceanicautomation are accepted is the aircraft identification starts with a number).11/15/2012DRAFT9
FAA ICAO Flight Planning Interface Reference Guide2.1.7Optional Message NumberFAA allows use of an Optional Message Number in Item 3, Field 3b, for routing of ACK/REJmessages (see Section 3.6 for guidance on ACK/REJ messages). When provided, this OptionalMessage Number allows ERAS to distinguish between multiple flights with the same aircraftidentification, departure point and destination. Field 3b consists of three parts and shall include:Part 1. The three-letter National Data Interchange Network (NADIN) address where thefiler would like the ACK/REJ message sent, followed by an oblique stroke (XXX/);Part 2. The four-letter location identifier (LOCID) of the ARTCC to which the FPL isaddressed by the filer (KZXX); andNote: Allowable LOCIDs can be found in Section 5.3.Part 3. A three-digit sequential message number assigned by the filer (ddd).Example: COA/KZHU004 is message #004 addressed to Houston ARTCC withACK to Continental AirlinesMessage numbers should be used sequentially, 001 through 999, before restarting the messagenumbering sequence again at 001. Do not restart the message numbering sequence based on timeof day, e.g., restart at 001 at 0000Z, or there could be ambiguity when a CHG, CNL or DLAmessage is received if the FAA automation system is storing multiple FPLs with the samemessage number.2.1.8FPLs with the Same Aircraft IdentificationTwo or more FPLs filed to the same ARTCC with the same aircraft identification can beaccepted under some circumstances; but often cause problems. The processing rules for suchflight plans are summarized in Table 2-2-1.11/15/2012DRAFT10
FAA ICAO Flight Planning Interface Reference GuideTable 2-2-1. Duplicate Flight Plan RulesScenarioRecommendationsIssuesFlight withmultiplestopoversFile each leg of the flight in aseparate FPL as required.None. Each FPL will have a differentdeparture/destination and will thus bedistinguishable as separate legs by ERAS.MultipleFPLs filed forthe sameflightDo not file multiple FPLs withthe same departure, destinationand departure time.If departure, destination, departure time androute are ide
FAA ICAO Flight Planning Interface Reference Guide 11/15/2012 DRAFT 8 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
ICAO Doc 9184, Airport Planning Manual, Parts 1 to 3; ICAO Doc 9261, Heliport Manual; ICAO Doc 9332, Manual on the ICAO Bird Strike Information System (IBIS); ICAO Doc 9365, Manual of All-Weather Operations; ICAO Doc 9426, Air Traffic Services Planning Manual; ICAO Doc 9476, Manual of Surface Movement Guidance and Control Systems (SMGCS); ICAO .
FAA-H-8083-3 Airplane Flying Handbook FAA-H-8083-6 Advanced Avionics Handbook FAA-H-8083-9 Aviation Instructor's Handbook FAA-H-8083-15 Instrument Flying Handbook FAA-H-8083-16 Instrument Procedures Handbook FAA-H-8083-25 Pilot's Handbook of Aeronautical Knowledge FAA-H-8083-30 Aviation Maintenance Technician Handbook— General FAA-H-8083 .
ederal Aviation Administration 10 Flight Planning Information FAA Website FAA Form 7233-4 ICAO Doc 7030 (Link to Purchase) Useful Links ICAO Flight Planning Reference Guide Aeronautical Information Manual (AIM) Section 1, Para- graph 5-1-9 Flight Plan Filing (SKYbrary) Filing for data link operations (See AC 90-117) Flight Planning for Oceanic and Remote Continental Air-
ICAO Doc 9683, Human Factors Training Manual; ICAO Doc 9734, Establishment and Management of a State‘s Safety Oversight System; ICAO Doc 9760, Airworthiness Manual, Volumes I and II; ICAO Doc 9774, Manual on Certification of Aerodromes; ICAO Doc 9815, Manual on Laser Emitters and Flight Safety; ICAO
From: Vantrees, Stephen (FAA) stephen.vantrees@faa.gov Sent: Thursday, March 19, 2020 8:17 AM To: White, Peter (FAA) peter.white@faa.gov Cc: Vantrees, Stephen (FAA) stephen.vantrees@faa.gov Subject: Fw: Actions from 3/12/2020 Meeting: AVS/ATO Executive Coordination on NASA/General Atomics SIO
The FAA will implement flight plan filing for civil aircraft using a format that aligns with International Civil Aviation Organization (ICAO) standards. The new format appears on FAA Form 7233-4, FAA International Flight Plan (Revision 7/2015). Aligning our flight plan
FAA-H-8083-9 Aviation Instructor’s Handbook FAA-S-8081-4 Instrument Rating Practical Test Standards FAA-S-8081-12Commercial Pilot Practical Test Standards FAA-S-8081-14Private Pilot Practical Test Standards FAA-H-8083-15Instrument Flying Handbook FAA/AS
Core 6 – Equality and Diversity . Status Core – this is a key aspect of all jobs and of everything that everyone does. It underpins all dimensions in the NHS KSF. Levels 1 Act in ways that support equality and value diversity . 2. Support equality and value diversity . 3. Promote equality and value diversity
