ESSIP Plan Edition 2012
Consultation & Approval
Working arrangement in charge: NETOPS / ODSG
Outline description approved in: -
Latest objective review at expert level in: 04/2012
Commitment decision body: Provisional Council (PC)
Objective approved/endorsed in: 07/2000
Latest change to objective approved/endorsed in: 07/2012
Expected performance benefits
Safety : Prevention of overloads.
Capacity : Better use of the available network capacity.
Cost-effectiveness : Reduction of costs induced by delays.
Environment : N/A
Security : N/A
Detailed SloA descriptions
FCM03-ASP01 Provide flight plan message processing in ICAO format Start:03/1995 Finish:12/1995
Action by : ANS Providers
Description & purpose : Receive and automatically process IFPS output of all ICAO-defined flight plan messages for input into the local ATC systems. This excludes FPLs derived from RPLs (see also FCM03-ASP02).
Notes : Processing of IFPS output without manual intervention. The SloA can be considered as not applicable if the amount of
IFR/GAT traffic does not justify automation.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Automatic processing of flight plan messages in ICAO format has been implemented.
FCM03-ASP02 Automatically process FPLs derived from RPLs Start:03/1995 Finish:12/1995
Action by : ANS Providers
Description & purpose : Receive and automatically process IFPS output derived from RPL to suppress the need for RPL bulk-output from IFPS.
Notes : No longer requiring RPL bulk-output or transmission of FPLs derived from RPLs by the CFMU. The SloA can be
considered as not applicable if the amount of IFR/GAT traffic does not justify automation.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Automatic processing of FPLs derived from RPLs has been implemented.
FCM03-ASP03 Provide flight plan message processing in ADEXP format Start:12/1997 Finish:12/2012
Action by : ANS Providers
Description & purpose : Receive and automatically process IFPS output of all defined flight plan messages for input into local ATC systems in ADEXP format in line with ICAO State Letter (AN 13/2.1-08/50) - 25 June 2008.
Impact of Flight Plan 2012 changes:
The basic flight plan form and the field composition within the FPL message remains unchanged, but the content of some fields will change.
- changes to indications in Items 10 and 18 (including the use of digits) describing the precise NAV/COM/SUR capabilities of the flight
- the ability to file a FPL up to 5 days (120 hours) before the flight, using the Date of Flight (DOF/) in Item 18 - addition of new Item 18 indicators and changes to the contents of several existing indicators.
- a change to the description of a significant point which may now be described by range and bearing
The field composition within associated messages (CHG, DEP, CNL, ARR, RQP) will change to include the EOBT and Item 18 DOF/ thus ensuring association to the correct FPL.
FCM03
Implement collaborative flight planning
ESSIP Plan Edition 2012
Notes : All national ATC systems that receive flight plan data from IFPS receive and process the data in ADEXP format. The
SloA can be considered as not applicable if the amount of IFR/GAT traffic does not justify automation.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : ATC system is able to receive and process flight plan data from IFPS in ADEXP format.
FCM03-ASP04 Processing of APL and ACH messages Start:12/1997 Finish:12/1999
Action by : ANS Providers
Description & purpose : Process automatically, in the local ATC systems, real time updates to flight plan information as provided by IFPS via APL and ACH messages.
Notes : The SLoA may be implemented as a manual processing if the amount of IFR/GAT traffic does not justify automation.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Processing of APL and ACH messages by the ANSP is implemented.
FCM03-ASP05 Provide AFP for missing flight plans Start:03/1998 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated flight plan information on airborne flights by means of AFP message. Provide the AFP in case an IFR-GAT flight exists but no IFPL has been received from IFPS.
The related AFP message can be sent in either ICAO or ADEXP format.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Reception of AFP messages by CFMU has been ensured.
FCM03-ASP06 Provide AFP message for change of route Start:03/2003 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated flight plan information on airborne flights by means of AFP message; provide the AFP in case of a change of route where the exit point from the flight data processing area (FDPA) has changed.
The related AFP message must be provided in ADEXP format only.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Transmission of AFP messages for route changes by the ANSP has been implemented.
FCM03-ASP07 Provide AFP message for a diversion Start:03/2008 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated flight plan information on airborne flights by means of AFP message; provide the AFP in case of a diversion.
The related AFP message must be provided in ADEXP format only.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Transmission of AFP messages for diversions by the ANSP has been implemented.
FCM03-ASP08 Provide AFP message for a change of flight rules or flight type Start:03/2003 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated flight plan information on airborne flights by means of AFP message; provide the AFP in case of a change of flight rules from VFR to IFR, or IFR to VFR, or a change of flight type from OAT to GAT, or GAT to OAT.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Transmission of AFP messages for changes of flight rules and flight types by the ANSP has been implemented.
FCM03-ASP09 Provide AFP message for a change of requested cruising level Start:03/2003 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated flight plan information on airborne flights by means of AFP message. Provide the AFP in case of a change of requested cruising level. The SLoA refers to a permanent change of a Requested Cruising Level and not to flight level changes allocated on a tactical basis by ATC.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Transmission of AFP messages for changes of requested cruising level by the ANSP has been implemented.
FCM03
Implement collaborative flight planning
ESSIP Plan Edition 2012
FCM03-ASP10 Provide AFP messages in ADEXP format Start:03/1998 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated flight plan information on airborne flights by means of AFP messages in ADEXP format instead of ICAO format. This is relevant for any trigger event.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Reception of AFP messages in ADEXP format by the CFMU has been ensured.
FCM03-ASP11 Use IFPLID in all messages to ETFMS Start:03/2005 Finish:12/2006
Action by : ANS Providers
Description & purpose : Use the IFPLID as provided by IFPS in all messages to ETFMS. The IFPLID shall only be used for system
generated/formatted messages. It is not the intention to enter the IFPLID manually. The use of the IFPLID will simplify the correlation of incoming flight plan messages with locally stored flight plan data at the CFMU.
Notes : The SloA can be considered as not applicable if the amount of IFR/GAT traffic does not justify automation.
Finalisation criteria : Reception of messages by CFMU/ETFMS that include the IFPLID has been ensured.
FCM03-ASP13 Provide AFP message for change of aircraft type Start:03/2003 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated Flight Plan information on airborne flights by means of AFP message. Provide the AFP in case of a change of aircraft type.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Transmission of AFP messages for changes of aircraft type by ANSP has been implemented.
FCM03-ASP14 Provide AFP message for change of aircraft equipment Start:03/2008 Finish:12/2012
Action by : ANS Providers
Description & purpose : Provide IFPS with updated Flight Plan information on airborne flights by means of AFP message. Provide the AFP in case of a change of aircraft equipment.
The related AFP message must be provided in ADEXP format only.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Transmission of AFP messages for changes of aircraft equipment by ANSP has been implemented.
ECIP Active PE
GEN01
Implement European ANS contingency measures for Safety Critical Modes of OperationREG ASP MIL APO USE INT IND
ESSIP Plan Edition 2012
Description & purpose
Implement contingency measures to be applied in the event of disruption or potential disruption of Air Traffic Navigation Services at European network, flow and individual ATS units (TWR, APP, ACC, UAC, FIS, AIS, ATFM, CNS, MET) levels, during Emergency and degraded modes of operation and to ensure the return to normal operations.
Applicable area(s) Operational capability dates FOR THIS OBJECTIVE
Initial operational capability: 06/2007 All ECAC States
Full operational capability: 12/2008
References
European ATM Master Plan relationship
None - None
Applicable legislation
Commission Regulation (EU) No 1035/2011 laying down common requirements for the provision of air navigation services and amending Regulations (EC) No 482/2008 and (EU) No 691/2010
Applicable ICAO Annexes and other references
None
Stakeholder Lines of Action (SloA )
SloA ref. Title Start Finish
GEN01-REG01 Enact National contingency regulations and oversee plans based on the European regulation
06/2007 06/2008 ▲
GEN01-ASP01 Implement contingency measures in accordance with ICAO, European Commission and EUROCONTROL regulation and deliverables
06/2007 06/2008 ▲
GEN01-ASP02 Train Air Traffic Controllers for the application of contingency procedures 06/2007 06/2008 ▲
GEN01-USE01 Update aircrew training manual to include the contingency measures occurrences
06/2007 06/2008 ▲
GEN01-AGY01 Develop initial guidelines for Contingency Planning FINALISED GEN01-AGY02 Develop final guidelines for Contingency Planning FINALISED ▲ Applicable to the military.
Description of finalised SLoAs is available on the EIPR website at http://www.eurocontrol.int/articles/essip-plan/
Consultation & Approval
Working arrangement in charge: Agency Advisory Board (AAB)
Outline description approved in: -
Latest objective review at expert level in: 12/2009
Commitment decision body: Provisional Council (PC)
Objective approved/endorsed in: 07/2007
Latest change to objective approved/endorsed in: -
Expected performance benefits
Safety : The availability of organised measures for contingency at European level is expected to prevent the occurrence of
incidents and accidents that could happen without set procedures.
Capacity : Structured contingency plans will enable to optimise capacity despite disrupted services.
Cost-effectiveness : The prevention of disorganised provision of ATS and the optimisation of capacity are cost/effective.