Airport ATFM delay

From wiki
Jump to: navigation, search
1. Contact
1.1 Contact organisation EUROCONTROL: The European organisation for the safety of air navigation.
1.2 Contact organisation unit Directorate Single Sky - Performance Review Unit (DSS/PRU)
1.3 Contact name Performance Review Unit - EUROCONTROL
1.5 Contact mail address 96 Rue de la Fusée
1130 Brussels
BELGIUM
1.6 Contact e-mail address NSA-PRU-Support@eurocontrol.int
1.7 Contact phone number +32 2 729 39 56
2. Metadata update
2.1. Metadata last certified not applicable
2.2. Metadata last update 01 November 2016

3. Statistical presentation

3.1. Data description

Please note that software release 20.0 of the Network Manager on 04 April 2016 introduced a change in the computation of ATFM delay 
for operational purposes. For consistency reasons, ATFM delays used for regulatory purposes within the SES performance scheme will
continue to be based on the methodology used before April 2016 on this web page. As a result, the data published on this website
might deviate from the data directly published by EUROCONTROL for operational purposes. See the Source data section below for more
information on the changes in NM release 20.0.

The measure provides an indication of ATFM delays on the ground due to constraints at airports.

In Europe, when traffic demand is anticipated to exceed the available capacity in en route centres or at airports, Air Traffic Control (ATC) units may request the local Flow Management Position (FMP) to instigate an Air Traffic Flow Management (ATFM) measure, or regulation. Aircraft expected to arrive during a period of congestion are given Air Traffic Flow Management delay at their departure airport, under the authority of the Network Manager, in order to regulate the flow of traffic into the constrained downstream en route sector or airport, thus ensuring safety. The resulting ATFM delays are calculated as the difference between the estimated take-off time calculated from the filed flight plan including updates and the calculated take-off time allocated by the central unit of ATFM. The reason for the regulation is indicated by the responsible Flow Management Position (FMP). The delay is attributed to the most constraining ATC unit.

As an output of the ATMAP Group, Airport ATFM delay has been in use as a commonly agreed proxy for airport capacity shortfalls since 2009. The calculation of Airport ATFM delay is based on a well established and commonly accepted algorithm and is compliant with the KPI definition in the EU legislation.

3.2. Classification system

Airport ATFM delay is classified per Member State, with a breakdown by airport.

3.3. Sector coverage

The measures pertain to the Air Transport and Air Traffic Management Sector of the economy.

3.4. Statistical concepts and definitions

ATFM delays
ATFM delay” is defined as the duration between the last Estimated Take-Off Time (ETOT) and the Calculated Take-Off Time (CTOT) allocated by the European ATM Network Manager. ATFM Delay comprises both Airport ATFM Delay and En-route ATFM Delay. This indicator is solely concerned with Airport ATFM Delay.
The delay is truncated to minutes.
Flights
All the IFR flights which have filed a flight plan and have landed at the relevant airport are taken into account.
Attribution of Delay

ATFM delay to which a flight is subjected is defined to have as cause the most penalizing ATFM regulation which affects it. Depending of the type and the entity responsible for the reference location protected by the ATFM regulation, the ATFM delay is classified as either an airport or an en-route ATFM delay and attributed to the relevant ANSP (en route) or airport. Airport ATFM delays generated by arrival or global regulations are attributed to the arrival airport as stated in the flight plan. If the regulation is protecting a group of airports, the delay is attributed to the destination airport of the affected flight.

Each ATFM regulation also comprises a designator referring to the cause of delay which can be used in further analysis.

3.5. Statistical unit

The statistical unit is the airport. Airport level data is also aggregated to States.

3.6. Statistical population

The statistical population is the set of airports subject to performance monitoring within the Single European Sky Performance Scheme.

3.7. Reference area

The reference area is the Single European Sky Area.

3.8. Time coverage

2009 is the first year for which data is presented.

3.9. Base period

Not applicable.

4. Unit of measure

Airport ATFM delay is measured in minutes per IFR arrival.

5. Reference period

  • The first reference period (RP1) covers the calendar years 2012 to 2014 inclusive.
  • The second reference period (RP2) covers the calendar years 2015 to 2019 inclusive.

Unless decided otherwise, the following reference periods shall be of five calendar years.

6. Institutional Mandate

Legal acts and agreements are established in the Performance Regulation (691/2010) and Commission Implementing Regulation (EU) No 390/2013;

7. Confidentiality


8. Release policy

8.1. Release calendar

Airport ATFM delay data is released monthly with yearly aggregates.

8.2. Release calendar access

