Publicly available flight data can be automatically downloaded within the package itself. This dataset can also be directly downloaded from here. See the datasheet for additional high-level information about this dataset. Details of the flights are described in the readme files.

Data Summary

For more detailed information about the available fields please reference the flight data readme here. Several fields to pay attention to are as follows:

• flux_a_{x,y,z}, flux_b_{x,y,z}, flux_c_{x,y,z},  and flux_d_{x,y,z} are the available fluxgate (vector) magnetometers. Flux A, C, and D were placed within the cabin, and Flux B was placed at the base of the tail stinger and is considered a truth signal.

• mag_{1,2,3,4,5}_uc are the available uncompensated scalar magnetometers. Mags 2, 3, 4, and 5 were placed within the cabin and are to be treated as the input signal, as these are the signals of interest for compensation. Mag 1 was placed at the end of the tail stinger and is considered a truth signal.

Each flight was split into train and evaluation portions, with the primary consideration being a representative sample of each flight location and altitude in the held out evaluation dataset.

Flight 1002

The goal of this flight was to do 2 compensation loops alongside free flight and a survey repetition. More detailed flight line information is available here. Note that Flux A and Mag 2 had some data integrity issues that led to Flux A being dropped from this flight and Mag 2 not having a signal at 180 degree headings during pitch/roll maneuvers. The affected lines for the problem with Mag 2 are: 1002.02, 1369.00 and 1002.20

Flight 1003

The goal of this flight was to collect additional free flight data over several hours. More detailed flight line information is available here. Note that Mag 2 had data issues at a 180 degree heading during pitch/roll maneuvers. The affected lines for the problem with Mag 2 are: 1003.01

Flights 1004 & 1005

The goal of these flights was to repeat a known mini-survey within Eastern Ontario. Due to weather concerns this collection was split into two data collections. More detailed flight line information is available here and here.

Flight 1006

The goal of this flight was to perform compensation maneuvers at a variety of altitudes and locations. Additional commentary from the pilot is available here, and more detailed flight information is available here. Note that Mag 2 had data issues at a 180 degree heading during pitch/roll maneuvers. The affected lines for the problem with Mag 2 are: 1006.02, 1006.03, 1006.06, 1006.07, and 1006.08.

Flight 1007

The goal of this flight was to collect free flight data within the Perth mini-survey and the Eastern Ontario/Renfrew regions. More detailed flight information is available here.

Data Sharing Agreement

Please read the full Data Sharing Agreement located here.

By granting You access to Data, the Air Force grants You a limited personal, non-exclusive, non-transferable, non-assignable, and revocable license to copy, modify, publicly display, and use the Data in accordance with this AGREEMENT solely for the purpose of non-profit research, non-profit education, or for government purposes by or on behalf of the U.S. Government. No license is granted for any other purpose, and there are no implied licenses in this Agreement. This Agreement is effective as of the date of approval by Air Force and remains in force for a period of one year from such date, unless terminated earlier or amended in writing. By using Data, You hereby grant an unlimited, irrevocable, world-wide, royalty-free right to The United States Government to use for any purpose and in any manner whatsoever any feedback from You to the Air Force concerning Your use of Data.