The data and indicators for reference period 2 are in accordance with Implementing Regulations (EU) No 390/2013 and (EU) No 391/2013.
|
Traffic
|
|||
|
Average daily IFR flights
|
|||
|
Period: January-December
|
Source: Network Manager
|
||
|
|
| ||
|
SAFETY
|
|||||
|
Safety KPI #1: Effectiveness of safety management (EoSM)
|
|||
|
Period: January-December
|
Source: EASA
|
||
|
|
|
||
|
FAB level
| |||
|
State level
|
|||
|
ANSP level
|
|||
|
RAT methodology application
(Meta data)
|
Reporting of Just Culture
(Meta data)
|
||||
|
Period: January-December
|
Source: DPS/SSR
|
Period: January-December
|
Source: EASA
|
||
|
|
There are no just culture results at European wide level.
Note that the total number of “NO” answers may not reflect an absence of Just Culture. |
||||
|
ENVIRONMENT
|
|||
|
Environment KPI #1: Horizontal en-route flight efficiency [%]
|
|||
|
Period: January-December
|
Source: PRU analysis; Network Manager
|
||
|
|
| ||
|
Environment PI #1: Additional taxi-out time [minutes per departure]
|
|||
|
Period: January-December
|
Source: PRU analysis; Airports
|
||
|
|
|
||
|
Environment PI #2: Additional time in terminal airspace [minutes per arrival]
|
|||
|
Period: January-December
|
Source: PRU analysis; Airports; Network Manager
|
||
|
|
|
||
|
CAPACITY
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 on this web page will continue to be based on the methodology used before April 2016. As a result, the data published on this website might deviate from the data directly published by EUROCONTROL for operational purposes.
See the Meta data for more information on the changes in NM release 20.0.Changes due to the [Post Operations Adjustment Process] will only be taken into account when the full year 2016 is available. |
|||
|
Capacity KPI #1: En-route ATFM delay per flight [minutes per flight]
|
|||
|
Period: January-December
|
Source: Network Manager
|
||
|
|
| ||
|
Capacity KPI #2: Airport ATFM arrival delay per flight [min./arr.]
|
|||
|
Period: January-December
|
Source: PRU analysis; Network Manager
|
||
|
|
| ||
|
Capacity PI #1: Adherence to ATFM slots [% flights inside the slot tolerance window of [-5, +10 min.]]
|
|||
|
Period: January-December
|
Source: Network Manager
|
||
|
|
| ||
|
Capacity PI #2: Air traffic control pre-departure delay [min. per dep.]
|
|||
|
Period: January-December
|
Source: Airports
|
||
|
|
|
||
|
COST-EFFICIENCY
|
|||
|
En-route Service Units (TSU)[actual vs. determined]
|
|||
|
Period: January-December
|
Source: CRCO; EC; PRU analysis
|
|
|
|
En-route TSU: by charging zones (2016)
|
En-route TSU: actual vs. determined (2016)
|
||
|
Cost efficiency KPI #1: Determined unit cost (DUC) for en-route (ER) ANS
|
|||
|
Period: January-December
|
Source: States, CRCO
|
||
| The figures shown below are expressed in real term (Euro 2009). The underlying data (currencies, etc.) are available in the download file. (D)=Determined ; (A)=Actual | |||
|
Cost efficiency KPI #2: Determined unit cost (DUC) for terminal (TR) ANS
|
|||
|
Period: January-December
|
Source: States, CRCO
|
||
| The figures shown below are expressed in real term (Euro 2009). The underlying data (currencies, etc.) are available in the download file. (D)=Determined ; (A)=Actual | |||