The data is supplied by the EUROCONTROL Performance Review Unit and the EUROCONTROL Aviation Sustainability Unit.
The CO2/NOXX/SOX emissions were calculated with the EUROCONTROL Performance Review Unit and the EUROCONTROL Aviation Sustainability Unit Gate-to-Gate methodology which employs the Advanced Emission Model (AEM) which is developed in the EUROCONTROL Innovation Hub by the EUROCONTROL Aviation Sustainability Unit. The values provided in this data set are the historical emissions as displayed on the EUROCONTROL FlyingGreen Platform.
As explained on the FlyingGreen Platform, emission values are calculated with EUROCONTROL tool, Advance Emission Model, and based on the best available actual trajectory data available to EUROCONTROL. The FlyingGreen platform allows the user to select the methodology (‘Area Focus’ or ‘Trajectory (UNFCCC) methodology’), the area of interest , and the traffic of interest (Flight type - DAIO) and returns the fuel burn and emission values based on the user’s selection.
The past emissions are being presented using two different methodologies (these can be selected as filter options on the FlyingGreen platform):
The data in these data sets provided here represent the Area focus methodology. In upcoming releases the available data will be expanded. The gate-to-gate emissions provided here are calculated taking into account the individual trajectories (from gate-to-gate) of each flight and are modeled for all Flying Green flight phases:
In technical terms these Flying Green Flight Phases described above are subdivided in the following so called PRU Sub Phases which are used for the calculations of emissions within the trajectory.
Flying Green Flight Phase | PRU Sub Phase | Start | End |
---|---|---|---|
Taxi-out | Taxi-out | AOBT | ATOT - 42 sec (*) |
Climb | Take-off | ATOT - 42 sec (*) | ATOT |
Climb | Climb-Out | ATOT | First crossing of 3000 ft AGL |
Climb | Climb | First crossing of 3000 ft AGL | Top of Climb |
Cruise | Cruise | Top of Climb | Top of Descent |
Descent | Descent | Top of Descent | Last crossing of 3000 ft AGL |
Descent | Approach | Last crossing of 3000 ft AGL | ALDT |
Descent | Landing | ALDT | ALDT + 40 sec (*) |
Taxi-in | Taxi-in | ALDT + 40 sec (*) | AIBT |
Note(s):
(*): The take-off roll duration is defined to be standard 42 seconds and landing roll duration 40 seconds by the Reference Landing and Take-off (LTO) cycle. See https://data.europa.eu/doi/10.2822/385503.
Abbreviation(s):
Subsequently these emissions are aggregated by the following variables:
For more information on the methodologies see the description under ‘READ MORE’ for NetZero on FlyingGreen.
Column Name | Description | Example Values |
---|---|---|
LEVEL | Indicates the geographic aggregation level of the data. | NETWORK , STATE |
AREA | Defines the area within the selected LEVEL . |
If LEVEL = NETWORK : ECAC , EEA , EU27 , EU27 + EFTA , EUROCONTROL , RP3 If LEVEL = STATE : ISO2 codes such as BE , DE , PT - LISBON FIR , PT - SANTA MARIA FIR |
FOCUS_TYPE | Indicates the methodology used to assign flights to areas. | AREA FOCUS |
YEAR | Year in which the emissions occurred. | 2019 , 2020 , 2021 , 2022 , 2023 , 2024 |
MONTH | Month in which the emissions occurred. | 1 = January through 12 = December |
MARKET_SEGMENT | Type of airline or operational market segment. | business , cargo , lowcost , mainline , other , regional |
FLIGHT_TYPE | Indicates the spatial flight type relative to the area. | A = ArrivalD = DepartureI = InternalO = Overflight |
FLIGHT_PHASE | Segment of the flight in which emissions are calculated. | cruise , descent , climb , taxi-in , taxi-out |
NB_FLIGHTS | Number of flights matching all above criteria. | e.g., 3428 , 444 |
CO2_TONS | Estimated CO₂ emissions (in metric tons) for these flights. | e.g., 23112.0 , 2695.7 |
NOX_KG | Estimated nitrogen oxides (NOₓ) emissions in kilograms. | e.g., 69539.62 , 8766.93 |
SOX_KG | Estimated sulfur oxides (SOₓ) emissions in kilograms. | e.g., 6150.15 , 717.68 |
Use the Gate-to-Gate Emissions dataset when you need:
Note: This dataset is not yet updated monthly — the update process is being developed and will be available in the future.