Dataset was introduced by Toby Seagaran in his book Programming Collective Intelligence.

The columns are: Departure airport code, Arrival airport code , Time of Arrival(24h), Time of Departure(24h), Cost (USD)

Problem Definition

Planning a trip for a group of people from different locations all arriving at the same place is always a challenge, and it makes for an interesting optimization problem. In our situation group members are from all over the country and wish to meet up at a prticular location say New York. They will all arrive on the same day and leave on the same day, and they would like to share transportation to and from the airport. There are dozens of flights per day to New York from any of the family members’ locations, all leaving at different times.

For more information and examples check out github.com/Agrover112/fliscopt/examples

Daily data showing UK flight numbers and rolling seven-day average, including flights to, from, and within the UK. These are official statistics in development. Source: EUROCONTROL.

As new technologies are developed to handle the complexities of the Next Generation Air Transportation System (NextGen), it is increasingly important to address both current and future safety concerns along with the operational, environmental, and efficiency issues within the National Airspace System (NAS). In recent years, the Federal Aviation Administration’s (FAA) safety offices have been researching ways to utilize the many safety databases maintained by the FAA, such as those involving flight recorders, radar tracks, weather, and many other high-volume sensors, in order to monitor this unique and complex system. Although a number of current technologies do monitor the frequency of known safety risks in the NAS, very few methods currently exist that are capable of analyzing large data repositories with the purpose of discovering new and previously unmonitored safety risks. While monitoring the frequency of known events in the NAS enables mitigation of already identified problems, a more proactive approach of finding unidentified issues still needs to be addressed. This is especially important in the proactive identification of new, emergent safety issues that may result from the planned introduction of advanced NextGen air traffic management technologies and procedures. Development of an automated tool that continuously evaluates the NAS to discover both events exhibiting flight characteristics indicative of safety-related concerns as well as operational anomalies will heighten the awareness of such situations in the aviation community and serve to increase the overall safety of the NAS. This paper discusses the extension of previous anomaly detection work to identify operationally significant flights within the highly complex airspace encompassing the New York area of operations, focusing on the major airports of Newark International (EWR), LaGuardia International (LGA), and John F. Kennedy International (JFK). In addition, flight traffic in the vicinity of Denver International (DEN) airport/airspace is also investigated to evaluate the impact on operations due to variances in seasonal weather and airport elevation. From our previous research, subject matter experts determined that some of the identified anomalies were significant, but could not reach conclusive findings without additional supportive data. To advance this research further, causal examination using domain experts is continued along with the integration of air traffic control (ATC) voice data to shed much needed insight into resolving which flight characteristic(s) may be impacting an aircraft's unusual profile. Once a flight characteristic is identified, it could be included in a list of potential safety precursors. This paper also describes a process that has been developed and implemented to automatically identify and produce daily reports on flights of interest from the previous day.

Airlines Traffic Passenger Statistics

A New Look at an Old Problem

About this dataset

This dataset contains information on air traffic passenger statistics by the airline. It includes information on the airlines, airports, and regions that the flights departed from and arrived at. It also includes information on the type of activity, price category, terminal, boarding area, and number of passengers

How to use the dataset

Air traffic passenger statistics can be a useful tool for understanding the airline industry and for making travel plans. This dataset from Open Flights contains information on air traffic passenger statistics by airline for 2017. The data includes the number of passengers, the operating airline, the published airline, the geographic region, the activity type code, the price category code, the terminal, the boarding area, and the year and month of the flight

Research Ideas

• Air traffic passenger statistics could be used to predict future trends in air travel.
• The data could be used to generate heat maps of airline traffic patterns.
• The data could be used to study the effects of different factors on air traffic passenger numbers, such as the time of year or day, the price of airfare, or the number of flights offered by an airline

License

License: Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) - You are free to: - Share - copy and redistribute the material in any medium or format for non-commercial purposes only. - Adapt - remix, transform, and build upon the material for non-commercial purposes only. - You must: - Give appropriate credit - Provide a link to the license, and indicate if changes were made. - ShareAlike - You must distribute your contributions under the same license as the original. - You may not: - Use the material for commercial purposes.

