This SES-related implementation objective is derived from Regulation (EC) No 633/2007 of 7 June 2007 laying down requirements for the application of a flight message transfer protocol (FMTP) for information exchanges between flight data processing systems for the purpose of notification, coordination and transfer of flights between air traffic control units and for the purposes of civil-military coordination, in accordance with Regulation (EC) No 1032/2006 [Ref. Article 1(1)].
Regulation (EC) No 633/2007 applies to [Ref. Article 1(2)]:
a) Communication systems supporting the coordination procedures between air traffic control units using a peer-to-peer communication mechanism and providing services to general air traffic;
b) Communication systems supporting the coordination procedures between air traffic services units and controlling military units, using a peer-to-peer communication mechanism and providing services to general air traffic.
The terms used in this objective are defined in Article 2 of Regulation (EC) No 549/2004, complemented by Article 2 of Regulation (EC) No 633/2007.
This implementation objective has been amended in order to introduce the new optional conditional transitional arrangements defined in Regulation (EU) No 283/2011 of 22 March 2011.
NOTE: This SES-related implementation objective does not replace the EC legislation. It aims at facilitating the monitoring and reporting of the implementation of a common flight message transfer protocol in European ATM in line with the EC regulations and through the SES implementation monitoring and reporting mechanism.
NOTE FOR MILITARY AUTHORITIES: It is the responsibility of each military authority to review this Objective IN ITS ENTIRETY and address each of the SLoAs that the military authority considers RELEVANT for itself. This has to be done on top and above of the review of "MIL" SLoAs which identify actions EXCLUSIVE to military authorities.
|Entry into force of regulation||28-06-2007||—||Applicability Area|
|All EATMN systems put into service after 01/01/09||01-01-2009||—||Applicability Area|
|All EATMN systems in operation by 20/04/11||—||20-04-2011||Applicability Area|
|Transitional arrangements||—||31-12-2012||Applicability Area|
|Transitional arrangements when bilaterally agreed between ANSPs||—||31-12-2014||Applicability Area|
|ASP01||Upgrade and put into service communication systems to support information exchange via FMTP between FDPS(s) for the purpose of notification, coordination and transfer of the flights between ATC units||
|ASP02||Develop safety assessment for the changes||
|ASP03||Train technical staff||
|MIL01||Upgrade and put into service communication systems to support information exchange via FMTP between FDPS(s) for the purpose of notification, coordination, transfer of the flights and civil-military coordination between ATS units and controlling military units||
EC - COMMISSION IMPLEMENTING REGULATION (EU) 2017/373 - (OJ L 62, 8.03.2017, p. 1) - COMMISSION IMPLEMENTING REGULATION (EU) 2017/373 of 1 March 2017 laying down common requirements for providers of air traffic management/air navigation services and other air traffic management network functions and their oversight, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011, (EU) No 1035/2011 and (EU) 2016/1377 and amending Regulation (EU) No 677/2011 03/2017
EUROCONTROL - Air Navigation Systems Safety Assessment Methodology (SAM) - Version 2.1 / 11/2006
EUROCONTROL - EAM 4 - ESARR 4 - Risk Assessment and Mitigation in ATM - Edition 1.0 / 04/2001
EUROCONTROL - EUROCONTROL Inter Centre Test Tool (ETIC) - Version 3.2.2. / 08/2012
EUROCONTROL - Guidelines for Implementation Support (EGIS) Part 5 Communication & Navigation Specifications Chapter 13 Flight Message Transfer Protocol (FMTP) - Edition 2.0 / 12/2008
|ASP01, ASP02, ASP03|
EUROCONTROL - SPEC-100 - EUROCONTROL Specification of Interoperability and Performance Requirements for the Flight Message Transfer Protocol (FMTP) - Edition 2.0 / 06/2007
|ASP01, ASP02, ASP03|