Aerospace & Defense · EUROCONTROL

EUROCONTROL Aviation Data & Dashboard

Datadory delivers eurocontrol aviation data dashboard data covering the European air navigation and traffic evidence base of the intergovernmental organisation and its Aviation Intelligence Unit: more than twenty statistical series - gate-to-gate CO2, NOx and SOx emissions by market segment and flight phase, en-route IFR flights, ATFM delays by IATA cause code, airport traffic, ASMA additional time, taxi times, flight efficiency and ANSP cost lines - with histories reaching back to January 2010 alongside daily traffic, punctuality and delay dashboards current to the previous day. Delivered as API, files, or your warehouse.

API, files, or your warehouse. Daily, weekly, or hourly.

Where it covers
ECAC area - EUROCONTROL member states aggregated at network, state, FIR (flight information region), area-control-unit, airport and ANSP levels, so a single scheme spans continent-wide totals and single-provider cuts
How far back
Staggered starts by series: CO2 by state from January 2010, en-route IFR flights and ATFM delays from January 2011 (FIR basis extended in 2013), horizontal en-route flight efficiency from 2014, airport traffic from January 2016, modelled gate-to-gate emissions January 2019 through December 2024; daily dashboards current to the previous day
How fine
Daily buckets for delay, traffic and efficiency series; monthly for emissions, ASMA additional time and taxi-time measures; yearly for ACE operational and ANSP financial lines

What is EUROCONTROL Aviation Data & Dashboard?

It is the analytical weight of the organisation that manages Europe's pan-continental air traffic network, published by EUROCONTROL and its Aviation Intelligence Unit and delivered by Datadory as analysis-ready rows. Two registers cover the same subject: an analytics layer of daily dashboards - network flight counts with one-, three-, six- and twelve-month evolution curves, top-40 airline and airport rankings, all-causes passenger delay graphics from CODA and ATFM delay analyses organised by IATA cause code - and a statistical layer of twenty-plus named series available in XLSX, CSV and Parquet.

The statistical layer runs staggered histories by design: CO2 by state from the Small Emitters Tool reaches back to January 2010, en-route IFR flights and ATFM delay series to January 2011, horizontal en-route flight efficiency to 2014, airport traffic to January 2016, and the modelled gate-to-gate emissions window covers January 2019 through December 2024. Around the core sit unit rates adjusted monthly via CRCO, sustainability measures spanning noise, contrails and CO2, and a publications library of Data Snapshots, the Seven-Year Forecast and the Aviation Long-Term Outlook 2024-2050.

That combination - institutional authority, twenty-plus series and self-documented fields - is why Datadory scores it 9/10 against a cross-catalog mean of 7.81. Get a sample of this dataset cut to your states and series, or read the rows below first.

What do sample rows look like?

One bucket from the gate-to-gate emissions extract exactly as it arrives, followed by its neighbour, so you can judge keys, typing and units before requesting anything:

# one row: ECAC network, business aviation, cruise phase, Jan 2019
LEVEL          = NETWORK
AREA           = ECAC
FOCUS_TYPE     = AREA FOCUS
YEAR = 2019    MONTH = 1
MARKET_SEGMENT = business        FLIGHT_TYPE = D
FLIGHT_PHASE   = cruise
NB_FLIGHTS     = 3247
CO2_TONS       = 26607.3         NOX_KG = 91683.56      SOX_KG = 7080.21

# the adjacent bucket: same month, arrivals (FLIGHT_TYPE = A)
FLIGHT_TYPE    = A               NB_FLIGHTS = 3428
CO2_TONS       = 23112.0         NOX_KG = 69539.62      SOX_KG = 6150.15

Every row is a fully specified bucket - level, area, period, segment, flight type and phase. That completeness is what makes the table additive: summing the right slices reproduces any aggregate the analytics layer displays, and splitting on FLIGHT_PHASE keeps cruise burn apart from taxi and approach work. The flagship file alone carries roughly 47 MB of such rows, and the delay side arrives the same way - minutes booked against cause codes rather than one undifferentiated total.

Which fields does the dictionary define?

Twelve fields define every row of the flagship emissions table, and they divide cleanly into address, period and measure. The address columns - LEVEL, AREA and FOCUS_TYPE - resolve where a bucket sits in the hierarchy from continental network down to state. The period columns pair YEAR with MONTH. The measures carry the payload: NB_FLIGHTS counts the movements, then CO2_TONS, NOX_KG and SOX_KG attribute each pollutant to the same bucket, with MARKET_SEGMENT, FLIGHT_TYPE and FLIGHT_PHASE preventing any blending of scheduled with business traffic or cruise with ground operations.

Filtering on those three qualifier columns before any trend work is the habit worth forming early: a business-aviation cruise line plotted beside a scheduled-carrier taxi line answers different questions, and only the qualifiers tell you which one you are looking at.

Which fields and series arrive only on request?