Columns

File: Air_Traffic_Passenger_Statistics.csv | Column name | Description | |:--------------------------------|:------------------------------------------------------------------------------| | Activity Period | The date of the activity. (Date) | | Operating Airline | The airline that operated the flight. (String) | | Operating Airline IATA Code | The IATA code of the airline that operated the flight. (String) | | Published Airline | The airline that published the fare for the flight. (String) | | Published Airline IATA Code | The IATA code of the airline that published the fare for the flight. (String) | | GEO Summary | A summary of the geographic region. (String) | | GEO Region | The geographic region. (String) | | Activity Type Code | The type of activity. (String) | | Price Category Code | The price category of the fare. (String) | | Terminal | The terminal of the flight. (String) | | Boarding Area | The boarding area of the flight. (String) | | Passenger Count | The number of passengers on the flight. (Integer) | | Adjusted Activity Type Code | The type of activity, adjusted for missing data. (String) | | Adjusted Passenger Count | The number of passengers on the flight, adjusted for missing data. (Integer) | | Year | The year of the activity. (Integer) | | Month | The month of the activity. (Integer) |

Airline on-time performance Have you ever been stuck in an airport because your flight was delayed or canceled and wondered if you could have predicted it if you'd had more data? This is your chance to find out.

The results We had a total of nine entries, and turn out at the poster session at the JSM was great, with plenty of people stopping by to find out why their flights were delayed.

The data The data consists of flight arrival and departure details for all commercial flights within the USA, from October 1987 to April 2008. This is a large dataset: there are nearly 120 million records in total and takes up 1.6 gigabytes of space when compressed and 12 gigabytes when uncompressed.

The challenge The aim of the data expo is to provide a graphical summary of important features of the data set. This is intentionally vague in order to allow different entries to focus on different aspects of the data, but here are a few ideas to get you started:

When is the best time of day/day of week/time of year to fly to minimise delays? Do older planes suffer more delays? How does the number of people flying between different locations change over time? How well does weather predict plane delays? Can you detect cascading failures as delays in one airport create delays in others? Are there critical links in the system? You are also welcome to work with interesting subsets: you might want to compare flight patterns before and after 9/11, or between the pair of cities that you fly between most often, or all flights to and from a major airport like Chicago (ORD). Smaller subsets may also help you to match up the data to other interesting datasets.

Columns | Name|Description| | --- | --- | |year| 1987-2008| |month| 1-12| |day of month| 1-31| |day of week| 1 (Monday) - 7 (Sunday)| |DepTime| actual departure time (minutes)| |CRSDepTime| scheduled departure time (minutes) |ArrTime| actual arrival time (minutes)| |CRSArrTime| scheduled arrival time (minutes)| |UniqueCarrier| unique carrier code| |FlightNum| flight number| |TailNum| plane tail number| |ActualElapsedTime| in minutes| |CRSElapsedTime| in minutes| |AirTime| in minutes| |ArrDelay| arrival delay, in minutes| |DepDelay| departure delay, in minutes| |Origin| origin IATA airport code| |Dest| destination IATA airport code| |Distance| in miles| |TaxiIn| taxi in time, in minutes| |TaxiOut| taxi out time in minutes| |Cancelled| was the flight cancelled?| |CancellationCode| reason for cancellation (A = carrier, B = weather, C = NAS, D = security)| |Diverted| 1 = yes, 0 = no| |CarrierDelay| in minutes| |WeatherDelay| in minutes| |NASDelay| in minutes| |SecurityDelay| in minutes| |LateAircraftDelay| in minutes|

Motivation

The data in this dataset is derived and cleaned from the full OpenSky dataset to illustrate the development of air traffic during the COVID-19 pandemic. It spans all flights seen by the network's more than 2500 members since 1 January 2019. More data has been periodically included in the dataset until the end of the COVID-19 pandemic.

We stopped updating the dataset after December 2022. Previous files have been fixed after a thorough sanity check.

License

See LICENSE.txt

Disclaimer

The data provided in the files is provided as is. Despite our best efforts at filtering out potential issues, some information could be erroneous.

