PRB monitoring
▪ ANS Finland registered zero minutes of average en route ATFM delay per flight during 2020, thus meeting the local breakdown value of 0.09.
▪ Delays must be considered in the context of the traffic evolution: IFR movements in 2020 were 58% below the 2019 levels in Finland.
▪ Finland reported no capacity issues and a 32% drop in ATCO FTE numbers compared to 2019 and also compared to 2020 planned values. Finland did not report any specific drivers behind the ATCO FTE number reduction, however, only two ATCO FTEs are reported to have stopped working in OPS.
▪ The yearly total of sector opening hours in Tampere ACC was 10,168, showing a 24.6% decrease compared to 2019.
▪ Tampere ACC registered 8.44 IFR movements per one sector opening hour in 2020, being 42.9% below 2019 levels.
Summary of capacity performance
The Finland FIR experienced a traffic reduction of 58% from 2019 levels, to 119k flights. The traffic level was accommodated with zero en route ATFM delays to airspace users.
NSA’s assessment of capacity performance
The traffic dropped significantly over the year due to COVID-19 pandemic. The en-route ATFM delay has been 0 for many years. During RP3 planning, airspace user demand was to keep the delays as low as possible, and ANSP has achieved the target of this KPI.
Monitoring process for capacity performance
Review of the actual values from the NM dashboard.
Capacity planning
ANSP is expected to continue this good trend on en-route ATFM delay.
Application of Corrective Measures for Capacity (if applicable)
No data available
Finland identifies only Helsinki airport as subject to RP3 monitoring.
The Airport Operator Data Flow is fully established and the monitoring of all capacity indicators can be performed. Nevertheless, the quality of the reporting does not allow for the calculation of the ATC pre-departure delay, with more than 60% of the reported delay not allocated to any cause.
Traffic at this airport in 2020 decreased by 63% with respect to 2019. Arrival ATFM delays were observed only in the first trimester and slot adherence was well above 90%.
The average arrival ATFM delay at Helsinki in 2020 was 0.20 min/arr, 47% less than the 0.37 min/arr observed in 2019.
The terminal ANS ATFM delay target was achieved, and the 0,20 actual values were caused by weather causes. The delays were only in winter months (January-February-March) and after significant drop in traffic, the terminal delays dropped to zero for the rest of the year.
The provisional national target on arrival ATFM delay in 2020 was met.
In accordance with Article 3 (3) (a) of Implementing Regulation (EU) 2020/1627: The incentive scheme shall cover only the calendar years 2022 to 2024.
| Airport level |
| Airport name |
Avg arrival
ATFM delay (KPI#2)
|
Slot adherence (PI#1)
|
ATC pre departure
delay (PI#2)
|
All causes pre departure
delay (PI#3)
|
| 2020 |
2021 |
2022 |
2023 |
2020 |
2021 |
2022 |
2023 |
2020 |
2021 |
2022 |
2023 |
2020 |
2021 |
2022 |
2023 |
| Helsinki-Vantaa |
0.2 |
NA |
NA |
NA |
93.6% |
NA% |
NA% |
NA% |
0.08 |
NA |
NA |
NA |
7.8 |
NA |
NA |
NA |
ATFM slot adherence
With the drastic drop in traffic, regulated departures from Helsinki also virtually disappeared as of April. The annual figure is therefore driven by the performance in the first trimester.
Helsinki’s ATFM slot compliance was 93.6%. With regard to the 6.4% of flights that did not adhere, 2.4% was early and 4% was late.
Finnish NSA reports: Slot adherence remained on a similar level with 2019 (93,9%) and was better than all other years in RP2 (2015-2018). ANSP updated internal documentation (instructions) related to flow management in ATS units in December 2019, and this might have effect on this PI.
ATC pre-departure delay
The quality of the airport data reported by Helsinki is too low, preventing the calculation of this indicator.
The calculation of the ATC pre-departure delay is based on the data provided by the airport operators through the Airport Operator Data Flow (APDF) which is properly implemented at Helsinki.
However, there are several quality checks before EUROCONTROL can produce the final value which is established as the average minutes of pre-departure delay (delay in the actual off block time) associated to the IATA delay code 89 (through the APDF, for each delayed flight, the reasons for that delay have to be transmitted and coded according to IATA delay codes.
However, sometimes the airport operator has no information concerning the reasons for the delay in the off block, or they cannot convert the reasons to the IATA delay codes. In those cases, the airport operator might:
- Not report any information about the reasons for the delay for that flight (unreported delay)
- Report a special code to indicate they do not have the information (code ZZZ)
- Report a special code to indicate they do not have the means to collect and/or translate the information (code 999)
To be able to calculate with a minimum of accuracy the PI for a given month, the minutes of delay that are not attributed to any IATA code reason should not exceed 40% of the total minutes of pre-departure delay observed at the airport.
Finally, to be able to produce the annual figure, at least 10 months of valid data is requested by EUROCONTROL.
The share of unidentified delay reported by Helsinki was above 40% for 5 months in 2020, preventing the annual calculation of this indicator. Helsinki usually has proper reporting, and the issue those months is likely to be due to the special traffic composition.
All causes pre-departure delay
The total (all causes) delay in the actual off block time at Helsinki in 2020 was 7.76 min/dep. The higher delays per flight were observed in April, due to the lower traffic and extraordinary circumstances.
This performance indicator has been introduced in the performance scheme for the first time this year, so no evolution with respect to 2019 can be analysed.