FPL2012 TF#7Brussels 10 October 2012 Kim Breivik Operational Requirements Network Management EUROCONTROL Deployment

FPL2012 TF#7 10 October Deployment Content Deployment Policy Transition Contingency States IFPS AOs Preparation Formal Feedback (State Letter) – EUR Implementation Plan AIC Publication NEC Feedback for IFPS Documentation IFPS User Manual Doc CNS Filing ‘Guidance Material’ Training

FPL2012 TF#7 10 October EUR Region Deployment Policy Objective: All FPLs in New format from 15/11 AOs and CFSPs should submit FPLs in New format from 00:01 UTC on 12 Nov 2012 onwards AROs, IFPS, ATC systems should accept New from 12/11 FPLs should NOT be submitted in Old format after 00:01 UTC on 15 Nov 2012  IFPS will not accept FPLs with DOF on 15 Nov during the period Nov 2012  RPLs for Winter ’12-’13 should be submitted in New format

FPL2012 TF#7 10 October © EUROCONTROL Central Flow Management Unit Transition – IFPS ANSPs 00:00 15/11/2012 Reception of Old by ANSPs Reception of New by ANSPs IFPS Translation from New to Old Possible transition for an IFPS State without a period of mixed reception of Old and New ENV Parameter per Addressee (ICAO_2012_READY_DATE) Default = 00:00UTC on 16/11/ hrs + 24 hrs *Applicable only for IFR/GAT FPLs !

FPL2012 TF#7 10 October © EUROCONTROL Central Flow Management Unit ANSP Database Content ≈ FPL Dist. Parameter and Size of Airspace IFPS ‘FPL2012_READY’ Parameter Old format only New format only

FPL2012 TF#7 10 October © EUROCONTROL Central Flow Management Unit Reception by IFPS/ACCs of Old format on 15/11 FPL received by ARO in Old format Initial EOBT Flying time to Europe = 12hrs 24 hrs FPL distributed by ARO & received by IFPS / ANSPs in Old format ! ACCs don’t want to receive FPLs +/- 18hrs in advance therefore FPLs frequently distributed by ARO several hours after reception: Long-haul flight departing outside Europe:

FPL2012 TF#7 10 October © EUROCONTROL Central Flow Management Unit Reception by ACCs of Old format from IFPS after 16 Nov (1) Received by IFPS in Old format EOBT 24 hrs Flying time to Europe = 12hrs FPL Dist Parameter e.g. – 4hrs FPL reception by ANSP in Old format Long-haul flight departing outside Europe: DLA

FPL2012 TF#7 10 October Re-Addressing by IFPS FF EUCHZMFP EUCBZMFP EGLLZPZX AD ADDRESS1 ADDRESS2 (FPL-ABC123-I/S......) Aircraft Operator IFPS AD Line Addressing Normal Addressing

FPL2012 TF#7 10 October Re-Addressing & 2012 Transition ‘Unknown’ (= address doesn’t exist in IFPS database) AD Line addressees Receive Old format prior to 15 Nov Receive New format after 15 Nov ‘Known’ AD Line addressees Receive Old/New in accordance with ENV parameters for the unit concerned

FPL2012 TF#7 10 October AO - FPL Submission Scenarios 1.Entirely within IFPZ a) May be submitted to IFPS in New format now b) May be submitted in Old format until 23:59 on14/11 c) Should be submitted in New format from 12/11 d) Shall be submitted in New format from 15/11 2. Departing to outside IFPZ Same as for 1. and may inc. AD line addresses in each of the cases a) to d) 3. Departing from outside IFPZ Should be submitted to ARO at ADEP in accordance with State requirements

FPL2012 TF#7 10 October IFPS Default Addressing Scenarios AD UKKKZQZQ UREEZQZX UARRZQZX (FPL-AZA123-I/S -A334/H-B2GRSYW/S1 -LIRF1800 -N0460F380……. -VIDP0750 VIDD -PBN/B2 DOF/ Normal - Old format Copy - Old format ‘AD’ - Old format Normal - New format Copy - New format ‘AD’ - New format