Origin and destination airports are computed online based on the ADS-B trajectories on approach/takeoff: no crosschecking with external sources of data has been conducted. Fields origin or destination are empty when no airport could be found.

Aircraft information come from the OpenSky aircraft database. Fields typecode and registration are empty when the aircraft is not present in the database.

Description of the dataset

One file per month is provided as a csv file with the following features:

callsign: the identifier of the flight displayed on ATC screens (usually the first three letters are reserved for an airline: AFR for Air France, DLH for Lufthansa, etc.)

number: the commercial number of the flight, when available (the matching with the callsign comes from public open API); this field may not be very reliable;

icao24: the transponder unique identification number;

registration: the aircraft tail number (when available);

typecode: the aircraft model type (when available);

origin: a four letter code for the origin airport of the flight (when available);

destination: a four letter code for the destination airport of the flight (when available);

firstseen: the UTC timestamp of the first message received by the OpenSky Network;

lastseen: the UTC timestamp of the last message received by the OpenSky Network;

day: the UTC day of the last message received by the OpenSky Network;

latitude_1, longitude_1, altitude_1: the first detected position of the aircraft;

latitude_2, longitude_2, altitude_2: the last detected position of the aircraft.

Examples

Possible visualisations and a more detailed description of the data are available at the following page:

Credit

If you use this dataset, please cite:

Martin Strohmeier, Xavier Olive, Jannis Lübbe, Matthias Schäfer, and Vincent Lenders "Crowdsourced air traffic data from the OpenSky Network 2019–2020" Earth System Science Data 13(2), 2021 https://doi.org/10.5194/essd-13-357-2021

The number of flights performed globally by the airline industry has increased steadily since the early 2000s and reached **** million in 2019. However, due to the coronavirus pandemic, the number of flights dropped to **** million in 2020. The flight volume increased again in the following years and was forecasted to reach ** million in 2025.

Multivariate regression data set from: https://link.springer.com/article/10.1007%2Fs10994-016-5546-z : The Airline Ticket Price dataset concerns the prediction of airline ticket prices. The rows are a sequence of time-ordered observations over several days. Each sample in this dataset represents a set of observations from a specific observation date and departure date pair. The input variables for each sample are values that may be useful for prediction of the airline ticket prices for a specific departure date. The target variables in these datasets are the next day (ATP1D) price or minimum price observed over the next 7 days (ATP7D) for 6 target flight preferences: (1) any airline with any number of stops, (2) any airline non-stop only, (3) Delta Airlines, (4) Continental Airlines, (5) Airtrain Airlines, and (6) United Airlines. The input variables include the following types: the number of days between the observation date and the departure date (1 feature), the boolean variables for day-of-the-week of the observation date (7 features), the complete enumeration of the following 4 values: (1) the minimum price, mean price, and number of quotes from (2) all airlines and from each airline quoting more than 50 % of the observation days (3) for non-stop, one-stop, and two-stop flights, (4) for the current day, previous day, and two days previous. The result is a feature set of 411 variables. For specific details on how these datasets are constructed please consult Groves and Gini (2015). The nature of these datasets is heterogeneous with a mixture of several types of variables including boolean variables, prices, and counts.

The "flights.csv" dataset contains information about the flights of an airport. This dataset includes information such as departure and arrival time, delays, flight company, flight number, flight origin and destination, flight duration, distance, hour and minute of flight, and exact date and time of flight. This data can be used in management analysis and strategies and provide useful information about the performance of flights and placement companies. The analysis of the data in this dataset can be used as a basis for the following activities: - Analysis of time patterns and trends: by examining the departure and arrival time of the aircraft, changes and time changes, patterns and trends in flight behavior can be identified. - Analysis of American companies: By viewing information about airlines such as the number of flights, the impact and overall performance, you can compare and analyze the performance of each company. - Analysis of delays and service quality: By examining delays and arrival time, I can collect and analyze information about the quality of services provided by the airport and companies. - Analysis of flight routes: by checking the origin and destination of flights, distances and flight duration, popular routes and people's choices can be identified and analyzed. - Analysis of airport performance: by observing the characteristics of flights and airport performance, it is possible to identify and analyze the strengths and weaknesses of the airport and suggest improvements.

It provides various tools for data analysis and visualization and can be used as a basis for managerial decisions in the field of aviation industry.

Airline Company Codes (in order of frequency for this dataset)

WN -- Southwest Airlines Co.

DL -- Delta Air Lines Inc.

AA -- American Airlines Inc.

UA -- United Air Lines Inc.

B6 -- JetBlue Airways

AS -- Alaska Airlines Inc.

NK -- Spirit Air Lines

G4 -- Allegiant Air

F9 -- Frontier Airlines Inc.

HA -- Hawaiian Airlines Inc.

SY -- Sun Country Airlines d/b/a MN Airlines

VX -- Virgin America

Passengers enplaned and deplaned at Canadian airports, annual.

In 2023, the estimated number of scheduled passengers boarded by the global airline industry amounted to approximately *** billion people. This represents a significant increase compared to the previous year since the pandemic started and the positive trend was forecast to continue in 2024, with the scheduled passenger volume reaching just below **** billion travelers. Airline passenger traffic The number of scheduled passengers handled by the global airline industry has increased in all but one of the last decade. Scheduled passengers refer to the number of passengers who have booked a flight with a commercial airline. Excluded are passengers on charter flights, whereby an entire plane is booked by a private group. In 2023, the Asia Pacific region had the highest share of airline passenger traffic, accounting for ********* of the global total.

United States No. of Flights: JFK Terminal: 1 data was reported at 30.000 Unit in 30 Nov 2025. This records a decrease from the previous number of 33.000 Unit for 29 Nov 2025. United States No. of Flights: JFK Terminal: 1 data is updated daily, averaging 0.000 Unit from May 2008 (Median) to 30 Nov 2025, with 6413 observations. The data reached an all-time high of 0.000 Unit in 30 Nov 2025 and a record low of 0.000 Unit in 30 Nov 2025. United States No. of Flights: JFK Terminal: 1 data remains active status in CEIC and is reported by U.S. Customs and Border Protection. The data is categorized under Global Database’s United States – Table US.TA: Airport Statistics: Number of Flights: by Airport. [COVID-19-IMPACT]

BACKGROUND The data contained in the compressed file has been extracted from the Marketing Carrier On-Time Performance (Beginning January 2018) data table of the "On-Time" database from the TranStats data library. The time period is indicated in the name of the compressed file; for example, XXX_XXXXX_2001_1 contains data of the first month of the year 2001.

