The proposal to amend the ICAO flight plan provisions was notified 25 May 2007 via State Letter AN13/2.5 07/35.

When the proposal was approved, after some changes, notification was provided via State Letter AN 13/2.1-08/50 dated 25 June 2008. This State Letter required States to implement the amendment by 15 November 2012 or publish any differences as of 15 November 2012.

Followed up by State Letter AN 13/2.1 – 09/9 dated 6 February 2009 which provided guidelines for the implementation of the amendment and AN 13/2-2010/31 dated 29 March 2010 which provided information concerning the Flight Plan Implementation Tracking System (FITS).

FPL 2012 Workshop – Batumi, Georgia 20-22 September 2011

The amendment arose out of the work of the Flight Plan Study Group, which proposed updates to the ICAO Model Flight Plan form (Appendix 2 to the PANS-ATM). Supporting changes were made to Appendix 3 (ATS Messages). There were also changes to some of the provisions related to the filing and handling of flight plans.

2

3

Detailed description of how to access the information on the ICAO EUR/NAT website is provided on the back of the Agenda along with a description of how to access the CFMU documentation related to the FPL 2012 implementation. Also included is a list of Item 18 indicators and flight data message types.

4

Chapter 4, General Provisions for Air Traffic Services, 4.4 – Flight Plan

(new) Note 1 – Failure to adhere to the provisions of Appendix 2 or any constraint identified in relevant AIPs may result in data being rejected, processed incorrectly or lost.

5

Filed Flight Plan (FPL) messages

11.4.2.2.2 – FPL messages should be transmitted immediately after the filing of the flight plan. If a flight plan is filed more than 24 hours in advance of the EOBT of the flight to which it refers, the date of the flight departure shall be inserted in Item of the flight plan.

Previously – the flight plan would be held in abeyance until it would not be necessary to insert the date of the flight.

Modification (CHG) messages

11.4.2.2.4 A CHG message shall be transmitted when any change is to be made to basic flight plan data contained in previously transmitted FPL or RPL data. The CHG message shall be sent to those recipients of basic flight plan data which are affected by the change.

NEW TEXT: Relevant revised basic flight plan data shall be provided to suchNEW TEXT: Relevant revised basic flight plan data shall be provided to such affected entities not previously having received this.

DOF – a DLA message is not sufficient if the delay results in the intended date of flight changing.

6

(new) Note 2.— Air traffic services data systems may impose communications or processing constraints on information in filed flight plans. Possible constraints may, for example, be limits with regard to item length, number of elements in the route item or total flight plan length. Significant constraints are documented in the relevant Aeronautical Information Publication.

7

I if it is intended that the entire flight will be operated under the IFR

V if it is intended that the entire flight will be operated under the VFR

Y if the flight initially will be operated under the IFR, followed by one or more subsequent changes of flight rules

Z if the flight initially will be operated under the VFR, followed by one or more subsequent changes of flight rules

Specif in Item 15 the point or points at hich a change of flight r les is plannedSpecify in Item 15 the point or points at which a change of flight rules is planned.

8

9

Note 1.— If the letter S is used, standard equipment is considered to be VHF RTF, VOR and ILS, unless another combination is prescribed by the appropriate ATS authority.

Note 2.— If the letter G is used, the types of external GNSS augmentation, if any, are specified in Item 18 following the indicator NAV/ and separated by a space.

Note 3.—(if J1 inserted) See RTCA/EUROCAE Interoperability Requirements Standard For ATN Baseline 1 (ATN B1 INTEROP Standard – DO-280B/ED-110B) for data link services air traffic control clearance and information/air traffic control communications management/air traffic control microphone check.

Note 4.—If the letter R is used, the performance based navigation levels that can be met are specified in Item 18 following the indicator PBN/. Guidance material on the application of performance based navigation to a specific the route segment, route or area is contained in the Performance-Based Navigation Manual (Doc 9613).

Note 5.— If the letter Z is used, specify in Item 18 the other equipment carried or other capabilities, preceded by COM/, NAV/ and/or DAT, as appropriate.

Note 6.— Information on navigation capability is provided to ATC for clearance and routing purposes.

10

11

Mention of Doc 7910 is new.

Only new provision is option to insert route point or marker beacon in Item 18 if aircraft has not taken off from the aerodrome.

12

Clarified that same point can be used to indicate change in speed and/or level (rather than speed or level), and the point is where the change is planned to commence.

Mention of Manual on Required Navigation Performance (Doc 9613) is removed

Significant point can be defined as bearing and distance from a reference point rather than just from a NAVAID.

13

Location Indicators – Doc 7910

14

Location Indicators – Doc 7910

Indicator/name/location only of Destination Alternate Aerodromes – no estimated elapsed time .

No more than 2 alternates (no change to this provision)

15

Note.— Use of indicators not included under this item may result in data being rejected, processed incorrectly or lost.

STS – Reason for special handling by ATS PBN – Indication of RNAV and/or RNP capabilities

NAV – Navigation data COM – Communication applications/capabilities

DAT – Data applications/capabilities SUR – Surveillance applications/capabilities

DEP – Name/location departure aerodrome DEST – Name/location destination aerodrome

DOF – Date of Flight REG – Nationality/common mark and registration

EET – Estimated Elapsed Time SEL – SELCAL (Selective Calling) code

TYP – Type(s) of aircraft CODE – aircraft address

DLE – Enroute delay/holding OPR – aircraft operating agency

ORGN – originator of flight plan PER – aircraft performance data (from Doc 8168, Vol 1)

ALTN – Alternate destinations(s) RALT – Enroute Alternate(s)

TALT – Take off Alternate RIF – Route to revised destination

RMK – Remarks

16

17

