European Organisation for the Safety of Air Navigation

Presentation to ICAO WorkshopKiev 28 July – 1 July 2010

EUR Regional Implementation of Flight Plan Amendment 1 for 2012

Andrew.Hill@eurocontrol.int

Version d4

2

1. ICAO has published a State Letter AN 13/2.1-08/50, dated 25 June 2008 announcing changes to the FPL for 15 November 2012.

2. No basic change to FPL format and fields:

3. Changes are to field content.4. FPLs can be filed up to 5 days in advance5. CHG, DLA, CNL, DEP, RQP, RQS shall contain Item

18.

Introduction

(Field 3 – Field 7 – Field 8ab – Field 9ab / c – Field 10a / b – Field 13ab – Field 15ab c – Field 16ab c – Field 18)

3

(FPL-EIN105-IS-B763/H-E3J4M2SRYWX/HB2U2V2G1-ZZZZ1200-N0400F100 DENUT UL610 LAM UL10 BPK UN601 LESTA UP6 MIMKU/M082F320 NATB YAY/N0464F320 N188B YRI/N0462F340 DCT NOTAP180040 DCT TVC PMM5-KORD0700 KATL-STS/ATFMX MARSA FLTCK PBN/A1C3L1 NAV/GBAS SBAS OTHER DAT/FREE TEXT SUR/FREE TEXT DEP/MALAHIDE 5327N00609W DOF/080622 REG/DAISK TYP/2F15 3F5 DLE/NTM0130 ORGN/EBBDZMFP PER/A TALT/EIDW RMK/FREE TEXT)

Some of the New / Modified Elements

New Field or ElementNew or Modified content

Digits in Field 10 a&b

Up to 20 chars in Field 10b

4

Non-Exclusive List: Flight Planning systems of Aircraft Operators Systems used by ATS Reporting Offices to generate FPLs and

associated messages Automated Flight Briefing systems Flight Plan Service Provider systems Flight Data Processing Systems of ATC Centres, Military

Centres and Airports Route Charges systems On-Line Data Interchange (OLDI) Standard ATS Data Exchange presentation (ADEXP) Standard HMI of ATC Controller positions Flight plan data archive systems ICAO Doc.7030

Operational Testing will be essential

Potential Impact on Stakeholder Systems

5

1. The ICAO European Air Navigation Planning Group (EANPG) has invited “all States to support EUROCONTROL to develop an Implementation Plan of the new contents to the ICAO FPL for the ICAO EUR Region in order to ensure the required level of coordination for modifications to the Flight Data Processing Systems".

2. The ICAO Regional Director, Europe and North Atlantic has invited “EUROCONTROL to coordinate and monitor the progress of the Plan to ensure its timely implementation (November 2012)"

Actions at EUR/NAT regional level

6

Organisational Matters

1. The EANPG is the main coordination group for the EUR Region.

2. Eurocontrol has produced an EUR Region Implementation Plan for the 2012 FPL.

3. Eurocontrol ATFCM Operations and Development Sub-Group (ODSG) is responsible for the detailed technical and operational arrangements.

4. A special 2012 FPL Task Force has been formed to discuss technical and operational issues and has held 2 meetings (September 2009 and February 2010). Next meeting is likely to be in the Autumn of 2010 – States which are non-Eurocontrol Members are encouraged to attend.

5. A special meeting for industrial partners was held on 4 March 2010.

7

EUR Implementation Plan

Scope: All IFR or VFR flights conducted fully or partly under ICAO rules in the following area:

A. States in the ‘IFPS Zone’, which receive their IFR flight plan data from the IFPS system operated by EUROCONTROL’s Central Flow Management Unit (CFMU).

Albania, Andorra, Armenia, Austria, Belgium, Bosnia-Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, FYROM, Germany, Greece, Hungary, Ireland, Italy, Lithuania, Luxembourg, Malta, Moldova, Monaco, Montenegro, Morocco, the Netherlands, Norway, Poland, Portugal, Romania, San Marino, Serbia, Slovak Republic, Slovenia, Spain, Sweden, Switzerland, Turkey, Ukraine and United Kingdom.Maastricht UAC is included within this scope.

B. States not in the IFPS Zone. Algeria, Azerbaijan, Belarus, Georgia, Iceland, Israel, Kazakhstan,

Kyrgyzstan, Latvia, Russian Federation, Tajikistan, Tunisia, Turkmenistan, Uzbekistan

8

Approach for all States in the EUR Region

1. Adhere to 00.00 UTC on 15 November 2012 as target date/time for operational deployment.

2. There will be a period of a few days before and after 15 Nov. 2012 when New and Old content FPLs are in the system – should be minimised to avoid confusion.

3. FPL originators for flights all or partly in the EUR Region requested to provide New FPLs no earlier than 12 Nov. 2012, and to achieve complete transition by 00.00 on 15 Nov. 2012.

Note: AFTN group addressing may result in some addressees receiving mixed New/Present FPLs

9

Detection of ‘Present’ or ‘New’ Content FPLs