RECORD LAYOUT Below are fields in the order that they appear on the records: Year Year Quarter Quarter (1-4) Month Month DayofMonth Day of Month DayOfWeek Day of Week FlightDate Flight Date (yyyymmdd) Marketing_Airline_Network Unique Marketing Carrier Code. When the same code has been used by multiple carriers, a numeric suffix is used for earlier users, for example, PA, PA(1), PA(2). Use this field for analysis across a range of years. Operated_or_Branded_Code_Share_Partners Reporting Carrier Operated or Branded Code Share Partners DOT_ID_Marketing_Airline An identification number assigned by US DOT to identify a unique airline (carrier). A unique airline (carrier) is defined as one holding and reporting under the same DOT certificate regardless of its Code, Name, or holding company/corporation. IATA_Code_Marketing_Airline Code assigned by IATA and commonly used to identify a carrier. As the same code may have been assigned to different carriers over time, the code is not always unique. For analysis, use the Unique Carrier Code. Flight_Number_Marketing_Airline Flight Number Originally_Scheduled_Code_Share_Airline Unique Scheduled Operating Carrier Code. When the same code has been used by multiple carriers, a numeric suffix is used for earlier users,for example, PA, PA(1), PA(2). Use this field for analysis across a range of years. DOT_ID_Originally_Scheduled_Code_Share_Airline An identification number assigned by US DOT to identify a unique airline (carrier). A unique airline (carrier) is defined as one holding and reporting under the same DOT certificate regardless of its Code, Name, or holding company/corporation. IATA_Code_Originally_Scheduled_Code_Share_Airline Code assigned by IATA and commonly used to identify a carrier. As the same code may have been assigned to different carriers over time, the code is not always unique. For analysis, use the Unique Carrier Code. Flight_Num_Originally_Scheduled_Code_Share_Airline Flight Number Operating_Airline Unique Carrier Code. When the same code has been used by multiple carriers, a numeric suffix is used for earlier users, for example, PA, PA(1), PA(2). Use this field for analysis across a range of years. DOT_ID_Operating_Airline An identification number assigned by US DOT to identify a unique airline (carrier). A unique airline (carrier) is defined as one holding and reporting under the same DOT certificate regardless of its Code, Name, or holding company/corporation. IATA_Code_Operating_Airline Code assigned by IATA and commonly used to identify a carrier. As the same code may have been assigned to different carriers over time, the code is not always unique. For analysis, use the Unique Carrier Code. Tail_Number Tail Number Flight_Number_Operating_Airline Flight Number OriginAirportID Origin Airport, Airport ID. An identification number assigned by US DOT to identify a unique airport. Use this field for airport analysis across a range of years because an airport can change its airport code and airport codes can be reused. OriginAirportSeqID Origin Airport, Airport Sequence ID. An identification number assigned by US DOT to identify a unique airport at a given point of time. Airport attributes, such as airport name or coordinates, may change over time. OriginCityMarketID Origin Airport, City Market ID. City Market ID is an identification number assigned by US DOT to identify a city market. Use this field to consolidate airports serving the same city market. Origin Origin Airport OriginCityName Origin Airport, City Name OriginState Origin Airport, State Code OriginStateFips Origin Airport, State Fips OriginStateName Origin Airport, State Name OriginWac Origin Airport, World Area Code DestAirportID Destination Airport, Airport ID. An identification number assigned by US DOT to identify a unique airport. Use this field for airport analysis across a range of years because an airport can change its airport code and airport codes can be reused. DestAirportSeqID Destination Airport, Airport Sequence ID. An identification number assigned by US DOT to identify a unique airport at a given point of time. Airport attributes, such as airport name or coordinates, may change over time. DestCityMarketID Destination Airport, City Market ID. City Market ID is an identification number assigned by US DOT to identify a city market. Use this field to consolidate airports serving the same city market. Dest Destination Airport DestCityName Destination Airport, City Name DestState Destination Airport, State Code DestStateFips De...

Geospatial Dataset of GNSS Anomalies and Political Violence Events (2023)

Overview

The Geospatial Dataset of GNSS Anomalies and Political Violence Events (2023) is a collection of data that integrates aircraft flight information, GNSS (Global Navigation Satellite System) anomalies, and political violence events from the ACLED (Armed Conflict Location & Event Data Project) database.

Dataset Files

The dataset consists of two CSV files:

Daily_GNSS_Anomalies_and_ACLED-2023-V1.csv

Description: Contains all grids and dates that had aircraft traffic during 2023.

Number of Records: 6,777,228

Purpose: Provides a complete view of aircraft movements and associated data, including grids without any GNSS anomalies.

Daily_GNSS_Anomalies_and_ACLED-2023-V2.csv

Description: A filtered version of V1, including only the grids and dates where GNSS anomalies (jumps or gaps) were reported.

Number of Records: 718,237

Purpose: Focuses on areas and times with GNSS anomalies for targeted analysis.

Data Fields

Both files share the same set of fields, which are detailed below:

grid_id

Description: Unique identifier for a grid cell on Earth measuring 0.5 degrees latitude by 0.5 degrees longitude.

Format: String combining latitude and longitude (e.g., -10.0_-36.0).

day

Description: Date of the recorded data.

Format: YYYY-MM-DD (e.g., 2023-03-28).

geometry

Description: Polygon coordinates of the grid cell in Well-Known Text (WKT) format.

Format: POLYGON((longitude latitude, ...)) (e.g., POLYGON((-36.0 -10.0, -35.5 -10.0, -35.5 -9.5, -36.0 -9.5, -36.0 -10.0))).