FPL2012 TF#7 10 October IFPS Default Addressing Scenarios cont. AD UKDDZQZX UREEZQZX UARRZQZX (FPL-AZA123-I/S -A334/H-B2GRSYW/S -LIRF1800 -N0460F380……. -VIDP0750 VIDD -PBN/B2 DOF/ Normal - Old format Copy - Old format ‘AD’ - Old format Normal - New format Copy - New format ‘AD’ - New format

FPL2012 TF#7 10 October IFPS Default Addressing Scenarios cont. AD UKDDZQZX UREEZQZX UARRZQZX (FPL-AZA123-I/S -A334/H-B2GRSYW/S -LIRF1800 -N0460F380……. -VIDP0750 VIDD -PBN/B2 DOF/ Normal - Old format Copy - Old format ‘AD’ - Old format Normal - New format Copy - New format ‘AD’ - New format

FPL2012 TF#7 10 October Mixed Mode - Considerations (FPL-AZA123-I/S -A334/H-B2RSYW/S1 -LIRF1800 -N0460F380……. -VIDP0750 VIDD -PBN/B2 DOF/ Old format New format Aircraft Operator Departure ACC 1 ACC 2 ACC 3 Destination (DEP-AZA123-LIRF1830-VIDP- DOF/121115) ? ? ? (ARR-AZA123-LIRF-VIDP0110) ‘New’ ‘Old’

FPL2012 TF#7 10 October Problem Example An example from 24 th September: 1.TAM submit (using SITA service) a FPL in New format including the IFPS addresses 2.IFPS automatically rejects due to a syntax error (NAV/ contains too many characters) and sends a REJ to TAM 3.TAM don’t understand the error and are unable to correct it because it doesn’t reflect the message they sent! Analysis made with Madrid Comms centre, SITA, TAM and Brasilian authorities reveals: Brasil Comms centre translated into Old format believing IFPS requires it.

FPL2012 TF#7 10 October Roll-Over Period - Analysis Technical Conclusions IFPS and/or an ATC unit may expect to receive some, legitimately submitted, Old format messages on 15 Nov IFPS and/or an ATC unit may expect to receive both Old and New format messages for the same flight The communications network can influence the result therefore end-to-end (OPT) testing essential A State having installed a translator at the level of the Comms Centre must be sure it will switch correctly on 15/11 Procedural Conclusion AOs should submit in New format from 12/11. Certainly if any part of a flight could possibly occur on the 15 th, then all messages should be submitted in New format IFPOs need to be aware that not all errors are due to originator mistakes

FPL2012 TF#7 10 October Contingency – IFPS State An IFPS State which experiences a problem with the switch to New format can request to revert to Old format Via request to IFPS Supervisor Messages processed by IFPS prior to the change back to Old and awaiting transmission will still be received in New format (short FPL Distribution Parameter = short transition period)

FPL2012 TF#7 10 October Contingency – Non-IFPS State A non-IFPS State which experiences a problem with the switch to New format can have FPLs received via IFPS re-addressing function (AD line addressing) sent in Old format Via request to IFPS Supervisor Only a partial solution – not relevant to FPLs that don’t penetrate the IFPS zone (IFPZ) or VFR or OAT

FPL2012 TF#7 10 October Contingency – Flight Plan Providers No mitigation against the need to submit in New format from 15/11 Provided at least a portion of flight (IFR) is within the IFPS Zone then: An AFTN communication problem can be mitigated by: Submitting directly to IFPS via SITA network using IFPS SITA addresses (BRUEP7X + PAREP7X) Submitting directly to IFPS via B2B (for existing B2B users, cannot be implemented at short notice) An ATC unit outside IFPZ having announced it’s unable to accept New format can be addressed via AD line

FPL2012 TF#7 10 October Deployment Content Deployment Policy Transition Contingency States IFPS AOs Preparation Formal Feedback (State Letter) – EUR Implementation Plan AIC Publication NEC Feedback for IFPS Documentation IFPS User Manual Doc CNS Filing ‘Guidance Material’ Training