Central Office for Delay Analysis - CODA

The objective of the Central Office for Delay Analysis (CODA) within EUROCONTROL is to provide policy makers and managers of the ECAC Air Transport System with timely, consistent and comprehensive information on the air traffic delay situation in Europe, and to make these available to anyone with an interest in delay performance.

Ensuring timely performance delivery of the European ATM system is the result of performance monitoring, performance driven planning, timely identification, development and deployment of Best Practices and Operational Improvements and above all strong collaboration between all Stakeholders. The main tasks of the activity involve:

Enhanced CODA

In order to achieve this purpose in the most timely and comprehensive manner, an enhanced CODA product (eCODA) has been developed. eCODA aims to provide information on all delay causes, one week after of the end of each calendar month. This is facilitated by the excellent co-operation of aircraft operators who supply eCODA with the necessary data; together with Air Traffic Flow Management data from the EUROCONTROL Central Flow Management Unit, they enable the reports to be produced.

By following the tabs on this page, each industry partner can reach its specific part of the CODA website.

These pages provide secured access to the on-line analysis tools of CODA. Only those professionally engaged in Air Traffic Flow Management and aircraft operations who have applied for access, signed a Letter of Agreement with CODA and received the necessary access authority may enter these pages.

Airlines

There are 2 applications available to our airline partners that help to analyse their data.

Airports

There is currently 1 application available to our airport operators that can help to analyse their data.

Stakeholders

Please be aware that these applications are only accessable to certified people. If you would like access to the tools, please send your details to coda.

There is currently 1 application available to our industry partners that can help to analyse their data. This tool allows for detailed information by grouping flights.

Airline Data Processing

Besides statistics and reports based on CFMU flight data, CODA incorporates operational data received from various operators. This data first needs to be uploaded into the CODA database, and is then aggregated in order to allow responsive queries. This note documents the processes responsible of loading the raw data received from the provider into the CODA tables.

The complexity stems from the diversity of file formats that different operators send us. The ad hoc nature of their procedures used to make those files also often results in slight variations between successive deliveries.

Target Format

Operators have been asked to produce information in the form of CSV tables with one line per flight, including the some of the following fields:

Minimum required data set in Italic.

Cy ICAO 3-letter code of the company that flies the aircraft
CallSign IACO 3-letter flightnumber prefix followed by the flight number (no blanks)
ComFltNbr The commercial flightnumber (as given to airports for passenger info displays)
AcReg 5 characters (no hyphen)
Dep ICAO 4-letter code of the departure station (the IATA 3-letter code can also be accepted)
Dst ICAO 4-letter code of the destination station (the IATA 3-letter code can also be accepted)
Std Standard Time of Departure according to the schedules including the date
Sta Standard Time of Arrival according to the schedules including the date
Eet (FP) Estimated Flight time in minutes according to the flight plan
Out Actual Time of Departure from the gate including the date
Off Actual Time of Take-off including the date
On Actual Time of Landing including the date
In Actual Time of Arrival at the gate including the date
Dl1 First delay cause in IATA 2 digit code
Time1 First delay cause duration in minutes
Dly2 Second delay cause in IATA 2 digit code
Time2 Second delay cause duration in minutes
Dly3 Third delay cause in IATA 2 digit code
Time3 Third delay cause duration in minutes
Dly4 Fourth delay cause in IATA 2 digit code
Time4 Fourth delay cause duration in minutes
Dly5 Fifth delay cause in IATA 2 digit code
Time5 Fifth delay cause duration in minutes
RD from Flt If there is a reactionary delay, give the call sign of the flight having directly caused the reactionary delay
STXO Standard Outbound Taxi Time in minutes
STXI Standard Inbound Taxi Time in minutes
ServType Service Type (See IATA SSIM appendix C) (1 character)
FltType Flight Type ("S" for Scheduled or "N" for Non-scheduled (Charter))
QC Quality Control ("A" for ACARS, "M" for Manual or "C" for Combination or both)

Processing Chain

Input files are a subset or variation of the above format, and need to undergo the following steps:

  • Extraction of the attached data from an email message (contact us)
  • Construction of a mapping filter from the various input formats to the unique target format, based on the operator code and date concerned
  • Application of the filter to the incoming data, and loading of the resulting table to a staging area within the database
  • Matching data received against CFMU flight information; only the files that can be successfully linked will be moved to the actual CODA tables

Contact

If you would like to know more about the CODA, request an Ad-Hoc report or wish to communicate an error please send an email to CODA.

Tagged under: