Proposed by Istanbul Airport, the objective of this project is to establish a real-time communication of the delay reasons.
If delayed, flights are more likely to have been affected by non-ATFM delays (e.g. knock-on delays, baggage loading, security checks, late fuelling, de-icing, etc.) with little real-time visibility to airport operators, ANSPs and the EUROCONTROL Network Manager on the reasons for these delays. Having a real-time insight into the delay reasons improves the situational awareness across the different actors and allows them to react during the operational day. The real-time sharing of the delay information in a centralised manner would allow for the tactical management of staff and resources adjusted to the actual operational situation. This allows early identification of disruptions at outstations potentially impacting the operation and at the same time centralises the collection of delay reasons to be used for post-ops performance analysis.
The READI project addresses a current need for airport operators and its ecosystem of operational stakeholders: real-time awareness of the delay drivers at the (own) airport and understanding of the delay drivers at outstations (departing airports for inbound flights).
The READI project grouped airports, airlines, ground handlers with IATA endorsing the project and EUROCONTROL acting as “honest data broker” providing the technical platform
There is a lag in the current delay data reporting mechanism with the information becoming available too late to the airport operator to deploy remedial actions to stabilise or improve the local departure punctuality (OTP).
The lack of real-time delay information can be addressed by technology (in the near future) but more importantly it’s the legacy delay code schema that limits the live sharing of delay causes. The legacy delay code schema focus is on the delay reason and stakeholder rather than the turnaround process.
The legacy IATA AHM730 delay code schema was therefore deemed not fit for the live trials which were conducted between May 8-21 2023.The READI project opted to use the new IATA AHM732 delay code schema which has a 3-layer structure:
- Process – which aircraft turnaround process is affected?
- Reason – what is the actual reason causing a flight delay?
- Stakeholder – which stakeholder is responsible? ex. handler, passenger, etc.
The READI project only used the first Process layer to power a performance dashboard displaying live operational information helping local stakeholders to deploy tactical measures. The second and third layer of the AHM732 was not used in the READI project but in future will allow in-depth post-operational analysis and steer strategic changes.
The results of the limited (both in time and scope) live trials showed great value in a process centric reporting of tactical issues. On the day it is (often) sufficient for operational partners to know which turnaround processes are under pressure with post-ops analysis allowing for more in-depth analysis into the delay reasons and assess which stakeholders caused the delays.