FAA ICAO Flight Planning Interface Reference Guide version 2

Faa Icao Flight Planning Interface Reference Guide Version 2-PDF Download

  • Date:31 Jul 2020
  • Views:3
  • Downloads:0
  • Pages:73
  • Size:814.49 KB

Share Pdf : Faa Icao Flight Planning Interface Reference Guide Version 2

Download and Preview : Faa Icao Flight Planning Interface Reference Guide Version 2


Report CopyRight/DMCA Form For : Faa Icao Flight Planning Interface Reference Guide Version 2


Transcription:

FAA ICAO Flight Planning Interface Reference Guide. Table of Contents,1 Introduction 7,1 1 Scope 7,1 2 Background 7. 1 3 FAA FPL Services 8,1 4 Document Organization 8. 2 Operational Use of Flight Planning Messages 8,2 1 Initial FPL Filing 8. 2 1 1 Flights Remaining Entirely within U S Domestic Airspace 8. 2 1 2 Flights Leaving U S Domestic Airspace 9, 2 1 3 Flights Entering U S Domestic Airspace from or Through Canada 9. 2 1 4 Flights Entering U S Domestic Airspace Except from Canada 9. 2 1 5 Addressing an FPL Message 9,2 1 6 Aircraft Identification 9.
2 1 7 Optional Message Number 10, 2 1 8 FPLs with the Same Aircraft Identification 10. 2 2 Changing an FPL after Filing 11,2 2 1 Eligibility to Change FPL Data 11. 2 2 2 Identifying an FPL to be Changed 11,2 2 3 Message Types Used to Change an FPL 12. 3 Automated Filing of ICAO Format Flight Planning Messages 12. 3 1 General Message Construction 12,3 1 1 Header 12. 3 1 2 Message Syntax 12,3 1 3 Message Content 14,3 2 Filed Flight Plan FPL Message 15.
3 2 1 FPL Contents 15,3 2 2 FPL Examples 21,3 3 Modification CHG Message 29. 3 3 1 CHG Contents 30,3 3 2 CHG Examples 32,3 4 Delay DLA Message 34. 11 15 2012 DRAFT, FAA ICAO Flight Planning Interface Reference Guide. 3 4 1 DLA Contents 34,3 4 2 DLA Examples 36,3 5 Cancellation CNL Message 36. 3 5 1 CNL Contents 36,3 5 2 CNL Examples 38,3 6 ACK Responses 38.
3 6 1 Use of Optional Elements in Field 3 Message Type to Identify a Filed Flight. Plan FPL 39,3 6 2 Examples of ACK Messages 40,3 7 REJ Response 41. 3 7 1 Examples of REJ Messages 42,3 7 2 Reason for a REJ Message 44. 4 FAA Guidance for Equipment and Capabilities 51,4 1 Reduced Vertical Separation Minimum RVSM 51. 4 2 Navigation Capability 51,4 3 Communications Data Link Capability 51. 4 4 Global Navigation Satellite System GNSS 52,4 5 Performance Based Navigation 52.
4 5 1 North Atlantic Minimum Navigation Performance Specification MNPS 52. 4 5 2 Oceanic RNP10 and 50 NM lateral or 50 NM longitudinal separation 52. 4 5 3 Oceanic RNP4 and 30 30 separation 53,4 5 4 Domestic Area Navigation RNAV Capability 53. 4 5 5 Domestic U S RNAV 1 Capability 53,4 5 6 Domestic U S RNP Capability 54. 4 5 7 General Specification of RNAV Capability for FAA domestic route. assignment 54,5 Reference Material 55,5 1 Acronyms 55. 5 2 References 58,5 3 ARTCC Four letter Location Identifiers 59. Attachments,11 15 2012 DRAFT, 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, FAA ICAO Flight Planning Interface Reference Guide. Change History,Change Description Action Date Version. Initial Release 12 20 07 1 1,Add change table Insert table on pg 3 1 15 08 1 2. Change EET data filing Replace Section 2 1 1 para 2 with new. instructions for flights para,remaining entirely within.
U S domestic airspace, Add specific information Section 3 1 2 insert para 4 Message 4 30 08 1 3. 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 3 3 2 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 2 0 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 2 0. in reviews 2 13 12,11 15 2012 DRAFT, FAA ICAO Flight Planning Interface Reference Guide. Change Description Action Date Version,Released 2 0 Version for Updates 6 5 12 2 0. ICAO Amendment 1 FPL 1 Various editorial cleanup,2 Clarified requirement for Field 8b. 3 Added requirements for ADS B,4 Clarified some items where.
behavior is different for the en,route and oceanic systems. Released 3 0 Version with Updates 11 15 12 2 1, 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, FAA ICAO Flight Planning Interface Reference Guide. 1 Introduction, This document provides references for filing International Civil Aviation Organization ICAO. 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 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,1 2 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. 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 non U S 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. equivalents which is an issue for flights that traverse another country s airspace one that. follows ICAO conventions,11 15 2012 DRAFT, 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. 1 3 FAA FPL Services,FAA 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 nominally. 30 minutes and, 3 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 4 Document Organization, Section 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 flight. planning message and its associated fields, Section 4 identifies FAA and ICAO documents defines terms and acronyms and provides. detailed reference material for field content, Section 5 provides suggested guidelines for user flight planning interfaces. 2 Operational Use of Flight Planning Messages,2 1 Initial FPL Filing. 2 1 1 Flights Remaining Entirely within U S Domestic Airspace. File an ICAO FPL if your flight will remain entirely within U S domestic airspace1 and the. operator desires application of RNAV routes File only with the Air Route Traffic Control. Center ARTCC containing the departure airport flight information is automatically passed to. each ARTCC along the route of flight FPLs filed with any other ARTCCs along the route may. create 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 domestic. airspace ERAS will accept EET data however it will not process that data if filed. U S Domestic Airspace In this document U S domestic airspace includes that airspace over the 48 contiguous. United States and Puerto Rico It does not include any foreign or international airspace e g oceanic airspace. controlled by Oakland New York and or Anchorage ARTCCs. 11 15 2012 DRAFT, FAA ICAO Flight Planning Interface Reference Guide.
Note 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 2 Flights Leaving U S Domestic Airspace, File an FPL for any flight leaving U S domestic airspace For the U S domestic portion of the. flight file only with the ARTCC containing the departure airport Flight information is. automatically passed to each ARTCC along the route of flight within U S airspace FPLs filed. with any other U S domestic ARTCC along the route may be discarded or rejected by. subsequent ARTCCs, Provide EET data starting with the first Oceanic or non U S Flight Information Region FIR in. accordance 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 3 Flights 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 Canadian. Automated Air Traffic System CAATS to ERAS prior to boundary crossing FPLs addressed. to any U S domestic ARTCC along the route may create processing problems including. duplicate flight plans and or flight plan rejections by downstream facilities. 2 1 4 Flights 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 in. the route of flight FPLs addressed to any other U S domestic ARTCC along the route may. create processing problems for downstream facilities They may also be discarded or rejected by. those ARTCCs,2 1 5 Addressing an FPL Message, Guidance on addressing flight plans for domestic or international flight planning can be found in. the Aeronautical Information Publication AIP ENR Section 1 11 AFTN addresses for sending. FPLs to ERAS are documented in ICAO Doc 8585 Designators for Aircraft Operating. Agencies Aeronautical Authorities and Services The list of relevant addresses is also found in. section 5 3 Identifying a Flight in an FPL,2 1 6 Aircraft Identification.
A 2 7 character aircraft identification is required in Item 7 of an FPL in compliance with ICAO. Doc 4444 and ICAO Annex 7 Aircraft Nationality and Registration Marks with the following. 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 the. FPL was sent so they can ensure acceptance in ERAS FPLs filed with oceanic. automation are accepted is the aircraft identification starts with a number. 11 15 2012 DRAFT, FAA ICAO Flight Planning Interface Reference Guide. 2 1 7 Optional Message Number, FAA allows use of an Optional Message Number in Item 3 Field 3b for routing of ACK REJ. messages see Section 3 6 for guidance on ACK REJ messages When provided this Optional. Message Number allows ERAS to distinguish between multiple flights with the same aircraft. identification 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 the. filer 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 is. FAA ICAO Flight Planning Interface Reference Guide Version 2 1 November 15 2012 Air Traffic Organization En Route and Oceanic Services ATO E Technical Performance Support Group JE 36A Federal Aviation Administration FAA ICAO Flight Planning Interface Reference Guide 11 15 2012 DRAFT 2 Table of Contents 1 Introduction 7 1 1 Scope 7 1 2 Background 7 1 3 FAA FPL

Related Books