The twelve-column spine covers the flagship table; the extensions below fold into additional fields on request because they depend on the cut you specify:

  1. Sibling series on their own dimensions. En-route IFR flights and ATFM delays on area-control-unit and FIR bases, airport arrival delays, ASMA additional time, vertical flight efficiency, taxi times, pre-departure delays, slot adherence and complexity indicators, each keyed to your analysis rather than shipped generically.
  2. Delay-cause attribution. Minutes booked against IATA delay codes so capacity, staffing and weather separate cleanly.
  3. ANSP economics. ACE operational figures and provider financial lines joined onto the performance series for cost-per-unit benchmarks.
  4. Measured-versus-modelled CO2. State-level Small Emitters Tool series from January 2010 set beside the modelled window ending December 2024.
  5. Trajectory layering. Flight-level 4D positions from the companion repository - 25 million-plus flights - under the aggregates when aircraft granularity is wanted.

Where does coverage run across geography, time and grain?

  • Geography: the ECAC area - EUROCONTROL member states - aggregated at network, state, FIR, area-control-unit, airport and ANSP levels. One scheme spans continent-wide totals and single-provider cuts, so a regional rollup is a grouping exercise rather than a reconciliation project.
  • Temporal: staggered starts by series, not one arbitrary cutoff - CO2 by state from January 2010, en-route flights and delays from January 2011, flight efficiency from 2014, airport traffic from January 2016, modelled emissions January 2019 through December 2024. Dashboards run current to the previous day.
  • Granularity: day-level buckets for delay, traffic and efficiency; month-level for emissions, ASMA and taxi measures; year-level for ACE operational and ANSP financial lines.

Set against the wider catalog - where the average quality score across all 1,744 datasets is 7.81 - this record's 9/10 reflects verified field documentation, verified coverage statements and a publisher whose own operations generate the numbers.

How is the data delivered?

API, files, or your warehouse. Daily, weekly, or hourly.

Name the states, series, segments and period range when you request the sample and it lands shaped to that scope with the field dictionary unchanged - typed numerics, parsed periods, pollutant masses kept as columns rather than footnotes. Most teams take the historical depth once and keep recent periods rotating on whatever cadence matches their planning cycle; the key structure stays identical either way, so each pull appends cleanly to the last.

Two caveats travel with the rows and we label them explicitly: the modelled emissions series has a fixed window ending December 2024 while measured series run longer, and the dashboard layer is a presentation register rather than a row store. Datadory marks which is which in every delivery, so nobody models a chart image by accident.

Who uses this data, and for what?

  • Demand and capacity modelling - day-level en-route counts by state and FIR give forecasting models real European history; the workflow continues on our demand-forecasting page.
  • Delay-cause attribution - IATA-coded ATFM splits separate weather from capacity and staffing; see quant-backtesting for how trading desks consume the same series.
  • Emissions baselining and ESG reporting - gate-to-gate CO2, NOx and SOx by segment and phase supply the denominator for aviation footprint claims; the method continues on our esg-emissions-analysis page.
  • Market sizing and benchmarking - airport traffic and ANSP economics rank airports and providers on one consistent grid; see market-sizing.
  • Citation-grade research and journalism - every figure traces to the organisation operating the network itself; see citation-grade-research.

Which personas get the most value?

Data scientists and ML engineers get day-level series with stable keys and typed measures - enough history to train delay and traffic models without scraping chart views first; more in the data scientists hub.

Market researchers and consultants size and benchmark European aviation from state-, airport- and ANSP-level figures issued by a citable agency instead of stitching national statistics offices together.

Journalists, academics and students anchor traffic-recovery, punctuality and emissions reporting in the operator's own record - see journalists academics aerospace & defense.

Investors and quant researchers read traffic and CO2 series as demand indicators for airline and airport positions, with a decade-plus behind every signal; see investors quants aerospace & defense.

Which notes and neighboring datasets pair with it?

Scope note - this record bundles the organisation's whole public analytical output, from presentation dashboards to bulk series. Extracts are cut series-first by default; widen them deliberately if the publications layer is wanted too.

Completeness note - the twelve definitions above were verified against the source's own field documentation during the August 2026 research pass, and the newest reference periods are confirmed against live records when your sample is prepared rather than claimed here.

Where to go next - the rail below collects the attributional twin from the same publisher, the trajectory-level alternatives and the glossary entries that decode the delay vocabulary.

Field dictionary

Every field below is documented against real records. The full dictionary ships with the sample.

Field dictionary — twelve verified fields, one observation per geography x period x segment x flight-type x phase
fieldtypedefinitionexample
LEVELstringAggregation level of the row - NETWORK totals beside state-level and smaller-area cutsNETWORK
AREAstringGeographic basis of the aggregation, from the pan-European region down to individual statesECAC
FOCUS_TYPEstringWhich analytical cut the row represents within its level and areaAREA FOCUS
YEARintegerCalendar year of the observation bucket2019
MONTHintegerCalendar month of the observation bucket; modelled window runs January 2019 through December 20241
MARKET_SEGMENTstringTraffic market-segment classification, separating scheduled from business and other trafficbusiness
FLIGHT_TYPEstringMovement class within the segment, keeping departures and arrivals in separate bucketsD
FLIGHT_PHASEstringPhase of flight for emissions attribution - cruise, taxi, climb, approachcruise
NB_FLIGHTSnumberCount of flights inside the aggregation bucket3247
CO2_TONSnumberCarbon dioxide mass attributed to the bucket, tonnes26607.3
NOX_KGnumberNitrogen oxides mass attributed to the bucket, kilograms91683.56
SOX_KGnumberSulphur oxides mass attributed to the bucket, kilograms7080.21

