DOI: 10.5281/zenodo.3937483
title: Reference datasets for in-flight emergency situations

description: <strong>Motivation</strong> The data in this dataset is derived and cleaned from the full OpenSky dataset in order to illustrate in-flight emergency situations triggering the 7700 transponder code. It spans flights seen by the network's more than 2500 members between 1 January 2018 and 29 January 2020. The dataset complements the following publication: Xavier Olive, Axel Tanner, Martin Strohmeier, Matthias Schäfer, Metin Feridun, Allan Tart, Ivan Martinovic and Vincent Lenders.<br> "OpenSky Report 2020: Analysing in-flight emergencies using big data".<br> In <em>2020 IEEE/AIAA 39th Digital Avionics Systems Conference (DASC)</em><em>,</em> October 2020 <strong>License</strong> See LICENSE.txt <strong>Disclaimer</strong> The data provided in the files is provided as is. Despite our best efforts at filtering out potential issues, some information could be erroneous. Most aircraft information come from the OpenSky aircraft database and have been filled with manual research from various sources on the Internet. Most information about flight plans has been automatically fetched and processed using open APIs; some manual processing was required to cross-check, correct erroneous and fill missing information. <strong>Description of the dataset</strong> Two files are provided in the dataset: one compressed parquet file with trajectory information; one metadata CSV file with the following features: <strong>flight_id</strong>: a unique identifier for each trajectory; <strong>callsign</strong>: ICAO flight callsign information; <strong>number</strong>: IATA flight number, when available; <strong>icao24</strong>, <strong>registration</strong>, <strong>typecode</strong>: information about the aircraft; <strong>origin</strong>: the origin airport for the aircraft, when available; <strong>landing</strong>: the airport where the aircraft actually landed, when available; <strong>destination</strong>: the intended destination airport, when available; <strong>diverted</strong>: the diversion airport, if applicable, when available; <strong>tweet_problem</strong>, <strong>tweet_result</strong>, <strong>tweet_fueldump</strong>: information extracted from Twitter accounts, about the nature of the issue, the consequence of the emergency and whether the aircraft is known to have dumped fuel; <strong>avh_id</strong>, <strong>avh_problem</strong>, <strong>avh_result</strong>, <strong>avh_fueldump</strong>: information extracted from The Aviation Herald, about the nature of the issue, the consequence of the emergency and whether the aircraft is known to have dumped fuel.<br> The complete URL for each event is https://avherald.com/h?article={avh_id}&opt=1 (replace avh_id by the actual value) <strong>Examples</strong> Additional analyses and visualisations of the data are available at the following page:<br> &lt;https://traffic-viz.github.io/paper/squawk7700.html&gt; <strong>Credit</strong> If you use this dataset, please cite the original OpenSky paper: Xavier Olive, Axel Tanner, Martin Strohmeier, Matthias Schäfer, Metin Feridun, Allan Tart, Ivan Martinovic and Vincent Lenders.<br> "OpenSky Report 2020: Analysing in-flight emergencies using big data".<br> In <em>2020 IEEE/AIAA 39th Digital Avionics Systems Conference (DASC)</em><em>,</em> October 2020 Matthias Schäfer, Martin Strohmeier, Vincent Lenders, Ivan Martinovic and Matthias Wilhelm.<br> "Bringing Up OpenSky: A Large-scale ADS-B Sensor Network for Research".<br> In<em> Proceedings of the 13th IEEE/ACM International Symposium on Information Processing in Sensor Networks (IPSN)</em>, pages 83-94, April 2014. and the traffic library used to derive the data: Xavier Olive.<br> "traffic, a toolbox for processing and analysing air traffic data."<br> <em>Journal of Open Source Software</em> 4(39), July 2019.