flights

Description: Number of aircraft flights that passed through the grid on that day.

Format: Integer (e.g., 28).

GPS_jumps

Description: Number of reported GNSS "jump" anomalies (possible spoofing incidents) in the grid on that day.

Format: Integer (e.g., 1).

GPS_gaps

Description: Number of reported GNSS "gap" anomalies, indicating gaps in aircraft routes, in the grid on that day.

Format: Integer (e.g., 0).

gaps_density

Description: Density of GNSS gaps, calculated as the number of gaps divided by the number of flights.

Format: Decimal (e.g., 0).

jumps_density

Description: Density of GNSS jumps, calculated as the number of jumps divided by the number of flights.

Format: Decimal (e.g., 0.035714286).

event_id_cnty

Description: ACLED event ID corresponding to political violence events in the grid on that day.

Format: String (e.g., BRA69267).

disorder_type

Description: Type of disorder as classified by ACLED (e.g., "Political violence").

Format: String.

event_type

Description: General category of the event according to ACLED (e.g., "Violence against civilians").

Format: String.

sub_event_type

Description: Specific subtype of the event as per ACLED classification (e.g., "Attack").

Format: String.

acled_count

Description: Number of ACLED events in the grid on that day.

Format: Integer (e.g., 1).

acled_flag

Description: Indicator of ACLED event presence in the grid on that day (0 for no events, 1 for one or more events).

Format: Integer (0 or 1).

Data Sources

GNSS Anomalies Data:

Calculated from ADS-B (Automatic Dependent Surveillance-Broadcast) messages obtained via the OpenSky Network's Trino database.

GNSS anomalies include "jumps" (potential spoofing incidents) and "gaps" (interruptions in aircraft route data).

Political Violence Events Data:

Sourced from the ACLED database, which provides detailed information on political violence and protest events worldwide.

Temporal and Spatial Coverage

Temporal Coverage:

From January 1, 2023, to December 31, 2023.

Daily records provide temporal granularity for time-series analysis.

Spatial Coverage:

Global coverage with grid cells measuring 0.5 degrees latitude by 0.5 degrees longitude.

Each grid cell represents an area on Earth's surface, facilitating spatial analysis.

Usage and Applications

Security Analysis:

Assess potential correlations between GNSS anomalies and political violence events.

Identify regions with increased risk of GNSS spoofing or signal disruption.

Research and Development:

Develop models to predict socio-political events based on GNSS anomalies.

Study the impact of political instability on aviation safety.

Policy and Decision Making:

Inform aviation authorities and policymakers about regions requiring enhanced navigation security measures.

Support conflict analysis and monitoring efforts.

Large go-around, also referred to as missed approach, data set. The data set is in support of the paper presented at the OpenSky Symposium on November the 10th.

If you use this data for a scientific publication, please consider citing our paper.

The data set contains landings from 176 (mostly) large airports from 44 different countries. The landings are labelled as performing a go-around (GA) or not. In total, the data set contains almost 9 million landings with more than 33000 GAs. The data was collected from OpenSky Network's historical data base for the year 2019. The published data set contains multiple files:

go_arounds_minimal.csv.gz

Compressed CSV containing the minimal data set. It contains a row for each landing and a minimal amount of information about the landing, and if it was a GA. The data is structured in the following way:

    Column name
    Type
    Description




    time
    date time
    UTC time of landing or first GA attempt


    icao24
    string
    Unique 24-bit (hexadecimal number) ICAO identifier of the aircraft concerned


    callsign
    string
    Aircraft identifier in air-ground communications


    airport
    string
    ICAO airport code where the aircraft is landing


    runway
    string
    Runway designator on which the aircraft landed


    has_ga
    string
    "True" if at least one GA was performed, otherwise "False"


    n_approaches
    integer
    Number of approaches identified for this flight


    n_rwy_approached
    integer
    Number of unique runways approached by this flight

The last two columns, n_approaches and n_rwy_approached, are useful to filter out training and calibration flight. These have usually a large number of n_approaches, so an easy way to exclude them is to filter by n_approaches > 2.