NAV – Significant data related to navigation equipment, other than specified in PBN/, as required by the appropriate ATS authority. Indicate GNSS augmentation under this indicator, with a space between two or more methods of augmentation, e.g. NAV/GBAS SBAS

COM – communications

DAT – data

SUR – surveillanceSUR surveillance

18

DEP – Name and location of departure aerodrome

DEST – Name and location of destination aerodrome

19

DOF – Date of flight departure

CHG – Modification message

20

REG – The nationality or common mark and registration mark of the aircraft, if different from the aircraft identification in Item 7. For example, when an ICAO designator for the operating agency is used.

EET - Significant points or FIR boundary designators and accumulated estimated elapsed times from take-off to such points or FIR boundaries, when so prescribed on the basis of regional air navigation agreements, or by the appropriate ATS authority. NO CHANGE TO THIS PROVISION

Examples: EET/CAP0745 XYZ0830 EET/EINN0204

21

SEL – selective calling

TYP - Type(s) of aircraft, preceded if necessary without a space by number(s) of aircraft and separated by one space, if ZZZZ is inserted in Item 9. Example: TYP/2F15 5F5 3B2

22

CODE - Aircraft address (expressed in the form of an alphanumerical code of six hexadecimal characters) when required by the appropriate ATS authority. Example: “F00001” is the lowest aircraft address contained in the specific block administered by ICAO. NO CHANGE TO THIS PROVISION

DLE - Enroute delay or holding, insert the significant point(s) on the route where a delay is planned to occur, followed by the length of delay using four figure time in hours and minutes (hhmm).

Example: DLE/MDG0030

23

OPR - ICAO designator or name of the aircraft operating agency, if different from the aircraft identification in item 7.

ORGN - The originator’s 8 letter AFTN address or other appropriate contact details, in cases where the originator of the flight plan may not be readily identified, as required by the appropriate ATS authority. Note.— In some areas, flight plan reception centres may insert the ORGN/ identifier and originator’s AFTN address automatically.

PER - Aircraft performance data, indicated by a single letter as specified in the Procedures for Air Navigation Services — Aircraft Operations (PANS-OPS, Doc 8168), Volume I — Flight Procedures, if so prescribed by the appropriate ATS authority. (Aircraft Category A, B, C, D, E or H)

24

ALTN - Name of destination alternate aerodrome(s), if ZZZZ is inserted in Item 16. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/ above.

RALT - ICAO four letter indicator(s) for en-route alternate(s), as specified in Doc 7910, Location Indicators, or name(s) of en-route alternate aerodrome(s), if no indicator is allocated. For aerodromes not listed in the relevant Aeronautical I f ti P bli ti i di t l ti i LAT/LONG b i d di tInformation Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/ above.

TALT - ICAO four letter indicator(s) for take-off alternate, as specified in Doc 7910, Location Indicators, or name of take-off alternate aerodrome, if no indicator is allocated. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point as described in DEP/ abovenearest significant point, as described in DEP/ above.

25

RIF - The route details to the revised destination aerodrome, following by the ICAO four-letter location indicator of the aerodrome. The revised route is subject to reclearance in flight.

Examples: RIF/DTA HEC KLAX RIF/ESP G94 CLA YPPH

RMK/ Any other plain language remarks when required by the appropriate ATS authority or deemed necessary. If special codes are created for regional or State application, they should be notified in AIP or other appropriate documents.

26

Box 13 contains the departure aerodrome and time; details concerning the SPL message are in Appendix 3

G – Supplementary Data At

The name and appropriate contact details of entity where information normally provided under Item 19 of the FPL is kept readily available and can be supplied without delay.

27

Entry for Field 16 used to refer only to “alternate aerodromes”

Point – Used to be only 2 or 3 characters for NAVAID, now 2 to 5 characters for significant point. Used to mention only degrees magnetic for the bearing, now includes degrees true.

28

29

N – no COM/NAV/approach aid equipment for the route to be flown is carried, or is unserviceable

30

Location Indicators – Doc 7910

13a – used to be terminated in CHG, CNL, ARR and RQS messages too.

CPL – Current Flight Plan

EST - Estimate

CDN - Coordination

ACP – Acceptance

CHG - Modification

CNL - Cancellation

ARR - Arrival,

RQS – Request Supplementary Flight Plan

RQP – Request Flight Plan

31

13b – Amendment used to state that EOBT would be included in messages “transmitted before departure” – this is not correct for ARR and RQS messages, so the amendment was corrected to remove the words “transmitted before departure”

EOBT used to be included only in FPL and DLA messages transmitted before departure

FPL – Filed Flight Plan

DLA – DelayDLA Delay

EOBT in RQP – no change to this provision

No change to actual time of departure in ALR, DEP and SPL messages

ALR – Alerting

DEP – Departure

SPL – Supplementary Flight PlanSPL Supplementary Flight Plan

14a – used to refer to designated point, for example VOR

32

RQP (Request Flight Plan) was missing in current document, too

33

16a – Location Indicators – Doc 7910, Note now refers to name AND LOCATION to be inserted in Field 18, if ZZZZ in Field 16

16b - Total estimated elapsed time – NO CHANGE TO THIS PROVISION

16c – Note now refers to name AND LOCATION

34

Amendment added a Note to refer to ZZZZ being shown in Field Type 18; this was incorrect. The current provision, of being able to add ZZZZ in 17a will be kept and 17c will continue to be used to provide the name and location.

35

CHG – Modification

DLA – Delay

CNL – Cancellation

DEP – Departure

RQP – Request Flight Plan

RQS – Request Supplementary Flight Plan

36

Updates arising from Amendment 1, such as field 10 now referring to Equipment and Capabilities instead of just equipment, or revise the explanations and order of items, etc.

Some updates are to make the content appear more current – for example, referring to A320 rather than DC9.

37

38