Coverage at a glance

chipvalue
GeographyECAC area via EUROCONTROL member states - network, state, FIR, area-control-unit, airport and ANSP levels under one scheme
TemporalStaggered starts: CO2 by state from January 2010; en-route flights and ATFM delays from January 2011; flight efficiency from 2014; airport traffic from January 2016; modelled emissions January 2019 - December 2024; dashboards current to the previous day
GranularityDaily for delay, traffic and efficiency series; monthly for emissions, ASMA and taxi measures; yearly for ACE operational and ANSP financial lines

What teams do with it

  • Airline demand and capacity modelling Day-level en-route flight counts by state, FIR and control unit give demand models a decade-plus of European history, with the dashboards' evolution curves providing the sanity check before a forecast ships.
  • Delay-cause attribution studies ATFM delay split by IATA cause code separates weather-driven holding from capacity and staffing shortfalls, the distinction route planners and regulators argue over whenever a summer season goes wrong.
  • Aviation emissions baselining and ESG reporting Gate-to-gate CO2, NOx and SOx by market segment and flight phase, plus measured CO2-by-state back to 2010, gives sustainability teams a citable institutional denominator for aviation footprint claims.
  • Airport and ANSP benchmarking Airport traffic, ASMA additional time, taxi times and slot adherence sit beside ACE cost lines, so operational efficiency and provider economics land in the same table instead of two incompatible spreadsheets.
  • Policy and airspace-reform analysis Horizontal flight-efficiency and complexity indicators measure how directly Europe actually flies - the baseline any functional airspace block restructuring argument has to start from.
  • Citation-grade journalism and research Traffic recovery, punctuality collapse and aviation-emissions stories stand up under review when the numbers come from the organisation that operates the network itself.

Questions buyers ask

What does the eurocontrol aviation data dashboard data contain?

Two registers of European air traffic: daily dashboards showing network flight counts with evolution curves, top-40 airline and airport rankings, CODA passenger-delay graphics and ATFM delay analyses by IATA cause code; and more than twenty statistical series delivered as tables - gate-to-gate CO2, NOx and SOx emissions by market segment and flight phase, en-route IFR flights, ATFM delays, airport traffic, ASMA additional time, taxi times, flight efficiency, slot adherence, complexity and ANSP cost lines - with histories reaching back to January 2010.

How far back does it go?

Staggered by series rather than one cutoff: CO2 by state starts January 2010, en-route IFR flights and ATFM delays January 2011 with the flight-information-region basis added in 2013, horizontal flight efficiency 2014, airport traffic January 2016, and the modelled gate-to-gate emissions window runs January 2019 through December 2024. Daily dashboards reflect traffic current to the previous day. Every extract states its own span up front, so gaps never surprise you mid-analysis.

How does this differ from the ANSperf ATC performance dataset?

Attribution versus topicality. ANSperf is the Performance Review Unit's instrument for answering who-and-why questions - delay decomposed by cause code at state, ANSP and functional-airspace-block level. This collection is the topical counterpart: dashboards that show yesterday's network today, plus the broadest single sweep of series including the emissions panel and CRCO unit rates. Delay studies that need provider-level attribution start with ANSperf; market watches and emissions baselines start here. Many teams take both, joined on shared keys.

Is the emissions data measured or modelled?

Both, and the distinction matters enough that we label it in every delivery. The gate-to-gate series is a modelled estimate covering January 2019 through December 2024, built from observed movement patterns. The Small Emitters Tool CO2-by-state series is measured-based reporting running monthly from January 2010 through June 2026. Requesting both puts a modelled-versus-measured cross-check in one table on shared state keys.

What geographies can the series be cut on?

The full ECAC area under one scheme: network-wide aggregates, individual member states, flight information regions, area control units, airports and air navigation service providers. Because every level lives in the same tables with LEVEL and AREA columns distinguishing them, moving from a European view to a single-country or single-provider view is a filter operation, not a new procurement.

Can a sample be scoped to my states, series and years?

Yes, and that is the default. Name the countries or levels, the series - the emissions panel alone, or delays plus traffic plus efficiency - and the period range: one series across the full history since 2010, or five recent quarters across every series. The sample returns exactly that slice with the complete field dictionary attached, in the same schema the production feed uses, so joins built during evaluation survive unchanged.

Notes on this record

  • Scored 9/10 Datadory scores this record 9 of 10 on its rubric against a cross-catalog mean of 7.81 across 1,744 datasets - field definitions verified end to end with sample evidence attached.

Datasets that pair with this one

See the rows before you pay anything.

Name this dataset and we send real records from it — scoped to the fields you asked for.

See pricing