go_arounds_augmented.csv.gz

Compressed CSV containing the augmented data set. It contains a row for each landing and additional information about the landing, and if it was a GA. The data is structured in the following way:

    Column name
    Type
    Description




    time
    date time
    UTC time of landing or first GA attempt


    icao24
    string
    Unique 24-bit (hexadecimal number) ICAO identifier of the aircraft concerned


    callsign
    string
    Aircraft identifier in air-ground communications


    airport
    string
    ICAO airport code where the aircraft is landing


    runway
    string
    Runway designator on which the aircraft landed


    has_ga
    string
    "True" if at least one GA was performed, otherwise "False"


    n_approaches
    integer
    Number of approaches identified for this flight


    n_rwy_approached
    integer
    Number of unique runways approached by this flight


    registration
    string
    Aircraft registration


    typecode
    string
    Aircraft ICAO typecode


    icaoaircrafttype
    string
    ICAO aircraft type


    wtc
    string
    ICAO wake turbulence category


    glide_slope_angle
    float
    Angle of the ILS glide slope in degrees


    has_intersection

string

    Boolean that is true if the runway has an other runway intersecting it, otherwise false


    rwy_length
    float
    Length of the runway in kilometre


    airport_country
    string
    ISO Alpha-3 country code of the airport


    airport_region
    string
    Geographical region of the airport (either Europe, North America, South America, Asia, Africa, or Oceania)


    operator_country
    string
    ISO Alpha-3 country code of the operator


    operator_region
    string
    Geographical region of the operator of the aircraft (either Europe, North America, South America, Asia, Africa, or Oceania)


    wind_speed_knts
    integer
    METAR, surface wind speed in knots


    wind_dir_deg
    integer
    METAR, surface wind direction in degrees


    wind_gust_knts
    integer
    METAR, surface wind gust speed in knots


    visibility_m
    float
    METAR, visibility in m


    temperature_deg
    integer
    METAR, temperature in degrees Celsius


    press_sea_level_p
    float
    METAR, sea level pressure in hPa


    press_p
    float
    METAR, QNH in hPA


    weather_intensity
    list
    METAR, list of present weather codes: qualifier - intensity


    weather_precipitation
    list
    METAR, list of present weather codes: weather phenomena - precipitation


    weather_desc
    list
    METAR, list of present weather codes: qualifier - descriptor


    weather_obscuration
    list
    METAR, list of present weather codes: weather phenomena - obscuration


    weather_other
    list
    METAR, list of present weather codes: weather phenomena - other

This data set is augmented with data from various public data sources. Aircraft related data is mostly from the OpenSky Network's aircraft data base, the METAR information is from the Iowa State University, and the rest is mostly scraped from different web sites. If you need help with the METAR information, you can consult the WMO's Aerodrom Reports and Forecasts handbook.

go_arounds_agg.csv.gz

Compressed CSV containing the aggregated data set. It contains a row for each airport-runway, i.e. every runway at every airport for which data is available. The data is structured in the following way:

    Column name
    Type
    Description




    airport
    string
    ICAO airport code where the aircraft is landing


    runway
    string
    Runway designator on which the aircraft landed


    n_landings
    integer
    Total number of landings observed on this runway in 2019


    ga_rate
    float
    Go-around rate, per 1000 landings


    glide_slope_angle
    float
    Angle of the ILS glide slope in degrees


    has_intersection
    string
    Boolean that is true if the runway has an other runway intersecting it, otherwise false


    rwy_length
    float
    Length of the runway in kilometres


    airport_country
    string
    ISO Alpha-3 country code of the airport


    airport_region
    string
    Geographical region of the airport (either Europe, North America, South America, Asia, Africa, or Oceania)

This aggregated data set is used in the paper for the generalized linear regression model.

Downloading the trajectories

Users of this data set with access to OpenSky Network's Impala shell can download the historical trajectories from the historical data base with a few lines of Python code. For example, you want to get all the go-arounds of the 4th of January 2019 at London City Airport (EGLC). You can use the Traffic library for easy access to the database:

import datetime from tqdm.auto import tqdm import pandas as pd from traffic.data import opensky from traffic.core import Traffic

