Overview

Row ———————————————————-

Aerodrome Layout

General

Row ———————————————————-

Summary

Daily Traffic Variation snapshot

Traffic

Row ———————————————————–

Annual Traffic

Monthly Traffic

Row ———————————————————–

Annual Variation of Daily Movements

Average Weekday Hourly Throughput

ATFM Delay

Row ———————————————————–

Annual Arrival ATFM Delay

Monthly Arrival ATFM Delay

Row ———————————————————–

Daily Arrival ATFM Delay

Share of ATFM Delay

ATFM Slot

Row ———————————————————–

Annual Regulated Departures

Monthly Regulated Departures

Row ———————————————————–

Annual ATFM Slot Adherence

Monthly ATFM Slot Adherence

CDO/CCO

Row ———————————————————–

Average time flown level per flight

Median CDO/CCO altitudes

Row ———————————————————–

Share of CDO/CCO flights

Median CDO/CCO altitudes vs. Average time flown level per flight

ASMA Time

Analyses on approach times are only available for airports providing the required data using the Airport Operator Data Flow (APDF).

If you belong to the airport and would like to implement such data flow, please contact

Taxi-Out Time

Analyses on taxi-out times are only available for airports providing the required data using the Airport Operator Data Flow (APDF).

If you belong to the airport and would like to implement such data flow, please contact

Taxi-In Time

Analyses on taxi-in times are only available for airports providing the required data using the Airport Operator Data Flow (APDF).

If you belong to the airport and would like to implement such data flow, please contact

Pre-Dep Delay

Analyses on pre-departure delay are only available for airports providing the required data using the Airport Operator Data Flow (APDF).

If you belong to the airport and would like to implement such data flow, please contact

Turnaround Times

Analyses on turnaround times are only available for airports providing the required data using the Airport Operator Data Flow (APDF).

If you belong to the airport and would like to implement such data flow, please contact

About

Row ——————————————————————

Powered by

About this Dashboard

This data is published by the EUROCONTROL Performance Review Unit (PRU) in the interest of the exchange of information. It may be copied in whole or in part providing that this copyright notice © and disclaimer are included. The information may not be modified without prior written permission from the EUROCONTROL Performance Review Unit. The information does not necessarily reflect the official views or policy of EUROCONTROL, which makes no warranty, either implied or expressed, for the information contained in this document, including its accuracy, completeness or usefulness. 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 or if you have any questions then please contact us at: Performance Review Unit ().

About Performance Review Unit

The PRU is responsible for monitoring and reviewing the performance of the Pan-European ANS system across a number of key performance areas. As part of the EUROCONTROL Agency, the PRU supports the independent Performance Review Commission (PRC) in running the EUROCONTROL Performance Review System and executing the associated PRC work programme with the appropriate level of independence. The PRU also provides support to the European Commission (EC) on the SES Performance and Charging Schemes. In performing its tasks, the PRU maintains transparent working arrangements with service providers, airspace user organisations and the industry. Although the PRU is independent, it is administratively reporting to the Directorate European Civil-Military Aviation (DECMA). For feedback or questions please contact us at: Performance Review Unit ().

Row ——————————————————————

Data and Methodology

This dashboard is updated on a monthly basis.

IFR traffic data and ATFM delay related data is extracted from the Network Manager. CDO/CCO data are calculated by the Aviation Intelligence Unit of EUROCONTROL based on Network Manager data. All other airport related data is collected through the Airport Operator Data Flow (APDF). Under the APDF airports are required to report flight-by-flight data on a monthly basis. The data is reported during the month following the month of operations. Thus, typically, APDF data becomes available the 2nd month following the month of operation.

Data and metrics are shown based on availability at the moment of publication

  • Traffic data comprises all IFR flown flight plans for the airport (arrivals and departures) based on NM data.
  • ATFM delay data captures the arrival ATFM delay triggered by constraints at the airport based on NM data.
  • ATFM delays are grouped according to the regulation reason as described in https://ansperformance.eu/definition/atfm-delay-codes/
  • CDO/CCO performance is calculated by identifying level segments during the climb and descent. These level segments are considered to be inefficient. For more information please visit https://ansperformance.eu/efficiency/vfe/
  • Additional ASMA time measures the difference between an observed travel time elapsing from entering the 40NM radius around the airport to landing. This time is compared against a reference time to the respective entry sector, aircraft type, and landing runway. For more information please visit https://ansperformance.eu/methodology/additional-asma-time-pi/
  • In analogy, additional taxi-times are measured for the taxi-out and taxi-in phase. The observed taxi times are compared with a respective reference time. The reference time considers the parking position and runway used by the departure/arrival. For more information please visit https://ansperformance.eu/definition/additional-taxi-out-time/
  • Pre-departure delay is the delay in the off-block time with respect to the schedule time for departure. It provides for the airspace user reported delay reasoning in case of departures blocking off late. Delay codes have to be provided for delays >= 4 minutes. Most airports per se do not validate these delay codes, however, effort is underway to ensure appropriateness of the reported delay codes.Delay reasons are reported according to the IATA delay codes https://ansperformance.eu/library/iata-delay-codes.pdf Delay reported associated to code 89 is used for the calculation of the ATC pre-departure delay https://ansperformance.eu/definition/atc-pre-departure-delay/
  • Turnaround shows the time elapsing between an aircraft blocking in and blocking off for the next flight from the same parking stand on the same day and the sample is treated to filter out.