Not applicable.

8.3. User access

Information is disseminated to the general public via the EUROCONTROL website.

9. Frequency of dissemination

Airport ATFM data is published monthly with the annual performance aggregate being available in January of the following year.

10. Dissemination format

The information is available on the EUROCONTROL website.

11. Accessibility of documentation

11.1. Documentation on methodology

As per the pertaining regulations (see Institutional Mandate).
For technical questions not addressed in Statistical processing please contact: NSA-PRU-Support@eurocontrol.int.
Additional definitions of the terms used in the frame of the this KPI are available in the Glossary.

11.2. Quality documentation

Documentation on procedures applied for quality management and quality assessment is under development.

12. Quality Management

12.1. Quality assurance

The data is provided by the Network Manager and as such it is their responsibility to perform any quality assurance activities.

12.2. Quality assessment

Data is validated by random quality checks, e.g. missing data for given a day, adherent data, etc. Any issues are reported to the Network manager who works with the EUROCONTROL Performance Review Unit to resolve them.

13. Relevance

The information is published for performance monitoring purposes in accordance with the relevant EU legislation.

13.3. Completeness

The data is collected for the entire Single European Sky Area.

14. Accuracy and reliability

14.1. Overall accuracy

The Airport ATFM delay is the delay calculated as defined in Commission Regulation (EU) No 255/2010. This calculation is based on a well established methodology, which has been in place since 2009.

15. Timeliness and punctuality

15.1. Timeliness

The full set of Airport ATFM delay per IFR arrival at airports included in the performance scheme is published each month - in general between 14 and 16 days after the end of the month in question.

15.2. Punctuality

The internal databases are updated daily. The statistical processing is performed once per month.

16. Comparability

16.1. Comparability — geographical

The data is collected centrally by the Network Manager and computed consistently throughout the entire Single European Sky Area which allows comparisons across different airports.

16.2. Comparability over time

Comparison over time is valid.

17. Coherence

17.1. Coherence — cross domain

ATFM delays is calculated relative to the flight plan.

Although not fully cohered, the delay reported by aircraft operators to CODA under the corresponding IATA delay categories shows a high correlation with the ATFM delay calculated by the Network Manager. It should be noted that the delay reported by aircraft operators relates to airline schedules rather than flight plan.

17.2. Coherence — internal

Data is fully coherent from an internal perspective.

18. Cost and burden

Not available.

19. Data revision

The data revision policy has not yet been defined.

20. Statistical processing

20.1. Source data

The data for the calculation of this indicator is provided by the Network Manager.

Please note that the delays caused by READY to Depart (REA) messages and ATFM slot extensions were excluded from the
ATFM delay computation with NM release 20 (4 April 2016) which reduces the overall amount of computed ATFM delay.
More information on the adjusted ATFM delay computation as of NM release 20.0 from 4 April can be found here:
NM release 20.0 - 4 April 2016 - FB750-Delay Calculation improvements.
For consistency reasons, the ATFM delay computation used for the SES Performance Scheme in RP2 (2015-2019) continues to be based on 
the old methodology which includes delays from READY to Depart (REA)messages and ATFM slot extensions. This leads to differences 
between the ATFM delay data in the SES performance scheme and the reporting for operational purposes as published by NM and the PRU.

20.2. Frequency of data collection

Data is collected for each individual flight in real time.

20.3. Data collection

Data is collected and compiled by the EUROCONTROL Network Manager.

20.4. Data validation

Data is validated and cross-checked by the EUROCONTROL Network Manager.

20.5. Data compilation

Data is aggregated for different delay groups, airports, and Member States.

20.6. Adjustment

Corrections may be made when issues are discovered as described in the Quality Assessment section of this document.

21. Comment

Disclaimer

This data is published by the Performance Review Body (PRB) of the Single European Sky. Every effort has been made to ensure that the information and analysis contained on this website are as accurate and complete as possible. Despite these precautions, should you find any errors or inconsistencies we would be grateful if you could please bring them to the Performance Review Unit’s attention.

The information may be copied in whole or in part providing that the copyright notice and disclaimer are included. The information may not be modified without prior written permission from the PRB. The views expressed herein do not necessarily reflect the official views or policy of EUROCONTROL or of the European Commission, which make no warranty, either implied or express, for the information contained on this website, neither do they assume any legal liability or responsibility for the accuracy, completeness or usefulness of this information. The PRB reserves the right to change or amend the information provided at any time and without prior notice.

Personal tools
Namespaces

Variants
Actions
Meta Data
Navigation
Toolbox
Print/export