load minimum data set

df = pd.read_csv("go_arounds_minimal.csv.gz", low_memory=False) df["time"] = pd.to_datetime(df["time"])

select London City Airport, go-arounds, and 2019-01-04

airport = "EGLC" start = datetime.datetime(year=2019, month=1, day=4).replace( tzinfo=datetime.timezone.utc ) stop = datetime.datetime(year=2019, month=1, day=5).replace( tzinfo=datetime.timezone.utc )

df_selection = df.query("airport==@airport & has_ga & (@start <= time <= @stop)")

iterate over flights and pull the data from OpenSky Network

flights = [] delta_time = pd.Timedelta(minutes=10) for _, row in tqdm(df_selection.iterrows(), total=df_selection.shape[0]): # take at most 10 minutes before and 10 minutes after the landing or go-around start_time = row["time"] - delta_time stop_time = row["time"] + delta_time

# fetch the data from OpenSky Network
flights.append(
  opensky.history(
    start=start_time.strftime("%Y-%m-%d %H:%M:%S"),
    stop=stop_time.strftime("%Y-%m-%d %H:%M:%S"),
    callsign=row["callsign"],
    return_flight=True,
  )
)

The flights can be converted into a Traffic object

Traffic.from_flights(flights)

Additional files

Additional files are available to check the quality of the classification into GA/not GA and the selection of the landing runway. These are:

validation_table.xlsx: This Excel sheet was manually completed during the review of the samples for each runway in the data set. It provides an estimate of the false positive and false negative rate of the go-around classification. It also provides an estimate of the runway misclassification rate when the airport has two or more parallel runways. The columns with the headers highlighted in red were filled in manually, the rest is generated automatically.

validation_sample.zip: For each runway, 8 batches of 500 randomly selected trajectories (or as many as available, if fewer than 4000) classified as not having a GA and up to 8 batches of 10 random landings, classified as GA, are plotted. This allows the interested user to visually inspect a random sample of the landings and go-arounds easily.

In 2022, the number of total flights of Vietnam Airlines amounted to approximately *** thousand, indicating a significant increase compared to previous year. Vietnam Airlines is a state-owned enterprise and is among Southeast Asia's leading airline groups.

This dataset provides flight track and aircraft navigation data from the NASA Atmospheric Tomography Mission (ATom). Flight track information is available for the four ATom campaigns: ATom-1, ATom-2, ATom-3, and ATom-4. Each ATom campaign consists of multiple individual flights and flight navigational information is recorded in 10-second intervals. Data available for each flight includes research flight number, date, and start and stop time of each 10-second interval. In addition, latitude, longitude, altitude, pressure and temperature is included at each 10-second interval. NASA's ATom campaign deploys an extensive gas and aerosol payload on the NASA DC-8 aircraft for systematic, global-scale sampling of the atmosphere, profiling continuously from 0.2 to 12 km altitude. Flights occurred in each of 4 seasons from 2016 to 2018. During each campaign, flights originate from the Armstrong Flight Research Center in Palmdale, California, fly north to the western Arctic, south to the South Pacific, east to the Atlantic, north to Greenland, and return to California across central North America. ATom establishes a single, contiguous, global-scale dataset. One intended use of this flight track data is to facilitate to mapping model results from global models onto the precise ATom flight tracks for comparison.

China Air: Passenger Traffic: Domestic data was reported at 664.657 Person mn in 2024. This records an increase from the previous number of 590.516 Person mn for 2023. China Air: Passenger Traffic: Domestic data is updated yearly, averaging 95.618 Person mn from Dec 1970 (Median) to 2024, with 42 observations. The data reached an all-time high of 664.657 Person mn in 2024 and a record low of 0.210 Person mn in 1970. China Air: Passenger Traffic: Domestic data remains active status in CEIC and is reported by Civil Aviation Administration of China. The data is categorized under China Premium Database’s Transportation and Storage Sector – Table CN.TI: Air: Passenger Traffic.

Total monthly number of passengers arriving to and departing from Heathrow Airport, including both international and domestic flights.