1. FPL is PRESENT if: In Field 10a, if the Qualifier E, J, M, P, Q is filed. In Field 10b, if the Qualifier D is filed. In Item 18, an entry used for STS/ is not in the allowed list for

NEW. In Item 18, an entry used for PER/ is not A, B, C, D, E, or H.

2. FPL is NEW if: In Field 10a, if any of the following Qualifiers are filed: E1, E2, E3,

J1, J2, J3, J4, J5, J6, J7, M1, M2, M3, P1, P2, P3, P4, P5, P6, or P7. In Field 10b, if any of the following Qualifiers are filed: E, H, L, B1,

B2, U1, U2, V1, V2, O1 or G1. In Item 18, if any of the following Indicators are filed: PBN/, SUR/,

DLE/, ORGN/, or TALT/. In Item 18, if DAT/ contains text other than S, H, V or M

3. Mixed Present and New content cannot be accepted.

10

Approach for all VFR or OAT Flights & for IFR in States outside the IFPS Zone

1. ANSPs in the IFPS Zone receiving pure VFR or OAT FPLs: may receive mixture of Present and New VFR or OAT

FPLs up to 00.00 UTC on 16/11, after 00.00 UTC on 16/11, only New VFR or OAT FPLs

should be received. (even if IFPS translation function requested for IFR/GAT FPLs)

2. ANSPs outside IFPS Zone may receive mixture of Present and New FPLs (VFR

or IFR, OAT or GAT) up to 00.00 UTC on 16/11, after 00.00 UTC on 16/11, only New FPLs should be

received. 

11

Details around 15 Nov. 2012 All VFR or OAT Flights, & IFR in States outside IFPS Zone

8/11 9/11 10/11 11/11 12/11 13/11 14/11 15/11 16/11 17/11 18/11

All AOs requested to start to send New FPLs

All AOs shall only send New FPLs

Some AOs may send New FPLs

ANSPs unable to process New FPLs should only receive Present FPLs

ANSPs only receive New

FPLs

ANSPs able to process New FPLs likely to receive a mixture of Present and New

12

1. IFPUV (off-line test system) will be able to accept New FPLs from June 2011.

2. Operational testing with IFPS before 15 Nov. 2012.3. IFPS will reject any Old content FPLs received from 15

November 2012. 4. IFPS offers possibility to translate from New FPL to Present

FPL thus enabling, within IFPS Zone only:a) flexible migration period for Aircraft Operators;b) fallback or contingency arrangement allowing Air

Navigation Service Providers (ANSPs), to receive Present FPLs until April/May 2013 only.

5. A CFMU parameter will permit each addressee of FPL messages to indicate the date/time from which he wishes to receive New FPLs. By default, parameter set to 12.00 UTC on 16/11/2012.

6. From 10/11/12 to 14/11/12, IFPS will only accept FPLs 24H before the flight.

Deployment Approach for IFR Flights in States in IFPS Zone

13

Details around 15 Nov. 2012 (For IFR GAT Flights in States in IFPS Zone only)

10/11 11/11 12/11 13/11 14/11 15/11 16/11 17/11 18/11

IFPS only accepts FPL 24H before EOBT.

All AOs requested to start to send New FPLs

All AOs shall only send New FPLs

Some AOs may send New FPLs

ANSPs unable to process New FPLs should only receive Present FPLs

IFPS accepts FPLs up to 120H before EOBT.

1. IFPS distributes New FPLs to ANSPs able to process New.2. IFPS translates New FPLs into Present FPLs for ANSPs unable to process New.

ANSPs able to process New FPLs only receive New

IFPS accepts both New and Present FPLs.

IFPS only accepts New FPLs.

ANSPs able to process New FPLs likely to receive a mixture of Present and New

14

CFMU Deployment and Testing

‘Switch 1’ = CFMU Ops acceptance of ‘Old’ & ‘New’, output of “Old only’ or ‘Old + New’

‘Switch 2’ = CFMU Ops acceptance of ‘New’ only, output of “Old only’ or ‘New only’

‘Switch 3’ = CFMU Ops acceptance of ‘New’ only, output of ‘New’ only

‘Switch 2’

Apr/May2012

CFMU 16

‘Switch 1’ ‘Switch 3’

CFMU 15

Apr/May2011

CFMU Implementation

IFPUV with

‘Old’ + ‘New’

June2011

15 Nov. 2012

2012

OPT 1

June2012

2012

OPT 2

Sept2012

2012

OPT 3

Oct2012

16OPT 1

Feb2012

15OPT 1

Feb2011

15OPT 2

Mar2011

16OPT 2

Mar2012

Apr/May2013

CFMU 17

15

AFTN Considerations

Message Length Some FPLs will be a little longer (more in Field 18) Possible Message Truncation

Group Addressing at Com Centre may result in mixed New and Present FPLs for some addressees

Traffic Load During test sessions During Operations (sometimes there will be New and Present

versions of same FPL)

16

State Implementation Status – 14/6/10

17

Questions?